Hi, I'm getting this error when building:
ERROR: visual-studio-code.desktop was not found in the build directory and is not a URL.
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.87 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2024-11-15 11:08 (UTC) |
« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 78 Next › Last »
Hi, I'm getting this error when building:
ERROR: visual-studio-code.desktop was not found in the build directory and is not a URL.
shrug yea, maintainers rarely wanna co-maintain (even me back when I was doing it).
@Det Yep, I can do the actual download and replace with the actual checksum just as easily, but doing an extra git commit and push would allow me to share it, just wanted to check if that was an option.
@mixedCase, well.. on quick glance looks like you could maintain this locally with:
pkgver=$(curl -sL https://code.visualstudio.com/updates | grep -Pom1 "version \K[^)]*") # cut up from after "version " to the first ")" ("<h1>April 2020 (version 1.45)</h1>"), -m1: use only first result
pkgrel=1 # reset
sha256sums[0]='SKIP'
Put it at the end of the PKGBUILD, and it's a portable piece of text that doesn't even conflict with anything.
@dcelasun Yes, and thank you for keeping it within reasonable bounds all this time!. I'm offering because I update packages within the hour (usually less), since I automate new release checks to fire an e-mail usually before an user files the package as out of date, edit the PKGBUILD, make some quick tests and ship it.
As for my personal reason, I've been working with VS Code much more often recently and the damned gear with the notification gets on my nerves, but I understand being hesitant.
Let me know if you do change your mind :)
@mixedCase thanks for the offer! Over the years I've managed to keep this updated within hours of release. I'll ping you if that becomes untenable in the future.
Hi @dcelasun. I've been using your package for, well a couple of years now. I've noticed that MS tends to release updates during my office hours, making it practical for me to help out making version bumps shortly after releases occur. Would you accept a co-maintainer?
Would you mind creating visual-studio-code-insiders-bin? The Insiders version of the package would be very similar to this one - only pointing to a different URL, and having sha256sums=SKIP since Insiders is a daily build. Thank you.
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.