Package Details: sonarr-git 2.0.0.r7071.ef044f1ff-1

Git Clone URL: (read-only, click to copy)
Package Base: sonarr-git
Description: Automated TV series manager and downloader - git branch develop
Upstream URL:
Keywords: pvr
Licenses: GPL3
Conflicts: sonarr, sonarr-develop
Provides: sonarr
Submitter: shkercuh
Maintainer: fryfrog
Last Packager: shkercuh
Votes: 2
Popularity: 0.000000
First Submitted: 2015-02-18 22:00
Last Updated: 2017-01-30 00:20

Required by (7)

Sources (3)

Latest Comments

fryfrog commented on 2019-08-24 17:44

Is there anyone who uses this package that feels strongly about using it instead of sonarr or sonarr-develop? I've adopted it, but will probably request that it be merged w/ sonarr-develop unless someone very strongly likes it.

ejstacey commented on 2017-01-30 00:50

@shkercuh: Thanks! I can confirm it builds successfully now w/o the patch.

shkercuh commented on 2017-01-30 00:25

Thanks, @ejstacey. I've fixed the package now.

ejstacey commented on 2017-01-30 00:08

This fails to build with the current sonarr git:

-> Patching Mono-Set-process-name
error: src/NzbDrone.Mono/EnvironmentInfo/MonoRuntimeProvider.cs: No such file or directory
==> ERROR: A failure occurred in prepare().
The build failed.

I think the file got changed (renamed?) to MonoPlatformInfo.cs (in that same directory). I am not confident enough around c# to try and adapt the patch.

jebarb commented on 2015-09-03 00:26

nuget-cert no longer exists on AUR, presumably caused by the switch to AUR4. Package is now broken.

SAKUJ0 commented on 2015-04-13 14:02

maybe I am totally wrong with the sonarr->sonarr-git suggestion. sonarr-develop does not do this either.

SAKUJ0 commented on 2015-04-13 12:18

Hey there!

You asked over on sonarr's AUR page for us to check if you used best practices. By now, thanks to the helpful maintainers and submitters over there, I have managed to find and study

I have noticed something and I actually believe some changes could be quite important. Going through the guidelines top to bottom:

1) Package files should follow these general directory guidelines:
/opt/{pkg} Large self-contained packages such as Java, etc.
/usr/lib/{pkg} Modules, plugins, etc.
The important thing to note is that I believe {pkg} to be sonarr-git and not sonarr! The reason for that is actually quite important. Further below you will see how we should ensure directory usage never overlaps with various AUR packages. Imagine, the sonarr AUR package deciding to move to /opt out of the sudden.

2) Also, Sonarr technically is not *large*. But to my knowledge git packages without write access don't make a whole lot of sense (I don't use them myself).

3) "Please add a comment line to the top of the PKGBUILD file that follows this format."
# Maintainer: Your Name <address at domain dot com>
# Contributor: Previous Name <address at domain dot com>

shkercuh commented on 2015-04-10 10:24

Package has been updated to have Mono's debug mode enabled by default.

shkercuh commented on 2015-03-04 17:13

sonarr-develop is the official build; this one you'd compile yourself.

johannvonperfect commented on 2015-03-04 15:45

Is there a difference between this package and sonarr-develop?