> The package does not appear to ever use ucf to manage its configuration
> files, nor is there any suggestion in the changelog that it ever did so.
> If that's the case, why are the calls to ucf{,r} in the postrm to begin
> with?The ucf calls in postrm seem to be remnants of the moodle package code that inspired the first version of the package (moodle package was used as a template of web application with database access due to its similarities with dotlrn (and openacs) packages). They have been there almost unaltered since the first version, and nobody noticed they were useless until now... which is weird. I honestly didn't even consider if they were necessary in the first place when i fixed the bug, just assumed they were there for any good reason. So, the proposed update doesn't seem adequate, to say the least. Also, a RC bug has been filed against dotlrn this week which involves config management[1] and, ironically, the solution involves using ucf to manage a debconf generated config file, so i was thinking on fixing the two issues at the same time, if that's fine. I'm working on it right now, and plan to commit to svn and ask for upload to t-p-u before tomorrow. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688435 Kind regards, Héctor -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
