Fix handling of holds

Project Lead:

mandyke (23 credits)

 

Bounty:

US $24.69(Sponsor Project)

Goal funding:

More Less
Aptitude's hold status is distinct to other apt front ends, which use the dpkg status.  The goal of this sub-project is to implement 'aptitude hold pkg' in the same way that other front ends do.
 
Note: You can propose changes using the forum below.
Aptitude's hold status is distinct to other apt front ends, which use the dpkg status.  The goal of this sub-project is to implement 'aptitude hold pkg' in the same way that other front ends do.

http://bugs.debian.org/137771

(and others)

aptitudeDepCache and it's internal classes will have to be updated to support reading hold status directly from dpkg states, not just 'updating' from there in an ad-hoc manner.

Running 'apt-mark hold' on a package, then aptitude, must have that hold shown in aptitude *always*.  Same for unhold.

Running 'aptitude hold' on a package, then another front end (which uses dpkg holds), must show the hold set by aptitude.  Same for unhold.

Running any combination of other aptitude, apt-get, and other front end commands between setting a hold (except commands such as 'apt-get install foo', which would unhold the package foo) should not result in aptitude confusing the hold status of any package the next time it is run.

Test cases must also be provided using the framework requested in:

http://www.fossfactory.org/project/p308

They should demonstrate the correctness of the solution and the problems with the current version of aptitude (0.6.7).
Post a Comment

There are currently no comments in this forum.

FOSS Factory Source