public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eric Sammer <eric@ineoconcepts.com>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] depgraph creation failure
Date: Sat, 26 Jul 2003 05:21:34 -0400	[thread overview]
Message-ID: <3F22481E.1000002@ineoconcepts.com> (raw)

I just sync'd (update came from rsync 2 in US) this morning and now 
there's a depgraph creation error. (Warning: it's part of the 
ExtUtils-MakeMaker saga but I *have* read forums and bugs - I swear ;))

Here's the error:

--- begin snippit ---

samus root # emerge -up world

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

Calculating world dependencies ...done!
[ebuild     UD] sys-apps/portage-2.0.48-r5 [2.0.48-r6]
*** Portage will stop merging at this point and reload itself,
     recalculate dependencies, and complete the merge.

!!! aux_get(): ebuild for '<dev-perl/ExtUtils-MakeMaker-6.05-r6' does 
not exist at:
!!! 
/usr/portage/<dev-perl/ExtUtils-MakeMaker/ExtUtils-MakeMaker-6.05-r6.ebuild
Traceback (most recent call last):
   File "/usr/bin/emerge", line 1978, in ?
     mydepgraph.display(mydepgraph.altlist())
   File "/usr/bin/emerge", line 943, in display
     if ("fetch" in 
string.split(portage.portdb.aux_get(x[2],["RESTRICT"])[0])):
   File "/usr/lib/python2.2/site-packages/portage.py", line 3435, in aux_get
     raise KeyError
KeyError

--- end snippit ---

Now, I know that there was the issue of a buggy make maker so the ebuild 
was added, yadda yadda yadda, but now it seems as if something is still 
listing it as a dep. This is (obviously) a show stopper. I'll work some 
magical grep mojo and try and track down what, if anything, is still 
using this ebuild. Below is the relevant 'emerge info' bits...

samus root # emerge info
Portage 2.0.48-r6 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.21 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz
GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ 
ftp://ftp.ussg.iu.edu/pub/linux/gentoo 
ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://gentoo.noved.org/"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config 
/usr/kde/2/share/config /usr/kde/3/share/config /var/bind /opt/tomcat/conf"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/portage"
USE="x86 3dnow apm crypt cups encode gif jpeg libg++ libwww mmx ncurses 
nls pdflib png slang spell svga xml2 zlib gdbm berkdb readline java 
postgres tcpd pam ssl perl python ldap acpi curl jikes junit objc sasl 
sse -oss -arts -avi -foomaticdb -gtk -imlib -kde -gnome -mad -mikmod 
-motif -mpeg -oggvorbis -opengl -qt -quicktime -sdl -truetype -X -xmms 
-xv -gpm"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-mcpu=pentium3 -O3 -pipe"
CXXFLAGS="-mcpu=pentium3 -O3 -pipe"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

-- 
Eric Sammer
eric@ineoconcepts.com
http://www.ineoconcepts.com


--
gentoo-dev@gentoo.org mailing list


                 reply	other threads:[~2003-07-26  9:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F22481E.1000002@ineoconcepts.com \
    --to=eric@ineoconcepts.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox