Your message dated Fri, 14 Mar 2025 21:45:14 +0000
with message-id <[email protected]>
and subject line Bug#1098714: fixed in strongswan 6.0.1-1
has caused the Debian Bug report #1098714,
regarding strongswan-starter should depends on strongswan-charon
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1098714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098714
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: strongswan-starter
Version: 6.0.0-2
Severity: important

When I run the command: "ipsec start", it fails to locate the necessary
binary.

    $ ipsec start
    IKE daemon '/usr/lib/ipsec/charon' not found

It appears that "strongswan-starter", built as /usr/sbin/ipsec,
locates and uses /usr/lib/ipsec/charon [1].

    [1] (src/starter/starter.c line 52) 
https://salsa.debian.org/debian/strongswan/-/blob/debian/master/src/starter/starter.c#L52

The binary /usr/sbin/ipsec is in "strongswan-starter"[2],
while /usr/lib/ipsec/charon is in "strongswan-charon"[3].

    [2] (/usr/sbin/ipsec       in "strongswan-starter") 
https://salsa.debian.org/debian/strongswan/-/blob/debian/master/debian/strongswan-starter.install#L5
    [3] (/usr/lib/ipsec/charon in "strongswan-charon" ) 
https://salsa.debian.org/debian/strongswan/-/blob/debian/master/debian/strongswan-charon.install#L1

Currently, "strongswan-charon" is listed under "Recommends:" for
"strongswan-starter"[4]. Shouldn't it be listed under "Depends:" instead?

    [4] (d/control line 219) 
https://salsa.debian.org/debian/strongswan/-/blob/debian/master/debian/control#L219

It was in "Depends:" when the latter was in "strongswan-ike"[5] 11 years
ago.

    [5] (-ike splitted into -charon and -libcharon) 
https://salsa.debian.org/debian/strongswan/-/commit/c707682e759fbd97b9603f650a491ef086f7fd5f#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2_178_176

Please forgive me if I am mistaken, as I do not fully understand the
context of these packages.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.15-amd64 (SMP w/22 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages strongswan-starter depends on:
ii  adduser                3.141
ii  debconf [debconf-2.0]  1.5.89
ii  init-system-helpers    1.68
ii  libc6                  2.40-7
ii  libstrongswan          6.0.0-2
ii  sysvinit-utils         3.14-1

Versions of packages strongswan-starter recommends:
pn  strongswan-charon  <none>

strongswan-starter suggests no packages.

-- Configuration Files:
/etc/ipsec.secrets [Errno 13] Permission denied: '/etc/ipsec.secrets'

-- debconf information excluded

--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 6.0.1-1
Done: Yves-Alexis Perez <[email protected]>

We believe that the bug you reported is fixed in the latest version of
strongswan, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez <[email protected]> (supplier of updated strongswan package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 14 Mar 2025 18:55:38 +0100
Source: strongswan
Architecture: source
Version: 6.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers <[email protected]>
Changed-By: Yves-Alexis Perez <[email protected]>
Closes: 1098714 1098857
Changes:
 strongswan (6.0.1-1) unstable; urgency=medium
 .
   * d/control: revert strongswan-charon to strongswan-starter dependency
     (Closes: #1098714)
   * New upstream version 6.0.1
     - fix regression in DHCP handling (Closes: #1098857)
   * d/strongswan-nm.install: ship the charon-nm config
Checksums-Sha1:
 642e77e52bd73bda4db80a46468e0070e7a3bd9c 3180 strongswan_6.0.1-1.dsc
 25cb159b4fedec58fed147fdda8230e5363baa20 4844260 strongswan_6.0.1.orig.tar.bz2
 5adc2e335e396551657b38d9b85829209ba37833 659 strongswan_6.0.1.orig.tar.bz2.asc
 2e889275a761939de642f3710084532deda545e2 128076 
strongswan_6.0.1-1.debian.tar.xz
 472404c952feb8e5feebf97ac5bf78f2e00ea7f0 18344 
strongswan_6.0.1-1_amd64.buildinfo
Checksums-Sha256:
 706477ba0960f5623e193455d90e55a3693ca97374629ffc9472e7860fc96264 3180 
strongswan_6.0.1-1.dsc
 212368cbc674fed31f3292210303fff06da8b90acad2d1387375ed855e6879c4 4844260 
strongswan_6.0.1.orig.tar.bz2
 da977644f98277849dffabaa84ccb1560473abecc1f4c647c55512ba64b24d46 659 
strongswan_6.0.1.orig.tar.bz2.asc
 44573d7f71337557bfd3f7d2ed74ec7ce43e7e63d861219bc8b70ac93b0b6945 128076 
strongswan_6.0.1-1.debian.tar.xz
 c37fe76324807bef27321b0e7eb438c723bdcd2555a24de531aa44ff22c97c01 18344 
strongswan_6.0.1-1_amd64.buildinfo
Files:
 3e272eb426f791fc44ddb31744c45020 3180 net optional strongswan_6.0.1-1.dsc
 c3ddc81d1d11ce3d5431e15da7718748 4844260 net optional 
strongswan_6.0.1.orig.tar.bz2
 a49da804cbd7502ce7564d153f14e91a 659 net optional 
strongswan_6.0.1.orig.tar.bz2.asc
 f2b170312d145130c5721d7554be181e 128076 net optional 
strongswan_6.0.1-1.debian.tar.xz
 bb5ae28b04b9061e3328b0f458c93eaf 18344 net optional 
strongswan_6.0.1-1_amd64.buildinfo


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

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmfUluIACgkQ3rYcyPpX
RFub2AgAraXeZEiedQmhSAc3lMk47PnCRyVC8wS/nPXYTqNyS2kaco2cD1J0ZR3Q
o+0pqVn9hWlofvUwDD1nK2Hu6QFG6P7gEvo/Kn2KTR02wjPw50xlGV4to5H/85L7
rd7/Xh8s2hUXQTa8WohEH2tBvdct9sFtZU5D3Befyup56ZOVoWN1eZUxLzE5+IBi
YXf8tTC1Xy8R/MdO53hyIYIiWDDTLJFm1H2Z27/x7D56nPV5G33VI79P+9sNe5zb
w+GCSfHAtkksN3SncPBXbdll8TjrimBneYYg3AYRT84ScQV8ZcU/lSZPZZ/7UHz0
rRCN8wARzB9TM5oghVPmfyZsLfwfuA==
=x6gM
-----END PGP SIGNATURE-----

Attachment: pgp8Lm4hFA58_.pgp
Description: PGP signature


--- End Message ---

Reply via email to