| 1 |
>> From pre11 on I often get errors which always look like (this is with |
| 2 |
>> the last one released, pre17): |
| 3 |
>> |
| 4 |
>> # emerge mozilla -p |
| 5 |
>> |
| 6 |
>> |
| 7 |
>> Invalid package name: moznomail |
| 8 |
>> |
| 9 |
>> These are the packages that I would merge, in order: |
| 10 |
>> |
| 11 |
>> Calculating dependencies |
| 12 |
>> !!! Problem in net-www/mozilla dependencies. |
| 13 |
>> !!! 73 |
| 14 |
|
| 15 |
>http://bugs.gentoo.org/show_bug.cgi?id=57212 |
| 16 |
|
| 17 |
Oh ****, this time you were already into it. As I said, I had similar |
| 18 |
problems with some 2.0.49 versions already, and back them I didn't find |
| 19 |
anybody else facing them. |
| 20 |
I should have checked bugzilla anyway, sorry. |
| 21 |
|
| 22 |
>The _pre11 patch you provided will cause lots of problems with regards to |
| 23 |
>virtuals. For example, if the default virtual/x11 is xfree and the user tries |
| 24 |
>to emerge xorg-x11, portage will try to install both xfree and xorg-x11 |
| 25 |
>without those lines. |
| 26 |
|
| 27 |
As I explained, it was not itself a patch, but only a hunk of |
| 28 |
difference between pre10 and pre11 which made pre10 fail when applied. |
| 29 |
I have no idea of Python, hence I thought the quickest way to find a |
| 30 |
workaround --which could also be a hint for where to look for a proper |
| 31 |
bug fix-- was going over every difference between both portage releases. |
| 32 |
|
| 33 |
>The _pre17 patch I'm not to sure about, but it is definately unrelated to the |
| 34 |
>problem you are having - even if enabling the code does appear to fix it. |
| 35 |
|
| 36 |
The procedure I followed to get to it was the same as for the pre11. |
| 37 |
Anyhow, I began to see that it was not a proper fix when I started to |
| 38 |
read pym/portage.py and bin/emerge more closely, and also after I saw |
| 39 |
packages and virtuals blocking was not working at all. |
| 40 |
|
| 41 |
>Anyway, it is fixed now and will be in portage-2.0.51_pre18. |
| 42 |
|
| 43 |
Thanks a lot, I've tried the patch you provide on bug #57212 and it |
| 44 |
definitely solves all my problems and without any side effect. Virtuals' |
| 45 |
blocking, packages blocking within normal ebuilds, ... everything works |
| 46 |
fine. |
| 47 |
I'll be trying to see if I get again the 'invalid package name' when |
| 48 |
doing an 'ebuild xxxxxxx.ebuild qmerge' after it has been compiled & |
| 49 |
installed properly. Since your patch only targets bin/emerge, the ebuild |
| 50 |
problem will remain. It is much less common to hit a package which shows |
| 51 |
this behavior, though, at least with pre17, for other older versions it |
| 52 |
was much more common. |
| 53 |
|
| 54 |
BTW, do you think I should file a bug report about the hardened-gcc not |
| 55 |
existing anymore but being present on current gcc ebuilds? |
| 56 |
|
| 57 |
Thanks again :) This indeed was faaast, much faster than my tonight |
| 58 |
chasing session (in a language unknown to me). |
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
"Our nation must come together to unite." |
| 63 |
|
| 64 |
George W. Bush |
| 65 |
June 4, 2001 |
| 66 |
Remark made in Tampa, Florida. |
| 67 |
|
| 68 |
Javier Marcet <javier@××××××.info> |
Archives