Portage automatically attempts to update to the latest unmasked version of a package. The package.unmask file is one way around this, but some ebuilds have explicit version dependencies - you probably have one that depends on the stable version of fluxbox. One workaround is to have portage only upgrade packages, ignoring dependencies for earlier versions. You can do this with the -U switch (--upgrade-only), i.e.:
emerge -vDUup world (the short form for --deep is -D) On Wed, 2 Jul 2003 13:42:02 -0600 Shane Hickey <[EMAIL PROTECTED]> wrote: > Can anyone fill me in on this file. I emerge'd fluxbox-0.9.3 and I > want it to get ignored when I 'emerge -vu --deep world'. > > I see in /usr/portage/profiles/package.mask there is a line: > > # new fluxbox dev series. no guarentees. > >=x11-wm/fluxbox-0.9.0 > > So, based on something I read in the forums, I created > /etc/portage/package.unmask and I made it look like this: > > >=x11-wm/fluxbox-0.9.3 > > I then did an 'emerge -vu --deep world' before and after an 'emerge > sync' and it still wants to upgrade fluxbox. > > Also, how can you get a package ignored if it isn't specifically > masked by package.mask? > > That is, I emerge'd pan-0.14.0 and everytime I do an emerge world it > wants to go back to pan-0.13.4. I can't find pan anywhere in > /usr/portage/profiles/package.mask > > Thanks, > > -- > Shane Hickey <[EMAIL PROTECTED]>: Nerd > http://www.nerddiary.org > GPG KeyID: 777CBF3F > Key fingerprint: 254F B2AC 9939 C715 278C DA95 4109 9F69 777C BF3F > > -- > [EMAIL PROTECTED] mailing list >
pgp00000.pgp
Description: PGP signature
