On Thu, Mar 06, 2008 at 05:24:11PM +0100, Richard Hartmann <[EMAIL PROTECTED]>
was heard to say:
> On Thu, Mar 6, 2008 at 4:27 PM, Daniel Burrows <[EMAIL PROTECTED]> wrote:
>
>
> > > At the moment, I am forced to either set _all_ packages as
> > > automatically or manually installed when doing security upgrades.
> >
> > Ouch. "aptitude install blah" is clearing the manual flag? That's a
> > bug. Which packages are you seeing this on and in what circumstance?
> > (bearing in mind #446609, that "aptitude show" reverses the automatic
> > flag)
>
> No, aptitude install foo&M would do that (which is OK).
OK, but then i'm confused.
> What I mean is that I am forced to either set all packages to manually
> installed or set all packages to automatically installed during installation.
> It is not possible to tell aptitude 'in case this package is already
> installed,
> do not touch its manually/automatically installed flag and just install it',
> which is why I filed this wishlist item.
That's exactly what aptitude should be doing (see below).
> To clarify what I want to do:
>
> 1) I have a system with a few hundred or thousand packages
> 2) There is a security vulnerability for both foo and bar
> 2.1) foo has been installed manually
> 2.2) bar has been installed automatically to satisfy a Depends
> 3) I want to install new versions of both foo and bar in one go
> 4) I want to be able to do this without needing to know wether
> foo or bar were installed manually or automatically. Neither do
> I want the flag for either of them to change after the installation.
I'm sorry if I was unclear before. What I mean was that in step 4 you
run:
aptitude install foo bar
or go into the curses interface and do the same thing. Just
"installing" (i.e., upgrading) a already-installed package will not
(should not) touch its auto flag. Since you have apparently encountered
a case where it does, this is a bug and I need more information to
reproduce it. e.g., the result of "aptitude-create-state-bundle" should
be enough to see what's happening.
To be even more clear: suppose that I can upgrade libgif4 and
ttf-opensymbol, but only libgif4 is automatically installed:
[EMAIL PROTECTED]:~$ aptitude search '^libgif4$|^ttf-opensymbol$'
iuA libgif4 - library for GIF images (library)
iu ttf-opensymbol - The OpenSymbol TrueType font
Now running "aptitude install libgif4 ttf-opensymbol" will upgrade
these two packages but leave their auto flags intact:
[EMAIL PROTECTED]:~# aptitude install libgif4 ttf-opensymbol
[snip]
[EMAIL PROTECTED]:~$ aptitude search '^libgif4$|^ttf-opensymbol$'
i A libgif4 - library for GIF images (library)
i ttf-opensymbol - The OpenSymbol TrueType font
In other words, the solution to your problem is not to add a new
feature that does what "install" is supposed to do, but to figure out
what's going on for you and fix "install" to behave the way it's
supposed to.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
