Package Details: gosign 2.4.3-1

Git Clone URL: https://aur.archlinux.org/gosign.git (read-only, click to copy)
Package Base: gosign
Description: Nuovo tool di firma e rinnovo online per i certificati digitali emessi da InfoCert
Upstream URL: https://www.firma.infocert.it
Keywords: digital signature
Licenses: custom
Submitter: neuromante
Maintainer: snack
Last Packager: snack
Votes: 1
Popularity: 0.001206
First Submitted: 2022-02-23 10:04 (UTC)
Last Updated: 2025-12-26 08:06 (UTC)

Pinned Comments

snack commented on 2025-11-27 07:36 (UTC)

The installer file is provided with no versioning in its name, so it is the same for all versions. For this reason you might need to manually delete it from your machine before updating the package, otherwise makepkg will use the existing one but the checksum will fail.

Also, when the package is out-of-date you will get a checksum error since the installer for the new version will be downloaded but the SHA sum for the old version will be checked. In this case please flag the package out-of-date.

Latest Comments

1 2 3 4 Next › Last »

simona commented on 2025-12-26 12:04 (UTC)

solved. tnx.

snack commented on 2025-12-26 09:03 (UTC)

@Ranius It works for me. The 2.4.3-1 PKGBUILD has a working, updated checksum, maybe you have a previous installer file in your build/cache folder? If yes then please remove it and try again from scratch (and also take a look at the pinned comment if you still didn't).

Ranius commented on 2025-12-26 08:57 (UTC)

The sha512 checksum in PKGBUILD does not match the current GoSign-Desktop-installer-linux.deb provided upstream.

The .deb seems to have been updated without a versioned filename. Rebuilding requires updating sha512sums with updpkgsums.

Please update the checksums.

snack commented on 2025-12-26 08:07 (UTC)

@simona Package updated, thanks for the heads-up and please check the pinned comment if you still have checksum errors.

simona commented on 2025-12-25 18:45 (UTC)

fail checksum

nevernow commented on 2025-12-01 10:19 (UTC)

@snack thanks! It's a pity they don't use a proper naming standard.

snack commented on 2025-11-27 07:36 (UTC)

The installer file is provided with no versioning in its name, so it is the same for all versions. For this reason you might need to manually delete it from your machine before updating the package, otherwise makepkg will use the existing one but the checksum will fail.

Also, when the package is out-of-date you will get a checksum error since the installer for the new version will be downloaded but the SHA sum for the old version will be checked. In this case please flag the package out-of-date.

snack commented on 2025-11-27 07:30 (UTC)

@nevernow The package was out-of-date, and since the installer file has no versioning in the name the outdated PKGBUILD was downloading it for 2.4.2 while still applying the checksum for 2.4.1. I bumped the PKGBUILD so now it should work, thanks for the report.

nevernow commented on 2025-11-26 21:28 (UTC) (edited on 2025-11-26 21:30 (UTC) by nevernow)

Source was updated to 2.4.2. sha512:

99411bd14328328e976cf20d310db718f33127adabbc5930d2cc09ebff6b1f92cf16043acbad1a4b3c550bb5cbd5717cc03f50a125c81a6d06c7dc12f764aa20

snack commented on 2025-05-06 16:00 (UTC)

@leo72 In my system the current libxml2 2.14.2-2 ships libxml2.so.16 while the gosign executable tries to load libxml2.so.2. This caused the program window to remain blank at startup. Installing libxml2-legacy fixed the problem since it ships libxml2.so.2, so I pushed revision 2 with this new dependency. I have been able to successfully build and run the package on my system, so I'd need more info about the error you got.

1 2 3 4 Next › Last »