@samueldy I think you have a corrupted package. I don't see any CRLF characters:
$ grep -U $'\015' visual-studio-code-bin/PKGBUILD
$
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: | 1462 |
Popularity: | 13.57 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2024-11-15 11:08 (UTC) |
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 78 Next › Last »
@samueldy I think you have a corrupted package. I don't see any CRLF characters:
$ grep -U $'\015' visual-studio-code-bin/PKGBUILD
$
Updating via yay -Syu
gives the error:
:: (1/1) Parsing SRCINFO: visual-studio-code-bin
==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.
error downloading sources: visual-studio-code-bin
Navigating to the downloaded package directory (~/.cache/yay/visual-studio-code-bin
for me), running dos2unix
on PKGBUILD and the two .desktop files, and running makepkg -i
worked for me.
I've tried updating from 1.47.0.1 -> 1.47.1.1 using yay today. Updating failes:
curl: (6) Could not resolve host: update.code.visualstudio.com
==> ERROR: Failure while downloading https://vscode-update.azurewebsites.net/1.47.1/linux-x64/stable
Aborting...
Error downloading sources: visual-studio-code-bin
Same thing happens if I run makepkg -si
on the tarball.
I've tried to update this package (pkgver 1.41.1) several times over several days in the last week or so and every time the download times out. I can't even download directly.
wget https://update.code.visualstudio.com/1.41.1/linux-x64/stable/code_x64_1.41.1.tar.gz
HTTP request sent, awaiting response... 404 Not Found
Anyone have similar issues?
Is there an alternative URL?
Any ideas whatsoever welcome.
@emke Thanks, can confirm that it failed on pamac
, but works with yay
@lordflaron after the latest pamac update, I no longer get that error.
@lordflaron then that's a problem with pamac
. Please read the pinned Frequently Asked Questions.
@dcelasun I'm using the pamac
GUI with air support
@lordflaron that file is definitely in the package. How are you installing this package, with an AUR helper?
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.