Package Details: lidarr

Git Clone URL: (read-only, click to copy)
Package Base: lidarr
Description: Music download automation for usenet and torrents.
Upstream URL:
Licenses: GPL3
Submitter: orkeren
Maintainer: orkeren (fryfrog)
Last Packager: fryfrog
Votes: 11
Popularity: 0.036721
First Submitted: 2017-10-06 08:46
Last Updated: 2020-10-31 21:48

Dependencies (14)

Required by (3)

Sources (4)

Pinned Comments

fryfrog commented on 2021-02-12 07:01

You may also be interested in lidarr-develop or lidarr-nightly.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

binhex commented on 2018-03-17 16:39

I'm getting validation failure:-

Validating source files with sha512sums... Lidarr.develop. ... ?[0m ?[91mFAILED

binhex commented on 2018-03-09 09:31

@fryfrog looks good to me mate, my automated scripts picked up your change and built a new docker image with no issues, so its all good for me.

fryfrog commented on 2018-03-08 17:39

@binhex and @orkeren, check out what I just pushed and see what you think. When Lidarr has regular (pre)releases, we can do away w/ the silliness. We'll still need to manually edit the pkgver, so don't forget to do that! :)

binhex commented on 2018-03-08 10:46

ok how about a bit of regex then so we don't rely on jq:-

lidarr_url=$(curl -s "" | grep -P -o -m 1 '(?<=url":")[^"]+' | head -1)

orkeren commented on 2018-03-08 10:04

@binhex - that snippet though requires jq which we would have to add as dependency.

orkeren commented on 2018-03-08 10:03

@fryfrog I'll add you. @binhex thanks for that snippet!

binhex commented on 2018-03-06 16:01

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 "" | jq -r '.[0].url')

fryfrog commented on 2018-03-05 20:42 <- this one fixes mono 5.10.

I'd be happy to be a co-maintainer to help keep it more up to date.

orkeren commented on 2018-02-19 10:20

@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.

binhex commented on 2018-02-08 09:47

@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?