Hi Yves-Alexis, * Yves-Alexis Perez <cor...@debian.org> [2025-07-20 16:29]:
I'm still not sure it's the right solution but I tried to add:Package: charon-systemd [...] Replaces: strongswan-charon (<< 6.0.1-1~) But I still get the same during the upgrade: Investigating (0) strongswan:amd64 < 5.9.8-5+deb12u1 -> 6.0.1-6 @ii umU Ib > Broken strongswan:amd64 Depends on charon-systemd:amd64 < none | 6.0.1-6 @un uH > Considering charon-systemd:amd64 -1 as a solution to strongswan:amd64 0 Holding Back strongswan:amd64 rather than change charon-systemd:amd64 Try to Re-Instate (1) strongswan:amd64 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/RenamingPackagesSo 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. Cheers Jochen
signature.asc
Description: PGP signature
