Hey Frederic, > I need to backport the tango-db package which use dbconfig-common infrastructure. > this allow to upgrade the tango-db mysql tables during the upgrade process > > the process use files named with the version of the transition. > If the database need to be upgrade with the package > 8.1.2+dfsg-1 this is the name of the first package which provide the transition. > now the version is 8.1.2c+dfsg-3 > > for now I have these files in my package > > picca@mordor:~/Debian/main/tango/tango/debian/mysql$ ls > 7.2.0~rc1+dfsg-1 7.2.6+dfsg-1 8.0.5+dfsg-1 8.1.2+dfsg-1 As I understand it the choice of naming those schemas like the first Debian release version is wrong. You want to name them like the upstream version, e.g. 7.2.0~rc1 or 7.2.6. Any dfsg tag or revision would not be required, unless anything in the schema changes there. All dbconfig-common does is to compare old-version with the new one: A old version = 1.7.0-1 B old schema = 1.7.0 C new version = 1.7.1-1 D new schema = 1.7.1 So the database gets updated when a schema change occured between A and C, and because of D > A, but D <= C the update will be applied. The fix should be to change the filenames in the original packaging, but be aware that if you change it for backporting, a switch to the upstream package will apply a schema update twice. Example: 1.7.0 < 1.7.0-1 < 1.7.1-1 ^^^^ ^^^^ same schema Cheers Markus -- Markus Frosch markus@lazyfrosch.de http://www.lazyfrosch.de
Attachment:
signature.asc
Description: This is a digitally signed message part