[Openstack-devel] Bug#704949: Bug#704949: cinder: [debconf_rewrite] Debconf templates and debian/control review proposal
zigo at debian.org
Mon Apr 8 05:37:44 UTC 2013
I was expecting to get in touch with you sooner or later, for a full
review, not only about these templates, but about the system with
Debconf in general for Openstack. Seems you beat me to it, Christian.
I'm convince that you will be able to give valuable advices here, and
probably some help.
We have the following components in Openstack:
cinder - block storage system
glance - cloud image service
keystone - identity (eg: auth) service
nova - compute service (starting virtual machines)
heat - auto-scaling service (eg: asks nova to start instances when the
load gets higher)
quantum - network service
ceilometer - metering service (eg: counts resource usage for billing)
All of the above packages need to:
- Register their API components in the Keystone service catalog
(concerned packages: glance-api, cinder-api, nova-api, heat-api,
quantum-server and keystone).
- Configure a database through dbconfig-common (concerned packages:
cinder-common, glance-common, keystone, nova-common, heat-common,
quantum-common and ceilometer-common).
We also have:
horizon - a web GUI for Openstack
but that one has different Debconf templates, and shall be managed
So, in all of the above packages, we have a huge redundancy in
templates. I thought that best would be to have a system to avoid this
redundancy, like having a package holding (most of) the templates, and
we would do dynamic replacements of variables. This way, translations
would need to happen only once, which would be a very good thing.
But I'm really not sure how to do that. Do you know what my options are?
How to implement something like this? Could you point at a set of
package which has such kind of implementation already? Please don't
point at dbconfig-common, it is quite complicated, and its
implementation is wrong (eg: it can't be pre-seeded like normal
packages), and very complicated to understand (I've dug into it, and
it's quite hard to understand).
Also, note that all packages above are currently in Debian experimental
due to the freeze. Only Cinder isn't, because it's not in testing
anyway, so it's not a problem to have it in SID.
Last, of course, I think that only until the above is addressed, a
translation effort should start. Do you agree?
On 04/08/2013 12:19 PM, Christian Perrier wrote:
> Package: cinder
> Version: N/A
> Severity: normal
> Dear Debian maintainer,
> I just noticed new or modified debconf templates appearing for this
> I would like to suggest you to consider calling for debconf templates
> review AND translation updates when you introduce new debconf
> templates or modify the existing templates in a package or, if you
> prefer, to send a call for translations after uploading the first
> version that introduces new templates or templates changes.
> If you're interested in suggestions for doing this, you can find some
> at the end of this bug report.
> The debian-l10n-english team will now start a review, on our own
> initiative. It will be conducted through this bug report.
> Suggestions for future debconf templates review
> 1) Getting debconf templates reviewed
> The Debian i18n contributors have developed a set of suggestions for
> the writing style of debconf templates, to give them an overall
> consistency all around Debian. These writing style suggestions are
> explained in the Developers Reference. Lintian also warns about common
> writing style concerns.
> Maintainers are welcome when they ask for a review of debconf templates
> and/or packages descriptions on debian-l10n-english at lists.debian.org.
> It is of course not needed to wait for someone (such as me right me)
> proposing you such a review.
> In such situations (whether the review is requested by the maintainer
> or proposed by someone else), someone from the debian-l10n-english
> team will pick up the review to do, handle it, and finally send you a
> bug report with the suggested templates. If you want, you can ask for
> being CC'ed to the various discussions when the templates are
> 2) Call for new translations
> As soon as the templates have been reviewed, you can ask Debian
> translators for new translations:
> Just go to your package's build tree and use:
> $ podebconf-report-po --call
> This will propose you a generic mail which is to be sent to
> debian-i18n at lists.debian.org and call for new translations.
> This utility will mention existing translations to avoid duplicate
> It will also attach the needed material to this mail.
> Please also think about giving a deadline to translators. We like
> 3) Always call for translation updates before uploading
> (of course only when you change the debconf templates!)
> If your package already includes debconf translations (ie *.po files
> in debian/po), please consider calling for translation updates if you
> happen to change something in the templates...or just in case when you
> release a new version.
> This is done with the following command:
> $ podebconf-report-po
> This will build private mails to translators (ie people listed in
> "Last-Translator" in the PO files) for translations that are
> incomplete. These mails will included the needed PO file for each
> -- System Information:
> Debian Release: 7.0
> APT prefers unstable
> APT policy: (500, 'unstable'), (101, 'experimental')
> Architecture: i386 (i686)
> Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
> Openstack-devel mailing list
> Openstack-devel at lists.alioth.debian.org
More information about the Openstack-devel