On 13 May 2009, at 11:03, Alexey Luchko wrote:
Alexey Luchko wrote:
colinux ~ # emerge portage --pretend --tree
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[nomerge ] sys-apps/portage-2.1.6.11 [2.1.2.2]
[ebuild U ] app-shells/bash-3.2_p39 [3.1_p17] USE="-examples% -
plugins%"
[ebuild U ] sys-apps/portage-2.1.6.11 [2.1.2.2]
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
[ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17]
[ebuild N ] app-arch/lzma-utils-4.32.7 USE="-nocxx"
[ebuild N ] app-admin/eselect-news-20080320
[ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE="-vim-
syntax%"
[ebuild U ] app-misc/pax-utils-0.1.19 [0.1.15]
[blocks B ] <sys-apps/portage-2.1.5 (is blocking app-shells/
bash-3.2_p39)
colinux ~ #
Hi!
Thank every one for your help.
Finally I got it out this way:
first emerge --nodeps bash
then emerge portage upgraded portage to the latest version
and then, of cause, emerge -uDN system -pvt
it had blocked packages
[blocks B ] <sys-apps/man-pages-3 ("<sys-apps/man-pages-3" is
blocking
sys-apps/man-pages-posix-2003a)
[blocks B ] <sys-fs/e2fsprogs-1.41 ("<sys-fs/e2fsprogs-1.41" is
blocking
sys-libs/e2fsprogs-libs-1.41.3-r1)
[blocks B ] sys-apps/mktemp ("sys-apps/mktemp" is blocking
sys-apps/coreutils-7.1)
[blocks B ] sys-libs/com_err ("sys-libs/com_err" is blocking
sys-libs/e2fsprogs-libs-1.41.3-r1)
[blocks B ] <sys-apps/util-linux-2.13 ("<sys-apps/util-
linux-2.13" is
blocking sys-apps/coreutils-7.1)
[blocks B ] sys-libs/ss ("sys-libs/ss" is blocking
sys-libs/e2fsprogs-libs-1.41.3-r1)
I unmerged them, and then emerge -uDN system had been working fine
until
sys-libs/e2fsprogs-libs-1.41.3-r1 compilation failed with
../../lib/libuuid.so: undefined reference to `___tls_get_addr'
Alexey,
I think `emerge --nodeps bash` was the cause of your problem. You need
to resolve each and every dependency - often sequentially or
incrementally - before you go on to the next package. --nodpes is just
asking your system to break.
I gave you advice in my previous message - you should have emerged
earlier versions of packages in order, for the reason to avoid
blockers. The Gentoo devs had a GOOD REASON when they declared
bash-3.2_p39 as blocking the current portage. If you had tried to
emerge the earlier bash you would probably have found it blocked by an
earlier portage &/or mktemp &/or com_err &/or util-linux &/or sys-libs/
ss. If you had resolved each dependency in turn you would have
eventually been able to upgrade to the latest versions.
I know this, because last month I did this myself. A system last
upgraded in August or September 2007 now has bash-3.2_p39 and
portage-2.1.6.4 installed on it.
If you don't have the patience for this, then do as Alan says &
reinstall the whole system.
If you don't understand what I wrote, then just ask.
If you want to upgrade this system then you're going to have to do a
lot of work yourself. You WILL need to get older intermediate package
versions from the CVS attic <http://sources.gentoo.org/> and you will
need to Google & read the list archive to see the correct procedure
for resolving the mktemp, com_err, util-linux & sys-libs/ss problems.
But that really is pretty straightforward - it is clearly documented
on the list "emerge version X of this, then version Y of that".
Stroller.
