| Git Clone URL: | https://aur.archlinux.org/lidarr.git (read-only, click to copy) |
|---|---|
| Package Base: | lidarr |
| Description: | Music download automation for usenet and torrents. |
| Upstream URL: | https://github.com/lidarr/Lidarr |
| Licenses: | GPL3 |
| Submitter: | orkeren |
| Maintainer: | fryfrog |
| Last Packager: | fryfrog |
| Votes: | 14 |
| Popularity: | 1.05 |
| First Submitted: | 2017-10-06 08:46 (UTC) |
| Last Updated: | 2024-05-13 17:57 (UTC) |
This might be of interest @fryfrog @orkeren, json output from appveyor, so you could curl this and then jq to get first entry, that way you can then just re-run without having to alter the url in the PKGBUILD:-
lidarr_url=$(curl "https://services.lidarr.audio/v1/update/nightly/changes?os=linux" | jq -r '.[0].url')
https://ci.appveyor.com/api/buildjobs/w3mqu9a4gtrdgv38/artifacts/Lidarr.develop.0.2.0.289.linux.tar.gz <- this one fixes mono 5.10.
I'd be happy to be a co-maintainer to help keep it more up to date.
@binhex there sadly is no way of targeting latest on appveyor. I am looking into creating an automated way though. Until then I will try to remember updating weekly.
@orkeren hey no probs, no apology required. How about a weekly build of this until things stabilise a bit, as those dev builds are obviously continuous, would that be a possibility? Not sure if there is a way of targeting 'latest' on appveyor to prevent the need to change the package?
@binhex - I have updated the package to the current build. I apologize for the delay in updating packages. In the future just flag it as out of date, as I get a priority alert for that.
i appreciate this is pre-alpha and thus difficult at this time, but is there a later developer build we can move to?, this hasn't changed in a while, if not could this package target github master branch instead?
edit - i cannot use the built in app updater as im running this in a docker container.
edit2 - bit of googling revelaed a link to appveyor with their latest dev build (0.2.0.267) :- https://ci.appveyor.com/project/lidarr/lidarr/build/artifacts
To make the built in updater work, you probably just need to update some permissions in the package. While it isn't Arch to use the built in updater... you don't need to block it. :)
Edit: Which it looks like you might already be doing!
@mhicklen I have now updated this package to the latest version of lidarr. Regarding the built-in updates page - you have to remember that this is still pre-alpha software, and as such features like that are not exptected to work. Furthermore it would be against the spirit of using a package manager like pacman to use such a build-in update feature.
Looks like the database schema is not being properly read in this release. The author has advised an update; however, the artifact being downloaded here is too old. Additionally, the updates page in the software's UI fails to function.
Pinned Comments
fryfrog commented on 2021-02-12 07:01 (UTC)
You may also be interested in lidarr-develop or lidarr-nightly.