On Wed, Jun 25, 2008 at 05:16:05AM +0800, Telemachus <[EMAIL PROTECTED]> was heard to say: > On the command line, I can no longer remove a package but keep one of the > auto-installed dependencies. I could swear that I used to be able to do this: > > aptitude purge mpd libshout3+
I thought this used to work as well. But I think I've found the problem in the code, and it goes back to at least 2002. Can you verify that this was working before? (because I could swear I remember using it) This may be due to the changes last year in how automatic packages are handled (although I can't see how). For my own future reference, the problem is that I use an action group to defer computation of, e.g., unused packages, until I'm done applying all the command-line actions. That's probably good overall, but it does mean that install commands won't cancel unused-removals since the unused-removal hasn't taken effect yet. Oh, the other thing that I can see that might have affected this is the change that caused the "install" operation on a package to not affect its automatic flag unless the package was already installed. Your suggestion seems like a good idea, but I'm not sure what the follow-on consequences would be if I just slapped it in right now. However, you can get a similar effect by doing: # aptitude remove mpd "libshout3&m" Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
