Bug#913454: dpkg: warning: found unknown packages; this might mean the available database...

[積丹尼 Dan Jacobson]

I was able to catch this bug, because I have a machine in town which I
only use every five weeks or so, thus spanning the unexpected gap, that
others who upgrade more, or less, frequently, wouldn't have caught.

Bug#913454: dpkg: warning: found unknown packages; this might mean the available database...

[Stuart Prescott]

Control: reassign -1 apt 1.7.0
Control: severity -1 minor

> > Processing triggers for systemd (239-11) ...

systemd is an innocent party here; the operation was completed by dpkg and 
then the communication back and forth between apt and dpkg goes a little awry 
due to recent changes.

> > dpkg: warning: package not in status nor available database at line 1:
> > libx265-160:amd64 
[...]

The messages are harmless and don't occur in the default configuration (always 
purging is likely required) or when following the two-step upgrade procedure 
as normally recommended (upgrade followed by dist-upgrade).

It's likely that we want to document them in the release notes for buster if 
there is no way of preventing them from every appearing; apt developers, can 
you please clone this bug to release-notes if that is indeed the case?

(based on comments from DonKult on IRC; insightful comments are his and errors 
are mine)

Cheers
Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#913454: dpkg: warning: found unknown packages; this might mean the available database...

[Michael Biebl]

Control: tags -1 + moreinfo

Am 11.11.18 um 08:06 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 239-11
> 
> # aptitude full-upgrade
> 
> Processing triggers for systemd (239-11) ...
> dpkg: warning: package not in status nor available database at line 1: 
> libx265-160:amd64
> dpkg: warning: package not in status nor available database at line 2: 
> libplacebo5:amd64
> dpkg: warning: package not in status nor available database at line 3: 
> libisccfg160:amd64
> dpkg: warning: package not in status nor available database at line 4: 
> libupnp6:amd64
> dpkg: warning: package not in status nor available database at line 5: 
> libipt1:amd64
> dpkg: warning: package not in status nor available database at line 6: 
> libicu62:amd64
> dpkg: warning: package not in status nor available database at line 7: 
> perl-modules-5.26:all
> dpkg: warning: package not in status nor available database at line 8: 
> python3.6:amd64
> dpkg: warning: package not in status nor available database at line 9: 
> libisc169:amd64
> dpkg: warning: package not in status nor available database at line 10: 
> libperl5.26:amd64
> dpkg: warning: package not in status nor available database at line 11: 
> libunbound2:amd64
> dpkg: warning: package not in status nor available database at line 12: 
> libx264-152:amd64
> dpkg: warning: package not in status nor available database at line 13: 
> libsvgsalamander-java:all
> dpkg: warning: package not in status nor available database at line 14: 
> libprotobuf-lite10:amd64
> dpkg: warning: package not in status nor available database at line 15: 
> guile-2.0-libs:amd64
> dpkg: warning: package not in status nor available database at line 16: 
> libgdbm5:amd64
> dpkg: warning: package not in status nor available database at line 17: 
> liblwres160:amd64
> dpkg: warning: package not in status nor available database at line 18: 
> python3-pbkdf2:all
> dpkg: warning: package not in status nor available database at line 19: 
> librarian0:amd64
> dpkg: warning: package not in status nor available database at line 20: 
> python3-cairo:amd64
> dpkg: warning: package not in status nor available database at line 21: 
> libisccc160:amd64
> dpkg: warning: package not in status nor available database at line 22: 
> libbind9-160:amd64
> dpkg: warning: package not in status nor available database at line 23: 
> libprotobuf10:amd64
> dpkg: warning: package not in status nor available database at line 24: 
> libdns1102:amd64
> dpkg: warning: package not in status nor available database at line 25: 
> libpoppler74:amd64
> dpkg: warning: package not in status nor available database at line 26: 
> libpoppler77:amd64
> dpkg: warning: found unknown packages; this might mean the available database
> is outdated, and needs to be updated through a frontend method;
> please see the FAQ 
> W: APT had planned for dpkg to do more than it reported back (3117 vs 3170).
>Affected packages: guile-2.0-libs:amd64 libbind9-160:amd64 
> libdns1102:amd64 libgdbm5:amd64 libicu62:amd64 libipt1:amd64 libisc169:amd64 
> libisccc160:amd64 libisccfg160:amd64 liblwres160:amd64 libperl5.26:amd64 
> libplacebo5:amd64 libpoppler74:amd64 libpoppler77:amd64 
> libprotobuf-lite10:amd64 libprotobuf10:amd64 l

