[Resolvconf-devel] Bug#464499: resolvconf: [debconf_rewrite] Debconf templates and debian/control review

Thu Feb 7 06:37:13 UTC 2008

Package: resolvconf
Version: N/A
Severity: normal
Tags: patch

Dear Debian maintainer,

On Wednesday, January 23, 2008, I notified you of the beginning of a review process
concerning debconf templates for resolvconf.

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 resolvconf with these changes right now.

The second phase of this process will begin on Sunday, February 10, 2008, 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 Sunday, March 02, 2008. 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 Monday, March 03, 2008, 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')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-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
-------------- next part --------------

--- resolvconf.old/debian/templates	2008-01-18 06:22:38.669402447 +0100
+++ resolvconf/debian/templates	2008-02-07 07:37:06.119264633 +0100
@@ -1,56 +1,64 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english at lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: resolvconf/linkify-resolvconf
 Type: boolean
 Default: true
 _Description: Prepare /etc/resolv.conf for dynamic updates?
- This package contains the infrastructure required for dynamic updating of
- the resolver configuration file. Part of the necessary infrastructure is
- a symbolic link from /etc/resolv.conf to /etc/resolvconf/run/resolv.conf.
- If you agree then this link will be created. The existing /etc/resolv.conf
- file will be preserved as /etc/resolvconf/resolv.conf.d/original; it will
- be restored if this package is removed.
- .
- If you wish to prevent future installations from recreating the symbolic
- link then you can run dpkg-reconfigure later to withdraw your agreement.
+ The resolvconf package contains the infrastructure required for
+ dynamic updating of the resolver configuration file. Part of the
+ necessary infrastructure is a symbolic link from /etc/resolv.conf to
+ /etc/resolvconf/run/resolv.conf. If you choose this option then this
+ link will be created; the existing /etc/resolv.conf file will be
+ preserved as /etc/resolvconf/resolv.conf.d/original, and will be
+ restored if this package is removed.
  .
- If you do not agree then the necessary symbolic link will not be created
- and consequently your resolver configuration file will not be dynamically
- updated. In order to activate dynamic updating you will have to configure
- resolvconf manually following the straightforward instructions in the
- README file. If you choose not to configure resolvconf at all then you
- should remove the package because its presence causes some programs to
- deviate from their default behavior.
+ Declining this option will prevent future installations from
+ recreating the symbolic link and therefore the resolver configuration
+ file will not be dynamically updated. Dynamic updating can then be
+ activated following instructions in the README file.
  .
- However you decide, you should read the README file.
+ The presence of resolvconf can affect the behavior of other programs,
+ so it should not be left installed if unconfigured.
 
 Template: resolvconf/downup-interfaces
 Type: note
