# Unable to locate package bashdb

**URL:** <https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333>\
**Category:** Support Debian\
**Created:** [Mai 27, 2019, 8:18 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333 "2019-05-27T08:18:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmchen](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/k/3d9bf3/32.png) [@kmchen](https://www.debian-fr.org/u/kmchen)\
**Post date:** [Mai 27, 2019, 8:18 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/1 "2019-05-27T08:18:06Z")

</div>

Bonjour à tous  
Impossible de trouver bashdb sur ma debian 9. Pourtant il devrait être dispo sur une distrib de base d’après [https://www.howtoinstall.co/en/debian/stretch/bashdb](https://www.howtoinstall.co/en/debian/stretch/bashdb)  
Je note au passage un petit pb avec Appstream mais d’après ce que j’ai vu sur d’autres forums on peut ignorer ces warnings mais je les rapporte ici au cas où :

```nohighlight
root@kmcs:/home/kmc# apt update 
...
Get:69 http://cdn-fastly.deb.debian.org/debian sid/contrib DEP-11 128x128 Icons [214 kB]
Fetched 27,5 MB in 28s (959 kB/s)                                                    
The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.
Reading package lists... Done
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi'
E: Sub-process returned an error code
root@kmcs:/home/kmc# appstreamcli --version
AppStream CLI tool version: 0.10.6
root@kmcs:/home/kmc# apt-get install bashdb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package bashdb

```

```nohighlight
root@kmcs:/home/kmc# cat /etc/apt/sources.list
# 

# deb cdrom:[Debian GNU/Linux 8 _stretch_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150908-22:00]/ stretch main

deb http://httpredir.debian.org/debian/ stretch main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free

# stretch-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://httpredir.debian.org/debian/ stretch-updates main contrib non-free

#backports
deb http://httpredir.debian.org/debian stretch-backports main contrib non-free

#Unstable
deb http://httpredir.debian.org/debian/ sid main contrib non-free

```

```nohighlight
root@kmcs:/home/kmc# cat /etc/apt/sources.list.d/
cisofy-lynis.list tangostudio-debian.list  
postgres.list teamviewer.list          

```

```nohighlight
root@kmcs:/home/kmc# cat /etc/apt/preferences.d/testing-avec-sid 
Package: *
Pin: release n=sid
Pin-Priority: 100

```

---

<div class="post-metadata">

**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\
**Post date:** [Mai 27, 2019, 8:27 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/2 "2019-05-27T08:27:23Z")

</div>

Le paquet n’est plus présent dans les dépôts Debian officiels :

[https://packages.debian.org/search?arch=s390x&keywords=bashdb](https://packages.debian.org/search?arch=s390x&keywords=bashdb)

La raison, le retrait pur et simple :

[https://tracker.debian.org/pkg/bashdb](https://tracker.debian.org/pkg/bashdb)

---

<div class="post-metadata">

**Author:** ![kmchen](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/k/3d9bf3/32.png) [@kmchen](https://www.debian-fr.org/u/kmchen)\
**Post date:** [Mai 27, 2019, 8:32 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/3 "2019-05-27T08:32:11Z")

</div>

Un autre moyen pour debugger du bash sous Debian ?

---

<div class="post-metadata">

**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\
**Post date:** [Mai 27, 2019, 11:18 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/4 "2019-05-27T11:18:58Z")

</div>

C’est à dire ?  
Avec l’option -x j’ai mon déroulé et je vois où ça bloque en générale, voir mettre un set -x dans tes scripts au besoin, et l’établissement d’un log est appréciable en programmation.

---

<div class="post-metadata">

**Author:** ![Sputnik93](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/s/35a633/32.png) [@Sputnik93](https://www.debian-fr.org/u/Sputnik93)\
**Post date:** [Mai 27, 2019, 12:52 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/5 "2019-05-27T12:52:02Z")

</div>

Il y a le paquet shellcheck, qui peut se montrer intéressant.

---

<div class="post-metadata">

**Author:** ![kmchen](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/k/3d9bf3/32.png) [@kmchen](https://www.debian-fr.org/u/kmchen)\
**Post date:** [Mai 27, 2019, 3:16 UTC](https://www.debian-fr.org/t/unable-to-locate-package-bashdb/79333/6 "2019-05-27T15:16:11Z")

</div>

Oui j’utilisais -x jusqu’à présent mais je voulais voir s’il y avait mieux.  
Je vais voir shell check  
merci pour vos indications