They didn't change the name, it's a fork.
On Mon, Aug 29, 2022 at 8:16 AM Elias Pereira wrote:
> Hello Marcin,
>
> Sorry for the question, but why did you change the name from "baculum" to
> "bacularis"? :D
>
> On Fri, Aug 26, 2022 at 6:14 PM Marcin Haba wrote:
>
>> Hello Everybody,
>>
>> We
Hello Marcin,
Sorry for the question, but why did you change the name from "baculum" to
"bacularis"? :D
On Fri, Aug 26, 2022 at 6:14 PM Marcin Haba wrote:
> Hello Everybody,
>
> We are pleased to let you know that a new version of Bacularis has been
> released.
>
> This is a new feature and
Hi Uwe,
You might want to try just dumping the data as full inserts and then
import it with pgsql. IE:
mysqldump -nc bacula |grep INSERT >output.sql
psql bacula
\. output.sql
Another option wqould be to use the --default-character-set option to
mysqldump to switch the output to just
Hello Eric,
thanks much for your reply.
On Thu, Aug 25, 2022 at 03:36:09PM +0200, Eric Bollengier via Bacula-users
wrote:
>
> Bacula might have to store characters coming from the different clients
> (filename and
>
> path mostly), and we have no guarantee that they will be in valid UTF8.
>
On Thu, Aug 25, 2022 at 06:57:46PM +0100, Martin Simmons wrote:
> Do you have non-ASCII characters in your volume, job or client names? If not,
> then I don't see why the warning would cause them to look quite funny
> (whatever that means).
>
> __Martin
Hi folks,
thanks for your answers. No, I
