[Pkg-swan-devel] Bug#1098865: Bug#1098865: strongswan-starter: bug in /usr/sbin/ipsec, service fails to start

[Yves-Alexis Perez]

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

On Wed, 2025-02-26 at 09:46 +0100, Giacomo Mulas wrote:
> Sorry, I missed that part, the NEWS.debian was huge and contained tons of
> unrelated stuff before.

apt-listchanges should only display the relevant / last entry. The 6.0.0-1 one
was a bit large because there were multiple important changes but I tried to
do separate paragraphs for the various changes. It might be worth noting them
in the trixie release note as well, actually.

>  I apologise for wasting your time. The problem
> arised because apt dist-upgrade made choices for me, evicting strongswan-
> charon
> in favour of other charon alternatives.
>  I now installed strongswan-charon
> and indeed strongswan-starter appears to work (I still have to test it
> better in some complex ipsec setup, but at least it appears to start
> properly). However, strongswan-charon appears to be incompatible with the
> strongswan package, which insists on installing charon-systemd and removing 
> strongswan-charon, which is a bit puzzling for "old" strongswan users like
> me. 

Yes. As indicated in the NEWS entry, the (upstream) strongSwan project moved
away from the ipsec command a long time ago and it's time Debian moves as
well, so the strongswan metapackage setting the default was updated.

You can safely remove the strongSwan metapackage and keep only the strongswan-
charon and strongswan-starter packages.

> It would be nice (at a "wishlist" level) to have this made a bit clearer
> and more explicit in the package description 

I tried to do my best but feel free to propose alternative wording. Especially
for trixie release notes.

> and/or making strongswan-charon
> provide strongswan.

That won't happen though.

> 
> Thanks for your kind response, and sorry again to have failed to properly
> read the NEWS.

No problem, hopefully your problems are now solved.

Regards,
- -- 
Yves-Alexis

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAme+2vEACgkQ3rYcyPpX
RFvZ9ggAlrRNVI1NsFAlYAy273zhQJcjFtSlG+CYXyFBYbyg4OFOpinmMNBdvyQC
qRVsCfte/ZwAX4avIbMjo6Iej9v8xIIghIY7553MhM+Mu9QCCAUoz1S4tQRogE5I
3Jxux6DSvJmhfk4ff8VNXOGVtPFGUPL2u+yOuxouXhg7Qiq7RsbtzgDcNt+/enYv
JilN1Xl+2smNFeqGYy+H75Beph7XgD6WonE1yEUPMEQmIdWQaPdac1UdrrUWuik2
BUP2WSwPKn6KUrI3/cCpr/PZx1rdU1+5uQ/xflh5WXgemU1Cb8st1ywAQyRxQtBt
TKsvI7znKenVyqHbQVBUP2Kh6+Yjgg==
=6IEK
-----END PGP SIGNATURE-----