In fact full aptitude utput is this:

# LC_ALL=C aptitude full-upgrade -V
...
The following packages will be REMOVED:
  network-manager-strongswan{a} [1.1.2-1]
  strongswan-ikev2{a} [4.3.2-1.3]  
  strongswan-nm{a} [4.3.2-1.3]
  ...
The following packages will be upgraded:
  ipsec-tools [1:0.7.3-6 -> 1:0.7.3-7]
  racoon [1:0.7.3-6 -> 1:0.7.3-7] 
  ...
...
#

Full apt-cache output:

$ apt-cache show strongswan-ikev2
Package: strongswan-ikev2
Priority: optional
Section: net
Installed-Size: 616
Maintainer: Rene Mayrhofer <rm...@debian.org>
Architecture: i386
Source: strongswan
Version: 4.3.2-1.3
Provides: ike-server
Depends: libc6 (>= 2.4), libcurl3 (>= 7.16.2-1), libgmp3c2, libldap-2.4-2 (>= 
2.4.7), libpam0g (>= 0.99.7.1), libstrongswan, strongswan-starter | 
strongswan-nm, bsdmainutils, debianutils (>= 1.7), ipsec-tools, host, iproute
Pre-Depends: debconf | debconf-2.0
Suggests: curl
Conflicts: freeswan (<< 2.04-12), openswan, strongswan (<= 4.2.12-1)
Filename: pool/main/s/strongswan/strongswan-ikev2_4.3.2-1.3_i386.deb
Size: 228682
MD5sum: 19ae8455189d2bae381287175df775ac
SHA1: aeaee74a22193287d010364635353b524994fd13
SHA256: 8ea625f93b0677f5ebde3c54cd233d4044f6ed2f9d4476a235aeb76dd973dbc3
Description: strongSwan Internet Key Exchange (v2) daemon
 StrongSwan is an IPsec-based VPN solution for the Linux kernel. It uses the
 native IPsec stack and runs on any recent 2.6 kernel (no patching required).
 It supports both IKEv1 and the newer IKEv2 protocols.
 .
 Charon is an IPsec IKEv2 daemon. It is
 written from scratch using a fully multi-threaded design and a modular
 architecture. Various plugins provide additional functionality.
 .
 This build of charon can run in parallel with pluto, the IKEv1 daemon.
Homepage: http://www.strongswan.org
Tag: qa::low-popcon
$

$ LC_ALL=C apt-cache show racoon
Package: racoon
Priority: extra
Section: net
Installed-Size: 1116
Maintainer: Stefan Bauer <stefan.ba...@cubewerk.de>
Architecture: i386
Source: ipsec-tools
Version: 1:0.7.3-7
Provides: ike-server
Depends: debconf (>= 0.5) | debconf-2.0, ipsec-tools (= 1:0.7.3-7), libc6 (>= 
2.8), libcomerr2 (>= 1.01), libgssapi-krb5-2 (>= 1.8+dfsg), libk5crypto3 (>= 
1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libpam0g (>= 0.99.7.1), libssl0.9.8 (>= 
0.9.8m-1), perl
Conflicts: ike-server
Filename: pool/main/i/ipsec-tools/racoon_0.7.3-7_i386.deb
Size: 379302
MD5sum: c6b4fbc3a0ed3463dee80df654065146
SHA1: beadab5577e3574cc4cc5104c1beca3a8cdfb421
SHA256: 46decfa33c3e45808eb9248899c393584a0a230b99316d4be68d814bd3eb27d2
Description: IPsec IKE keying daemon
 racoon is the KAME IKE (ipsec key exchange) server. It can be used with
 the Linux ipsec implementation in 2.6 and later kernels or with
 the 2.4 backport of the ipsec changes.
Tag: interface::daemon, network::server, role::program, security::cryptography

Package: racoon
Status: install ok installed
Priority: extra
Section: net
Installed-Size: 1116
Maintainer: Stefan Bauer <stefan.ba...@cubewerk.de>
Architecture: i386
Source: ipsec-tools
Version: 1:0.7.3-6
Provides: ike-server
Depends: debconf (>= 0.5) | debconf-2.0, ipsec-tools (= 1:0.7.3-6), libc6 (>= 
2.8), libcomerr2 (>= 1.01), libgssapi-krb5-2 (>= 1.7dfsg~beta1), libk5crypto3 
(>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libpam0g (>= 0.99.7.1), libssl0.9.8 
(>= 0.9.8m-1), perl
Conffiles:
 /etc/init.d/racoon f0c0eba484b1844d661615044e0513a8
 /etc/racoon/racoon.conf 219cc425820a34d12a65fd9dd02b0675
 /etc/racoon/psk.txt 8912f9ec996ab814f11c45064e80b749
 /etc/racoon/racoon-tool.conf c86858a7a12d4e995c5a038558c6e1a2
Description: IPsec IKE keying daemon
 racoon is the KAME IKE (ipsec key exchange) server. It can be used with
 the Linux ipsec implementation in 2.6 and later kernels or with
 the 2.4 backport of the ipsec changes.
$



So APT behaves correctly, just it choose to remove racoon, not strongswan-ikev2.
Aptitude do the reverse, removes strongswan-ikev2, not racoon.

Both solutions are acceptable, in fact in aptitude one can choose
other solution.


Regards.

-- 
Witold Baryluk
JID: witold.baryluk // jabster.pl

Attachment: signature.asc
Description: Digital signature

Reply via email to