Dear Debian maintainer, On Monday, August 04, 2014, I notified you of the beginning of a review process concerning debconf templates for whatmaps. The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original 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 whatmaps with these changes right now. The second phase of this process will begin on Friday, August 22, 2014, 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, September 12, 2014. 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 Saturday, September 13, 2014, 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. --
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # debian-l10n-english@lists.debian.org for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: whatmaps/enable_service_restarts Type: boolean Default: false _Description: Automatically restart services after library security updates? Services need to be restarted to benefit from updates of shared libraries they depend on. Otherwise they remain vulnerable to security bugs fixed in these updates. . Automatic service restarts are only done if APT fetched the library from a source providing security updates. This also affects packages installed via "unattended-upgrades".
Source: whatmaps
Section: admin
Priority: extra
Maintainer: Guido Günther <agx@sigxcpu.org>
Build-Depends: debhelper (>= 9~), lsb-release,
python-all (>> 2.6.6-3~),
python-mock,
python-nose,
python-setuptools,
Standards-Version: 3.9.5
Homepage: https://honk.sigxcpu.org/piki/projects/whatmaps
Vcs-Git: git://honk.sigxcpu.org/git/whatmaps.git/
X-Python-Version: >= 2.7
XS-Testsuite: autopkgtest
Package: whatmaps
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, lsb-release,
python-apt, python-pkg-resources
Description: tool to find processes mapping shared objects
After package upgrades (especially security fixes), services using a
shared library need to be restarted to make use of the updated version.
.
Whatmaps looks for shared objects provided by upgraded packages, lists any
running processes that map them, and can integrate with APT to restart
services as needed after security upgrades.
--- whatmaps.old/debian/templates 2014-07-31 07:22:25.299890957 +0200 +++ whatmaps/debian/templates 2014-08-19 06:54:02.993127798 +0200 @@ -1,11 +1,20 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# debian-l10n-english@lists.debian.org for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: whatmaps/enable_service_restarts Type: boolean Default: false -_Description: Automatically restart services after shared library security updates? +_Description: Automatically restart services after library security updates? Services need to be restarted to benefit from updates of shared libraries they - depend on. Without that they remain vulnerable to security bugs fixed in these + depend on. Otherwise they remain vulnerable to security bugs fixed in these updates. . - Automatic service restarts are only done if apt fetched the library from a + Automatic service restarts are only done if APT fetched the library from a source providing security updates. This also affects packages installed - via unattended-upgrades. + via "unattended-upgrades".
Attachment:
signature.asc
Description: Digital signature