[Pkg-puppet-devel] Bug#749479: Please include puppet into backports
Apollon Oikonomopoulos
apoikos at debian.org
Mon Nov 17 14:54:05 UTC 2014
Hi all,
On 17:28 Tue 09 Sep , Santiago Vila wrote:
> I have an environment in which the clients will likely be upgraded a
> lot before than the server, so I would like to see a backport as well.
>
> The puppet source package seems to build ok under wheezy provided you
> use dh-systemd, which is already in wheezy-backports.
>
> The only problem is that not all the dependencies are in wheezy.
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.
> ruby-augeas
> build-depends on gem2deb (>= 0.5.0~) which needs to be backported as well
Note that gem2deb does not need backporting in these cases; as there is
no ruby 2.x in wheezy (which is the main reason to use >= 0.5.0), you
can just lower the build-dependency to >= 0.3.0.
Regards,
Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20141117/86870e8a/attachment.sig>
More information about the Pkg-puppet-devel
mailing list