After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 516294 - Mapping DB not as bidirectional as thought
Mapping DB not as bidirectional as thought
Status: RESOLVED WONTFIX
Product: conduit
Classification: Other
Component: core
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: conduit-maint@gnome.bugs
conduit-maint@gnome.bugs
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2008-02-13 20:17 UTC by John Stowers
Modified: 2018-07-11 23:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Stowers 2008-02-13 20:17:13 UTC
From Brent Gueth:

> 1. It would seem that if you setup a group to sync one direction and
> then setup another group with the same sync points in the opposite
> direction it doesn't map the sync objects properly and resends the
> data that's already there.  Ironically if you delete a sync point and
> recreate it though it "remembers" - not sure why it treats it
> differently.

Need to look into this as I am sure I test this scenario in the test suite
Comment 1 André Klapper 2018-07-11 23:18:43 UTC
Conduit is not under active development anymore, has not seen code changes for eight years, and saw its last tarball release in 2010.
Its codebase has been archived: https://gitlab.gnome.org/Archive/conduit/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.