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 additional small > > changes to address some of the lintian warnings. > > Thanks for doing that and for still being interested. > I'll try to find time and motivation to look over your new version > soon. (Please feel free to poke me if I seem to have forgotten about > this.)
Thank you for trying. I suppose you might not have found the time or might not have the motivation. Which is perfectly fine, there are no obligations. > [...] > > I haven't really looked at the available options to get the changes > > uploaded. So any pointers would be welcomed. :-) > > I assume you're not a DD, so unless current pam maintainers show > any interest I guess it's up to me to review your stuff and then > I think it would be quite harmless if we upload it to experimental. 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-date in Debian. [...] > Please see here if you're > interested in the administrative details on how it should be > done properly these days: > > https://wiki.debian.org/PackageSalvaging > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging The following points are taken from the Debian Developer's Reference document mentioned above: * NMUs, especially if there has been more than one NMU in a row. Since the 18th of April 2016, date at which this bug was opened there was: 2016-06-02 1.1.8-3.3 NMU 2016-12-20 1.1.8-3.4 NMU 2017-01-04 1.1.8-3.5 NMU 2017-05-27 1.1.8-3.6 NMU 2018-02-07 1.1.8-3.7 NMU 2018-08-13 1.1.8-3.8 NMU 2019-01-09 1.1.8-4 upload by a maintainer * Bugs filed against the package do not have answers from the maintainer. 9 out of the 15 first bugs displayed on the BTS page appear to have been neglected for more than a year. I did not inspect the other bug reports. https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pam No answer since #917374 December 2018 Important #916169 December 2018 Important #914541 November 2018 Important #890626 February 2018 Normal #890524 February 2018 Important #889910 February 2018 Important #824607 May 2017 Normal #834589 August 2016 Important #332292 June 2013 Important #583958 May 2013 Normal #691008 October 2012 Normal #601825 November 2010 Important #569746 February 2010 Important #336513 October 2005 Important #182605 July 2008 Normal * Upstream has released several versions, but despite there being a bug entry asking for it, it has not been packaged. This bug reports asked for an up-to-date version of PAM in April 2016. In February 2017, I proposed an updated package including PAM 1.3.0 but no feedback was received from the maintainers. In December 2018, I proposed an updated package including PAM 1.3.1 but no feedback was received from the maintainers. The version currently in Debian is 1.1.8 which has been released by upstream in September 2013. So, it appears to me that the Package Salvaging process is applicable. It's is however unclear to me if the Package Salvaging process can be performed by someone like me who is not a DD or a DM. As it is defined in the Debian Developer's Reference, I presume the process is to be performed by a DD. Is there a chance to get an up-to-date version of PAM in Buster? Cheers, -- Florian
signature.asc
Description: PGP signature
