Package Details: sonarr-develop 2.0.0.5250-1

Git Clone URL: https://aur.archlinux.org/sonarr-develop.git (read-only)
Package Base: sonarr-develop
Description: TV download automation for usenet and torrents.
Upstream URL: http://www.sonarr.tv
Licenses: GPL3
Conflicts: sonarr
Provides: sonarr
Submitter: justin8
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 8
Popularity: 0.309793
First Submitted: 2014-12-11 00:32
Last Updated: 2018-09-18 16:42

Dependencies (11)

Required by (4)

Sources (4)

Latest Comments

1 2 3 Next › Last »

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.

P.S.:
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: https://repo.dray.be/dray-repo-0.7-1-any.pkg.tar.xz

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.

justin8 commented on 2015-08-10 04:19

I won't be adding support for auto update, it completely goes against the whole philosophy of packages and the Linux ecosystem. Your package manager should handle your updates, and not random programs being able to download and modify executable binaries at will on a system, it is a glaring security hole.

If you want to follow those directions, I would suggest copying the service file from /usr/lib/systemd/system/sonarr.service to /etc/systemd/system/sonarr.service and modifying it. That way it isn't overwritten on package updates if you use it in the future, but keeps your service file changes.

The update function should also work if you just change ownership of the directory in /usr (don't do this, it's a bad idea) and if we remove the -data option, as sonarr doesn't keep that flag when it restarts itself. I'll be removing the -data flag when the regular sonarr package does, at the moment it is staying the same so that you can change from one version to the other without having to manually move files between the two locations.

Evils commented on 2015-08-10 02:12

Would be useful to exchange the systemd/service file with the one mentioned here to make auto update work:
http://dominicm.com/install-nzbdrone-sonarr-on-arch-linux/

justin8 commented on 2015-05-22 14:19

It has a pkgver function, so building the package will update to the correct version like all other VCS packages. Also saved me having to upload a new package twice a week ;)

SAKUJ0 commented on 2015-05-22 11:01

I suppose the version in the AUR title, 2.0.0.2597-1, is out of date and will be most of the time. Right now this package links to 2.0.0.3159. Is there a way people like me can update the title to reflect that?