Two options: (a) If we release the GIL, and call pkgAllUpgrade(), pkgAllUpgrade() can modify the depCache. If now another (Python)-thread accesses the depcache, we're lost (and that's potentially a real bug, given that APT is almost totally not thread-safe).
(b) The cache file is broken - we rule out too short cache files now, as that is detected since August 2011, so it can basically only be caused by a broken storage or memory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/842676 Title: aptd crashed with SIGSEGV in pkgProblemResolver::MakeScores() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/842676/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
