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.

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.

Hey @willemw , I see what you mean, makes no difference... but for the uninformed user, it looks like a downgrade or something, looks like going backward. That's why I got really confused. But thank you for the elucidation and the "bump" on the pkgver to keep things sane.

@spectroman: There is nothing to do. Update (i.e. reinstall) the package and/or update with the built-in SickChill updater, as usual, whenever you want.

The version number for VCS packages in the AUR, inside files PKGBUILD and .SCRINFO, don't really mean anything. Only after building the package does it get the real calculated version number.

I'll bump the version here anyway, to bring the .SRCINFO file in sync with the PKGBUILD file.

Something went wrong here? Or did I miss the memo on how this works?

I have installed last 15 Feb 2024 a new sickchill-git version which was:

pkgname=sickchill-git
pkgver=2024.2.2.r0

I noticed today there is a new release (from Sickchill) and as I came to check this package here, it "went back" to a 2022 version? What happened?

I even have built packages from 2023 releases... so I don't understand why the package went to further back.

Anything that we should know?

All program files are now removed before an upgrade.

@willemw said:

Now that I think about it: putting 'rm -rf /opt/sickchill/app' in pre_upgrade() in sickchill-git.install may fix all those "file exist" conflict errors.

I looked at PKGBUILD after you mentioned the rm -rf line and came to same conclusion. I think that would be a good idea, since it seems to run into conflicts otherwise.

If you do make this change, I'll be happy to test it.

Now that I think about it: putting 'rm -rf /opt/sickchill/app' in pre_upgrade() in sickchill-git.install may fix all those "file exist" conflict errors.

My recommendation would be to enable auto-updating in SickChill. And add 'sickchill-git' to IgnorePkg= in /etc/pacman.conf. Then, when you need to upgrade the package for some reason, uninstall the package first before upgrading/reinstalling.

Or do the reverse: disable auto-updating in SickChill. (Not sure, but you may then still get some of those "file conflict" errors though, if you don't uninstall before upgrading/reinstalling).

The point is not to have two conflicting updaters (Pacman and SickChill) running all the time, but only when you need to.

@willemw: Thanks for the update.

After my last message, I uninstalled the package again, did a "git clean -xfd" on the sickchill-git repo, pulled latest, and rebuilt/reinstalled. I then also did a second reinstall to see if it would allow overwriting, which worked.

Previously, I was running into several errors like:

sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/__pycache__/__init__.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/__pycache__/__init__.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/__pycache__/appdirs.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/__pycache__/pyparsing.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/__about__.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/__init__.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/_manylinux.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/_musllinux.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/_structures.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/markers.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/requirements.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/specifiers.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/tags.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/utils.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/__pycache__/version.cpython-310.pyc exists in filesystem
sickchill-git: /opt/sickchill/app/lib/python3.10/site-packages/pkg_resources/extern/__pycache__/__init__.cpython-310.pyc exists in filesystem

Generally I use the in-app update function, which usually has worked, but the last time I tried to update several days ago, it got into the "white screen" state and I had to manually intervene. Hopefully it's all squared away for now. Thanks again.

@albeec13:

An uninstall removes all the program code (the whole /opt/sickchill/app/ folder), including dependencies downloaded during the build, pychache folders, etc. See 'rm -rf /opt/sickchill/app' in sickchill-git.install.

Starting with an empty folder, before building and installing the package, should give you a clean install, apart from your data (/opt/sickchill/data/). Pay attention during the build that all dependencies are successfully downloaded.

You can update either by reinstalling the package or, more conveniently, keep automatically up-to-date by enabling SickChill's built-in updater.