On Sat, Aug 16, 2008 at 05:42:42PM +0100, Chris Jackson <[EMAIL PROTECTED]> was heard to say: > severity 477665 serious > thanks > > Regardless of the circumstances, "don't install" should mean "don't > install". Not taking action when the user requests it is one thing, > but taking action that user is under the impression they have > instructed the program *not* to perform (i.e. ignoring user input) is > a serious matter. > > I see no reason why this option *shoudn't* work in interactive mode, > especially since the current situation means that when the option is > explicitly given to a non-interactive command and the user drops back > to interactive, the program "forgets" that it has happened.
This is not a policy violation and it does not, in my opinion, make the package unfit for release (especially since the bug has existed for multiple years and across multiple Debian releases). Unless you are a release manager, this is the wrong severity for this bug (see http://www.debian.org/Bugs/Developer#severities). To fix this bug, what needs to happen is: (1) Create and document a new option, Aptitude::Download-Only, defaulting to "false". (2) Change the code that checks for Aptitude::CmdLine::Download-Only to also accept Aptitude::Download-Only. (3) Find the places where download_install_manager is instantiated (I think there's only one, in ui.cc) and make its instantiation conditional on Aptitude::Download-Only. This is not hard, I just haven't gotten around to it because I have other things I'm working on. If you want it to happen faster, you can do it yourself, but raising the severity to inappropriate levels will not fix the code. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
