[gentoo-user] portage update problem

[gentoo-user] portage update problem

[Rafael Barrera Oro]

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

Hello, just installed from gentoo LiveCd 2006.0

after an emerge --sync, i upgraded portage, everything was running smooth
until the unmerging of the previous portage version started, this ended
abruptly with the error:

*[portage-2.0.54] bash: /usr/lib/portage/bin/ebuild.sh: No such file or
directory


*after that, whenever i invoke the emerge command in any manner, emerge
package, emerge sync, etc i get:

Traceback (most recent call last):
  File "/usr/bin/emerge", line 37, in ?
    from output import blue, bold, colorize, darkblue, darkgreen, darkred,
green, \
ImportError: cannot import name colorize

i am really baffled by this, and since what is failing its portage itself i
am really power less to solve this since i am a little short of ideas

i cry to you all for help

thanks in advance

Rafael

[-- Attachment #2: Type: text/html, Size: 999 bytes --]

Re: [gentoo-user] portage update problem

[Alan McKinnon]

On Thursday 06 September 2007, Rafael Barrera Oro wrote:
> Hello, just installed from gentoo LiveCd 2006.0
>
> after an emerge --sync, i upgraded portage, everything was running
> smooth until the unmerging of the previous portage version started,
> this ended abruptly with the error:
>
> *[portage-2.0.54] bash: /usr/lib/portage/bin/ebuild.sh: No such file
> or directory


Hmm, I don't seem to have ever seen that one before.

If you don't get help anywhere else, what could possibly solve it is to:

build a binpackage from the livecd and store it somewhere
emerge -k this to your real system

Hopefully this will give you a working portage. Then,
upgrade portage incrementally, say from 2.0.x to 2.2.1.x to 2.1.2.x to 
2.1.3.x, taking not of all notices printed to the console and doing the 
appropriate thing at each step.

This is a brute force approach that you should use only if no-one else 
tells you exactly what's going on. I myself have done several installs 
since June this year off a 2006.0 CD, and each time portage was a bit 
tricky, but never the error you are experiencing.

Good luck

alan


>
>
> *after that, whenever i invoke the emerge command in any manner,
> emerge package, emerge sync, etc i get:
>
> Traceback (most recent call last):
>   File "/usr/bin/emerge", line 37, in ?
>     from output import blue, bold, colorize, darkblue, darkgreen,
> darkred, green, \
> ImportError: cannot import name colorize
>
> i am really baffled by this, and since what is failing its portage
> itself i am really power less to solve this since i am a little short
> of ideas
>
> i cry to you all for help
>
> thanks in advance
>
> Rafael



-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] portage update problem

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Thursday 06 September 2007 17:22:15 Rafael Barrera Oro wrote:
> Hello, just installed from gentoo LiveCd 2006.0

Why are you using such an ancient stage?

> after an emerge --sync, i upgraded portage, everything was running smooth
> until the unmerging of the previous portage version started, this ended
> abruptly with the error:
>
> *[portage-2.0.54] bash: /usr/lib/portage/bin/ebuild.sh: No such file or
> directory
>
>
> *after that, whenever i invoke the emerge command in any manner, emerge
> package, emerge sync, etc i get:
>
> Traceback (most recent call last):
>   File "/usr/bin/emerge", line 37, in ?
>     from output import blue, bold, colorize, darkblue, darkgreen, darkred,
> green, \
> ImportError: cannot import name colorize
>
> i am really baffled by this, and since what is failing its portage itself i
> am really power less to solve this since i am a little short of ideas
>
> i cry to you all for help

Bug #172015 ?

# cd /usr && ln -s lib64 lib

As per comment 4 on bug #170178 there are hardened amd64 multilib stages from 
2007.0.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] portage update problem

[Rafael Barrera Oro]

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

I tried the 2007.0 amd64 LiveCD with no success. I tried the graphical
installer and whenever it got the unpack stage from LiveCD part, it hanged
for ever, did not freeze my machina though. So i tried the non graphical
installer which always died after formating the disk partitions. I posted
about this and since i did not get any answers tried with the 2006.0 which
was the best i could do at that moment.

