Package Details: pac 1.3.7-1

Git Clone URL: https://aur.archlinux.org/pac.git (read-only)
Package Base: pac
Description: Small wrapper around pacaur to mimic yaourts search feature
Upstream URL: https://github.com/XenGi/pac
Keywords: pacaur wrapper
Licenses: MIT
Submitter: XenGi
Maintainer: XenGi
Last Packager: XenGi
Votes: 12
Popularity: 0.909944
First Submitted: 2017-01-14 06:10
Last Updated: 2017-12-01 14:38

Pinned Comments

XenGi commented on 2017-05-16 13:11

@romanlevin I don't use antergos or manjaro. It should work on archlinux based distros but I can't test it.
Regarding the key. You just have to import it in your keyring. Try doing:

gpg --recv-keys 1A9D657D06B5820E

And then try to install pac again.

Latest Comments

XenGi commented on 2017-09-13 09:40

@najodleglejszy did you do it as a normal user? pacaur operates as your normal user and tries to find the keys in your users keyring. If you import it as root or in the pacman keyring it won't find it.

najodleglejszy commented on 2017-09-13 07:12

I tried doing

gpg --recv-keys 1A9D657D06B5820E

but I'm still getting:

:: Retrieving package(s)...
:: pac build files are up-to-date -- skipping
:: Checking pac integrity...
==> Making package: pac 1.3.6-1 (Wed 13 Sep 09:12:08 CEST 2017)
==> Retrieving sources...
-> Found v1.3.6.tar.gz
-> Found v1.3.6.tar.gz.sig
==> Validating source files with sha256sums...
v1.3.6.tar.gz ... Passed
v1.3.6.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
v1.3.6.tar.gz ... FAILED (unknown public key 1A9D657D06B5820E)
==> ERROR: One or more PGP signatures could not be verified!
:: failed to verify pac integrity

XenGi commented on 2017-09-07 10:00

@RogueScholar First, wtf? This pacmanager thing looks like someone who never used a terminal emulator wrote a terminal emulator. You could easily switch to putty if you're into that kinda thing or just use a normal terminal and ssh like everyone else.

But seriously, pac is just a single python script. If you want to use it and still have that strange pacmanager thing around, just get it manually, put it somewhere and rename it.
pac won't get any updates in the future anyway. It is feature complete and I will only change it if pacaur introduces some breaking changes. I will try to merge it in pacaur. Then all our problems would be solved.

RogueScholar commented on 2017-09-07 05:35

Is there an established procedure or protocol when two packages attempt to use the same filename? I use the Perl Auto Connector (PAC Manager) for my ssh terminals and it lays claim to the /usr/bin/pac file system address. This of course prevents this package from installing after it's built.

I'm anticipating the response "Dance with the one that brung ya, son" but didn't want to assume that smarter people than I would've already agreed on the best way to resolve these sorts of issues. I thank you kindly in advance for any responses.

timofonic commented on 2017-07-26 03:48

Sorry. I didn't read this.

I also wonder if this would be merged into pacaur. Did you talk with the developer? :D

timofonic commented on 2017-07-26 03:47

: Package pac not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...

AUR Packages (1) pac-1.3.6-1

:: Proceed with installation? [Y/n]
:: Retrieving package(s)...
:: Checking pac integrity...
==> Making package: pac 1.3.6-1 (Wed Jul 26 05:45:58 CEST 2017)
==> Retrieving sources...
-> Found v1.3.6.tar.gz
-> Found v1.3.6.tar.gz.sig
==> Validating source files with sha256sums...
v1.3.6.tar.gz ... Passed
v1.3.6.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
v1.3.6.tar.gz ... FAILED (unknown public key 1A9D657D06B5820E)
==> ERROR: One or more PGP signatures could not be verified!
:: failed to verify pac integrity

XenGi commented on 2017-05-16 13:11

@romanlevin I don't use antergos or manjaro. It should work on archlinux based distros but I can't test it.
Regarding the key. You just have to import it in your keyring. Try doing:

gpg --recv-keys 1A9D657D06B5820E

And then try to install pac again.

romanlevin commented on 2017-05-16 12:41

Installing on Antergos fails with an unknown public key error:

$ pacaur -S pac
:: Package pac not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...

AUR Packages (1) pac-1.3.5-1

:: Proceed with installation? [Y/n]

:: Retrieving package(s)...
:: pac build files are up-to-date -- skipping
[sudo] password for roman:
:: Checking pac integrity...
==> Making package: pac 1.3.5-1 (Tue May 16 14:40:15 CEST 2017)
==> Retrieving sources...
-> Found v1.3.5.tar.gz
-> Found v1.3.5.tar.gz.sig
==> Validating source files with sha256sums...
v1.3.5.tar.gz ... Passed
v1.3.5.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
v1.3.5.tar.gz ... FAILED (unknown public key 1A9D657D06B5820E)
==> ERROR: One or more PGP signatures could not be verified!
:: failed to verify pac integrity

menna commented on 2017-02-14 14:54

Please add pacaur as a dependency.