Bug#704424: release-notes: sufficient-space hints give confusing advice

2013-04-01 Thread Justin B Rye
Jonathan Nieder wrote: Justin B Rye wrote: * Run aptitude and look for the Obsolete and Locally Created Packages category, which will contain packages from previous releases that you never bothered to remove. These may be obsolete, but unless they're *also* redundant

Bug#704424: release-notes: sufficient-space hints give confusing advice

2013-04-01 Thread Justin B Rye
Justin B Rye wrote: [...] It seems to me we should put all our coverage of redundant packages in 4.4.3 (mentioning apt-get autoremove and avoiding the word obsolete), put all our coverage of relic packages in 4.9, and leave the two sections completely unconnected. Here's an attempt at a patch

Bug#704424: release-notes: sufficient-space hints give confusing advice

2013-04-01 Thread Justin B Rye
Justin B Rye wrote: Is it still true that deborphan is highly recommended, or is that a leftover from the days when it was the only tool that implemented any of this functionality? And does popcon-largest-unused still work? It thinks I don't use my web browser or window manager. Is it

Bug#704424: release-notes: sufficient-space hints give confusing advice

2013-04-01 Thread Jonathan Nieder
Justin B Rye wrote: Justin B Rye wrote: [...] It seems to me we should put all our coverage of redundant packages in 4.4.3 (mentioning apt-get autoremove and avoiding the word obsolete), put all our coverage of relic packages in 4.9, and leave the two sections completely unconnected.

Bug#704424: release-notes: sufficient-space hints give confusing advice

2013-03-31 Thread Jonathan Nieder
Package: release-notes Version: r9661 Tags: wheezy patch Justin B Rye wrote: I don't see anything about apt-get autoremove in the copy I've just checked out of SVN... nothing about that or aptitude's older support for the same feature. Yeah, that was me guessing about the intent. There's no