-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sun, 2025-07-20 at 12:25 +0200, Yves-Alexis Perez wrote: > In any case, help would be appreciated on how to interpret apt output and > how > to make it accept the removal of strongswan-charon for upgrading the > strongswan metapackage. > > Maybe I need to add Replaces: strongswan-charon to the charon-systemd > package > but I'm not sure it really express the situation.
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'. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh8/UQACgkQ3rYcyPpX RFshbwf8CXCTAJg5Vv1ubcZswDF5AtZ7Yt4qfaScZ34PQ/4PvgJSWsvDu7nfuaQU yV0gBqaYUNUbzOSBLFI20JGT1rl9xrddtbZep3DE/Y4QVQRlwbEwXAtyy1Z9e1O4 ZpEce4iYM/lZvIQ2/W2cQnT5vdxjD3YtfxQfkWoF2dZsXDwbwWGrndg6tWexpbnv eNthF0WYCChkloVF6ZFwDMGQcAINrNtJT8lcnlo0YCl1/b6DkzuJsI998lvQ3Bcf eoQF90U2kiTd+tp+PKwkbVGQLzjmEKHKoyJP91eiAn8KRYTDj9wV2b/VsRsXWJQe i4h7QmXtZQIbV1HkqEunpI8fGmHM6Q== =Ehh8 -----END PGP SIGNATURE-----
