Fix some migration-related bugs

chrome/browser/sync/profile_sync_service.h

Index: chrome/browser/sync/profile_sync_service.h
diff --git a/chrome/browser/sync/profile_sync_service.h b/chrome/browser/sync/profile_sync_service.h
index 3b37103e56a87c39c5efd842a377b2833eeaca95..b8a0f418a7f381d38287246feb874b498edda1c6 100644
--- a/chrome/browser/sync/profile_sync_service.h
+++ b/chrome/browser/sync/profile_sync_service.h
@@ -296,6 +296,9 @@ class ProfileSyncService : public browser_sync::SyncFrontend,
     return unrecoverable_error_location_;
   }
 
+  // Puts the scheduler into NORMAL mode.
+  void StartSyncingWithServer();

[tim (not reviewing), 2012/04/20 22:38:09]

We can't expose this through here. Any old code in chrome/browser should not
concern itself with, or worse,  depend on / tinker with this most fundamental of
actions in sync. Can we hand the BackendMigrator a callback instead?

[rlarocque, 2012/04/20 22:45:08]

I was struggling to find the least bad way to do this.  I never thought of using
a callback as a means of information hiding.  I'll give it a shot.  

+
   // Returns true if OnPassphraseRequired has been called for any reason.
   virtual bool IsPassphraseRequired() const;