Bug#821408: Pam 1.3.0

2019-01-25 Thread Florian Vessaz
Hello Steve and Andreas, On Thu, Jan 24, 2019 at 12:10:18AM +0100, Florian Vessaz wrote: [...] > I'll take the time to review those differences tomorrow or Friday night. I compared the two branches: [a] https://gitlab.gnugen.ch:fvessaz/pkg-pam.git ah/master [b]

Bug#821408: Pam 1.3.0

2019-01-23 Thread Florian Vessaz
Hello Andreas and Steve, On Wed, Jan 23, 2019 at 01:29:07PM +0100, Andreas Henriksson wrote: > Hello Florian and Steve, > > On Tue, Jan 22, 2019 at 02:40:00PM -0800, Steve Langasek wrote: > > On Tue, Jan 22, 2019 at 09:12:31PM +0100, Florian Vessaz wrote: > > > We've got no reply from the

Bug#821408: Pam 1.3.0

2019-01-23 Thread Andreas Henriksson
Hello Florian and Steve, On Tue, Jan 22, 2019 at 02:40:00PM -0800, Steve Langasek wrote: > On Tue, Jan 22, 2019 at 09:12:31PM +0100, Florian Vessaz wrote: > > We've got no reply from the current maintainers to this bug report since > > the approximately 2 and a half years it has been opened. I

Bug#821408: Pam 1.3.0

2019-01-22 Thread Steve Langasek
On Tue, Jan 22, 2019 at 09:12:31PM +0100, Florian Vessaz wrote: > We've got no reply from the current maintainers to this bug report since > the approximately 2 and a half years it has been opened. I thus think > it's safe to presume the current maintainers have no interest in keeping > PAM

Bug#821408: Pam 1.3.0

2019-01-22 Thread Florian Vessaz
Hi Andreas, On Thu, Dec 06, 2018 at 11:44:14AM +0100, Andreas Henriksson wrote: > Hi Florian, > > On Mon, Dec 03, 2018 at 10:13:23PM +0100, Florian Vessaz wrote: > [...] > > I updated my Git repository such that it now contains pam 1.3.1, the > > changes from the previous NMUs, your changes and

Bug#821408: Pam 1.3.0

2018-12-06 Thread Andreas Henriksson
Hi Florian, On Mon, Dec 03, 2018 at 10:13:23PM +0100, Florian Vessaz wrote: [...] > I updated my Git repository such that it now contains pam 1.3.1, the > changes from the previous NMUs, your changes and additional small > changes to address some of the lintian warnings. Thanks for doing that

Bug#821408: Pam 1.3.0

2018-12-03 Thread Florian Vessaz
Hi Andreas, On Fri, Nov 09, 2018 at 01:17:45AM +0100, Andreas Henriksson wrote: > Hi Florian, > > On Sun, Feb 05, 2017 at 05:48:23PM +0100, Florian Vessaz wrote: > > Hi, > > > > I've refreshed the patches against the 1.3.0 release and moved the > > packaging to Git as upstream is also using

Bug#821408: Pam 1.3.0

2018-11-08 Thread Andreas Henriksson
Control: retitle -1 New upstream release available (1.3.1) Hi Florian, On Sun, Feb 05, 2017 at 05:48:23PM +0100, Florian Vessaz wrote: > Hi, > > I've refreshed the patches against the 1.3.0 release and moved the > packaging to Git as upstream is also using Git. (This was discussed with > Steve

Bug#821408: Pam 1.3.0

2017-02-05 Thread Florian Vessaz
Hi, I've refreshed the patches against the 1.3.0 release and moved the packaging to Git as upstream is also using Git. (This was discussed with Steve two weeks ago.) I've imported the packaging history from bzr. The history of the packaging is not pretty, but I don't think there is a reasonable