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 <https://wiki.debian.org/Teams/Dpkg/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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181111/d3e27a8c/attachment-0002.sig>