Your message dated Wed, 02 Nov 2005 14:32:14 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318782: fixed in backup-manager 0.5.9a-1
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Jul 2005 17:17:37 +0000
>From [EMAIL PROTECTED] Sun Jul 17 10:17:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp06.web.de [217.72.192.224]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1DuClk-0001ia-00; Sun, 17 Jul 2005 10:17:36 -0700
Received: from [217.251.234.196] (helo=[127.0.0.1])
by smtp06.web.de with asmtp (WEB.DE 4.105 #297)
id 1DuClE-00067P-00
for [EMAIL PROTECTED]; Sun, 17 Jul 2005 19:17:05 +0200
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 17 Jul 2005 19:17:05 +0200
From: Sven Joachim <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050331)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: backup-manager: tar errors are not noticed
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: [EMAIL PROTECTED]
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: backup-manager
Version: 0.5.8-2
Severity: important
There is a problem with backup-manager which has a great impact on the
robustness of the package: Errors encountered during the creation of
the archives will often go unnoticed. To see what I mean, here is an
example with the relevant variables set as follows:
BM_FILETYPE="tar.gz"
BM_ARCHIVES_REPOSITORY="/tmp/junk"
BM_DIRECTORIES="/etc/ /nonexistent"
Then "backup-manager -v" prints the following (leading and trailing
lines omitted):
...
Creating /tmp/junk/debian-etc.20050717.tar.gz:ok
(1M,6485f90d217a75dc5831332bf6ba25c4)
Creating /tmp/junk/debian-nonexistent.20050717.tar.gz:~ok
(1M,a055d13c14a5f9a5be59d6481eb33226)
...
The _only_ indication of an error (the non-existing source directory)
is that small "~" in the second line, which not many people will
recognize as an error or warning message. The same problem occurs with
other possible tar errors, such as insufficient disk space on the
partition with the archives repository.
I suggest that backup-manager should
- print a warning if tar exits with non-zero status
- return itself a non-zero exit status in that case
- not suppress error messages by tar (if tar prints error messages and
- backup-manager is run via (ana)cron, these messages will be mailed
- to the administrator which seems appropriate to me).
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages backup-manager depends on:
ii debconf 1.4.30.13 Debian configuration
management sy
ii gzip 1.3.5-10 The GNU compression utility
ii ucf 1.17 Update Configuration File:
preserv
-- debconf information excluded
---------------------------------------
Received: (at 318782-close) by bugs.debian.org; 2 Nov 2005 22:37:31 +0000
>From [EMAIL PROTECTED] Wed Nov 02 14:37:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EXR9S-0005aP-00; Wed, 02 Nov 2005 14:32:14 -0800
From: Alexis Sukrieh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#318782: fixed in backup-manager 0.5.9a-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 02 Nov 2005 14:32:14 -0800
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 4
Source: backup-manager
Source-Version: 0.5.9a-1
We believe that the bug you reported is fixed in the latest version of
backup-manager, which is due to be installed in the Debian FTP archive:
backup-manager_0.5.9a-1.diff.gz
to pool/main/b/backup-manager/backup-manager_0.5.9a-1.diff.gz
backup-manager_0.5.9a-1.dsc
to pool/main/b/backup-manager/backup-manager_0.5.9a-1.dsc
backup-manager_0.5.9a-1_all.deb
to pool/main/b/backup-manager/backup-manager_0.5.9a-1_all.deb
backup-manager_0.5.9a.orig.tar.gz
to pool/main/b/backup-manager/backup-manager_0.5.9a.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexis Sukrieh <[EMAIL PROTECTED]> (supplier of updated backup-manager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 14 Oct 2005 11:16:52 +0200
Source: backup-manager
Binary: backup-manager
Architecture: source all
Version: 0.5.9a-1
Distribution: unstable
Urgency: low
Maintainer: Alexis Sukrieh <[EMAIL PROTECTED]>
Changed-By: Alexis Sukrieh <[EMAIL PROTECTED]>
Description:
backup-manager - command-line backup tool
Closes: 317956 318782 319909 324014 325636 327635 331755
Changes:
backup-manager (0.5.9a-1) unstable; urgency=low
.
* New upstream release: error during archive generation are handled
nicely.
(closes: #318782)
* Depends on debconf-2.0 as well.
(closes: #331755)
* New templates in debconf for configuring BM_REPOSITORY_USER and
BM_REPOSITORY_GROUP.
(closes: #317956)
* It's possible to choose "never" in debconf when the CRON frequency is
prompted.
(closes: #325636)
* Updated the postrm script so we use ucf --purge only when ucf is
installed, and we remove manually the conffile /etc/backup-manager.conf as
it's installed by postinst, and then not flagged as a conffile.
(closes: #319909)
* Upstream bug fixed in debian/patches/01_md5sum_fixfor_324014.dpatch:
MD5 files are now readable by md5sum (added two spaces instead of one,
thanks to Scott Wolchok)
(closes: #324014)
* Updates for upstream and debconf l10n:
+ New french po files (closes: #327635).
+ New Czech po files.
+ New Italian debconf po file.
* Added a note in README.Debian about the conffile transition for 0.5.9a and
give a hint about how to upgrade a conffile with the contrib script
`upgrade-conffile.sh'.
Files:
9fd18ab1bc666affe2551393479090cc 620 admin optional backup-manager_0.5.9a-1.dsc
ae8a84c15df12f95f185c76a5b661e3c 48389 admin optional
backup-manager_0.5.9a.orig.tar.gz
0e771fe0618b1625224006db1345771d 41827 admin optional
backup-manager_0.5.9a-1.diff.gz
11e98f07c4de9992872dd19c619a715e 62638 admin optional
backup-manager_0.5.9a-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDaRguhYgK5b1UDsERAl4ZAJ9wee64MYTmHBgymlvjh03e0eduUgCfaEpx
GqxqIPXum2yhfOaTfwfHEjw=
=4XdX
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
