My worry there is that listchanges.conf is owned by another package, though it doesn't appear to be a conffile. Does that mean that you're allowed to write to it in your maintainer scripts? I'm not sure.
Really, listchanges.conf should be listchanges.d, which each [foo] section becoming a file listchanges.d/foo.
That's a good idea to solve the problem with the LISTCHANGES_PROFILE variable and defaults if it's blank. It hadn't occurred to me.
Thanks for the quick fixes, - Marc
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
