bacula versions
Elan Ruusamäe
glen at pld-linux.org
Wed Apr 20 12:19:18 CEST 2016
so, we have 5.2.13 -> 7.0.5 upgrade in th
https://github.com/pld-linux/bacula/blob/auto/th/bacula-7.0.5-1/bacula.spec#L494-L499
# install the updatedb scripts for older versions that last full release
# 2.0 -> 3.0 : 10_to_11
# 5.0 -> 5.2 : 12_to_14
install -p updatedb/update_*_tables_10_to_11
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
install -p updatedb/update_*_tables_11_to_12
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
install -p updatedb/update_*_tables_12_to_14
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
i looked bacula website and found 7.2.0 and 7.4.0 there
so i tried to build 7.2.0 and it would have such files (12->13->14, not
12-14)
install -p updatedb/update_*_tables_10_to_11
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
install -p updatedb/update_*_tables_11_to_12
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
install -p updatedb/update_*_tables_12_to_13
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
install -p updatedb/update_*_tables_13_to_14
$RPM_BUILD_ROOT%{_libexecdir}/%{name}
looks like 7.2.0 is older than 7.0.5? like 7.2 is development branch for
7.0? huh? and they both result v14 database?
so i'm a bit confused of their releases, and what version series we
should stick in pld?
the problem i have is that i have bacula5 director, and having upraded
clients to bacula7 results authentication failures
yet if i read 7.4.0 release notes http://blog.bacula.org/release-7-4-0/
it claims: " Upgrading should be easy since there is no database change
and all older File Daemons should remain compatible with Bacula 7.4.0."
of course i don't know do they claim if 5.2 clients can connect there or not
--
glen
More information about the pld-devel-en
mailing list