You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Then update the package cache and install the package using:
68
+
1. Create a `/etc/apt/sources.list.d/vscode.sources` file with the following contents to add a reference to the upstream package repository:
69
+
70
+
```plaintext
71
+
Types: deb
72
+
URIs: https://packages.microsoft.com/repos/code
73
+
Suites: stable
74
+
Components: main
75
+
Architectures: amd64,arm64,armhf
76
+
Signed-By: /usr/share/keyrings/microsoft.gpg
77
+
```
78
+
79
+
1. Lastly, update the package cache and install the package:
70
80
71
81
```bash
72
82
sudo apt install apt-transport-https
73
83
sudo apt update
74
84
sudo apt install code # or code-insiders
75
85
```
76
86
87
+
> [!NOTE]
88
+
> Due to the manual signing process and the publishing system we use, the Debian repo could lag behind by up to three hours and not immediately get the latest version of VS Code.
89
+
77
90
### RHEL, Fedora, and CentOS based distributions
78
91
79
92
We currently ship the stable 64-bit VS Code for RHEL, Fedora, or CentOS based distributions in a yum repository.
80
93
81
-
1. Install the key and yum repository by running the following script:
94
+
1. Install the key and yum repository by running the following script:
@@ -100,7 +113,7 @@ We currently ship the stable 64-bit VS Code for RHEL, Fedora, or CentOS based di
100
113
```
101
114
102
115
> [!NOTE]
103
-
> Due to the manual signing process and the publishing system we use, the yum repo could lag behind and might not immediately get the latest version of VS Code.
116
+
> Due to the manual signing process and the publishing system we use, the yum repo could lag behind by up to three hours and not immediately get the latest version of VS Code.
0 commit comments