Package Details: visual-studio-code-insiders-bin 1748582492-1

Git Clone URL: https://aur.archlinux.org/visual-studio-code-insiders-bin.git (read-only, click to copy)
Package Base: visual-studio-code-insiders-bin
Description: Visual Studio Code Insiders (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-insiders
Provides: code-insiders, vscode-insiders
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 34
Popularity: 0.32
First Submitted: 2020-11-17 19:53 (UTC)
Last Updated: 2025-05-30 07:19 (UTC)

Pinned Comments

dcelasun commented on 2025-05-25 06:44 (UTC)

This package is now automatically updated every day.

No need to build manually or mess with your AUR helpers.

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

furai commented on 2025-05-27 12:26 (UTC)

@dcelasun thank you!

dcelasun commented on 2025-05-27 12:19 (UTC)

Well, it runs once a day. I'll make it more frequent. In the meantime, I triggered it manually just now so you can update regularly.

furai commented on 2025-05-27 12:13 (UTC)

Uh, I've actually got used to doing clean build whenever new version was available. Now I can't update my visual studio code insiders this way and I have to wait for dcelasun's script to run to upgrade PKGBUILD. Which is a great change! Just that the script isn't probably run as often as I'd like it to.

For now I'll just edit PKGBUILD on my end with new version.

dcelasun commented on 2025-05-26 07:55 (UTC) (edited on 2025-05-26 09:45 (UTC) by dcelasun)

@Tymon3310 it's because Microsoft pushed a new version in the last hour or so and my updater didn't run yet. Try again please, should work now.

I need to find versioned URLs as opposed to https://update.code.visualstudio.com/latest/linux-x64/insider to properly fix this.

EDIT: Switched to versioned URLs, this shouldn't happen again.

Tymon3310 commented on 2025-05-26 07:44 (UTC)

==> Validating source_x86_64 files with sha256sums... code_x64_1747983148.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

angelfox commented on 2025-05-25 22:23 (UTC)

That's great, thank you!

dcelasun commented on 2025-05-25 06:44 (UTC)

This package is now automatically updated every day.

No need to build manually or mess with your AUR helpers.

dcelasun commented on 2025-05-22 06:49 (UTC)

@angelfox unfortunately the only real workaround is to build it manually. Longer term, I'd like to automate this package so new versions are pushed to AUR every day. That will avoid the pkgver hack.

angelfox commented on 2025-05-22 02:34 (UTC) (edited on 2025-05-22 02:36 (UTC) by angelfox)

Package does not update with paru, despite adding the --rebuild flag.

Quote from maintainers:

Makepkg's pkgver function is not meant for a pkg to be like this. Makepkg downloads the sources then runs the pkgver. This workflow is meant for git repos where you pull then calculate the version.

So when you run an update with makepkg, it will update the pkgver but use the sources of the old version. If you run makepkg again it should then download the current ver sources and built an up to date package (except it will skip the build and use the cached old package with the same ver unless you pass -f)

I've not really got any solution to this. The issue linked in yay just adds the suffix to a devel list to hide a newer than warning. So this issue will exist in yay too (as it exists in makepkg itself).

Really a package like this doesn't belong on the AUR as it doesn't follow how makepkg works.

https://github.com/Morganamilo/paru/issues/857#issuecomment-1312460937

dcelasun commented on 2025-03-05 20:39 (UTC)

You probably still have the previous version cached, but I just pushed a new pkgver, should invalidate any caches.

1 2 3 4 5 6 .. 11 Next › Last »