| 1 |
> On 10-09-2009 10:05:24 +0800, Galaxy wrote: |
| 2 |
>> >> It was once a bug for $ ./bootstrap-prefix.sh $EPREFIX/tmp findutils3 |
| 3 |
>> >> but why this happens in emerge ? |
| 4 |
>> >> |
| 5 |
>> >> I just use ./bootstrap-prefix.sh $EPREFIX findutils3 to bypass it. |
| 6 |
>> |
| 7 |
>> > that feels like a very bad idea to me. |
| 8 |
>> So do I when I emerge -u system and find 4.5.5 works, it just conflict |
| 9 |
>> with the 4 files that from findutils3. I went through by rm them. |
| 10 |
|
| 11 |
> Can you explain why it suddenly works then? Or why you would need a |
| 12 |
> newer version of findutils bootstrapped (as suggested by Michael Yang)? |
| 13 |
> I don't quite understand how the problem goes away because of that. |
| 14 |
|
| 15 |
>> So, just need to emerge --sync before setup findutils. The protage |
| 16 |
>> package need to be updated. |
| 17 |
|
| 18 |
> Yesterday I bumped the snapshot, so it should have 4.5.5 included for a |
| 19 |
> new bootstrap now. Does that solve things? |
| 20 |
|
| 21 |
I just skip 'emerge --oneshot findutils' and run 'emerge --sync' after |
| 22 |
'env FEATURES="-collision-protect" emerge --oneshot portage'. Then I |
| 23 |
tried 'emerge --oneshot findutils' again and it works. |
| 24 |
All things are done under 'screen', so no other changes on `env` should |
| 25 |
happen. |
| 26 |
I am not sure whether I was './bootstrap-prefix.sh $EPREFIX/tmp |
| 27 |
findutils' instead of findutils3. That may be the reason. |
Archives