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]
