Description of problem: Two tray monitor configuration files are provided with different contents! Only one configuration file is needed. Ususaly it is bacula-tray-monitor.conf. tray-monitor.conf is unuseful but his content is more appropriate than the other one. Clean-up is expected.
Clean-up is the following : diff bacula.spec bacula.spec.org 357c358 < %{__install} -p -m 644 -D src/qt-console/tray-monitor/tray-monitor.conf %{buildroot}%{_sysconfdir}/bacula/bacula-tray-monitor.conf --- > %{__install} -p -m 644 -D src/qt-console/tray-monitor/tray-monitor.conf %{buildroot}%{_sysconfdir}/bacula/tray-monitor.conf 624d623 > %attr(640,root,root)%config(noreplace) %{sysconf_dir}/tray-monitor.conf 627d628 > %{_sbindir}/.libs/bacula-tray-monitor
Thank you for the report of the problem, and your research into it. Indeed, the pkg bacula-tray-monitor does provide these two files: /etc/bacula/bacula-tray-monitor.conf /etc/bacula/tray-monitor.conf Bacula has various maintainers, so assigning this bug globally.
Assignee: bugsquad => pkg-bugsSource RPM: bacula-tray-monitor-9.6.7-1.mga8.x86_64 => bacula-9.6.7-1.mga8.src.rpm
Raising the priority because this is 1/3 bacula bugs. See also: Bug 28630, Bug 28618.
Priority: Normal => High
Actually there was and still are are four open stalled bugs on Bacula: § This one § Bug 24096 - bacula's bat doesn't lauch (missing /usr/sbin/.libs/bat binary) § Bug 28618 - bat (Bacula Administration Tool) fails at start § Bug 28630 - The group "root" of files bat.conf, bconsole.conf and bacula-tray-monitor.conf located in /etc/bacula is wrong And on top of that I have suggested to move to a fully open source fork Bug 25553 - bareos backup solution, a 100% open source fork of bacula.org.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=24096, https://bugs.mageia.org/show_bug.cgi?id=28618, https://bugs.mageia.org/show_bug.cgi?id=28630, https://bugs.mageia.org/show_bug.cgi?id=25553CC: (none) => fri
What means "on top of that I have suggested to move to a fully open source fork" Does it means these bugs won't be fixed (in mga8 or mga9)? Should we understand that bacula will be given up and replaced by bareos? If that's the plan, when will it be implemented. Please confirm bacula is still part of Mageia 9? AFAIK, and based on the feedback I had on my bugs reports, it seems there are only few bacula users on Mageia (or should I say there is only one "me"!). Please react if I'm wrong. By the way, I don't understand why you consider implicitly bacula as not completely open source : - Bacula is based on mariadb or PostgreSQL and both are open source! - Bacula and Bareos are supported by commercial companies. - For those users of bacula + mariadb, to switch to bareos + PostgreSQL would be a huge investment. So what are pros and cons? This comment applies also to Bugs 24096 - 28618 - 28630 - Bug 25553.
(In reply to pat dealt from comment #5) > What means "on top of that I have suggested to move to a fully open source > fork" > "bareos backup solution, a 100% open source fork of bacula.org" It was just a thought of Morgan's, a future possibility. But needing more justification: the 'open source' differences are unclear. Bacula's site says: "Open Source Bacula is a set of Open Source, computer programs that permit..." But the heading buttons are iffy: "Buy" & "Try Free". Bareos' site says: "Free Our backup solution is licensed under the AGPLv3. You’re free to use and modify Bareos as you see fit" > Please confirm bacula is still part of Mageia 9? bacula-13.0.1-1.mga9.src.rpm bacula-backup-mysql-0.8-4.mga9.src.rpm And under Cauldron: $ urpmq -y bacula bacula-backup-mysql bacula-bat bacula-common bacula-console bacula-dir bacula-fd bacula-sd bacula-tray-monitor lib64bacula-devel lib64bacula-sql7 lib64bacula7 nagios-plugins-bacula > Should we understand that bacula will be given up and replaced by bareos? Certainly not for Mageia 9, if ever. > Does it means these bugs won't be fixed (in mga8 or mga9)? These bugs ought to be fixed. Raising the importance again.
Severity: normal => majorCC: (none) => lewyssmith