| 1 |
On 02/19/2013 12:08 AM, Fabian Groffen wrote: |
| 2 |
> On 18-02-2013 15:55:11 -0700, darrell wrote: |
| 3 |
>> I ran emerge --sync today and the update from 3.3.0 to 3.3.0-r1 errored |
| 4 |
>> with the same message as before so did the update from 2.7.3-r2 to 2.7.3-r3. |
| 5 |
>> |
| 6 |
>> bootstrapping on the MBP got to 3.3.0-r1 and failed with the same error |
| 7 |
>> as well |
| 8 |
> |
| 9 |
> Can you please verify that you have |
| 10 |
> PREFIX_PATCHREV="-r2" |
| 11 |
> in 3.3.0-r1. And what is the problem with 2.7.3? |
| 12 |
|
| 13 |
|
| 14 |
3.3.0-r1 does have PREFIX_PATCHREV="-r2" on line 13 |
| 15 |
i removed EXTRA_ECONF from etc/portage/env/dev-lang/python |
| 16 |
and recompiled the ebuild. |
| 17 |
|
| 18 |
it downloaded python-prefix-3.3.0-gentoo-patches-r2.tar.bz2 |
| 19 |
before configure tonight which i apparently didn't already have (that |
| 20 |
was probably the problem). this time it compiled just fine. |
| 21 |
|
| 22 |
2.7.3-r3 didn't throw errors tonight either |
| 23 |
I didn't think to check if it downloaded patches prior to building. |
| 24 |
|
| 25 |
but to answer your question about what was wrong with 2.7.3-r3 update, |
| 26 |
it was giving me the same error as 3.3.0 in my original post. |
| 27 |
|
| 28 |
I hope all that made sense :) |
| 29 |
everything is working and all is fine, i'm going to sleep |
| 30 |
|
| 31 |
darrell |
Archives