hi! On Wed, Jan 06, 2010 at 11:17:49AM +0100, Thijs Kinkhorst wrote: > > Afaics I'm using dbconfig-common as documented, so this issue should imho > > be handled there. > > One thing you're not doing is "Recommends: mysql-client". But I doubt that > would have helped here.
a Recommends on the database server might be helpful, but even this would
not guarantee a fix in all install cases, so something else would still need
to be done inside of dbconfig-common.
> > I'll leave it to Sean to decide, how dbconfig-common should behave in a
> > non-interactive mode (which I guess was used in the piuparts test)
>
> If someone installs a dbconfig-common-using package in non-interactive mode
> and doesn't supply any explicit preseeding, then I think we can assume that
> they want to answer "no" to "Configure database for ${pkg} with
> dbconfig-common?"
i'd say that it should still try, but in the case that it fails to install
it should be able to handle the failure and gracefully ignore the failure.
i'm preparing an upload with other various fixes at the moment, if i have
time to look into this issue i'll make a patch for it. if i run out of
time i'll just include the patch you provided as a stop-gap for the
time being.
sean
signature.asc
Description: Digital signature
