Hey Frederic, > thanks a lot for your explaination. > I will switch to the upstream version number instread of the debian package version number. > > I think that this kind of explaination should be part of the documentation. You're welcome! Maybe open a bug? ;) > Since you seems to know about dbconfig-common. > Is there something to know or to add in the pre/post scripts to be sure that a mysql-server is running during the upgrade of the package ? > The purpose is to avoid a faillure when the database and the package are upgrade in same time. Well, there might be a way to integrate this in your own postinst script, after configuring the database. *But* that you require some fiddling and usage of functions to load the configuration to check which database type is used. But keep in mind: dbconfig-common is generic, your database can be anywhere, not just localhost. All you need is the mysql-client or postgresql-client and proper remote access to setup a database on somewhere else. It would require the admin to setup the database beforehand. Internals of dbconfig-common are a bit weird sometimes, e.g. preseeding to disable the database setup will require a special setting in debconf (/internal/skip-preseed), so that the install choices (dbconfig-install) are used from debconf instead of loading default first. Cheers Markus -- Markus Frosch markus@lazyfrosch.de http://www.lazyfrosch.de
Attachment:
signature.asc
Description: This is a digitally signed message part