You are not logged in.
It has been a while since I ran the last pacman update, and now when I do it, pacman hangs on checking the packages.
I've interrupted the check after half an hour, deleted the pacman lock and ran again, and it gets stuck on the same point, package 291 of 511.
After the update there was an error about one package taking too long to download. I deleted it and it redownloaded smoothly, but it didn't solve it.
So I suppose there is one package in my recent update that causes this and that may be corrupted in some special way. How can I find out which package it is ?
And why does it hang and not simply say the package is corrupted ?
What are other approaches to fix this ?
I imagine I could list all the packages in my pacman cache, delete all the ones downloaded today and try again, but I am not sure how to do this from the terminal.
Last edited by nourathar (2024-07-02 19:59:18)
Offline
A lot to say, but why no command line output? What package/version hangs? Post the terminal output (copy paste in code block).
System maintenance lacking? https://wiki.archlinux.org/title/system_maintenance
Specifically, '4.3 Update the mirrorlist'
I am not sure how to do this from the terminal.
I'd guess maintaining Arch without knowing your way around the terminal would be a challenge to say the least.
Last edited by NuSkool (2024-07-02 19:18:46)
Offline
Have you tried an different mirror ?
Last edited by cmm11 (2024-07-02 19:43:51)
$20 Free Credit Hetzner - https://hetzner.cloud/?ref=fuVilhv403fA
Offline
Thanks for your reply !
A lot to say, but why no command line output? What package/version hangs? Post the terminal output (copy paste in code block).
pacman does not actually provide feedback when checking packages in the same way when it installs them. Not in normal mode and not in verbose mode.
So there is no terminal output to show you.
Which is why I asked how I could find out which package causes the problem.
I am not sure how to do this from the terminal.
I'd guess maintaining Arch without knowing your way around the terminal would be a challenge to say the least.
There are many things I can do in the terminal, but deleting only today's files from a directory does not happen to be one of them.
I solved it by moving the contents of the pacman cache elsewhere, rerunning the update and moving the old contents of the cache back without overwriting the freshly downloaded packages.
No idea what caused pacman to hang on verifying one package like that.
In the journals I found this from the first time I tried to update:
Jul 02 17:56:25 box sudo[16185]: me: TTY=pts/1 ; PWD=/home/me ; USER=me ; COMMAND=/usr/bin/pacman -Syu
Jul 02 18:05:16 box kernel: BUG: Bad page state in process pacman pfn:35e424
Jul 02 18:05:16 box kernel: CPU: 2 PID: 16190 Comm: pacman Not tainted 6.8.9-arch1-2 #1 2add8ee915b565df906f38100dd434d161273f2d
Offline