emerge -Up world wants to downgrade a package?

andy

Is this a bug in Portage? I installed a masked version of smartmontools a while ago, and Portage now wants to remove it and install a lower version, even though I'm using the -U flag.

# emerge -Up world
>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild UD] sys-apps/smartmontools-5.0.45 [5.1.10]

The latest masked version is now 5.1.11, so I just upgraded to 5.1.11, and now emerge -Up world works normally and doesn't want to downgrade.

gigel · Guru Joined: 14 Jan 2003 Posts: 334 Location: .RO

are you using stable or unstable...
_________________
$emerge sux

andy · Posted: Sat May 24, 2003 10:25 pm Post subject:

I'm not sure what you mean... the version of smartmontools I am using is marked as unstable in Gentoo. The version of Portage installed is the latest stable version, 2.0.48. As I understand it the point of the -U flag is so you can have some things installed from unstable builds and not have them removed every time you update. Since the problem went away once I went to the latest unstable version, I'm guessing there is a bug in how Portage calculates versions when the version installed is between the stable and the latest unstable version.

gigel · Guru Joined: 14 Jan 2003 Posts: 334 Location: .RO

chammer · Posted: Sun May 25, 2003 3:46 pm Post subject:

having this problem as well, up until last week -Up then eventually -U would emerge everything leaving my "bleeding edge" stuff alone. for the past week, however, i've been getting this output from emerge -Up world...

http://www.nasland.nu/world.txt

...the kde stuff seems to depend on gnome1 stuff now? at any rate, i cant upgrade kde until i know for sure its not going to install gnome1. i do have gnome2 obviously, and i realize there's slots with portage...however, thats not the point. i dont want gnome1, period.

this makes no sense, as i've been running the lastest versions of things ever since i've installed gentoo, and have had no problems like this. it started like i said about a week ago. the kicker was when i rsynced then, ibm's java ebuild was broken...or something to that effect. it was stated that they knew about it, and would have it fixed within 30mins. i got busy doing other things, but sure enough couple hours later on another rsync it was fixed. however, ever since then i've been going through this crap with -U.

feel free to ignore some of the other stuff (mirrorselect, shadow, etc) as they've been upgraded a lil while after i ran that.

anyways, i'd appreciate any clues on this...
_________________
http://www.nasland.nu
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' |dc

gigel · Guru Joined: 14 Jan 2003 Posts: 334 Location: .RO

Lion · Apprentice Joined: 23 Jun 2002 Posts: 207

I had exactly the same (portage first leaving alone unstable packages when selecting -U, then suddenly wanting to downgrade).

What I noticed (and this is probably the cause for the behaviour):
For all ebuilds that portage now wants to downgrade, the ebuild for the exact version that I have installed has been removed.
Example: when I installed package xyzzy, xyzzy-2.0 was stable, xyzzy-3.0 was in ~x86. I needed features of xyzzyy-3.0 so I emerged it with ACCEPT_KEYWORDS="~x86" emerge xyzzy.
So far so good, xyzzy-3.0 is now on my system, and emerge -U leaves it alone.

But, development on xyzzy continues, and a new ebuild is created, xyzzy-3.0-r1, and later on, xyzzy-3.0-r2. Still no problems.

Then, it is decided that xyzzy-3.0-r1 and r2 are more stable in every respect than xyzzy-3.0, and the ebuild for xyzzy-3.0 is removed from the portage tree. Now, we get a problem when performing an emerge -U. The exact version of xyzzy that we have installed is no longer part of the tree, so portage only sees a choice between upgrading to a newer version in ~x86, or downgrading to a version that is in x86. As I don't have ~x86 in my standard ACCEPT_KEYWORDS, it chooses the 'safe' option, downgrading, even though, by specifying -U instead of -u, we have told it that we are happy with the packages that are already installed.

I think this is a bug in portage, but it may be intended behaviour.

Can anyone confirm / disprove my analysis?

chammer · Posted: Mon May 26, 2003 11:43 am Post subject:

lion, i just checked and that explanation seems to make sense. however, upon checking i find this...

$ emerge -Up world
*clip*
[ebuild U ] gnome-base/gconf-1.0.8-r3 [2.2.0]
(as an example)

now, if i cd to /usr/portage/gnome-base/gconf and ls -al i get this...

-rw-r--r-- 1 root root 1797 Apr 8 22:03 gconf-2.2.0.ebuild

so the ebuild is there. i dunno, i just dont understand it. i may just set my default keyword to ~x86 and be done with it. reason i installed gentoo in first place was to be bleeding edge...as stability isnt really a concern for me (its stable enough as a workstation). i'm coming off of freebsd which didnt have the newest things always and i hated waiting for a port.
_________________
http://www.nasland.nu
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' |dc

gordonNgentoo · n00b Joined: 10 Feb 2003 Posts: 38

1)Can someone tell me what are slots in portage?

2) I do have some bleeding edge on my system. someone tells me to do emerge -upD world , and I argue that I shouldn't because it would downgrade some libraries and compilers as I've noted by the notation [ebuild UD]
Am I correct to say UD would update by a downgrade??

so would the correct command be emerge -UpD world?
does emerge -UpD world also emerge stuff for the system? Another words, is world the most complete update I can get or do I have to do something more?

Thanks.
-Gordon

gordonNgentoo · n00b Joined: 10 Feb 2003 Posts: 38

Chammer, just because you have an ebuild in the directory doesn't mean portage will use it; even if the ebuild is in the directory, it could still be masked! The newer ebuild that's on your directory (as you've pointed out) is there for you to use in case you want to force it to use that ebuild. How you force it, I forgot. It has something to do with typing the "USE=~X86 emerge -p /directory to that newest ebuild you want" this USE=~x86 (u better check the syntax by searching the forums) will overide the USE in the make.conf temporarily.

-Gordon

gigel · Guru Joined: 14 Jan 2003 Posts: 334 Location: .RO

Cyclone · n00b Joined: 27 Jan 2003 Posts: 23

Actually, the D indicates a downgrade, U indicates that the package's install will be updated (As opposed to N for new package) So [ UD] indicates that the already installed package will have an older version installed over it
_________________
Cyclone
Successfully running Gentoo 1.4 on a Toshiba 2415-s205 from stage1