On Wed, Oct 13, 2010 at 8:54 AM, Dennis Hoppe <dennis.ho...@debian-solutions.de> wrote: > Hello Felix, > > Am 13.10.2010 16:43, schrieb Felix Frank: >> On 10/13/2010 04:37 PM, Disconnect wrote: >>> - lenny (stable) <http://packages.debian.org/lenny/puppet> (admin): >>> centralised configuration management for networks >>> 0.24.5-3: all >>> - lenny-backports >>> <http://packages.debian.org/lenny-backports/puppet>(admin): >>> centralised configuration management for networks >>> 0.25.4-2~bpo50+1 [*backports* <http://backports.debian.org/>]: all >>> >>> Looks pretty out of date to me. Lets see.. 0.24.5-1 was packaged on "Thu, 24 >>> Jul 2008 10:58:08 +0100". (Days after release, which is good, but over 2 >>> years ago, which is bad..) Looks like 12 releases since then. >>> >>> 0.25.4 was released upstream in January and is -also- not "up to date" >>> (minor, major, then another minor revs since then..) >> >> What's with the nitpicking? They call it "Debian stable" because it is, >> well, stable. You get what you choose. >> >> I think the OP suggest that Reductive Labs offer the download of >> packages that both >> a) will install on Debian (stable?) and >> b) offer varying amounts of bleeding-edged-ness. >> >> This idea is not without merit, I might add. > > i know Debian is very stable, but they also have really long release > cycles and sometimes you just want to have the current features. > > There is a reason, why many companies are offering her own Debian > packages and i have had many discussions with some of my colleagues, > which are debian developers.
We have an enthusiastic and active Debian packaging group (Hi Stig Mathias Russ!) and I think we're managing to balance Debian policy and user needs pretty well. If you want the current features, grab the more recent packages. This is standard Debian practice, and working with distro policy is a good thing for upstream vendors to do in my opinion. http://www.debian.org/doc/FAQ/ch-choosing.en.html#s3.1.3 "As you can see, stability and novelty are two opposing ends of the spectrum. If stability is required: install stable distribution. If you want to work with the latest packages, then install unstable." We do need to post up decent instructions on using git-buildpackage to package your own debs if needed, as it's a simple couple of commands. I've sent it to this list at least once, but we need to document this on the puppet deb pkg site. > But that is not the point. I need help with my module. ;) Lets get it back on the rails then :) You might find more luck if you put the manifests into pastebin.com or directly inline, as it's much easier for people to glance at your setup without requiring them to download attachments and unpack them. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
