Package Details: pkgbrowser 0.28-1

Git Clone URL: (read-only, click to copy)
Package Base: pkgbrowser
Description: A utility for browsing pacman databases and the AUR
Upstream URL:
Licenses: GPL2
Submitter: kachelaqa
Maintainer: kachelaqa
Last Packager: kachelaqa
Votes: 279
Popularity: 0.26
First Submitted: 2011-04-20 18:18 (UTC)
Last Updated: 2023-05-05 13:24 (UTC)

Latest Comments

1 2 3 4 5 6 .. 18 Next › Last »

nimbusflow commented on 2023-05-31 23:53 (UTC)

Just a quick note to let you know that I looked into this again last week and was able to fix it.

Before trying your suggestions, I tried rebuilding pkgbrowser once again but this time I made sure I cleared my local cache first (yay -Scc). Not sure I had done it before to be honest. All good now, thanks for your help!

nimbusflow commented on 2023-05-12 21:11 (UTC) (edited on 2023-05-12 21:12 (UTC) by nimbusflow)

(sorry both, can't test any of the suggestions at the moment)

@rafaelff: thanks - literally the first thing I tried, before my first post even!

@kachelaqa: cool, thanks. For the record, I just was saying the justification you provided didn't apply in my case (because I did the exact opposite), not the actual suggested fix. For the sake of clarity, the sequence I went through last week before posting my first comment was 'upgrade pkgbrowser' -> 'full system upgrade' -> 'reinstall pkgbrowser' (after realising it wasn't working)

rafaelff commented on 2023-05-12 19:57 (UTC)

Yeah, first perform a full system upgrade (-Syu) and then rebuild pkgbrowser

kachelaqa commented on 2023-05-12 19:31 (UTC)

@nimbusflow Actually, it does apply, because either way you'll end up with a compiled extension (alpm) that is built for the wrong version of python. That's why you see the exception ImportError: cannot import name 'alpm'.

nimbusflow commented on 2023-05-12 18:04 (UTC) (edited on 2023-05-12 18:04 (UTC) by nimbusflow)

@rafaelff: thanks, I'll give that a try. I should have been clearer, I only deleted what was relevant to pkgbrowser. No other files were harmed in the debugging of this package!

@kachelaqa: I had to upgrade pkgbrowser before I upgraded python as the 3.10 dependency was stopping me from updating my system, so your suggestion doesn't apply to my case. I'll check /usr/lib/pkgbrowser/ anyway though, thanks.

kachelaqa commented on 2023-05-09 19:02 (UTC)

@rafaelff There was no point checking site-packages at all, because pkgbrowser does not install anything in there. As I suggested earlier, there are probably some stale cached files generated when python was upgraded before upgrading pkgbrowser. So look at the /usr/lib/pkgbrowser/ directory, and check whether its modification time differs from any of the files it contains. (Alternatively, remove pkgbrowser with pacman, and then check whether /usr/lib/pkgbrowser/ still exists - and if so, what files it contains).

rafaelff commented on 2023-05-09 18:20 (UTC)

You should definitely not go removing contents from /usr/lib/python3.10/site-packages/ without checking, as you could leave an incomplete package installed.

Lets try something more straightforward, building in a clean chroot:

sudo pacman -S devtools
git clone
cd pkgbrowser
sudo pacman -U pkgbrowser-0.28-1-x86_64.pkg.tar.zst

nimbusflow commented on 2023-05-09 18:00 (UTC)

Thanks for the feedback, rafaelff

In my case, the version is shown as 'Python 3.11.3' when I run that command. Deleting the contents of /usr/lib/python3.10/site-packages/ doesn't seem to make any difference either, same output.

Not sure if Pietro can corroborate similar behaviour.

rafaelff commented on 2023-05-08 20:57 (UTC)

I suggest checking /usr/lib/python3.10/site-packages/ for leftovers of Python 3.10.

Also, make sure python --version gives 3.11, and not another custom version.