Package Details: cope-git 168.a0e6692-1

Git Clone URL: (read-only)
Package Base: cope-git
Description: A colourful wrapper for terminal programs
Upstream URL:
Licenses: GPL, PerlArtistic
Conflicts: cope
Provides: cope
Submitter: None
Maintainer: lotrfan
Last Packager: lotrfan
Votes: 93
Popularity: 0.211084
First Submitted: 2009-12-08 08:25
Last Updated: 2015-06-08 23:09

Latest Comments

marius.knaust commented on 2014-04-28 18:02

Please add the following variables, so other packages can depend on 'cope':

lotrfan commented on 2013-12-28 18:35

Sorry for the late responses...

Looks related to [1], [2], and [3]. Quoting from [3]:

"The update to glibc-2.18 removes pt_chown which is a security risk. It is not needed on an Arch system given we have /dev/pts.

However, some people appear to have /dev/pts in their /etc/fstab file, which generates it with the wrong permissions. This will result in errors like "grantpt failed: Operation not permitted".

To fix this, remove that line from your fstab file. systemd will take care of generating /dev/pts with the right permissions."


It is a fork (mine), but upstream is dead (i.e., non-existent - the Upstream URL above has been dead since before 2011 ([4] is the most recent copy I could find), and the original GitHub repo [5] doesn't exist, either). According to [6], there has been little actual development in the other forks (mainly fixing issues with perl versions). If there's a different fork that you prefer, which one is it? I'll consider switching, or merging it into mine.

It also clones from GitHub (using the git:// protocol in the source array).

Assuming this is why it's marked out-of-date, I'm unflagging it.


t.ask commented on 2013-12-13 15:16

It clones from a fork and also doesn't git clone from Github.

ould commented on 2013-11-01 18:02

I get this before every cope command:

IO::Tty::pty_allocate(nonfatal): grantpt(): Operation not permitted at /usr/lib/perl5/vendor_perl/IO/ line 24.

Any ideas how to fix? It is rather annoying. Thanks!!

lotrfan commented on 2013-10-06 09:02

I pushed a fix to GitHub.

(I get the error too, but I normally run ps through grep, so I never saw it... thanks for reporting it!)

I don't think it was an API change, but I don't have another version of perl to test on right now... It was an issue with the /p regexp modifier not being applied for some reason when using a compiled regular expression... The fix I applied doesn't need that functionality, although it might be slightly slower.

Also, @adam900710, you put "nocope" in front of any commands to run the original:
nocope make menuconfig

roy_hu commented on 2013-10-06 07:20

I'm seeing errors with the ps command.

$ ps
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/vendor_perl/auto/share/dist/Cope/ps line 82.

$ ps u
Use of uninitialized value $uid in string eq at /usr/share/perl5/vendor_perl/App/Cope/ line 105.

Are they due to API changes in perl 5.18?

lotrfan commented on 2013-06-21 06:16

I'm adopting this package. (This is my first stab at being a maintainer, so any comments are appreciated!)

Summary of changes:
* Instead of patching, I forked the old source.
* The PKGBUILD now uses the package() and pkgver() functions introduced with pacman 4.1.
* [Most of] the scripts should work (without errors) using perl 5.18. I don't use all of the scripts, so if one isn't working, let me know.
* There's a new dependency: perl-regexp-ipv6. This was installed by the makefile (using cpan) if needed, so it's technically not a "new" dependency - it just now uses the version on the AUR.
* The 'ifconfig' script should now work with Arch's ifconfig output.

null commented on 2013-05-26 13:16

Disowned, have no time for this at the moment.
There are some build errors since Perl 5.18 which I can't fix.

For the next maintainer: I guess the most active and updated repository is

Neuromatic commented on 2013-05-21 17:04

Perl API changed at last update to perl 5-18. Please update this package

adam900710 commented on 2012-10-29 00:45

If the cope wrap the make command, "make menuconfig" will not function as it always does.
Please refer to this bug:

It would be very nice if an exception can be add for "menuconfig"

All comments