--nextPart1503316.qlTdBgkyGd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > Subject: [gentoo-user] portage upgrade =3D error Well, sure, a portage update may result into an error, but an error may not= =20 result into an portage upgrade. so, you shall not choose the =3D but try = =3D>=20 instead ;) On Friday 17 September 2004 6:23 pm, Michael W. Holdeman wrote: > After upgrading portage today I cannot emerge anything, this is only on t= he > machine that gets it distfiles via nfs, the laptopm that has its own > distfiles works fine. > The user is a member aof the portage group, although I am using root to > emerge the files. [snip] try emerge -B portage on a working box, move that newly created binary pack= age=20 over to the infected machine's /path/to/portage/packages/All/ and emerge -k= =20 portage then. Maybe this works well ;) Christian Parpart. =2D-=20 19:57:46 up 24 days, 7:37, 3 users, load average: 0.26, 0.31, 0.32 --nextPart1503316.qlTdBgkyGd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBBSyYkPpa2GmDVhK0RAka5AJwLG4VO+lXW420UhImE4L2gh64guwCdHIVp FIaA+3NbVt86eUPgpdGjK/M= =OPHh -----END PGP SIGNATURE----- --nextPart1503316.qlTdBgkyGd--