Mailing List Archive

Portage problem
Hi all,

I had a system crash this weekend, about 12 hours after getting the 2.6.8
kernel working on my alpha. (unrelated problem).

I've restored the system to a backup from about 10 days ago but it now seems
my portage database is problematic and the typical emerge commands are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



--
gentoo-alpha@gentoo.org mailing list
RE: Portage problem [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

E.g.,

alpha-omega export # emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 4) sys-apps/portage-2.0.51_rc9 to /
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work Source unpacked.
alpha-omega export #

The process is exiting prematurely but I'm not sure for what reason.

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net]
Sent: Monday, October 11, 2004 10:41 AM
To: gentoo-alpha@lists.gentoo.org
Subject: [gentoo-alpha] Portage problem

Hi all,

I had a system crash this weekend, about 12 hours after getting the
2.6.8
kernel working on my alpha. (unrelated problem).

I've restored the system to a backup from about 10 days ago but it
now seems
my portage database is problematic and the typical emerge commands
are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it
an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the
gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



- --
gentoo-alpha@gentoo.org mailing list


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQWrXX/Z0qmLutBiIEQLouwCg5fmq/9ewY1+eqLCg6ruH75/7PqYAoNmm
d4jJ97EH4Zz9A9gSj9umc+Yl
=AuJV
-----END PGP SIGNATURE-----


--
gentoo-alpha@gentoo.org mailing list
RE: Portage problem [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Additional info from emerge -duv portage

Script started on Mon Oct 11 12:02:17 2004
alpha-omega portage #
emerge -duv portage
Calculating dependencies
Parent: None
Depstring: sys-apps/portage
Candidates: ['sys-apps/portage']
ebuild: sys-apps/portage-2.0.51_rc9
binpkg: None
Parent: ebuild / sys-apps/portage-2.0.51_rc9 merge
Depstring: !bootstrap? ( sys-devel/patch ) !build? (
>=sys-apps/sed-4.0.5 dev-python/python-fchksum
>=dev-lang/python-2.2.1 sys-apps/debianutils >=app-shells/bash-2.05a
) selinux? ( >=dev-python/python-selinux-2.15 )
Candidates: ['dev-python/python-fchksum', 'sys-devel/patch',
'>=dev-lang/python-2.2.1', '>=sys-apps/sed-4.0.5',
'>=app-shells/bash-2.05a', 'sys-apps/debianutils']
ebuild: dev-python/python-fchksum-1.7.1
binpkg: None
ebuild: sys-devel/patch-2.5.9
binpkg: None
ebuild: dev-lang/python-2.3.4
binpkg: None
ebuild: sys-apps/sed-4.1.2
binpkg: None
ebuild: app-shells/bash-3.0-r6
binpkg: None
ebuild: sys-apps/debianutils-1.16.7-r4
binpkg: None
Exiting... ebuild / sys-apps/portage-2.0.51_rc9 merge
Exiting... None
...done!
>>> emerge (1 of 1) sys-apps/portage-2.0.51_rc9 to /
+ dyn_clean
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/image
+ hasq keeptemp autoaddcvs buildpkg ccache distcc distlocks notitles
sandbox userpriv usersandbox
+ local x
+ local me=keeptemp
+ shift
+ for x in '"$@"'
+ '[' autoaddcvs == keeptemp ']'
+ for x in '"$@"'
+ '[' buildpkg == keeptemp ']'
+ for x in '"$@"'
+ '[' ccache == keeptemp ']'
+ for x in '"$@"'
+ '[' distcc == keeptemp ']'
+ for x in '"$@"'
+ '[' distlocks == keeptemp ']'
+ for x in '"$@"'
+ '[' notitles == keeptemp ']'
+ for x in '"$@"'
+ '[' sandbox == keeptemp ']'
+ for x in '"$@"'
+ '[' userpriv == keeptemp ']'
+ for x in '"$@"'
+ '[' usersandbox == keeptemp ']'
+ return 1
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/temp/eclass-debug.log
+ hasq keepwork autoaddcvs buildpkg ccache distcc distlocks notitles
sandbox userpriv usersandbox
+ local x
+ local me=keepwork
+ shift
+ for x in '"$@"'
+ '[' autoaddcvs == keepwork ']'
+ for x in '"$@"'
+ '[' buildpkg == keepwork ']'
+ for x in '"$@"'
+ '[' ccache == keepwork ']'
+ for x in '"$@"'
+ '[' distcc == keepwork ']'
+ for x in '"$@"'
+ '[' distlocks == keepwork ']'
+ for x in '"$@"'
+ '[' notitles == keepwork ']'
+ for x in '"$@"'
+ '[' sandbox == keepwork ']'
+ for x in '"$@"'
+ '[' userpriv == keepwork ']'
+ for x in '"$@"'
+ '[' usersandbox == keepwork ']'
+ return 1
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.compiled
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.unpacked
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.installed
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/build-info
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/work
+ '[' -f /var/tmp/portage/portage-2.0.51_rc9/.unpacked ']'
+ true
+ set +x
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
+ dyn_setup
+ '[' GNU == Linux ']'
+ pkg_setup
+ return
+ set +x
+ dyn_unpack
+ trap abort_unpack SIGINT SIGQUIT
+ local newstuff=no
+ '[' -e /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ '[' -e /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ install -m0700 -d /var/tmp/portage/portage-2.0.51_rc9/work
+ '[' -d /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ cd /var/tmp/portage/portage-2.0.51_rc9/work
+ echo '>>> Unpacking source...'
>>> Unpacking source...
+ src_unpack
+ unpack portage-2.0.51_rc9.tar.bz2
+ local x
+ local y
+ local myfail
+ local tarvars
+ '[' GNU == BSD ']'
+ tarvars=--no-same-owner
+ for x in '"$@"'
+ myfail='failure unpacking portage-2.0.51_rc9.tar.bz2'
++ pwd
+ echo '>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
/var/tmp/portage/portage-2.0.51_rc9/work'
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work
+ y=portage-2.0.51_rc9.tar
+ y=tar
+ case "${x##*.}" in
+ '[' tar == tar ']'
+ bzip2 -dc /usr/portage/distfiles/portage-2.0.51_rc9.tar.bz2
+ tar xf - --no-same-owner
+ cd /var/tmp/portage/portage-2.0.51_rc9/work/portage-2.0.51_rc9
+ touch /var/tmp/portage/portage-2.0.51_rc9/.unpacked
+ echo '>>> Source unpacked.'
>>> Source unpacked.
+ cd /var/tmp/portage/portage-2.0.51_rc9
+ trap SIGINT SIGQUIT
+ set +x
alpha-omega portage:

Script done on Mon Oct 11 12:02:46 2004

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net]
Sent: Monday, October 11, 2004 11:57 AM
To: 'Brian Parkhurst'; gentoo-alpha@lists.gentoo.org
Subject: RE: [gentoo-alpha] Portage problem


