Time for me to chime in. I think we made good progress today. The scripts should work fine in general, but our use-case still does not work well.
The biggest problem right now is when trying to run a cron job for the daily builds. Right now, this does not really work because of problems with the permissions. So we definately need some assistance in that spot. When run via crontab, some folders (like autom4te) are not recognized correctly as writable and thus ultimately the build process fails. Perhaps David can provide some insight? Another point is still the key for signing the packages. Right now we use a passphraseless key. While this works, it isn't very secure. At least we could get around using personal keys for now. If you guys have some ideas floating on how to improve this, please let us know. In the coming days, I will also add the changes I made for the scheduled releases to the scripts that were not yet added to the daily builds, mainly Kafka support Florian 2015-06-15 18:06 GMT+02:00 Rainer Gerhards <[email protected]>: > Hi folks, > > I have worked today with Florian on migrating my scripts to the new > environment. All in all, it looks promising, but there are a couple of > hopefully smaller nits (some permission issues with my setup, unclear > procedure on digital signing, some mail issues and maybe a couple of > other one). Florian will initiate discussions and/or ask for solutions > soon. > > I myself will be off for a pretty unscheduled two day biz trip for > Berlin tomorrow morning, so Florian will be the prime contact. > > Please note that what we have set up is the environment to build they > daily packages (when it full works). For the regular release packages, > we need to work together to find a good procedure to follow. But > getting the daily tarballs and packages in place is a very important > first step. I hope we can conclude this by the end of the week. > > I'd say that once it works, Brian can also add the 0mq components, > let's get them going for the daily builds first. Florian can aid with > file locations, scripts etc. Note that file system layout etc is also > documented (but can improve, of course). > > Rainer > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
