Hi Simon, On Mon, May 05, 2014 at 01:27:28PM +0100, Simon McVittie wrote: > I'd rather not maintain nodm long-term, but I'd consider NMUing it if > the maintainers would like that to happen. I attach a possible patch > series, also available to pull from > https://alioth.debian.org/anonscm/git/users/smcv/nodm.git > (gitweb: <http://anonscm.debian.org/gitweb/?p=users/smcv/nodm.git>).
Neither Enrico nor Joachim are still working actively on this package. I have spoken with Enrico at DebConf 13 if he would be ok with opening a RFH bug for the package and he approved it. Then I totally forgot to actually do it. The pkg-fso is quite small (I think I'm the last DD :/) and nobody is working on nodm. Feel free to do whatever. > While preparing this patch series I noticed that nodm is maintained > in git as a non-native package, but it appears to be treated more like > a native package, with no real upstream and no use of debian/patches to > split out Debian changes - would the maintainers be willing to consider > making it a real native package? That would work better with git-buildpackage, > for instance. sounds reasonable to me. > Alternatively, if the maintainers would prefer to go to 3.0 (quilt) with > maintainer-approved changes made "upstream" but NMU changes in > debian/patches, I could prepare a version that looked more like that > and make it available for git pull instead. To summarize what Enrico told me: Do whatever is needed to keep nodm up to date and working. Thanks for working on this :) -- Sebastian
signature.asc
Description: Digital signature
