| 1 |
Zac Medico wrote: |
| 2 |
|
| 3 |
>Karsten Gebbert wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>Hello list, |
| 7 |
>> |
| 8 |
>>The described error, or failure, always occures when building the 59th |
| 9 |
>>app after emerge --newuse --emptytree system: |
| 10 |
>> |
| 11 |
>> |
| 12 |
>> |
| 13 |
>>>sys-apps/baselayout-1.11.12-r4 |
| 14 |
>>> |
| 15 |
>>> |
| 16 |
>>and again: |
| 17 |
>> |
| 18 |
>> |
| 19 |
>> |
| 20 |
>>>!!!Files listed in the manifest do not exist! |
| 21 |
>>>files/digest-baselayout-1.12.0-pre1 |
| 22 |
>>>baselayout-1.12.0_pre1.ebuild |
| 23 |
>>> |
| 24 |
>>> |
| 25 |
>>Why can it not get the sources and build it? Could this be a problem |
| 26 |
>>within make.conf's known mirrors or so? |
| 27 |
>> |
| 28 |
>>KArsten |
| 29 |
>> |
| 30 |
>> |
| 31 |
> |
| 32 |
>Unfortunately our portage tree rsync system does not handle concurrency well which occasionally results in an inconsistent portage snapshot. If you emerge sync again that should fix it. Alteratively, you can use "ebuild <path to ebuild> digest" to correct the inconsistency yourself. See the ebuild(1) manpage for details. |
| 33 |
> |
| 34 |
>Also, maybe you can skip the first 58 packages with "emerge --resume". |
| 35 |
> |
| 36 |
>Zac |
| 37 |
> |
| 38 |
> |
| 39 |
actually, that works fine! after emerge --sync and another emerge |
| 40 |
system, it seemed to have resumed at the respective point. |
| 41 |
|
| 42 |
cheers, |
| 43 |
|
| 44 |
KArsten |
| 45 |
-- |
| 46 |
gentoo-user@g.o mailing list |
Archives