Package Details: openasar-bin 3:20221202224042-2

Git Clone URL: https://aur.archlinux.org/openasar-bin.git (read-only, click to copy)
Package Base: openasar-bin
Description: Open-source alternative of Discord desktop's app.asar, needs Discord installed. Nightly builds.
Upstream URL: https://openasar.dev/
Keywords: asar discord goosemod openasar
Licenses: MIT
Submitter: GBember
Maintainer: alsoGAMER
Last Packager: Sir-Photch
Votes: 3
Popularity: 0.044398
First Submitted: 2022-09-01 22:51 (UTC)
Last Updated: 2022-12-03 08:50 (UTC)

Pinned Comments

Sir-Photch commented on 2022-12-11 18:50 (UTC)

consider changing the permissions of the resources folder of your discord installation for openasar to update automatically. See: https://github.com/GooseMod/OpenAsar/blob/main/faq.md#does-openasar-update-itself

Latest Comments

« First ‹ Previous 1 2

GBember commented on 2022-10-02 20:18 (UTC)

I'm quite new to making/maintaining AUR packages, I think I also mixed up pkgver with pkgrel, sorry for the problems

Lili1228 commented on 2022-10-02 20:04 (UTC) (edited on 2022-10-02 20:19 (UTC) by Lili1228)

This is absolutely not how you should version the package. Refer to https://wiki.archlinux.org/title/PKGBUILD, but I'll be nice enough to summarize:

epoch should be used only when the next version of the package would be considered older by pacman, for example 1.0 → 2.0 → 3.0 → 1.0 again for some reason, 2nd 1.0 would be older according to pacman.

Then you have pkgver, I assume the GitHub release is made on every commit. Curling https://api.github.com/repos/GooseMod/OpenAsar/releases, getting the published_at date and sed -i 's/[-:]//g' on that should be good enough.

Finally, pkgrel is updated every time you change PKGBUILD, but the version it builds doesn't change.

Since the release changes every commit and the PKGBUILD downloads the latest version every time, I think it's safe to just replace the checksum of app.asar with 'SKIP'.

GBember commented on 2022-10-02 13:58 (UTC)

It looks like this fixed the problem with AUR helpers, thank you.

1nikolas commented on 2022-10-02 11:10 (UTC)

I've seen this problem with other aur packages too. When the same link is used for all the versions of the app, aur managers use the cached version of that file (aka the old version) and then do the sha512 check against the old one (which fails). A potential solution to this would be to add "?$pkgrel" at the end of the url. Haven't tested it but in theory it should force it to re-download the new file.

GBember commented on 2022-09-28 15:47 (UTC) (edited on 2022-09-29 01:41 (UTC) by GBember)

Upstream updated the package but the version number is still "nightly", it should be working now

Coelacanthus commented on 2022-09-28 14:32 (UTC)

checksum mismatch

« First ‹ Previous 1 2