Change:
%description Visual Studio Code is a new choice of tool that combines the simplicity of a code editor with what developers need for the core edit-build-debug cycle. See https://code.visualstudio.com/docs/setup/linux for installation instructions and FAQ. <ins> # Don't generate build_id links to prevent conflicts when installing multiple # versions of VS Code alongside each other (e.g. `code` and `code-insiders`) %define _build_id_links none </ins> %install mkdir -p %{buildroot}/usr/share/@@NAME@@ mkdir -p %{buildroot}/usr/share/applications

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: code-insiders-1.54.0-.el7.x8664 code-1.53.0-.el7.x8664 OS Version: Fedora 32 5.10.12-100.fc32.x8664 Steps to Reproduce: dnf install code-insiders dnf install code Observe installation error (see below) <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Unrelated. This is an installation bug. bash ... Visual Studio Code 24 kB/s | 3.0 kB 00:00 Dependencies resolved. Package Architecture Version Repository Size Installing: code x8664 1.53.0-.el7 code 92 M Transaction Summary Install 1 Package Total download size: 92 M Installed size: 259 M Is this ok [y/N]: y Downloading Packages: code-1.53.0- 4.7 MB/s | 92 MB 00:19
Total 4.7 MB/s | 92 MB 00:19 Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction test error: file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.

x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.

el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664 file from install of code-1.53.0-.el7.x8664 conflicts with file from package code-insiders-1.54.0-.el7.x8664
I believe this may be an issue with , as I have encountered the same issue with some packages of my own which share the same Electron version ( and from my project). The conflicting files are debugging symbols for the Electron binary bundled with the RPM package. They are the same across both packages because the same Electron version is used. See also: One solution would be for electron-installer-redhat to skip generating these symbols so that there would be no files to conflict. The binaries themselves do not conflict as they are installed in different locations for each VS Code build type. Another solution would be to generate a separate package (eg ) which provides the Electron binary, and have each VS Code package depend on that package instead of providing the binary themselves. However, this may not work if an Insiders build wants to use a different Electron version to the stable build. Edit: it looks like rather than using electron-installer-redhat; however, the problem described is the same regardless.
Looks like a duplicate of
I think you're right, this is a duplicate. I searched issues looking for install problems, since that's what I was experiencing. Also, this is a relatively new problem. Previously I had both and installed from the repo and everything was fine. Something must have changed in the past week or so.
I would imagine that's because, until the 1.53.0 release, the Electron binaries were different versions between and , but this release has brought the stable build up-to-date with the version used in the insiders build.