I wonder if this is a libapt issue.  If I recall correctly, this error
message is shown when opening the deb database (using libapt) fails or
when it throws an exception.  Do we have any libapt automated tests that
would help determine whether this is an adept issue or one of its
dependencies?  It seems like more and more bugs are touching this gray
area.

-- 
Adept should handle invalid repositories more gracefully
https://bugs.launchpad.net/bugs/81073
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to