Package Details: pkgbrowser 0.22-2

Git Clone URL: https://aur.archlinux.org/pkgbrowser.git (read-only, click to copy)
Package Base: pkgbrowser
Description: A utility for browsing pacman databases and the AUR
Upstream URL: https://bitbucket.org/kachelaqa/pkgbrowser
Licenses: GPL2
Submitter: kachelaqa
Maintainer: kachelaqa
Last Packager: kachelaqa
Votes: 273
Popularity: 0.37
First Submitted: 2011-04-20 18:18
Last Updated: 2019-11-14 22:19

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

kachelaqa commented on 2015-07-19 16:56

@majo. Looks like the "bug" is at your end. Everything works fine for me.

majo commented on 2015-07-19 09:35

I see this bug:

$ pkgbrowser
Traceback (most recent call last):
File "/usr/lib/pkgbrowser/main.py", line 9, in <module>
sys.exit(app.run())
File "/usr/lib/pkgbrowser/pkgbrowser/app.py", line 114, in run
app.window().setup()
File "/usr/lib/pkgbrowser/pkgbrowser/app.py", line 58, in window
from pkgbrowser.window import Window
File "/usr/lib/pkgbrowser/pkgbrowser/window.py", line 16, in <module>
from pkgbrowser.backend import (
File "/usr/lib/pkgbrowser/pkgbrowser/backend.py", line 13, in <module>
from pkgbrowser import alpm, conf, utils
ImportError: /usr/lib/pkgbrowser/pkgbrowser/alpm.cpython-34m.so: undefined symbol: AnnotateIgnoreReadsEnd

kachelaqa commented on 2015-04-19 21:30

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

rcrath commented on 2015-04-19 20:57

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

JKAbrams commented on 2015-03-29 15:48

I got this after the update of python:

ImportError: /usr/lib/pkgbrowser/pkgbrowser/alpm.cpython-34m.so: undefined symbol: AnnotateIgnoreReadsEnd

Solution: rebuild pkgbrowser

kachelaqa commented on 2015-02-07 17:57

@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.

Thah commented on 2015-02-07 09:36

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...

cda commented on 2015-01-04 11:40

After the last update pkgbrowser does not work.

└─[$]> pkgbrowser
Traceback (most recent call last):
File "/usr/lib/pkgbrowser/main.py", line 9, in <module>
sys.exit(app.run())
File "/usr/lib/pkgbrowser/pkgbrowser/app.py", line 114, in run
app.window().setup()
File "/usr/lib/pkgbrowser/pkgbrowser/app.py", line 58, in window
from pkgbrowser.window import Window
File "/usr/lib/pkgbrowser/pkgbrowser/window.py", line 16, in <module>
from pkgbrowser.backend import (
File "/usr/lib/pkgbrowser/pkgbrowser/backend.py", line 13, in <module>
from pkgbrowser import alpm, conf, utils
ImportError: libalpm.so.8: cannot open shared object file: No such file or directory

└─[$]> ls /usr/lib |grep libalpm
libalpm.so
libalpm.so.9
libalpm.so.9.0.0

OldNuc commented on 2014-12-31 00:50

Removed and rebuilt from tarball, fixed problem. Thanks!

I think I may have just done a reinstall following the update.

OldNuc commented on 2014-12-31 00:21

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