Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
> On (02/08/05 09:49), Jules Dubois wrote: > > I suggest, rather than using 'h' for "hold", using 'm' for "mark as manually > > installed" for packages the OP is certain he wants to keep. In this way, > > those packages and their dependencies are both "protected" and upgradable. > > I just found another useful option in the onscreen help ':' holds the current version for this upgrade but won't prevent future upgrades. Very useful, where you're waiting for a bug corrected version to be uploaded. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On (02/08/05 09:49), Jules Dubois wrote: > On Monday 01 August 2005 06:19, Clive Menzies <[EMAIL PROTECTED]> > (<[EMAIL PROTECTED]>) wrote: > > > On (01/08/05 12:32), Adam Funk wrote: > >> Inspired by the advice on this group and the -s option, I'm trying out > >> aptitude. But I'm surprised by this: > >> > >> followed by a long list of packages, some of which I'm running right now. > >> How does aptitude determine this list, and what's the best way to correct > >> it? > >> > > Briefly, run aptitude in interactive mode - ie # aptitude > > If you press g (only once), the proposed actions will be displayed, you > > can then 'h' hold packages you don't want removed. > > I suggest, rather than using 'h' for "hold", using 'm' for "mark as manually > installed" for packages the OP is certain he wants to keep. In this way, > those packages and their dependencies are both "protected" and upgradable. > good suggestion ;) > > see man aptitude > > There's also a very nice "aptitude user's guide". IIRC, the package is > named aptitude-doc or aptitude-doc-en (for EN speakers). > I've never bothered to install it . probably about time I did. > > If you're running etch or sid you definitely ought to install > > apt-listbugs before upgrading anything. > > But not if he's running Sarge? I wasn't sure whether it is available for sarge but I guess it is. I've been running 'stable' servers (woody and sarge) for the last couple of years and not felt the need. . but maybe better safe than sorry ;) Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On Monday 01 August 2005 06:19, Clive Menzies <[EMAIL PROTECTED]> (<[EMAIL PROTECTED]>) wrote: > On (01/08/05 12:32), Adam Funk wrote: >> Inspired by the advice on this group and the -s option, I'm trying out >> aptitude. But I'm surprised by this: >> >> followed by a long list of packages, some of which I'm running right now. >> How does aptitude determine this list, and what's the best way to correct >> it? >> > Briefly, run aptitude in interactive mode - ie # aptitude > If you press g (only once), the proposed actions will be displayed, you > can then 'h' hold packages you don't want removed. I suggest, rather than using 'h' for "hold", using 'm' for "mark as manually installed" for packages the OP is certain he wants to keep. In this way, those packages and their dependencies are both "protected" and upgradable. > see man aptitude There's also a very nice "aptitude user's guide". IIRC, the package is named aptitude-doc or aptitude-doc-en (for EN speakers). > If you're running etch or sid you definitely ought to install > apt-listbugs before upgrading anything. But not if he's running Sarge? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
> > Even if there's a third, neutral, unmarked state - it's still a > > problem in my eyes when users switch from dselect to aptitude. > > It's not a problem if you tell aptitude what to do when you start using it. How would I do that? Even if I wanted to go through all packages and mark them, how would I tell "manually installed with aptitude, will not touch" from "installed with whatever, treating as auto-installed"? > In addition, if you think there is a bug in aptitude, please file a bug > report. Considering all the bug reports already filed on this or related issues I think I'll wait for them to be fixed and then try aptitude again. Examples: #299009: aptitude: Different package status results from command line vs. interactive use #316027: aptitude: "upgrade" didn't work with unfullfilled dependencies #164869: aptitude should be less aggressive about upgrading #200415: aptitude: dependencies are not handled well when upgrading as well as various other reports about aptitude not playing well with / ignoring state changes made by other package manager frontends. Although aptitude incorporates some great features, especially marking packages installed only because they were depended upon, I have purged it for now. I really can't say it's safe to use. C.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On (01/08/05 19:17), Clive Menzies wrote: > To: debian-user@lists.debian.org > From: Clive Menzies <[EMAIL PROTECTED]> > Date: Mon, 1 Aug 2005 19:17:30 +0100 > Subject: Re: Aptitude erroneously thinks many packages are unused and wants > to remove them. > > On (01/08/05 13:56), Bryan Donlan wrote: > > On 8/1/05, Bryan Donlan <[EMAIL PROTECTED]> wrote: > > > On 8/1/05, Clive Menzies <[EMAIL PROTECTED]> wrote: > > > > On (01/08/05 12:32), Adam Funk wrote: > > > > > Inspired by the advice on this group and the -s option, I'm trying out > > > > > aptitude. But I'm surprised by this: > > > > > > > > > > $ aptitude -s upgrade > > > > > Reading Package Lists... Done > > > > > Building Dependency Tree > > > > > Reading extended state information > > > > > Initializing package states... Done > > > > > Reading task descriptions... Done > > > > > The following packages are unused and will be REMOVED: > > > > > > > > > > followed by a long list of packages, some of which I'm running right > > > > > now. > > > > > How does aptitude determine this list, and what's the best way to > > > > > correct > > > > > it? > > > > > > > > > There've been a few posts on this over the last few days; have a look at > > > > the d-u list archive. > > > > > > > > Briefly, run aptitude in interactive mode - ie # aptitude > > > > If you press g (only once), the proposed actions will be displayed, you > > > > can then 'h' hold packages you don't want removed. > > > > > > A better option is '+' - 'h' will disable updates. > > > > Correction, '=' will disable updates, 'h' doesn't do anything afaik > > > Yes, my bad I was thinking of what's displayed on the left ;( > D'oh, I don't know where my brain was. The point about holding packages '=' is that it's useful if you are getting conflicts and and dependency problems. Sometimes, upgrading a package will 'break' something else. In this event 'holding' it should resolve the problem. It is sometimes an iterative process. Hold everything that is creating any sort of problem and upgrade what's left. Once that's completed go back to the 'held' packages and try '+' one by one and watch the top for 'Broken n' where n is the number of broken packages. As soon as something 'breaks' examine the warnings on the broken package(s) and if necessary 'hold' the package that caused the break. Bear in mind that if you press 'g' to see the packages being upgraded, you won't see which other packages have broken; press 'q' to get back to the full list and then search for the broken packages: / ~b Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
> That's the point. _It_ (aptitude hasn't been told to install them. > This situation often arises when packages have been installed with > apt-get, in which case it's not aptitude's fault that _it_ doesn't know > that you want to install them. I'd assumed that there were just two package states concerning that: manually installed: not marked with A auto-installed: marked with A Even if there's a third, neutral, unmarked state - it's still a problem in my eyes when users switch from dselect to aptitude. Where does it say "thou shalt only use one package managing frontend?" C.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
> Aptitude shouldn't remove packages you've told it to install - but it > doesn't know whether packages installed through other means (apt-get, > dselect, dpkg -i, etc) were manually or automatically installed. AFAIK I had only ever used aptitude on that system. Besides, why not play it safe and assume that everything not explicitly tagged is manually installed? > Also, if you're on sid, there are a lot of uninstallable packages due to the > C++ transition I know. That's the point. dselect / apt-get just put these packages on hold themselves, while with aptitude I have to do it manually. C.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On 8/1/05, Christian Pernegger <[EMAIL PROTECTED]> wrote: > > Briefly, run aptitude in interactive mode - ie # aptitude > > If you press g (only once), the proposed actions will be displayed, you > > can then 'h' hold packages you don't want removed. > > Since this is basically the issue I brought up a day or so earlier... > > Why should users have to wade through a (potentially long) list of > packages and tell aptitude to install [+] or hold [=] the packages > they don't want removed? After all it's been told to install the > package at some point, and without an order to the contrary shouldn't > even consider removing it. Maybe an explicit upgrade order for a > single package should have this effect, but not the standard bring me > up to date sequence ([u], [U], [g], [g]). > > Again what's the advantage over the old "don't auto-remove a package > under any circumstances" behaviour? Especially given that this could > easily be adapted to ""don't auto-remove a package unless it is marked > auto (A)". Aptitude shouldn't remove packages you've told it to install - but it doesn't know whether packages installed through other means (apt-get, dselect, dpkg -i, etc) were manually or automatically installed. Also, if you're on sid, there are a lot of uninstallable packages due to the C++ transition - the only good solution in that case is to temporarily hold them as needed.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
> Briefly, run aptitude in interactive mode - ie # aptitude > If you press g (only once), the proposed actions will be displayed, you > can then 'h' hold packages you don't want removed. Since this is basically the issue I brought up a day or so earlier... Why should users have to wade through a (potentially long) list of packages and tell aptitude to install [+] or hold [=] the packages they don't want removed? After all it's been told to install the package at some point, and without an order to the contrary shouldn't even consider removing it. Maybe an explicit upgrade order for a single package should have this effect, but not the standard bring me up to date sequence ([u], [U], [g], [g]). Again what's the advantage over the old "don't auto-remove a package under any circumstances" behaviour? Especially given that this could easily be adapted to ""don't auto-remove a package unless it is marked auto (A)". C.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On (01/08/05 13:56), Bryan Donlan wrote: > On 8/1/05, Bryan Donlan <[EMAIL PROTECTED]> wrote: > > On 8/1/05, Clive Menzies <[EMAIL PROTECTED]> wrote: > > > On (01/08/05 12:32), Adam Funk wrote: > > > > Inspired by the advice on this group and the -s option, I'm trying out > > > > aptitude. But I'm surprised by this: > > > > > > > > $ aptitude -s upgrade > > > > Reading Package Lists... Done > > > > Building Dependency Tree > > > > Reading extended state information > > > > Initializing package states... Done > > > > Reading task descriptions... Done > > > > The following packages are unused and will be REMOVED: > > > > > > > > followed by a long list of packages, some of which I'm running right > > > > now. > > > > How does aptitude determine this list, and what's the best way to > > > > correct > > > > it? > > > > > > > There've been a few posts on this over the last few days; have a look at > > > the d-u list archive. > > > > > > Briefly, run aptitude in interactive mode - ie # aptitude > > > If you press g (only once), the proposed actions will be displayed, you > > > can then 'h' hold packages you don't want removed. > > > > A better option is '+' - 'h' will disable updates. > > Correction, '=' will disable updates, 'h' doesn't do anything afaik > Yes, my bad I was thinking of what's displayed on the left ;( '+' looks useful must go back to the man page Thanks Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On 8/1/05, Bryan Donlan <[EMAIL PROTECTED]> wrote: > On 8/1/05, Clive Menzies <[EMAIL PROTECTED]> wrote: > > On (01/08/05 12:32), Adam Funk wrote: > > > Inspired by the advice on this group and the -s option, I'm trying out > > > aptitude. But I'm surprised by this: > > > > > > $ aptitude -s upgrade > > > Reading Package Lists... Done > > > Building Dependency Tree > > > Reading extended state information > > > Initializing package states... Done > > > Reading task descriptions... Done > > > The following packages are unused and will be REMOVED: > > > > > > followed by a long list of packages, some of which I'm running right now. > > > How does aptitude determine this list, and what's the best way to correct > > > it? > > > > > There've been a few posts on this over the last few days; have a look at > > the d-u list archive. > > > > Briefly, run aptitude in interactive mode - ie # aptitude > > If you press g (only once), the proposed actions will be displayed, you > > can then 'h' hold packages you don't want removed. > > A better option is '+' - 'h' will disable updates. Correction, '=' will disable updates, 'h' doesn't do anything afaik
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On 8/1/05, Clive Menzies <[EMAIL PROTECTED]> wrote: > On (01/08/05 12:32), Adam Funk wrote: > > Inspired by the advice on this group and the -s option, I'm trying out > > aptitude. But I'm surprised by this: > > > > $ aptitude -s upgrade > > Reading Package Lists... Done > > Building Dependency Tree > > Reading extended state information > > Initializing package states... Done > > Reading task descriptions... Done > > The following packages are unused and will be REMOVED: > > > > followed by a long list of packages, some of which I'm running right now. > > How does aptitude determine this list, and what's the best way to correct > > it? > > > There've been a few posts on this over the last few days; have a look at > the d-u list archive. > > Briefly, run aptitude in interactive mode - ie # aptitude > If you press g (only once), the proposed actions will be displayed, you > can then 'h' hold packages you don't want removed. A better option is '+' - 'h' will disable updates.
Re: Aptitude erroneously thinks many packages are unused and wants to remove them.
On (01/08/05 12:32), Adam Funk wrote: > Inspired by the advice on this group and the -s option, I'm trying out > aptitude. But I'm surprised by this: > > $ aptitude -s upgrade > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > The following packages are unused and will be REMOVED: > > followed by a long list of packages, some of which I'm running right now. > How does aptitude determine this list, and what's the best way to correct > it? > There've been a few posts on this over the last few days; have a look at the d-u list archive. Briefly, run aptitude in interactive mode - ie # aptitude If you press g (only once), the proposed actions will be displayed, you can then 'h' hold packages you don't want removed. see man aptitude If you're running etch or sid you definitely ought to install apt-listbugs before upgrading anything. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
