> On Fri, 04 Apr 2014 01:25:27 +0200, Kern Sibbald said:
>
> On 04/03/2014 10:32 PM, Dan Langille wrote:
> > On 2014-04-03 02:27 PM, Kern Sibbald wrote:
> >> Strange. I build FreeBSD binaries, and I never had to make *any*
> >> patches to Bacula to build an run it. I seem to be missing somethi
> On Thu, 03 Apr 2014 20:27:38 +0200, Kern Sibbald said:
>
> Strange. I build FreeBSD binaries, and I never had to make *any*
> patches to Bacula to build an run it. I seem to be missing
> something here. Please don't get me wrong, I am not complaining or
> anything like that, but I have a h
On 2014-04-03 09:51 AM, Martin Simmons wrote:
> This problem with ECHO affects the main bacula makefiles as well. The
> definition of ECHO comes from libtool.m4, but it will not work in
> makefiles
> because of the backslash.
libtool feeds that definition into configure? I ask with regards to m
On Apr 3, 2014, at 7:25 PM, Kern Sibbald wrote:
> On 04/03/2014 10:32 PM, Dan Langille wrote:
>> On 2014-04-03 02:27 PM, Kern Sibbald wrote:
>>> Strange. I build FreeBSD binaries, and I never had to make *any*
>>> patches to Bacula to build an run it. I seem to be missing something
>>> here. Ple
On 04/03/2014 10:32 PM, Dan Langille wrote:
> On 2014-04-03 02:27 PM, Kern Sibbald wrote:
>> Strange. I build FreeBSD binaries, and I never had to make *any*
>> patches to Bacula to build an run it. I seem to be missing something
>> here. Please don't get me wrong, I am not complaining or anything
On 2014-04-03 02:27 PM, Kern Sibbald wrote:
> Strange. I build FreeBSD binaries, and I never had to make *any*
> patches to Bacula to build an run it. I seem to be missing something
> here. Please don't get me wrong, I am not complaining or anything like
> that, but I have a hard time understanding
Strange. I build FreeBSD binaries, and I never had to make *any*
patches to Bacula to build an run it. I seem to be missing
something here. Please don't get me wrong, I am not complaining or
anything like that, but I have a hard time understanding what the
real problem
Hello Martin,
Are you saying that Bacula is wrong assuming that echo works like
defined in the Unix/Linux man pages?
If that is the case, what are you suggesting? To men MAKEFILEECHO
doesn't mean much.
Best regards,
Kern
On 04/03/2014 03:51 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dan,
Good news. Thanks.
Best regards,
Kern
On 04/03/2014 01:19 AM, Dan Langille wrote:
> I had local changes for this
echo problem. I just did a ?git stash? on my checkout so
On 2014-04-03 09:51 AM, Martin Simmons wrote:
> This problem with ECHO affects the main bacula makefiles as well. The
> definition of ECHO comes from libtool.m4, but it will not work in
> makefiles
> because of the backslash.
>
> I think the makefiles should stop using ECHO, or at least
> Make.
This problem with ECHO affects the main bacula makefiles as well. The
definition of ECHO comes from libtool.m4, but it will not work in makefiles
because of the backslash.
I think the makefiles should stop using ECHO, or at least Make.common.in
should do something like:
ECHO = @MAKEFILEECHO@
wh
I had local changes for this echo problem. I just did a ‘git stash’ on my
checkout so I could try 7.0.2
It fails.
I notice that the 5.x code using:
@$(ECHO) "# DO NOT DELETE: nice dependency list follows" >> Makefile
It works.
This makes me think: has configure changed?
So I went looking at
In addition to my previous post, this just in:
http://regress.bacula.org/viewTest.php?onlyfailed&buildid=24144
Only disk:tls-test failed this time.
On Mar 31, 2014, at 11:16 AM, Kern Sibbald wrote:
> Hello Dan,
>
> Can you try applying the attached patch to release 7.0.0 and see if it
> fixes
It seems to have switched the failure to another test:
http://regress.bacula.org/viewTest.php?onlyfailed&buildid=24125 2014-03-30
21:32:44
NameStatus TimeDetails Labels
disk:plugin-testFailed 1m 11s 100msCompleted (Failed)
disk:tls-test Failed 1m 41s 380msCompl
OK. The patch I just sent might help too ...
Best regards,
Kern
On 03/31/2014 05:16 PM, Dan Langille wrote:
> On 2014-03-31 10:41 AM, Kern Sibbald wrote:
>> Hello Dan,
>>
>> Sorry I didn't read to the bottom of your email. Well, then the problem
>> is very likely what you originally said -- a c
Hello Dan,
Can you try applying the attached patch to release 7.0.0 and see if it
fixes the problem with the tls-test? I am not 100% convinced that it
will, but at least the code is much tighter now and will not store any
address if it is not either IPv4 or IPv6 and if IPv6 is not configured
and
On 2014-03-31 10:41 AM, Kern Sibbald wrote:
> Hello Dan,
>
> Sorry I didn't read to the bottom of your email. Well, then the
> problem
> is very likely what you originally said -- a configuration error.
> Apparently, Bacula has detected that IPv6 is enabled, but it isn't
> really on your machine
Hello Dan,
Sorry I didn't read to the bottom of your email. Well, then the problem
is very likely what you originally said -- a configuration error.
Apparently, Bacula has detected that IPv6 is enabled, but it isn't
really on your machine.
Please look in /src/config.h after having done a ./confi
Hello Dan,
Hmmm. That is an interesting patch. I would do it a bit differently in
Bacula. I would just skip everything that is not IPv4 or IPv6. I
almost did that when I implemented the new code, but since I had never
seen any other types I decided not to do it.
I will look and see how hard th
Hello Dan,
Sorry, I was not very precise. It will be somewhere in /usr/include
probably in one of the network header files. On Linux the low level
definitions come from PF_INET and PF_INET6.
Best regards,
Kern
On 03/31/2014 03:01 PM, Dan Langille wrote:
> On 2014-03-31 07:36 AM, Kern Sibbald
On 2014-03-31 09:01 AM, Dan Langille wrote:
> On 2014-03-31 07:36 AM, Kern Sibbald wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello Dan,
>>
>> I have to admit that I haven't run a Dart test for a very long time.
>> The plugin-test should be removed from it, which I have d
On 2014-03-31 09:01 AM, Dan Langille wrote:
> On 2014-03-31 07:36 AM, Kern Sibbald wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello Dan,
>>
>> I have to admit that I haven't run a Dart test for a very long time.
>> The plugin-test should be removed from it, which I have d
On 2014-03-31 07:36 AM, Kern Sibbald wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello Dan,
>
> I have to admit that I haven't run a Dart test for a very long time.
> The plugin-test should be removed from it, which I have done. I've
> pushed the patch to the git repo.
>
> C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dan,
I have to admit that I haven't run a Dart test for a very long
time. The plugin-test should be removed from it, which I have
done. I've pushed the patch to the git repo.
Concerning the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/30/2014 11:32 PM, Dan Anguilla wrote:
>
> On Mar 30, 2014, at 4:44 PM, Dan Langille
wrote:
>
>> I tried some regression tests for Bacula 7 tonight. I
found what I think may be a conf
On Mar 30, 2014, at 4:44 PM, Dan Langille wrote:
> I tried some regression tests for Bacula 7 tonight. I found what I think may
> be a configure issue.
The test finished, two errors:
http://regress.bacula.org/buildSummary.php?buildid=24125
--
Dan Langille - http://langille.org
signature.
On Mar 30, 2014, at 4:44 PM, Dan Langille wrote:
> I tried some regression tests for Bacula 7 tonight. I found what I think may
> be a configure issue.
FYI, I think a step needs to be added to the regression testing:
git checkout -b Branch-7.0 origin/Branch-7.0
For whatever branch you wil
I tried some regression tests for Bacula 7 tonight. I found what I think may
be a configure issue.
It stops with:
Stop in /usr/home/dan/src/Bacula7RegressionTesting-TRUNK/regress/build.
==>Entering directory
/usr/home/dan/src/Bacula7RegressionTesting-TRUNK/regress/build/src
==>Entering directo
28 matches
Mail list logo
