You are not logged in.
Pages: 1
im having trouble upgrading the filesystem
sudo pacman -Q filesystem
filesystem 2014.06-1
sudo pacman -S filesystem
resolving dependencies...
looking for inter-conflicts...
Packages (1): filesystem-2014.06-2
Total Installed Size: 0.01 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [#####################] 100%
(1/1) checking package integrity [#####################] 100%
(1/1) loading package files [#####################] 100%
(1/1) checking for file conflicts [#####################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /etc/arch-release exists in filesystem
filesystem: /etc/mtab exists in filesystem
filesystem: /etc/os-release exists in filesystem
filesystem: /etc/profile.d/locale.sh exists in filesystem
filesystem: /lib exists in filesystem
filesystem: /lib64 exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/lib/modprobe.d/usb-load-ehci-first.conf exists in filesystem
filesystem: /usr/lib64 exists in filesystem
filesystem: /usr/local/share/man exists in filesystem
filesystem: /usr/sbin exists in filesystem
filesystem: /usr/share/man/man7/archlinux.7.gz exists in filesystem
filesystem: /var/lock exists in filesystem
filesystem: /var/mail exists in filesystem
filesystem: /var/run exists in filesystem
Errors occurred, no packages were upgraded.
should i --force it or delete all the stuff in these directories?
pacman -Qqo /bin /sbin /usr/sbin /lib64 /lib | pacman -Qm -
error: No package owns /bin
error: No package owns /sbin
error: No package owns /usr/sbin
error: No package owns /lib64
error: No package owns /lib
Offline
What's the output of
stat -c %s /var/lib/pacman/local/filesystem-2014.06-1/files
?
Offline
stat -c %s /var/lib/pacman/local/filesystem-2014.06-1/files
0
possibly unrelated detail, everything is spontaneously segfaulting.
Last edited by ktfh (2014-07-03 21:41:42)
Offline
Something happened to your package database. Generally in such situations you have to force the update of this package. Since this is the filesystem package, it's even more risky.
You can cross your fingers and just do it or wait for somebody else to come here, maybe with a better idea.
Offline
stat -c %s /var/lib/pacman/local/filesystem-2014.06-1/files 0
possibly unrelated detail, everything is spontaneously segfaulting.
Sounds like a bad case of filesystem corruption to me. Check the health of your drive from a liveCD, and back up anything you don't already have a backup of.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I forced the update through and everything seems fine now. No segfaults yet. Should i delete these directories to prevent the error in the future?
filesystem: /bin exists in filesystem
filesystem: /etc/arch-release exists in filesystem
filesystem: /etc/mtab exists in filesystem
filesystem: /etc/os-release exists in filesystem
filesystem: /etc/profile.d/locale.sh exists in filesystem
filesystem: /lib exists in filesystem
filesystem: /lib64 exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/lib/modprobe.d/usb-load-ehci-first.conf exists in filesystem
filesystem: /usr/lib64 exists in filesystem
filesystem: /usr/local/share/man exists in filesystem
filesystem: /usr/sbin exists in filesystem
filesystem: /usr/share/man/man7/archlinux.7.gz exists in filesystem
filesystem: /var/lock exists in filesystem
filesystem: /var/mail exists in filesystem
filesystem: /var/run exists in filesystem
Offline
No, let them be.
The problem was with the package database. The files and the directories themselves are fine and they are of vital importance.
Offline
filesystem was most likely replacing directories with symlinks, you can check if you want but I know for a fact
/bin
/sbin
/lib64
/lib
are all symlinks now, and removing them is probably the fastest way to brick your machine, or at least it used to be.
Offline
l0vot, that symlink change happened a long long time ago and OP was using filesystem 2014.06-1, so his system was up to date before it suffered some corruption.
Offline
Pages: 1