Bug#613775: aptitude upgrades lose extended state (automatic status)
On 2011-02-17 11:44 +0100, David Kalnischkies wrote:
> On Thu, Feb 17, 2011 at 11:10, Sven Joachim <email@example.com> wrote:
>> This may make sense for apt-get, but I would like to be able to upgrade
>> some selected packages _without_ changing their manual/automatic state.
>> Especially in interactive situations (like aptitude's TUI/GUI or in
>> synaptic) this seems better. Especially since there are dedicated
>> commands for changing the manual/auto status.
> Which is fine, the software just shouldn't request to alter the autobit if
> it doesn't want it to be changed - the FromUser bit is exactly responsible
> for that and nothing else, so why setting it if you don't want it?
> Just to be clear, it was possible that the autobit was changed already by
> the "old" behavior which doesn't make sense in your usecase as well.
> I discussed that with Michael quiet a bit and we don't see a reason for
> this "random" condition: Flipping the autobit only if the package is not
> marked changes depending on what requests are served before or after
> in the same run - so the behavior depends on the order in which the
> requests are executed which is always bad.
>>> So could you please describe more detailed why do you consider it a bug
>>> in APT rather than in aptitude? Exact commands you use for example?
>> I did not run anything else than "aptitude safe-upgrade", IIRC.
> apt-get (dist-)upgrade does all MarkInstall requests in this situation
> with FromUser == false as no installation was requested explicitly.
> The question is now why aptitude sets the FromUser bit here to true…
Because it does not set it at all, it only ever uses the first two
parameters of MarkInstall, so FromUser is always true.
Anybody who wants to revive aptitude development should look into
modernizing these parts.