It is unreasonable to expect users to manually fix apt-get's cache files
when they become corrupted. As a long-time apt-get user who has
encountered this bug frequently, I can attest to its age, and am
surprised it has not been fixed after all these years. For proof, simply
see this bug report from 2001: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=93453

At minimum, apt-get should catch the corruption and exit gracefully
whilst informing the user how to fix it.

Better would be for apt-get to warn of the corrupted file and fix it
automatically.

Best would be to fix the bug(s) causing the corruption, thus avoiding
this issue entirely.


As to its difficulty: that just makes it more challenging and rewarding to fix, 
right? ;)

** Bug watch added: Debian Bug tracker #93453
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93453

-- 
[MASTER] aptitude/apt-get segmentation fault on currupted cache
https://bugs.launchpad.net/bugs/16467
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

Reply via email to