[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-puppet-devel] Bug#749479: Please include puppet into backports

Hi Stig,

On 18:13 Mon 17 Nov     , Stig Sandbeck Mathisen wrote:
> Apollon Oikonomopoulos <apoikos@debian.org> writes:
> > I have prepared a backport of puppet 3.7.2 and all its dependencies.
> > This currently includes:
> >
> >   augeas          1.2.0-0.2~bpo70+1
> >   facter          2.2.0-1~bpo70+1
> >   hiera           1.3.4-1~bpo70+1
> >   puppet          3.7.2-1~bpo70+1
> >   ruby-augeas     0.5.0-2~bpo70+1
> >   ruby-hashie     2.0.5-1~bpo70+1
> >   ruby-rgen       0.7.0-1~bpo70+1
> >   ruby-safe-yaml  1.0.3-1~bpo70+1
> >
> > I have tested the client part, and will also test the master part in
> > our setup tomorrow. If all goes well, I intend to upload them to
> > wheezy-backports if noone objects.
> A nice set of backports. :)
> Regarding testing, there are DEP-8 tests in the puppet packaging. The
> tests install a puppet master with apache and mod_passenger, and run the
> agent against it. That should be a decent indicator if the packages are
> good enough or not.

Good to know, I'll run the autopkgtests before deploying. Thanks!

> If any changes were necessary, and committed to git, would you like to
> push to a wheezy-backports branch on each packaging repository? If not,
> I should be able to use «gbp import-dsc» to add them to the packaging
> repository.

I was already granted access to the project on Alioth, so I will push 
the wheezy-backports branch. Note that no real changes seem to be needed 
in neither puppet, nor facter, but we'll see how testing goes.


Reply to: