You are not logged in.

#1 2024-03-24 10:07:06

jlumme
Member
Registered: 2019-04-06
Posts: 9

Failing to install vscode due to file naming conflict ?

I'm having a problem installing pre-compiled Visual Studio Code (the closed source version visual-studio-code-bin) due to what appears to be a package naming conflict with Saleae Logic2 software.

The installation fails in following way:

$ yay -S visual-studio-code-bin
....

Packages (2) visual-studio-code-bin-1.87.2-1  visual-studio-code-bin-debug-1.87.2-1

Total Installed Size:  373,85 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                                                            [###############################################################] 100%
(2/2) checking package integrity                                                                          [###############################################################] 100%
(2/2) loading package files                                                                               [###############################################################] 100%
(2/2) checking for file conflicts                                                                         [###############################################################] 100%
error: failed to commit transaction (conflicting files)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/0d/49e5f81cf7bbad601d3475297659adf7675b2d exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/0d/49e5f81cf7bbad601d3475297659adf7675b2d.debug exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/2c/4a719b602d37b12e2a5b0390e66f786415d29e exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/2c/4a719b602d37b12e2a5b0390e66f786415d29e.debug exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/6b/0e72b380e0372437ef8a2ad744b059fb0c4fd5 exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/6b/0e72b380e0372437ef8a2ad744b059fb0c4fd5.debug exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/fc/959a81aaed5e7b8bb3edcd75d8ba6717e3bbf4 exists in filesystem (owned by saleae-logic2-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/fc/959a81aaed5e7b8bb3edcd75d8ba6717e3bbf4.debug exists in filesystem (owned by saleae-logic2-debug)
Errors occurred, no packages were upgraded.

I seem to have found some advice to "complain to package maintainer" - but I'm not really sure what I should actually be doing here...
Is there some way I can have both Logic2 and vscode installed cleanly ?

Offline

#2 2024-03-24 10:12:42

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,956
Website

Re: Failing to install vscode due to file naming conflict ?

Mod note: moving to AUR Issues.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2024-03-24 14:08:53

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,050

Re: Failing to install vscode due to file naming conflict ?

Are you planning to troubleshoot/debug and register upstream bugreports for either of those applications ?

If not you don't need debug packages.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#4 2024-03-25 12:59:06

jlumme
Member
Registered: 2019-04-06
Posts: 9

Re: Failing to install vscode due to file naming conflict ?

Lone_Wolf wrote:

Are you planning to troubleshoot/debug and register upstream bugreports for either of those applications ?

If not you don't need debug packages.

Thanks, I did not know of this feature.

For posterity, I modified /etc/makepkg.conf OPTIONS variable to "!debug" from "debug".

I presume there is no "package specific" configuration setting anywhere ? I wonder why the debug flag is on by default ? I would imagine most people are not looking to debug individual packages...

Last edited by jlumme (2024-03-25 13:00:16)

Offline

#5 2024-03-25 13:05:22

loqs
Member
Registered: 2014-03-06
Posts: 17,639

Re: Failing to install vscode due to file naming conflict ?

jlumme wrote:

I wonder why the debug flag is on by default ? I would imagine most people are not looking to debug individual packages...

makepkg.conf has been synchronized with the flags from the devtools package which are used to build official packages.

Offline

#6 2024-03-25 13:40:16

jlumme
Member
Registered: 2019-04-06
Posts: 9

Re: Failing to install vscode due to file naming conflict ?

loqs wrote:
jlumme wrote:

I wonder why the debug flag is on by default ? I would imagine most people are not looking to debug individual packages...

makepkg.conf has been synchronized with the flags from the devtools package which are used to build official packages.

Hmm, to educate myself, can you clarify a bit more what you mean ? I'm not clear what you mean by the devtools package here. Also what does the synchronization mean in this context ? That it has been automatically configured and it will get overwritten somehow at some point ?

Offline

#7 2024-03-25 14:06:32

loqs
Member
Registered: 2014-03-06
Posts: 17,639

Re: Failing to install vscode due to file naming conflict ?

The devtools package, which contains https://gitlab.archlinux.org/archlinux/ … 86_64.conf.
By synchronization I meant a commit to the pacman PKGBUILD that synchronized the options between the two configurations.  Your changes to /etc/makepkg.conf will not be overwritten.

Offline

Board footer

Powered by FluxBB