On Wednesday 08 August 2007 15:48, Dan Langille wrote:
> With the upcoming release of 2.2.0, we should publicize Bat as much
> as possible. I'll write something up in advance. It will be
> similar to the previous press release:
>
> http://www.bacula.org/about/press/presskit200.html.en
>
> Then
On Wednesday 08 August 2007 18:49, Martin Simmons wrote:
> > On Wed, 8 Aug 2007 16:13:45 +0200, Kern Sibbald said:
> >
> > On Wednesday 08 August 2007 15:52, Martin Simmons wrote:
> > > > On Wed, 8 Aug 2007 13:42:03 +0200, Kern Sibbald said:
> > > >
> > > > On Wednesday 08 August 2007 12:46
On Wednesday 08 August 2007 18:35, Berend Dekens wrote:
> Does the message that the director is busy when using bat have something
> to do with the fact that I ran it against a 2.0.3 director?
Bat will not run with any Director less than something like 2.1.18. It may
seem to run, but at some po
> On Wed, 8 Aug 2007 16:13:45 +0200, Kern Sibbald said:
>
> On Wednesday 08 August 2007 15:52, Martin Simmons wrote:
> > > On Wed, 8 Aug 2007 13:42:03 +0200, Kern Sibbald said:
> > >
> > > On Wednesday 08 August 2007 12:46, Martin Simmons wrote:
> > > > Unless I've missed it, it looks like
Does the message that the director is busy when using bat have something
to do with the fact that I ran it against a 2.0.3 director? Also, is
that 'alpha' warning gone now (it was there a while ago...).
Also, I can translate the announcement into Dutch if anybody wants me to ;-)
Regards,
Berend
Hello,
Unless something unexpected crops up, I am planning on releasing Bacula 2.2.0
this weekend. As a consequence, I would appreciate it if the beta testers
and regression testers could update to the latest SVN and do the maximum of
testing.
For developers, please keep your changes to a mi
Hi,
08.08.2007 15:48,, Dan Langille wrote::
> With the upcoming release of 2.2.0, we should publicize Bat as much
> as possible. I'll write something up in advance. It will be
> similar to the previous press release:
>
> http://www.bacula.org/about/press/presskit200.html.en
>
> Then I'll
On Wednesday 08 August 2007 15:48, Dan Langille wrote:
> With the upcoming release of 2.2.0, we should publicize Bat as much
> as possible. I'll write something up in advance. It will be
> similar to the previous press release:
>
> http://www.bacula.org/about/press/presskit200.html.en
>
> Then
After looking, I see you were referring to the src/qt-console README file
which was a bit out of date. I have now updated it.
Thanks for pointing this out.
Regards,
Kern
On Wednesday 08 August 2007 16:35, Dan Langille wrote:
> Either I need education or the README does. :)
>
> I'm trying to
On Wednesday 08 August 2007 16:11, John Drescher wrote:
> > I consider it stable, but given that it is a *very* large body of brand
> > new code, we can expect a number of bugs to crop up when it becomes
> > heavily used under varying conditions. I don't expect any of the bugs to
> > be a show sto
If you did the ./configure with --enable-bat, it should have created a
project file called bat.pro. This file is generated from make Makefiles
in the base bacula directory. It generates this using bat.pro.in.
Judging from qmake not recognizing what to do, I'd guess there is no
bat.pro in the qt-c
On Wednesday 08 August 2007 16:35, Dan Langille wrote:
> Either I need education or the README does. :)
It would help to be a bit more specific since there are a lot of README's.
If you are referring to the README in the src/qt-console directory, it could
be slightly out of date as it was targe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Langille wrote:
> With the upcoming release of 2.2.0, we should publicize Bat as much
> as possible. I'll write something up in advance. It will be
> similar to the previous press release:
>
> http://www.bacula.org/about/press/presskit200.h
Either I need education or the README does. :)
I'm trying to build Bat [on FreeBSD]. I have qwt 4.2.0 and qmake
1.0.7a installed.
README says to do this:
qmake
make
When I run qmake:
[EMAIL PROTECTED]:~/src/bacula-server-devel/work/bacula-2.1.28/src/qt-
console] $ qmake -v
Qmake version
On Wednesday 08 August 2007 15:55, Allan Black wrote:
> Kern Sibbald wrote:
> > On Wednesday 08 August 2007 15:09, Allan Black wrote:
> >> Found what I think is a (minor) bug in the find_next_volume code;
> >> patch attached.
> >
> > Could you resend your email with the diff in unified format (diff
On Wednesday 08 August 2007 15:52, Martin Simmons wrote:
> > On Wed, 8 Aug 2007 13:42:03 +0200, Kern Sibbald said:
> >
> > On Wednesday 08 August 2007 12:46, Martin Simmons wrote:
> > > Unless I've missed it, it looks like jcr->SDErrors is never set (in the
> > > Director). Bug? Similarly, it
> I consider it stable, but given that it is a *very* large body of brand new
> code, we can expect a number of bugs to crop up when it becomes heavily used
> under varying conditions. I don't expect any of the bugs to be a show
> stopper. I have used it exclusively for at least four months now.
On Wednesday 08 August 2007 15:36, John Drescher wrote:
> > During the process of getting it fully functional, I found the JobList
> > feature of bat particularly useful because it instantly showed me which
> > jobs failed, and by right clicking on them, I could even see the Job
> > Report with the
Kern Sibbald wrote:
On Wednesday 08 August 2007 15:09, Allan Black wrote:
Found what I think is a (minor) bug in the find_next_volume code;
patch attached.
Could you resend your email with the diff in unified format (diff -u). I
don't read the format you sent.
OK, here it is (and I'll bear t
> On Wed, 8 Aug 2007 13:42:03 +0200, Kern Sibbald said:
>
> On Wednesday 08 August 2007 12:46, Martin Simmons wrote:
> > Unless I've missed it, it looks like jcr->SDErrors is never set (in the
> > Director). Bug? Similarly, it looks like the value of jcr->Errors in the
> > SD is never passed
With the upcoming release of 2.2.0, we should publicize Bat as much
as possible. I'll write something up in advance. It will be
similar to the previous press release:
http://www.bacula.org/about/press/presskit200.html.en
Then I'll be looking for help with two things:
- translation - int
> During the process of getting it fully functional, I found the JobList feature
> of bat particularly useful because it instantly showed me which jobs failed,
> and by right clicking on them, I could even see the Job Report with the
> details of the errors. Pretty cool. Though bat was initially
On Wednesday 08 August 2007 15:09, Allan Black wrote:
> Found what I think is a (minor) bug in the find_next_volume code;
> patch attached.
>
> I had been wondering why tapes with 'Recycle' status seemed to be
> used in reverse order to what I expected
>
> Allan
Could you resend your email wi
Found what I think is a (minor) bug in the find_next_volume code;
patch attached.
I had been wondering why tapes with 'Recycle' status seemed to be
used in reverse order to what I expected
Allan
*** sql_find.c.orig Mon Nov 27 10:03:06 2006
--- sql_find.c Wed Aug 8 13:29:11 2007
***
On Wednesday 08 August 2007 12:46, Martin Simmons wrote:
> Unless I've missed it, it looks like jcr->SDErrors is never set (in the
> Director). Bug? Similarly, it looks like the value of jcr->Errors in the
> SD is never passed back to the Director.
SDErrors are non-fatal errors, and it is likely
Unless I've missed it, it looks like jcr->SDErrors is never set (in the
Director). Bug? Similarly, it looks like the value of jcr->Errors in the SD
is never passed back to the Director.
See http://article.gmane.org/gmane.comp.bacula.user/37143
__Martin
-
On Friday 03 August 2007 02:57, James Harper wrote:
> I was just trying to restore a file (eg restore, option 7) and went to
> paste in the filename from the clipboard but I was also in the middle of
> doing some unrelated SQL work and so pasted the following in by mistake:
>
> --UPDATE SO_LineDeta
On Wednesday 08 August 2007 05:47, John Drescher wrote:
> > That is a really interesting idea that I doubt that I would have thought
> > of, and I would have worried a lot about the GTK++ code. However, I
> > think you may be on to something really good here -- it is always good to
> > leverage th
28 matches
Mail list logo
