Make the gpg signature file available through the official download.vscodium.com domain #24

New Issue

giteasync · 2025-09-10T22:49:55-05:00

giteasync commented

2025-09-10 22:49:55 -05:00

Originally created by @locture on GitHub.

Currently the gpg key can only be accessed thru the gitlab page https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/.
While the rpm/deb packages have already been made accessible thru the more official CDN mirror download.vscodium.com, it will be more convenient and organized to keep a copy of the gpg key file under the mirror for better management and setup purpose.

Originally created by @locture on GitHub. Currently the gpg key can only be accessed thru the gitlab page https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/. While the rpm/deb packages have already been made accessible thru the more official CDN mirror download.vscodium.com, it will be more convenient and organized to keep a copy of the gpg key file under the mirror for better management and setup purpose.

giteasync commented

2025-09-10 22:49:55 -05:00

@TzourCode commented on GitHub:

Maybe a stupid question and don't belongs here. But i have this problem when i wan't to update VScodium. I did find out eventually and downloaded the GPG key through gitlab and added the key in apt source list. But when i update the system it still says that the Certificate verification failed and is not trusted. Should i just ignore and wait until they put the gpg key under the same mirror or should i bypass the SSL verification with (--insecure) command?
I have linux mint.

[ Update about the certification not trusted problem. 2025/02/21:

I changed from packages to download in the "/etc/apt/sources.list.d/vscodium.list" from
( https://packages.vscodium.com/debs ) to ( https://download.vscodium.com/debs )

{ deb [arch=amd64 signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg] https://download.vscodium.com/debs vscodium main }

Thought it might help someone. 🖖]

@TzourCode commented on GitHub: Maybe a stupid question and don't belongs here. But i have this problem when i wan't to update VScodium. I did find out eventually and downloaded the GPG key through gitlab and added the key in apt source list. But when i update the system it still says that the Certificate verification failed and is not trusted. Should i just ignore and wait until they put the gpg key under the same mirror or should i bypass the SSL verification with (--insecure) command? I have linux mint. [ Update about the certification not trusted problem. 2025/02/21: I changed from packages to download in the "/etc/apt/sources.list.d/vscodium.list" from ( https://packages.vscodium.com/debs ) to ( https://download.vscodium.com/debs ) { deb [arch=amd64 signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg] https://download.vscodium.com/debs vscodium main } Thought it might help someone. 🖖]

giteasync referenced this issue

2025-09-10 22:50:15 -05:00

[PR #24] [MERGED] fixes vscodium.github.io#19 #80

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: VSCodium/vscodium.github.io#24