-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Langille wrote:
On 13 Feb 2006 at 13:10, Sebastian Stark wrote:
On 13.02.2006, at 12:24, Sebastian Stark wrote:
On 13.02.2006, at 11:56, Michel Meyers wrote:
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perf
On 13.02.2006, at 13:52, Dan Langille wrote:
On 13 Feb 2006 at 13:10, Sebastian Stark wrote:
On 13.02.2006, at 12:24, Sebastian Stark wrote:
On 13.02.2006, at 11:56, Michel Meyers wrote:
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perfect
but one
job
On 13 Feb 2006 at 13:10, Sebastian Stark wrote:
>
> On 13.02.2006, at 12:24, Sebastian Stark wrote:
> >
> > On 13.02.2006, at 11:56, Michel Meyers wrote:
> >>
> >> Sebastian Stark wrote:
> >>>
> >>> After upgrading from 1.36.2 to 1.38.3 everything worked perfect
> >>> but one
> >>> job refuses
On 13.02.2006, at 12:24, Sebastian Stark wrote:
On 13.02.2006, at 11:56, Michel Meyers wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perfect
but one
job refuses to backup anything. An upgrade to 1.38.5
On 13.02.2006, at 11:56, Michel Meyers wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perfect
but one
job refuses to backup anything. An upgrade to 1.38.5 did not fix
this.
The FileSet definition did n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perfect but one
job refuses to backup anything. An upgrade to 1.38.5 did not fix this.
The FileSet definition did not change and there are definitely files
that need to
After upgrading from 1.36.2 to 1.38.3 everything worked perfect but
one job refuses to backup anything. An upgrade to 1.38.5 did not fix
this.
The FileSet definition did not change and there are definitely files
that need to be backed up (new files, changed files..).
The job and fileset
