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. (This was discussed with > > Steve two weeks ago.) > [...] > > https://gitlab.gnugen.ch/fvessaz/pkg-pam.git > [...] > > I'm naturally open to constructive criticism. Let me know if there is > > something I can do to help out. > > I (unfortunately) just redid all of your work because I didn't > find this bug report because of the non-standard subject. :( > > OTOH I did against pam 1.3.1 so slightly newer. > See https://people.debian.org/~ah/pkg-pam/ > > I'm just at the point where it now builds. No further checks done yet. > > I guess we can always compare work to see if we did it the same.
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. > Since a long time has passed, I'd like to ask if you are still > interested in working on pam in Debian? Yes, I'm interested in having an up-to-date pam in Debian. Over the last two years or so, I've just installed pam through other means to get the latest upstream versions. So if I instead spend time to keep the package updated, that would actually be more useful. > I think an upload to experimental would be a good start and I'm willing > to sponsor if there's a need. (If we continue from your work then > incorporating all the NMUs that happened since it was prepared is > also needed.) I haven't really looked at the available options to get the changes uploaded. So any pointers would be welcomed. :-) Cheers, -- Florian
signature.asc
Description: PGP signature
