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.

Just a follow up to previous comment. I opened an issue upstream but it seems the issue below was resolved back in march, and the latest version should not be experiencing it, as this offending code was removed. Details here: https://github.com/SickChill/SickChill/issues/8040

Just to be clear, I upgraded by pulling the latest sickchill-git from AUR, and installing with "makepkg -sir" as per usual. When this was not working correctly, I uninstalled sickchill-git via "pacman -R sickchill-git" and then reinstalled with makepkg. I also deleted some .cache and pycache directories and some files that were failing to be overwritten by the upgrade before getting it to successfully upgrade.

Is there some other procedure missing here that's preventing files from being upgraded to the latest package?

After updating within the GUI recently, i can no longer access the GUI, though the service appears to be running successfully according to systemd.

Getting this error when attempting to load the GUI:

Jul 26 11:18:38 arch systemd[1]: Stopping SickChill Daemon...
Jul 26 11:18:39 arch systemd[1]: Stopped SickChill Daemon.
Jul 26 11:18:39 arch systemd[1]: Started SickChill Daemon.
Jul 26 11:18:40 arch SickChill.py[967919]: Checking poetry
Jul 26 11:18:40 arch SickChill.py[967919]: sickchill installed: True
Jul 26 11:18:48 arch SickChill.py[967919]: sickchill installed: True
Jul 26 11:18:48 arch SickChill.py[967919]: /opt/sickchill/app/bin/SickChill.py:103: DeprecationWarning: currentThread() is deprecated, use current_thread() instead
Jul 26 11:18:48 arch SickChill.py[967919]:   threading.currentThread().name = "MAIN"
Jul 26 11:18:49 arch SickChill.py[967919]: sickchill installed: True
Jul 26 11:18:49 arch SickChill.py[967919]: Traceback (most recent call last):
Jul 26 11:18:49 arch SickChill.py[967919]:   File "/opt/sickchill/app/bin/SickChill.py", line 357, in <module>
Jul 26 11:18:49 arch SickChill.py[967919]:     SickChill().start()
Jul 26 11:18:49 arch SickChill.py[967919]:   File "/opt/sickchill/app/bin/SickChill.py", line 201, in start
Jul 26 11:18:49 arch SickChill.py[967919]:     failed_history.trimHistory()
Jul 26 11:18:49 arch SickChill.py[967919]: AttributeError: module 'sickchill.oldbeard.failed_history' has no attribute 'trimHistory'

I was able to load the gui successfully by commenting out the following lines in SickChill.py:

        # sure, why not?
        #if settings.USE_FAILED_DOWNLOADS:
        #    failed_history.trimHistory()

I guess it's probably an upstream issue, but posting here as well in case anyone runs into it.

Sickchill now caches all its build files locally in srcdir. To clear old cache files that are still outside the build directory, remove ~/.cache/pip/. It is probably also safe to remove ~/.local/share/virtualenv/.

Migrating to Python 3.

Switching from a "git install" to a "pip install".

NOTE:

If sickchill is already installed, then uninstall the package and delete the cached build files, then reinstall.

Check the journalctl output, if the service does not start. You may need to delete some cache files.

@nomad980: No. Restart=On-Success is there so that SickChill will restart after an update by the built-in updater.

Try to get more information from journalctl. Maybe there is a SickChill setting to increase log output.

@willemw the service seems to not want to start at boot. When I checked the status of the service just says "Failed with result 'exit-code'. When checking the sickchill.log in the data/log folder there is nothing new since the shutdown. Could it have something to do with the Restart=On-Success in sickchill.service?

Added https://aur.archlinux.org/packages/sickchill-git. Sickrage2-git may get merged into sickchill-git.