Bug 195370 – emerge shows a bogus 'downgrade' on transition from old-style virtual to a new-style one

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Andy Dalton 2007-10-10 12:28:13 UTC]

While updating my system, I saw this strange output during an 'emerge -uDNav world':

[ebuild     UD] virtual/editor-0 [21.4.20-r4] USE="(-X%*) (-Xaw3d%) (-athena%) (                                                                            -berkdb%*) (-canna%) (-dnd%) (-eolconv%) (-esd%) (-freewnn%) (-gdbm%*) (-gif%*)                                                                             (-gpm%*) (-jpeg%*) (-ldap%) (-motif%) (-mule%) (-nas%*) (-neXt%) (-png%*) (-pop%                                                                            ) (-postgres%) (-tiff%*) (-xface%) (-xim%)" 0 kB

Since this was a virtual (and a new one if I'm not mistaken), I found it odd to be downgrading to 0 from 21.4.20-r4.  Then I checked to see if virtual/editor-21.4.20-r4 was actually installed (by attempting to remove it):

$ emerge -Cp virtual/editor

>>> These are the packages that would be unmerged:

 app-editors/vim
    selected: 7.1.042
   protected: none
     omitted: none


$ emerge -Cp =virtual/editor-21.4.20-r4

>>> These are the packages that would be unmerged:

--- Couldn't find '=virtual/editor-21.4.20-r4' to unmerge.

It looks like portage has somehow gotten confused.  I'm concerned that if I do allow it to continue, it will remove *some* package at version 21.4.20-r4 that I want to keep (what that might be, I'm not sure).

If I can provide any further information, please let me know.

Thanks,

Andy

Reproducible: Always

Steps to Reproduce:
1.emerge -p virtual/editor

Actual Results:  
[ebuild     UD] virtual/editor-0 [21.4.20-r4]


Expected Results:  
[ebuild      U] virtual/editor-0


$ emerge --info
Portage 2.1.3.9 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r5 i686)
=================================================================
System uname: 2.6.22-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Timestamp of tree: Wed, 10 Oct 2007 09:00:01 +0000
app-shells/bash:     3.2_p17
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r5
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.22-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -ftracer -pipe"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -ftracer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch userpriv"

[Comment 1 Petteri Räty (RETIRED) 2007-10-10 12:53:05 UTC]

Yep the same old problem I reported in bug #154223. I will leave it up to Portage devs on if they want to mark this as duplicate or not.

[Comment 2 Petteri Räty (RETIRED) 2007-10-10 12:56:00 UTC]

Basically the version comes from the old style provider (virtual/editor was recently migrated to new style virtuals) and you should just downgrade the virtual.

[Comment 3 Zac Medico 2007-10-10 15:43:01 UTC]

(In reply to comment #0)
> Steps to Reproduce:
> 1.emerge -p virtual/editor
> 
> Actual Results:  
> [ebuild     UD] virtual/editor-0 [21.4.20-r4]
> 
> 
> Expected Results:  
> [ebuild      U] virtual/editor-0

It's fixed in svn r8039 so it won't display as a bogus downgrade anymore. This bug doesn't hurt anything. It just makes the display confusing. The code that uninstalls old versions is completely separate and works just fine.

[Comment 4 Zac Medico 2007-10-13 20:17:19 UTC]

This has been released in 2.1.3.13.