On Fri, Jun 28, 2019, at 1:38 PM, Martin Simmons wrote:
> > On Fri, 28 Jun 2019 09:38:02 -0400, Dan Langille said:
> >
> > > On Jan 24, 2019, at 10:16 AM, Martin Simmons wrote:
> > >
> > >> On Wed, 23 Jan 2019 16:33:14 -0500, Dan Langille said:
> > >>
> > >> But there is one error:
> >
> On Fri, 28 Jun 2019 09:38:02 -0400, Dan Langille said:
>
> > On Jan 24, 2019, at 10:16 AM, Martin Simmons wrote:
> >
> >> On Wed, 23 Jan 2019 16:33:14 -0500, Dan Langille said:
> >>
> >> But there is one error:
> >>
> >> ==>Entering directory /usr/home/dan/src/bacula/regress/build/sr
> On Jan 24, 2019, at 10:16 AM, Martin Simmons wrote:
>
>> On Wed, 23 Jan 2019 16:33:14 -0500, Dan Langille said:
>>
>> But there is one error:
>>
>> ==>Entering directory /usr/home/dan/src/bacula/regress/build/src/tools
>> cats_test.c:533:75: error: too many arguments provided to function-
Oh, nice. Thanks for the feedback.
On 1/29/19 1:39 PM, Martin Simmons wrote:
Thanks, all of those warnings are gone from the latest git build.
__Martin
On Fri, 25 Jan 2019 16:20:37 +0100, Kern Sibbald said:
Hello,
I am *finally* back from a month on the west coast of the US, followed
by 4
Thanks, all of those warnings are gone from the latest git build.
__Martin
> On Fri, 25 Jan 2019 16:20:37 +0100, Kern Sibbald said:
>
> Hello,
>
> I am *finally* back from a month on the west coast of the US, followed
> by 4 days at the Bacula Systems bi-annual meeting and am working on
Hello,
I am *finally* back from a month on the west coast of the US, followed
by 4 days at the Bacula Systems bi-annual meeting and am working on
these problems. It is strange that I don't find them here, but as
always, I *much* appreciate Martin's patches.
I have also updated regress.bacul
> On Thu, 24 Jan 2019 10:54:06 -0500, Dan Langille said:
>
> > On Jan 24, 2019, at 10:39 AM, Martin Simmons wrote:
> >
> >> On Wed, 23 Jan 2019 18:04:30 -0500, Dan Langille said:
> >>
> >> The full test run is at
> >> https://gist.github.com/dlangille/f9b32caf723ce96576cb74ac038f64a2
>
> On Jan 24, 2019, at 10:39 AM, Martin Simmons wrote:
>
>> On Wed, 23 Jan 2019 18:04:30 -0500, Dan Langille said:
>>
>> The full test run is at
>> https://gist.github.com/dlangille/f9b32caf723ce96576cb74ac038f64a2
>
> You need to find the logs of the failing tests (possibly in a file calle
> On Wed, 23 Jan 2019 18:04:30 -0500, Dan Langille said:
>
> The full test run is at
> https://gist.github.com/dlangille/f9b32caf723ce96576cb74ac038f64a2
You need to find the logs of the failing tests (possibly in a file called
test.out).
__Martin
_
> On Wed, 23 Jan 2019 16:33:14 -0500, Dan Langille said:
>
> But there is one error:
>
> ==>Entering directory /usr/home/dan/src/bacula/regress/build/src/tools
> cats_test.c:533:75: error: too many arguments provided to function-like macro
> invocation
>ok(db_get_file_list(jcr, jcr->db_b
> On Jan 23, 2019, at 4:33 PM, Dan Langille wrote:
>
> Signed PGP part
>> On Jan 15, 2019, at 1:17 PM, Martin Simmons wrote:
>>
>>> On Tue, 15 Jan 2019 11:11:21 -0500, Dan Langille said:
>>>
On Jan 15, 2019, at 10:58 AM, Martin Simmons wrote:
> On Mon, 14 Jan 2019 22:46
> On Jan 15, 2019, at 1:17 PM, Martin Simmons wrote:
>
>> On Tue, 15 Jan 2019 11:11:21 -0500, Dan Langille said:
>>
>>> On Jan 15, 2019, at 10:58 AM, Martin Simmons wrote:
>>>
On Mon, 14 Jan 2019 22:46:57 -0500, Dan Langille said:
> On Dec 17, 2018, at 11:08 AM, Martin S
> On Tue, 15 Jan 2019 11:11:21 -0500, Dan Langille said:
>
> > On Jan 15, 2019, at 10:58 AM, Martin Simmons wrote:
> >
> >> On Mon, 14 Jan 2019 22:46:57 -0500, Dan Langille said:
> >>
> >>> On Dec 17, 2018, at 11:08 AM, Martin Simmons wrote:
> >>>
> >>> Thanks, that's a long list of c
> On Jan 15, 2019, at 10:58 AM, Martin Simmons wrote:
>
>> On Mon, 14 Jan 2019 22:46:57 -0500, Dan Langille said:
>>
>>> On Dec 17, 2018, at 11:08 AM, Martin Simmons wrote:
>>>
>>> Thanks, that's a long list of changes.
>>>
>>> Compiling it on FreeBSD 11.2 gives a few warnings for files i
> On Mon, 14 Jan 2019 22:46:57 -0500, Dan Langille said:
>
> > On Dec 17, 2018, at 11:08 AM, Martin Simmons wrote:
> >
> > Thanks, that's a long list of changes.
> >
> > Compiling it on FreeBSD 11.2 gives a few warnings for files in
> > bacula/src/lib
> > though:
> >
>
> Did everything g
> On Dec 17, 2018, at 11:08 AM, Martin Simmons wrote:
>
> Thanks, that's a long list of changes.
>
> Compiling it on FreeBSD 11.2 gives a few warnings for files in bacula/src/lib
> though:
>
Did everything get sorted out here?
Coincidentally, I just found that my regression testing jails are
Hello Sven,
After Christmas I will take a look at your patches. Your way of doing
it sounds
more correct to me than what the Bacula guys did -- for me fixing warnings
is better than masking them.
Best regards,
Kern
On 12/20/18 5:18 PM, Sven Hartge wrote:
On 20.12.18 17:07, Kern Sibbald wrot
On 20.12.18 17:07, Kern Sibbald wrote:
> Many thanks for the heads up ...
In fact, the main difference is this here:
--- libs3-2.0+20161214git06a4683/GNUmakefile2016-12-14
19:13:34.0 +0100
+++ libs3-20181010/GNUmakefile 2018-10-11 09:29:33.0 +0200
@@ -136,7 +136,7 @@
end
Many thanks for the heads up ...
Kern
On 12/20/18 4:00 PM, Sven Hartge wrote:
On 20.12.18 15:56, Sven Hartge wrote:
You better throw away my version of the change and directly base your
changes on upstream commit 4f2db1eb.
Scratch that comment from me, I should have looked at the version you
On 20.12.18 15:56, Sven Hartge wrote:
> You better throw away my version of the change and directly base your
> changes on upstream commit 4f2db1eb.
Scratch that comment from me, I should have looked at the version you
uploaded before.
The date in the filename says 2018-10-10, but inside it is t
On 20.12.18 15:41, Kern Sibbald wrote:
> I have also put the latest version of the Bacula libs3 source code into
>
> https://blog.bacula.org/downloads/libs3-20181010.tar.gz
>
> This source does not contain the latest patches that you mention below
> to make it work with a newer libcurl and gcc.
Hello Sven,
As you previously pointed out, I forgot to integrate the support_s3=yes
in configure.in. I have now added
that line recompiled configure.in and pushed the updated code into the
Bacula git repository.
I have also put the latest version of the Bacula libs3 source code into
https:/
On 20.12.18 12:47, Kern Sibbald wrote:
> I will download the very latest version they are using (probably
> patched), and post it on bacula.org. The version I have no longer
> even compiles :-(
I guess you need both patches from here
https://salsa.debian.org/hartge-guest/libs3/tree/master/debia
Hello Sven,
Thanks for the information. Yes, I agree this is a mess. We really
need a good libs3. In addition,
libs3 does not work for Oracle S3 nor does it work for Google S3 which
are both supposed
to work the same as Amazon S3.
It is lunch time now here (not for me), but as soon as I ca
On 20.12.18 12:08, Kern Sibbald wrote:
> I wrote this code about 2 years ago, so I think I had forgotten a
> few things that are starting to come back. I do remember having to
> patch libs3 to bring it more up to date, but what I did not remember
> was that apparently I installed it in /usr/local.
Sven,
I wrote this code about 2 years ago, so I think I had forgotten a few
things that are starting to come back.
I do remember having to patch libs3 to bring it more up to date, but
what I did not remember was that
apparently I installed it in /usr/local.
It appears that I downloaded libs3-
On 20.12.18 11:35, Kern Sibbald wrote:
> Sven,
>
> Hmm. Maybe I forgot to include some code in configure.in that detects
> libs3,
> since HAVE_LIBS3 seems to be undefined here too.
>
> Sorry for the inconvenience. I will have to look into why the libs3
> detection is not working.
>
> I just ma
Sven,
Hmm. Maybe I forgot to include some code in configure.in that detects
libs3,
since HAVE_LIBS3 seems to be undefined here too.
Sorry for the inconvenience. I will have to look into why the libs3
detection is not working.
I just manually added
#define HAVE_LIBS3 1
to my config.h fil
On 20.12.18 10:07, Kern Sibbald wrote:
> Hello Sven,
>
> Sorry you had problems.
>
> On my system, once libs3 is installed on the system, building Bacula
> automatically picks it up.
Does it? Looking really really hard at the shell code in configure tells
me: It doesn't.
This line
https://bacul
Hello Sven,
Sorry you had problems.
On my system, once libs3 is installed on the system, building Bacula
automatically picks it up.
Yes the original libs3 package is a bit old as the author stopped
updating it.
I am reasonably sure I am buildin
On 19.12.18 22:56, Sven Hartge wrote:
> On 19.12.18 22:05, Sven Hartge wrote:
>> On 19.12.18 21:55, Sven Hartge wrote:
>>
>>> Is libs3 in Debian too old or the wrong libs3 to begin with?
>>
>> To answer my own question: Yes, libs3 in Debian is too old.
>
> Using the current libs3-HEAD from https:/
On 19.12.18 22:05, Sven Hartge wrote:
> On 19.12.18 21:55, Sven Hartge wrote:
>
>> Is libs3 in Debian too old or the wrong libs3 to begin with?
>
> To answer my own question: Yes, libs3 in Debian is too old.
Using the current libs3-HEAD from https://github.com/bji/libs3 results
in different erro
On 16.12.18 19:06, Kern Sibbald wrote:
> The main new feature is the addition support for using Amazon S3 (and
> other *identical* S3 providers). Note: Azur, Oracle S3,and Goggle S3
> are not compatible with Amazon S3.
I've been trying to get the cloud-driver with S3 enabled for Debian, but
I hi
On 19.12.18 21:55, Sven Hartge wrote:
> Is libs3 in Debian too old or the wrong libs3 to begin with?
To answer my own question: Yes, libs3 in Debian is too old.
Grüße,
Sven
signature.asc
Description: OpenPGP digital signature
___
Bacula-devel mailin
On 12/17/18 9:11 PM, Phil Stracchino wrote:
> On 12/17/18 8:23 PM, Kern Sibbald wrote:
>> Hello Phil,
>>
>> Thanks for the Solaris update.
>>
>> Could you send me a list of all the warnings, or better yet, add them to
>> bug #2443 that Martin created?
>>
>> Best regards,
>> Kern
>
> I will attach
On 12/17/18 8:23 PM, Kern Sibbald wrote:
> Hello Phil,
>
> Thanks for the Solaris update.
>
> Could you send me a list of all the warnings, or better yet, add them to
> bug #2443 that Martin created?
>
> Best regards,
> Kern
I will attach a complete build log to that ticket. That's the most
p
Thanks.
Yes, I think the recv(int) is used in the new statistics code in the
Enterprise version. Hmm. I thought I removed all
references to it. I think I missed getting some of the patches from
9.2.2 into 9.4.0 :-(
Best regards,
Kern
On 12/17/18 8:45 PM, Martin Simmons wrote:
Hi Kern,
Th
Hello Phil,
Thanks for the Solaris update.
Could you send me a list of all the warnings, or better yet, add them to
bug #2443 that Martin created?
Best regards,
Kern
On 12/17/18 7:59 PM, Phil Stracchino wrote:
Bacula 9.4.0 using Sun CC (Solaris Studio) on Solaris 11.3: Many
anachronism w
Sorry, I meant to say the change reason was "Remove unused prototype
recv(len)" after a change with reason "Fix complier warning due to unused
subroutine variable".
__Martin
> On Mon, 17 Dec 2018 19:45:43 GMT, Martin Simmons said:
>
> Hi Kern,
>
> The change reason for dd0cd2b1016f86c34d79
Hi Kern,
The change reason for dd0cd2b1016f86c34d790d2f819af5ea245ab4e3 was "Fix
complier warning due to unused subroutine variable" so maybe the fix in
607303c975cc361802bb93db8317d8c32c8701a5 was causing other warnings about
BSOCK? Ironically, it seems that BSOCKCORE::recv(int) is never actuall
Bacula 9.4.0 using Sun CC (Solaris Studio) on Solaris 11.3: Many
anachronism warnings and 'hides' warnings, no errors, all modules built
successfully.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998
Hello Martin,
Thanks for the report.
That is strange. I thought the BSOCK stuff had been corrected in
9.2.2. Maybe some patches got lost as you note. I will check this. I
was 99% sure I started from the latest 9.2.2, but maybe not ...
The problems from the cloud driver don't surprise me m
Thanks, that's a long list of changes.
Compiling it on FreeBSD 11.2 gives a few warnings for files in bacula/src/lib
though:
1. Many of these:
Compiling attr.c
In file included from attr.c:27:
In file included from ../bacula.h:169:
In file included from ../lib/lib.h:51:
./bsock.h:73:12: warning:
Hello,
We are pleased to announce the release of Bacula version 9.4.0.
This is a major release (currently a Beta release) comprised of more
than 13,000 lines of differences since version 9.2.2. It has updates to
Baculum and small number of bug fixes and back ports from Bacula Systems
Enterpri
44 matches
Mail list logo
