Your message dated Thu, 26 Jun 2014 10:52:22 +0200
with message-id <20140626085222.ga6...@sym.noone.org>
and subject line Re: Bug#748918: postgrey fails to start
has caused the Debian Bug report #748918,
regarding postgrey fails to start
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.)
--
748918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgrey
Version: 1.34-1.1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
A fresh install of postgrey on two Wheezy machines fails to start. Much like
was the case in debian bug #722136, starting the postgrey daemon on the
command
line reveals the same failure mode:
$ sudo postgrey --inet 10023
2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting!
pid(15633)
Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
Binding to TCP port 10023 on host 127.0.0.1 with IPv4
Insecure dependency in bind while running with -T switch at
/usr/lib/perl/5.14/IO/Socket.pm line 202.
Applying the same patch,
https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8,
fixes this problem for me.
I wonder if the changes introduced with perl-base 5.14.2-21+deb7u1
created the problem, but I haven't found a perl-base 5.14.2-21 package
to install to see if the problem goes away.
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages postgrey depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.49
ii libberkeleydb-perl 0.51-1
ii libnet-dns-perl 0.66-2+b2
ii libnet-server-perl 2.006-1+deb7u1
ii perl 5.14.2-21+deb7u1
ii ucf 3.0025+nmu3
Versions of packages postgrey recommends:
ii libnet-rblclient-perl 0.5-2
ii libparse-syslog-perl 1.10-2
ii postfix 2.9.6-2
postgrey suggests no packages.
-- debconf information:
postgrey/1.32-3_changeport:
--- End Message ---
--- Begin Message ---
Version: 1.34-1.2
Control: tag -1 + unreproducible moreinfo
Hi Geoff,
thanks for the report.
Geoff Crompton wrote:
> Package: postgrey
> Version: 1.34-1.1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
>
> Dear Maintainer,
>
> A fresh install of postgrey on two Wheezy machines fails to start.
>
> Much like was the case in debian bug #722136, starting the postgrey
> daemon on the command line reveals the same failure mode:
>
> $ sudo postgrey --inet 10023
> 2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting!
> pid(15633)
> Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
> Binding to TCP port 10023 on host 127.0.0.1 with IPv4
> Insecure dependency in bind while running with -T switch at
> /usr/lib/perl/5.14/IO/Socket.pm line 202.
>
> Applying the same patch,
> https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8,
> fixes this problem for me.
In that case this bug report is _the_ same issue as in #722136.
Because #722136 has been fixed by applying exactly the patch you
mentioned above.
Closing this bug for the version in Testing and Unstable, but leaving
it open in Wheezy for now.
> I wonder if the changes introduced with perl-base 5.14.2-21+deb7u1
> created the problem, but I haven't found a perl-base 5.14.2-21 package
> to install to see if the problem goes away.
You can find it http://snapshot.debian.org/package/perl/5.14.2-21/
A first glance at /usr/share/doc/perl/changelog.Debian.gz of
5.14.2-21+deb7u1 didn't reveal any changes which _obviously_ cause
such breakage. But it would be nice if you could check if the perl
stable update broke postgrey.
I also can't reproduce this issue with my postgrey installations
running under Wheezy (and with perl 5.14.2-21+deb7u1).
Do you have any third-party APT repositories in your sources.list
which may have updated some dependencies of postgrey? Can you run the
which-pkg-broke tool from the debian-goodies package like this:
$ which-pkg-broke postgrey
and send the output to the bug report?
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--- End Message ---
