| 1 |
On Thu, 2008-06-26 at 14:21 +0200, Fabian Groffen wrote: |
| 2 |
> On 26-06-2008 12:54:14 +0200, Markus Duft wrote: |
| 3 |
> > > I've never seen it before. Could it be some dirty upgrade-path |
| 4 |
> > > problem? |
| 5 |
> > |
| 6 |
> > Maybe yes, I haven't seen it now anymore. |
| 7 |
> > |
| 8 |
> > And: portage does work _only_ with cPickle, not with pickle... I ruined another prefix, by simply doing update world, since portage is updated before python... AAAARRR... |
| 9 |
> |
| 10 |
> That must be some old portage then? I know zmedico put some efforts in |
| 11 |
> getting bash and python to be emerged before portage, but portage also |
| 12 |
> asap before any other packages. |
| 13 |
|
| 14 |
I get this.... |
| 15 |
|
| 16 |
These are the packages that would be merged, in order: |
| 17 |
|
| 18 |
Calculating dependencies... done! |
| 19 |
|
| 20 |
[ebuild U ] sys-apps/portage-2.2.00.10788 [2.2.00.10770] |
| 21 |
*** Portage will stop merging at this point and reload itself, |
| 22 |
then resume the merge. |
| 23 |
[ebuild U ] app-admin/python-updater-0.5 [0.4] |
| 24 |
[ebuild N ] virtual/editor-0 |
| 25 |
[ebuild N ] virtual/pager-0 |
| 26 |
[ebuild U ] dev-lang/python-2.5.2-r5 [2.5.2-r4] |
| 27 |
|
| 28 |
So portage is going to be emerged first. |
| 29 |
|
| 30 |
Alan. |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-alt@l.g.o mailing list |
Archives