[Resolvconf-devel] Bug#464499: resolvconf: General update after the debconf review process

Christian Perrier bubulle at debian.org
Fri Feb 29 06:22:55 UTC 2008 

Dear Debian maintainer,

On Wednesday, January 23, 2008, I sent you a notification about the beginning of a review
action on debconf templates for resolvconf.

Then, I sent you a bug report with rewritten templates and announcing
the beginning of the second phase of this action: call for translation
updates.

Translators have been working hard and here is now the result of their efforts.

Please consider using it EVEN if you committed files to your
development tree as long as they were reported.

The attached tarball contains:

- debian/changelog with the list of changes
- debian/control with rewrites of packages' descriptions
- debian/<templates> with all the rewritten templates file(s)
- debian/po/*.po with all PO files (existing ones and new ones)

As said, please use *at least* the PO files as provided here,
preferrably over those sent by translators in their bug reports. All
of them have been checked and reformatted. In some cases, formatting
errors have been corrected.

The patch.rfr file contains a patch for the templates and control
file(s) alone.

Please note that this patch applies to the templates and control
file(s) of your package as of Wednesday, January 23, 2008. If your package was updated
in the meantime, I may have updated my reference copy....but I also
may have missed that. This is indeed why I suggested you do not
modified such files while the review process was running,
remember..:-)

It is now safe to upload a new package version with these changes.

Please notify me of your intents with regards to this. 

There is of course no hurry to update your package but feel free to
contact me in case you would need sponsoring or any other action to
fix this.



-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.tar.gz
Type: application/octet-stream
Size: 44096 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20080229/0ceef77f/attachment-0001.obj 
-------------- next part --------------
--- resolvconf.old/debian/templates	2008-01-18 06:22:38.669402447 +0100
+++ resolvconf/debian/templates	2008-02-07 18:23:26.942638726 +0100
@@ -1,56 +1,65 @@
+# 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 reconfiguration 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
- "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.
+ 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. For more
+ information, please consult the resolvconf(8) man page and the
+ 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-07 18:25:13.618639259 +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.
--- resolvconf.old/debian/changelog	2008-01-18 06:22:38.665401307 +0100
+++ resolvconf/debian/changelog	2008-02-28 07:16:46.643531405 +0100
@@ -1,3 +1,21 @@
+resolvconf (1.39) UNRELEASED; urgency=low
+
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+    english team as part of the Smith review project. Closes: #464499
+  * [Debconf translation updates]
+  * Galician. Closes: #465305
+  * Indonesian. Closes: #465411
+  * Vietnamese. Closes: #465436
+  * German. Closes: #466099
+  * Czech. Closes: #466307
+  * Portuguese. Closes: #466464
+  * Finnish. Closes: #466607
+  * Russian. Closes: #467443
+  * French. Closes: #467530
+  * Dutch. Closes: #468249
+
+ -- Christian Perrier <bubulle at debian.org>  Thu, 28 Feb 2008 07:16:46 +0100
+
 resolvconf (1.38) unstable; urgency=low
 
   [ Thomas Hood ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20080229/0ceef77f/attachment-0001.pgp

More information about the Resolvconf-devel mailing list