Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 127999 - emerge --sync damaged/destroyed portage tree
Summary: emerge --sync damaged/destroyed portage tree
Status: VERIFIED DUPLICATE of bug 114798
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: Low critical
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-29 08:12 UTC by Robert G. Hays
Modified: 2006-03-29 09:56 UTC (History)
0 users

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 Robert G. Hays 2006-03-29 08:12:43 UTC
('as-it happened' report below emerge--info)
---------------------------------------------
Gentoo Base System version 1.4.16
Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.11-rc4-onion1 i686)
=================================================================
System uname: 2.6.11-rc4-onion1 i686 AMD Athlon(tm) XP 2100+
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 12:15:55)]
dev-lang/python:     2.3.4
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.8.5-r3, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS=""
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
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/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://gentoo.netnitco.net ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://gentoo.osuosl.org/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://gentoo.mirrors.pair.com/ http://mirror.tucdemonic.org/gentoo/ http://gentoo.seren.com/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.ccccom.com http://gentoo.mirrors.tds.net/gentoo http://mirror.clarkson.edu/pub/distributions/gentoo/ http://ftp.ankara.edu.tr/gentoo/ http://lug.mtu.edu/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://vlaai.snt.utwente.nl/pub/os/linux/gentoo/ http://vlaai.snt.utwente.nl/pub/os/linux/gentoo/ http://gentoo.eliteitminds.com ftp://cudlug.cudenver.edu/pub/mirrors/distributions/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE=""
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

-------------------------------------------------------------------

Got this at about 11:25 PM EST/USA 3/28/06 (GMT-6) from an "emerge --sync"...

  "
    >>> Updating Portage cache: 89%!!! Cannot resolve a virtual package name
    to an ebuild.
    !!! This is a bug, please report it. (virtual/libintl-0).
  "

Also, updating the Portage cache gets --real-- slow around 50% through
somewhere short of 66% -- probably around 55% ?

A re-do of the "emerge --sync" gave the same message at the same place.

THEN doing:
    emerge --ask --deep --verbose libstdc++-v3
(which I already done before '--sync'; re-did to test)
yields:
  "
    <fgcolor=green>
    These are the files that I would emerge, in order:

    <fgcolor=red>
    !!! ARCH is not set... are you missing the /etc/make.profile symlink?
    !!! Is the symlink correct? Is your portage tree complete?
    <fgcolor=default>
  "

The symlink is there, pointing to:
    /usr/portage/profiles/default-linux/x86/2004.3
which **USED** to be there, but is -not- now !!!
All **was** working fine until this.
Using eth0 --> dsl_modem (1.5Mb/256Kb).

Shuttle AN35N-ultra-400-plusMCP mobo, AMD2100XP, 1GB, 120+80+120GB, 52^3CDRW,
ATI A-I-W 9600 w/ 1280x1024 + 1600x1280, assorted USB, etc, etc, blah, blah,
blah...  --  not earth-endangering, but no snoozer neither, and a Westell
dsl modem from bellsouth (my provider) J.I.C. you had some need to know to
help debuging... . . .  .  .   .   .    .    .     .

I was actually looking for libstdc++.so.6, for kbasic, which I need -Now-.

(I have a backup, not too much out of date to matter --
 -- has my portage tree been taken to the "Recycle Bin"? (guess whom's!) )

rghays,
    rghays9693@netscape.net
    hays9857@bellsouth.net
    Rome, Georgia, USA.
Comment 1 Allen Brooker (AllenJB) 2006-03-29 08:21:14 UTC
(In reply to comment #0)
> Got this at about 11:25 PM EST/USA 3/28/06 (GMT-6) from an "emerge --sync"...
> 
>   "
>     >>> Updating Portage cache: 89%!!! Cannot resolve a virtual package name
>     to an ebuild.
>     !!! This is a bug, please report it. (virtual/libintl-0).
>   "
> 
> Also, updating the Portage cache gets --real-- slow around 50% through
> somewhere short of 66% -- probably around 55% ?
> 
> A re-do of the "emerge --sync" gave the same message at the same place.

This a known bug - please see:
http://bugs.gentoo.org/show_bug.cgi?id=114798

The slow updating of portage at around 50% is normal. There's an easy solution tho: Stop watching it =P

> 
> THEN doing:
>     emerge --ask --deep --verbose libstdc++-v3
> (which I already done before '--sync'; re-did to test)
> yields:
>   "
>     <fgcolor=green>
>     These are the files that I would emerge, in order:
> 
>     <fgcolor=red>
>     !!! ARCH is not set... are you missing the /etc/make.profile symlink?
>     !!! Is the symlink correct? Is your portage tree complete?
>     <fgcolor=default>
>   "
> 
> The symlink is there, pointing to:
>     /usr/portage/profiles/default-linux/x86/2004.3
> which **USED** to be there, but is -not- now !!!
> All **was** working fine until this.
> Using eth0 --> dsl_modem (1.5Mb/256Kb).
>

Oooh - nice move. Rather than trying to sort out the first error you try to continue anyway... then you wonder why you get further errors!
 
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2006-03-29 09:14:38 UTC

*** This bug has been marked as a duplicate of 114798 ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-03-29 09:56:41 UTC
CLOSED