#1136785 libpicohttpparser1: dpkg is loosing accounting of /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 on installation #1136785
- Package:
- libpicohttpparser1
- Source:
- libpicohttpparser1
- Submitter:
- Alexandre Detiste
- Date:
- 2026-05-16 06:53:02 UTC
- Severity:
- normal
Hi, When libpicohttpparser1 is installed, I'm getting a "mysterious" /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 file that neither dpkg nor the debian website knows about https://packages.debian.org/sid/amd64/libpicohttpparser1/filelist I got tipped of this be my cruft-ng tool that check for files unknow to dpkg. That is just so weird :/ I'd be glad if you figured out why this happens. Greetings Alexandre $ dpkg -L libpicohttpparser1 /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1.2+ds /usr/share /usr/share/doc /usr/share/doc/libpicohttpparser1 /usr/share/doc/libpicohttpparser1/changelog.Debian.gz /usr/share/doc/libpicohttpparser1/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libpicohttpparser1 $ dpkg -S /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 dpkg-query: aucun chemin ne correspond à /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 $ ls -l /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 lrwxrwxrwx 1 root root 27 15 mai 22:16 /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 -> libpicohttpparser.so.1.2+ds $ sudo cruft cruft report: ven 15 mai 2026 22:16:44 ---- missing: dpkg ---- /etc/apparmor.d/disable ---- unexplained: / ---- /etc/apt/preferences.d/tchet /etc/icedtea-web /usr/lib/python3/dist-packages/colorclass/py.typed /usr/lib/python3/dist-packages/omg/__init__.pyi /usr/lib/python3/dist-packages/omg/py.typed /usr/lib/systemd/user/cron-user-mail@.service /usr/lib/x86_64-linux-gnu/libpicohttpparser.so.1 <---------- end. $
Am Freitag, dem 15.05.2026 um 22:20 +0200 schrieb Alexandre Detiste: After installing the package an activate-noawait ldconfig trigger has creates the libpicohttpparser.so.1 symlink. This is something that the debuild toolchain is doing automatically, so I think there is no need to do it explicitly. Unfortunately I do not understand why this is happening myself. Sincerely, Joachim
Hi, I think you cannot use DEB_VERSION_UPSTREAM as is as it will contain "+ds" d/rules needs more sed-fu to cut of at "1.2" Le ven. 15 mai 2026 à 23:00, Joachim Zobel <jzobel@heute-morgen.de> a écrit : Debian is indeed very hard to break, full of safeties.
Am Freitag, dem 15.05.2026 um 23:33 +0200 schrieb Alexandre Detiste: This is a weirdness and will be fixed. Not sure, but in my opinion it is not safety but the usual way to do this. Sincerely, Joachim