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