Your message dated Wed, 17 May 2017 10:48:40 +0000
with message-id <e1dawvu-0004sc...@fasolo.debian.org>
and subject line Bug#862780: fixed in haproxy 1.7.5-2
has caused the Debian Bug report #862780,
regarding haproxy: Please build with -DUSE_GETADDRINFO for functional IPv6 
hostname lookups
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 ow...@bugs.debian.org
immediately.)


-- 
862780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haproxy
Version: 1.7.5-1~bpo8+1.1
Severity: normal
Tags: patch ipv6

Dear Maintainer,

Without this configuration option, haproxy cannot resolve hostnames that have 
only IPv6 (AAAA) records. To quote the project's README:

Recent systems can resolve IPv6 host names using getaddrinfo(). This primitive
is not present in all libcs and does not work in all of them either. Support in
glibc was broken before 2.3. Some embedded libs may not properly work either,
thus, support is disabled by default, meaning that some host names which only
resolve as IPv6 addresses will not resolve and configs might emit an error
during parsing. If you know that your OS libc has reliable support for
getaddrinfo(), you can add USE_GETADDRINFO=1 on the make command line to enable
it. This is the recommended option for most Linux distro packagers since it's
working fine on all recent mainstream distros. It is automatically enabled on
Solaris 8 and above, as it's known to work.


-- System Information:
Debian Release: 8.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- a/debian/rules	2017-04-11 16:07:51.000000000 +0200
+++ b/debian/rules	2017-05-16 22:48:29.820047917 +0200
@@ -12,6 +12,7 @@
 	 USE_OPENSSL=1 \
 	 USE_ZLIB=1 \
 	 USE_LUA=1 \
+	 USE_GETADDRINFO=1 \
 	 LUA_INC=/usr/include/lua5.3
 
 OS_TYPE = $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
--- a/debian/rules	2017-04-11 16:07:51.000000000 +0200
+++ b/debian/rules	2017-05-16 22:48:29.820047917 +0200
@@ -12,6 +12,7 @@
 	 USE_OPENSSL=1 \
 	 USE_ZLIB=1 \
 	 USE_LUA=1 \
+	 USE_GETADDRINFO=1 \
 	 LUA_INC=/usr/include/lua5.3
 
 OS_TYPE = $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)

--- End Message ---
--- Begin Message ---
Source: haproxy
Source-Version: 1.7.5-2

We believe that the bug you reported is fixed in the latest version of
haproxy, 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 862...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos <apoi...@debian.org> (supplier of updated haproxy 
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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Wed, 17 May 2017 13:01:45 +0300
Source: haproxy
Binary: haproxy haproxy-doc vim-haproxy
Architecture: source
Version: 1.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian HAProxy Maintainers 
<pkg-haproxy-maintain...@lists.alioth.debian.org>
Changed-By: Apollon Oikonomopoulos <apoi...@debian.org>
Description:
 haproxy    - fast and reliable load balancing reverse proxy
 haproxy-doc - fast and reliable load balancing reverse proxy (HTML documentatio
 vim-haproxy - syntax highlighting for HAProxy configuration files
Closes: 862780
Changes:
 haproxy (1.7.5-2) unstable; urgency=medium
 .
   * Enable getaddrinfo() support, allowing resolution of hostnames to IPv6
     addresses (Closes: #862780). Thanks to Anton Eliasson
     <de...@antoneliasson.se>!
Checksums-Sha1:
 b01ce5c4cf17153e4f8a9ff03167d813a3994e7f 2329 haproxy_1.7.5-2.dsc
 999981df24b062cf09096dd2a2cd9efa58e431eb 62544 haproxy_1.7.5-2.debian.tar.xz
 71744633f07b2d8fa5608de87f8435b7aded3798 6960 haproxy_1.7.5-2_source.buildinfo
Checksums-Sha256:
 63d9a6ff7b120f40d732a373b55c28b0d7068494f8f741a5b61a418474f9873b 2329 
haproxy_1.7.5-2.dsc
 62342cf9014b3b259295a248f7071af3405e49ea55f8da8e27211ca408ad805f 62544 
haproxy_1.7.5-2.debian.tar.xz
 304978813b99b9e8a4ca785e1d0b084c45943ebd2365bc4921f2c14765c2f883 6960 
haproxy_1.7.5-2_source.buildinfo
Files:
 69ba2f13e9dfd54a5992d247fac58eeb 2329 net optional haproxy_1.7.5-2.dsc
 0dfd6e14b553093e4fc5c71d4b934811 62544 net optional 
haproxy_1.7.5-2.debian.tar.xz
 41a349406039a527e09de245c4def72c 6960 net optional 
haproxy_1.7.5-2_source.buildinfo

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

iQJHBAEBCAAxFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAlkcJm0THGFwb2lrb3NA
ZGViaWFuLm9yZwAKCRD1GxjHICSCJOiLEADEIpEmCxZv2b/Ks4M7bPVzUs8shwms
Ij1xJAcmt1g/NiL+pd1WDVhU/bTr9FDE1CKliiJFQrT+o8iPZWLB15YggJrYDP/Q
JVNHG53KO26zELwK0TFem/naTDOt7KQEbZjhO3Oip+cnoYARAn8xxkOibQNit3ht
qJWx9vapE8jMvzLg0s+QBP0337fQ20cyLVFkei58n8vu9wtvpXlehJYIG+RWVwB7
AUBoditOg++cy76W7idGDbH2STjMy9PFt2sM+sLne0k3hzLpRwm1SnhGt+lJTt0Q
q09elb+zbKSroem3/JSUajUzgENi+CUeJAZdhDmMnkl3E5lMrYMa06f6+Pj4LTPZ
UtVUJsa50F076xi+dN3OmCSKTlcKr2IIr70w6Qo36ideJyBNuJp2Fg7bf/zNGhBX
czXP3Bt5tF/QV1UXc9naf1frGZ+kdcrJUo2/augK0Xh0CWgOKxsPqoHbuASvjLWN
mhyhvAjuknuJeFtMLdc7whBD2dwYPRDbiEmoWeYG2B1K5ZRZPumUG51uIhIvZpa5
xljxvSN2+kwOlxmlHPGW8yes6xyh2TAxnB0PmMGPbzgqckd9Iaqo6ch6G6OeDWAH
XL4fqTs9EVQyznF484G6/Ty4xZreJ5YsJDRF+vIg77OTF4xGejf21EG3FGkaZQQJ
+UzQX+7xO8GYzA==
=BJjP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to