Your message dated Sat, 19 Jul 2014 19:08:11 +0200
with message-id <[email protected]>
and subject line Mark bug closed in 1.1-6 upload
has caused the Debian Bug report #754593,
regarding mt erase is a full (long) erase, document it as such
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
754593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754593
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mt-st
Version: 1.1-5
Severity: minor
Tags: patch
Attached is a patch which improves the man page to say that 'mt erase'
is a full erase (not a quick one, erasing just the file/end-of-tape
marks).
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14.12-ruru0 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mt-st depends on:
ii libc6 2.18-7
mt-st recommends no packages.
mt-st suggests no packages.
-- Configuration Files:
/etc/stinit.def changed [not included]
-- no debconf information
Author: Iustin Pop <[email protected]>
Description: Improve manual page for the erase subcommand
--- a/mt.1
+++ b/mt.1
@@ -104,7 +104,9 @@
.I count
setmarks at current position (only SCSI tape).
.IP erase
-Erase the tape.
+Erase the tape. Note that this is a long erase, which on modern
+(high-capacity) tapes can take many hours, and which usually can't be
+aborted.
.IP status
Print status information about the tape unit. (If the density code is
"no translation" in the status output, this does not affect working of the
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.1-6
Version 1.1-6 actually fixes this bug, but the changelog entry was
wrong.
signature.asc
Description: Digital signature
--- End Message ---