"exists in filesystem" in a new install

[guisacouto]

Hi,

I've done a fresh sdcard install recently with the latest image, but however I'm getting a lot of erros while updating..

$this->bbcode_second_pass_code('', '
pam: /usr/share/man/man5/time.conf.5.gz exists in filesystem
pam: /usr/share/man/man8/PAM.8.gz exists in filesystem
pam: /usr/share/man/man8/mkhomedir_helper.8.gz exists in filesystem
pam: /usr/share/man/man8/pam.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_access.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_cracklib.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_debug.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_deny.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_echo.8.gz exists in filesystem
pam: /usr/share/man/man8/pam_env.8.gz exists in filesystem
(...)
dbus-core: /etc/dbus-1/session.conf exists in filesystem
dbus-core: /etc/dbus-1/system.conf exists in filesystem
dbus-core: /etc/rc.d/dbus exists in filesystem
dbus-core: /usr/bin/dbus-cleanup-sockets exists in filesystem
dbus-core: /usr/bin/dbus-daemon exists in filesystem
dbus-core: /usr/bin/dbus-monitor exists in filesystem
dbus-core: /usr/bin/dbus-send exists in filesystem
dbus-core: /usr/bin/dbus-uuidgen exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-address.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-bus.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-connection.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-errors.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-macros.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-memory.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-message.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-misc.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-pending-call.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-protocol.h exists in filesystem
dbus-core: /usr/include/dbus-1.0/dbus/dbus-server.h exists in filesystem
(...)
gcc-libs: /usr/lib/libgfortran.so exists in filesystem
gcc-libs: /usr/lib/libgfortran.so.3 exists in filesystem
gcc-libs: /usr/lib/libgfortran.so.3.0.0 exists in filesystem
gcc-libs: /usr/lib/libgomp.so exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1 exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1.0.0 exists in filesystem
gcc-libs: /usr/lib/libitm.so exists in filesystem
gcc-libs: /usr/lib/libitm.so.1 exists in filesystem
gcc-libs: /usr/lib/libitm.so.1.0.0 exists in filesystem
gcc-libs: /usr/lib/libmudflap.so exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libobjc.so exists in filesystem
(...)
iputils: /usr/bin/ping6 exists in filesystem
iputils: /usr/sbin/arping exists in filesystem
iputils: /usr/sbin/clockdiff exists in filesystem
iputils: /usr/sbin/rarpd exists in filesystem
iputils: /usr/sbin/rdisc exists in filesystem
iputils: /usr/sbin/tftpd exists in filesystem
iputils: /usr/sbin/tracepath exists in filesystem
iputils: /usr/sbin/tracepath6 exists in filesystem
iputils: /usr/share/man/man8/arping.8.gz exists in filesystem
iputils: /usr/share/man/man8/clockdiff.8.gz exists in filesystem
iputils: /usr/share/man/man8/ping.8.gz exists in filesystem
iputils: /usr/share/man/man8/ping6.8.gz exists in filesystem
iputils: /usr/share/man/man8/rarpd.8.gz exists in filesystem
iputils: /usr/share/man/man8/rdisc.8.gz exists in filesystem
(...)
linux-api-headers: /usr/include/asm-generic/statfs.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/swab.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/termbits.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/termios.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/types.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/ucontext.h exists in filesystem
linux-api-headers: /usr/include/asm-generic/unistd.h exists in filesystem
linux-api-headers: /usr/include/asm/a.out.h exists in filesystem
linux-api-headers: /usr/include/asm/auxvec.h exists in filesystem
linux-api-headers: /usr/include/asm/bitsperlong.h exists in filesystem
(..........)
')

What should I do? I have forced it once when I first updated it but haven't done it again..

Best regards,

Guilherme

[guisacouto]

I really don't like to bump threads, but I really need some advice.. to force or not to force?

best regards

[pepedog]

I suspect this is corruption. Typically each file is actually owned by the file trying to install or upgrade to it.
You might as well try pacman -Syuf
Or reinstall.
Just for fun, what does pacman -Qq say, it should list installed pkgs
Then try pacman -Qo /path/to/one/of/those/files

[guisacouto]

Tks for the reply pepedog!

pacman -Qq lists all the packages correctly.. pacman -Qq <file> for instance tells me no package owns the <file>

$this->bbcode_second_pass_code('', '
guilherme:~$ pacman -Qo /usr/share/man/man8/pam_cracklib.8.gz
error: No package owns /usr/share/man/man8/pam_cracklib.8.gz
')

I guess I will force it and then retest this.. If after the update with force the files start to be owned by the package it means its fixed right?

best regards

edit:

After the force, now the files are owned by the packages : ) tks!