Package Details: lidarr 2.2.5.4141-1

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: 13
Popularity: 0.079602
First Submitted: 2017-10-06 08:46 (UTC)
Last Updated: 2024-04-13 18:53 (UTC)

Dependencies (13)

Required by (6)

Sources (7)

Pinned Comments

fryfrog commented on 2021-02-12 07:01 (UTC)

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

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

resol341 commented on 2022-04-20 03:24 (UTC)

Thank you!

eta-carinae commented on 2022-04-19 22:22 (UTC)

resol341,

You can work around this issue for now by setting the environment variable DOTNET_SYSTEM_GLOBALIZATION_INVARIANT to 1 when you run lidarr.

resol341 commented on 2022-04-17 15:57 (UTC)

Getting "Process terminated. Couldn't find a valid ICU package installed on the system." after icu update.

fryfrog commented on 2021-02-12 07:01 (UTC)

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

fryfrog commented on 2019-04-13 14:31 (UTC) (edited on 2019-04-13 14:31 (UTC) by fryfrog)

@xombiemp: I've added it as an optdepend for now, thanks for letting me know.

xombiemp commented on 2019-04-13 13:54 (UTC)

After the latest update I'm seeing this message in the Health check page: fpcalc could not be found. Audio fingerprinting disabled.

Looks like we can solve the issue by making chromaprint a dependency. https://github.com/Lidarr/Lidarr/wiki/Health-checks#fpcalc-missing

storrgie commented on 2018-05-30 17:10 (UTC)

Alright, thanks! I didn't want to harass via a flag if you had something else in mind. Thanks for the quick update.

fryfrog commented on 2018-05-30 15:06 (UTC)

It started by tracking development, since that was all they had. Now it tracks their pre-releases, though I was expecting them to be a little more frequent. When they have a release version, I'll have it track that.

You can totally flag out of date for pre-releases. :)

storrgie commented on 2018-05-30 14:52 (UTC)

Would this package consider moving to their most recent "prerelease" or should that be done in a lidarr-git package?

https://github.com/lidarr/Lidarr/releases/tag/v0.3.0.430

fryfrog commented on 2018-04-26 23:10 (UTC)

@binhex, now that they've had a "release" ... what do you think we should track here? :/

« First ‹ Previous 1 2 3 4 Next › Last »