On 06.11.25 16:03, 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, [...] > [...] > 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.
The reason for the conflict is pretty simple: Both packages provide a rather large common set of binaries, libraries, manpages, etc. Without putting *a ton* of work into making these packages co-existable, they will always conflict. Even when they would be able to co-exist, you'd then have to modify all your downstream tooling to use /usr/bin/doveadm23, /usr/bin/dovecot23, /usr/lib/dovecot23/dovecot-lda, etc. For a simple alternative package version, it's definitely preferred to keep the overall packaging process as similar as possible, just built from a different source version. To circumvent your issue, you'd just have to perform 'pacman -R --noconfirm dovecot' followed by 'pacman -S --noconfirm dovecot23' or vice-versa. By default, no package removal or installation will stop or start services automatically. Thus, even after e.g. removing 'dovecot' and installing 'dovecot23', the dovecot.service should still be running from the 2.4 binary. Although that might not last for lang depending on what it tries to do. Cheers -- Thore "foxxx0" Bödecker GPG ID: 0xEB763B4E9DB887A6 GPG FP: 051E AD6A 6155 389D 69DA 02E5 EB76 3B4E 9DB8 87A6
signature.asc
Description: PGP signature
