The init.d script for bacula, when using postgres, contains : use postgres when it should be use postgresql Reproducible: Always Steps to Reproduce: 1.Install bacula with postgres use flag 2.Start bacula with postgres stopped Actual Results: Postgres doesn't start
Created attachment 73120 [details] bacula-1.36.3-r2.ebuild change in src-install USEDB='use postgres' to USEDB='use postgresql'
Re-assigning to herd wrt Bug 98505. Remove labmonkey from metadata.xml please.
I believe this bug to be fixed in bacula-1.36.3-r3.ebuild.
Actually upon further investigation, recommend that this bug be closed as this branch is no longer patched. The current stable patched branch from upstream bacula is 1.38.11. Arches please stabilize that.
There is no ebuild for 1.38.11 in Portage :) The latest version in Portage is 2.0.2, but it's still archmasked. It should work regarding the postgresql thingy, though :)
(In reply to comment #5) > There is no ebuild for 1.38.11 in Portage :) > The latest version in Portage is 2.0.2, but it's still archmasked. > It should work regarding the postgresql thingy, though :) > So then this would be a RESOLVED WONT FIX then wouldn't it?
Here you go :)
Lol =P well I hate it when these bugs are open for *years* =P but if its been fixed in a new ebuild might as well let everything be posted against that then eh? or no? I'm still new to this so if this isn't how its done tell me to shut up or what not =)
Sorry, I don't understand your last posting :] Would you mind rephrasing it?
(In reply to comment #9) > Sorry, I don't understand your last posting :] > Would you mind rephrasing it? > Sure, I was saying that it bothers me when a bug is open a long time. That is why I tried to get this bug closed. I hope that since this bug is closed people will log bugs against the new version instead. I felt like maybe you were just marking it in hopes of getting me to be quiet in a funny way. =) If my repeated posting is causing problems, then please tell me that. I am not trying to be trouble.