Arch Linux User Repository

require python 3.14 and not 3.14.2

Is the python<3.14 really needed ? Isn't enough to say that it need python>3.2 ?

@kachelaqa, with the new python 3.14 in testing, you will need to fix the PKGBUILD, just changed to "<3.15" and it worked fine.

Please, also fix the menu "help/about" which points to an non existing page (https://osdn.net/projects/pkgbrowser)...

Thanks for this great project!

wchouser3 you have to recompile the package anyway so not much of a deal IMO other solution would be disabling dependency checks, but I would not recommend that

Ive used this tool for many years now. Every now and then I have to uninstall it so that my system will update without running into a dependency problem. And then re-install it after the system is done updating. Does anyone know how I can avoid this?

tnx. solved.

@simona, you can edit the PKGBUILD line 10 and change to 'pacman<7.2', it will work fine! If you want to try, I uploaded a new package to my sourceforge page, see my account details for the link.

incompatible with pacman 7.1

@Cody_Learner See: https://bbs.archlinux.org/viewtopic.php?id=309590. It appears to be an intermittent problem. There's nothing pkgbrowser can do about it, as it's a purely server-side issue. Note that this only seems to effect the cgit backend, rather than rpc or the website. If you keep trying, pkgbrowser will eventually fetch the required data.

@Popolon, I just rebuilt the package w/o issues. Try building in clean chroot? Complete build output if it's helpful: http://0x0.st/KOoe.txt

python3 -m compileall -ql pkgbrowser pkgbrowser/ui
running build_ext
building 'pkgbrowser.alpm' extension
creating build/src
gcc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -flto=auto -fPIC -I/usr/include/python3.13 -c src/alpm.c -o build/src/alpm.o
creating build/lib.linux-x86_64-cpython-313/pkgbrowser
gcc -shared -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -flto=auto build/src/alpm.o -L/usr/lib -lalpm -o build/lib.linux-x86_64-cpython-313/pkgbrowser/alpm.cpython-313-x86_64-linux-gnu.so
copying build/lib.linux-x86_64-cpython-313/pkgbrowser/alpm.cpython-313-x86_64-linux-gnu.so -> pkgbrowser
rm -vrf build
removed 'build/src/alpm.o'
removed directory 'build/src'
removed 'build/lib.linux-x86_64-cpython-313/pkgbrowser/alpm.cpython-313-x86_64-linux-gnu.so'
removed directory 'build/lib.linux-x86_64-cpython-313/pkgbrowser'
removed directory 'build/lib.linux-x86_64-cpython-313'
removed directory 'build'
==> Entering fakeroot environment...
==> Starting package()...

.

@kachelaqa, I'm getting 502 Bad Gateway errors when I click on AUR pkgs listed after a search.

Not every time though, ~50%.
Could this be related to potential rate limit changes to aur.archlinux.org/rpc due to the recent ddos attacks?
Whenever I get the error, I can use the web interface for the pkg.

FYI: I did just rebuild, reinstall, and confirmed a rebuild didn't fix it.

.