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] https://salsa.debian.org/ah/pam.
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 current
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 thu
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 up-to-d
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 a
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 and
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 Git.
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 t
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 w
9 matches
Mail list logo