[Pkg-puppet-devel] Inclusion of new/updated puppet module packages

[Russ Allbery]

Michael Weiser <m.weiser at science-computing.de> writes:

> I've created Debian packages for a number of puppet modules. They can be
> found here: ftp://ftp.science-computing.de/outgoing/weiser/puppet/. New
> packages are:

> puppet-module-domcleal-augeasproviders_1.2.0-1
> puppet-module-erwbgy-limits_0.3.1-1
> puppet-module-jakeb-system_1.0.0-1
> puppet-module-saz-timezone_3.1.1-1

> Updated packages are (no real need, just a case of "while I'm at it
> let's run uscan"):

> puppet-module-puppetlabs-apt_1.7.0-1.1
> puppet-module-puppetlabs-concat_1.1.2-1.1
> puppet-module-puppetlabs-ntp_3.3.0-1.1
> puppet-module-puppetlabs-stdlib_4.4.0-1.1

> I'd love to have them included in Debian because I need to deploy them
> in an environment where there's no Internet connectivity (and thus no
> puppet module install) but access to a Debian mirror.

Hi Michael,

Thank you very much for this!  I'm not sure if I personally will get a
chance to look at them soon, but wanted to let you know that your work
here is really appreciated.

Just to set expectations, it's too late at this point for new work to be
included in the jessie release, but the packages could go into sid and
into the next release after jessie, and of course could be backported to
jessie.

> I am no Debian developer, however, and my continued availability for
> maintainership is uncertain.

Do you feel like you might have some spare moments from time to time?  If
so, I'd encourage you to create an Alioth account if you haven't already
so that you can get commit access to the pkg-puppet repository and commit
your packages directly.  That makes ongoing collaboration a lot easier,
and doesn't come with any assumption that you'll be actively maintaining
them all the time.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>