Want to get rid of built_with_use and has been in the tree for ages. Ok for stable? Just migrated it to EAPI 2.
(In reply to comment #0) > Want to get rid of built_with_use and has been in the tree for ages. Ok for > stable? Just migrated it to EAPI 2. I just committed 3.0.2 which fixes lots of bugs reported for 2.4.x, thus I'd rather wait for 3.0.2 to go stable in a few weeks...
Hi, the current stable of bacula is old and fails to build. What's the state of the 3.0.* series. Can we get going with 3.0.3 ?
I just dropped maintainership of bacula.
IMHO 2.x and 3.x should be dropped and 5.0.2 should be stabilized in a few weeks...
(In reply to comment #4) > IMHO 2.x and 3.x should be dropped and 5.0.2 should be stabilized in a few > weeks... > Something wrong with 5.0.1-r2?
As there were some important bug fixes I would suggest waiting for 5.0.2.
(In reply to comment #6) > As there were some important bug fixes I would suggest waiting for 5.0.2. > Is 5.0.1-r2 a worse option than the current stable 2.4.1-r1?
Package is in tree for >30 days without bugs. As the stable version in the tree is very old now and has some serious problems I suggest to ignore the minor problem in Bug #322181 for now. It can be worked around (see comment #3). It will be fixed in next revision. Arches please do your work.
When setting multiple databases the ebuild fails: You have set bacula-5.0.2 to use multiple database types. * I don't know which to set as the default! * You can use /etc/portage/package.use to set per-package USE flags * Set it so only one database type, mysql, postgres, sqlite3 I think this behaviour is deprecated and should be replaced by chosing a default. (See "Conflicting Useflags": http://devmanual.gentoo.org/general-concepts/use-flags/index.html )
I did the build tests and ebuild checks for x86. Except the minor annoyance that a simple 'emerge bacula' will fail on an average desktop system (assuming it has USE="mysql sqlite3") this seems to be fine. I did not test all of the functionality, somebody else should judge this if needed.
amd64 stable mentioned behaviour is in all ebuilds, including stable, so that's not a regression I've also noticed that the build system ignores CXX and C(XX)FLAGS, which also is not a regression, but should be fixed anyway.
Thanks for pointing out the quirks in comment #9 and #11. I will have a look at it in next revision.
Currently, there is not clean way to only install bat and client fd. If one wants to install bat (qt4), database must be selected.
(In reply to comment #13) > Currently, there is not clean way to only install bat and client fd. If one > wants to install bat (qt4), database must be selected. > Yes. See comment #3 of bug #322181
stable x86, thanks Thomas
sparc stable
Stable for HPPA.
PPC please don't waste your time on this one and stable the actual 5.0.3-r1 instead (bug #341471).
As ppc (as last arch in question) stabled the newer bacula-5.0.3-r1 in meantime (thanks jer) we can finally close these bug.
