Your message dated Wed, 12 Oct 2016 19:33:27 +0200
with message-id <20161012173327.liwhtcwx2wuye...@sid.showcase.amasol.de>
and subject line Re: Bug#788831: proftpd-basic: error setting listen fd 
IPV6_TCLASS: Protocol not available
has caused the Debian Bug report #788831,
regarding proftpd-basic: error setting listen fd IPV6_TCLASS: Protocol not 
available
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.)


-- 
788831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-basic   
Version: 1.3.5-1.1+deb8u1
Severity: normal

On a proftpd server reachable by IPv4 & IPv6, IPv6 connections fail with the
following line in logs:

        2015-06-15 14:02:30,212 servername.domain proftpd[26589] 
servername.domain (2001:41d0:aaaa:bbbb::1[2001:41d0:aaaa:bbbb::1]): error 
setting listen fd IPV6_TCLASS: Protocol not available

This bug is fixed upstream, and the according patch has been backported in the
latest 1.3.5 tree:
https://github.com/proftpd/proftpd/commit/415e723333a1d1626a93a8eeb77e5660877ee8ed

Upstream bug report: http://bugs.proftpd.org/show_bug.cgi?id=4055

Please consider including this bugfix in the next Debian packages. 

I think this /might/ also be a fix for #620871, but I'm not sure if it's
related or not.

Thanks,
Felix Krohn

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

Kernel: Linux 3.14.25-xxxx-grspax-ipv6-64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages proftpd-basic depends on:
ii  adduser            3.113+nmu3
ii  debconf            1.5.56
ii  debianutils        4.4+b1
ii  libacl1            2.2.52-2
ii  libc6              2.19-18
ii  libcap2            1:2.24-8
ii  libmemcached11     1.0.18-4
ii  libmemcachedutil2  1.0.18-4
ii  libncurses5        5.9+20140913-1+b1
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  libpcre3           2:8.35-3.3
ii  libssl1.0.0        1.0.1k-3+deb8u1
ii  libtinfo5          5.9+20140913-1+b1
ii  libwrap0           7.6.q-25
ii  netbase            5.3
ii  sed                4.2.2-4+b1
ii  ucf                3.0030
ii  zlib1g             1:1.2.8.dfsg-2+b1

proftpd-basic recommends no packages.

Versions of packages proftpd-basic suggests:
pn  openbsd-inetd | inet-superserver  <none>
ii  openssl                           1.0.1k-3+deb8u1
pn  proftpd-doc                       <none>
pn  proftpd-mod-geoip                 <none>
pn  proftpd-mod-ldap                  <none>
pn  proftpd-mod-mysql                 <none>
pn  proftpd-mod-odbc                  <none>
pn  proftpd-mod-pgsql                 <none>
pn  proftpd-mod-sqlite                <none>

-- debconf information:
* shared/proftpd/inetd_or_standalone: standalone

--- End Message ---
--- Begin Message ---
Version: 1.3.5a-1

On 15.06.15 Felix Krohn (felix.kr...@ovh.net) wrote:

Hi,

> On a proftpd server reachable by IPv4 & IPv6, IPv6 connections fail
> with the following line in logs:
> 
>       2015-06-15 14:02:30,212 servername.domain proftpd[26589] 
> servername.domain (2001:41d0:aaaa:bbbb::1[2001:41d0:aaaa:bbbb::1]): error 
> setting listen fd IPV6_TCLASS: Protocol not available
> 
> This bug is fixed upstream, and the according patch has been backported in the
> latest 1.3.5 tree:
> https://github.com/proftpd/proftpd/commit/415e723333a1d1626a93a8eeb77e5660877ee8ed
> 
> Upstream bug report: http://bugs.proftpd.org/show_bug.cgi?id=4055
> 
According to that bug record it is fixed in 1.3.5a currently in
unstable.  Hence I'm closing that bug.

> Please consider including this bugfix in the next Debian packages. 
> 
> I think this /might/ also be a fix for #620871, but I'm not sure if it's
> related or not.
> 

Hilmar
-- 
sigmentation fault

--- End Message ---

Reply via email to