Quoting Frans Pop ([EMAIL PROTECTED]): > It is actually a side-effect of my changes to get rid of all those > annoying perl warnings. I forgot that mdadm has a debconf template while > making those changes.
Hmmm, reading this, I understand that there are situations where mdadm templates are used during the installation. If we follow the theory that drove us up to now, it means that mdadm should be added to one of the D-I "levels", similarly to xorg, samba, popcon and a few other "regular" packages that are likely to display something during some kind of installs. I would then be tempted to add mdadm to "level 4" as it will be used only in some "specific" situations. Am I right ? If I do so, I would probably need to talk with mdadm maintainers and get commit access in their workplace as adding the package to a D-I level will immediatly trigger a bunch of incoming translations.
signature.asc
Description: Digital signature
