| Git Clone URL: | https://aur.archlinux.org/tomb.git (read-only, click to copy) |
|---|---|
| Package Base: | tomb |
| Description: | Crypto Undertaker, a simple tool to manage encrypted storage |
| Upstream URL: | https://www.dyne.org/software/tomb/ |
| Licenses: | GPL3 |
| Submitter: | None |
| Maintainer: | parazyd (roddhjav) |
| Last Packager: | roddhjav |
| Votes: | 53 |
| Popularity: | 0.036678 |
| First Submitted: | 2011-04-15 15:20 (UTC) |
| Last Updated: | 2024-07-12 17:24 (UTC) |
@TrialnError Yup, I agree, after seeing [1] and [2] (see JGC's first comment). If you uninstall gtk2, tomb likely bails for you too. Fine with me to just have the info in the comments.
[1] https://bugs.archlinux.org/task/76407 [2] https://bugs.archlinux.org/task/66741
@randomice: Yes, but Tomb uses the pinentry package. And if you list the information regarding the deps you will see gtk2 listed:
$ pacman -Qi pinentry
Name : pinentry
Version : 1.2.1-3
Description : Collection of simple PIN or passphrase entry dialogs which utilize the Assuan protocol
(...)
Depends On : glibc ncurses libassuan libsecret glib2 libsecret-1.so=0-64 libncursesw.so=6-64
libassuan.so=0-64 libglib-2.0.so=0-64
Optional Deps : gtk2: gtk2 backend [installed]
qt5-x11extras: qt backend
kwayland5: qt backend
gcr: gnome3 backend [installed]
(...)
There is gtk2 listed as an optional dep if someone wants to use the gtk2 backend. But kinda stupidly the gtk2 backend is also the default...
But it would be wrong to declare gtk2 as a dep for tomb.
@TrialnError Curiously, when I don't have gtk2 installed and don't hardcode a pinentry via [1], a local tomb open results in
pinentry-gtk-2: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
That's why I made the suggestion. cheers.
@randomice: This is covered through optdepends on the pinentry package. This PKGBUILD shouldn't hardcode this, as people could use different pinentries (like myself, as I use the gnome3-pinentry for its better wayland support)
@tamjan: But you did import the pgp key in question into your local keyring?
==> Making package: tomb 2.9-3 (fre 3 nov 2023 08:00:12)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Tomb-2.9.tar.gz
-> Found Tomb-2.9.tar.gz.sha
-> Found Tomb-2.9.tar.gz.asc
==> Validating source files with sha256sums...
Tomb-2.9.tar.gz ... Passed
Tomb-2.9.tar.gz.sha ... Passed
Tomb-2.9.tar.gz.asc ... Skipped
==> Verifying source file signatures with gpg...
Tomb-2.9.tar.gz ... SOURCE FILE NOT FOUND
==> ERROR: One or more PGP signatures could not be verified!On Gnome with wayland, the package required a missing depend on gtk2 [1] to invoke pinentry.
To install the package first import jaromil PGP key:
gpg --recv-keys 6113D89CA825C5CEDD02C87273B35DA54ACB7D10
Alternatively add keyserver-options auto-key-retrieve to your ~/.gnupg/gpg.conf.
This key can also be found on https://keybase.io/jaromil
PKGBUILD giving following error :
==> Verifying source file signatures with gpg...
Tomb-2.7.tar.gz ... FAILED (unknown public key 73B35DA54ACB7D10)
==> ERROR: One or more PGP signatures could not be verified!
Pinned Comments
roddhjav commented on 2020-05-24 12:13 (UTC) (edited on 2020-05-24 12:16 (UTC) by roddhjav)
To install the package first import jaromil PGP key:
Alternatively add
keyserver-options auto-key-retrieveto your~/.gnupg/gpg.conf.This key can also be found on https://keybase.io/jaromil