#63997 closed defect (fixed)
xrootd 5.3.3 checksum mismatch (Big Sur, 11.6.1)
Reported by: | mtetcs | Owned by: | Chris Jones <jonesc@…> |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | jonesc@…, mascguy (Christopher Nielsen) | |
Port: | xrootd |
Description (last modified by mtetcs)
xrootd 5.3.3 does not install from the usual sudo port selfupdate;sudo port upgrade outdated procedure. sudo port clean xrootd does not remove the issue.
The port details page https://ports.macports.org/port/xrootd/details/ shows port health for all versions with a Red Cross.
Error: Checksum (rmd160) mismatch for xrootd-5.3.3.tar.gz Error: Checksum (sha256) mismatch for xrootd-5.3.3.tar.gz Error: Checksum (size) mismatch for xrootd-5.3.3.tar.gz Error: Failed to checksum xrootd: Unable to verify file checksums
Previous xrootd version installed and working fine.
macbook:~ $ port installed | grep xrootd root6 @6.24.06_1+cocoa+davix+gcc10+graphviz+gsl+opengl+python39+roofit+tmva+xml+xrootd (active) xrootd @5.3.2_1+kerberos+python39+readline+ssl (active)
Attachments (1)
Change History (12)
Changed 3 years ago by mtetcs
comment:1 Changed 3 years ago by mtetcs
Description: | modified (diff) |
---|
comment:2 Changed 3 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:3 follow-up: 10 Changed 3 years ago by cjones051073 (Chris Jones)
Odd, works just fine for me. Please try this
Oberon ~/Projects/MacPorts/ports > sudo port clean --all xrootd ---> Cleaning xrootd Oberon ~/Projects/MacPorts/ports > sudo port -v checksum xrootd ---> Fetching distfiles for xrootd ---> xrootd-5.3.3.tar.gz does not exist in /opt/local/var/macports/distfiles/xrootd ---> Attempting to fetch xrootd-5.3.3.tar.gz from https://distfiles.macports.org/xrootd % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2849k 100 2849k 0 0 3617k 0 --:--:-- --:--:-- --:--:-- 3625k ---> Verifying checksums for xrootd ---> Checksumming xrootd-5.3.3.tar.gz
comment:4 Changed 3 years ago by mtetcs
Curious... I first saw this on a colleague's M1 MacBook Pro earlier today, and I subsequently saw the same issue. I'll try this again on a different connection.
The FAQ first aid suggestions didn't help when I tried them.
macbook:~ $ sudo port clean --all xrootd ---> Cleaning xrootd macbook:~ $ sudo port -v checksum xrootd ---> Fetching distfiles for xrootd ---> xrootd-5.3.3.tar.gz does not exist in /opt/local/var/macports/distfiles/xrootd ---> Attempting to fetch xrootd-5.3.3.tar.gz from https://github.com/xrootd/xrootd/tarball/v5.3.3 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 128 100 128 0 0 83 0 0:00:01 0:00:01 --:--:-- 83 100 2849k 0 2849k 0 0 750k 0 --:--:-- 0:00:03 --:--:-- 2254k ---> Verifying checksums for xrootd ---> Checksumming xrootd-5.3.3.tar.gz Error: Checksum (rmd160) mismatch for xrootd-5.3.3.tar.gz Portfile checksum: xrootd-5.3.3.tar.gz rmd160 a14aec908c697fa6158d788c17c5b8e02f046971 Distfile checksum: xrootd-5.3.3.tar.gz rmd160 ab63264fea2ed2be97101ffa6a53a6b24b10f6ac Error: Checksum (sha256) mismatch for xrootd-5.3.3.tar.gz Portfile checksum: xrootd-5.3.3.tar.gz sha256 107b11041372ee5f32913548fbba297547a936a012b0f529b7f07a7687b958fd Distfile checksum: xrootd-5.3.3.tar.gz sha256 70dc79721829541134b5d08e87f9c2403fa0ecb7b019f90e34287bb9c8e88428 Error: Checksum (size) mismatch for xrootd-5.3.3.tar.gz Portfile checksum: xrootd-5.3.3.tar.gz size 2918163 Distfile checksum: xrootd-5.3.3.tar.gz size 2918154 The correct checksum line may be: checksums rmd160 ab63264fea2ed2be97101ffa6a53a6b24b10f6ac \ sha256 70dc79721829541134b5d08e87f9c2403fa0ecb7b019f90e34287bb9c8e88428 \ size 2918154 Error: Failed to checksum xrootd: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_xrootd/xrootd/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port xrootd failed macbook:~ $
comment:5 Changed 3 years ago by mtetcs
Changed connection, changed DNS servers, updated command line tools - no change in behaviour.
There is something strange with the Python variants though:
sudo port upgrade xrootd tries to fetch xrootd-5.3.3_0+kerberos+python310+readline+ssl.darwin_20.x86_64.tbz2 even though the current installation is the python39 variant. And looking at the existing installation:
macbook:~ $ port installed | grep xrootd root6 @6.24.06_1+cocoa+davix+gcc10+graphviz+gsl+opengl+python39+roofit+tmva+xml+xrootd (active) xrootd @5.3.2_1+kerberos+python39+readline+ssl (active)
python39 xrootd variant above; dependent on python310:
macbook:~ $ port dependents python310 xrootd depends on python310
comment:6 Changed 3 years ago by cjones051073 (Chris Jones)
OK, it looks like upstream have done a stealth update here....
comment:8 Changed 3 years ago by Chris Jones <jonesc@…>
Owner: | set to Chris Jones <jonesc@…> |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:10 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to cjones051073:
Odd, works just fine for me.
Not odd at all; on the contrary, this is exactly how stealth updates manifest themselves: some users (because they are closer to one of our mirror servers) receive our previously-mirrored file with the "right" checksums, while other users (because they are closer to one of the upstream servers) receive the new file with the different checksums. When a user reports a checksum mismatch that you can't immediately reproduce, your first reaction should not be "works for me"; it should be to check whether the file has the right checksums on every server, to discover a possible stealth update or other reason for the difference.
Replying to mtetcs:
There is something strange with the Python variants though:
sudo port upgrade xrootd tries to fetch xrootd-5.3.3_0+kerberos+python310+readline+ssl.darwin_20.x86_64.tbz2 even though the current installation is the python39 variant.
Not strange at all. New in MacPorts 2.7.0, we now remember which variants you requested and which ones were merely defaults at the time. Prior to MacPorts 2.7.0, any variants that were enabled, regardless of how they were enabled, would be preserved during upgrades. Now, as of 2.7.0, only variants you requested are preserved while defaults which have changed are merged in. xrootd's default python variant changed from +python39 to +python310 8 days ago.
main.log