On Wed, Jun 11, 2014 at 04:13:28PM +0200, Axel Beckert wrote:
> Control: tag -1 + fixed-upstream
> 
> Hi,
> 
> Geoff Crompton wrote on 22 May 2014:
> > 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.
> 
> Despite not being mentioned in the upstream changelog[1], that patch
> has been applied[2] upstream and is part of the recent 1.35 upstream
> release[3].
> 
> [1] http://postgrey.schweikert.ch/pub/Changes
> [2] https://github.com/schweikert/postgrey/commits/master
> [3] http://postgrey.schweikert.ch/pub/postgrey-1.35.tar.gz
> 
> So packaging the new upstream release should fix the issue in Sid and
> Jessie. Maybe a stable-update with only that patch would be a good
> idea, too.
> 
> Antonio and Jon: Do you need help in maintaining postgrey in Debian?
> 
> I'm a long-time postgrey user at work as well as at home, and
> occassionally contribute to upstream's default whitelist. I also know
> postgrey's upstream developer from maintaining fping in Debian which
> has the same upstream developer. I could join you as co-maintainer.

Hi Axel,
if you have time it would be great if you could prepare an NMU for the patch at
the existing release and then I can add you as co-maintainer and we can work on
the 1.35 packaging (there is already a git, you just need to be on
collab-maint).

On the long run we should run postgrey using a team rather than a single person
(me), that should make things easier in terms of maintainership and uploads.

Does it sound good to you?

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to