On Fri, Dec 28, 2007 at 04:04:02PM -0500, "Douglas A. Tutty" <[EMAIL PROTECTED]> was heard to say: > On Fri, Dec 28, 2007 at 04:35:36PM -0300, Gabriel Parrondo wrote: > > I'm not sure what does it mean with "will not be saved when you...". Is > > it that there will be no way to know that the package was reinstalled or > > that the action will be executed immediately and not when I press g? Or > > maybe something else. > > It means what it says. Aptitude keeps track of a package's state: > installed, not-installed, installed-but-not-configured. It contains no > state "reinstalled". So, you tell aptitude to reinstall a package. It > fetches the .deb and tells dpkg to install it. When dpkg returns, it > either returns successful or not, but aptitude has no way to record a > correct reinstall. You should watch the screen.
Just to clarify, the problem isn't just that aptitude doesn't have a state for "reinstall". It actually did at one point (#167236, #121346), but there's no way for aptitude to find out from the dpkg/apt layer whether a reinstall that it requested actually took place. (ideally the reinstall state should persist until the reinstallation is performed, then be removed) Without this information it has to either arbitrarily preserve all reinstalls, or arbitrarily drop all of them, and after getting the bugs referenced above, I decided that dropping all of them was a less annoying behavior. Usually aptitude figures this sort of thing out with an after-the-fact examination of package states, but since a reinstallation leaves packages in the same state that they started in, this won't work to detect reinstalls. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
