emerge -uD world with a sync from the last couple hours returns: >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/www-client/firefox/metadata.xml !!! Reason: Filesize does not match recorded size !!! Got: 2104 !!! Expected: 2223 I'm guessing it's an issue with mirrors updating, but I tried a couple different mirrors and got the same. I'll try again in an hour or so and see if it fixes itself.
(In reply to N. Andrew Walsh from comment #0) > emerge -uD world with a sync from the last couple hours returns: > > >>> Verifying ebuild manifests > > !!! Digest verification failed: > !!! /usr/portage/www-client/firefox/metadata.xml > !!! Reason: Filesize does not match recorded size > !!! Got: 2104 > !!! Expected: 2223 > > I'm guessing it's an issue with mirrors updating, but I tried a couple > different mirrors and got the same. I'll try again in an hour or so and see > if it fixes itself. Been trying since last night. Same behavior here. I know there are ways around this, but I don't like circumventing security features.
I am observing the same as well since last night. Removing the files and syncing from different mirrors, I get the same error message described above.
Same here. Doing emerge operations on a terminal as root, tried eix-sync at different times of the day and changed mirrors twice. Executing emain --auto sync didn't improve the situation. __________________________________________________ Command: emerge --fetchonly firefox Message: >>> Fetching (1 of 1) www-client/firefox-49.0::gentoo !!! Digest verification failed: !!! /usr/portage/www-client/firefox/metadata.xml !!! Reason: Filesize does not match recorded size !!! Got: 2104 !!! Expected: 2223 __________________________________________________ Emerge --info As attachment due to comment size limit.
Created attachment 449280 [details] emerge info
As soon as I get back to my dev computer I will check and correct this. If any other dev wants to beat me to it please go ahead
*** Bug 596420 has been marked as a duplicate of this bug. ***
This is probably caused by edge cases mentioned in bug 577722 comment 34 and bug 577722 comment 35. Committing anything to www-client/firefox will fix it, but I'm trying to figure out a better solution.
Same mismatch with these ebuilds: Would you like to merge these packages? [Yes/No] yes >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/x11-libs/libX11/libX11-1.6.4.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 1619 !!! Expected: 1620 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXrender/libXrender-0.9.10.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 649 !!! Expected: 650 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXfixes/libXfixes-5.0.3.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 709 !!! Expected: 710 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXrandr/libXrandr-1.5.1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 798 !!! Expected: 799 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXi/libXi-1.7.7.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 973 !!! Expected: 974 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXv/libXv-1.0.11.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 669 !!! Expected: 670 !!! Digest verification failed: !!! /usr/portage/x11-libs/libXtst/libXtst-1.2.3.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 831 !!! Expected: 832 !!! Digest verification failed: !!! /usr/portage/www-client/firefox/metadata.xml !!! Reason: Filesize does not match recorded size !!! Got: 2104 !!! Expected: 2223 !!! Digest verification failed: !!! /usr/portage/net-wireless/wpa_supplicant/wpa_supplicant-2.6.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 10295 !!! Expected: 10296
I have got mozilla overlay to solve the problem, so that I can update my system now to solve some problems.
same problem after sync, mozilla overlay resolves firefox's problem though it's not the best method, but how to handle the other..
(In reply to rtgiskard from comment #10) > same problem after sync, mozilla overlay resolves firefox's problem though > it's not the best method, but how to handle the other.. It looks like configuring Portage to use git backend instead of rsync completely bypasses this problem. Edit /etc/portage/repos.conf/gentoo.conf : [DEFAULT] main-repo = gentoo [gentoo] location = /usr/portage sync-type = git sync-uri = https://github.com/gentoo-mirror/gentoo Then: mv /usr/portage{,.old} emerge --sync mv /usr/portage.old/distfiles /usr/portage/ mv /usr/portage.old/packages /usr/portage/ ...and continue with the rest of your upgrade. Delete /usr/portage.old when you're satisfied you'll never want to go back to rsync again (probably immediately after you see how nice syncs are with git).
Simple solution: I run emerge --sync; find /usr/portage/ -iname '.ebuild' -exec ebuild {} digest \; #Thanks Thumper This rebuilds updates all Manifests. Then run my usual upgrade command: emerge --update --deep --with-bdeps=y --newuse --backtrack=300 --changed-deps=y --keep-going=y @world -va
(In reply to Elmar Haag from comment #12) > Simple solution: > > I run emerge --sync; > find /usr/portage/ -iname '.ebuild' -exec ebuild {} digest \; > #Thanks Thumper > > This rebuilds updates all Manifests. > > Then run my usual upgrade command: > emerge --update --deep --with-bdeps=y --newuse --backtrack=300 > --changed-deps=y --keep-going=y @world -va FYI, a simpler solution is to run 'emerge --regen' and then -uDN as normal. There have been a couple of commits to www-client/firefox since this bug was triggered, so there shouldn't be a manifest/metadata issue anymore. I'm going to close this bug and let dwfreed continue to work on the originating issue from the other bug he mentioned.
(In reply to Brent Busby from comment #11) > It looks like configuring Portage to use git backend instead of rsync > completely bypasses this problem. Edit /etc/portage/repos.conf/gentoo.conf : > > ...and continue with the rest of your upgrade. Delete /usr/portage.old when > you're satisfied you'll never want to go back to rsync again (probably > immediately after you see how nice syncs are with git). What are pros/cons of rsync vs git except using git means extra 200MB in /usr/portage/.git/?