*** PGP SIGNATURE VERIFICATION ***
*** Status: Good Signature
*** Signer: Brian C. Parkhurst <brianp@u.washington.edu>
(0xEEB41888)
*** Signed: 10/11/2004 11:56:31 AM
*** Verified: 10/11/2004 12:03:43 PM
*** BEGIN PGP VERIFIED MESSAGE ***

E.g.,

alpha-omega export # emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 4) sys-apps/portage-2.0.51_rc9 to /
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work Source unpacked.
alpha-omega export #

The process is exiting prematurely but I'm not sure for what reason.

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net]
Sent: Monday, October 11, 2004 10:41 AM
To: gentoo-alpha@lists.gentoo.org
Subject: [gentoo-alpha] Portage problem

Hi all,

I had a system crash this weekend, about 12 hours after getting the
2.6.8
kernel working on my alpha. (unrelated problem).

I've restored the system to a backup from about 10 days ago but it
now seems
my portage database is problematic and the typical emerge commands
are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it
an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the
gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



- --
gentoo-alpha@gentoo.org mailing list



*** END PGP VERIFIED MESSAGE ***


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQWrZ1PZ0qmLutBiIEQIUeQCgxgY0dIUfqrKMZRwIEhiLK+qlE6gAoIry
4UYNuHAPhe+yxR1qTJpZAr9b
=61Fh
-----END PGP SIGNATURE-----


--
gentoo-alpha@gentoo.org mailing list
Re: Portage problem [ In reply to ]
As I've not had any success in restoring emerge functionality to the system.
I'm wiping it and doing a full restore of the system from my backup tape
from 3 weeks ago.

Hopefully this will resolve the emerge failures. Otherwise its back to
Gentoo 2004.2 and build out from my backup world file. The re-compile time
should be about 5 days with all that I've emerged over the past year. What
a way to upgrade...

Brian Parkhurst
www.pyrobrian.com (offline at the moment)



--
gentoo-alpha@gentoo.org mailing list