You are not logged in.

Pages: 1

#1 2020-02-29 09:45:54

IzzyGiessen
Member
Registered: 2020-02-29
Posts: 4

error: failed to commit transaction (conflicting files)

I've had Arch for some time now, but during the last upgrade of pacman, I got this error:
error: failed to commit transaction (conflicting files)

I tried the recommended solutions on the Arch wiki. The conflicting files weren't owned by any other package, so I tried to rename them, but apparently they are necessary for pacman to upgrade. This sounds to me like I can't upgrade if I still have the files, but I need the files to upgrade.

The full output is:

error: failed to commit transaction (conflicting files)
pacman: /usr/lib/libalpm.so.12 exists in filesystem
pacman: /usr/lib/libalpm.so.12.0.1 exists in filesystem
pacman: /usr/share/locale/sl/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/makepkg/buildenv.sh exists in filesystem
pacman: /usr/share/makepkg/buildenv/buildflags.sh exists in filesystem
pacman: /usr/share/makepkg/buildenv/compiler.sh exists in filesystem
pacman: /usr/share/makepkg/buildenv/debugflags.sh exists in filesystem
pacman: /usr/share/makepkg/buildenv/makeflags.sh exists in filesystem
pacman: /usr/share/makepkg/executable.sh exists in filesystem
pacman: /usr/share/makepkg/executable/ccache.sh exists in filesystem
pacman: /usr/share/makepkg/executable/checksum.sh exists in filesystem
pacman: /usr/share/makepkg/executable/distcc.sh exists in filesystem
pacman: /usr/share/makepkg/executable/fakeroot.sh exists in filesystem
pacman: /usr/share/makepkg/executable/gpg.sh exists in filesystem
pacman: /usr/share/makepkg/executable/gzip.sh exists in filesystem
pacman: /usr/share/makepkg/executable/pacman.sh exists in filesystem
pacman: /usr/share/makepkg/executable/strip.sh exists in filesystem
pacman: /usr/share/makepkg/executable/sudo.sh exists in filesystem
pacman: /usr/share/makepkg/executable/vcs.sh exists in filesystem
pacman: /usr/share/makepkg/lint_config/ext.sh exists in filesystem
pacman: /usr/share/makepkg/lint_config/source_date_epoch.sh exists in filesystem
pacman: /usr/share/makepkg/lint_pkgbuild/arch_specific.sh exists in filesystem
pacman: /usr/share/makepkg/lint_pkgbuild/fullpkgver.sh exists in filesystem
pacman: /usr/share/makepkg/lint_pkgbuild/package_function_variable.sh exists in filesystem
pacman: /usr/share/makepkg/util/config.sh exists in filesystem
pacman: /usr/share/makepkg/util/dirsize.sh exists in filesystem
pacman: /usr/share/makepkg/util/schema.sh exists in filesystem
pacman: /usr/share/man/man8/checkupdates.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacdiff.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacman-conf.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacsort.8.gz exists in filesystem
pacman: /usr/share/man/man8/updpkgsums.8.gz exists in filesystem
pacman: /usr/share/pkgconfig/libmakepkg.pc exists in filesystem
Errors occurred, no packages were upgraded.


Does anyone know how to fix this?

Offline

#2 2020-02-29 10:23:39

loqs
Member
Registered: 2014-03-06
Posts: 19,089

Re: error: failed to commit transaction (conflicting files)

What is the output of

pacman -Qkk pacman

Offline

#3 2020-02-29 17:26:07

IzzyGiessen
Member
Registered: 2020-02-29
Posts: 4

Re: error: failed to commit transaction (conflicting files)

loqs wrote:

What is the output of

pacman -Qkk pacman

backup file: pacman: /etc/makepkg.conf (Modification time mismatch)
backup file: pacman: /etc/makepkg.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)

And then a lot of warnings similar to:
warning: pacman: /usr/bin/checkupdates (Modification time mismatch)
warning: pacman: /usr/bin/checkupdates (Size mismatch)

Offline

#4 2020-02-29 17:31:30

loqs
Member
Registered: 2014-03-06
Posts: 19,089

Re: error: failed to commit transaction (conflicting files)

pacman has a record of only some of the contents of the pacman package.
Try the following to fix the databse entry for the pacman package.

# pacman -S --dbonly pacman

Then try reinstalling the pacman package.
Would also recommend you fsck the filesystem,  check S.M.A.R.T. status of the storage device and ensure your backups are up to date.

Offline

#5 2020-03-01 12:46:49

IzzyGiessen
Member
Registered: 2020-02-29
Posts: 4

