I agree that -U will work, howerver, it still doesn't seem to fix the underlying problem of telling portage that package-2.3.4 is what is supposed to be on a system now and not the blessed package-1.2.3. The only way I've found to fix this is to go into /var/edb and change the world file to say: >=package-2.3.4 It seems there should be a way in /etc/portage to make this happen without having to muck with portages idea of what is in world. Maybe it's just me, but I'd like to edit a file somewhere to tell portage that I've emerged a thing or two that aren't standard and that is the way my particular system is now without having to resort to -U, since -U will miss any regressions in what should be stable everywhere else. (kportage comes to mind...I think it just went through a 'blessed' regression from 0.7 to 0.6.1, this would be missed by -U) -Rob On Wed, 9 Jul 2003 20:11:01 -0700, el lodger wrote > On Wed, 9 Jul 2003 20:51:08 -0600 > Brian Hall <[EMAIL PROTECTED]> wrote: > > > I create package.unmask and add this line to it (trying to prevent > > downgrade of pan): > > > > >=net-news/pan-0.14.0 > > > > and then I do: > > > > # emerge -Duvlp world > > try emerge -DUvlp world > > --upgradeonly (-U short option) > Updates packages, but excludes updates that would > result in a lower version of the package being > installed. SLOTs are considered at a basic level. > > try emerge -DUvlp world > > -- > > [EMAIL PROTECTED] mailing list > > > > -- > Powered by GENTOO LINUX > > -- > [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
