Many file conflicts after a pause in updates

This forum is for topics dealing with problems with software specifically in the ARMv7h repo.

Many file conflicts after a pause in updates

Postby nbd » Fri May 26, 2017 2:59 pm

Greetings,

I have a pause in updating the Alarm on Raspberry Pi 2, maybe 7 or 8 months, and today when I tried to 'pacman -Syu' I got 263 packages to update and a long list of 'file exists' errors like these (this is only a small fragment):
Code: Select all
linux-api-headers: /usr/include/sound/tlv.h exists in filesystem
linux-api-headers: /usr/include/sound/usb_stream.h exists in filesystem
tzdata: /usr/share/zoneinfo/Asia/Tomsk exists in filesystem
tzdata: /usr/share/zoneinfo/Europe/Kirov exists in filesystem
tzdata: /usr/share/zoneinfo/posix/Asia/Tomsk exists in filesystem
tzdata: /usr/share/zoneinfo/posix/Europe/Kirov exists in filesystem
tzdata: /usr/share/zoneinfo/right/Asia/Tomsk exists in filesystem
tzdata: /usr/share/zoneinfo/right/Europe/Kirov exists in filesystem
glibc: /usr/share/i18n/locales/chr_US exists in filesystem
glibc: /usr/share/i18n/locales/de_IT exists in filesystem
glibc: /usr/share/i18n/locales/de_LI exists in filesystem
glibc: /usr/share/i18n/locales/en_IL exists in filesystem
glibc: /usr/share/i18n/locales/eo exists in filesystem
glibc: /usr/share/i18n/locales/ln_CD exists in filesystem
glibc: /usr/share/i18n/locales/sgs_LT exists in filesystem
gcc-libs: /usr/lib/libatomic.so.1.2.0 exists in filesystem
gcc-libs: /usr/lib/libgo.so.9 exists in filesystem
gcc-libs: /usr/lib/libgo.so.9.0.0 exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6.0.22 exists in filesystem
diffutils: /usr/share/locale/ca/LC_MESSAGES/diffutils.mo exists in filesystem
diffutils: /usr/share/locale/cs/LC_MESSAGES/diffutils.mo exists in filesystem


Is there a way for this to be corrected without complete reinstalling Alarm?

<< nbd
nbd
 
Posts: 14
Joined: Sun Sep 13, 2015 9:55 pm

Re: Many file conflicts after a pause in updates

Postby RMJ » Fri Jun 02, 2017 4:30 pm

This usually happens to me with corrupted data.
If you try to get the size of the file, I bet it will be all the same "0" bytes...

Try forcing an reinstalation of the package with
pacman -S package_that_contains_the_Files --force

I usually do this manually, one by one, finding out what package must be reinstaled at the time, to avoid worse problems, but I think you could also run:
pacman -Syu --force
RMJ
 
Posts: 31
Joined: Fri May 05, 2017 9:32 pm


Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 4 guests