| 1 |
On Sat, Jul 26, 2008 at 7:22 PM, Dale <dalek1967@×××××××××.net> wrote: |
| 2 |
> Mark Knecht wrote: |
| 3 |
<SNIP> |
| 4 |
>> |
| 5 |
>> |
| 6 |
>> Somehow the equery depends seems very unhappy. python-updater hasn't |
| 7 |
>> run but equery is doing this: |
| 8 |
>> |
| 9 |
>> dragonfly ~ # equery depends =dev-lang/python-2.3.6-r2 |
| 10 |
>> [ Searching for packages depending on =dev-lang/python-2.3.6-r2... ] |
| 11 |
>> !!! Warning: No packages found matching =dev-lang/python-2.3.6-r2 |
| 12 |
>> dragonfly ~ # |
| 13 |
>> |
| 14 |
>> I'm very confused at this point. |
| 15 |
>> |
| 16 |
>> I wonder what I'd even call a different thread! :-) |
| 17 |
>> |
| 18 |
>> - Mark |
| 19 |
>> |
| 20 |
> |
| 21 |
> Have you tried to unmask x11-libs/vte-0.16.12 and see if that works? Just |
| 22 |
> put the following in package.unmask: "=x11-libs/vte-0.16.12 " See if that |
| 23 |
> helps any. |
| 24 |
> |
| 25 |
> It appears that you have not updated your system in a while. It may take |
| 26 |
> some time to sort all this out. ;-) |
| 27 |
> |
| 28 |
> Dale |
| 29 |
|
| 30 |
OK, what I'm doing (which seems to be working so far) is masking |
| 31 |
python-updater-0.5 and doing an update using python-updater-0.2 which |
| 32 |
was on the machine already. It seems that somehow python-updater-0.5 |
| 33 |
requires a newer python already be on the machine and if it isn't this |
| 34 |
block gets created. The problems unfortunately run a bit deeper than |
| 35 |
that as python-updater-0.2 complains about multiple slot issues which |
| 36 |
isn't a big deal except there weren't any. The 5 packages it didn't |
| 37 |
like weren't in use according to equery depends so I unmerged them by |
| 38 |
hand, emerged them by hand to get them back on the system, and now |
| 39 |
python-updater-0.2 has created an 86 package emerge which is finally |
| 40 |
running. We'll see if it completes... |
| 41 |
|
| 42 |
I think these latest tools are not very well QA'ed, but of course if |
| 43 |
the portage tree wasn't pruned so aggressively then maybe we normal |
| 44 |
people have enough time to get to this stuff before all these problems |
| 45 |
are created. |
| 46 |
|
| 47 |
With 7 Gentoo machines here at home if the others are this much |
| 48 |
trouble to update then it may be time for me to look for a new distro. |
| 49 |
I would literally cry if I had to stop using Gentoo but maybe it's |
| 50 |
coming to that. After 8 years of running nothing but Gentoo this |
| 51 |
problem is becoming too much of an issue. I cannot do this much work |
| 52 |
on 7 machines. Updates (for me) need to be quarterly, not weekly... |
| 53 |
|
| 54 |
Cheers, |
| 55 |
Mark |
Archives