Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
emerge --sync verification failed then OK. Worry?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
GreenNeonWhale
n00b
n00b


Joined: 30 Mar 2016
Posts: 35

PostPosted: Tue Dec 17, 2019 9:35 am    Post subject: emerge --sync verification failed then OK. Worry? Reply with quote

To put this as shortly as possible. I just did an emerge --sync on my box. It went to the Indiana University rsync mirror, rsync25.us.gentoo.org, and synced. I know it was this mirror as they have very nice ASCII art at the beginning. The sync then failed with this message:
Code:

sent 532.39K bytes  received 37.60M bytes  128.18K bytes/sec
total size is 218.24M  speedup is 5.72
 * Manifest timestamp: 2019-12-17 06:08:46 UTC
 * Valid OpenPGP signature found:
 * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
 * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
 * - timestamp: 2019-12-17 06:08:46 UTC
 * Verifying /usr/portage/.tmp-unverified-download-quarantine ...!!! Manifest verification failed:
Manifest mismatch for metadata/news/Manifest
  BLAKE2B: expected: 32a94d7a13f76f4f57853861b139f0009354bf892db1e5f3e51dcb4ef1688cbbd5c68ea90545807edc99032ebcef21aacd50863bc5161927337a42c5ed04e4c6, have: 54b46cb24ea3e3b36cf1dac79ad63b2fd8ff7d53a48fd6e3db284913fba4836166f917b2c1ee1709323b1e4d0862f9580e7bf1f8fbe5395190da09b7ea91ac4b
  SHA512: expected: 3cab439fab2500bf0f8e8a9540230efbce2c441133d1d1b361d3bcba64d9d6e5f14bb1df324955b882ccf46d4bdbbbb278905515b64e33ccd46d4639cb226c1d, have: 202b5c8b93cc950e9d6ec710ee4b544cd7766988681c6c6ddfae8743893d137cc287670ee5f69ab51990cace0e30308c3011864dc82e77d90debdee28f8021f2

Action: sync for repo: gentoo, returned code = 1


I then went into /etc/portage/repos.conf/gentoo.conf and set the mirror to Georgia Tech - rsync3.us.gentoo.org, and did another emerge sync, this completed just fine. Subsequent gemato verify /usr/portage checked out OK too.

