On Tue, 2013-02-12 at 06:17 -0500, Thomas Simmons wrote: > Forwarding this to the technical list for assistance. If it's not possible > to upgrade from 4.0.0, is there any idea when an "upgrade strategy" will be > available?
So, what happened was this: We got 4.0.3 ready, thinking that the upgrade strategy was: samba_upgradeprovision samba-tool dbcheck [--fix [--yes]] The problem is, that in https://bugzilla.samba.org/show_bug.cgi?id=9267 this was contra-indicated - the user lost specific ACLs that they had set. We need to work out why that happened, and how to fix that. Sadly it all happened too late, so we got a bit stuck without an upgrade plan. Running the new code is fine, but ACLs won't be quite right until we fix the DB. It should even be possible to drop setting 'acl:search=false', but as we don't know for sure I really need to dig into this. This isn't helped by the fact that the samba_upgradeprovision tool is both amazing in what it does, and amazing in it's internal complexity. This is a tool that can work out (pretty well) what parts of the database were created by our provision tool, and what parts were altered later, and fix errors in that initial provisioning, given new defaults. Additional complexity also comes from the fact that 'samba-tool dbcheck' will alter the DB, and so make it potentially harder for samba_upgradeprovision to run correctly later. All in all, this is not how we would like it to be, but we hope we can work this all out soon. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
