Bug#749479: Re: Bug#749479: Please include puppet into backports
On Fri, 10 Apr 2015 14:10:12 +0200 Raphael Geissert wrote: > On 8 April 2015 at 18:02, Apollon Oikonomopoulos wrote: > > On 15:17 Wed 08 Apr , Raphael Geissert wrote: > >> Could you please push your wheezy-backports branch to git? > > > > Pushed, apologies for the delay. I'll upload ruby-augeas shortly as > > well, so all (build-)deps should be in place after that. > > Thanks! it looks good so far. > > Will report back if I find anything interesting. It appears the dependencies have all made it to the wheezy-backports archive. I've built the puppet packages with success, although I haven't put them into production. Perhaps all that's left now is to nudge the final piece of this backport into the archive? -- Jerome signature.asc Description: OpenPGP digital signature
Bug#749479: Re: Bug#749479: Please include puppet into backports
Hi, On 15:17 Wed 08 Apr , Raphael Geissert wrote: > Hi, > > On 26 February 2015 at 23:06, Raphael Geissert wrote: > > On Thursday 26 February 2015 20:28:58 Apollon Oikonomopoulos wrote: > >> I uploaded augeas, facter, hiera and ruby-hashie to wheezy-backports. > >> Apart from facter, the rest are in backports NEW. As for the rest, > >> ruby-augeas has to wait for augeas and ruby-safe-yaml needs ruby-hashie, > >> so I'm not uploading them yet. > > > > Great, thanks! > > > > As for testing, I'm going to have to do some. Will report back. > > Could you please push your wheezy-backports branch to git? Pushed, apologies for the delay. I'll upload ruby-augeas shortly as well, so all (build-)deps should be in place after that. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Re: Bug#749479: Please include puppet into backports
Hi, On 26 February 2015 at 23:06, Raphael Geissert wrote: > On Thursday 26 February 2015 20:28:58 Apollon Oikonomopoulos wrote: >> I uploaded augeas, facter, hiera and ruby-hashie to wheezy-backports. >> Apart from facter, the rest are in backports NEW. As for the rest, >> ruby-augeas has to wait for augeas and ruby-safe-yaml needs ruby-hashie, >> so I'm not uploading them yet. > > Great, thanks! > > As for testing, I'm going to have to do some. Will report back. Could you please push your wheezy-backports branch to git? Thanks in advance! Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Please include puppet into backports
> On 25 Feb 2015, at 21:50, Raphael Geissert wrote: > > Hi, > > Has there been any progress regarding the backport of puppet? > I'm probably going to have to prepare the backports for work, so we could > try not to do things twice. > >> From some quick&dirty backports, I see that ruby-safe-yaml's test suite has > some failures under ruby 1.8 and 1.9.1. Have you taken a look at those? Please note that upstream provides packages (of pretty much all Puppet versions) that work perfectly fine on wheezy. If you just want to skip duplication of work, I’d use those. -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Re: Bug#749479: Please include puppet into backports
On Thursday 26 February 2015 20:28:58 Apollon Oikonomopoulos wrote: > I uploaded augeas, facter, hiera and ruby-hashie to wheezy-backports. > Apart from facter, the rest are in backports NEW. As for the rest, > ruby-augeas has to wait for augeas and ruby-safe-yaml needs ruby-hashie, > so I'm not uploading them yet. Great, thanks! As for testing, I'm going to have to do some. Will report back. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Please include puppet into backports
I uploaded augeas, facter, hiera and ruby-hashie to wheezy-backports. Apart from facter, the rest are in backports NEW. As for the rest, ruby-augeas has to wait for augeas and ruby-safe-yaml needs ruby-hashie, so I'm not uploading them yet. Cheers, Apollon signature.asc Description: Digital signature
Bug#749479: Please include puppet into backports
Hi Raphael, On 21:50 Wed 25 Feb , Raphael Geissert wrote: > Hi, > > Has there been any progress regarding the backport of puppet? > I'm probably going to have to prepare the backports for work, so we could > try not to do things twice. > > From some quick&dirty backports, I see that ruby-safe-yaml's test suite has > some failures under ruby 1.8 and 1.9.1. Have you taken a look at those? I have the packages ready but haven't found the time to actually test them in production (although ADT runs fine). As for ruby-safe-yaml, yes, I have already applied patches fixing compatibility with Ruby 1.8 and Ruby bug #6849 that affects our Ruby version. I guess I can go ahead and upload at least the dependencies to wheezy-backports today. I'll post a followup. Cheers and thanks for bringing this up, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Please include puppet into backports
Hi, Has there been any progress regarding the backport of puppet? I'm probably going to have to prepare the backports for work, so we could try not to do things twice. >From some quick&dirty backports, I see that ruby-safe-yaml's test suite has some failures under ruby 1.8 and 1.9.1. Have you taken a look at those? Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: [Pkg-puppet-devel] Bug#749479: Please include puppet into backports
Hi Stig, On 18:13 Mon 17 Nov , Stig Sandbeck Mathisen wrote: > Apollon Oikonomopoulos 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. Thanks, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: [Pkg-puppet-devel] Bug#749479: Please include puppet into backports
Apollon Oikonomopoulos 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. 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. -- Stig Sandbeck Mathisen signature.asc Description: PGP signature
Bug#749479: Please include puppet into backports
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 signature.asc Description: Digital signature
Bug#749479: Please include puppet into backports
On Tue, 27 May 2014, Klaus Ethgen wrote: > Package: puppet > Version: 3.6.1-1 > Severity: wishlist > > As Puppet is doing the backward compatibility the wrong way, there is > the problem that for the clients is always a current version of puppet > available but for the server, that would most likely run on stable, only > a old version is available that is not compatible anymore with the > puppet client version in sid and testing. > > So please add puppet and puppetmaster to backports to have a working > setup also with mixed environments. Hello. 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. To summarize what I found so far: puppet-common depends on: ruby-augeas ruby-hiera ruby-safe-yaml ruby-augeas build-depends on gem2deb (>= 0.5.0~) which needs to be backported as well build-depends on libaugeas-dev (>= 1.0.0) which needs to be backported as well ruby-hiera is in testing but not in stable seems to build ok ruby-safe-yaml is in testing but not in stable build-depends on ruby-hashie which needs to be backported as well I can try to build and upload all this but if someone wants to take over or just help, that would be more than welcome. [ Cc: debian-backports ] Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749479: Please include puppet into backports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: puppet Version: 3.6.1-1 Severity: wishlist As Puppet is doing the backward compatibility the wrong way, there is the problem that for the clients is always a current version of puppet available but for the server, that would most likely run on stable, only a old version is available that is not compatible anymore with the puppet client version in sid and testing. So please add puppet and puppetmaster to backports to have a working setup also with mixed environments. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages puppet depends on: ii init-system-helpers 1.18 ii puppet-common 3.6.1-1 ii ruby 1:2.1.0.1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter]2.1.2-2 puppet recommends no packages. Versions of packages puppet suggests: ii etckeeper 1.11 pn puppet-el ii vim-puppet 3.6.1-1 - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJThFQbAAoJEKZ8CrGAGfasmVoL/0H/40D938/oNGS5I/aoRPWw kXbZKVfdxOQ63ZsrlrDJzZmt2jVeDtaD/BWXOT2JCItxQVDm0uJpQH9e43f9C5s3 Sop2mrp1CEfjanv8ymR5LxxDB4biLSAuQKWn7b8L029bQqIQq5fPJUxaXvE1+npz cNthIP08JewWKCAUJ9kXkXqvgwsEHcGEZbkPrNdr4IbvBCs4pEBj9oY6xYZoH7+g SDSQyc/ynlh5uaE1zFh8pZEe/ilBVn1UdtACnCT/fjvwOITxLtZNzcMeWo2t76oX jWrkGjsoDMx8HiMAYQoQSS4ZNROBS5eOfXonf8z4Xde165J/PbuA5kReSl3IdDKh kA5H1UY5iJ/dqnMUnb1tBb9Z4FDc7f2DGBPnm+o8Gs00UqMNAi2ukzJ2XuNY2iMP kx8NAZUHHNNcAN0fT1ZgdLiW1qXeuwTsUqa/TKIXab+RxUm27V6ox6dmspgWzw/F fSTfT/Ln/mAOm+sK+nseuY8BNM6AYjoIRwPGVGY3rA== =T3x1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