-_Description: Remember to reconfigure network interfaces
- Once resolvconf is installed, interface configurers supply nameserver
- information to it (which it then makes available to the C Library resolver
+_Description: Network interfaces configuration mandatory
+ Once resolvconf is installed, interface configurers supply name server
+ information to it (which it then makes available to the C library resolver
  and to DNS caches). However, they do this only when they bring up interfaces.
- Therefore for resolvconf's nameserver information to be up to date after
- initial installation it is necessary to reconfigure interfaces --
- that is, to take them down and then to bring them up again -- and to restart
+ Therefore for resolvconf's name server information to be up to date after
+ initial installation it is necessary to reconfigure interfaces (that is,
+ to take them down and then to bring them up again) and to restart
  DNS caches.
 
 Template: resolvconf/link-tail-to-original
 Type: boolean
 Default: false
 _Description: Append original file to dynamic file?
- If your original static resolver configuration file (/etc/resolv.conf)
- contains nameserver addresses then those addresses should be listed on
+ If the original static resolver configuration file (/etc/resolv.conf)
+ contains name server addresses, those addresses should be listed on
  "dns-nameservers" lines in /etc/network/interfaces as described in the
- README. Until you have modified /etc/network/interfaces and reconfigured
- the affected interfaces resolvconf will not include those addresses in the
- dynamically generated resolver configuration file. Without those addresses
- you may have trouble resolving domain names. A TEMPORARY solution is to
- append the whole original resolver configuration file to the end of
- the dynamically generated file. This will be done if there is a symbolic
- link from /etc/resolvconf/resolv.conf.d/tail to
- /etc/resolvconf/resolv.conf.d/original. If you agree then this symbolic
- link will be created, provided that no /etc/resolvconf/resolv.conf.d/tail
- already exists.
+ README file.
+ .
+ Until /etc/network/interfaces has been edited and the affected
+ interfaces brought down and up again, the name server addresses will
+ not be included in the dynamically generated resolver configuration
+ file.
+ .
+ If you choose this option, a temporary workaround will be put in
+ place: a symbolic link will be created (if it does not already exist)
+ from /etc/resolvconf/resolv.conf.d/tail to
+ /etc/resolvconf/resolv.conf.d/original. This will cause the whole of
+ that original resolver configuration file to be appended to the
+ dynamically generated file.
  .
- After you have modified /etc/network/interfaces to add the required
- "dns-nameservers" lines you should point the
- /etc/resolvconf/resolv.conf.d/tail symbolic link to /dev/null.
+ After the required "dns-nameservers" lines have been added to
+ /etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link
+ should be replaced by one to /dev/null.
--- resolvconf.old/debian/control	2008-01-18 06:22:38.669402447 +0100
+++ resolvconf/debian/control	2008-02-04 17:51:13.069697645 +0100
@@ -11,16 +11,13 @@
 Enhances: dhcp3-client (>= 3.0+3.0.1rc11-5), dhcp-client (>= 2.0pl5-18), dhcpcd (>= 1:1.3.22pl4-9), pump (>= 0.8.19), udhcpc (>= 0.9.8cvs20050124-3), ppp (>= 2.4.2), ifupdown (>= 0.6.4-4.7), network-manager, bind9 (>= 1:9.2.3-1), bind (>= 1:8.4.1-2), dnsmasq (>= 2.9-2), pdnsd (>= 1.1.11par-1), totd (>= 1.4-4), libc6, nscd
 Depends: coreutils (>= 5.93), lsb-base (>= 3.0-9), ${misc:Depends}
 Conflicts: pppconfig (<< 2.3.1), pppoeconf (<< 1.0), xisp, webmin (<< 1.150-2), webmin-wvdial (<< 1.160-3), dhcp3-client (<< 3.0+3.0.1rc11-5), dhcp-client (<< 2.0pl5-18), dhcp-client (= 3.0.1betaRC4-1), dhcpcd (<< 1:1.3.22pl4-7), pump (<< 0.8.15-1), udhcpc (<< 0.9.8cvs20050124-3), pcmcia-cs (<< 3.2.5-1), ifupdown (<< 0.6.4-4.1), divine, laptop-net (<< 2.21-1), whereami (<< 0.3.3), bind9 (<< 1:9.2.1-7), bind (<< 1:8.3.4-1), dnsmasq (<< 1.13-2), pdnsd (<< 1.1.10par-4), totd (<< 1.4-4)
-Description: nameserver information handler
- Resolvconf is a framework for keeping track of the system's
- information about currently available nameservers. It sets
- itself up as the intermediary between programs that supply
- nameserver information and programs that use nameserver
- information. Examples of programs that supply nameserver
- information are: ifupdown, DHCP clients, the PPP daemon and
- local nameservers. Examples of programs that use this
- information are: DNS caches, resolver libraries and the
- programs that use them.
+Description: name server information handler
+ Resolvconf is a framework for keeping the system's information about
+ currently available name servers up to date. It sets itself up as the
+ intermediary between programs that supply this information, such as
+ ifupdown, DHCP clients, the PPP daemon, and local name servers, and
+ programs that use this information, such as DNS caches and resolver
+ libraries.
  .
- This package may require some manual configuration.  Please
+ This package may require some manual configuration. Please
  read the README file for detailed instructions.
