-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, 2025-07-22 at 08:43 +0200, Jochen Sprickerhof wrote:
> > as already said, that's not an option for us. There's no plan to retire
> > strongswan-charon (and strongswan-starter) packages.
> 
> Why would you drop the alternate dependency in Forky then?

Because at some point I'd like that strongswan only dependency would be for
charon-systemd and strongswan-swanctl.
> 
> What should happen to users having strongswan and strongswan-charon 
> installed when upgrading to Forky?

I think I would have expected strongswan to be upgraded, strongswan-charon
(and strongswan-starter) removed and charon-systemd/strongswan-swanctl
installed.

It would have been better to have the package co-installable but they bind on
the same port so that doesn't really make sense.
> 
> Btw. there is currently a new solver in apt that would remove 
> strongswan-charon and install charon-systemd instead. That will likely 
> become the default in Forky so it could work without a transition dummy 
> package then.

That would be nice, yes.
> 
> In any case, I would propose to add the alternate dependency for Trixie 
> and do do an upload soon as time is running out.

I guess so…
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh/t4gACgkQ3rYcyPpX
RFuvSAgAtFc/s/rDb91CcOMPR8W55GAYlbJHYlab+w+B2y0KgFdvkicRsF0FrmAI
3gXIzxhQWMgx8gbydhuntRflJxph14jZgE6D218lsoLVHftrtfF7UnQ40lfcYCRB
SR7A2KtvxvtZ9xcozwyTyWaT+MNupfq+n/qAtJ3lfQjGV9AJN/H346Zr3nYEhKft
hjxGDhwIYbCq6uDD0hLX2hhxNBUZuIQ3jmvO/MC6RLjwS4mRjKcydaOeQ0wvzK3m
TA14vjtYzlaEvtYcSQp4aigwXF7SHUGV6IPmsYX0WH6SowsCl6B45zb641ddbG7v
JIG7i2KX1MK6yo0c7IwPudB70wiZuw==
=elR7
-----END PGP SIGNATURE-----

Reply via email to