From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Alexey Luchko <luchik@gmail.com>
Subject: Re: [gentoo-user] Re: how to recover a portage that wasn't in use for very long time
Date: Wed, 13 May 2009 12:17:11 +0200 [thread overview]
Message-ID: <200905131217.11212.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4A0A9AFC.50203@gmail.com>
On Wednesday 13 May 2009 12:03:40 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.
[snip long sad story of portage blockers]
> Here I am now ;)
> Any advice is welcome!
Why are you doing this? Is it to learn how to cope with such things?
If not, you are really wasting time that you will never get back. The last 18
months has seen much activity in the tree, lot's of it from large packages
being split into smaller ones, and blockers installed.
You've already come across mktemp/coreutils and e2fsprogs. You still have to
deal with bash/python then that delicious recent cock-up with wget, expat and
you have to decide if you want com_err or not. And plenty more. This all
happened so long ago I forget the details (lucky for you it's all in the mail
archives!).
Trust me, if this is not a learning exercise, just unmount your data volumes
and reinstall the machine. The pain is not worth it. Really. Especially if
glibc decides it doesn't like your headers, then you really are up the creek
if you didn't quickpkg critical apps in the system set first :-)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-05-13 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 0:58 [gentoo-user] how to recover a portage that wasn't in use for very long time Alexey Luchko
2009-05-10 1:54 ` Mike Kazantsev
2009-05-10 1:56 ` Mike Kazantsev
2009-05-10 12:20 ` Stroller
2009-05-10 17:31 ` Alan McKinnon
2009-05-10 19:25 ` [gentoo-user] " Francesco Talamona
2009-05-10 22:31 ` [gentoo-user] " Nick Fortino
2009-05-12 13:56 ` Alexey Luchko
2009-05-13 10:03 ` [gentoo-user] " Alexey Luchko
2009-05-13 10:17 ` Alan McKinnon [this message]
2009-05-13 14:16 ` Stroller
2009-05-13 14:27 ` Alan McKinnon
2009-05-13 14:49 ` Stroller
2009-05-13 15:00 ` Alan McKinnon
2009-05-13 15:14 ` Paul Hartman
2009-05-13 15:30 ` Graham Murray
2009-05-13 15:44 ` Paul Hartman
2009-05-13 16:55 ` Neil Bothwick
2009-05-13 14:33 ` Stroller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905131217.11212.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=luchik@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox