| Git Clone URL: | https://aur.archlinux.org/visual-studio-code-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | visual-studio-code-bin |
| Description: | Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version) |
| Upstream URL: | https://code.visualstudio.com/ |
| Licenses: | custom: commercial |
| Conflicts: | code |
| Provides: | code, vscode |
| Submitter: | dcelasun |
| Maintainer: | dcelasun |
| Last Packager: | dcelasun |
| Votes: | 1493 |
| Popularity: | 17.22 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2025-02-13 18:48 (UTC) |
Live Share seems to work without icu69-bin now.
After the update to glibc-2.41, icu69-bin seems to introduce some segfaults to Chromium based browsers for me, Edge, Chromium, Google-Chrome.
YMMV, but leaving this here in case anyone else is having issues.
download from https://gitdl.cn/https://raw.githubusercontent.com/microsoft/vscode/1.97.2/resources/linux/code.desktop\n
正在初始化下载：https://gitdl.cn/https://raw.githubusercontent.com/microsoft/vscode/1.97.2/resources/linux/code.desktop
ERROR 502: Bad Gateway.
it is ok，after modify the axel setting。the path is /usr/bin/fake_axel_for_makepkg.
kdialog should be added as an optional dependency IMO.
@Nowaker What fixed it for me was removing the yay cache rm -rf ~/.cache/yay/visual-studio-code-bin then doing the update again.
The issue might be cause by an extension called Custom CSS and JS loader that needed me to change ownership of some vscode directories.
@mrjxtr I don't have any issues, and I use yay too.
I cannot update using yay -Syu because of this error.
❯ yay -Syu
[sudo] password for mrjxtr:
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
-> Flagged Out Of Date AUR Packages: snapd
:: 1 package to upgrade/install.
1 aur/visual-studio-code-bin 1.95.3-1 -> 1.96.0-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
-> Excluding packages may cause partial upgrades and break systems
==>
AUR Explicit (1): visual-studio-code-bin-1.96.0-1
:: (0/1) Failed to download PKGBUILD: visual-studio-code-bin
-> error fetching visual-studio-code-bin: You are not currently on a branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
context: exit status 1
If an extension is trying to write to /opt/visual-studio-code instead of ~/.code, it's the extension that's broken, not this package. Please report it upstream.
Request for joint maintenance
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)
FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)
This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.
Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.
Sometimes AUR helpers do weird things. Download the tarball and install it manually with
makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.
The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.