| 1 |
Martin Vaeth wrote: |
| 2 |
> Neil Bothwick <neil@××××××××××.uk> wrote: |
| 3 |
>> I deleted the busybox directory from the tree then ran emerge --sync. |
| 4 |
>> The error is still there |
| 5 |
> You have the same files that I have. |
| 6 |
> Unfortunately, only now I actually did: |
| 7 |
> |
| 8 |
> $ grep busybox-9999 Manifest |
| 9 |
> EBUILD busybox-9999.ebuild 8580 [...] |
| 10 |
> |
| 11 |
> ??? |
| 12 |
> I have the same wrong size recorded in the Manifest! |
| 13 |
> No idea why portage didn't yell at me - there seems |
| 14 |
> to be another bug involved. |
| 15 |
> |
| 16 |
> So, sorry, my previous conjecture was wrong. |
| 17 |
> |
| 18 |
> The only information which I can give you currently, |
| 19 |
> is that probably all mirrors contain the same broken Manifest |
| 20 |
> in the moment. |
| 21 |
> |
| 22 |
> *Perhaps* (a very wild conjecture!) the reason why this Manifest |
| 23 |
> got not updated is the same bug which caused portage not to yell |
| 24 |
> at me, despite the broken Manifest. |
| 25 |
> |
| 26 |
> As a temporary hack, calling "ebuild manifest" on that file is |
| 27 |
> probably the only reasonable way to proceed, but this problem |
| 28 |
> must be fixed, of course... |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
|
| 33 |
|
| 34 |
Wasn't there a emerge option to ignore the manifest? I seem to recall |
| 35 |
there used to be one but it was a LONG time ago. Of course, if someone |
| 36 |
has tinkered with something that would be a bad thing to do. |
| 37 |
|
| 38 |
Dale |
| 39 |
|
| 40 |
:-) :-) |
Archives