I can't see a bug caused by systemd here.
Please elaborate


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#913454: dpkg: warning: found unknown packages; this might mean the available database...

[積丹尼 Dan Jacobson]

Package: systemd
Version: 239-11

# aptitude full-upgrade

Processing triggers for systemd (239-11) ...
dpkg: warning: package not in status nor available database at line 1: 
libx265-160:amd64
dpkg: warning: package not in status nor available database at line 2: 
libplacebo5:amd64
dpkg: warning: package not in status nor available database at line 3: 
libisccfg160:amd64
dpkg: warning: package not in status nor available database at line 4: 
libupnp6:amd64
dpkg: warning: package not in status nor available database at line 5: 
libipt1:amd64
dpkg: warning: package not in status nor available database at line 6: 
libicu62:amd64
dpkg: warning: package not in status nor available database at line 7: 
perl-modules-5.26:all
dpkg: warning: package not in status nor available database at line 8: 
python3.6:amd64
dpkg: warning: package not in status nor available database at line 9: 
libisc169:amd64
dpkg: warning: package not in status nor available database at line 10: 
libperl5.26:amd64
dpkg: warning: package not in status nor available database at line 11: 
libunbound2:amd64
dpkg: warning: package not in status nor available database at line 12: 
libx264-152:amd64
dpkg: warning: package not in status nor available database at line 13: 
libsvgsalamander-java:all
dpkg: warning: package not in status nor available database at line 14: 
libprotobuf-lite10:amd64
dpkg: warning: package not in status nor available database at line 15: 
guile-2.0-libs:amd64
dpkg: warning: package not in status nor available database at line 16: 
libgdbm5:amd64
dpkg: warning: package not in status nor available database at line 17: 
liblwres160:amd64
dpkg: warning: package not in status nor available database at line 18: 
python3-pbkdf2:all
dpkg: warning: package not in status nor available database at line 19: 
librarian0:amd64
dpkg: warning: package not in status nor available database at line 20: 
python3-cairo:amd64
dpkg: warning: package not in status nor available database at line 21: 
libisccc160:amd64
dpkg: warning: package not in status nor available database at line 22: 
libbind9-160:amd64
dpkg: warning: package not in status nor available database at line 23: 
libprotobuf10:amd64
dpkg: warning: package not in status nor available database at line 24: 
libdns1102:amd64
dpkg: warning: package not in status nor available database at line 25: 
libpoppler74:amd64
dpkg: warning: package not in status nor available database at line 26: 
libpoppler77:amd64
dpkg: warning: found unknown packages; this might mean the available database
is outdated, and needs to be updated through a frontend method;
please see the FAQ 
W: APT had planned for dpkg to do more than it reported back (3117 vs 3170).
   Affected packages: guile-2.0-libs:amd64 libbind9-160:amd64 libdns1102:amd64 
libgdbm5:amd64 libicu62:amd64 libipt1:amd64 libisc169:amd64 libisccc160:amd64 
libisccfg160:amd64 liblwres160:amd64 libperl5.26:amd64 libplacebo5:amd64 
libpoppler74:amd64 libpoppler77:amd64 libprotobuf-lite10:amd64 
libprotobuf10:amd64 l

P.S., reading that FAQ didn't help.