Arch Linux User Repository

I've added the pkgver + pkgrel to the download filename. Please be advised that file hashes are used not only for version control but also to make sure the file integrity and origin. Also it's a way for the mantainers to check if packaging changes are required between versions.

@a36233, thank you for your work on this package, it's very useful.

The validity issue is not AUR helper related. The sha512sum for the original file changes when they publish a new version, which makes the file to be different, even if the file name remains the same. So the sha512sum hash needs to be changed in the PKGBUILD file. It's easy to do it manually for most of us, but I believe we can all agree that it's a more polished job if the PKGBUILD file is updated accordingly, when there are changes.

@a36233 First of all, thank you very much for this package. Secondly, most users will (understandably) use a AUR helper to manage packages for them, expecting everyone to perform a clean git clone + makepkg + pacman installation is unrealistic and detrimental for new adopters/newbies.

Most of the AUR helpers implement caching which will keep the git repository around across builds/installations which will keep any downloaded files (like the .deb which this package depends on). There is a permanent solution for this, however, but you'll need to make some changes for us. As per my previous comment:

The deb package this AUR package is based on changes upstream every time the AMA releases a new version and the AUR package maintainer has to update the validity hashes for it. If you don't run a clean build, the older .deb file is preserved and the new hash is validating the older file, thus failing.

The way to solve this permanently for all users is for the maintainer to force a re-download of the .deb file every time the validity hash changes. This can be achieved by aliasing the downloaded file with a name that depends on the pkgver or similar: https://forum.manjaro.org/t/how-can-i-always-download-new-build-assets-on-package-update/115421/5

Updated to 2.0.97 SD

Those errors seem to be AUR helper related, use the AUR / ArchLinux recommended method ... git clone + makepkg + pacman -U

Those errors seem to be AUR helper related, use the AUR / ArchLinux recommended method ... git clone + makepkg + pacman -U

==> Validating source files with sha512sums...
    plugin-autenticacao-gov-pt.install ... Passed
    plugin-autenticacao-gov.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

@tomaspinho My AUR helper doesn't ask anything, I use aptpac upgrade. That link gives Oops! That page doesn’t exist or is private. After deleting the package from .cache/paru/clone/ it worked!

@gabber just make sure to run a "clean build" when your AUR helper asks you how to install.

The deb package this AUR package is based on changes upstream every time the AMA releases a new version and the AUR package maintainer has to update the validity hashes for it. If you don't run a clean build, the older .deb file is preserved and the new hash is validating the older file, thus failing.

The way to solve this permanently for all users is for the maintainer to force a re-download of the .deb file every time the validity hash changes. This can be achieved by aliasing the downloaded file with a name that depends on the pkgver or similar: https://forum.manjaro.org/t/how-can-i-always-download-new-build-assets-on-package-update/115421/5

Same error that @stunts @luisnabais @a36233 what is supposed to do with git clean -dfffx && git pull? I didn't install it with git