Can't do full sysupgrade becausen of file permission conflict between `brotli` and its `lib32` counterpart

[loustro]

Hi, I was just trying to do my sysugrade through yay when suddenly I get file permission conflicts between brotli and its lib32 counterpart. How do I resolve this conflict? Thank you in advance for the help!

yay -Syyu 
:: Synchronizing package databases...
 endeavouros                   14.6 KiB  44.2 KiB/s 00:00 [------------------------------] 100%
 core                         126.4 KiB   635 KiB/s 00:00 [------------------------------] 100%
 extra                          8.3 MiB  14.7 MiB/s 00:01 [------------------------------] 100%
 multilib                     127.5 KiB   637 KiB/s 00:00 [------------------------------] 100%
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Flagged Out Of Date AUR Packages: libajantv2
:: 1 package to upgrade/install.
1  multilib/lib32-brotli  1.1.0-1 -> 1.2.0-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> 
Sync Dependency (1): lib32-brotli-1.2.0-1
:: Synchronizing package databases...
 endeavouros                   14.6 KiB  42.9 KiB/s 00:00 [------------------------------] 100%
 core                         126.4 KiB   648 KiB/s 00:00 [------------------------------] 100%
 extra                          8.3 MiB  15.8 MiB/s 00:01 [------------------------------] 100%
 multilib                     127.5 KiB   582 KiB/s 00:00 [------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (1)            Old Version  New Version  Net Change

multilib/lib32-brotli  1.1.0-1      1.2.0-1        0.01 MiB

Total Installed Size:  0.87 MiB
Net Upgrade Size:      0.01 MiB

:: Proceed with installation? [Y/n] 
(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)
lib32-brotli: /usr/share/man/man1/brotli.1.gz exists in filesystem (owned by brotli)
lib32-brotli: /usr/share/man/man3/constants.h.3.gz exists in filesystem (owned by brotli)
lib32-brotli: /usr/share/man/man3/decode.h.3.gz exists in filesystem (owned by brotli)
lib32-brotli: /usr/share/man/man3/encode.h.3.gz exists in filesystem (owned by brotli)
lib32-brotli: /usr/share/man/man3/types.h.3.gz exists in filesystem (owned by brotli)
Errors occurred, no packages were upgraded.
 -> error installing repo packages

[cactux]

It is not about file permission.

Looks like both brotli and its lib32 counterpart use man pages with the same naming.

Since those already exist on the filesystem, pacman refuses to overwrite them.

Have a look at the following post by highly estimated and missed @jonathon:

[FAQ] Package installation says FILENAME exists in filesystem; “Failed to commit transaction (conflicting files)”

I can’t install or update a package because I get (something like) this: error: could not prepare transaction error: failed to commit transaction (conflicting files) libname: /insert/file/name/here exists in filesystem Errors occurred, no packages were upgraded. Why is this happening? The package manager, pacman , has detected an unexpected file already exists on disk. By design it will not overwrite files that already exist. This is a design feature, not a flaw - package managers are desi…

[loustro]

Hi, thanks for the help. Although, I tried another sysupgrade to check which files are having problems but it seems that lib32-brotli just had a package update to 1.2.0-2, and the sysupgrade worked. Thanks for the help though

[Cphusion]

That’s the case most of the time when you get an error during updating, just be patient.

[loustro]

Fair enough, I had no idea what happened so I thought it’s a system issue. At least it’s fixed now

[cactux]

It is a little bit odd that a new version solved the “file already exist” issue unless they have changed the packaging to rename those files or perhaps not even include them .

Also, there are cases when a manual intervention to resolve issues during updates is necessary.
Waiting would not always help in those situations.