Bug 108135 – `emerge -upD world` fails with dependancy problems

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Iain Buchanan 2005-10-04 17:32:37 UTC]

`emerge --sync`-ed a few days ago, and then did an `emerge -uD world`.  One of
the packages to update was portage, to version sys-apps/portage-2.0.53_rc3.  

After updating portage, emerge restarted itself as usual, but then in the
process I got an error similar to:
$ emerge -upD world

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

Calculating world dependencies -
emerge: there are no ebuilds to satisfy "app-doc/apache-manual".

!!! Problem resolving dependencies for app-doc/apache-manual
!!! Depgraph creation failed.


This happens every time I do an `emerge -upD world` or `emerge -u world`. 
emerging individual packages seems to be ok.

This doesn't seem related to the package app-doc/apache-manual, because the
error was originally something else (bmp-lame or something), which I unmerged. 
Then it complained about a second package, so I unmerged that one, then it
complained about apache-manual, so I figured it wasn't the packages themselves
that were the problem...

I downgraded to sys-apps/portage-2.0.51.22-r2 and everything seems ok.

Reproducible: Always
Steps to Reproduce:
1. emerge sys-apps/portage-2.0.53_rc3.
2. emerge -u world, or emerge -uD world
Actual Results:  
emerge fails with dependancy problems


$ emerge info
Portage 2.0.53_rc3 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.13-gentoo-r2 i686)
=================================================================
System uname: 2.6.13-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.12.0_pre8
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.13
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c
/etc/env.d"
CXXFLAGS="-march=pentium4 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig collision-protect distlocks fixpackages sandbox sfperms strict"
GENTOO_MIRRORS="ftp://arion/pub/gentoo-portage/
ftp://mirror.isp.net.au/pub/gentoo/ ftp://gg3.net/pub/linux/gentoo/
ftp://gentoo.ccccom.com ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
LANG="en_AU"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="x86 X acpi alsa apache2 arts avi bash-completion berkdb bitmap-fonts
bluetooth cdr crypt cups curl directfb dvd dvdr eds emboss encode esd evo fam
flac foomaticdb fortran ftp gdbm gif gnome gpm gstreamer gtk gtk2 guile
imagemagick imlib ipv6 irmc java jpeg libg++ libwww mad mikmod mmx motif mozilla
mozsvg mp3 mpeg mysql ncurses nfs nls ogg oggvorbis opengl pam pdflib perl php
png postgres python quicktime readline samba sdl spell sse ssl svg svga tcltk
tcpd tetex tiff truetype truetype-fonts type1-fonts vorbis win32codecs xml xml2
xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 Iain Buchanan 2005-10-04 17:35:28 UTC]

I should add that I synced again just a few minutes ago, so there were a few
days between the two syncs, and the problem still occurs.

[Comment 2 Jason Stubbs (RETIRED) 2005-10-04 18:26:19 UTC]

Yes and no. It is a package that is no longer in the ebuild tree and cannot ever
be updated again. Emerge is meant to be ignoring such packages but currently isn't.

[Comment 3 Jakub Moc (RETIRED) 2005-10-05 00:11:55 UTC]

*** Bug 108140 has been marked as a duplicate of this bug. ***

[Comment 4 Jakub Moc (RETIRED) 2005-10-05 00:15:06 UTC]

This is really annoying. If you don't plan to restore the old behaviour, then at
least add some hint to unmerge the package that has been removed from the tree. 

[Comment 5 Jason Stubbs (RETIRED) 2005-10-05 03:09:51 UTC]

Is this bug marked as INVALID? Did I not mark it as blocking 2.0.53 going 
stable? Did you not notice Brian and I talking about it on IRC last night? 
 
Have patience and keep your comments to yourself. 

[Comment 6 Jason Stubbs (RETIRED) 2005-10-05 07:51:56 UTC]

Created attachment 69920 [details]
New utility for portage

This will likely become (at least the basis for) a new tool for portage.
Presently it does two things - checks for world file problems and fixes world
file problems.

emaint --check world
emaint --fix world

Running this should get 2.0.53_rc3 working smooth for you again.

[Comment 7 Jason Stubbs (RETIRED) 2005-10-05 07:54:23 UTC]

Created attachment 69921 [details]
Take #2

The previous version is broken after changes from discussing cleanliness. :/

[Comment 8 Jason Stubbs (RETIRED) 2005-10-05 07:58:07 UTC]

Created attachment 69922 [details]
Take #3

No substitutions on the output so everything was showing as '%s'.
No fear though! All functionality has now been tested.

[Comment 9 Jason Stubbs (RETIRED) 2005-10-05 13:17:00 UTC]

Fixed in portage-2.0.53_rc4 

[Comment 10 Iain Buchanan 2005-10-05 16:44:47 UTC]

thanks, portage-2.0.53_rc4 works.