--- Begin Message ---
Package: nbd
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Saturday, April 25, 2009, I notified you of the beginning of a review process
concerning debconf templates for nbd.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading nbd with these changes
right now.
The second phase of this process will begin on Saturday, May 16, 2009, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Saturday, June 06, 2009. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Sunday, June 07, 2009, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- nbd.old/debian/nbd-client.templates 2009-04-24 09:09:42.985273108 +0200
+++ nbd/debian/nbd-client.templates 2009-05-13 07:20:51.247382443 +0200
@@ -1,9 +1,17 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [email protected] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: nbd-client/no-auto-config
Type: error
-_Description: AUTO_GEN is set at "n" in /etc/nbd-client.
- There's a line in /etc/nbd-client that reads "AUTO_GEN=n" -- or
- something likewise in sh-syntaxis. This means you don't want me to
- automatically regenerate that file.
+_Description: AUTO_GEN is set to "n" in /etc/nbd-client
+ The /etc/nbd-client file contains a line that sets the AUTO_GEN variable
+ to "n". The file will therefore not be regenerated automatically.
.
If that's wrong, remove the line and call "dpkg-reconfigure nbd-client"
afterwards.
@@ -11,8 +19,8 @@
Template: nbd-client/number
Type: string
Default: 0
-_Description: How many nbd-client connections do you want to use?
- nbd-client can handle multiple concurrent connections. Please state the
+_Description: Number of nbd-client connections to use:
+ nbd-client can handle multiple concurrent connections. Please specify the
number of connections you'd like this configuration script to set up.
.
Note that if something has already been specified in /etc/nbd-client, the
@@ -22,33 +30,29 @@
Type: select
_Choices: swap, filesystem, raw
Default: raw
-_Description: How do you intend to use the network block device (number:
${number})?
+_Description: Intended use of the network block device number ${number}:
The network block device can serve multiple purposes. One of the most
- interesting is to provide swapspace over the network for diskless clients,
+ interesting is to provide swap space over the network for diskless clients,
but you can store a filesystem on it, or do other things with it for which
a block device is interesting.
.
- If you intend to use the network block device as a swapdevice, choose
+ If you intend to use the network block device as a swap device, choose
"swap". If you intend to use it as a filesystem, add a line to /etc/fstab,
give it the option "_netdev" (else init will try to mount it before it's
usable), and choose "filesystem". For all other purposes, choose "raw".
- The only thing the nbd-client bootscript will do then is start an
+ The only thing the nbd-client boot script will do then is start an
nbd-client process; you will have to set it up manually.
Template: nbd-client/host
Type: string
_Description: Hostname of the server (number: ${number})?
- You need to fill in some name with which to resolve the machine on which
- the nbd-server process is running. This can be its hostname (also known to
- some as its "network name") or its IP-address.
+ Please enter the network name or IP address of the machine on which
+ the nbd-server process is running.
Template: nbd-client/port
Type: string
_Description: Port on which the nbd-server is running (number: ${number})?
- You need to fill in the portnumber on which the nbd-server is running.
- This could technically be any number between 1 and 65535, but for this to
- work, it needs to be the one on which a server can be found on the machine
- running nbd-server...
+ Please enter the TCP port number to access nbd-server.
Template: nbd-client/device
Type: string
@@ -58,21 +62,19 @@
this nbd-client. Note that this needs to be the full path to that entry,
not just the last part.
.
- If an unexisting /dev entry is provided, it will be created with minor
- number ${number}
+ If the /dev entry specified does not exist, it will be created with minor
+ number ${number}.
Template: nbd-client/killall
Type: boolean
Default: true
-_Description: Kill all nbd devices on 'stop'?
- When the nbd-client initscript is called to stop the nbd-client
- service, there are two things that can be done: either it can stop all
- nbd-client devices, or it can stop only those nbd-client devices that
- it knows about in its config file.
+_Description: Disconnect all NBD devices on "stop"?
+ When the nbd-client init script is called to stop the nbd-client service,
+ there are two things that can be done: either it can disconnect all
+ nbd-client devices (which are assumed not to be in use), or it can
+ disconnect only those nbd-client devices that it knows about in its
+ config file.
.
- The traditional behaviour was to stop all nbd-client devices, including
- those that were not specified in the nbd-client config file; for that
- reason, the default answer is to kill all nbd devices. However, if you
- are running critical file systems, such as your root device, on NBD,
- then this is a bad idea; in that case, please do not accept this
- option.
+ The default (and the traditional behavior) is to disconnect all
+ nbd-client devices. If the root device or other critical file systems
+ are on NBD this will cause data loss and should not be accepted.
--- nbd.old/debian/nbd-server.templates 2009-04-24 09:09:42.985273108 +0200
+++ nbd/debian/nbd-server.templates 2009-05-13 07:20:58.059382239 +0200
@@ -1,36 +1,41 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [email protected] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: nbd-server/number
Type: string
Default: 0
-_Description: How many nbd-servers do you want to run?
- You can run multiple nbd-server processes, to export multiple files or
- block devices. Please specify how many nbd-server configurations you
- want this configuration script to generate.
+_Description: Number of nbd-server instances to run:
+ Multiple nbd-server processes may run to export multiple files or
+ block devices. Please specify how many configurations for such servers you
+ want to generate.
.
Note that you can always add extra servers by adding them to
- /etc/nbd-server/config, or by running 'dpkg-reconfigure nbd-server'.
+ /etc/nbd-server/config, or by running "dpkg-reconfigure nbd-server".
Template: nbd-server/port
Type: string
-_Description: What port do you want to run the server on (number: ${number})?
- A port is a number in the TCP-header of a TCP/IP network package, that
- defines which application should process the data being sent. For most
- application-layer protocols, like FTP, HTTP, POP3 or SMTP, these numbers
- have been well-defined by IANA, and can be found in /etc/services or STD
- 2; for NBD, however, this would not be appropriate since NBD works with a
- separate port for each and every block device being used.
- .
- Therefore, NBD does not have a standard portnumber, which means you need
- to enter one. Make sure the portnumber being entered is not in use
- already.
+_Description: TCP Port for server number ${number}:
+ Please specify the TCP port this instance of nbd server will use for
+ listening. As NBD is likely to use more than one port, no dedicated
+ port has been assigned in IANA lists.
+ .
+ Therefore, NBD does not have a standard port number, which means you need
+ to provide one. You should make sure this port is not already in use.
Template: nbd-server/filename
Type: string
-_Description: What file do you want to export (number: ${number})?
- You need to enter a filename to a file or block device you want to export
- over the network. You can either export a real block device (e.g.
- "/dev/hda1"), export a normal file (e.g. "/export/nbd/bl1"), or export a
- bunch of files all at once; for the last option, you have the
- possibility to use "%s" in the filename, which will be expanded to the
+_Description: File to export (server number ${number}):
+ Please specify a file name or block device that should be exported
+ over the network. You can export a real block device (for instance
+ "/dev/hda1"); a normal file (such as "/export/nbd/bl1"); or a
+ bunch of files all at once. For the third option, you can
+ use "%s" in the filename, which will be expanded to the
IP-address of the connecting client. An example would be
"/export/swaps/swp%s".
.
@@ -39,35 +44,33 @@
Template: nbd-server/autogen
Type: error
-_Description: AUTO_GEN is set at "n" in /etc/nbd-server
- /etc/nbd-server contains a line "AUTO_GEN=n" -- or something equivalent in
- bash-syntaxis. This means you don't want me to automatically regenerate
- that file.
+_Description: AUTO_GEN is set to "n" in /etc/nbd-server
+ The /etc/nbd-server file contains a line that sets the AUTO_GEN variable
+ to "n". The file will therefore not be regenerated automatically.
.
Note that the current version of the nbd-server package no longer uses
- /etc/nbd-server; rather, it uses a new configuration file that is read by
- nbd-server itself (rather than the initscript), and which allows to set more
- options. See 'man 5 nbd-server' for details.
- .
- If you remove or uncomment the AUTO_GEN line, a file
- /etc/nbd-server/config in the new format may be generated based on your
- current configuration. Until then, your nbd-server installation will be
+ /etc/nbd-server. Instead it uses a new configuration file, read by
+ nbd-server itself (rather than the init script), which supports more
+ options. See "man 5 nbd-server" for details.
+ .
+ If you remove or comment out the AUTO_GEN line, a file
+ /etc/nbd-server/config in the new format may be generated based on the
+ current configuration. Until then, the nbd-server installation will be
broken.
Template: nbd-server/convert
Type: boolean
Default: true
-_Description: Convert old style nbd-server configuration file?
- A pre-2.9 nbd-server configuration file has been found on your system.
- The current nbd-server package no longer supports this file; if you
- depend on it, your nbd-server no longer works. If you accept this
+_Description: Convert old-style nbd-server configuration file?
+ A pre-2.9 nbd-server configuration file has been found on this system.
+ The current nbd-server package no longer supports this file and will
+ not work if it is kept as is.
+ .
+ If you choose this
option, the system will generate a new style configuration file based
- upon your old style configuration file. Then, the old style
- configuration file will be removed. If you do not accept this option, a
- new style configuration file will be generated based on a number of
- questions that will be asked; these may be the very same questions that
- you used to create the old style configuration file in the first place.
+ upon the old-style configuration file, which will be removed. Otherwise,
+ configuration questions will be asked and the system will generate a new
configuration file.
.
- If you already have a new style configuration file and you accept this
+ If a new-style configuration file already exists and you choose this
option, you will shortly see a "modified configuration file" prompt, as
usual.
--- nbd.old/debian/control 2009-04-24 09:09:42.985273108 +0200
+++ nbd/debian/control 2009-05-10 12:07:06.251683204 +0200
@@ -8,36 +8,34 @@
Package: nbd-server
Architecture: any
Depends: ${shlibs:Depends}, debconf (>= 1.2.9) | debconf-2.0, ucf, adduser,
${misc:Depends}
-Description: the Network Block Device server
- This package contains the server process for the Network Block
- Device. The Network Block Device is a client/server protocol that
- emulates a block device (like a hard disk, a floppy, a CD-ROM, ...)
+Description: Network Block Device protocol - server
+ Network Block Device (NBD) is a client/server protocol that
+ emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
over the network, thus giving the system the ability to swap over the
- network, or to use raw network diskspace for other purposes.
+ network, or to use raw network disk space for other purposes.
.
- Note, however, that it is not recommended to write to a single
- networked block device from different clients simultaneously, since
- that would probably result in data loss; if you want different
- clients to use the same shared network resource, you don't need the
- Network Block Device (which, basically, is a Disk Server protocol)
- but something else, like Sun's Network File System (NFS), or CODA.
+ However, writing to one Network Block Device from different clients
+ simultaneously is not recommended, and would probably result in data
+ loss. If you want multiple clients to share a remote resource, use a
+ network file system such as NFS or Coda.
+ .
+ This package provides the server binary for NBD.
Package: nbd-client
Architecture: alpha amd64 arm armeb armel hppa i386 ia64 lpia m32r m68k mips
mipsel powerpc ppc64 s390 sh3 sh3eb sh4 sh4eb sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0
-Description: the Network Block Device client
- This package contains the client process for the Network Block
- Device. The Network Block Device is a client/server protocol that
- emulates a block device (like a hard disk, a floppy, a CD-ROM, ...)
+Description: Network Block Device protocol - client
+ Network Block Device (NBD) is a client/server protocol that
+ emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
over the network, thus giving the system the ability to swap over the
- network, or to use raw network diskspace for other purposes.
+ network, or to use raw network disk space for other purposes.
+ .
+ However, writing to one Network Block Device from different clients
+ simultaneously is not recommended, and would probably result in data
+ loss. If you want multiple clients to share a remote resource, use a
+ network file system such as NFS or Coda.
.
- Note, however, that it is not recommended to write to a single
- networked block device from different clients simultaneously, since
- that would probably result in data loss; if you want different
- clients to use the same shared network resource, you don't need the
- Network Block Device (which, basically, is a Disk Server protocol)
- but something else, like Sun's Network File System (NFS), or CODA.
+ This package provides the client binary for NBD.
Package: nbd-client-udeb
Section: debian-installer
@@ -45,6 +43,12 @@
Depends: ${shlibs:Depends}
XC-Package-Type: udeb
Architecture: alpha amd64 arm armeb armel hppa i386 ia64 lpia m32r m68k mips
mipsel powerpc ppc64 s390 sh3 sh3eb sh4 sh4eb sparc
-Description: the Network Block Device client
- This package contains the client process for the Network Block Device.
+Description: Network Block Device protocol - client for Debian Installer
+ Network Block Device (NBD) is a client/server protocol that
+ emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
+ over the network, thus giving the system the ability to swap over the
+ network, or to use raw network disks pace for other purposes.
+ .
+ This package provides the client binary for NBD.
+ .
It is a minimal version meant for use in the installer only.
--- End Message ---
