Arch Linux User Repository

@jongeduard It looks like your zenpower3-0.2.0.tar.gz is from the old GitHub upstream and not a copy downloaded from the new upstream. The two zenpower3-0.2.0.tar.gzs are different but have the same name, which I think is causing the validation problems.

Perhaps I should have just kept the pkgrel the same when updating the upstream URL, since it wasn't a change that needed a rebuild, but it might be too late to do that now.

Edit: I changed the pkgrel back to 1, maybe that fixes things, maybe that just makes it worse...

Same issue here!

And not only that: I permanently maintain copies inside my home folder of everything I install AUR, and normally I can always simply "git pull" to update anything before I run my "makepkg -csi" - which I have both automated using a self-written script, but this time I got the error from git that I have made local changes, while I am certain that this is not the case.

I needed a "git reset --hard" to solve the issue.

Sadly after that I got this validation problem as well.

So clearly there is something wrong.

Update: I have manually checked things myself now:

The PKGBUILD mentions 2 files and 2 checksums:

source=("$_pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz" "$_pkgname.conf")

sha256sums=('6c48f7e07d13658f357a02005da1689cb6935fac34e21a4bf5b7483c7d0c4476' '7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a')

But when I manually check the sums of the files which I have:

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] % sha256sum zenpower3-0.2.0.tar.gz

b206c1dfd8ea742a802126d012404d31ae62f2a23ae4723ea1c0f9f54581f6a3 zenpower3-0.2.0.tar.gz

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] % sha256sum zenpower3.conf
7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a zenpower3.conf

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] %
7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a zenpower3.conf

Extra info: My zenpower3-0.2.0.tar.gz is still from 2022-01-06, whhich is the same version as the one mentioned here

My guess: You forgot to update the version number while making changes, so the new one is not going to be downloaded?

Huh, I don't get a validity check error when building this package in a clean environment, so I think those errors might be caused by your AUR helper. Upstream (AKA me) changed URLs so the tar.gz has changed, but it still has the same name so it might be confusing your AUR helper.

Still getting a validity check error on 0.2.0-3

Is anyone still experiencing the validity check error? It should be fixed now with version 0.2.0-3.

@martinje same here

I switched to zenpower3-dkms-git which is working for me.

getting the following error on this last update; [code] ==> Retrieving sources... -> Found zenpower3-0.2.0.tar.gz -> Found zenpower3.conf ==> Validating source files with sha256sums... zenpower3-0.2.0.tar.gz ... FAILED zenpower3.conf ... Passed ==> ERROR: One or more files did not pass the validity check! [code]

This package is meant to be used with zenmonitor3 and zenmonitor3-git which require zenpower3, not zenpower.

Shouldn't this provide zenpower instead of zenpower3? The way it is you cannot build zenmonitor and others as they fail.

If you modify the dependency of zenmonitor to zenpower3 it compiles and operates correctly