On 11/6/25 5:03 PM, David C Rankin wrote:
Arch pacman gurus,
I'd thought I would automate the swap between dovecot versions for
testing between dovecot23 and dovecot with pacman -U --noconfirm, but
since pacman considers dovecot23 and dovecot to be in conflict, the
upgrade fails with:
:: dovecot-2.4.2-3 and dovecot23-2.3.21.1-3 are in conflict. Remove
dovecot23? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: dovecot-2.4.2-3 and dovecot23-2.3.21.1-3 are in conflict
Job for dovecot.service failed because the control process exited with
error code.
See "systemctl status dovecot.service" and "journalctl -xeu
dovecot.service" for details.
Manually swapping is easy enough, it just takes a little more time to
do the service stop, pacman upgrade, copy the changed configs and
restart the service. Is there any way to script around the dovecot23/
dovecot conflict issue?
Moreover, since dovecot23 and dovecot are single packages, why the
conflict? Seems a warning about config breakage would be appropriate,
but the user should be able to swap between them without triggering a
conflict.
I use the btrfs filesystem, I create a subvolume for version 1 and
install the base packages and the "old version" It is configured and
boots and "runs" using systemd-nspawn.
I then create a subvolume for version 2, install the base packages and
the "old version" It is configured and boots and "runs" using
systemd-nspawn.
I then can use machinectl to run/start a "version" and then I can shut
it down and run the other, ie
machinectl start "version 1"
machine login "version 1"
when I am finished then
machinectl start "version 2"
machine login "version 2"
systemd containers are your friend
--
Hindi madali ang maging ako
