Source: vpnc
Version: 0.5.3+git20241220-1
Severity: important
Hi,
I just noticed strongSwan won't migrate to testing because of a failing autopkgtest in vpnc.
I'm a bit surprised that a depending package would prevent migration but
I'm not really fluent in autopkgtest.
A quick look at
https://ci.debian.net/packages/v/vpnc/testing/amd64/58881929/ shows:
51s autopkgtest [15:28:02]: test connect-to-server: - - - - - - - - - - results - - - - - - - - - -
52s autopkgtest [15:28:03]: test connect-to-server: - - - - - - - - - - stderr - - - - - - - - - -
52s Failed to stop strongswan-starter.service: Unit strongswan-starter.service not loaded.
It looks to me that you don't depend on the strongswan-starter package
(which provides the unit) and instead relied on the strongswan
metapackage. That metapackage got updated in 6.0.0-1 and now depends on
the (more modern) strongswan-swanctl.
Could you please upgrade the dependencies in the test and/or the
package, so strongSwan can migrate?
Don't hesitate to ask/discuss this with me as I might be totally wrong
about the vpnc dependencies and/or autopkgtest.
Thanks in advance!
Regards.
--
Yves-Alexis
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (450, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.17-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)