You are not logged in.
I just noticed that pacaur does not properly send an exit code when an install/update fails due to a failed gpg check:
$ pacaur -Syu && echo "This should not get echoed"
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
infinality-bundle is up to date
infinality-bundle-multilib is up to date
infinality-bundle-fonts is up to date
:: Starting full system upgrade...
there is nothing to do
:: Starting AUR upgrade...
:: resolving dependencies...
:: looking for inter-conflicts...
AUR Packages (1): ffmpeg-full-1:2.5.2-3
:: Proceed with installation? [Y/n] y
:: Retrieving package(s)...
:: View ffmpeg-full PKGBUILD? [Y/n] n
:: Building ffmpeg-full package(s)...
==> Making package: ffmpeg-full 1:2.5.2-3 (Wed Dec 31 18:39:54 EST 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading ffmpeg-2.5.2.tar.bz2...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 7495k 100 7495k 0 0 1018k 0 0:00:07 0:00:07 --:--:-- 1485k
-> Downloading ffmpeg-2.5.2.tar.bz2.asc...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 473 100 473 0 0 1837 0 --:--:-- --:--:-- --:--:-- 1840
-> Found UNREDISTRIBUTABLE.txt
==> Validating source files with sha256sums...
ffmpeg-2.5.2.tar.bz2 ... Passed
ffmpeg-2.5.2.tar.bz2.asc ... Skipped
UNREDISTRIBUTABLE.txt ... Passed
==> Verifying source file signatures with gpg...
ffmpeg-2.5.2.tar.bz2 ... FAILED (unknown public key B4322F04D67658D8)
==> ERROR: One or more PGP signatures could not be verified!
:: ffmpeg-full cleaned
This should not get echoed
I also need to figure out why that gpg check is failing, but that's a separate issue... that echo command should not have been reached.
Offline
that echo command should not have been reached.
pacaur -Syu does more than installing package, the last step is cleaning the leftover.. which succeeds. But generally speaking, errors handling is most probably the main weakness of pacaur. There are several issues/feature requests open in the bugtracker.
Last edited by Spyhawk (2015-01-01 10:25:07)
Offline
I figured out the problem seems like because I run a different locale other than english , pacaur doesn accept y as an answer for yes. I have to press the letter for my locale (in my case danish) for it to run the makepkg and install the aur package. Very confusing.
I generated the da_DK.UTF-8 locale on my computer, rebooted and all I can say is that this is working for me. It seems the issue is on your side.
$ echo $LANG
da_DK.UTF-8
$ pacaur -S cower
:: Package(s) cower not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...
:: cower-12-2 is up to date -- reinstalling
AUR Packages (1):
Name Old Version New Version
aur/cower 12-2 12-2
:: Proceed with installation? [Y/n] y
:: Retrieving package(s)...
:: View cower PKGBUILD? [Y/n] n
[sudo] password for spyhawk:
:: Building cower package(s)...
==> Making package: cower 12-2 (tor jan 1 11:16:41 CET 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found cower-12.tar.gz
-> Found cower-12.tar.gz.sig
==> Validating source files with md5sums...
cower-12.tar.gz ... Passed
cower-12.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
cower-12.tar.gz ... Passed
==> Extracting sources...
-> Extracting cower-12.tar.gz with bsdtar
==> Starting build()...
cc -std=c99 -g -pedantic -Wall -Wextra -pthread -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -D_GNU_SOURCE -DCOWER_VERSION=\"12\" -D_FORTIFY_SOURCE=2 -pthread -Wl,-O1,--sort-common,--as-needed,-z,relro cower.c -lcurl -lalpm -lyajl -larchive -lcrypto -o cower
pod2man --section=1 --center="Cower Manual" --name="COWER" --release="cower 12" README.pod cower.1
==> Entering fakeroot environment...
==> Starting package()...
install -D -m755 cower "/tmp/pacaurtmp-remy/cower/pkg/cower/usr/bin/cower"
install -D -m644 cower.1 "/tmp/pacaurtmp-remy/cower/pkg/cower/usr/share/man/man1/cower.1"
install -D -m644 bash_completion "/tmp/pacaurtmp-remy/cower/pkg/cower/usr/share/bash-completion/completions/cower"
install -D -m644 zsh_completion "/tmp/pacaurtmp-remy/cower/pkg/cower/usr/share/zsh/site-functions/_cower"
install -D -m644 config "/tmp/pacaurtmp-remy/cower/pkg/cower/usr/share/doc/cower/config"
==> Tidying install...
-> Purging unwanted files...
-> Removing libtool files...
-> Removing static library files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
==> Creating package "cower"...
-> Generating .PKGINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: cower 12-2 (tor jan 1 11:16:48 CET 2015)
==> Installing package cower with pacman -U...
loading packages...
warning: cower-12-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
cower 12-2 12-2 0,00 MiB
Total Installed Size: 0,06 MiB
Net Upgrade Size: 0,00 MiB
:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [#############################################] 100%
(1/1) checking package integrity [#############################################] 100%
(1/1) loading package files [#############################################] 100%
(1/1) checking for file conflicts [#############################################] 100%
(1/1) checking available disk space [#############################################] 100%
(1/1) reinstalling cower [#############################################] 100%
$ echo $LANG
da_DK.UTF-8
$ LANG=da_DK.UTF-8 pacaur -S cower
:: Package(s) cower not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...
:: cower-12-2 is up to date -- reinstalling
AUR Packages (1):
Name Old Version New Version
aur/cower 12-2 12-2 (cached)
:: Proceed with installation? [Y/n] y
:: Retrieving package(s)...
:: Installing cower cached package...
loading packages...
warning: cower-12-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
cower 12-2 12-2 0,00 MiB
Total Installed Size: 0,06 MiB
Net Upgrade Size: 0,00 MiB
:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [#############################################] 100%
(1/1) checking package integrity [#############################################] 100%
(1/1) loading package files [#############################################] 100%
(1/1) checking for file conflicts [#############################################] 100%
(1/1) checking available disk space [#############################################] 100%
(1/1) reinstalling cower
Offline
pacaur -Syu does more than installing package, the last step is cleaning the leftover.. which succeeds. But generally speaking, errors handling is most probably the main weakness of pacaur. There are several issues/feature requests open in the bugtracker.
I'm sure I don't need to tell you it should only give a non-zero exit status if all steps succeed. But in any case, pacaur -S [packagename] will also exit 0 after a failed gpg check.
Offline
I found your post because I had the same GPG key check problem for ffmpeg-full. I kept searching and found a solution which I posted at at https://aur.archlinux.org/packages/ffmpeg-full/ :
I found http://unix.stackexchange.com/questions … nd-tar-bz2 and just had to do this:
gpg --keyserver x-hkp://pool.sks-keyservers.net --recv-keys 0xD67658D8
to get it to work.
The argument for --recv-keys was found by trying to verify manually:
gpg --verify ffmpeg-2.5.2.tar.bz2.asc
.
Offline
I'm sure I don't need to tell you it should only give a non-zero exit status if all steps succeed. But in any case, pacaur -S [packagename] will also exit 0 after a failed gpg check.
Error exit codes should now behave as expected. Feedback welcome. You can test it out by installing the "pacaur-git" package.
Offline
Spyhawk -- thanks a lot. I can confirm the git version now works as expected (at least re: this issue). Thanks for getting on this.
piratejon -- thanks for you good intentions; I already solved the gpg issue on my own. I was just posting it here to illustrate the problem with pacaur.
Offline
Suddenly, dependencies are not being installed before the target packages.
For example, 'paper-gtk-theme-git' depends on 'gtk-engine-murrine', but murrine is never installed. And makepkg eventually fails when building the paper-gtk-theme-git package because dependencies haven't been met.
Similarly, installing 'gnome-multi-writer-git' fails because 'libgusb-stable' is needed. Notably, pacaur does prompt me to review the PKGBUILD for 'libgusb-stable', but still fails to install it first. Again, I can tell pacaur to install 'libgusb-stable', then later, install 'gnome-multi-writer-git'.
Those are just examples. This appears to reproduce for anything from the AUR that needs dependencies resolved. This behavior reproduces on three unique machines. All three machines have had pacaur and cower rebuilt (even if they didn't need it), expac reinstalled, and pacman-db-upgrade has been run (one was a new installation done around 12 hours ago, meaning, after the most recent pacaur PKGBUILD was pushed to the AUR).
Is anyone else hitting this? IRC was incredibly unhelpful, as usual.
Last edited by jswagner (2015-01-07 01:36:34)
Offline
@jswagner> Thanks for the report. My entire monkey-tester team is in extended vacation (due to a lack of banana) and a last minute change resulted in a code break. Should be quick-fixed in the newly released 4.2.17.
Last edited by Spyhawk (2015-01-07 06:29:01)
Offline
It appears I spoke too soon when I said the issue about exit codes was completely fixed. There seems to be a problem in the other direction now--I'm getting non-zero exit codes in circumstances where it seems as if no error occurred.
I'm having a hard time pinning down exactly under what conditions this obtains, mainly because my best guess is that this happens whenever it updates an AUR package, but the only way for me to test that hypothesis would be to create fake package updates and submit to AUR, and I don't want to do that.
However, last time I ran the command:
pacaur --noconfirm --noedit --noprogressbar -Syu
It gave the output in this pastebin -- I don't see anything there that qualifies as an error, but it gave me a non-zero exit code.
I'm using pacaur 4.2.17; let me know if I should go back to the git branch instead.
Offline
I'm using pacaur 4.2.17; let me know if I should go back to the git branch instead.
I fixed this issue in git branch a few days ago.
Offline
I am a devoted user of pacaur; thanks for this great tool. I would like to combine it with pacmatic, and this goes well except for one minor issue:
export PACMAN=pacmatic; pacaur -Syuv
leads to
Recent ML chatter: python(2), python2(1)
Root : /
Conf File : /etc/pacman.conf
DB Path : /var/lib/pacman/
Cache Dirs: /var/cache/pacman/pkg/
Lock File : /var/lib/pacman/db.lck
Log File : /var/log/pacman.log
GPG Dir : /etc/pacman.d/gnupg/
Targets : None
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
No pacnew files to update.
:: Starting AUR upgrade...
:: No is not present in AUR -- skipping
:: files is not present in AUR -- skipping
:: pacnew is not present in AUR -- skipping
:: to is not present in AUR -- skipping
:: update. is not present in AUR -- skipping
there is nothing to do
How to prevent this checking of "No pacnew files to update." in AUR?
Thanks in advance,
Theo
Offline
You're doing it wrong. It should work if you configure pacmatic to use pacaur instead of pacman.
Offline
Ok, got it, thanks.
Offline
Is it OK to ask in this thread what is the key advantage of pacaur over packer/apacman if someone happens to have used both these AUR helpers? (I'm asking because pacaur has another AUR dependency - cower, whereas apacman - doesn't.)
bing different
Offline
Is it OK to ask in this thread what is the key advantage of pacaur over packer/apacman if someone happens to have used both these AUR helpers? (I'm asking because pacaur has another AUR dependency - cower, whereas apacman - doesn't.)
Have you read the wiki page?
Also, a few reasons you might prefer packer over pacaur:
- does not need to be recompiled when a libalpm change occurs (unlike cower).
- interactive search ("packer pkg") like yaourt does. I won't implement this feature in pacaur.
- you like the name better.
Feel free to ask any more specific questions about pacaur.
Last edited by Spyhawk (2015-02-21 08:35:44)
Offline
pacaur hasn't worked for me in quite a while. It won't open any pkgbuilds for viewing and if I tell it to proceed with the install without viewing the pkgbuild I get this:
/usr/bin/pacaur: line 668: cd: /tmp/pacaurtmp-gary/snake-ncurses: No such file or directory
:: Checking snake-ncurses integrity...
==> ERROR: PKGBUILD does not exist.
:: failed to verify snake-ncurses integrity
Offline
bowhuntr> The snake-ncurses package correctly installs on my machine. I can view the PKGBUILD.
Check /tmp/pacaurtmp-gary/ folder permission. If you ever ran pacaur as root in the past, it might be possible that you lost write permission in this directory.
Offline
What should the permission be, my user?
Offline
What should the permission be, my user?
Yes, the /tmp folder should be accessible to the user (755).
Offline
The permissions are set for my user and the group users. I compared this folder and the yaourt folder in the same directory. They are the same.
Offline
The permissions are set for my user and the group users. I compared this folder and the yaourt folder in the same directory. They are the same.
Try removing the /tmp/pacaurtmp-gary/ folder entirely and try again.
If the issue still occurs, cd to the /tmp/pacaurtmp-gary/ directory as your user, and try "cower -d snake-ncurses". Check that the snake-ncurses is correctly created. Does it contains the PKGBUILD?
Offline
Ok, here is the problem:
cower: error while loading shared libraries: libalpm.so.8: cannot open shared object file: No such file or directory
Offline
This is a well known issue due to the new version of pacman released two months ago. Please refers to the wiki, or the numerous similar post in the forums.
Last edited by Spyhawk (2015-02-22 13:21:14)
Offline
If you are referring to rebuilding cower, I tried that, it won't build with yaourt due to a PGP signature not being verified.
Offline