Package: hobbit
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Tuesday, September 04, 2007, I notified you of the beginning of a review
process
concerning debconf templates for hobbit.
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 are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading hobbit with these changes right now.
The second phase of this process will begin on Friday, September 21, 2007, 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 Friday, October 12, 2007. 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 <DAY25>, 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: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- hobbit.old/debian/hobbit-client.templates 2007-09-08 10:01:50.000000000
+0200
+++ hobbit/debian/hobbit-client.templates 2007-09-18 07:45:05.413054151
+0200
@@ -1,18 +1,29 @@
+# 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: hobbit-client/HOBBITSERVERS
Type: string
Default: 127.0.0.1
_Description: Hobbit server:
- The network address used to access your Hobbit server(s). If you have multiple
- servers, list all of them separated by spaces.
- Consider using the IP-adresses instead of hostnames, in case of a problem DNS
- might not work.
+ Please enter the network address used to access the Hobbit
+ server(s). If you use multiple servers, use a space-separated list of
+ addresses.
+ .
+ Using host names instead of IP addresses is discouraged in case the
+ network experiences DNS failures.
Template: hobbit-client/CLIENTHOSTNAME
Type: string
Default:
_Description: Client hostname:
- The hostname used by the Hobbit client when sending
+ Please enter the host name used by the Hobbit client when sending
reports to the Hobbit server. This name must match
- the named used in the bb-hosts file on the Hobbit
+ the name used in the bb-hosts file on the Hobbit
server.
--- hobbit.old/debian/control 2007-09-08 10:01:50.000000000 +0200
+++ hobbit/debian/control 2007-09-15 11:39:02.962495432 +0200
@@ -12,9 +12,9 @@
Package: hobbit
Architecture: any
Depends: hobbit-client, ${shlibs:Depends}, ${misc:Depends}
-Description: monitoring system for systems, networks and applications
+Description: monitoring system for systems, networks and applications - server
Hobbit is a network- and applications-monitoring system designed for use in
- large-scale networks. But it will also work just fine on a small network with
+ large-scale networks. It will also work just fine on a small network with
just a few nodes. It is low-overhead and high-performance, with an easy to use
web front-end. It handles monitoring of network services, and through client
packages it can also be used to monitor server-specific items. Alerts can
