Control: forcemerge 8639 -1 Hi!
On Tue, 2014-06-24 at 18:28:43 +0200, Harald Dunkel wrote: > On 06/24/14 12:27, Guillem Jover wrote: > > The correct solution is usually to upgrade to a fixed version. > > Sorry to say, but I disagree. Removing a package should not be > blocked completely, if it is not in a dependency chain of > something else. Installing a newer version might not be an > option. A packages that cannot be removed/purged is (RC) buggy, and needs to be fixed, even on stable. dpkg cannot know if the contents of the maintainer scripts are important, and required for a proper cleanup of the package. Not running the scripts might leave junk on the filesystem, stray processes running or worse. I can agree that having a --force-script-errors or similar (as requested in the other bug report) can be convenient in this kind of situations if one does not want or cannot wait for a fixed packages. It's still not the correct solution, which should be obvious by the fact one would have to use a --force option. :) > If you think this is a dup, then please merge. Yeah, merged now. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
