| 1 |
On Wednesday 06 February 2008, James wrote: |
| 2 |
> Hello |
| 3 |
> |
| 4 |
> I just 'emerge --sync' as system, then proceeded to start a normal |
| 5 |
> update. |
| 6 |
> |
| 7 |
> I get this error: |
| 8 |
> |
| 9 |
> Verifying ebuild Manifests... |
| 10 |
> |
| 11 |
> !!! A file listed in the Manifest could not be found: |
| 12 |
> /usr/portage/sys-apps/busybox/busybox-1.4.1-r2.ebuild |
| 13 |
|
| 14 |
It's a bug. The Manifest lists files that are no longer there. You can |
| 15 |
ignore it as the referenced file doesn't exist anymore so can't be |
| 16 |
emerged. |
| 17 |
|
| 18 |
Or you could report a bug at b.g.o., but make sure it isn't there |
| 19 |
already so you create a dupe or you will suffer the wrath of jakub |
| 20 |
|
| 21 |
Or you could |
| 22 |
run 'ebuild /usr/portage/sys-apps/busybox/busybox-<valid-version> |
| 23 |
manifest' to regenerate a Manifest yourself. |
| 24 |
|
| 25 |
Or you could just wait till the next sync when the busybox dev fixes it |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Alan McKinnon |
| 30 |
alan dot mckinnon at gmail dot com |
| 31 |
-- |
| 32 |
gentoo-user@l.g.o mailing list |
Archives