Bacula 1.38.0 is out. Is a new ebuild scheduled ? Reproducible: Always Steps to Reproduce: A new release of bacula is out ... There are quite a few new interesting functionalities : http://www.bacula.org/?page=news&PHPSESSID=da34ba415d46d7a5399491c6c6408426
- The Director, Storage daemon, and File daemons are Deamons are not compatible with prior versions. All FDs must be upgraded at the same time. So, if you're using the latest bacula on other boxes, in my case, FreeBSD as bacula-dir, you cannot backup Gentoo box.
Bacula 1.38.1 is out. There are people who are implementing bacula by now and intent to use the latest version. Holding Bacula's ebuild because of legacy versions is not a good excuse.
Sorry folks, I've been out of town on business for the last week and am just now getting back to my desk so if you can hold on just a little longer I will try to get 1.38.1 into ~x86 sometime soon.
let me know if new unstable ebuild is available. I'm willing to test it.
Bacula 1.38.3 is out. Why not publish a unstable ebuild in the portage tree ? Have a nice day.
Created attachment 75550 [details] new ebuild for version 1.38.3 of bacula. Hi, this is an ebuild for last version of bacula. It is only a hack of the 1.36 ebuild. Someone more skilled than me in writting ebuilds should verify it and correct it if necessary. It compiles fine here, but I'm still learning bacula so don't know if it is working fine... Hope that help.
Created attachment 75555 [details, diff] die if sed failed Q1: SQL scripts should be under /usr/share? Q2: why /var/bacula? should it be created by ebuild? I'll test it tommorow.
Created attachment 75586 [details, diff] a patch to bacula-1.38.3.ebuild sed fix and openssl support also fixed #108971 it worked here.
*** Bug 118473 has been marked as a duplicate of this bug. ***
Hmm... I should have searched here first, I am too created an ebuild for 1.38.3 which is basically hacked 1.36. The difference - I added ssl & python by default. What does it take to publish an ebuild to the portage tree? Tested the "new ebuild for version 1.38.3 of bacula" - works fine
hadfield/fserb. You're listed as the maintainers. If you want I can take this package off your hands and bump it.
(In reply to comment #8) > Created an attachment (id=75586) [edit] > a patch to bacula-1.38.3.ebuild > > sed fix and openssl support > also fixed #108971 > it worked here. > Emerge successfully on PowerPC client and EM64T Server. trombik, please add ~ppc keywoerd. But I didn't understand how to use it, yet. :P
if no dev takes care of an ebuild any more, should I fill a bug for it? as for keyoword, it'll be added (hopefully) when the ebuild get proper love.
(In reply to comment #13) > if no dev takes care of an ebuild any more, should I fill a bug for it? > as for keyoword, it'll be added (hopefully) when the ebuild get proper love. I my humble opinion, the answer is yes and no. If we use this app, to added keywords is bit of useful for us to do emerge processes. (Of course, JUST to add the keyword is very easy like as much as I can. But I know you're a security guru and the digest verification is important as you know. :) At least, if the ebuild has the keyword, some users which have the arch as admin may try to test, I think. If we do not use this app, to take care of the ebuild is JUST pain for devs. So, the keyword SHOULD NOT be added, I think. But, if so (and if I remember correctly), why did you said to me like that?: "Hey, DO *FULL* backup your system with this app!" At least, I want to do full backup my system with this app. Otherwise, should I use other apps? This app is recommend by you, so I would like to use it. Chris is planning to write how-to doc, I heard. (Realy? :P) And then, I said JUST request as "please", it is NOT "SHOULD DO". If devs do not want to added ~ppc keyword, no offence taken.
Created attachment 77777 [details] bacula-1.38.5.ebuild JFYI, bacula 1.38.5 is out. this bacula-1.38.5.ebuild is just a renamed version of bacula-1.38.3.ebuild. http://sourceforge.net/project/showfiles.php?group_id=50727&package_id=44845&release_id=386633 emerged with the following USE flags [ebuild R ] app-backup/bacula-1.38.5 -X +client-only -gnome -mysql +ncurses -postgres +readline -sqlite +ssl -static -tcpd 0 kB
I'm not sure what happened to labmonkey. I'll try to put this into portage this weekend if I don't hear from him before then.
any "official" 1.38.5 to be in the tree? any problems with the attached ebuild? Thanks.
so far, bacula-1.38.5.ebuild works fine for me. I don't see any serious problem.
same here, no probs.
bacula-1.38.5.ebuild works fine for me too!
Permission to co-maintain this and kick this ebuild to the tree :P?
> Permission to co-maintain this and kick this ebuild to the tree :P? :confused: There is a bacula-1.38.5.ebuild in portage for almost 1 month now which is more advanced than this ebuild and works great...
(In reply to comment #22) does that mean we finally find the developer?
(In reply to comment #23) > (In reply to comment #22) > > does that mean we finally find the developer? > The developer (Chris Lee) created this ebuild.
1.38.9 in portage, closing an irrelevant bug.
