Arch Linux User Repository

@rcrath. what update are you talking about? everything still works perfectly fine for me...

update breaks, need to download & extract tarball and run makepkg -i in the pkgbrowser folder and then it works fine

I got this after the update of python: ImportError: /usr/lib/pkgbrowser/pkgbrowser/alpm.cpython-34m.so: undefined symbol: AnnotateIgnoreReadsEnd Solution: rebuild pkgbrowser

@Thah Please make a proper bug report (either on the upstream issue tracker, or on the arch forum thread). It would also be a good idea to delete your comment here, as most of it is not relevant to the AUR.

Build fails on systems with non-Bash /bin/sh Background: In the aftermath of the Shellshock vulnerability it was pointed out that Bash is not the most reasonable choice for a system shell. I changed it to point to /usr/bin/dash. Build failure: Running makepkg ends with > removed directory: ‘build/src’ > removed directory: ‘build’ > for f in designer/[^_]*.ui; do \ > /usr/bin/pyuic4 --from-imports -w -o "pkgbrowser/ui/$(basename $f .ui).py" > "$f"; > \ > done > Error: No such file or directory: "designer/[^_]*.ui" > Makefile:35: recipe for target 'pyqt' failed > make: *** [pyqt] Error 1 > ==> ERROR: A failure occurred in build(). > Aborting... > $ Explanation: make does not use the user's $SHELL environment variable as a shell (see (p)info make, 5.3.2 Choosing the Shell) on recipe lines but /bin/sh. Patching the Makefile with *** 20,25 **** --- 20,27 ---- distname := $(APPNAME)-$(VERSION) source := $(distdir)/$(distname) + export SHELL := /bin/bash + all: alpm pyqt scripts compile cython: and rebuilding with makepkg -e succeeds. Running checkbashisms -f on the Makefile reports among other things > possible bashism in Makefile line 37 ([^] should be [!]): > for f in designer/[^_]*.ui; do \ > $(PYUIC) --from-imports -w -o "$(APPNAME)/ui/$$(basename $$f .ui).py" > "$$f"; \ > done The above and comparing the man pages for bash/dash show that checkbashisms's output is correct. Fix: A quick fix is explicitly telling make to use Bash as above (or maybe /usr/bin/bash ? ). In this case there should be a build dependency on Bash although Bash would be installed on almost all systems anyway. A more elegant solution would be to avoid bashisms at all but I haven't checked the makefile for other bashisms. OTOH sticking to POSIX compliant recipe lines would avoid any problems with possible shell changes in the future. In any case, as /bin/sh is supposed to be POSIX compliant and nothing more it should not be used for cases, that use more that POSIX. In this case the use of /bin/sh is disguised quite well...

Removed and rebuilt from tarball, fixed problem. Thanks! I think I may have just done a reinstall following the update.

@ GSF1200S I will give that a shot as I did rebuild pkgbrowser right after the update but It may have missed something.

@ OldNuc Have you rebuilt PkgBrowser SINCE you updated pacman? I updated pacman first, then built PkgBrowser the following day when kachelaqa released the update- no problems here. I think you simply need to rebuild PkgBrowser so its built against the correct libalpm...

pkgbrowser 0.18-2 failing with following error. Package-query rebuilt to 1.5-2 12/30/15 and same eror no longer failing yaourt. Traceback (most recent call last): [trimmed to initial error] ImportError: libalpm.so.8: cannot open shared object file: No such file or directory