Re: error: failed to commit transaction (conflicting files)

loqs wrote:

pacman has a record of only some of the contents of the pacman package.
Try the following to fix the databse entry for the pacman package.

# pacman -S --dbonly pacman

Then try reinstalling the pacman package.
Would also recommend you fsck the filesystem,  check S.M.A.R.T. status of the storage device and ensure your backups are up to date.

Thanks! It worked!
The only problem now is that my speakers stopped working after I did that. I don't know what happened, but the volume now ranges from -65.25db to 0 db.

Offline

#6 2020-03-01 13:26:33

blitz
Banned
Registered: 2014-06-14
Posts: 32

Re: error: failed to commit transaction (conflicting files)

Regress pacman package: ignoring package upgrade (5.0.1-4 => 5.2.1-4) and use option --force.
Not recommended action, unless You know what You are doing.

Nawt. Do Not try it @ home.
Requires deep insight into systemd's and udev's inners.

blitz@inode ~ % sudo pacman -Syu --force
:: Synchronizing package databases...
 core                                                    134.5 KiB  1386K/s 00:00 [###############################################] 100%
 extra is up to date
 community is up to date
 multilib is up to date
 sublime-text is up to date
:: Starting full system upgrade...
warning: linux-zen: ignoring package upgrade (5.5.5.zen1-1 => 5.5.6.zen1-1)
warning: linux-zen-headers: ignoring package upgrade (5.5.5.zen1-1 => 5.5.6.zen1-1)
warning: mono: ignoring package upgrade (5.18.1.0-1 => 6.4.0.198-1)
warning: pacman: ignoring package upgrade (5.0.1-4 => 5.2.1-4)
resolving dependencies...
looking for conflicting packages...

Package (8)                                     Old Version  New Version  Net Change  Download Size

extra/at-spi2-atk                               2.34.1-1     2.34.2-1       0.00 MiB       0.06 MiB
extra/imagemagick                               7.0.9.26-1   7.0.9.27-1     0.00 MiB       2.51 MiB
core/libcap                                     2.31-1       2.32-1         0.00 MiB       0.05 MiB
community/python-sphinxcontrib-applehelp        1.0.1-4      1.0.2-1        0.00 MiB       0.03 MiB
community/python-sphinxcontrib-devhelp          1.0.1-4      1.0.2-1        0.00 MiB       0.02 MiB
community/python-sphinxcontrib-qthelp           1.0.2-4      1.0.3-1        0.00 MiB       0.03 MiB
community/python-sphinxcontrib-serializinghtml  1.1.3-4      1.1.4-1        0.00 MiB       0.02 MiB
extra/wayland-protocols                         1.18-1       1.20-1         0.00 MiB       0.06 MiB

Total Download Size:    2.78 MiB
Total Installed Size:  11.11 MiB
Net Upgrade Size:       0.01 MiB

:: Proceed with installation? [Y/n]

The only problem now is that my speakers stopped working after I did that. I don't know what happened, but the volume now ranges from -65.25db to 0 db.

blitz@inode ~ % journalctl -xb | grep -Ein "alsa|bad|crash|disable|doesn't support|error|fail|filtered out|ignoring|invalid value|line takes no |no |not found|not supported|unable|unset|warning|was not"

Last edited by blitz (2020-03-01 13:43:23)

Offline

#7 2020-03-01 14:44:20

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: error: failed to commit transaction (conflicting files)

blitz wrote:

Regress pacman package: ignoring package upgrade (5.0.1-4 => 5.2.1-4) and use option --force.
Not recommended action, unless You know what You are doing.

Nawt. Do Not try it @ home.
Requires deep insight into systemd's and udev's inners.

blitz@inode ~ % sudo pacman -Syu --force
:: Synchronizing package databases...
[...]

I'm mind-boggled that this could ever work for you.

$ sudo pacman -Syu --force
error: invalid option '--force'

"not recommended", you say?

Ah, but of course...

warning: pacman: ignoring package upgrade (5.0.1-4 => 5.2.1-4)

Last edited by eschwartz (2020-03-01 14:45:38)

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

#8 2020-03-01 15:48:04

blitz
Banned
Registered: 2014-06-14
Posts: 32

Re: error: failed to commit transaction (conflicting files)

Ah, but of course...

warning: pacman: ignoring package upgrade (5.0.1-4 => 5.2.1-4)

We are keep on learning.
Mistakes made, experience achieved, lessons learned. Like the Arch mindset ))

Offline

Pages: 1

Board footer

Powered by FluxBB