2007/9/6, Bo Ørsted Andresen <bo.andresen@zlin.dk>:
>
> On Thursday 06 September 2007 17:22:15 Rafael Barrera Oro wrote:
> > Hello, just installed from gentoo LiveCd 2006.0
>
> Why are you using such an ancient stage?
>
> > after an emerge --sync, i upgraded portage, everything was running
> smooth
> > until the unmerging of the previous portage version started, this ended
> > abruptly with the error:
> >
> > *[portage-2.0.54] bash: /usr/lib/portage/bin/ebuild.sh: No such file or
> > directory
> >
> >
> > *after that, whenever i invoke the emerge command in any manner, emerge
> > package, emerge sync, etc i get:
> >
> > Traceback (most recent call last):
> >   File "/usr/bin/emerge", line 37, in ?
> >     from output import blue, bold, colorize, darkblue, darkgreen,
> darkred,
> > green, \
> > ImportError: cannot import name colorize
> >
> > i am really baffled by this, and since what is failing its portage
> itself i
> > am really power less to solve this since i am a little short of ideas
> >
> > i cry to you all for help
>
> Bug #172015 ?
>
> # cd /usr && ln -s lib64 lib
>
> As per comment 4 on bug #170178 there are hardened amd64 multilib stages
> from
> 2007.0.
>
> --
> Bo Andresen
>
>

[-- Attachment #2: Type: text/html, Size: 2023 bytes --]

[gentoo-user] portage update problem

[Redouane Boumghar]

Hello all,

I am using the same topic as Rafael Barrera Oro the 6th of September 2007

I updated portage 
from sys-apps/portage-2.0.54-r2
to   sys-apps/portage-2.1.3.19
And the unmerging of sys-apps/portage-2.0.54-r2
ended like this :
----------------------------------------------------------------------
 * 
 * FEATURES="userfetch" is now enabled by default. Depending on your ${DISTDIR}
 * permissions, this may result in Permission Denied errors. If you would like
 * to fetch with superuser privileges, add FEATURES="-userfetch" to make.conf.
 * 
 * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
 * cases, emerge --depclean may remove slots that it would not have removed
 * in the past. The emerge --noreplace command can be used to add an atom to
 * the world file and prevent matching packages from being removed.  A slot
 * atom will be recorded in the world file for any atom that is precise enough
 * to identify a specific slot.
 * 
 * For help with using portage please consult the Gentoo Handbook
 * at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3
 * 
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-2.1.3.19 merged.

 sys-apps/portage
    selected: 2.0.54-r2
   protected: 2.1.3.19
     omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1 
>>> Unmerging sys-apps/portage-2.0.54-r2...
No package files given... Grabbing a set.
--- !mtime obj /usr/share/man/man5/portage.5.gz
--- !mtime obj /usr/share/man/man5/make.conf.5.gz
--- !mtime obj /usr/share/man/man5/ebuild.5.gz
--- !mtime obj /usr/share/man/man1/repoman.1.gz
--- !mtime obj /usr/share/man/man1/quickpkg.1.gz
--- !mtime obj /usr/share/man/man1/etc-update.1.gz
--- !mtime obj /usr/share/man/man1/env-update.1.gz
--- !mtime obj /usr/share/man/man1/emerge.1.gz
--- !mtime obj /usr/share/man/man1/ebuild.1.gz
--- !mtime obj /usr/share/man/man1/dispatch-conf.1.gz
[... lines snipped ...]
--- !empty dir /usr/share/man/man5
--- !empty dir /usr/share/man/man1
--- !empty dir /usr/share/man
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/sbin
--- !empty dir /usr/lib/python2.4/site-packages
--- !empty dir /usr/lib/python2.4
--- !empty dir /usr/lib/portage/pym
--- !empty dir /usr/lib/portage
--- !empty dir /usr/lib
--- !empty dir /usr/bin
--- !empty dir /usr
--- !empty dir /etc
--- !targe sym /usr/sbin/regenworld
--- !targe sym /usr/sbin/quickpkg
--- !targe sym /usr/sbin/fixpackages
--- !targe sym /usr/sbin/etc-update
--- !targe sym /usr/sbin/env-update
--- !targe sym /usr/sbin/emerge-webrsync
--- !targe sym /usr/sbin/emaint
--- !targe sym /usr/sbin/dispatch-conf
--- !targe sym /usr/sbin/archive-conf
--- !targe sym /usr/bin/xpak
--- !targe sym /usr/bin/tbz2tool
--- !targe sym /usr/bin/repoman
--- !targe sym /usr/bin/portageq
--- !targe sym /usr/bin/emerge
--- !targe sym /usr/bin/ebuild
[portage-2.0.54-r2] bash: /usr/lib/portage/bin/ebuild.sh: No such file or directory
!!! FAILED postrm: 127
----------------------------------------------------------------------





Ok now everytime I try to use emerge I get this :
root ~ # emerge -s alfred
Traceback (most recent call last):
  File "/usr/bin/emerge", line 37, in ?
    from output import blue, bold, colorize, darkblue, darkgreen, darkred, green, \
ImportError: cannot import name colorize


and I guess I found the source and have to reinstall portage manually
The fact is that i changed the make.profile to a 64 bits profile since
the server I use is said to be 64 bits .
but it's a :
vendor_id       : GenuineIntel
model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
clflush size    : 64
vendor_id       : GenuineIntel
model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
clflush size    : 64

So now when I get :
root ~ # ls -l $(whereis emerge) 2>> /dev/null 
lrwxrwxrwx 1 root root    27 déc 18 16:22 /usr/bin/emerge -> ../lib64/portage/bin/emerge
-rw-r--r-- 1 root root 11305 déc 18 16:22 /usr/share/man/man1/emerge.1.gz

So I suppose my Intel can't execute that lib64 portage binary !!!!
So I'll link my make.profile back to a normal x86 arch
and reinstall portage manually...

Anyone any better suggestion ?

Thanks in advance,

-- 
Redouane BOUMGHAR
Physics, Remote Sensing and Digital Imagery

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] portage update problem

