Now and then Arch fixes something or changes something in its packages and then “require intervention on this upgrade”. Down the road this also will hit Manjaro and thats kind of a bad situation, because not all of our users are on the forums or even want to deal with that and I can fully understand it, because at those moments I’m also upset every single time.
We need to find a good solution for this.
Right now we workaround this by firing up manjaro-release, that deletes the pacman lock file, and forcefully call pacman inside a running pacman session. On all of my systems this wasnt working and it’s also not a good solution to remove the lock file or to call pacman at all.
So the rules are something like …
- no pacman/libalpm-frontend inside a running update
- no pacman --force at all
- no point where the upgrade itself could fail (like dependency circles, usage of the SyncFirst option, need of active internet while the upgrade is running, etc)
Testpkg-0.1-1-any.pkg.tar.xz, now try to install
Testpkg-0.1-2-any.pkg.tar.xz. It’ll fail because of
error: failed to commit transaction (conflicting files) Testpkg: /etc/testing exists in filesystem pacman -Qo /etc/testing error: No package owns /etc/testing
Now how to install/upgrade
Testpkg-0.1-2-any.pkg.tar.xz, without the need of the user itself?