On Sun, Feb 01 2009, sean finney wrote:
> hiya,
>
> On Sat, Jan 31, 2009 at 11:27:22PM +0200, Niko Tyni wrote:
>> From an installation of request-tracker3.6:
>>
>> dbconfig-common: writing config to
>> /etc/dbconfig-common/request-tracker3.6.conf
>> *** WARNING: ucf was run from a maintainer script that uses debconf, but
>> the script did not pass --debconf-ok to ucf. The maintainer
>> script should be fixed to not stop debconf before calling ucf,
>> and pass it this parameter. For now, ucf will revert to using
>> old-style, non-debconf prompting. Ugh!
>>
>> Please inform the package maintainer about this problem.
>
> ew, and now that's made it to lenny. thankfully the fix is simple and the
> existing delta between lenny and sid is pretty small...
>
> Manoj, two quick questions:
>
> - do i need to pass --debconf-ok when purging files as well?
No. Recent ucf short circuits the purge code path; however,
there is no harm in passing it in.
> - if the maintainer has called db_stop before ucf is called, and then ucf is
> called with --debconf-ok, is that a problem?
I think so. This is an issue really with debconf; once db_stop
has been called, it is currently impossible to resurrect a debconf
session, based on my (non-exhaustive) testing. Perhaps not call db_stop
until al ucf invocations are done might b the best.
manoj
--
I like your game but we have to change the rules.
Manoj Srivastava <[email protected]> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