[Redouane Boumghar]

Oh well.. replying to myself

to avoid anyone trying to resolve that problem.
I ordered a reinstallation...

Red.


Redouane Boumghar wrote:
> Hello all,
> 
> I am using the same topic as Rafael Barrera Oro the 6th of September 2007
> 
> I updated portage 
> from sys-apps/portage-2.0.54-r2
> to   sys-apps/portage-2.1.3.19
> And the unmerging of sys-apps/portage-2.0.54-r2
> ended like this :
> ----------------------------------------------------------------------
>  * 
>  * FEATURES="userfetch" is now enabled by default. Depending on your ${DISTDIR}
>  * permissions, this may result in Permission Denied errors. If you would like
>  * to fetch with superuser privileges, add FEATURES="-userfetch" to make.conf.
>  * 
>  * The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some
>  * cases, emerge --depclean may remove slots that it would not have removed
>  * in the past. The emerge --noreplace command can be used to add an atom to
>  * the world file and prevent matching packages from being removed.  A slot
>  * atom will be recorded in the world file for any atom that is precise enough
>  * to identify a specific slot.
>  * 
>  * For help with using portage please consult the Gentoo Handbook
>  * at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3
>  * 
>>>> Regenerating /etc/ld.so.cache...
>>>> sys-apps/portage-2.1.3.19 merged.
> 
>  sys-apps/portage
>     selected: 2.0.54-r2
>    protected: 2.1.3.19
>      omitted: none
> 
>>>> 'Selected' packages are slated for removal.
>>>> 'Protected' and 'omitted' packages will not be removed.
> 
>>>> Waiting 5 seconds before starting...
>>>> (Control-C to abort)...
>>>> Unmerging in: 5 4 3 2 1 
>>>> Unmerging sys-apps/portage-2.0.54-r2...
> No package files given... Grabbing a set.
> --- !mtime obj /usr/share/man/man5/portage.5.gz
> --- !mtime obj /usr/share/man/man5/make.conf.5.gz
> --- !mtime obj /usr/share/man/man5/ebuild.5.gz
> --- !mtime obj /usr/share/man/man1/repoman.1.gz
> --- !mtime obj /usr/share/man/man1/quickpkg.1.gz
> --- !mtime obj /usr/share/man/man1/etc-update.1.gz
> --- !mtime obj /usr/share/man/man1/env-update.1.gz
> --- !mtime obj /usr/share/man/man1/emerge.1.gz
> --- !mtime obj /usr/share/man/man1/ebuild.1.gz
> --- !mtime obj /usr/share/man/man1/dispatch-conf.1.gz
> [... lines snipped ...]
> --- !empty dir /usr/share/man/man5
> --- !empty dir /usr/share/man/man1
> --- !empty dir /usr/share/man
> --- !empty dir /usr/share/doc
> --- !empty dir /usr/share
> --- !empty dir /usr/sbin
> --- !empty dir /usr/lib/python2.4/site-packages
> --- !empty dir /usr/lib/python2.4
> --- !empty dir /usr/lib/portage/pym
> --- !empty dir /usr/lib/portage
> --- !empty dir /usr/lib
> --- !empty dir /usr/bin
> --- !empty dir /usr
> --- !empty dir /etc
> --- !targe sym /usr/sbin/regenworld
> --- !targe sym /usr/sbin/quickpkg
> --- !targe sym /usr/sbin/fixpackages
> --- !targe sym /usr/sbin/etc-update
> --- !targe sym /usr/sbin/env-update
> --- !targe sym /usr/sbin/emerge-webrsync
> --- !targe sym /usr/sbin/emaint
> --- !targe sym /usr/sbin/dispatch-conf
> --- !targe sym /usr/sbin/archive-conf
> --- !targe sym /usr/bin/xpak
> --- !targe sym /usr/bin/tbz2tool
> --- !targe sym /usr/bin/repoman
> --- !targe sym /usr/bin/portageq
> --- !targe sym /usr/bin/emerge
> --- !targe sym /usr/bin/ebuild
> [portage-2.0.54-r2] bash: /usr/lib/portage/bin/ebuild.sh: No such file or directory
> !!! FAILED postrm: 127
> ----------------------------------------------------------------------
> 
> 
> 
> 
> 
> Ok now everytime I try to use emerge I get this :
> root ~ # emerge -s alfred
> Traceback (most recent call last):
>   File "/usr/bin/emerge", line 37, in ?
>     from output import blue, bold, colorize, darkblue, darkgreen, darkred, green, \
> ImportError: cannot import name colorize
> 
> 
> and I guess I found the source and have to reinstall portage manually
> The fact is that i changed the make.profile to a 64 bits profile since
> the server I use is said to be 64 bits .
> but it's a :
> vendor_id       : GenuineIntel
> model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
> clflush size    : 64
> vendor_id       : GenuineIntel
> model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
> clflush size    : 64
> 
> So now when I get :
> root ~ # ls -l $(whereis emerge) 2>> /dev/null 
> lrwxrwxrwx 1 root root    27 déc 18 16:22 /usr/bin/emerge -> ../lib64/portage/bin/emerge
> -rw-r--r-- 1 root root 11305 déc 18 16:22 /usr/share/man/man1/emerge.1.gz
> 
> So I suppose my Intel can't execute that lib64 portage binary !!!!
> So I'll link my make.profile back to a normal x86 arch
> and reinstall portage manually...
> 
> Anyone any better suggestion ?
> 
> Thanks in advance,
> 

-- 
Redouane BOUMGHAR
Physics, Remote Sensing and Digital Imagery

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] portage update problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Tue, 18 Dec 2007 17:50:22 +0100, Redouane Boumghar wrote:

> and I guess I found the source and have to reinstall portage manually
> The fact is that i changed the make.profile to a 64 bits profile since
> the server I use is said to be 64 bits .
> but it's a :
> vendor_id       : GenuineIntel
> model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz

This is a 64 bit processor.


-- 
Neil Bothwick

The opposite of a profound truth may well be another profound truth. *
Bohr

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] portage update problem

[Redouane Boumghar]

Yep thanks,

The default install was made on a 32bit profile
The reinstall with the 64 bit profile worked out well
and I am now upgrading with no problem.

Have a good day,


-- 
Redouane BOUMGHAR
Physics, Remote Sensing and Digital Imagery

Neil Bothwick wrote:
> On Tue, 18 Dec 2007 17:50:22 +0100, Redouane Boumghar wrote:
> 
>> and I guess I found the source and have to reinstall portage manually
>> The fact is that i changed the make.profile to a 64 bits profile since
>> the server I use is said to be 64 bits .
>> but it's a :
>> vendor_id       : GenuineIntel
>> model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
> 
> This is a 64 bit processor.
> 
> 

-- 
gentoo-user@gentoo.org mailing list