Arch Linux

Stefan_xyz

Member

Registered: 2019-09-01

Posts: 104

[Solved] filesystem: /bin exists in filesystem on system upgrade

Okay I just tried to update my system (using Linux 5.1.2.6) via

 pacman -Syu 

But I got the following error:

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/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/os-release exists in filesystem
filesystem: /usr/lib/sysctl.d/10-arch.conf exists in filesystem
filesystem: /usr/lib/systemd/system-environment-generators/10-arch exists in filesystem
filesystem: /usr/lib/sysusers.d/arch.conf exists in filesystem
filesystem: /usr/lib/tmpfiles.d/arch.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/factory/etc/crypttab exists in filesystem
filesystem: /usr/share/factory/etc/fstab exists in filesystem
filesystem: /usr/share/factory/etc/group exists in filesystem
filesystem: /usr/share/factory/etc/gshadow exists in filesystem
filesystem: /usr/share/factory/etc/host.conf exists in filesystem
filesystem: /usr/share/factory/etc/hosts exists in filesystem
filesystem: /usr/share/factory/etc/issue exists in filesystem
filesystem: /usr/share/factory/etc/ld.so.conf exists in filesystem
filesystem: /usr/share/factory/etc/motd exists in filesystem
filesystem: /usr/share/factory/etc/nsswitch.conf exists in filesystem
filesystem: /usr/share/factory/etc/passwd exists in filesystem
filesystem: /usr/share/factory/etc/profile exists in filesystem
filesystem: /usr/share/factory/etc/resolv.conf exists in filesystem
filesystem: /usr/share/factory/etc/securetty exists in filesystem
filesystem: /usr/share/factory/etc/shadow exists in filesystem
filesystem: /usr/share/factory/etc/shells exists in filesystem
filesystem: /usr/share/pixmaps/archlinux-logo.png exists in filesystem
filesystem: /usr/share/pixmaps/archlinux-logo.svg exists in filesystem
filesystem: /usr/share/pixmaps/archlinux.png exists in filesystem
filesystem: /usr/share/pixmaps/archlinux.svg exists in filesystem
filesystem: /var/lock exists in filesystem
filesystem: /var/mail exists in filesystem
filesystem: /var/run exists in filesystem
libnftnl: /usr/include/libnftnl/batch.h exists in filesystem
libnftnl: /usr/include/libnftnl/chain.h exists in filesystem
libnftnl: /usr/include/libnftnl/common.h exists in filesystem
libnftnl: /usr/include/libnftnl/expr.h exists in filesystem
libnftnl: /usr/include/libnftnl/flowtable.h exists in filesystem
libnftnl: /usr/include/libnftnl/gen.h exists in filesystem
libnftnl: /usr/include/libnftnl/object.h exists in filesystem
libnftnl: /usr/include/libnftnl/rule.h exists in filesystem
libnftnl: /usr/include/libnftnl/ruleset.h exists in filesystem
libnftnl: /usr/include/libnftnl/set.h exists in filesystem
libnftnl: /usr/include/libnftnl/table.h exists in filesystem
libnftnl: /usr/include/libnftnl/trace.h exists in filesystem
libnftnl: /usr/include/libnftnl/udata.h exists in filesystem
libnftnl: /usr/lib/libnftnl.so exists in filesystem
libnftnl: /usr/lib/libnftnl.so.11 exists in filesystem
libnftnl: /usr/lib/libnftnl.so.11.5.0 exists in filesystem
libnftnl: /usr/lib/pkgconfig/libnftnl.pc exists in filesystem
Errors occurred, no packages were upgraded.

I have encountered that error before and I'm aware that normally you can check the ownership and if the file belongs to no package you can move it (or straight up delete it), but here I'm not certain because

a) I have never dealt with directories before
b) the given directories are rather important directories and I don't fancy braking everything.

I actually don't mind the errors from libnftnl but the filesystem package errors rather worry me.
I have found this forum entry but I don't quite trust it since it's from 2013 (maybe it still is valid but not certain there) and (I think) they are talking about a testing environment or something of the like.
So if somebody has an idea what I should do or what guide / forum-thread I should follow that would be appreciated.

I'm upgrading the package from

 filesystem 2021.01.19-1 

to

 filesystem-2021.05.31-1 

Last edited by Stefan_xyz (2021-06-17 09:38:08)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,665

Re: [Solved] filesystem: /bin exists in filesystem on system upgrade

Sounds like your local DB got corrupted, try fixing the DB before actually installing the package

pacman -S filesystem --dbonly
pacman -Syu filesystem

Stefan_xyz

Member

Registered: 2019-09-01

Posts: 104

Re: [Solved] filesystem: /bin exists in filesystem on system upgrade

Sounds like your local DB got corrupted, try fixing the DB before actually installing the package

pacman -S filesystem --dbonly
pacman -Syu filesystem

That fixed it. Thanks!