-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 2025-07-21 at 18:40 +0200, Jochen Sprickerhof wrote: > > 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. > > Why would people not upgrade? > I think a new Debian release is a good reason to migrate.
Yes indeed, we just don't want to force that on them. They can still keep strongswan-charon (and strongswan-starter) along with their current configuration, and migrate on their own term. > > > So I'm not sure how to express that in apt relationships. > > If both should be in trixie I would say: > > Package: strongswan > Depends: charon-systemd | strongswan-charon, strongswan-swanctl Ah, good point, that might work, let's try that. I'll report back here. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh+bfcACgkQ3rYcyPpX RFvlNwf/fxRNWlBYMonBMKtNivxgxqPKruU/wsMH9OF3WcyIqBLdBRjQ2xsx4haB aEBMHTY5u5jknAoq/9B740ZLztxacg3BoFm93uz7Vv8vU39yDAv6qyG63Wnt9X5p ip4PyG/zhmjJhRAvuHKs1sh+FoHevMpspbUn2TaCrVFFJYVsBykPLSyt2oI3JQ7P GVtJChFMNydnS0Y9c44xy2VdOwenNYYnH4onurdopYyTjdBv/WKySY3dpdqnSsHs bR6uxBM2bmMbB1AoWlK2F1yukvmvo/uKN0FGRdmSCinfief+G6RR42dhKJqNbd/s h6u11/xYDm1yeGm4EEKn+Gk7eYZU7A== =RHxU -----END PGP SIGNATURE-----
