I'll be packaging 3.6 as soon as it's released. Currently we have a (mostly) functioning 3.5.3.
It is our (the CfEngine-debian team and Antonio) intention that the cfengine-debian team take over official maintainership, probably in time for Jessie. If you'd like to help, we need some work in transition scripts. We've made some design decisions that are incompatible with previous debian packages of cfengine. We need some shell scripts to do the migration steps and some debconf dialogs to make sure the user is aware and confirms the change. See issue #53. If you're interested, make a fork and send pull requests. You can also work on (or file) any other issues. As far as when we will be ready to upload, we'll need issue #53 addressed first. Once that's done I think it will be safe enough for general testing/usage. -- Brian > On Feb 18, 2014, at 7:08 AM, Thomas Koch <[email protected]> wrote: > > Hi, > > this is a reply to the debian bug report asking for a newer cfengine version, > CCing the members of the debian packaging team on github. > > It seems there are people working on packaging a current cfengine version at > github: > https://github.com/Webhuis/Cfengine-debian/wiki > > I don't know, whether there have been trials to contact the current (MIA?) > maintainer of cfengine3, Antonio Radici. I'll send a MIA request to debian- > devel right after this mail > > @DebianPackagingTeam: Do you need any help? I'm not a DD, so I can't sponsor > your packages, but I might have some experience in packaging. Do you have an > estimation of when there might be an upload of cfengine 3.[56] to Debian? > > Regards, Thomas Koch
smime.p7s
Description: S/MIME cryptographic signature
