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.000006
First Submitted: 2012-05-04 21:54
Last Updated: 2017-11-30 00:18

Latest Comments


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: 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.

annoyingduck commented on 2017-04-08 04:54

@Stebalien I'm getting the key error too. I have Googled it, and most results are telling me to NOT import a public key manually. Are you suggesting by your response to go ahead and manually import the key from the PKGBUILD? Edit: I ran the command "gpg --recv-key B3C7CE210DE76DFC" to import your public key, and it built fine. Misread the key import option do's and don'ts.

Stebalien commented on 2017-04-08 00:03

@shihjay2 before asking for help, please at least google the error.

shihjay2 commented on 2017-04-07 23:40

Error during build -
pithos-1.3.0.tar.xz ... FAILED (unknown public key B3C7CE210DE76DFC)

Stebalien commented on 2017-01-07 20:03

@oberon2007 It's the only way to deal with out-of-sync mirrors. Otherwise, yaourt etc. could end up rebuilding *before* installing python3.6 (which defeats the purpose). Furthermore, it's not forcing python3.6; you don't *need* to update pithos unless you want to rebuild it for the latest python (and I plan on removing that restriction on the next pithos update).

Note: The correct way to do this would be to set `python=$(get_python_version)` (no `>=`) and let the user manually rebuild when needed. Unfortunately, that would make upgrading a bit troublesome (you'd need python3.6 before you could build pithos for python3.6 but you wouldn't be able to install python3.6 because your current version of pithos would depend on python3.5).

oberon2007 commented on 2017-01-07 19:36

"This is the only way to handle a rebuild in the AUR." is not true. It would be enough to just bump pkgrel and yaourt and pacaur will want to rebuild the package. I don't think it is a good idea to force python3.6 on the package without a specific reason.

Stebalien commented on 2017-01-07 17:10

@annoyingduck, use an up-to-date pacman mirror. You have python 3.5 but the latest is python 3.6.

annoyingduck commented on 2017-01-07 12:22

Keep getting a build error on latest update: Python>=3.6 not found. Python is installed in my system.

TingPing commented on 2016-12-01 23:54

@camb, Works here w/ free account.