Dear Debian maintainer, On Monday, July 02, 2012, I notified you of the beginning of a review process concerning debconf templates for fs2ram. 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 fs2ram with these changes right now. The second phase of this process will begin on Tuesday, July 10, 2012, 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, July 31, 2012. 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 Wednesday, August 01, 2012, 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: fs2ram/main_install_type
Type: select
__Choices: Content-preserving, Structure-preserving, Unconfigured
Default: Content-preserving
_Description: Configuration for fs2ram:
Please select the fs2ram configuration that best meets your needs.
.
* Content-preserving: /var/tmp, /var/cache, and /var/log will be in
RAM, reducing writes to the hard drive, and fs2ram will preserve the
contents of these file systems across reboots.
* Structure-preserving: /var/tmp, /var/cache, and /var/log will be in
RAM, but fs2ram will only preserve their directory structures across
reboots, not their (potentially private) contents.
* Unconfigured: the fs2ram configuration file will be left empty and
must be filled manually.
Template: fs2ram/rcs_enforce_ramtmp_configuration
Type: boolean
Default: true
_Description: Turn /tmp into a RAM file system?
Please choose whether /tmp should be converted into a tmpfs
mount point. This is not the default for freshly installed
systems.
Template: fs2ram/rcs_enforce_ramlock_configuration
Type: boolean
Default: true
_Description: Turn /var/lock into a RAM file system?
Please choose whether /var/lock should be converted into a tmpfs
mount point. This is the default for freshly installed systems.
Source: fs2ram
Section: admin
Priority: optional
Maintainer: Philippe Le Brouster <plb@nebkha.net>
Build-Depends: debhelper (>= 9~)
Standards-Version: 3.9.3
DM-Upload-Allowed: yes
Package: fs2ram
Architecture: all
Depends: ${misc:Depends}, ucf
Description: tools to preserve tmpfs contents across reboots
fs2ram manages temporary file systems across reboots. Each tmpfs mountpoint
can be associated with a pre-mount script, which is executed by fs2ram at
each shutdown/reboot before the file system is unmounted. The pre-unmount
script must print a post-mount script on standard output, which is saved and
then run at boot time after fs2ram mounts the corresponding file system.
.
This package provides two pre-unmount scripts designed to preserve folder
structure and file permissions across reboots: this is needed to allow
hierarchies such as /var/cache or /var/log to be mounted as tmpfs.
--- fs2ram.old/debian/templates 2012-07-02 01:53:16.376137159 -0600 +++ fs2ram/debian/templates 2012-07-07 08:35:29.704159210 -0600 @@ -1,9 +1,18 @@ +# 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: fs2ram/main_install_type Type: select __Choices: Content-preserving, Structure-preserving, Unconfigured Default: Content-preserving -_Description: fs2ram configuration +_Description: Configuration for fs2ram: Please select the fs2ram configuration that best meets your needs. . * Content-preserving: /var/tmp, /var/cache, and /var/log will be in @@ -18,14 +27,15 @@ Template: fs2ram/rcs_enforce_ramtmp_configuration Type: boolean Default: true -_Description: Make /tmp into RAM file systems? - Please choose whether /tmp should be converted into tmpfs - mountpoints. This is not the default for fresh installs of Debian. +_Description: Turn /tmp into a RAM file system? + Please choose whether /tmp should be converted into a tmpfs + mount point. This is not the default for freshly installed + systems. Template: fs2ram/rcs_enforce_ramlock_configuration Type: boolean Default: true -_Description: Make /var/lock into RAM file systems? - Please choose whether /var/lock should be converted into tmpfs - mountpoints. This is the default for fresh installs of Debian. +_Description: Turn /var/lock into a RAM file system? + Please choose whether /var/lock should be converted into a tmpfs + mount point. This is the default for freshly installed systems. --- fs2ram.old/debian/control 2012-07-02 01:53:16.376137159 -0600 +++ fs2ram/debian/control 2012-07-03 07:02:52.551941453 -0600 @@ -18,5 +18,4 @@ . This package provides two pre-unmount scripts designed to preserve folder structure and file permissions across reboots: this is needed to allow - hierarchies suc as /var/cache or /var/log to be mounted as tmpfs. - + hierarchies such as /var/cache or /var/log to be mounted as tmpfs.
Attachment:
signature.asc
Description: Digital signature