-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 2025-07-21 at 18:12 +0200, Jochen Sprickerhof wrote: > > I have no idea why apt doesn't want to 'change charon-systemd:amd64'. > > The problem is that bookworm apt prefers keeping strongswan-charon > installed over other solutions. This is described in: > > https://wiki.debian.org/RenamingPackages > > So strongswan-charon would need to become a transitional dummy package > that depend on charon-systemd and the maintainer scripts should take > care of transitioning the configuration files. The Conflicts: can also > be dropped then. > > Feel free to ask if you need more explanation.
Hi Jochen, thanks but it's not a case of renaming packages. Both strongswan-charon and charon-systemd exist in Bookworm and Trixie. Both are working and can be installed if the users choses so. They fill the same role (they include an IKE daemon for setting up IPsec tunnels) but differently. strongswan-charon is the "historical" (legacy) charon daemon, which is beeing phased out in favor of charon-systemd. That's why we updated the dependency for the strongswan metapackage. We recommend people to migrate to the new daemon, and for new install that'll be the case. For old installations one could actually wonder if we should actually migrate, but in any case we would still want to actually upgrade the packages. So I'm not sure how to express that in apt relationships. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh+a+wACgkQ3rYcyPpX RFuTwQgAzP+lKMPhqwnu8i/ebDDC2uXLV8Kkunk42r3mj1EHGLLclpSPm2IXO+tC oPV6DXXCwEIteR8nE/+vgxuVsq/+dMlJ1oAYbL9WPB3nivyBkESzMNlf4L2xyTZy NHM073WHw7qIFC+BiUDH6xzWDVw9JAzssDr5lfsVmYTjTuNhOelziz99SsQzo0sU Dbr979a+Vt5jZEOGOCvxxYCxsnsoBtxMgyiYCpWozy87FKv3WT1XWKSCxGA3zJ4I ErD0GWDf5ryg7mIkKM5rolsaaA2AeG5lFIqdUmWGVKfJ6x/n8FAKdj5MtDz6MIj2 PyAh4w23ihOzy9or44olpu/tV0UmEQ== =Rriw -----END PGP SIGNATURE-----
