List Archive: gentoo-scm
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Friday 20 February 2009, Robin H. Johnson wrote:
> Remember that Portage will only verify hashes that exist in the file.
> If they aren't in the file, they don't get verified. The fix you
> describe is unneeded.
If you use FEATURES=-digest, Portage refuses to build when there are
files missing in the Manifest:
# cat /usr/portage/media-libs/libpng/Manifest
DIST libpng-1.2.33.tar.lzma 513430 RMD160
DIST libpng-1.2.34.tar.lzma 514210 RMD160
# emerge libpng
Calculating dependencies... done!
>>> Verifying ebuild manifests
!!! A file is not listed in the
If you use FEATURES=digest, Portage ignores missing lines or errors in
the Manifest completely. So either overlays must ship full Manifests or
Portage would need a feature to fix slim Manifests.
However, this opens a bit of a conflict:
On the one hand, you want to recreate broken Manifests on as few file
trees as possible, since this will shadow errors or manipulation, on
the other hand you need to recreate it for overlays that are missing
This could be solved by adding a file to each tree that states whether
it comes with slim or full Manifests and whether regeneration is needed
or not. In case of signed trees, this file must be signed as well.
Repoman could even check the existence of that file and add or remove
Manifest entries based on that so you could use this tool to work on
new-style Manifest git repositories and old-style Manifest svn
 Just think you have a signed tree, but someone managed to sneak in a
bash-4.0.ebuild and Portage just ignores the missing signed Manifest.
signature.asc (This is a digitally signed message part.)