| 1 |
On Wednesday 13 May 2009 12:03:40 Alexey Luchko wrote: |
| 2 |
> Alexey Luchko wrote: |
| 3 |
> > colinux ~ # emerge portage --pretend --tree |
| 4 |
> > |
| 5 |
> > These are the packages that would be merged, in reverse order: |
| 6 |
> > |
| 7 |
> > Calculating dependencies... done! |
| 8 |
> > [nomerge ] sys-apps/portage-2.1.6.11 [2.1.2.2] |
| 9 |
> > [ebuild U ] app-shells/bash-3.2_p39 [3.1_p17] USE="-examples% |
| 10 |
> > -plugins%" |
| 11 |
> > [ebuild U ] sys-apps/portage-2.1.6.11 [2.1.2.2] |
| 12 |
> > [ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5] |
| 13 |
> > [ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17] |
| 14 |
> > [ebuild N ] app-arch/lzma-utils-4.32.7 USE="-nocxx" |
| 15 |
> > [ebuild N ] app-admin/eselect-news-20080320 |
| 16 |
> > [ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE="-vim-syntax%" |
| 17 |
> > [ebuild U ] app-misc/pax-utils-0.1.19 [0.1.15] |
| 18 |
> > [blocks B ] <sys-apps/portage-2.1.5 (is blocking |
| 19 |
> > app-shells/bash-3.2_p39) |
| 20 |
> > colinux ~ # |
| 21 |
> |
| 22 |
> Hi! |
| 23 |
> |
| 24 |
> Thank every one for your help. |
| 25 |
|
| 26 |
[snip long sad story of portage blockers] |
| 27 |
|
| 28 |
> Here I am now ;) |
| 29 |
> Any advice is welcome! |
| 30 |
|
| 31 |
Why are you doing this? Is it to learn how to cope with such things? |
| 32 |
|
| 33 |
If not, you are really wasting time that you will never get back. The last 18 |
| 34 |
months has seen much activity in the tree, lot's of it from large packages |
| 35 |
being split into smaller ones, and blockers installed. |
| 36 |
|
| 37 |
You've already come across mktemp/coreutils and e2fsprogs. You still have to |
| 38 |
deal with bash/python then that delicious recent cock-up with wget, expat and |
| 39 |
you have to decide if you want com_err or not. And plenty more. This all |
| 40 |
happened so long ago I forget the details (lucky for you it's all in the mail |
| 41 |
archives!). |
| 42 |
|
| 43 |
Trust me, if this is not a learning exercise, just unmount your data volumes |
| 44 |
and reinstall the machine. The pain is not worth it. Really. Especially if |
| 45 |
glibc decides it doesn't like your headers, then you really are up the creek |
| 46 |
if you didn't quickpkg critical apps in the system set first :-) |
| 47 |
|
| 48 |
-- |
| 49 |
alan dot mckinnon at gmail dot com |
Archives