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
--
[EMAIL PROTECTED] mailing list
