Your message dated Tue, 21 Nov 2017 12:50:23 +0000
with message-id <[email protected]>
and subject line Bug#880561: fixed in strongswan 5.6.1-1
has caused the Debian Bug report #880561,
regarding FYI - on FTBFS with newer glibc (>=2.26)
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.)


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

FYI - to prevent build error on newer glibc.
This will be in strongswan 5.6.1 according to the upstream git, but
depending how glibc 2.26 and strongswan upload versions to Debian this
might be an issue for you as well.

So FYI - Please take from the upstream git:

commit d4593353c97347fc9505a5a4fe3cfb66b246874f
Author: Tobias Brunner <[email protected]>
Date:   Thu Sep 14 11:59:30 2017 +0200

    utils: Include stdint.h

    Recent releases of glibc don't include the full stdint.h header in some
    network headers included by utils.h.  So uintptr_t might not be defined.
    Since we use fixed width integers, including the latter, all over the
place
    we make sure the complete file is included.

    Fixes #2425.

For now added in Ubuntu (has the newer glibc) as:
https://code.launchpad.net/~paelzer/ubuntu/+source/strongswan/+git/strongswan/+merge/332506

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 5.6.1-1

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: Tue, 21 Nov 2017 13:16:32 +0100
Source: strongswan
Binary: strongswan libstrongswan libstrongswan-standard-plugins 
libstrongswan-extra-plugins libcharon-extra-plugins strongswan-starter 
strongswan-libcharon strongswan-charon strongswan-nm charon-cmd strongswan-pki 
strongswan-scepclient strongswan-swanctl charon-systemd
Architecture: source
Version: 5.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers <[email protected]>
Changed-By: Yves-Alexis Perez <[email protected]>
Description:
 charon-cmd - standalone IPsec client
 charon-systemd - strongSwan IPsec client, systemd support
 libcharon-extra-plugins - strongSwan charon library (extra plugins)
 libstrongswan - strongSwan utility and crypto library
 libstrongswan-extra-plugins - strongSwan utility and crypto library (extra 
plugins)
 libstrongswan-standard-plugins - strongSwan utility and crypto library 
(standard plugins)
 strongswan - IPsec VPN solution metapackage
 strongswan-charon - strongSwan Internet Key Exchange daemon
 strongswan-libcharon - strongSwan charon library
 strongswan-nm - strongSwan plugin to interact with NetworkManager
 strongswan-pki - strongSwan IPsec client, pki command
 strongswan-scepclient - strongSwan IPsec client, SCEP client
 strongswan-starter - strongSwan daemon starter and configuration file parser
 strongswan-swanctl - strongSwan IPsec client, swanctl command
Closes: 878979 880561
Changes:
 strongswan (5.6.1-1) unstable; urgency=medium
 .
   * debian/control:
     - remove strongswan-ike{,v1,v2} packages.                   closes: #878979
   * New upstream version 5.6.1
     - fix FTBFS with glibc 2.26+.                               closes: #880561
   * debian/rules: explicitly enable tpm plugin
   * debian/strongswan-starter.install: install counters plugin
   * debian/libstrongswan.install: install MGF1 plugin
   * debian/libstrongswan-extra-plugins.install: install tpm plugin
   * debian/control:
     - update standards version to 4.1.1
     - replace dh-systemd build-dep by updated build-dep on debhelper
Checksums-Sha1:
 4e75585b75638e9f17853309efe84b573a2464ee 3378 strongswan_5.6.1-1.dsc
 d431809421fbe3a98223a4de6fb6895ea9c74a6f 4931679 strongswan_5.6.1.orig.tar.bz2
 d71b705507b99d2bbdc38326773ea544681f4808 989 strongswan_5.6.1.orig.tar.bz2.asc
 06e4638e873094f0539dbe189fad44e8c850f037 125700 
strongswan_5.6.1-1.debian.tar.xz
 d1bd2b875c27041337f52c5d887defdae7615b36 16664 
strongswan_5.6.1-1_amd64.buildinfo
Checksums-Sha256:
 800a6259dfe31afd2c220b69aeb4628e5b4ab0c6172311632a3a8ee9e3089e69 3378 
strongswan_5.6.1-1.dsc
 e0c282d8ad418609c5dfb5e8efa01b28b95ef3678070ed47bf2a229f55f4ab53 4931679 
strongswan_5.6.1.orig.tar.bz2
 92dab412a7e622cb3fac4c0a7d4f4a3ffbd73c6ae7cd642f80b2b5dd1aac45b7 989 
strongswan_5.6.1.orig.tar.bz2.asc
 8a5bbc21f5642eb151a13ba3daa84bad3a176abae477887d3c69af8318aeeb31 125700 
strongswan_5.6.1-1.debian.tar.xz
 b0c261ae1d832f57c1431790efb3dd98de55c5d2ccbf156fd14b5e58d2e40ab9 16664 
strongswan_5.6.1-1_amd64.buildinfo
Files:
 6a22ad02b57061195a85efe95aeb50ab 3378 net optional strongswan_5.6.1-1.dsc
 cb2241f1b96c524cd15b1c0f50ed9a27 4931679 net optional 
strongswan_5.6.1.orig.tar.bz2
 23fb17ae625bc52cacb006e42f0b3d55 989 net optional 
strongswan_5.6.1.orig.tar.bz2.asc
 5c4dea31b25dd924da88ca16b1deaaa9 125700 net optional 
strongswan_5.6.1-1.debian.tar.xz
 2e968ec89d273cf699660cd35cdd4686 16664 net optional 
strongswan_5.6.1-1_amd64.buildinfo

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

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAloUHNYACgkQ3rYcyPpX
RFsHTwf/eldHrYU6o4vCbDyZSrvasTyvjyFl+yGqyoYV1cszTSlmVKvjxSt7z0f8
hMGTPzh0Ol/h5JM7tTwTb6Nlx5h1bJxraGmc4dXdbHoOfXY6duffwFaOtIt5bzVa
UnS1Wu+su/tM4yiBeSdz+cxvFx3TLpD/zgst7mUn6U3aTI+oBQItMEO1xU5/LVPr
tw3D5/Xrw17KzaoC35cEF9mLjy/q6cegAf/OyQzi9e5GuKn8KKpB5UvvCx0XKIrI
P5hkcj086Z9sxBgTaEuxo780b+QX+OEWcx7fx9aKn2iwWK22B6yODGxS5l1LGyBu
XWe7q7VWvr2fGX8GOcIW7qJzwEs+Sw==
=b7X6
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to