Your message dated Thu, 15 Sep 2005 09:32:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316356: fixed in backup-manager 0.5.8b-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; 30 Jun 2005 11:38:17 +0000
>From [EMAIL PROTECTED] Thu Jun 30 04:38:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp05.web.de [217.72.192.209]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DnxN2-0003Uw-00; Thu, 30 Jun 2005 04:38:17 -0700
Received: from [217.251.235.193] (helo=[127.0.0.1])
by smtp05.web.de with asmtp (WEB.DE 4.105 #297)
id 1DnxMW-0006NO-00
for [EMAIL PROTECTED]; Thu, 30 Jun 2005 13:37:45 +0200
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 30 Jun 2005 13:36:02 +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: Problems with CD-Burning
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: backup-manager
Version: 0.5.8-2
Severity: important
I have a problem with writing archives to CDR(W). Backup-manager uses
the variable BM_BURNING_DEVICE both as device for cdrecord and as a
mountable device to verify the burned files. This causes problems for
me: if I set BM_BURNING_DEVICE to a device file, say /dev/cdrw, cdrecord
fails, leaving the following log (footnote 1):
scsidev: '/dev/cdrw'
devname: '/dev/cdrw'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
cdrecord: Read-only file system. Cannot open '/dev/cdrw'. Cannot open SCSI
driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord:
cdrecord: For more information, install the cdrtools-doc
cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <[EMAIL PROTECTED]>.
The original author should not be bothered with problems of this version.
But if I set BM_BURNING_DEVICE to "0,1,0" as in my /etc/default/cdrecord, the
burning works but not the verification, since "0,1,0" can obviously not be
mounted, as confirmed in the error message of backup-manager:
"unable to mount 0,1,0 on /tmp/bm-mnt.4oGUyF".
A workaround that worked for me: as root run (needs GNU sed 3.95 or higher)
sed -i~ 's/dev=${BM_BURNING_DEVICE}//' /usr/share/backup-manager/actions.sh
which will remove the explicit device setting for cdrecord and let
cdrecord the system's default burning device (most people will have
only one anyway)(footnote 2).
Regards,
Sven Joachim
-- 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:
backup-manager/upload-key:
* backup-manager/name-format: long
backup-manager/upload-hosts:
backup-manager/upload-user-ftp:
* backup-manager/cron_frequency: daily
* backup-manager/cron_d_remove_deprecated: true
* backup-manager/blacklist: /home/sven/tmp
* backup-manager/time-to-live: 5
* backup-manager/burning-maxsize: 650
backup-manager/upload-user-scp-warning:
backup-manager/transfert_mode: scp
* backup-manager/dump_symlinks: false
backup-manager/upload-user-scp: bmngr
* backup-manager/burning-device: /dev/cdrw
backup-manager/upload-dir: /var/archives/uploads
* backup-manager/directories: /etc /home/sven
* backup-manager/filetype: tar.gz
* backup-manager/backup-repository: /var/archives
* backup-manager/burning-method: CDR
* backup-manager/burning-enabled: true
* backup-manager/cron_remove_deprecated: false
* backup-manager/want_to_upload: false
footnote 1: To actually get the log, I had to comment out the line
with "rm -f $logfile" in logger.sh. This is subject of
another bug report.
footnote 2: After I applied this patch, mounting the freshly burned CDR
and verifying the md5sums worked fine. But I got an "MD5 hash mismatch"
for files which were actually symlinks in my $BM_ARCHIVES_REPOSITORY.
Tell me if you want another bug report on that.
---------------------------------------
Received: (at 316356-close) by bugs.debian.org; 15 Sep 2005 16:38:14 +0000
>From [EMAIL PROTECTED] Thu Sep 15 09:38:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EFwea-0005YF-00; Thu, 15 Sep 2005 09:32:04 -0700
From: Alexis Sukrieh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#316356: fixed in backup-manager 0.5.8b-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 15 Sep 2005 09:32:04 -0700
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: 3
Source: backup-manager
Source-Version: 0.5.8b-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.8b-1.diff.gz
to pool/main/b/backup-manager/backup-manager_0.5.8b-1.diff.gz
backup-manager_0.5.8b-1.dsc
to pool/main/b/backup-manager/backup-manager_0.5.8b-1.dsc
backup-manager_0.5.8b-1_all.deb
to pool/main/b/backup-manager/backup-manager_0.5.8b-1_all.deb
backup-manager_0.5.8b.orig.tar.gz
to pool/main/b/backup-manager/backup-manager_0.5.8b.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: Mon, 12 Sep 2005 17:32:16 +0200
Source: backup-manager
Binary: backup-manager
Architecture: source all
Version: 0.5.8b-1
Distribution: unstable
Urgency: low
Maintainer: Alexis Sukrieh <[EMAIL PROTECTED]>
Changed-By: Alexis Sukrieh <[EMAIL PROTECTED]>
Description:
backup-manager - command-line backup tool
Closes: 315983 316041 316356 316358 316359 324814
Changes:
backup-manager (0.5.8b-1) unstable; urgency=low
.
* New upstream release: 0.5.8b
+ The default cdrecord device is used instead of forcing a device.
(closes: #316356)
+ The log of cdrecord is removed only when everything went fine.
(closes: #316358)
+ The bzip2 binary is mandatory if the filetype chosen is tar.bz2.
(closes: #316359)
+ Typos fixed in the manpage backup-manager.3.
(closes: #316041)
* Removed already applied patches.
* New french translations
(closes: #324814)
* Fixed the manpages section.
(closes: #315983)
Files:
0a05fecae6b09f3bb43e467f939baa02 620 admin optional backup-manager_0.5.8b-1.dsc
e00fa528d0b17c960f17feaed866915f 42798 admin optional
backup-manager_0.5.8b.orig.tar.gz
626d5b967e448cc58a2c5c7bb6b4a065 42348 admin optional
backup-manager_0.5.8b-1.diff.gz
7bc77a7bb9e599f623b88607ee2effe7 59566 admin optional
backup-manager_0.5.8b-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDKZS7hYgK5b1UDsERApr8AJ9kcSwa6zZ5STLRwq/z9KrHPHm78QCfWvWr
+OdkC/UHbxwmFvKusikaivg=
=JNpB
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
