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.
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: w
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: warni
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:
4 matches
Mail list logo
