upgradeprovision alpha17 to alpha18: dbcheck errors

[Matthieu Patou]

Hi
> Now we just need to figure out the right way to explain this to our
> users.
>
> Matthieu,
Sorry for the late answer
> With the provision-time markers you made in the DB,
Well I don't think there is really a provision time marker, there is 
somekind of information in @PROVISION but they are more about usn 
ranges, there is also something in oEMInformation but I can't say that's 
highly reliable.

The best whould be to start to use 
CN=ForestUpdates,CN=Configuration,DC=domain,DC=tld

We could create a 
CN=Samba,CN=ForestUpdates,CN=Configuration,DC=domain,DC=tld and 
CN=Samba,CN=DomainUpdates,DC=domain,DC=tld
And use the objectversion attribute to store our "samba version".

Once that's done we can teach upgrapdeprovision not to run if the 
version is already the highest.

Then it leaves us with a task to update time to time the highest version 
of samba "provision" when we do schema / structure changes or corrections.

>   is there a way we
> can check these to tell if an upgradeprovision is required?  Could we
> make dbcheck check these markers, and only then offer an
> upgradeprovision (with --full if we detect that is needed)?
>
> That way, folks would not run this if not required, and we would have
> just one 'run this on upgrade' command.
>
> Let me know what you think,
>
> Andrew Bartlett
>
Matthieu.

-- 
Matthieu Patou
Samba Team
http://samba.org