Your message dated Mon, 18 Dec 2006 13:56:27 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403656: cedar-backup2-doc: section "Command Line
Interface" should probably be an entire chapter
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: cedar-backup2-doc
Version: 2.8.1-1
Severity: wishlist
"Chapter 4. Configuration" should probably only contain description of the
configuration file and instructions on how to set up typical backup systems, so
a section on command-line interface seems out of place. It should probably
be a whole another chapter preceeding chapter 4 on how at system level (as
opposed to abstract logical level presented in chapter 2) Cedar Backup
operations are organised. It turns out that every operation is done via cback
script invocation just like everything in Debian package management system is
done at low level via dpkg, so it would be appropriate to describe the script
and its role in that new chapter.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.1
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
-- no debconf information
--- End Message ---
--- Begin Message ---
On 12/18/06, Dmitry Rutsky <[EMAIL PROTECTED]> wrote:
Package: cedar-backup2-doc
Version: 2.8.1-1
Severity: wishlist
"Chapter 4. Configuration" should probably only contain description of the
configuration file and instructions on how to set up typical backup systems, so
a section on command-line interface seems out of place. It should probably
be a whole another chapter preceeding chapter 4 on how at system level (as
opposed to abstract logical level presented in chapter 2) Cedar Backup
operations are organised. It turns out that every operation is done via cback
script invocation just like everything in Debian package management system is
done at low level via dpkg, so it would be appropriate to describe the script
and its role in that new chapter.
I understand the point you're making. This subject probably does
merit some expansion in the manual, and possibly some reorganization.
However, at this stage in the project -- and with the limited time I
have to work on Cedar Backup currently -- it's not going to happen any
time soon. Sorry about that.
I am going to close this bug in Debian (since it's an enhancement
request that is not Debian-specific) and I'll track it upstream.
KEN
--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
http://www.cedar-solutions.com/
--- End Message ---
