On Tuesday 06 March 2007 03:58, Steve Langasek wrote: > > Why on earth is "$RET" now "value set", where it should be "0"? > > Good question. What does 'debconf-show x11-common' spit out at this > point? I would guess that the error is in the code that _sets_ the value of this debconf question. I'm fairly certain that "value set" is what is returned in $RET by the db_set command (together with an error code of 0). In general in debconf, $RET can contain error or informational messages from debconf itself as well as real values, roughly as follows: - error code <> 0: $RET = error message - error code = 0 and function should return a real value (e.g. db_get): $RET = real value - error code =0 and function does not return a real value (e.g. db_set or db_go): $RET = informational message This means that with incorrect error handling, or by executing a db_* function without saving the value of $RET in a different variable before "reusing" $RET, you can end up with these kind of values. Hope this helps. Cheers, FJP
Attachment:
pgphFCyqAPenN.pgp
Description: PGP signature