Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 36220 - coreutils-5.0.91-r2 don't "emerge -u" from stage3
Summary: coreutils-5.0.91-r2 don't "emerge -u" from stage3
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High major (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-21 02:30 UTC by Thiemo Kellner
Modified: 2004-02-21 16:25 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 Thiemo Kellner 2003-12-21 02:30:05 UTC
From stage 3 I tried to install vcron and metalog by "emerge -u vcron metalog". Within this process, coreutils would also get updated but fails due to a dependency problem. Portage does not emerge autoconf-1.7.6 or later beforehand to resolve DEPEND="...
                           >=sys-devel/automake-1.7.6
                           ..."

workaround: manually emerge -u "autoconf" such that it is at least 1.7.6

fee:~ # chroot /root/gentoo/ /bin/bash
bash-2.05b# emerge --info
Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031212-r0, 2.4.21-99-default)
=================================================================
System uname: 2.4.21-99-default i686 VIA Samuel 2
Gentoo Base System version 1.4.3.12
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=i586 -O3 -pipe -fomit-frame-pointer"
CHOST="i586-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=i586 -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/share/ch/thiam/ebuilds"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow S3TC X Xaw3d apm arts avi chasen cjk crypt cscope cups curl dga dnd doc dom dv dvd encode fbcon flash foomaticdb freewnn gd gdbm gif ginac gmttria gpm gtk gtk2 gtkhtml ilcms imagemagick imap imlib imlib2 ipv6 irmc j-noaim j-nojud j-nomsn j-nomuconf j-noyahoo java javascript jbig jikes joystick jpeg junit kakasi kde libg++ libwww mad maildir matroska md5sum mikmod milter mmx motif moznocompose moznoirc moznomail moznoxft mpeg music ncurses nls nocardbus nocstrike nodod nophysfs notfc oav offensive oggvorbis opengl oss pam parse-clocks pdflib perl pic plotutils png ppds python qt qtmt quicktime readline sasl sdl slang slp socks5 speex spell src sse ssl svga tcpd tetex threads tiff transcode truetype type1 uml usb vim-with-x x86 xface xine xinerama xml xml2 xmms xvid zlib"
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2003-12-27 13:28:41 UTC
autoconf and automake are two different packages.  I am unclear as to which one of them you're referring to.
Comment 2 Thiemo Kellner 2003-12-28 14:02:27 UTC
workaround should read: manually emerge -u "automake" such that it is at least 1.7.6

sorry
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2003-12-28 15:15:12 UTC
Can you expand on 'coreutils would also get updated but fails due to a dependency
problem' ?  This could mean that portage borks saying it could not resolve deps,
or it could mean the coreutils build break saying it needs a newer automake?
Thanks.
Comment 4 Thiemo Kellner 2003-12-28 22:32:22 UTC
I try to say that made a fresh install (clean disk and everything) and used a stage3 tarball. As described in the install howto, I emerged a logger and a cron, metalog and vcron in my case. But I did not plainly emerge it as described in the howto but emerged -u. The result of this was that portage tried to emerge (among other packages) a new version of coreutils but in the configure (?) process where the package itself checks whether various conditions are met, the configure process stopped having encountered that automake was only in version 1.7.5 available but it needed 1.7.6. As far as I remeber, I checked the respective coreutils package and it stated automake 1.7.6 as dependecy, but I am not sure.

I was thinking that portage was the trouble maker. My guess was that portage didn't resolve the dependency correctly but continued until the configure job stopped it.

Sorry for having included too little info.
Comment 5 Martin Schlemmer (RETIRED) gentoo-dev 2003-12-29 11:04:57 UTC
Seemant, as coreutils is your baby, can you get to changing DEPEND ?
Comment 6 Seemant Kulleen (RETIRED) gentoo-dev 2004-01-08 23:56:30 UTC
Az, coreutils-5.0.91* all have automake-1.7.6 as a dependency so I dunno what the story is here :/
Comment 7 Daniel Luera 2004-02-19 20:09:39 UTC
Could this be related to bug # 41944?

Basically, it looks like 5.0.91.tar.bz2 isn't available for download.

This will REALLY affect a new install.
Comment 8 Seemant Kulleen (RETIRED) gentoo-dev 2004-02-19 20:21:26 UTC
no, it's available for download, that's not the issue.
Comment 9 Seemant Kulleen (RETIRED) gentoo-dev 2004-02-21 16:25:20 UTC
well, the DEPEND is explicit in coreutils-5.0.91 and up, so I dunno why this happened for you.  re-open if it remains an issue