To check the mirror, I restored /usr/portage back to what is was before the sync, (while keeping the sync I got from Georgia's rysnc mirror), set gentoo.conf to go explicitly to Indiana's rsync mirror, and did an emerge --sync again. This time it emerged just fine. Subsequent gemato verify on both this new copy of portage, and the one I got from Georgia's mirror, checked out OK too.

I did a diff on the two portage copies, and there were a few differences: (portage is the Indiana copy, portage_OK_georgia is the Georgia copy)
Code:

Only in portage/app-emulation/bochs: bochs-2.6.10.ebuild
Files portage/app-emulation/bochs/Manifest and portage_OK_georgia/app-emulation/bochs/Manifest differ
Files portage/app-emulation/Manifest.gz and portage_OK_georgia/app-emulation/Manifest.gz differ
Only in portage_OK_georgia/dev-python/hypothesis: hypothesis-4.53.2.ebuild
Only in portage_OK_georgia/dev-python/hypothesis: hypothesis-4.54.0.ebuild
Only in portage/dev-python/hypothesis: hypothesis-4.55.1.ebuild
Files portage/dev-python/hypothesis/Manifest and portage_OK_georgia/dev-python/hypothesis/Manifest differ
Files portage/dev-python/Manifest.gz and portage_OK_georgia/dev-python/Manifest.gz differ
Files portage/dev-python/olefile/Manifest and portage_OK_georgia/dev-python/olefile/Manifest differ
Files portage/dev-python/olefile/olefile-0.46.ebuild and portage_OK_georgia/dev-python/olefile/olefile-0.46.ebuild differ
Files portage/dev-python/pillow/Manifest and portage_OK_georgia/dev-python/pillow/Manifest differ
Files portage/dev-python/pillow/pillow-6.2.1.ebuild and portage_OK_georgia/dev-python/pillow/pillow-6.2.1.ebuild differ
Files portage/dev-python/pluggy/Manifest and portage_OK_georgia/dev-python/pluggy/Manifest differ
Files portage/dev-python/pluggy/pluggy-0.11.0.ebuild and portage_OK_georgia/dev-python/pluggy/pluggy-0.11.0.ebuild differ
Files portage/dev-python/sortedcontainers/Manifest and portage_OK_georgia/dev-python/sortedcontainers/Manifest differ
Only in portage/dev-python/sortedcontainers: sortedcontainers-2.1.0.ebuild
Files portage/dev-python/wcwidth/Manifest and portage_OK_georgia/dev-python/wcwidth/Manifest differ
Files portage/dev-python/wcwidth/wcwidth-0.1.7-r2.ebuild and portage_OK_georgia/dev-python/wcwidth/wcwidth-0.1.7-r2.ebuild differ
Files portage/dev-python/zope-event/Manifest and portage_OK_georgia/dev-python/zope-event/Manifest differ
Files portage/dev-python/zope-event/zope-event-4.4.ebuild and portage_OK_georgia/dev-python/zope-event/zope-event-4.4.ebuild differ
Files portage/dev-tcltk/Manifest.gz and portage_OK_georgia/dev-tcltk/Manifest.gz differ
Files portage/dev-tcltk/tclxml/Manifest and portage_OK_georgia/dev-tcltk/tclxml/Manifest differ
Files portage/dev-tcltk/tclxml/tclxml-3.2-r2.ebuild and portage_OK_georgia/dev-tcltk/tclxml/tclxml-3.2-r2.ebuild differ
Files portage/dev-util/Manifest.gz and portage_OK_georgia/dev-util/Manifest.gz differ
Files portage/dev-util/scons/Manifest and portage_OK_georgia/dev-util/scons/Manifest differ
Only in portage/dev-util/scons: scons-3.1.2.ebuild
Files portage/Manifest and portage_OK_georgia/Manifest differ
Files portage/Manifest.files.gz and portage_OK_georgia/Manifest.files.gz differ
Files portage/media-gfx/libimagequant/libimagequant-2.12.2.ebuild and portage_OK_georgia/media-gfx/libimagequant/libimagequant-2.12.2.ebuild differ
Files portage/media-gfx/libimagequant/Manifest and portage_OK_georgia/media-gfx/libimagequant/Manifest differ
Files portage/media-gfx/Manifest.gz and portage_OK_georgia/media-gfx/Manifest.gz differ
Files portage/metadata/dtd/timestamp.chk and portage_OK_georgia/metadata/dtd/timestamp.chk differ
Files portage/metadata/glsa/Manifest and portage_OK_georgia/metadata/glsa/Manifest differ
Files portage/metadata/glsa/timestamp.chk and portage_OK_georgia/metadata/glsa/timestamp.chk differ
Files portage/metadata/Manifest.gz and portage_OK_georgia/metadata/Manifest.gz differ
Only in portage/metadata/md5-cache/app-emulation: bochs-2.6.10
Files portage/metadata/md5-cache/app-emulation/Manifest.gz and portage_OK_georgia/metadata/md5-cache/app-emulation/Manifest.gz differ
Only in portage_OK_georgia/metadata/md5-cache/dev-python: hypothesis-4.53.2
Only in portage_OK_georgia/metadata/md5-cache/dev-python: hypothesis-4.54.0
Only in portage/metadata/md5-cache/dev-python: hypothesis-4.55.1
Files portage/metadata/md5-cache/dev-python/Manifest.gz and portage_OK_georgia/metadata/md5-cache/dev-python/Manifest.gz differ
Files portage/metadata/md5-cache/dev-python/olefile-0.46 and portage_OK_georgia/metadata/md5-cache/dev-python/olefile-0.46 differ
Files portage/metadata/md5-cache/dev-python/pillow-6.2.1 and portage_OK_georgia/metadata/md5-cache/dev-python/pillow-6.2.1 differ
Files portage/metadata/md5-cache/dev-python/pluggy-0.11.0 and portage_OK_georgia/metadata/md5-cache/dev-python/pluggy-0.11.0 differ
Only in portage/metadata/md5-cache/dev-python: sortedcontainers-2.1.0
Files portage/metadata/md5-cache/dev-python/wcwidth-0.1.7-r2 and portage_OK_georgia/metadata/md5-cache/dev-python/wcwidth-0.1.7-r2 differ
Files portage/metadata/md5-cache/dev-python/zope-event-4.4 and portage_OK_georgia/metadata/md5-cache/dev-python/zope-event-4.4 differ
Files portage/metadata/md5-cache/dev-tcltk/Manifest.gz and portage_OK_georgia/metadata/md5-cache/dev-tcltk/Manifest.gz differ
Files portage/metadata/md5-cache/dev-tcltk/tclxml-3.2-r2 and portage_OK_georgia/metadata/md5-cache/dev-tcltk/tclxml-3.2-r2 differ
Files portage/metadata/md5-cache/dev-util/Manifest.gz and portage_OK_georgia/metadata/md5-cache/dev-util/Manifest.gz differ
Only in portage/metadata/md5-cache/dev-util: scons-3.1.2
Files portage/metadata/md5-cache/Manifest.gz and portage_OK_georgia/metadata/md5-cache/Manifest.gz differ
Files portage/metadata/md5-cache/media-gfx/libimagequant-2.12.2 and portage_OK_georgia/metadata/md5-cache/media-gfx/libimagequant-2.12.2 differ
Files portage/metadata/md5-cache/media-gfx/Manifest.gz and portage_OK_georgia/metadata/md5-cache/media-gfx/Manifest.gz differ
Files portage/metadata/md5-cache/sys-apps/Manifest.gz and portage_OK_georgia/metadata/md5-cache/sys-apps/Manifest.gz differ
Only in portage_OK_georgia/metadata/md5-cache/sys-apps: shadow-4.8-r1
Only in portage/metadata/md5-cache/sys-apps: shadow-4.8-r2
Files portage/metadata/news/Manifest and portage_OK_georgia/metadata/news/Manifest differ
Files portage/metadata/news/timestamp.chk and portage_OK_georgia/metadata/news/timestamp.chk differ
Files portage/metadata/timestamp and portage_OK_georgia/metadata/timestamp differ
Files portage/metadata/timestamp.chk and portage_OK_georgia/metadata/timestamp.chk differ
Files portage/metadata/timestamp.commit and portage_OK_georgia/metadata/timestamp.commit differ
Files portage/metadata/timestamp.x and portage_OK_georgia/metadata/timestamp.x differ
Files portage/metadata/xml-schema/timestamp.chk and portage_OK_georgia/metadata/xml-schema/timestamp.chk differ
Files portage/sys-apps/Manifest.gz and portage_OK_georgia/sys-apps/Manifest.gz differ
Files portage/sys-apps/shadow/Manifest and portage_OK_georgia/sys-apps/shadow/Manifest differ
Only in portage_OK_georgia/sys-apps/shadow: shadow-4.8-r1.ebuild
Only in portage/sys-apps/shadow: shadow-4.8-r2.ebuild
Only in portage_OK_georgia: .tmp-unverified-download-quarantine


Currently, I'm figuring that I either got a corrupted file, or the mirror was updating/syncing while I was syncing, or some other issue that is NOT a compromised mirror, and NOT compromised code.
Am I correct that this is not something to worry about?

Thanks to anyone taking the time to read this, and/or reply. :)
Back to top
View user's profile Send private message
Goverp
l33t
l33t


