Package Details: packer-color 20150808-1

Git Clone URL: (read-only)
Package Base: packer-color
Description: Adds AUR support to 'pacman' | Adds better colourisation and error handling to 'packer'
Upstream URL:
Licenses: GPL3
Submitter: Xavion
Maintainer: None
Last Packager: Xavion
Votes: 90
Popularity: 0.062412
First Submitted: 2011-08-06 00:55
Last Updated: 2016-02-15 04:55

Dependencies (11)

Required by (0)

Sources (1)

Latest Comments

Xavion commented on 2016-04-08 22:09

Hi All,

This is just to let you know that I have decided to orphan (and abandon) this package. I'm doing so purely because I've reverted to using the much improved 'yaourt'.

I created 'packer-color' to improve some of the shortcomings of 'packer', which had been designed as a replacement for the then old and decrepit 'yaourt'.

The latter has since been revamped, while 'packer' has remained stagnant. In particular, 'yaourt' now finds AUR package upgrades (via -Sua) in parallel (and it's much faster at doing so than 'packer' is).

Xavion commented on 2016-02-15 05:23

Thanks for pointing that out; I've added some brackets around 'license'. I must've overlooked that omission when forking from 'packer' all those years ago.

WFV commented on 2016-02-14 21:59

Need to edit PKGBUILD to make the license an array during install, same with the zsh-packer-color, else it fails on the license not being an array ()

Xavion commented on 2015-09-05 20:41

I'm not getting that here either. Maybe you've set a Git configuration flag that's interfering.

Perhaps this webpage will help:

Clouseau commented on 2015-09-05 13:08

Cannot build, anyon have issue?

packer -S packer-color

Aur Targets (1): packer-color

Proceed with installation? [Y/n] y
Edit packer-color PKGBUILD with $EDITOR? [Y/n] n
Edit packer-color.install with $EDITOR? [Y/n] n
==> Making package: packer-color 20150808-1 (Sub Ruj 5 15:08:07 CEST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found color.patch
==> Validating source files with sha1sums...
color.patch ... Passed
==> Extracting sources...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
==> Connecting to GIT server ...
Updating dc83901..ed928f8
error: Your local changes to the following files would be overwritten by merge:
Please, commit your changes or stash them before you can merge.
==> ERROR: A failure occurred in build().
The build failed.

Xavion commented on 2015-09-04 22:22

I'm not experiencing that problem here. When I extract the snapshot, all files are of type "ASCII text" (i.e. UNIX format). Accordingly, no EOL conversion is necessary before building the package.

anaveragehuman commented on 2015-09-03 22:46

When I downloaded the snapshot, I noticed that the patch didn't work because of line ending differences. I had to run dos2unix on the files so that it would work.

Xabre commented on 2015-08-09 12:52


Xavion commented on 2015-08-08 22:06

That was bound to happen at some point. The AUR v4 patch was no longer necessary; it has just been incorporated into 'packer'. As such, I have removed it from this package.

Xabre commented on 2015-08-08 14:56

==> Starting build()...
==> Connecting to GIT server ...
Cloning into 'packer'...
remote: Counting objects: 708, done.
remote: Total 708 (delta 0), reused 0 (delta 0), pack-reused 708
Receiving objects: 100% (708/708), 138.83 KiB | 0 bytes/s, done.
Resolving deltas: 100% (226/226), done.
Checking connectivity... done.
patching file packer
Hunk #1 succeeded at 663 (offset 83 lines).
patching file packer
Hunk #1 FAILED at 24.
Hunk #2 FAILED at 241.
2 out of 2 hunks FAILED -- saving rejects to file packer.rej
==> ERROR: A failure occurred in build().

Xavion commented on 2015-07-31 20:57

An alternative would be to just use tab completion. Have you heard of it? Instead of typing seven characters (packer<space>), I only have to enter six (packe<tab>).

hydranix commented on 2015-07-31 19:50

I found that after doing:
cd /tmp
git clone
cd packer-color*
makepkg -i
pacman -R packer
cd /usr/bin
sudo ls -s packer-color packer

it was a lot easier than retraining myself to type an extra 6 characters :)

Xavion commented on 2015-07-09 21:03

If you removed "packer", I'm not surprised it doesn't work anymore. To answer your question, "packer-color" does not require "packer" to be installed as well.

After installing "packer-color", you must use the "packer-color" executable. If this doesn't work for you, I will need to see the error message you're getting.

sams.viper commented on 2015-07-09 14:12

@Xavion: i remove the original packer and install packer-color from you... but now packer not working any more... are both packer and packer-color to be install side-by-site?

grondinm commented on 2015-06-22 10:26

updated the pull request for a change in what is provided by rpcinfo

Xavion commented on 2015-06-18 22:05

Thanks for doing that; I've incorporated your patch. If 'keenerd' doesn't design a better one, we'll stay with yours when AUR v4 goes live.

grondinm commented on 2015-06-18 12:46

just an FYI i created this pull request to the packer dev to make it work with AUR4. it might not be the best fix but it works

sysfu commented on 2013-12-28 00:41

Nevermind last comment, was a problem with multilib. Disabled multilib and reinstalled base-devel and now packer-color builds w-out errors.

sysfu commented on 2013-12-27 23:37

Trying to build with makepkg but it's failing with this error;

$ makepkg
==> Making package: packer-color 20130730-1 (Fri Dec 27 07:34:26 PST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> Extracting sources...
==> Starting build()...
==> Connecting to GIT server ...
Cloning into 'packer'...
remote: Reusing existing pack: 696, done.
remote: Total 696 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (696/696), 128.37 KiB | 0 bytes/s, done.
Resolving deltas: 100% (222/222), done.
Checking connectivity... done.
/home/user/packer-color/PKGBUILD: line 35: patch: command not found

$ ls -l
total 12
-rw-r--r-- 1 user users 341 Apr 5 2013 packer-color.install
-rw-r--r-- 1 user users 1344 Aug 21 2011 packer-color.patch
d--------- 1 user users 0 Dec 27 07:34 pkg
-rw-r----- 1 user users 1317 Jul 31 00:31 PKGBUILD
drwxr-xr-x 1 user users 12 Dec 27 07:34 src

Line 35 of PKGBUILD

patch -Np1 < "${startdir}"/${pkgname}.patch

Xavion commented on 2013-05-07 22:02

I don't think checking for updated packages on AUR should require 'root' privileges. However, these will be necessary when installing said packages after building them. If you disagree with my first sentence, you should inform the 'packer' developer.

allevil669 commented on 2013-05-07 17:05

I've just noticed something when using packer-color...

When I run the command: packer-color --auronly -Syu
Packer-color runs and updates everything just fine, even though root permissions should be needed. Am I doing something wrong? Or is this normal behavior?

Thanks for any help.

Xavion commented on 2013-04-06 03:17

Thanks for letting me know about this; I've modified the PKGBUILD accordingly.

helq commented on 2013-04-06 02:16

pacman-color doesn't exists!

Liquen commented on 2012-12-12 16:41

I get the following error after lua update from 5.1.5 to 5.2.1:

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

Does anyone have a solution? Thanks in advance.

Xavion commented on 2012-12-11 20:37

Thanks for letting me know about that. Upstream has a new maintainer and Git repository. I have updated the PKGBUILD accordingly.

Anonymous comment on 2012-12-11 19:10

==> Determining latest git revision...
-> Version found: 20121211
==> Making package: packer-color 20121211-1 (Tue 11 Dec 19:05:57 GMT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
==> Extracting Sources...
==> Starting build()...
==> Connecting to GIT server ...
Cloning into 'packer'...
Username for '':

do i need to register with github to install this :S

Xavion commented on 2012-03-01 20:57

I just rebuilt this package here without any troubles. Either the server was down earlier or there was a problem with your network connection.

Anonymous comment on 2012-03-01 20:45

=> Connecting to GIT server ...
Cloning into 'packer'...
error: The requested URL returned error: 403 while accessing
fatal: HTTP request failed

Problem with the GIT repo?

Xavion commented on 2011-10-10 05:15

That's actually the correct behaviour, since all unrecognised flags (e.g. -Sc, -Q, -R) are forwarded directly to "pacman-color".

Segaja commented on 2011-10-09 16:41

Normally packer-color automatically use sudo internally wherever it is needed.
However when running packer-color -Sc I get the message:
error: you cannot perform this operation unless you are root.

When I run sudo packer-color -Sc it works fine, so I would guess there is a sudo missing somewhere in the code.

The same thing applies for packer-color -Scc

Anonymous comment on 2011-08-23 03:06

Thanks !!!
Keep the good work !!!

Xavion commented on 2011-08-22 06:50

Thanks for notifying me of this issue. It occurred because the author of 'packer' changed his source code recently. I've updated the patch file accordingly. It may stop working again after he makes further coding changes.

Anonymous comment on 2011-08-21 20:58

I am new on Arch.
error when installing:

==> Connecting to GIT server ...
Cloning into packer...
remote: Counting objects: 624, done.
remote: Compressing objects: 100% (290/290), done.
remote: Total 624 (delta 205), reused 589 (delta 184)
Receiving objects: 100% (624/624), 84.40 KiB | 104 KiB/s, done.
Resolving deltas: 100% (205/205), done.
patching file packer
Hunk #1 FAILED at 595.
1 out of 1 hunk FAILED -- saving rejects to file packer.rej

Howto resolve this ?
Thanks for attention !