Axum
this is very, very strange behavior you’re seeing then.
I have the following in my /etc/pacman.conf
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
Does yours look like that?
and for mirror list, I have the following mirrors:
Server = https://mirror.stephanie.is/archlinux/$repo/os/$arch
Server = https://nocix.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://ohioix.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://mnvoip.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://arch.mirror.ivo.st/$repo/os/$arch
these settings yield me the python library just fine
Edit: the multilib repo is optional in the pacman.conf, as the package you want is in the extra
repo.
I suppose you could also clean out cached packages with pacman -Scc
and then delete the package database files in /var/lib/pacman/sync
so that you know for a fact that you are getting a fresh sync and it not depending on anything cached.
but the package is certainly there, are you able to directly download it from https://arch.mirror.constant.com/extra/os/x86_64/python-polib-1.2.0-2-any.pkg.tar.zst from a browser so we can rule out any weird dns fuckiness?
Well for the arch.mirror.constant.com mirror at the top, its certainly there.
so doing pacman -Syyu python-polib
Should find the package.
For sanity’s sake, you are on a X86_64 system, right?
I would check that your pacman mirror is not out of date and sees the new package.