On Tue, Jul 10, 2012 at 7:33 PM, Clint Byrum
<spamaps@debian.org> wrote:
Hi Pall. I just found pynag the other day and I am using it to do some
automation of nagios deployment using juju.
I have been using the package of the last couple hours, and it works
great.
Since pynag is a public python module, the package should be called
python-pynag. If you want to have a meta-package called 'pynag' that
depends on that, that would be a good idea too, or you could even move
/usr/bin/pynag into its own 'pynag' package and the library would remain
in python-pynag.
Would you consider passing maintainership over ot the Debian Python
Modules Team? You can remain as an Uploader so your changes will not
be NMU's. By letting the team handle it they can assist with large scale
policy changs and stuff like that.
Something to consider. If you're ok with maintaining it yourself, thats
fine too.
So, just the python-pynag issue needs to be resolved, and then I think
this is good to go for sponsoring into Debian. 'testing' is frozen right
now, so it may sit in the NEW queue for a while, but its still worth
uploading to get it into unstable whenever it thaws.