Hello, a very important information: After a long discussion with chris_c and chris_n, it seems I made a mistake and have found a hidden problem. * the hidden problem (that was hidden for me, and probably for most of you. both chris where aware) : in 3.4 and 3.6, when a patch with a updatedatabase was backported, it was backported with another number. It means that when you upgrade from 3.2 to 3.4 then 3.6, you get some error message about duplicate key of things like that. I've checked, those SQL errors are all harmless (and chris already had checked in fact). * my mistake: as I thought patches for 3.6 should have a 3.6 number and patches for master (future 3.8) should have a 3.7 number, i've pushed 3 patches with an updatedatabase numbered 3.6.x That was a bad idea, and I'll have to modify those updatedatabase, i'll do it now. So, anyone running master should get a "free" updatedatabase in the next hours. By free I mean the 3 DB revs that will be applied have already been applied, that will just be a number change. So, 1-take care, 2- don't worry. Also note that this problem will be solved once the new database mechanism will be pushed, as it will be non-linear, so the numbering won't refer to a release number anymore. HTH -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08