Package Details: pithos 1.4.1-1

Git Clone URL: (read-only)
Package Base: pithos
Description: Native Pandora Radio client
Upstream URL:
Licenses: GPL3
Submitter: kreed
Maintainer: Stebalien (TingPing)
Last Packager: Stebalien
Votes: 69
Popularity: 0.000905
First Submitted: 2012-05-04 21:54
Last Updated: 2017-11-30 00:18

Latest Comments

1 2 3 4 5 Next › Last »

TingPing commented on 2018-12-03 00:35

Should python-sphinx and help2man be added to makedepends?

They aren't useful for users only developers.

yochananmarqos commented on 2018-12-02 20:52

Should python-sphinx and help2man be added to makedepends?

Program sphinx-build-3 found: NO
Program sphinx-build found: NO
Program help2man found: NO

Stebalien commented on 2018-02-12 16:57


xovertheyearsx commented on 2018-02-12 06:27

I was experiencing a similar issue to @annyoingduck and @shihjay2

@Steblien, gpg had basic config setup and db was fine. I had to manually run a checksum as well.

TingPing commented on 2017-09-12 20:06


That will be fixed in next Meson release:

craeckie commented on 2017-09-12 19:48

When building it using the "nobody" user, I get the error "Permission denied" on "subprocess.check_call(['selinuxenabled'])" in meson.
See the full log here:
Using normal user it works.

annoyingduck commented on 2017-05-06 02:08

@Stebalien the gpg --list-key 108BF2212A051F4A72B18448B3C7CE210DE76DFC command kicked back a bunch of errors along with a recommended solution (gotta love the Arch terminal). I was able to fix it, the trustdb was corrupted. Thank you.

Stebalien commented on 2017-05-05 16:58


Something may be wrong with your PGP setup, the signature you've downloaded may be corrupted (the PKGBUILD doesn't checksum the signature, only the source code), or something else is going very wrong. It works for me (and I've tried re-downloading my cached copies of pithos and it's signature).

The signature's sha256sum should be 5658ae222c498f1d3fb2be3dc1f1ddb1ea2361b15b2406325e8bdb40ce1b2a73 if you want to verify that you've downloaded it correctly. Otherwise, make sure you actually have the key:

$ gpg --list-key 108BF2212A051F4A72B18448B3C7CE210DE76DFC

(and make sure the copy you have hasn't expired)

annoyingduck commented on 2017-05-05 03:55

I just tried updating pithos on my laptop after adding the key like I did before, and it simply will not build on this device. I keep getting: Verifying source file signatures with gpg...
pithos-1.3.1.tar.xz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build pithos.
==> Restart building pithos ? [y/N]
I've added your key using: gpg --recv-key B3C7CE210DE76DFC and it continues to fail. What am I missing?

Stebalien commented on 2017-04-10 16:26

For *pacman* key errors, you shouldn't import the key into your personal keyring. For *makepkg* key errors, you should. You may also be able to setup GPG to automatically import keys as needed.

FYI, importing a key *does not* imply that you trust the key (so there's really no reason not to import keys other than disk space).


@solus667, The out of date button is for out of date packages. Please don't use it for support.