Package Details: sonarr-develop

Git Clone URL: (read-only, click to copy)
Package Base: sonarr-develop
Description: TV download automation for usenet and torrents.
Upstream URL:
Licenses: GPL3
Conflicts: sonarr, sonarr-phantom
Provides: sonarr
Submitter: justin8
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 8
Popularity: 0.000000
First Submitted: 2014-12-11 00:32
Last Updated: 2021-06-22 16:59

Required by (5)

Sources (5)

Latest Comments

1 2 3 Next › Last »

fryfrog commented on 2021-03-08 22:54

Most users should use the sonarr package, only the technically inclined should be using this unstable nightly version.

fryfrog commented on 2020-07-09 03:41

The master and develop versions are effectively the same, and If you want v3 which is the one being actively developed, you want sonarr-phantom instead, which is also up to date.

20:39 <+dory> The latest release for develop is (2020-03-13 16:52 UTC)
20:39 <+dory> The latest release for master is (2020-03-13 21:56 UTC)
20:39 <+dory> The latest release for phantom-develop is (2020-06-25 21:59 UTC)

fryfrog commented on 2019-04-19 15:23

If you're running the sonarr-develop package, you obviously like the newest and most awesome things, so you'd probably like sonarr-phantom even more. This is v3, which has a totally new UI and comes w/ a huge number of usability improvements and many new features.

fryfrog commented on 2019-04-19 15:22

@Arzte: Right now, the released version of Sonarr is and the develop version is It's weird, but the next develop release will "fix" it.

demize commented on 2017-01-21 20:42

That pkgver function is really ugly. The PKGBUILD should never perform any network connections unless absolutely necessary, and this is most definitely not one of those cases. Please either make this a proper VCS PKGBUILD pulling the develop branch, or update the pkgver through some other means.

xelra commented on 2016-10-27 13:54

Trying to install this package with pacaur gives:

sonarr-develop package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD.

You surely have some kind of CI or at least some scripts for automation. Couldn't you make it so that the PKGBUILD is updated with pkgver and uploaded to the AUR? That would maybe also fix the SCRINFO mismatch. And it would be so much more convenient for the users of your package, because AUR helpers would work properly with it. It's really unfortunate that pkgver() functions don't get evaluated by AUR helpers for non-vcs packages.

justin8 commented on 2016-06-12 03:24

@xelra Sorry about that. updpkgsums overwrites SKIP checksums and broke it. Should be good now

xelra commented on 2016-06-11 09:57

The package doesn't seem to work anymore since a few days back. The md5 check has suddenly started to complain.

justin8 commented on 2015-10-30 22:06

I would like to tag it as -git or something, which would make aura/apacman/etc pick it up; but it's not a git package, so unless I manually do that all the time (new versions come out almost daily) and upload it, it won't really work.

If you don't want to do that, feel free to use my repo, it has this (and some other aur stuff) built weekly or when updates are pushed:

xelra commented on 2015-10-30 21:09

Can you make it so that the version of this package updates?

If I use an AUR manager like aura, unfortunately it will not update this package, because the version stays the same.