* Steve Langasek > Ugh, this comment in the bug log tipped me off that something was wrong... > and sure enough, what do I find when looking at the package but debconf note > abuse. Christian, please use NEWS.Debian for this, that's what it was > created for -- and this is *not* what debconf notes were created for. :/
Agreed. I never saw what Debconf was used for because I don't generally bother with the low-priority ones, but reading it now it seems pretty useless. NEWS.Debian would be a much better place for it, or even nowhere at all - Quagga wasn't included in Woody so it should /certainly/ not be displayed upon initial installations of Sarge. By being rather conservative about what we use Debconf for we may still be able to present Debconf to our users as something useful (as opposed to noise / superfluous chitchat). > For the record, the lintian error is *not* wrong. Unless the postinst > sources the debconf confmodule, a config script will never be run when > installing the package using dpkg (which is still valid and expected to > work, even though apt is now the norm). Oh my, and here I thought I knew everything. I was certain that dpkg itself took care of running the config script if apt-extracttemplates or whatever hadn't already. I guess I still learn something new every day. :-) By the way, Steve, I saw you add the "sid" tag explicitly. That puzzled me as I'm fairly sure I (tried to) add the sid tag when I submitted the bug, precisely to prevent it from bothering the probably already overworked Release Managers. Did I mess it up? Perhaps I'm overlooking something, but my report seem perfectly OK to me so I have no idea what happened. -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
