Package Details: lidarr-bin 2.8.2.4493-1

Git Clone URL: https://aur.archlinux.org/lidarr-bin.git (read-only, click to copy)
Package Base: lidarr-bin
Description: Music collection manager for newsgroup and torrent users.
Upstream URL: https://lidarr.audio
Licenses: GPL-3.0-or-later
Groups: servarr-bin
Conflicts: lidarr
Provides: lidarr
Submitter: txtsd
Maintainer: txtsd (fryfrog)
Last Packager: txtsd
Votes: 14
Popularity: 0.34
First Submitted: 2024-10-15 14:38 (UTC)
Last Updated: 2024-12-17 09:07 (UTC)

Dependencies (20)

Required by (7)

Sources (7)

Pinned Comments

txtsd commented on 2024-10-21 04:23 (UTC) (edited on 2024-10-30 12:50 (UTC) by txtsd)

Alternate versions

lidarr (source version of this package)
lidarr-develop (develop branch)
lidarr-develop-bin (binary version of the develop branch)
lidarr-nightly-bin (nightly builds)

Latest Comments

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

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? :/

fryfrog commented on 2018-03-21 14:46 (UTC)

@binhex, the lidarr.tmpfiles creates and maintains ownership of /var/lib/lidarr and /usr/lib/lidarr. The way of the future! :)

binhex commented on 2018-03-21 12:26 (UTC)

thanks @fryfrog

btw i think you may want to take a look at the lidarr.service file, it still has references to /var/lib/lidarr, which by the look of the PKGBUILD is no longer created.....unless the very action of running the service creates this folder?, i dunno but i thought its worth mentioning.

fryfrog commented on 2018-03-17 19:55 (UTC)

Ah, this is from using the trixie url thing. :/

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