portage option missing

Klavs · Guru Joined: 22 May 2002 Posts: 536 Location: Denmark

Hi guys,

I run a "stable" gentoo - and I have one annoying thing with portage in this regard.

Once in a while I install a package which is not considered stable yet - and when I run the emerge -u world -p - it wants to downgrade those - which is ofcourse normal behavior.

What I'm missing, is a --no-downgrade option.

Am I the only one? or how do you guys get around it?
_________________
Best regards,

Klavs Klavsen
Denmark

Working with Unix is like wrestling a worthy opponent.
Working with windows is like attacking a small whining child
who is carrying a .38.

hhaamu · Posted: Fri Jan 24, 2003 1:25 pm Post subject:

You need to put something in your /var/cache/edb/world file. For example, I have this for kde:

dannym · n00b Joined: 01 Nov 2002 Posts: 13 Location: Austria

Hm, but isn't that file overwritten on each emerge sync?

Kumba · Posted: Thu Feb 27, 2003 7:33 am Post subject:

It's called "Injecting", or "emerge -i", and no, it's not overwritten on the next rsync. It basically installs a stub entry into the portage database so portage thinks the package is installed when it really isn't. Ya just gotta be careful though next time an upgrade for that package comes out. Always add --pretend or -p to your "emerge -u world" line to see what it wants to merge first before blindly having it update world. You can also pass the --deep option too for a more aggressive search of stuff to up/downgrade.

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

Klavs · Guru Joined: 22 May 2002 Posts: 536 Location: Denmark

But if I -I a package - or manually insert it into /var/cache/edb/world it still wants to downgrade it !!

I get this output from emerge -u world -p
UD] media-video/nvidia-kernel-1.0.3123-r2 [1.0.4191-r1]

and I have this at the top of /var/cache/edb/world:
>=media-video/nvidia-kernel-1.0.4191-r1

Can anyone answer me why?
_________________
Best regards,

Klavs Klavsen
Denmark

Working with Unix is like wrestling a worthy opponent.
Working with windows is like attacking a small whining child
who is carrying a .38.

dannym · n00b Joined: 01 Nov 2002 Posts: 13 Location: Austria

yayyy!!!!

With 2.0.47-r6 portage:

emerge -u world -p -U

*jumps around*

Thank you thank you whoever added this option

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

dannym: I don't think this is a complete fix yet. If portage is working the way I think it is, only ebuilds with different SLOTs will not downgrade. See Minor issue with portage 2.0.47-r6 for details.
_________________
Quis separabit? Quo animo?

dannym · n00b Joined: 01 Nov 2002 Posts: 13 Location: Austria

Well, for me the -U fixed it completely. My issue was: I had experimental packages of libraries / programs installed. then I removed the "accept experimental" thing from the make.conf again and then did emerge -up world... boom it wanted to downgrade ~10% of my system's packages

As for what I understand slots are for having multiple "main" versions of a package installed, say gtk+ 1.2 and gtk+ 2.0 (because many prgs still need 1.2 and cant do 2.0). one would have slot 1 and one would have slot 2 so that both can be installed in parallel under the same name. (rpm-based distros try to do that by appending the main version to the package name: "libxml2" and "libxml", f.e.)

afaik portage -U distinguishes the slots but within one slot "area" it does the version checking correctly. What would it be supposed to do across slots?

Dunno

dannym · n00b Joined: 01 Nov 2002 Posts: 13 Location: Austria

As for the one nvidia-kernel per kernel stuff, I think that it is no problem to have multiple nvidia kernel modules for different kernels installed while having only one nvidia-glx.

I assume deps:
kernel<->nvidia-kernel<->nvidia-glx

So nvidia-glx is not directly affected by the kernel version in any way. Thus _it_ does not need the slot=$KV. It *does* need the dependency for a nvidia-kernel like this: having the exact same version as nvidia-glx and having the slot (kernel-version).

But as for what happens when you use nvidia 3123, install a nvidia kernel mod for 2.4.19, then upgrade the kernel to 2.4.20, then upgrade nvidia to 4191, then/by (add)install(ing) the new nvidia kernel mod (for 2.4.20).

Would nvidia-kernel-1.0.3123 with slot 2.4.19 be
1) kept or
2) upgraded to nvidia-kernel-1.0.4191 with slot 2.4.20 or
3) would it block the upgrading to 4191 (including glx) until it were removed?

hmm...