Package Base Details: tomb

Git Clone URL: https://aur.archlinux.org/tomb.git (read-only)
Submitter: None
Maintainer: parazyd (roddhjav)
Last Packager: roddhjav
Votes: 42
Popularity: 0.501573
First Submitted: 2011-04-15 15:20
Last Updated: 2019-10-13 12:31

Packages (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

TrialnError commented on 2015-04-17 18:33

@anderraso: Did you import the gpg key?

anderraso commented on 2015-03-02 08:11

It shows a GPG error:

==> Verificando las firmas de las fuentes con gpg...
Tomb-2.0.1.tar.gz ... HA FALLADO (clave pública desconocida 73B35DA54ACB7D10)
==> ERROR: ¡Una o más firmas PGP no pudieron ser verificadas!
==> ERROR: Makepkg no ha podido compilar tomb.

richli commented on 2015-02-03 16:53

@alexei: looks like they've finally added Tomb 2.0.1 to releases.dyne.org. I'll update and re-upload the PKGBUILD when I get some time later today. You can just uncomment out those lines yourself in the meantime, if you want.

alexei commented on 2015-02-01 03:59

URLs worked from the browser, but makepkg (on my system at least) could not fetch from the URLs with '.xsend.php?file=', but fetched fine when that substring was removed from each URL. The download links on the official website do not contain the substring. Perhaps they changed, as the comment in PKGBUILD warns.

TrialnError commented on 2015-01-07 13:34

@richli: Ok. But to justify it shouldn't be a problem ;) It would be maintained, you kind of use it (pointed releases instead of master) and would be an alternative if the pointed release has some serious bugs that are already fixed in git but not released yet (Example 2.0.1 was necessary because Ubuntu based distros had a serious problem with 2.0 ). And learn about upcoming changes that require adjustments in the PKGBuild (example for the next release https://github.com/dyne/Tomb/commit/dd91e124b41ef4d139f2b28d7b993529377d5ca5 )

I thought of doing it myself (I still use the pointed releases, but follow upstream devel), but wanted to offer you the possebility to take it (Just because you're maintaining the pointed releases).
And since you raised some valid concerns it seems you wouldn't have a problem if someone else takes the git one.

richli commented on 2015-01-07 00:40

@TrialnError: I'm a bit busy for the next while, but if I find some time, I'll see about updating the tomb-git package. Since I don't actually use it, it's hard for me to justify maintaining it. :)

frankspace commented on 2015-01-03 19:50

Thank you, adding that key worked. And I learned something. Thank you!

TrialnError commented on 2015-01-02 16:56

@richli: One question. Since you're maintaining this PKGBuild, could you also maintain the -git[0] one too? It's orphaned and not up to date. Would be nice if that could be changed.

_____
[0] https://aur.archlinux.org/packages/tomb-git/

TrialnError commented on 2015-01-02 16:51

frankspace:
The possebility was added to check if the signature of a tarball is really signed with the right key (validpgpkeys entry in the PKGBuild).
Two ways to handle that:
1) Add the key to your local keyring (just add it, do not sign it)
2) Use makepkg --skippgpcheck

See http://allanmcrae.com/2014/12/pacman-4-2-released/
Quote: "Source signatures are required to be from a trusted source or listed in the validpgpkeys array. We also support kernel.org style source signing"

richli commented on 2015-01-02 16:48

@frankspace: It's because makepkg can't find the public key. You need to run "gpg --recv-keys 0x73b35da54acb7d10" to download the public key into your keyring. No need to trust it or sign it or anything, it just needs to be accessible by gpg/makepkg.