Re: FW: knockd package long-standing bug

2019-05-17 Thread Brian
On Fri 17 May 2019 at 20:20:03 +, Riccardo Paolo Bestetti wrote: > > You could also consider just applying the patches which work for you > > and getting on with life. Bugs have been reported and not responded > > to. You have done your part; now it is up to someone else who is in > > a positi

RE: FW: knockd package long-standing bug

2019-05-17 Thread Riccardo Paolo Bestetti
-Original Message- From: Brian Sent: venerdì 17 maggio 2019 19:21 To: debian-user@lists.debian.org Subject: Re: FW: knockd package long-standing bug > You could also consider just applying the patches which work for you and > getting on with life. Bugs have been reported a

Re: FW: knockd package long-standing bug

2019-05-17 Thread Brian
On Wed 15 May 2019 at 08:02:01 +, Riccardo Paolo Bestetti wrote: > -Original Message- > From: to...@tuxteam.de > Sent: mercoledì 15 maggio 2019 07:47 > To: debian-user@lists.debian.org > Subject: Re: FW: knockd package long-standing bug > > Hi Tomás, > &

RE: FW: knockd package long-standing bug

2019-05-15 Thread Riccardo Paolo Bestetti
-Original Message- From: to...@tuxteam.de Sent: mercoledì 15 maggio 2019 07:47 To: debian-user@lists.debian.org Subject: Re: FW: knockd package long-standing bug Hi Tomás, > I don't understand to whom you sent a mail: to the maintainer's (Leonardo's) > Debian

Re: FW: knockd package long-standing bug

2019-05-14 Thread tomas
On Tue, May 14, 2019 at 10:56:18PM +, Riccardo Paolo Bestetti wrote: > >>Hello, > >> > >>Bug #868015 has been open since Jul 2017 [...] > >Hi Riccardo, I'll take a chance at answering your question [...] [good points] > Your input is much appreciated and you made some valid and interesting p

FW: knockd package long-standing bug

2019-05-14 Thread Riccardo Paolo Bestetti
>>Hello, >> >>Bug #868015 has been open since Jul 2017 and the fix consists in 3 >>lines added to the system unit file. I.e. knockd.service lacks the >>[Install] section and thus the service can't be made to auto-start after a >>reboot. >>Since the maintainer doesn't seem interested in fixing it