On Sat, Dec 29, 2007 at 08:30:15AM -0800, Daniel Burrows wrote: > On Fri, Dec 28, 2007 at 04:04:02PM -0500, "Douglas A. Tutty" <[EMAIL > PROTECTED]> was heard to say: > 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.
Why not have aptitude: 1) retreive the deb(s) required; 2) deinstall the package and verify that it is nolonger installed; 3) immediatly reinstall the package and verify that that it is now installed. Currently running programs won't be affected, only attempts to run new instances while the reinstall is happening. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
