> This warnings are normal?
>
> ua_run.c: In function ‘bool display_job_parameters(UAContext*, JCR*, JOB*,
> const char*, char*, const char*, char*)’:
> ua_run.c:1656:22: warning: deprecated conversion from string constant to
> ‘char*’ [-Wwrite-strings]
> prt_type = _("Run Copy job\n")
Hi,
I wanted to check the trust path to the new signing key, but I can't
find the key 0x72CC03058633ACFA that has signed it. Where can I find it?
- Carsten
--
Check out the vibrant tech community on one of the world's m
Davide Franco writes:
> On Tue, Aug 15, 2017 at 9:14 PM, Carsten Leonhardt wrote:
>> I wanted to check the trust path to the new signing key, but I can't
>> find the key 0x72CC03058633ACFA that has signed it. Where can I find it?
> You will find old and new gpg public k
Hi,
am I missing something, or is the new tray-monitor not built
automatically? There doesn't seem to be a configure option for it
either.
- Carsten
--
Check out the vibrant tech community on one of the world's most
eng
Hi,
QT4 is out of support since December 2015[1]. The QT maintainers in Debian
plan to not ship it in the next Debian release[2] (which will probably be
in 2019). It has to be assumed that other distributions will take the
same step in the near future.
Are there plans to update bat to use QT5? A
Hi Kern,
would you consider the following patch that replaces the SHA1 function
with another one by Steve Reid that's undoubtedly free?
(c.f. http://bugs.bacula.org/view.php?id=1869)
The proposed replacement is used in many open source projects, as can be
verified at https://codesearch.debian.net
Hi Simone,
> On Sat, Sep 16, 2017 at 5:32 PM, Carsten Leonhardt wrote:
>> would you consider the following patch that replaces the SHA1 function
>> with another one by Steve Reid that's undoubtedly free?
>> (c.f. http://bugs.bacula.org/view.php?id=1869)
>
>
Hi,
there are differences in the data type for used for CacheRetention, in
some cases it's "BIGINT" and sometimes "BIGINT UNSIGNED". Is that ok?
Quick check:
$ cd src/cats; grep -i CacheRetention *_tables.in
$ grep -i CacheRetention *_tables.in
make_mysql_tables.in: CacheRetention BIGINT UNSIG
Hi,
Sebastian Andrzej Siewior, one of the OpenSSL maintainers of Debian,
kindly submitted patches to support building with OpenSSL 1.1.
They are only compile-tested until now, but I thougt it might already be
interesting. They can be found here for now:
https://bugs.debian.org/cgi-bin/bugreport.
Hi,
as I wrote earlier, Sebastian Andrzej Siewior, one of the OpenSSL
maintainers of Debian, kindly submitted patches to support building with
OpenSSL 1.1.
I have now tested them in an installation with about 50 clients using
transport encryption without apparent problems.
The debian packages in
Hi Kern,
> Yes there are plans to update to Qt 5, but sometimes with such nice
> web interfaces (BWeb, Baculum, ...) I wonder whether it is really
> worth the effort.
I noticed the commits concerning Qt 5 support in git and gave them a
try. It seems that autoconfigure still needs some glue:
[...
Hi Wanderlei,
> How to apply the pacthes?
if you're asking how to technically apply them to the source, then use
"patch < patchfile". See also "man patch".
Regards,
Carsten
--
Check out the vibrant tech community on on
Hi Kern,
> I am looking at the request you made (see below). First: yes, I will be
> happy to consider your request, but have several questions:
>
> 1. What is wrong with the current SHA1 code/license? For me the license is
> very much like a BSD license and I don't see a problem with it on the
>
Hi Kern,
> I do not see a problem taking the newer RFC 6234 code. However here
> are a few points:
>
> 1. Is the source code available in files (a .h and a .c)? That would
> simplify getting the new source.
>
> 2. As I mentioned previously, the SHA1 code has been in Bacula for a
> long time (appa
Hi Kern,
> Could you try this again with the current Bacula that is in the repo
> (9.0.6 20Nov17). I am hoping it was a bug in pkg-config -- I
> simplified its use. The ./configure script relies on pkg-config to
> find your Qt installation.
>
> If it still fails could you send me the output of
>
Hi Kern,
there's a typo affecting the client-only build in autoconf/configure.in,
patch attached.
Regards,
Carsten
diff --git a/bacula/autoconf/configure.in b/bacula/autoconf/configure.in
index 764e6dcb61..7ed1e96020 100644
--- a/bacula/autoconf/configure.in
+++ b/bacula/autoconf/configure.in
@
Hi Kern,
is there a reason that CPPFLAGS aren't used when compiling gigaslam?
If not I'd propose the attached patch.
Regards,
Carsten
diff --git a/src/tools/Makefile.in b/src/tools/Makefile.in
index f9f6eb9..abd6619 100644
--- a/src/tools/Makefile.in
+++ b/src/tools/Makefile.in
@@ -130,7 +130,
Hi,
I made a patch that fixes some problems with building the tray-monitor.
Before I submit it, I'd like to know which of the config files is
supposed to be the correct one:
bacula-tray-console.conf (cf. src/qt-console/tray-monitor/install_conf_file)
or
tray-console.conf (cf. scripts/bacula-tra
Hi Kern,
the version of the manual published at
https://www.bacula.org/9.2.x-manuals/en/main/Installing_Configuring_Post.html
has changes that are neither in the git repository nor in the tarball
(in relation to bug 2430).
Could you please push the changes to the public git repository?
Also, the
Hi Kern,
Kern Sibbald writes:
> Between Bacula releases, I do make changes to the manual, then
> immediately publish the .pdfs and html on the web site in the
> Documentation section. However, I do not generally make an official
> source code release until the next Bacula release.
>
> I do not
Hi,
I already asked about which config file is the correct one for the
tray-monitor (probably bacula-tray-console.conf, but there is also
tray-console.conf).
Now another question is about the icon to be used: the file
scripts/bacula-tray-monitor.desktop.in contains
Icon=/usr/share/pixmaps/bacula
Hi Kern,
thanks for the new release!
While looking through the changes since v9.4 I noticed a few issues:
These files say they have non-free licenses:
bacula/src/plugins/fd/docker/baculatar/Dockerfile
regress/scripts/regress-utils.sh
These files have "Copyright (C) (...) Bacula Systems SA" an
Hi Wanderlei,
> Have you take a look in the wrong documentation encoding?
do you still see wrong encodings in the documentation in v9.6.3?
Regards,
Carsten
___
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.ne
Hi Wanderlei,
> I've took a quick look in the documentation and still have some wrong
> encodings
Thanks for the examples, I'll have a go at fixing the rest. The problem
is a mixup between ISO-8859-1 and UTF-8 encodings.
Regards,
Carsten
___
Bacula-
Hi Wanderlei,
> I want to see the commits. Is anybody seeing to fix?
until the website gets fixed, you can clone the repository and examine
it locally:
git clone https://git.bacula.org/bacula.git
Regards,
Carsten
___
Bacula-devel mailing list
Bacul
Hi Kern,
the git repository for the docs at http://git.bacula.org/docs.git seems
non-functional. A version that is in working state is at
http://git.bacula.org/xdocs.git but that isn't up to date.
Could you have a look?
Thanks,
Carsten
___
Bacula-de
Hi
Sven Hartge writes:
> I have both the source and the docs GIT cloned to my workstation and the
> docs remoted stopped working some time ago:
I can confirm that the docs repository worked, my clone's last commit is
2020-06-09 17:15 +0200 Kern Sibbald o [Branch-9.6]
{origin/Branch-
Hi Eric,
Hi Kern,
firstly, thanks for your past and future work and good luck with your new
positions :-)
This release is signed with a new PGP key which doesn't seem to be at
https://www.bacula.org/bacula-distribution-verification-public-keys/
yet:
RSA 0x16FCF91DCBDA197436ACA721CAA7F07F2911863C
Hi Eric,
I see that latex2html v2016 has been embedded into the source of
bacula-docs. Is that a modified version? Current upstream is v2020.2,
newer versions than v2016 are available in both Debian and Ubuntu. Do
you plan to keep it in the source tree?
Regards,
Carsten
___
Hi Eric,
you've fixed some bugs after releasing 11.0.0, may I ask that you push
the changes to the public git repository?
Debian is going into pre-release freeze soon and I'd like to be able to
use some of the bugfixes.
Thanks
Carsten
___
Bacula-dev
Hi Eric,
I wanted to update the documentation package for Debian, but I noticed
that the file LICENSE (which said the documentation is licensed under
CC-BY-SA) went missing beginning with the 11.0.0 release of bacula-doc.
Right now the only file about licensing in the docs is in
latex/license.tex
Hi Arno,
Arno Lehmann via Bacula-devel
writes:
> Hi Carsten, all
>
> Am 20.11.2024 um 14:21 schrieb Carsten Leonhardt:
> ... (snip description of the challenges with a really convoluted build
> process)
>> It seems to boil down to:
>> /usr/bin/pdflatex -halt-on-error
Hi,
I can't seem to be able to build the docs from the git source. To be
able to even start, I had to remove the stuff about version.h and
version.tex from the Makefile and placed a dummy file with "echo 15.0.2 >
latex/version.tex". The build fails to produce the main.pdf. After
haggling with the
Hi Eric,
I've attached two patches for the docs:
1) In one place **StartTLS** was changed to \texttt{StartTLS} in commit
71e9f56f8add21709bfd0491c3f4c592101eaf90 - the patch changes it in the
other two places with the same wording for consistency
2) Some change in newer LaTex versions causes the
Hi,
here with the actual patches...
Regards
Carsten
>From 0b956e2e22388d368452ede5e630205a3d326b57 Mon Sep 17 00:00:00 2001
From: Carsten Leonhardt
Date: Sat, 30 Nov 2024 12:19:38 +0100
Subject: [PATCH 1/2] Change **StartTLS** to \texttt{StartTLS}
For consistency with com
Hi Eric,
please consider the attached patch. Setting BUILD_VERBOSE to 1 in the
environment makes the build to be verbose with output to the console.
Regards
Carsten
>From a63bb05c614e49947ba0734000dbd8df8c2bb40c Mon Sep 17 00:00:00 2001
From: Carsten Leonhardt
Date: Sat, 30 Nov 2024 13:01
Hi Eric,
Eric Bollengier via Bacula-devel
writes:
> Hello,
>
> The pdfs are on the website in the documentation directory
> and the typo was fixed after the release process.
>
> The git repository is correct, you can either take the
> pdf from the website (15.0.x-manuals/en/main/main.pdf),
> use
37 matches
Mail list logo
