VS Code Debian package can create duplicate repo enrollment during install.

[mbearup]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.116
• OS Version: Ubuntu 24.04

Steps to Reproduce:

1. Manually enroll in the vscode repo (https://packages.microsoft.com/repos/code/pool/main/c/code/)
2. Install vscode. During install, vscode will create a repo enrollment of its own.
3. If the filename from step Open Source VS Code #1 doesn't match the file created in step gulp-symdest does not preserve links on electron #2, then the client will have a duplicate enrollment in the repo. This breaks package management actions (apt update, apt install, etc) until the user manually fixes it.

Recommended behavior:
Update post-install script to detect the existing repo enrollment. If a repo enrollment already exists (under a different filename created by the admin) then disable "our" enrollment (from step #2) and let the owner's enrollment take precedence.

Reference the following issue for context. The issue references .list files (Ubuntu/Debian) but should look for similar behavior with rpm (Fedora/RHEL).
microsoft/linux-package-repositories#317

[mbearup]

@rzhao271 FYI per our chat.

[rzhao271]

Verification steps for team members with Ubuntu or Debian machines (VMs and WSL OK)

Using a terminal,

1. Purge all VS Code installs from the Linux machine using apt purge or dpkg -P.
2. Install code-insiders. Select Yes when the signing key confirmation pops up.
3. Rename the file /etc/apt/sources.list.d/vscode.sources, e.g. sudo mv /etc/apt/sources.list.d/vscode.sources /etc/apt/sources.list.d/helloworld.sources.
4. Purge the code-insiders package using dpkg -P or apt purge.
5. Reinstall code-insiders. Confirm that the signing key confirmation does not pop up.