Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 29246 - portage dispay wrong
Summary: portage dispay wrong
Status: RESOLVED DUPLICATE of bug 18608
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-21 00:17 UTC by cantona
Modified: 2011-10-30 22:20 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cantona 2003-09-21 00:17:23 UTC
this error happens on metacity but not other..

gentoo root # emerge -p metacity
 
These are the packages that I would merge, in order:
 
Calculating dependencies ...done!
[ebuild     U ] x11-wm/metacity-2.4.55 [2.5.3-r1]
 
this should be "UD" not "U" since 2.5.3-r1 is newer than 2.4.55 right?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 SpanKY gentoo-dev 2003-09-21 00:56:41 UTC
no idea where you got 2.5.3-r1 since it isnt in cvs and/or the current rsync of the portage tree buuuuuuuuuuuuuuuut ...

imo this isnt a bug:
2.4.55 is the latest STABLE version of metacity
at some point you upgrade to 2.5.3-r1 so now portage is trying to 'downgrade' to the latest stable ...
Comment 2 cantona 2003-09-21 00:59:22 UTC
it is from breakmygentoo.net.....
anyway if it downgrade, so it would be "UD" not "U".....
Comment 3 David Peter 2003-09-21 01:24:50 UTC
Hi,

I can not prove this (because I don't have the ebuild from breakmygentoo, and I didn't find it there) but I think maybe:

* metacity 2.5.3-r1 is in the 2.5 slot and
* metacity 2.4.55 is in the 2.4 slot

so the output from portage is correct. it will only *upgrade* the 2.4 version to the new 2.4.55. Your 2.5.3-r1 version will not be touched.
Comment 4 SpanKY gentoo-dev 2003-09-21 01:29:08 UTC
yes, i know that it's a 'downgrade' because 2.5 is newer than 2.4

metacity is not SLOT-ed so that wouldnt apply here

the reason i dont think it's a bug persay is that portage is upgrading you to the latest STABLE version ... for example:
a package has the current portage stable of 1.0
you make a new stable of 1.1
you sync and lose the 1.1, thus the latest stable is 1.0
portage is going to 'upgrade' you to 1.0 ... i like this because if a newer STABLE is broken and a developer wants to push the older out but can't really -r bump because the next -r is UNSTABLE, he could just remove the current -r and all users of STABLE would upgrade to it
Comment 5 Marius Mauch (RETIRED) gentoo-dev 2003-09-21 22:53:59 UTC
Spanky, I think you're on the wrong track, the recent sylpheed and sylpheed-claws downgrades were displayed as downgrades. Did anyone check the BMG ebuilds for SLOT maybe it's broken on their side. We really need a SLOT change indicator for emerge -p, even if it's only a quick workaround until the real solution is integrated.
Comment 6 TGL 2003-09-22 06:07:11 UTC
> We really need a SLOT change indicator for emerge -p, even if it's only a quick 
> workaround until the real solution is integrated.

Oh yes, please... The current "emerge -p" output in case of slotted pkgs raises
several topics per day on forums, so there is obviously something to improve  
here, even if it is only a cosmetic issue. I've attached a patch to bug #18608 
which fixes it.
Comment 7 SpanKY gentoo-dev 2003-09-22 06:47:07 UTC
then since it's a SLOT issue this bug is a dup

*** This bug has been marked as a duplicate of 18608 ***