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

orkeren commented on 2018-02-08 00:19

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

binhex commented on 2018-02-07 10:07

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 ( :-

fryfrog commented on 2017-12-25 04:04

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!

orkeren commented on 2017-12-14 13:10

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

hicklemon commented on 2017-12-13 21:46

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.

orkeren commented on 2017-10-24 11:25

@Ryan-Bell you are obviously right. I have fixed this witth the update.

Ryan-Bell commented on 2017-10-22 23:50

I think the version in the .SRCINFO was not updated in the last commit (to The package fails to install.