Arch Linux

4p1C

Member

From: France

Registered: 2011-01-31

Posts: 58

A generic procedure to solve conflicts?

Hi all,
I was wondering if there is a generic procedure to solve conflicts between AUR packages.
For example, right now, I can't upgrade ungoogled-chromium-bin-debug because electron27-bin-debug is owned by vscodium-insiders-debug
This is not the first time that electron package is shared by two or more apps and is blocking updates.
Any help will be appreciated!

loqs

Member

Registered: 2014-03-06

Posts: 17,436

Re: A generic procedure to solve conflicts?

Please post the command you are using and the output it is producing that shows the issue.  Why are you installing debug packages for prebuilt binaries?

4p1C

Member

From: France

Registered: 2011-01-31

Posts: 58

Re: A generic procedure to solve conflicts?

Actually,
I was just invoking normal upgrades with:

$yay -Suy
[...]
2  aur/electron27-bin          27.3.1-1           -> 27.3.2-1
1  aur/ungoogled-chromium-bin  121.0.6167.160-1   -> 121.0.6167.184-1

And then in the end, I get:

(4/4) checking for file conflicts                                                                                                             [---------------------------------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
electron27-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca.debug exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d.debug exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6 exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6.debug exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699 exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699.debug exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c.debug exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d exists in filesystem (owned by vscodium-insiders-debug)
electron27-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d.debug exists in filesystem (owned by vscodium-insiders-debug)
Errors occurred, no packages were upgraded.
 -> error installing: [/home/tovo/.cache/yay/electron27-bin/electron27-bin-27.3.2-1-x86_64.pkg.tar.zst /home/tovo/.cache/yay/electron27-bin/electron27-bin-debug-27.3.2-1-x86_64.pkg.tar.zst /home/tovo/.cache/yay/ungoogled-chromium-bin/ungoogled-chromium-bin-121.0.6167.184-1-x86_64.pkg.tar.zst /home/tovo/.cache/yay/ungoogled-chromium-bin/ungoogled-chromium-bin-debug-121.0.6167.184-1-x86_64.pkg.tar.zst] - exit status 1

loqs

Member

Registered: 2014-03-06

Posts: 17,436

Re: A generic procedure to solve conflicts?

Why are you installing debug packages for prebuilt binaries?

You have multiple packages containing the same build of the same binary but installed to different locations in the file-system.  This is causing issues with the debug packages.  So why are you building and installing these debug packages?

4p1C

Member

From: France

Registered: 2011-01-31

Posts: 58

Re: A generic procedure to solve conflicts?

I can't remember exactly why but, I guess that I've met some bug at a time and tried to debug.
But at the end, you're right: if I remove debug packages, my troubles are gone.
This was a specific case and, what is the right way to debug when it happens with other packages?
I used to meet the same issue with Joplin because it's depending on electronXX with others.

loqs

Member

Registered: 2014-03-06

Posts: 17,436

Re: A generic procedure to solve conflicts?

There are lots of joplin packages in AUR.  If you do not need the debug packages I would suggest disabling building debug packages.  For packages that are only going to be used on the same machine I would also suggest considering reducing/disabling the compression used.