or we can use in stable
or we can use in stable
4.23.2-1 just now, it’s pretty broke…
-> % sudo pacman-mirrors --geoip Traceback (most recent call last): File "/usr/bin/pacman-mirrors", line 20, in <module> from pacman_mirrors import pacman_mirrors ModuleNotFoundError: No module named 'pacman_mirrors'
I simply installed
shiny-mirrors to get over the hump for now.
yay now says this about
-> % yay -Suy :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... there is nothing to do :: Searching databases for updates... :: Searching AUR for updates... -> Missing AUR Packages: pacman-mirrors there is nothing to do
yay think that
pacman-mirrors was from the AUR all of a sudden?
Thank you, this helped to make it work again.
Thank you man!!!
I was unaware of shiny-mirrors. Thanks for the info!
Hi, I just did a fresh installation of Manjaro and after updating to the new pacman-mirrors version (4.23.2-1) my package manager crashes, when opening the settings.
sudo pacman -U /var/cache/pacman/pkg/pacman-mirrors-4.23.1-5-any.pkg.tar.zst
Thanks, but for some reason, I only have the new version in the cache. Not sure if I updated anything at all or it’s just the fresh install.
Now you just have to wait for your mirrors to sync and then
sudo pacman -Syyu
Works again for me Big Thanks!
Well, there was just an update to
pacman-mirrors and things seem even worse now…
Package (1) Old Version New Version Net Change Download Size core/pacman-mirrors 4.23.2-1 4.23.2-1.1 0.00 MiB 0.17 MiB
-> % sudo pacman-mirrors --geoip ::WARNING https://repo.manjaro.org 'Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fd89e8ddf70>, 'Connection to repo.manjaro.org timed out. (connect timeout=2)'))' ::INFO Downloading mirrors from Manjaro ::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json ::ERROR Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Read timed out. (read timeout=2) ::INFO => Mirror status: https://repo.manjaro.org/status.json ::ERROR Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Read timed out. (read timeout=2) ::INFO User generated mirror list
I’m typing this on the same machine so I know it’s online and able to resolve “manjaro.org”…
Above I see you installed
shiny-mirrors, can you tell me if
shiny-mirrors is able to resolve the address and so on?
It seems weird that it would be caused by
pacman-mirrors itself, I think it was just some error fluke in dns query request or something, try it again with
Got the same issue, pacman manager crashes when i open the Preferences
All good on my side after this.
After some time has passed, it is resolving OK now.
-> % sudo pacman-mirrors --geoip ::INFO Downloading mirrors from Manjaro ::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json ::INFO => Mirror status: https://repo.manjaro.org/status.json ::INFO User generated mirror list ::------------------------------------------------------------ ::INFO Custom mirror file saved: /var/lib/pacman-mirrors/custom-mirrors.json ::INFO Using default mirror file ::INFO Querying mirrors - This may take some time 0.345 United_States : https://repo.ialab.dsu.edu/manjaro/ 0.732 United_States : https://mirrors.ocf.berkeley.edu/manjaro/ 0.120 United_States : https://mirror.math.princeton.edu/pub/manjaro/ 0.244 United_States : https://mirrors.gigenet.com/manjaro/ 0.553 United_States : https://mirrors.sonic.net/manjaro/ ::INFO Writing mirror list ::United_States : https://mirror.math.princeton.edu/pub/manjaro/stable ::United_States : https://mirrors.gigenet.com/manjaro/stable ::United_States : https://repo.ialab.dsu.edu/manjaro/stable ::United_States : https://mirrors.sonic.net/manjaro/stable ::United_States : https://mirrors.ocf.berkeley.edu/manjaro/stable ::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
I have the same issue. Applied this solution and everything is fine now.
Did I mention it was fixed with 4.23.2-1.1?
No other “solutions” required.