1 |
> |
2 |
> On 26-06-2008 10:29:16 +0200, Markus Duft wrote: |
3 |
> > > |
4 |
> > > On 24-06-2008 13:00:32 +0200, Markus Duft wrote: |
5 |
> > > > > > No but it looks like a trunk problem to me. |
6 |
> > > > > |
7 |
> > > > > what platform is this? |
8 |
> > > > |
9 |
> > > > Interix of course :) I think the problem could be related to not |
10 |
> > > having cPickle on interix, but only the python pickle |
11 |
> implementation |
12 |
> > > (?) ... |
13 |
> > > |
14 |
> > > Could be. Can we fix cPickle in this horribly broken language? |
15 |
> > |
16 |
> > Wohoo, test_cpickle.py _nearly_ runs through ;) all tests that |
17 |
> require |
18 |
> > locales fail though (also with pickle instead of cPickle so it seems |
19 |
> > unrelated), since locales don't seem to work :x ... maybe I find some |
20 |
> > time to look into this somewhere in the future, but not now. I'll |
21 |
> > enable cPickle again. |
22 |
> |
23 |
> You added another patch to the already huge patchlist of python? |
24 |
> Great! |
25 |
|
26 |
Ok, after re-enabling cPickle and upgrading to sys-apps/portage-2.2.00.10788 I get |
27 |
|
28 |
Calculating dependencies \!!! Error loading '/opt/gentoo/var/cache/edb/vdb_blockers.pickle': Global and instance pickles are not supported. |
29 |
... done! |
30 |
|
31 |
After restarting portage, but emerging works fine now. Don't know wether it was cPickle, or the newer portage revision which fixed the problem. |
32 |
|
33 |
Still I fear that the vdb_blockers.pickle error is related to cPickle? Os is it some known issue? |
34 |
|
35 |
Cheers, Markus |
36 |
|
37 |
> |
38 |
> |
39 |
> -- |
40 |
> Fabian Groffen |
41 |
> Gentoo on a different level |
42 |
> -- |
43 |
> gentoo-alt@l.g.o mailing list |
44 |
|
45 |
|
46 |
-- |
47 |
gentoo-alt@l.g.o mailing list |