Unattended-upgrades may handle this exception by exiting with failure
and not re-raising it to the top.
** Changed in: unattended-upgrades (Ubuntu)
Status: Opinion => Triaged
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => Low
--
You received this bug
** Tags added: id-5e8dd41b421c45209b1bd8e6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871145
Title:
apt.Cache.clear() -> apt.Cache._depcache.init() raises Error
To manage notifications about
@juliank Well, I have to agree in this particular case. If the package
archive was available u-u could try to fix it by even calling dpkg to
reinstall it, but the archive was not available.
At least u-u logs this error and includes it in the email now and only
after that it raises it again for
If clear() fails, you're a bit lost, but I'm not sure what you'd want to
do here, the system is completely broken at that point.
** Changed in: python-apt (Ubuntu)
Status: New => Opinion
** Changed in: unattended-upgrades (Ubuntu)
Status: Opinion => New
--
You received this bug
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871145
Title:
apt.Cache.clear() -> apt.Cache._depcache.init() raises Error
To manage notifications about this bug go