Package Details: cower-git 17-1

Git Clone URL: (read-only)
Package Base: cower-git
Description: A simple AUR agent with a pretentious name
Upstream URL:
Keywords: aur
Licenses: MIT
Conflicts: cower
Provides: cower
Submitter: falconindy
Maintainer: falconindy
Last Packager: falconindy
Votes: 81
Popularity: 0.521322
First Submitted: 2010-03-24 03:26
Last Updated: 2017-04-24 13:30

Required by (7)

Sources (1)

Latest Comments

falconindy commented on 2017-04-24 13:22

Poof. cower no longer depends on libcrypto as of:

trekdev commented on 2017-04-24 13:08

Since openssl was updated to 1.1.0 it now specifically requires the openssl-1.0 package but it's not listed as a dependency.

EchoLynx commented on 2015-10-13 14:57

I had to change the source from this "source=("git://")" to this "source=("git+")"

Det commented on 2015-08-05 17:51

Works fine here. You could try the HTTPS URL (, or the (

brittyazel commented on 2015-08-05 17:49

I am having trouble installing this package. It is getting stuck trying to pull from the git repository.

karol_007 commented on 2014-02-03 21:54

I know your comment "But it's also good you never admitted this was your mistake." was directed to falconindy, but I think I'm responsible for the noise as I should have phrased my question better.

Det commented on 2014-02-03 21:35

You realize that wasn't directed at you, right?

karol_007 commented on 2014-02-03 21:26

falconindy wrote "Looks like I never pushed the v11 tag." which answered my question "Why is cower-git still on version 10 even though cower is already on 11?"
I did look for the tag on github, didn't find it, came here and forgot post 3/4 of what I should have. This was my mistake. Sorry for all the noise.

Det commented on 2014-02-03 20:24

But it's also good you never admitted this was your mistake.

It never is.

falconindy commented on 2014-02-03 20:23

Mentioning this in your initial post would have been useful. Looks like I never pushed the v11 tag.

karol_007 commented on 2014-02-03 20:20

I'm not talking about the one that's posted on this page i.e. 'Package Details: cower-git 10.2.g86f6b53-1', I don't care about it, I know that it will change after each commit to the -git repo.

I don't understand why I've build cower-git today and I get cower-git 10.9.gd5ba9ab-1.

Det commented on 2014-02-03 20:16

And it doesn't do it past 10.9.

falconindy commented on 2014-02-03 20:15

Keeping the pkgver "up to date" in the PKGBUILD requires that I build a new source tarball every time I make a change to the cower git repo. It's not happening.

makepkg will update the pkgver for you.

Det commented on 2014-02-03 20:09

I don't either.

You should know this.

falconindy commented on 2014-02-03 17:56

Because you don't understand how pkgver works for -git packages.

karol_007 commented on 2014-02-03 17:34

Why is cower-git still on version 10 even though cower is already on 11?

Lastebil commented on 2013-08-25 11:32

(my comment was not a suggestion for a change to the packagebuild, just a note for anyone who uses zsh and not bash that yes, someone has tested this without the bash-completion bit, and no, you do not have to go using bash for cower (: )

Lastebil commented on 2013-08-25 11:30

It still builds and runs perfectly fine without bash-completion for those of us who do not use bash (zsh completion, for example, is in the source and works great, but zsh would not make sense as a dependency for those using bash.)

(I tend to build cower twice - one time, pulling directly from git; building it there, then using that binary to pull cower-git and install with pacman. Thus why I was a bit surprized at the sudden requirement of bash-completion (: )

apg commented on 2013-08-16 21:14

bash-completion needs to be added to makedepends. Otherwise the completion file ends up in /

Det commented on 2013-04-01 13:33

PKGBUILD for pacman 4.1:

axil42 commented on 2013-03-14 14:42

Oops, hadn't notice there was a pacman41 branch... Sorry for the noise.

Det commented on 2013-03-14 14:35

Why can't you hax it in the PKGBULDI with "pacman -V" or some such?

falconindy commented on 2013-03-14 14:31

A pacman-4.1 branch has existed in my repo for over a year now.

axil42 commented on 2013-03-14 10:24

Hi falconindy, cower-git fails to build [0] with pacman 4.1.0rc1. Do you intend to fix it before the stable release?



axil42 commented on 2013-03-14 10:23

Hi falconindy, cower-git fails to build [0] with pacman 4.1.0rc1. Do you intend to fix it before the stable release?



karol_007 commented on 2012-09-08 07:59

$ echo $PATH

What is yours?

fosskers commented on 2012-09-08 02:05

Interesting. My shell isn't including subdirectories of directories already in my PATH.

karol_007 commented on 2012-09-08 01:28

$ pacman -Qo /usr/bin/core_perl/pod2man
/usr/bin/core_perl/pod2man is owned by perl 5.16.1-1

karol_007 commented on 2012-09-08 01:28

$ sp -Qo /usr/bin/core_perl/pod2man
/usr/bin/core_perl/pod2man is owned by perl 5.16.1-1

fosskers commented on 2012-09-08 01:23

Hmm. /usr/bin is already in my path (where perl is).
Is pod2man a separate executable? `which` isn't finding it.

falconindy commented on 2012-09-07 12:46

pod2man is part of perl. You need to fix your PATH.

fosskers commented on 2012-09-07 12:41

Getting this on build:

pod2man --section=1 --center="Cower Manual" --name="COWER" --release="cower 6-3-g76a1644" README.pod > cower.1
/bin/sh: pod2man: command not found
make: *** [cower.1] Error 127

falconindy commented on 2012-02-19 14:21

The required by info is not in the JSON reply from the RPC -- it only appears on the package detail pages. Since cower isn't an HTML scraper, i won't be doing this.

Det commented on 2012-02-19 11:21

Why won't passing the '-i' flag twice tell me the list of the "Required by" packages as in pacman?

Shouldn't that be an easy thing to do?

muunleit commented on 2012-01-14 08:40

I have problems to build the latest version. =>

falconindy commented on 2011-08-29 12:56

"does not work with pacman-git" means cower doesn't compile against

c00kiemon5ter commented on 2011-08-29 12:49

cower doesn't intergrate with pacman in any way. Cower just downloads packages and optionally checks their deps from AUR.
It doesn't even build them. Maybe I'm off here, but I don't see what "does not work with pacman-git" mean.

falconindy commented on 2011-08-29 12:48

Well it does, you just need to pull from the pacman4 branch of the repo.

eworm commented on 2011-08-29 12:41

This does not yet work with pacman-git. Do you have patches or is there work in progress?

falconindy commented on 2011-03-07 05:32

cower now has a config file! A sample config is shipped and installed to /usr/share/cower/config.

falconindy commented on 2011-02-11 03:56

Annnnnd its fixed.

hellnest commented on 2011-02-11 03:16

I'm run on 32bit. Yeaps, thanks for ur response :)

falconindy commented on 2011-02-11 02:55

Mmmm, I wonder why I'm able to avoid that error on 64 bit... I've got multiple machines where that isn't triggered. Nonetheless, it shall be fixed ASAP.

hellnest commented on 2011-02-11 02:43

check this out

cc1: warnings being treated as errors
cower.c: In function ‘get_file_as_buffer’:
cower.c:700:3: error: format ‘%zd’ expects type ‘signed size_t’, but argument 4 has type ‘long int’
make: *** [cower.o] Error 1

Anonymous comment on 2011-02-09 18:36

Thanks, it works now.

falconindy commented on 2011-02-09 18:33

@bobdob: Because you're not using the latest PKGBUILD.

Anonymous comment on 2011-02-09 18:24

I'm getting an error while trying to update, or just search:

error: failed to initialize alpm library

Anyone know what the problem is?

Det commented on 2010-12-30 14:10

Nice. Thanks.

falconindy commented on 2010-12-30 14:07

Ditto what c00kimon4ter said. Strangely, in your case, your invocation should have enabled color and searched for 'asd' and 'auto'.

c00kiemon5ter commented on 2010-12-30 14:03

works here
the correct syntax is 'cower -c -s ads' or if you like 'cower --color=auto -s asd'

Det commented on 2010-12-30 13:55

So, no chance to "color" the search too? E.g. "cower -c auto -s asd".

falconindy commented on 2010-06-17 22:49

Try it and let me know how that goes ;)

Cower needs to link against curl and yajl during building. Without these installed, the build _will_ fail.

solstice commented on 2010-06-17 21:16

I think curl and yajl and pacman are not really makedepends. only git is.