| 1 |
On 30/10/10 16:45, Fabian Groffen wrote: |
| 2 |
> On 30-10-2010 16:44:39 +0200, Fabian Groffen wrote: |
| 3 |
>> On 30-10-2010 16:39:01 +0200, Justin (jlec) Lecher wrote: |
| 4 |
>>> So if I "re"bootstrap portage I can emerge portage as normal only |
| 5 |
>>> "Error during set creation: Could not import |
| 6 |
>>> 'portage.sets.security.NewAffectedSet' for section 'security'" |
| 7 |
>>> appears. But once I emerge portage again it is broken. What is going on? |
| 8 |
>>> Any change in the recent ebuilds? |
| 9 |
>> |
| 10 |
>> Well, sort of yeah. Most probably your bootstrap portage is 15333, |
| 11 |
>> while the portage you emerge is 17133 or something. |
| 12 |
> |
| 13 |
> ok, I will commit that 17133 now, since it is the equivalent of |
| 14 |
> 2.2.0_alpha2 |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
ld is segfaulting when emerging portage. This leads to a problem in |
| 19 |
prerm and postrm phase, which makes portage unusable. |
Archives