You are not logged in.
Like others, I removed yaourt and package-query because they conflicted with pacman4... not worried about that, I'll reinstall them later.
I put the new pacman.conf in place (my old one wasn't really customized). I left SigLevel = Never.
Now, I can run pacman -Sy fine, but if I try to install anything, I it just hangs:
sudo pacman -S audacity
resolving dependencies...
looking for inter-conflicts...
Targets (1): audacity-1.3.14-2
Total Download Size: 3.21 MiB
Total Installed Size: 15.29 MiB
Net Upgrade Size: -0.00 MiB
Proceed with installation? [Y/n]
:: Retrieving packages from extra...
audacity-1.3.14-2-x86_64 3.2 MiB 1397K/s 00:02 [###########################] 100%
(1/1) checking package integrity [###########################] 100%
(1/1) loading package files [###########################] 100%
(1/1) checking for file conflicts [###########################] 100%
I've waited up to 20 or 30 minutes and nothing happens. It's not just audacity, any package I try to install does this.
Suggestions?
Last edited by TheAmigo (2012-01-17 18:55:38)
Offline
Having rebooted, it's working now so I'll mark it as solved.
Does pacman load any kernel modules? I was running 3.1.8, but had previously installed 3.1.9. Thus, without having rebooted, I was missing the modules for my current kernel (though I didn't expect to be loading any in the short term).
Offline
Same problem here. Does this mean pacman can no longer install packages after a kernel upgrade unless you reboot? That'd be sad, because rebooting is a pain, and I can't do it after every new kernel!
Is this a bug in pacman4? Or do we have to live with it?
Offline
With --debug switch it prints:
...
checking for file conflicts...
debug: looking for file conflicts
debug: searching for file conflicts: coreutils
debug: searching for filesystem conflicts: coreutils
debug: searching for file conflicts: ethtool
debug: searching for filesystem conflicts: ethtool
debug: searching for file conflicts: fail2ban
debug: searching for filesystem conflicts: fail2ban
debug: searching for file conflicts: gpgme
debug: searching for filesystem conflicts: gpgme
debug: searching for file conflicts: vim-runtime
debug: searching for filesystem conflicts: vim-runtime
debug: searching for file conflicts: gvim
debug: searching for filesystem conflicts: gvim
debug: searching for file conflicts: hdparm
debug: searching for filesystem conflicts: hdparm
debug: searching for file conflicts: inetutils
debug: searching for filesystem conflicts: inetutils
debug: searching for file conflicts: lib32-glibc
debug: searching for filesystem conflicts: lib32-glibc
debug: searching for file conflicts: lib32-gcc-libs
debug: searching for filesystem conflicts: lib32-gcc-libs
debug: searching for file conflicts: lib32-glib2
debug: searching for filesystem conflicts: lib32-glib2
debug: searching for file conflicts: lib32-gdk-pixbuf2
debug: searching for filesystem conflicts: lib32-gdk-pixbuf2
debug: searching for file conflicts: lib32-pango
debug: searching for filesystem conflicts: lib32-pango
debug: searching for file conflicts: lib32-gtk2
debug: searching for filesystem conflicts: lib32-gtk2
debug: searching for file conflicts: linux
debug: searching for filesystem conflicts: linux
debug: searching for file conflicts: nspluginwrapper
debug: searching for filesystem conflicts: nspluginwrapper
debug: searching for file conflicts: nvidia
debug: searching for filesystem conflicts: nvidia
debug: searching for file conflicts: qtwebkit
debug: searching for filesystem conflicts: qtwebkit
debug: searching for file conflicts: rpcbind
debug: searching for filesystem conflicts: rpcbind
debug: searching for file conflicts: unrar
debug: searching for filesystem conflicts: unrar
debug: searching for file conflicts: xscreensaver
debug: searching for filesystem conflicts: xscreensaver
checking available disk space...
debug: checking available disk space
Without the --debug switch
Proceed with installation? [Y/n]
(21/21) checking package integrity [############################] 100%
(21/21) loading package files [############################] 100%
(21/21) checking for file conflicts [############################] 100%
Note that the 'checking available disk space...' is not printed without the --debug option although it doesn't look like being 'debug output'.
I don't see much disk activity after that and the pacman process uses no CPU time and the process status goes to D in `ps` (man ps says: D: Uninterruptible sleep (usually IO)).
Last edited by drrossum (2012-01-18 21:58:28)
Offline
Offline
You were right, it was hanging at checking a nfs mount to a machine that went offline. Purging that mount solved the issue.
For who may need it: commenting out the "CheckSpace" option in pacman.conf avoids the problem, as a workaround.
Thanks!
Last edited by drrossum (2012-01-18 22:09:19)
Offline
Ah, that would explain my issue too... I tend to have transient nfs mounts.
Offline
As an aside, how do you guys mount your nfs shares?
I use autofs and I haven't seen this behavior from pacman but to be honest, I haven't tested this thoroughly. Also, falconindy is there a way to fix this without having to comment CheckSpace ? I would imagine many users don't remove their nfs mount each time they run pacman -- and sometimes some machines on my network do tend to be unavailable.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Also, falconindy is there a way to fix this without having to comment CheckSpace ?
I believe there are patches from falconindy on the pacman-dev mailing list that will avoid this issue.
Offline
Thanks Allan
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Just a quick note for anyone pulling their hair out. Pacman tends to choke on this step if you have an NFS partition mounted but your connection to the server has dropped. I get this all the time when I switch wireless networks without unmounting the NFS share of my home server.
Offline
Just a quick note for anyone pulling their hair out. Pacman tends to choke on this step if you have an NFS partition mounted but your connection to the server has dropped. I get this all the time when I switch wireless networks without unmounting the NFS share of my home server.
Thanks for reprising the thread. As Allan mentioned, this is fixed in pacman:
Offline