This bug was fixed in the package python-apt - 1.7.0~alpha0~ubuntu3
---------------
python-apt (1.7.0~alpha0~ubuntu3) cosmic; urgency=medium
* apt.Cache: Fix error in apt.Package caching
* apt: Fix typing errors and use mypy --strict
* Correctly handle missing candidate in Package.get_changelog
* apt.Cache: Remap objects when reopening cache (LP: #1773316)
* apt_pkg.DepCache: Raise CacheMismatchError if argument belongs to diff.
cache
* apt.debfile: Avoid exception in replaces_real_pkg for no-candidate packages
* apt.debfile.DebPackage: Handle no-candidate package in
_maybe_append_multiarch_suffix
* utils/get_debian_mirrors.py: Get data from salsa
-- Julian Andres Klode <j...@debian.org> Wed, 06 Jun 2018 16:09:32
-0700
** Changed in: python-apt (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1773316
Title:
Object of different cache passed as argument to apt_pkg.DepCache
method
Status in python-apt package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
Confirmed
Status in python-apt source package in Bionic:
Triaged
Status in update-manager source package in Bionic:
Won't Fix
Status in python-apt source package in Cosmic:
Fix Released
Status in update-manager source package in Cosmic:
Won't Fix
Bug description:
[Impact]
python-apt 1.6 raises an exception when objects of an old cache are passed to
a apt_pkg.DepCache methods for a different cache. Prior to that, those would
either segfault, succeed, or silently operate on a different object, as they
use package/version ids, and e.g. two different packages in the old and new
cache might have the same id.
With 1.6.1, we introduce a remapping algorithm that remaps objects of
apt.Cache() when calling apt.Cache.open(), allowing old objects to be
used after reopening, as long as they exist in the new cache. If they
don't exist in the new cache, apt_pkg.CacheMismatchError will be
raised from the apt_pkg layer.
[Test case]
import apt
c=apt.Cache()
p=c["apt"]
c.open()
p.mark_install()
[Regression potential]
Could be remapping to wrong items which would cause us to install a wrong
version, for example. Compared to pre-bionic, bionic is a regression already,
though, and any regression caused here is less important than
what we have now.
[Original bug report]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-manager. This problem was most recently seen with package version
1:18.04.11, the problem page at
https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
