This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package python-apt - 0.9.3.5ubuntu3
---
python-apt (0.9.3.5ubuntu3) trusty-proposed; urgency=medium
* DepCache: Check that candidate we are setting belongs to package
* Raise CacheMismatchError if objects passed to DepCache are from different
cache
This bug was fixed in the package python-apt -
1.1.0~beta1ubuntu0.16.04.2
---
python-apt (1.1.0~beta1ubuntu0.16.04.2) xenial; urgency=medium
* python/tag.cc: Fix invalid read in TagFileNext
* DepCache: Check that candidate we are setting belongs to package
* Raise
The updates work fine, as can be seen by the autopkgtest, and a manual
run also confirms it:
= xenial =
$ run test
Changed []
<..crash..>
$ add proposed and upgrade
Unpacking python3-apt (1.1.0~beta1ubuntu0.16.04.2) over
(1.1.0~beta1ubuntu0.16.04.1)
$ run test
Changed []
= trusty =
$ run
Hello errors.ubuntu.com, or anyone else affected,
Accepted python-apt into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.1.0~beta1ubuntu0.16.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing
** Description changed:
[Impact]
Some applications, like unattended-upgrades or update-manager, reopen the apt
cache. They also keep around old apt.Package objects however, and operate on
them after reopening. Under the hood, this means that apt_pkg.Package objects
belonging to an old
6 matches
Mail list logo
