On two different almost identical machines one application fails in upgrade and one doesn't? One shows checksum error?

General system Newbie
1

Totally confused by this. Two almost identical systems. when running yay, an app called system-monitoring-center tries to upgrade to version 2.6.0-3, works fine on one and not on the other. The error I’m getting on the fail is:

:: 1 Packages to upgrade.
1 aur/system-monitoring-center 2.5.0-1 → 2.6.0-3
==> Packages to exclude: (eg: “1 2 3”, “1-3”, “^4” or repo name)
==>
:: Checking for conflicts…
:: Checking for inner conflicts…
[Aur:1] system-monitoring-center-2.6.0-3

1 system-monitoring-center (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: PKGBUILD up to date, Skipping (1/0): system-monitoring-center
1 system-monitoring-center (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: (1/1) Parsing SRCINFO: system-monitoring-center
==> Making package: system-monitoring-center 2.6.0-3 (Wed 01 Feb 2023 10:02:20 AM CST)
==> Retrieving sources…
→ Found system-monitoring-center-2.6.0.tar.gz
==> Validating source files with sha256sums…
system-monitoring-center-2.6.0.tar.gz … FAILED
==> ERROR: One or more files did not pass the validity check!
→ error downloading sources: system-monitoring-center
context: exit status 1

==> Making package: system-monitoring-center 2.6.0-3 (Wed 01 Feb 2023 10:02:20 AM CST)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
→ Found system-monitoring-center-2.6.0.tar.gz
==> Validating source files with sha256sums…
system-monitoring-center-2.6.0.tar.gz … FAILED
==> ERROR: One or more files did not pass the validity check!
→ error making: system-monitoring-center
[mark@mark-optiplex9020 ~]$

I understand what the checksum fail means, but how could it fail on one machine and not the other?

Any thoughts? Thanks in advance.

2

The difference is probably just timing.

It looks like there was a GitHub issue that changed checksums so the maintainer updated the checksums and then GitHub reverted the change.

See here for more info

1 Like
3

That explains why one of my package updates was failing! (one of Piotr’s nwg packages for sway).

4

I attempted the updates this morning, literally within a couple of minutes of each other. It has me wondering if the two machines might have been using different mirrors, and maybe the changes hadn’t propagated through all the mirrors yet in a synchronized way.

5

Really weird. I just tried the ‘yay’ upgrade, failed as before. Just on a wild shot, used ‘paru’ and it went right through!

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.