Package Details: sickrage-git 9.4.117.r0.g1db69f779-1

Git Clone URL: (read-only)
Package Base: sickrage-git
Description: A PVR application that downloads and manages your TV shows. Echel0n fork of sickbeard, with tvrage, torrents and anime support.
Upstream URL:
Licenses: GPL3
Conflicts: sickrage
Provides: sickrage
Submitter: justin8
Maintainer: willemw
Last Packager: willemw
Votes: 14
Popularity: 0.000003
First Submitted: 2014-05-07 02:20
Last Updated: 2019-07-10 18:59

Dependencies (5)

Required by (3)

  • ombi (requires sickrage) (optional)
  • ombi-dev (requires sickrage) (optional)
  • plexrequests (requires sickrage) (optional)

Sources (4)

Latest Comments

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

willemw commented on 2015-08-25 13:59

@MikuroK: Thanks. Updated.

Note: if upgrade fails (file "exists in filesystem" errors), then you can delete those files and folders manually. Make sure not to delete your configuration or your data files (.db files, for example).

MikuroK commented on 2015-08-25 12:11

sickrage now depends on extra/python2-mako

MikuroK commented on 2015-08-25 12:10

sickrage now depends on python extra/python2-mako

willemw commented on 2015-05-16 16:02

Note: removed the systemd user service file, because as normal user you don't have the file permissions to upgrade sickrage and also because a user service will only run when the user is logged in.

justin8 commented on 2015-01-02 01:55

Use epoch when you change major versioning methods so that it still shows as an upgrade.

willemw commented on 2015-01-01 15:04

Package changes:

Changed version numbering (appears to be a downgrade). To get the latest installation and systemd files, reinstall sickrage-git once.

Sickrage will now always restart when restarting or shutting down from the browser. This is, for example, useful when trying to restart after an upgrade from the browser. To start and stop sickrage, use systemctl.

Removed systemd user service file.

justin8 commented on 2014-12-22 03:02

@willemw: It replaces sickbeard-piratebay branch since that one disappeared and sickrage can import the database automatically; once everyone has moved off of the old one that no longer exists that could be removed from the package.

It should conflict with sickrage package, but this hasn't been updated since before sickrage had tagged releases, which meant there was no 'stable' version.

You're right about the updater should be removed from the stable one; but you have the option of not clicking update, and having a specific version being packaged. This can be good for the situations such as a few months ago where updating to master caused everyone's instance to crash due to a bad commit; you can just update via your AUR manager and always have something that will work. Feel free to remove the updater; both packages are orphaned since I haven't used sickrage in many months, I have no real way to test it.

willemw commented on 2014-12-18 08:44

Sickrage can update itself, so is there a real difference between sickrage and sickrage-git? The updater is not removed from 'sickrage'.

The 'provides', 'conflicts' and 'replaces' between several packages are not correct. They should normally not contain a -git package. When the other packages are correct, this package should have something like:


Maybe this, but I don't think so:
provides=('sickrage' 'sickbeard')
conflicts=('sickrage' 'sickbeard')

justin8 commented on 2014-12-18 00:11

Alright. the package is updated to use the new upstream source; version numbering has changed since they are finally doing tagged releases.

There is also a stable package uploaded now as well.

Let me know if you have any issues. The package builds fine; but I don't actively use this any more.

johannvonperfect commented on 2014-12-17 18:35

The upstream repository was moved to

Also, they have recently been doing actual releases as well so I don't know if you want to make a new package for a "stable"/non-git version (not that there is anything wrong with the git version). 4.0.1 was released today.

On the other hand, I know you're using sonarr at this point anyway so you might not be interested in updating this. Unfortunately my knowledge is too basic to maintain a package - I know just enough to see when something needs to be updated :)