Arch Linux User Repository

smartgit has a missing dependency on "which": The smartgit.sh startup script uses it when locating java. Without which installed, smartgit will not launch.

When Pamac asks if you want to edit build files, answer yes and replace b38b7ba2a7fe2e272f32d6f423d953890c6e7840 with 114375a1516ac06e5bb8ef260ceb266ef4019a4e (the manually calculated SHA provided by sez11a) and then save. By doing this, the installation worked fine (on Manjaro).

If you have problems with SHA1 checks, try removing the .tar.gz archive you downloaded from Syntevo and use the latest PKGBUILD.

I'm having the same problem. When I calculate the sha1sum value manually, it's not the value you posted; it's 114375a1516ac06e5bb8ef260ceb266ef4019a4e.

@cedricroijakkers: I don't understand you have this problem. I just upgradeded yesterday to "aur/smartgit 21.1.2-2 (+178 1.78) (Installed)" with no problems. Today, after reading you had problems I went to https://www.syntevo.com/downloads/smartgit/smartgit-linux-21_1_2.tar.gz and calculated the SHA1-value of the .gz-file. It is "b38b7ba2a7fe2e272f32d6f423d953890c6e7840" just as in the pkgbuild. So I don't understand it, if you have problems?

Looks like you have a checksum error in the latest version:

==> ERROR: One or more files did not pass the validity check! error: failed to download sources for 'smartgit-21.1.2-2': error: packages failed to build: smartgit-21.1.2-2

@Ovsyanka That's a good idea. An alternative is like the other packages, to create a custom JRE package for SmartGit, which becomes an optional install for SmartGit.

@alyst: Thanks a lot of updating pkgbuild. I don't like messing with sha-values myself and prefer that kind of things are dealt with from the aur-repo, especially because other people should be in the same boat when things like this happen. About the reason for changing sha-values: I hope it doesn't happen too often, sorry I cannot help but thanks for quickly fixing it and hopefully it'll stay working now for a long time.

@ovsyanka: Thanks for the temporary workaround with pkgbuild but luckily I didn't have to do this and things are solved now, from my point of view.

@newsboost I can't figure out that too. Looks like at the time this package was updated smartgit-linux-21_1_2.tar.gz on the site had different hash. And some time later the archive was changed.

Somehow I have 21.1.2-1 installed, but I can't find it's smartgit-linux-21_1_2.tar.gz in my yay cache so I can't prove the case.

I think @alyst (as packager) could verify my assumption and ask Smartgit devs why the hash was changed. If they admit that they changed the archive - then the packager should just update the hash. If they didn't change it then something strange is going on and should be investigated.

All this based on my understanding of the process, I am not specialist, so correct me if I am wrong.

If you want to update before this question will be sorted out you can change the hash for smartgit-linux-21_1_2.tar.gz to actual one "b38b7ba2a7fe2e272f32d6f423d953890c6e7840" in PKGBUILD before installation.

@simonzack About the JRE. In my opinion it would be appropriate to have two packages of smartgit - bundled with JRE and without it.

I always take the SHA1 from Syntevo website, but sometimes they silently update the package (and SHA1) without updating the version number. I've just updated the PKGBUILD to use the most recent .tar.gz.