Joined: 07 Mar 2007
Posts: 836

PostPosted: Tue Dec 17, 2019 10:09 am    Post subject: Reply with quote

I am not a lawyer, but
Code:
Files portage/metadata/news/Manifest and portage_OK_georgia/metadata/news/Manifest differ
Files portage/metadata/news/timestamp.chk and portage_OK_georgia/metadata/news/timestamp.chk differ

looks like some news updates were propagating to your mirror (I assume that's "eselect news"stuff) while you were syncing.
No problem.
_________________
Greybeard
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45423
Location: 56N 3W

PostPosted: Tue Dec 17, 2019 10:52 am    Post subject: Reply with quote

GreenNeonWhale,

be afraid ... be very afraid :)

Portage will not let you use a failed sync. .tmp-unverified-download-quarantine will not be merged into your copy of the repo if the gpg check fails.
You did the right thing and portage kept you safe.

The mirrors and your copy of the repo are updated with rsync, which does not do atomic updates for the whole repo.
There is thus a window when you can get part of an old copy of the repo and part of a new one.

This window has got much smaller that it was, with the introduction of the .tmp-unverified-download-quarantine step but it still exists.
Now, its just the copy time from .tmp-unverified-download-quarantine to the main repo, before that it was the entire sync time.

Before tree signing, errors of this nature were detected at emerge time but they wore still detected.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
GreenNeonWhale
n00b
n00b


Joined: 30 Mar 2016
Posts: 35

PostPosted: Tue Dec 17, 2019 5:02 pm    Post subject: Thanks! :) Reply with quote

Thank you Goverp, and NeddySeagoon for the helpful replies. :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum