On Fri, Sep 4, 2015 at 2:43 AM Bruno Friedmann <[email protected]> wrote:
> On Thursday 03 September 2015 19.24:36 Michael Mol wrote: > > The Bareos Yum repositories haven't been updated in quite some time; for > > the 14.2 series, the Yum repositories' latest package is 14.2.2 (released > > 2014-12-12). The next official release on the 14.2 branch was on > > 2015-02-02, seven months ago, and 14.2.4 was released almost six months > ago. > > > > I filed a ticket a bit over a week ago ( > > https://bugs.bareos.org/view.php?id=509 ), but I haven't seen it so > much as > > acknowledged. I queried on IRC a couple days ago about what a polite way > to > > get developer attention to the ticket would be, and got no reply. > > > > So...what's a good, polite way to get the developers to update the yum > > repos? Filing a ticket has not yet helped. > > > > > It seems you don't have completely understood how the repositories are > working. > Yeah, after my email to this list, Stephan and Joerg reponsed and closed the ticket, respectively, with the relevant information. > > The binaries are released once a version is estimated stable enough > last time the version was 14.2.2 > This is what you've got publicly available on download.bareos.org > > Afterward, if a very blocking bug is found, (was the case in 12x series if > my > memory is right) another build may be published. > > It's up to you, if you need last binaries to > a) pick the source and build from there > Probably going to do this. Your git repository includes the release tags, so I can set up a Jenkins VM to periodically pull from Git, scan for new release tags, build the packages I need and stuff them into my own repo. (No trouble with AGPL3 here; I've no problem sharing any changes I make back upstream, and I've no problem ensuring the source is available downstream. As a courtesy, I can restrict the RPMs' distribution to within my organization.) > b) Buy a subscription, download.bareos.com has always the last new > version build > and available here. > I've had a look at the price list. It's not going to work for me for the same reason Bacula's price list didn't work for me; too many seats, and I'm an MSP, so it gets sticky if I want to use subscribed Bareos packages on more than one environment I manage. Better to avoid the whole mess altogether. Which I did with Bacula, but I didn't catch that Bareos only publicly released binaries for one minor out of each major version. > c) May be there a third way, if you can monitor, and help on the build > process. > (no warranty) > I can feed back to you guys the scripts and processes for what I have to build to do the same internally. That won't be a problem. > > Why such a way may you ask? > Building and maintaining an open source project, need $$$ to pay bills. > The price of the subscription is very low honestly. > > I hope this help you to better know how it works. > The price may be low relative to other offerings, but it's not low enough for my environment. I understand where you're coming from, and I only have two problems with contributing: Time and money. But any work I need to do to get this working for me, I can share back upstream. That doesn't cost me a thing. Truth be told, if I hadn't gotten a reply, I was going to go build the latest released 14.2 version anyway, and see if that solved the problem. If it didn't, I was going to dust off my native code developer hat and dig in. It's just that I always resist doing that in each case until I've gone through proper channels. Of course, any alterations I make would get pushed back upstream. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
