© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Excuse the maybe ignorant question, but why is it assumed to be "just the way it is" if a package chokes on its own config data after an update? Certainly it should be expected to handle such a conflict in some graceful way?