Package: portmap
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Tuesday, August 28, 2007, I notified you of the beginning of a review process
concerning debconf templates for portmap.
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 portmap with these changes right now.
The second phase of this process will begin on Tuesday, September 18, 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 Tuesday, October 09, 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
--- portmap.old/debian/templates 2007-08-27 15:13:18.610015498 +0200
+++ portmap/debian/templates 2007-09-15 11:39:20.961623729 +0200
@@ -1,15 +1,24 @@
+# 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: portmap/loopback
Type: boolean
Default: false
_Description: Should portmap be bound to the loopback address?
- Portmap by default listens to all IP addresses. However, if you are
- not providing network RPC services to remote clients (you are if you are
- setting up a NFS or NIS server) you can safely bind it to the loopback
- IP address (127.0.0.1)
+ By default, portmap listens to all IP addresses. However, if this
+ machine does not provide network RPC services (such as NIS or NFS) to
+ remote clients, you can safely bind it to the loopback IP address
+ (127.0.0.1).
.
This will allow RPC local services (like FAM) to work properly, while
- preventing remote systems from accessing your RPC services.
+ preventing remote systems from accessing the RPC services.
.
- You can also change this configuration by editing the OPTIONS
- line in the /etc/default/portmap file. If you just don't specify
- the -i option it will bind to all interfaces.
+ This configuration can be changed by editing the OPTIONS line in the
+ /etc/default/portmap file and adapting the use of the -i option to
+ your needs.
--- portmap.old/debian/control 2007-08-27 15:13:18.610015498 +0200
+++ portmap/debian/control 2007-09-12 07:44:35.740867248 +0200
@@ -10,9 +10,9 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 1.3-9)
Replaces: netbase (<< 4.00)
-Description: The RPC portmapper
+Description: RPC port mapper
Portmap is a server that converts RPC (Remote Procedure Call) program
- numbers into DARPA protocol port numbers. It must be running in order
+ numbers into DARPA protocol port numbers. It must be running in order
to make RPC calls.
.
Services that use RPC include NFS and NIS.
