this post was submitted on 07 Sep 2024
4 points (83.3% liked)
Arch Linux
7761 readers
21 users here now
The beloved lightweight distro
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would check that your pacman mirror is not out of date and sees the new package.
giving this a try:
sudo reflector --latest 10 --protocol https --country 'United States' --sort rate --save /etc/pacman.d/mirrorlist
no luck. still getting:
error: target not found: python-polib
What mirror entry ended up in at the top after running reflector? I can just check the mirror directly.
The package comes up for me just fine on whatever I have for a mirror currently. I'll have to look in a bit what mirror I use
output:
Server = https://arch.mirror.constant.com/$repo/os/$arch
Server = https://mirrors.rit.edu/archlinux/$repo/os/$arch
Server = https://us.mirrors.cicku.me/archlinux/$repo/os/$arch
Server = https://america.mirror.pkgbuild.com/$repo/os/$arch
Server = https://mirrors.vectair.net/archlinux/$repo/os/$arch
Server = https://mirrors.lug.mtu.edu/archlinux/$repo/os/$arch
Server = https://arch.hu.fo/archlinux/$repo/os/$arch
Server = https://archmirror1.octyl.net/$repo/os/$arch
Server = https://mirror.theash.xyz/arch/$repo/os/$arch
Server = https://us.arch.niranjan.co/$repo/os/$arch
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?
absolutely. i've tried this on two x86 systems as well, my desktop and laptop. if there's no quick fix or obvious problem, i'm not above doing a full reinstall to fix this.
i'll spin up a vm to test too
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?
yep, dns points me to 108.61.5.83 and i can get there by hostname and address thru the browser. i spun up a new live arch session i built with archiso. still can't get a hit thru pacman tho. really can't explain it.
Entertain me, what's the output of
pacman -Qi python| grep Architecture
?pacman -Qi python | grep Architecture
yieldsArchitecture : x86_64
this is very, very strange behavior you're seeing then. I have the following in my
/etc/pacman.conf
Does yours look like that?
and for mirror list, I have the following mirrors:
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.okay i got it now.
was something wrong with the mirror i was using? if so, is there some way to know if i have a "lesser" mirror? or was the arch linux world just going thru a major update today and i had to wait it out?
My only gut 'guess' is that your original mirror was out of date, then you happened to switch to one mid sync potentially.
thanks so much for the coaching!
that asciicinema thing is super cool too
so... i did another reflector refresh and then did an Syyu. Now this is happening...
this is with the mirrorlist shown in the picture below. not sure why i'd be getting almost 3 gigs of updates right now. i've been updating this and using this machine daily for months on this installation. when that is complete i'll try for python-polib again.
about 15 ruby packages got replaced with extra/ruby just now too.
well... thats a good sign at least. hopefully it finally latched on to some working mirrors then. I'd surely think it should find that library now lol