Control: severity -1 important This looks harmless in practice. The files being modified contain SQL statements to be executed on initial installation. The fact that modifications are reverted on upgraded should not matter, since the files are never used again.
I can't find an explicit statement in policy that packages must not modify their own non-conffiles; and /usr must be writable during installation. Therefore I'm downgrading this. However, it is very bad practice. I'm surprised that dbconfig-common doesn't seem to support substitutions in the SQL install scripts. As a workaround, I would suggest making symlinks from the paths under /usr/share/dbconfig-common into (say) /var/lib/smbind, and making the postinst generate the complete install scripts there. Alternately, set the admin password by directly invoking pgsql or mysql as appropriate. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings.
signature.asc
Description: This is a digitally signed message part
