That overlay hasn't been manifested properly, the checksums and file sizes don't match. You have two options:
redigest every ebuild in the entire overlay resync and hope it's fixed (maybe report a bug) Just to confirm, this is vapier's overlay you are using? Not niifaq? I recall manifest problems with niifaq overlay a while ago, but can't recall issues with vapier's. It isn't the portage tree though, so I imagine it can be easy to forget the manifest step when committing files. What I can't explain is why one pc is happy using the overlay files and the other not. AFAIK portage doesn't allow digest checks to be disabled. On 01/09/2013 18:41, Mick wrote: > On Sunday 01 Sep 2013 15:45:05 Alan McKinnon wrote: > >> What's the contents of the Manifest file in those two directories? >> What does "ls -al" say ebuild the supposedly faulty ebuilds? >> >> I also note the error reported in both cases is exactly 6 bytes. >> Might be significant, let's keep that in mind > > Thanks Alan, it's not just these two ebuilds digests that come up with > errors. > I attach the complete error. I compared the corresponding Manifests between > the two PCs and there no differences. For example: > > Good PC: > ======= > # sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules- > forecasts/Manifest > d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11- > plugins/e_modules-forecasts/Manifest > > > Bad PC: > ====== > $ sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules- > forecasts/Manifest > d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11- > plugins/e_modules-forecasts/Manifest > > > Similarly, there's no difference between the checksums of the ebuilds in the > two PCs. > > > Here is the content of the e_modules-forecasts Manifest: > ======================================================= > $ cat /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/Manifest > EBUILD e_modules-forecasts-9999.ebuild 436 SHA256 > 66c7fd87b666ec5b29e3756b36ed3fcd3140c267a02757fe29997e912ad8fc05 SHA512 > 952910877f0cc2f36fb9980822b3088652c4f813de6ed1fa584fa9c9737c832000a5e7ffdce00bc9c255cf1663cc0efd76ec6910ba504e515303be44b9d792bc > > WHIRLPOOL > 8f7ba88d7658257d6cf9a9655a7152ed7bf6b126dade35a3f6304451bd2f16621e36298ac10b8c8420259dfae14e28289ba20bbec84373c25ed5f538df5bc8f1 > MISC ChangeLog 225 SHA256 > e4290d34b0e8936f485adee22ec8e596fdeff60ed041c03f0a6925bcdc973c2f SHA512 > 48819cea3e04612f94feeb8511cc79a583e777fa1de438ca287f8f8289301537b4ff4df5c1fe96d8edd6a10bc1f0a0dd76020e30b4e2210ff5e119239ce33664 > > WHIRLPOOL > 41478a52980a23476d21eec41a32d77dada0ced86b7baadd59bc8db9adbf06ae3c7d38b55516dec57a60a4ad67bae9d2d3aae6066f6ad6589b34ee6499420b52 > MISC metadata.xml 228 SHA256 > 42ea435327140212f3beb05aafebad5053cbad84532f9bb78987de8540c6459a SHA512 > 5b1191ceaa7bcaa10b4b28d5b80cbb214da3e5857c2897f7b8001d3ac7ef3491c2dbb8a51583677c79770c106368297c16698d7a10b5ba85ce211412a61ae8bd > > WHIRLPOOL > ed7fa6aacaa62a04fd1d184fc7a86eff8bd65a29664dca293f6723db14d1b8c22e5707cb0c1a0c7405cf2da2e0af1c031f7c9406fda5dfe74df3421b47b1cbf3 > ======================================================= > > > On the good PC I am able to emerge tclock: > ========================================= > # emerge -1aDv x11-plugins/e_modules-tclock > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N *] x11-plugins/e_modules-tclock-9999::enlightenment USE="nls - > doc" 0 kB > > Total: 1 package (1 new), Size of downloads: 0 kB > > The following keyword changes are necessary to proceed: > (see "package.accept_keywords" in the portage(5) man page for more details) > # required by x11-plugins/e_modules-tclock (argument) > =x11-plugins/e_modules-tclock-9999 ** > > NOTE: The --autounmask-keep-masks option will prevent emerge > from creating package.unmask or ** keyword changes. > > Use --autounmask-write to write changes to config files (honoring > CONFIG_PROTECT). Carefully examine the list of proposed changes, > paying special attention to mask or keyword changes that may expose > experimental or unstable packages. > ========================================= > > > On the bad PC it complaints of corrupt files: > ============================================ > # emerge -1aDv x11-plugins/e_modules-tclock > > These are the packages that would be merged, in order: > > Calculating dependencies \ * Digest verification failed: > * /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock/e_modules- > tclock-9999.ebuild > * Reason: Filesize does not match recorded size > * Got: 385 > * Expected: 379 > > ... done! > > !!! All ebuilds that could satisfy "x11-plugins/e_modules-tclock" have been > masked. > !!! One of the following masked packages is required to complete your request: > - x11-plugins/e_modules-tclock-9999::enlightenment (masked by: corruption) > > For more information, see the MASKED PACKAGES section in the emerge > man page or refer to the Gentoo Handbook. > ============================================ > > The content of two overlay package directories listed here as an example, > from > the bad PC: > > # ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock > total 24 > drwxr-xr-x 2 root root 4096 Sep 1 17:33 . > drwxr-xr-x 39 root root 4096 Sep 1 17:33 .. > -rw-r--r-- 1 root root 219 Sep 1 17:33 ChangeLog > -rw-r--r-- 1 root root 1487 Sep 1 17:33 Manifest > -rw-r--r-- 1 root root 385 Sep 1 17:33 e_modules-tclock-9999.ebuild > -rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml > > # ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/total > 24 > drwxr-xr-x 2 root root 4096 Sep 1 17:33 . > drwxr-xr-x 39 root root 4096 Sep 1 17:33 .. > -rw-r--r-- 1 root root 225 Sep 1 17:33 ChangeLog > -rw-r--r-- 1 root root 1490 Sep 1 17:33 Manifest > -rw-r--r-- 1 root root 442 Sep 1 17:33 e_modules-forecasts-9999.ebuild > -rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml > > > I am completely confused with this. :-/ > -- Alan McKinnon Systems Engineer^W Technician Infrastructure Services Internet Solutions +27 11 575 7585 -- Alan McKinnon [email protected]
