Bug 67228 – repoman fails to update gimp-2.0.4 in cvs

• Product: Portage Development
• Status: RESOLVED WONTFIX

[Description Alexander Gabert (RETIRED) 2004-10-12 07:08:51 UTC]

[0] pappy@PAPILLON gimp $ repoman scan

We're not in PORTDIR... setting to: /home/pappy/dev/gentoo/cvs/gentoo-x86

RepoMan scours the neighborhood...

  DEPEND.bad           6
   media-gfx/gimp/gimp-2.0.0.ebuild: x86 ['virtual/x11']
   media-gfx/gimp/gimp-2.0.0.ebuild: hppa ['virtual/x11']
   media-gfx/gimp/gimp-2.0.2.ebuild: ~x86 ['virtual/x11']
   media-gfx/gimp/gimp-2.0.2.ebuild: ~hppa ['virtual/x11']
   media-gfx/gimp/gimp-2.0.4.ebuild: x86 ['virtual/x11']
   media-gfx/gimp/gimp-2.0.4.ebuild: hppa ['virtual/x11']
  RDEPEND.bad          5
   media-gfx/gimp/gimp-2.0.0.ebuild: x86 ['virtual/x11']
   media-gfx/gimp/gimp-2.0.0.ebuild: hppa ['virtual/x11']
   media-gfx/gimp/gimp-2.0.2.ebuild: ~hppa ['virtual/x11']
   media-gfx/gimp/gimp-2.0.4.ebuild: x86 ['virtual/x11']
   media-gfx/gimp/gimp-2.0.4.ebuild: hppa ['virtual/x11']
  KEYWORDS.invalid     6
   media-gfx/gimp/gimp-1.2.5.ebuild: amd64
   media-gfx/gimp/gimp-2.0.0.ebuild: amd64
   media-gfx/gimp/gimp-2.0.2.ebuild: ~amd64
   media-gfx/gimp/gimp-2.0.2.ebuild: ppc64
   media-gfx/gimp/gimp-2.0.4.ebuild: ~amd64
   media-gfx/gimp/gimp-2.0.4.ebuild: ~ppc64


[0] pappy@PAPILLON gimp $ emerge info
Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.4.27)
=================================================================
System uname: 2.4.27 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 1.80GHz
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-g -ggdb -O2"
CHOST="i386-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-g -ggdb -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache cvs debug nostrip sandbox static strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/home/pappy/dev/gentoo/cvs/gentoo-x86"
SYNC="rsync://spout.ussg.indiana.edu/gentoo-portage"
USE="X aalib apm arts avi berkdb bitmap-fonts cdr crypt cups debug encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xprint xv zlib"

[0] pappy@PAPILLON gimp $ ls -ali /etc | grep profile
 130819 lrwxrwxrwx   1 root root    42 Jul  3 22:57 make.profile -> ../usr/portage/profiles/default-x86-2004.0
 132815 -rw-r--r--   1 root root  1231 Sep 22 20:47 profile
 130818 -rw-r--r--   1 root root  1396 Oct 12 11:50 profile.env
[0] pappy@PAPILLON gimp $ pwd
/home/pappy/dev/gentoo/cvs/gentoo-x86/media-gfx/gimp

[Comment 1 SpanKY 2004-10-12 15:13:28 UTC]

chances are it's because you're using portage-2.0.50

the profiles.desc file has hppa and x86 pointing to a profile in the cascading directory of default-linux ... that means the virtual/x11 is inherited via its parents in the base/virtuals file

solution -> upgrade to 2.0.51

[Comment 2 Alexander Gabert (RETIRED) 2004-10-19 08:54:03 UTC]

I feel so sorry and really stupid for opening this miserable excuse for a serious portage/repoman/QA utility bug.

I also feel so sorry for making a fuss about it on #gentoo-dev channel the last weeks.  I am really really ashamed of my foolish disgraceful behaviour.

Me love portage.  Me love portage dev.  Me will never ever again raise word against repoman.  I promise, seriously!

-Alex