Your message dated Wed, 18 Apr 2007 09:57:27 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419889: amanda fails due to tar 1.16
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: amanda-client
Version: 2.5.1p1-2.1
Severity: important
After the upgrade from sarge to etch the amanda backup fails on
"file changed as we read it". Looks like this is due to a change in
tar 1.16:
> * After creating an archive, tar exits with code 1 if some files were
> changed while being read. Previous versions exited with code 2 (fatal
> error), and only if some files were truncated while being archived.
The problem is fixed fixed upstream in amanda 2.5.1p3:
* client-src/sendbackup.c: Ignore tar exit with status 1.
Thanks in advance,
Joerg
--- End Message ---
--- Begin Message ---
On Wed, 2007-04-18 at 16:15 +0200, Joerg Schumacher wrote:
> Package: amanda-client
> Version: 2.5.1p1-2.1
> Severity: important
>
> After the upgrade from sarge to etch the amanda backup fails on
> "file changed as we read it". Looks like this is due to a change in
> tar 1.16:
>
> > * After creating an archive, tar exits with code 1 if some files were
> > changed while being read. Previous versions exited with code 2 (fatal
> > error), and only if some files were truncated while being archived.
>
> The problem is fixed fixed upstream in amanda 2.5.1p3:
>
> * client-src/sendbackup.c: Ignore tar exit with status 1.
2.5.1p3 is in unstable, and should work fine for you if you install it
on your otherwise-etch system. Unfortunately, p3 came out too late in
the etch release cycle to include... and since dump and other archivers
work well even when tar does not, this wasn't treated as RC.
Unclear to me whether this would qualify for inclusion in an etch stable
update or not, CC'ing the release team for their opinion rather than
just closing this bug immediately.
Bdale
--- End Message ---
