(use custom build, older th-snapshot repos, etc)
This is distro wide support vs custom configs problem.
Sorry, but if distro does not ship mysqlhotcopy, then defaulting to it
will create non-functioning package.
Bacula just should require >= mysql version that provides mysqld
On 4/11/18 9:31 AM, Jan Rękorajski wrote:
On Tue, 10 Apr 2018, Elan Ruusamäe wrote:
um, this would break setups if they have not defined the default in
their config.
and you can still have mysqlhotcopy functional if you put mysql packages
to hold (use custom build, older th-snapshot repos,
>> to hold (use custom build, older th-snapshot repos, etc)
> This is distro wide support vs custom configs problem.
> Sorry, but if distro does not ship mysqlhotcopy, then defaulting to it
> will create non-functioning package.
>
Bacula just should require >= mysql version that pro
On Tue, 10 Apr 2018, Elan Ruusamäe wrote:
> um, this would break setups if they have not defined the default in
> their config.
>
> and you can still have mysqlhotcopy functional if you put mysql packages
> to hold (use custom build, older th-snapshot repos, etc)
This is distro wide support
abb107aa8ae91f4acd76dec00348614518133fa1
Author: Jan Rękorajski <bagg...@pld-linux.org>
Date: Sun Apr 8 08:27:47 2018 +0200
- change default to mysqldump, mysqlhotcopy no longer exists in mysql 5.7
- rel 2
bacula-backup-mysql.spec | 5 +++--
default-mysqldump.patch | 22 ++
2 files chang
Don't know, those files just aren't there anymore.
2017-01-31 13:40 GMT+01:00 Elan Ruusamäe <g...@pld-linux.org>:
> On 31.01.2017 11:41, mmazur wrote:
>>
>> Name: bacula
>> -Version: 7.0.5
>> -Release: 2
>> +Version: 7.4.4
>&
On 31.01.2017 11:41, mmazur wrote:
Name: bacula
-Version: 7.0.5
-Release: 2
+Version: 7.4.4
+Release: 1
License: AGPL v3
..
@@ -495,7 +495,6 @@ touch $RPM_BUILD_ROOT/var/log/bacula/log
# 5.0 -> 5.2 : 12_to_14
install -p updatedb/upda
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?
Its not older. Bacula isn't always providing all SQL migration paths and
scripts
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?
Its not older. Bacula isn't always providing all SQL migration paths and
scripts
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
On Fri, Jan 22, 2016 at 08:35:53PM +0100, Jakub Bogusz wrote:
> I propose renaming alsa's bat to alsa-bat.
That's what I did in ALT Linux either back then :)
> The others:
> Fedora uses alsa-utils-bat subpackage.
> Debian doesn't have ALSA 1.1.0 yet.
--
WBR, Michael Shigorin /
On 2016-01-22 17:59, Elan Ruusamäe wrote:
> file /usr/bin/bat from install of alsa-utils-1.1.0-1.x86_64
> conflicts with file from package bacula-console-qt-5.2.13-4.x86_64
> file /usr/share/man/man1/bat.1.gz from install of
> alsa-utils-1.1.0-1.x86_64 conflicts wi
On Fri, Jan 22, 2016 at 08:01:41PM +0100, Jacek Konieczny wrote:
> On 2016-01-22 17:59, Elan Ruusamäe wrote:
> > file /usr/bin/bat from install of alsa-utils-1.1.0-1.x86_64
> > conflicts with file from package bacula-console-qt-5.2.13-4.x86_64
> > file /usr/sh
On 04.04.2011 16:45, Jakub Bogusz wrote:
On Mon, Apr 04, 2011 at 12:11:39PM +0200, Adam Chabin wrote:
Cześć,
Mam problem z bacula. Po uruchomieniu joba pod sam jego koniec proces
bacula-dir umiera z takim komunikatem:
[bacula-dir dies with:]
ripley-dir: msgchan.c:362-1004 === End msg_thread
On Mon, Apr 04, 2011 at 12:11:39PM +0200, Adam Chabin wrote:
Cześć,
Mam problem z bacula. Po uruchomieniu joba pod sam jego koniec proces
bacula-dir umiera z takim komunikatem:
[bacula-dir dies with:]
ripley-dir: msgchan.c:362-1004 === End msg_thread. JobId=1004 usecnt=2
/usr/sbin/bacula
Hello,
In Th, we still have a very old Bacula version: 2.4.4. To make it worse,
that build supports MySQL database only.
There have been many updated made in the CVS repository to improve that:
spec file had been updated to newer Bacula versions, 'libdbi' backend
had been enabled by default
Bacula uses a database backend, but can be compiled only against one database
at a time. The default in pld was mysql.
Recently released Bacula 3.0 adds support for libdbi, which, in short, is a
database abstraction layer with runtime db plugins (called drivers), so
bacula compiled with libdbi
On Tue, Apr 21, 2009 at 12:19:30PM +0200, Mariusz Mazur wrote:
Bacula uses a database backend, but can be compiled only against one database
at a time. The default in pld was mysql.
Recently released Bacula 3.0 adds support for libdbi, which, in short, is a
database abstraction layer
On Tue, 21 Apr 2009, Mariusz Mazur wrote:
Bacula uses a database backend, but can be compiled only against one database
at a time. The default in pld was mysql.
[...]
So, anybody got any ideas how to handle this properly? Would a %banner be
enough stating that you need to a) add libdbi
On Tuesday 21 April 2009 13:19:30 Mariusz Mazur wrote:
So, anybody got any ideas how to handle this properly? Would a %banner be
enough stating that you need to a) add libdbi-drivers-mysql and b) alter
the config? Or maybe something else?
is the mysql database otherwise compatible?
to make it
20 matches
Mail list logo
