| 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: | 16.54 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2025-02-13 18:48 (UTC) |
@pedromello, thanks for the confirmation. The hash I'm getting from both the Netherlands and UK is 154a316eb6785c126e2fccd80a5c76291321ca2d6945e7a2a13f2e262be89bde. Can someone else from a different country check as well?
EDIT: Checked from USA and Turkey as well, both get the above hash. I'm guessing this is a Latin American mirror issue.
I've got the same hash as @xereda 39e953dc16f248399d286cdca1653345ff32927affc0256ea4a62607f8f5f232 code_x64_1.31.1.tar.gz
I've noticed both me and @xereda are from Brazil (based on the language of the yay output in his post). I this case, @dcelasun hint about a mirror with a different version is valid... and annoying at the same time :)
OK first of all, please don't make multiple comments in succession. Just make one and edit it if necessary.
Secondly, please try without yay (see the stickied FAQ comment, just use makepkg -si). If that still doesn't work, my guess is the mirror you are downloading from has either a corrupted tarball or simply a different version.
@xereda, something must have gone wrong with your download which corrupted the file. Delete it and try again.
$ sha256sum code_x64_1.31.1.tar.gz
154a316eb6785c126e2fccd80a5c76291321ca2d6945e7a2a13f2e262be89bde code_x64_1.31.1.tar.gz
Getting the following error while upgrading from 1.30.2-1 -> 1.31.0-2
(OK):download completed.
mv: cannot stat '/tmp/yaourt-tmp-munim/aur-visual-studio-code-bin/stable': No such file or directory
-> Found visual-studio-code.desktop
-> Found visual-studio-code-url-handler.desktop
==> Validating source_x86_64 files with sha256sums...
code_x64_1.31.0.tar.gz ... NOT FOUND
visual-studio-code.desktop ... Passed
visual-studio-code-url-handler.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build visual-studio-code-bin.
==> Restart building visual-studio-code-bin ? [y/N]
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.