[Dbconfig-common-devel] Difficult/partial upgrade

Vincent Bernat bernat at debian.org
Wed Feb 16 22:55:44 UTC 2011


OoO La nuit ayant déjà recouvert  d'encre ce jour du mercredi 16 février
2011, vers 23:42, Sean Finney <seanius at debian.org> disait :

>> So,  I should  be able  to use  dbc_mysql_exec_file inside  the "script"
>> functionality, right?

> if you're doing that, i think you will need to actually do it in your
> postinst script directly (i.e. in an "if dpkg-compareversions ...." type
> block).

> it ought to be possible to setup dbconfig in a seperate script through
> the standard upgrade mechanism, but you'd need to spend some time
> reading what dbc_go actually does to do this, and it's probably just
> easier to do it int he postinst since everything's already set up there.

I did try without success, but I should try again. Maybe the problem was
I was testing some local variables that were not available in the scope.
-- 
printk("Cool stuff's happening!\n")
        2.4.3 linux/fs/jffs/intrep.c
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20110216/dc1ed5e4/attachment.pgp>


More information about the Dbconfig-common-devel mailing list