© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I believe that this should go into the list of sanity-checks we do: check for the timezone, compare, stop with an error message if any differ. The fix for this is to use the --set-vars option to set the time_zone variable for the connections. But in the general case, the DBA should decide whether that's the right fix.