Arch Linux User Repository

If an upgrade fails with "error: failed to commit transaction (conflicting files)", then one way of removing the conflicting files is to uninstall this package first.

To migrate your data from sickrage2, do something like:

# systemctl stop sickchill sickrage
# rm -rf /opt/sickchill/data/*
# cp -a --sparse=always /opt/sickrage/data/* /opt/sickchill/data/
# chown -R sickchill:sickchill /opt/sickchill/data/

Switched to https://github.com/SickChill/SickChill

@kanachan: Thanks. There is an update problem at the moment with the newer repo. When you click the update link:

"Unknown current version number: If you've never used the SickRage upgrade system before then current version is not set. — Update Now"

sickrage crashes. See https://github.com/Sick-Rage/Sick-Rage/issues/5024

Repository changed to: https://github.com/SickChill/SickChill due to legal issues between developers. The current one is pointing to an non official fork which I don't trust the developer (bitcoin mining software, stored end user's logins to torrent sites on his server, plans to make the app pay-to-use)

The upstream repo is currently down and has been for the past week or so, due to a DMCA takedown request issued by the original author. https://github.com/github/dmca/blob/master/2017/2017-07-17-SiCKRAGE.md From the takedown request, it sounds like the Sickrage2 guys removed the "Author: echel0n <echel0n@sickrage.ca>, URL: https://sickrage.ca" lines from files that had them. Per GPLv3, you're not allowed to remove the original author's copyright lines, only append your own. echel0n still owns copyright to the original files and any diffs he contributed just as the new authors own copyright to any diffs they created. But "Author: foo" isn't exactly the same as "(C) date FOO" as recommended by GPLv3. The Sickrage2 guys expect the repo to be back online shortly; hopefully they're right. This fork is way better. The drama in this project never ends, eh? Seems like mistakes were made on both sides. If you currently have it installed and are getting a mako error when trying to access the settings, there's instructions on Sickrage2's website: http://sickrage.github.io/ If anybody has a mirror of the source code and is thinking of publishing it, note that I am NOT a lawyer, but I think you'd be safe to publish it if you at least restore the original "Author:" lines and any original Copyright or (C) lines. I'd probably recommend just waiting it out, though.

Had an issue with a recent update https://gist.github.com/BubbatheVTOG/51f5828ca7f4d1ec32ca2261e55b8658 Remade SSL certs as outlined in this issue. Problem solved. https://github.com/SickRage/SickRage/issues/2917 Don't know if anybody else is having this error, but I thought I'd share anyways.

When your data/configuration files are in /opt/sickrage/data: If an upgrade fails with "error: failed to commit transaction (conflicting files)", then you can uninstall sickrage to get rid of the conflicting files.

This package kept failing to build and install properly for me. I had to move /opt/sickrage/app to /opt/sickrage/app.old in order to complete installation.

@lowph: Done.