Had the same problem but as @primos suggested fixing the md5sum allows you to install the package.
Search Criteria
Package Details: visual-studio-code-bin 1.95.3-1
Package Actions
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: | 1465 |
Popularity: | 14.57 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2024-11-15 11:08 (UTC) |
Dependencies (17)
- alsa-lib
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- gnupg (gnupg-gitAUR, gnupg-largekeysAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libnotify (libnotify-gitAUR)
- libsecret
- libxkbfile
- libxss
- lsof (lsof-gitAUR)
- nss (nss-hgAUR)
- shared-mime-info
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR) (optional) – Needed for move to trash functionality
- icu69AUR (icu69-binAUR) (optional) – Needed for live share
- libdbusmenu-glib (optional) – Needed for KDE global menu
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, dssdAUR, pass-secret-service-gitAUR, bitw-gitAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – Needed for settings sync
Required by (20)
- azure-sphere-sdk (requires code) (optional)
- code-appicons (requires code)
- code-features (requires code)
- code-features-insiders (requires code)
- code-icons (requires code)
- code-marketplace (requires code)
- code-nautilus-git (requires code) (optional)
- dokytree (requires code) (optional)
- dokytree-git (requires code) (optional)
- meta-package-manager (requires code) (optional)
- meta-package-manager-git (requires code) (optional)
- nautilus-code (requires code) (optional)
- neopo-git (optional)
- nwscript-code (requires code)
- rust-analyzer-vscode-git (requires code)
- stm32pio (requires code) (optional)
- unity-editor-lts (optional)
- unreal-engine-bin (requires code) (optional)
- vscode-xdg-patch-hook (requires vscode) (optional)
- vscode-xdg-patch-hook (requires code) (optional)
Sources (7)
Latest Comments
« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 78 Next › Last »
lszanto commented on 2017-03-02 08:12 (UTC)
primos commented on 2017-03-02 02:50 (UTC)
md5sums are not correct. I ran md5sum on the downloads and got
x64 => c74237b2bb22cc09716a297581ab87f0
i386 => d5b0217f3a764987499d83f2abf24036
Changed the pkgbuild file and x64 version installed for me.
gotaug commented on 2017-03-02 02:20 (UTC)
I'm getting the error:
==> Validating source_x86_64 files with md5sums...
code_x64_1.10.tar.gz ... FAILED
dcelasun commented on 2017-02-18 22:09 (UTC)
@gdamjan: Check the past comments please. It's needed for "move to trash" functionality. If it bothers enough people, I can move it to optdepends with the next release.
gdamjan commented on 2017-02-18 22:03 (UTC)
is the dependency to gvfs really needed??
I've masked gvfs-daemon gvfs-metadata gvfs-udisks2-volume-monitor in my --user systemd, and vscode still works.
raphi011 commented on 2017-02-09 10:08 (UTC) (edited on 2017-02-09 10:08 (UTC) by raphi011)
great, thanks! keep up the good work :)
dcelasun commented on 2017-02-09 08:25 (UTC)
Yes, because there was a new release and the download URLs always point to the latest. Try again now.
raphi011 commented on 2017-02-09 08:19 (UTC)
Getting the following error message after trying to update:
==> Validating source_x86_64 files with md5sums...
code_x64_1.9.0.tar.gz ... FAILED
visual-studio-code.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build visual-studio-code.
dcelasun commented on 2017-01-15 18:36 (UTC)
@goetzc: Done, thanks.
g360 commented on 2017-01-15 16:46 (UTC)
Hi! The desktop file could be improved, there is the "Categories" entry twice, and having also the category Utilities (as other editors) could be handy.
desktop-file-validate gives:
file contains multiple keys named "Categories" in group "Desktop Entry"
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-open
uses 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.