Package Details: cower 18-1

Git Clone URL: (read-only)
Package Base: cower
Description: A simple AUR agent with a pretentious name
Upstream URL:
Keywords: aur
Licenses: MIT
Submitter: falconindy
Maintainer: falconindy
Last Packager: falconindy
Votes: 1012
Popularity: 2.587831
First Submitted: 2010-12-30 02:30
Last Updated: 2018-05-12 14:40

Pinned Comments

ArchangeGabriel commented on 2017-05-14 12:36

Pinning answers to two often raised questions.

About pkg-config: this is part of base-devel group, which is expected to be installed on any system using the AUR. So this is not a missing dependency.

About armv7h in arch array: ArchLinux ARM is already providing cower for all arm archs, and more generally any other arch being unsupported it’s your responsibility to modify the PKGBUILD to add yours. And no, 'any' is not the same as a list of specific archs, it means that the produced binary is arch-independent, which is rarely the case.

falconindy commented on 2016-03-21 12:57

If you are having problems installing this package due to signature verification, please run the below before running makepkg:

gpg --recv-keys --keyserver hkp:// 1EB2638FF56C0C53

If makepkg still complains after this:

1) Ensure you're using makepkg, and not some wrapper.
2) Ensure you don't have GNUPGHOME set in /etc/makepkg.conf or ~/.makepkg.conf, or that the value of GNUGPHOME in makepkg.conf matches that which you've run the above gpg command with.
3) Ensure that the tarball you downloaded matches the md5sums in the PKGBUILD.

If you have problems locating pod2man during the build, please figure out where your PATH is being overridden. /etc/profile.d/ from the perl package will ensure that pod2man is in your PATH.

Kindly do not do the following because of failures in source tarball verification:

1) Complain that the package is broken.
2) Mark the package out of date.

Due to the amount of spam I receive, I've been forced to disable notifications for this package.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

talentedunicorn commented on 2018-12-21 14:19

$ gpg --recv-keys 1EB2638FF56C0C53 before running $ makepkg works

wilberfan commented on 2018-07-05 21:11

The suggested gpg command returns no data:

$ gpg --recv-keys --keyserver hkp:// 1EB2638FF56C0C53 gpg: keyserver receive failed: No data

hsantanna commented on 2018-06-03 16:15

To rebuild cower:

pacaur -S --rebuild cower

alex.shpilkin commented on 2018-06-02 13:46

@falconindy: GPG refuses to import your key. As far as I can see, this is because it only has self-signatures done with SHA-1 (digest algo 2).

$ gpg --recv-keys --keyserver hkp:// 1EB2638FF56C0C53
gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: key 1EB2638FF56C0C53: 3 duplicate signatures removed
gpg: key 1EB2638FF56C0C53: 26 signatures not checked due to missing keys
gpg: key 1EB2638FF56C0C53: 3 bad signatures
gpg: key 1EB2638FF56C0C53: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1

cluxter commented on 2018-06-01 15:14

About the issue saying:

cower: error while loading shared libraries: cannot open shared object file: No such file or directory

This issue does not only affect yaourt but also pacaur in my case, and no update has been released for it so far. So here is a temporary workaround:

EDIT: here is the proper way to fix this error:

berbae commented on 2018-05-31 09:01

Needs a rebuild with new pacman release :

cower --update <br> cower: error while loading shared libraries: cannot open shared object file: No such file or directory

artafinde commented on 2018-05-31 07:24

@happyarchlinuser: see

happyarchlinuser commented on 2018-05-31 07:03

How can I rebuild / update cower? I tried makepkg -sf and pacman -U but I still get

cower: error while loading shared libraries: cannot open shared object file: No such file or directory

ArchangeGabriel commented on 2018-05-29 09:56

Please people, this is the same thing on each major pacman upgrade, or for what matters on any sobump affecting an AUR package. Yes, you are responsible for rebuilding your AUR affected packages after a soname change in the repos.

E5ten commented on 2018-05-29 03:48

Could you bump the release number up once so that it rebuilds for people and links against the new version of libalpm?