[Aptitude-devel] Bug#406976: aptitude: source-strictness is not strict enough

Steinar H. Gunderson sgunderson at bigfoot.com
Fri Mar 18 12:30:54 UTC 2016


On Fri, Mar 18, 2016 at 12:15:02PM +0000, Manuel A. Fernandez Montecelo wrote:
> This specific problem of this bug report about upgrading to experimental
> might be different because the solutions using "non-default releases"
> are placed in another level/tier, but the score that you were using is
> only relevant within the same tier /nowadays/ (I don't know back then),
> so no matter how much one changes the Source-Strictness it will not
> cross the boundaries.

Ah, so tiers trump scoring? I wasn't aware of that. And I don't think the UI
makes that clear in any reasonable way either.

> For complex and infrequent solutions, rejecting some actions of the
> first suggestions with 'r' in the solution screens/questions (both in
> curses and in command line) would probably be enough to guide very
> quickly towards a solution, in the absence of big problems like
> transitions that make your request impossible to fulfill..

I don't think I've ever used 'r'; I've just used 'n'. I wasn't aware that
you could do much more than just ask for the next solution.

/* Steinar */
-- 
Homepage: https://www.sesse.net/



More information about the Aptitude-devel mailing list