https://bugs.freedesktop.org/show_bug.cgi?id=75274 Patrick Ohly <patrick.ohly(a)gmx.de&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- This is consistent with the configuration design. Have a look at the man page, in particular the glossary, and what that says about shared config properties. Let me explain: syncevolution --configure --template none backend=file database=file:///tmp/ databaseformat=text/calendar a@b s1 This command does two things: 1. it creates a source config "s1" in context "@b" 2. it creates a sync config "a" in context "@b" "--remove a@b" only removes the sync config and the per-specific properties of "s1" (like "sync") - actually in this case, no such per-specific properties were used, so only "a" gets removed and backend/database/databaseformat are all left unchanged. This is intentional. The goal is to configure sources separately from peers using the sources. When adding new peers in a context, it automatically has access to all sources configured in that context. To avoid that, use a new context or remove the context first. The latter is probably what you want: "--remove @b". This removes all properties of s1 and s2. Does that explain it? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=75274 Patrick Ohly <patrick.ohly(a)gmx.de&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- (In reply to comment #2) Yes, that's how it should work. I'm closing the issue now. Please reopen if you think something doesn't work right or needs to be changed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.