Mailing List Archive: emerge fails after update

emerge fails after update

Oct 25, 2004, 2:14 AM

Post #1 of 5 (368 views)

Hi,

After upgrading portage to portage-2.0.51_rc7 I've started getting errors
when using any portage command.

emerge-webrsync comes back with the following error:
***************************************************************************
>>> Updating Portage cache... ...done!

/usr/lib/portage/bin/ebuild.sh: line 1319:
/usr/portage/eclass/eutils.eclass: No such file or directory

!!! ERROR: sys-apps/portage-2.0.51_rc7 failed.
!!! Function inherit, Line 1320, Exitcode 1
!!! died sourcing /usr/portage/eclass/eutils.eclass in inherit()
!!! If you need support, post the topmost build error, NOT this status
message.

aux_get(): (0) Error in sys-apps/portage-2.0.51_rc7 ebuild. (1)
Check for syntax error or corruption in the ebuild. (--debug)

***************************************************************************

and if I try to do an emerge, I'm getting this:
***************************************************************************
# emerge portage
!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?
***************************************************************************

The /etc/make.profile links to ../usr/portage/profiles/default-x86-2004.0
(wich does NOT exist)

Any suggestions on how to solve this?

Regards,
--Dan

--
gentoo-user@gentoo.org mailing list

Re: emerge fails after update [ In reply to ]

motub at planet

Oct 25, 2004, 6:02 AM

Post #2 of 5 (365 views)

Permalink

Dan Johansson wrote:
> Hi,
> After upgrading portage to portage-2.0.51_rc7 I've started getting
> errors when using any portage command.
> emerge-webrsync comes back with the following error:
> ***************************************************************************
>
>>>> Updating Portage cache... ...done!
>
>
> /usr/lib/portage/bin/ebuild.sh: line 1319:
> /usr/portage/eclass/eutils.eclass: No such file or directory
> !!! ERROR: sys-apps/portage-2.0.51_rc7 failed.
> !!! Function inherit, Line 1320, Exitcode 1
> !!! died sourcing /usr/portage/eclass/eutils.eclass in inherit()
> !!! If you need support, post the topmost build error, NOT this status
> message.
>
> aux_get(): (0) Error in sys-apps/portage-2.0.51_rc7 ebuild. (1)
> Check for syntax error or corruption in the ebuild. (--debug)
> ***************************************************************************
> and if I try to do an emerge, I'm getting this:
> ***************************************************************************
> # emerge portage
> !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> !!! Is the symlink correct? Is your portage tree complete?
> ***************************************************************************
> The /etc/make.profile links to
> ../usr/portage/profiles/default-x86-2004.0 (wich does NOT exist)
> Any suggestions on how to solve this?
> Regards,
> --Dan

Maybe it was a bug in the RC, which was a rather old rc, all things
considered,even a couple of days ago. Portage development moved really
fast there before the release of 2.0.51-- I emerged one RC the day after
it was released, and had to upgrade it the same day (as a new RC,
jumping at least two versions was released).

I didn't have this problem that I recall (but I literally only had rc7
for a couple of hours, and didn't get to use it other than to update
Portage itself; iirc the incident I refer to occurred between rc7 and
rc9 or 10), but in any case 2.0.51 has been released and marked stable
(and is already on -r2, while rc7 is the only unstable version left in
the database), so my first suggestion would be to upgrade to that, and
see if the problem persists.

HTH,

Holly

--
gentoo-user@gentoo.org mailing list

Re: emerge fails after update [ In reply to ]

daniel at acceleration

Oct 25, 2004, 6:09 AM

Post #3 of 5 (380 views)

Permalink

On 2004-10-25 11:14:32 +0200, Dan Johansson wrote:
> Hi,
>
> After upgrading portage to portage-2.0.51_rc7 I've started getting
> errors when using any portage command.
>
> emerge-webrsync comes back with the following error:
> *********************************************************************
> >>>Updating Portage cache... ...done!
>
> /usr/lib/portage/bin/ebuild.sh: line 1319:
> /usr/portage/eclass/eutils.eclass: No such file or directory

Looks like you got the bad websync tarball. See
http://bugs.gentoo.org/show_bug.cgi?id=68790.

--
Daniel Westermann-Clark

--
gentoo-user@gentoo.org mailing list

Re: emerge fails after update [ In reply to ]

ext-dirk.heinrichs at nokia

Oct 25, 2004, 6:14 AM

Post #4 of 5 (366 views)

Permalink

Am Montag, 25. Oktober 2004 11:14 schrieb ext Dan Johansson:
> emerge-webrsync comes back with the following error:
^^^^^^^^^^^^^^^
That's the problem: the portage snapshot portage-20041024.tar.bz2 was
broken. It was about 916k in size (instead of 15M). There is a new snapshot
now, so depending on your selected mirrors you may get the correct snapshot
if you try again.

HTH...

Dirk
--
Dirk Heinrichs | Tel: +49 (0)151 1513 6954
Configuration Manager | Fax: +49 (0)211 47068 111
Cap Gemini Deutschland | Mail: dirk.heinrichs@capgemini.com
HambornerstraÃŸe 55 | Web: http://www.capgemini.com
D-40472 DÃ¼sseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

--
gentoo-user@gentoo.org mailing list

Re: [SOLVED] emerge fails after update [ In reply to ]

Dan.Johansson at dmj

Oct 25, 2004, 10:55 AM

Post #5 of 5 (375 views)

Permalink

On Monday 25 October 2004 15.14, Dirk Heinrichs wrote:
> Am Montag, 25. Oktober 2004 11:14 schrieb ext Dan Johansson:
> > emerge-webrsync comes back with the following error:
>
> ^^^^^^^^^^^^^^^
> That's the problem: the portage snapshot portage-20041024.tar.bz2 was
> broken. It was about 916k in size (instead of 15M). There is a new snapshot
> now, so depending on your selected mirrors you may get the correct snapshot
> if you try again.
After doing a emerge-webrsync again this evening everything works OK again.

Thanks,
--Dan

--
gentoo-user@gentoo.org mailing list