https://bugs.meego.com/show_bug.cgi?id=22691
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #2 from pohly <[email protected]> 2011-08-19 14:37:04 UTC --- commit a8effb21b8ad5d726829911046bf1c23380e2551 Author: Patrick Ohly <[email protected]> Date: Fri Aug 19 16:19:12 2011 +0200 config migration: avoid name conflicts and auto syncing of old configs (BMC #22691) When (auto-)migrating a config, it was possible that a name for the peer, say foo.old, was chosen for the renamed config although there was already such a config, for example foo.old in ~/.sync4j. Besides being confusing for users, this also led to a bug in the code where it copied from the older config with the foo.old name. Found when adding unit testing of migrating configs with auto syncing, because then the content of the migrated config mattered. The main problem fixed in this commit is the disabling of auto syncing in the old config. Done similar to ConsumerRead, by reading/writing the .ini (resp. .txt) file directly. commit d9ea929bff1965128e4ea08ef27cd1d67980609c Author: Patrick Ohly <[email protected]> Date: Fri Aug 19 15:08:14 2011 +0200 auto syncing: must check whether enabled when looking at unknown URLs (part of BMC #22691) "syncURL = insert your URL here" with "autoSync = 0" did lead to auto sync attempts although it wasn't enabled. A check for "auto syncing enabled" was missing for the "unknown transport" case. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: critical Priority: Undecided Keywords: Status: RESOLVED Who: [email protected] Assigned To: [email protected] Target Build: 1.2 Flags: Changed: Status Resolution -------- https://bugs.meego.com/show_bug.cgi?id=22691 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
