* Yves-Alexis Perez <cor...@debian.org> [2025-07-22 08:04]:
On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote:> So, it seems to work on Bookworm -> Trixie but won't that mean we'll have > the > same problem again (for those installs) in Trixie -> Forky if I remove the > alternate dependency at that point?For Forky you would have to do the transition dummy package and maintainer scripts conversion then.Hey Jochen 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?What should happen to users having strongswan and strongswan-charon installed when upgrading to Forky?
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.
In any case, I would propose to add the alternate dependency for Trixie and do do an upload soon as time is running out.
Cheers Jochen
signature.asc
Description: PGP signature
