| 1 |
Hi! |
| 2 |
|
| 3 |
On Wednesday 13 July 2005 16:32, Chris Gianelloni wrote: |
| 4 |
> On Wed, 2005-07-13 at 07:52 +0200, "Andreas Rückert" wrote: |
| 5 |
> > Hi! |
| 6 |
> > |
| 7 |
> > I'm stuck again. I guess I tried more than 20 times to run stage 2 |
| 8 |
> > with a current portage snapshot. No luck so far. I tried at least |
| 9 |
> > 5 kernel versions, 2 processor types and lots of spec file variants. |
| 10 |
> |
| 11 |
> livecd-stage2, right? |
| 12 |
|
| 13 |
Yup! |
| 14 |
|
| 15 |
> File a bug against genkernel. |
| 16 |
|
| 17 |
Ok, but let me complete the current building process, so I'm sure, that it's |
| 18 |
not my seed stage, that is causing the problem. |
| 19 |
|
| 20 |
> It seems to be working fine for us on the release building, however. |
| 21 |
> Perhaps there is something in your spec file causing this issue? |
| 22 |
> |
| 23 |
> Also, try upgrading to genkernel 3.2.2 first. |
| 24 |
|
| 25 |
That's my next step. Updating catalyst and genkernel, then rebuilding all the |
| 26 |
stages and if it doesn't work, file a bug. |
| 27 |
|
| 28 |
The problem is just, that the release cycles of genkernel and catalyst have |
| 29 |
become so short, that my build processes takes longer. So when my catalyst |
| 30 |
calls are completed and I get an error message in livecd-stage2, there's |
| 31 |
already a new release to try... :-) |
| 32 |
Maybe I should invest in something like a 4-way Opteron, so I could keep up |
| 33 |
with your pace... :-) |
| 34 |
|
| 35 |
Ciao, |
| 36 |
Andreas |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-catalyst@g.o mailing list |
Archives