September 2012 - Syncevolution-issues

[Bug 54998] New: disable PHOTO syncing for specific peers

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54998 Bug #: 54998 Summary: disable PHOTO syncing for specific peers Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: high Component: SyncML AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: patrick.ohly(a)gmx.de CC: syncevolution-issues(a)syncevolution.org Some peers, in particular older phones, have problems when being sent lots of photo data. It may be more useful to exclude photo data altogether for such peers. See "[SyncEvolution] Sync failure due to large addressbook entires." A possible solution would be: - introduce a new session variable in the <sessioninitscript> - set that variable in remote rules (see stripUID for an example) or based on a new config property (see preventSlowSync) - extend the <outgoingscript> for contacts such that it unsets the PHOTO property before encoding a contact for the peer if that session variable is set - see VCARD_OUTGOING_PHOTO_INLINING_SCRIPT That should take care of sending data to the phone. Ensuring that the photo doesn't get lost when receiving an update is harder. Something might be possible with a custom <mergescript>, but I am not sure whether it really gets invoked during a normal import. Alternatively, dynamically updating the field attributes after parsing the peer's CtCap would be a more elegant solution, because it would use existing libsynthesis mechanisms: - don't send properties to a peer which the peer doesn't support (strip PHOTO when sending) - preserve local properties not supported by the peer (preserve PHOTO) However, implementing that will require considerable changes in libsynthesis: - expose the field list attributes to scripts - ensure that a script is called after parsing CtCap and before using the field list (perhaps <datastoreinitscript> is suitable) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

2 years, 9 months

1
2
0 / 0

[Bug 54906] New: support IPv6 on syncevolution.org

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54906 Bug #: 54906 Summary: support IPv6 on syncevolution.org Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other URL: https://bugs.meego.com/show_bug.cgi?id=25562 OS/Version: All Status: ASSIGNED Severity: enhancement Priority: low Component: SyncEvolution AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: patrick.ohly(a)gmx.de CC: syncevolution-issues(a)syncevolution.org As pointed out in https://bugs.meego.com/show_bug.cgi?id=25562 the initial IPv6 setup on syncevolution.org did not work (some kind of SSL certificate issue when used over IPv6). Therefore the IPv6 address of syncevolution.org was removed from DNS again, as a short term workaround (not a pressing issue, though, so short term can become pretty long). Need to figure out what the problem was and fix it properly. It would be interesting to know whether https://01.org has the same problem - it uses a similar setup. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

7 years, 8 months

1
1
0 / 0

[Bug 55238] New: Timezone for DUE in allday events unhandled in calendar.xml script

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=55238 Priority: medium Bug ID: 55238 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: Timezone for DUE in allday events unhandled in calendar.xml script Severity: normal Classification: Unclassified OS: All Reporter: peterjan(a)poczta.onet.pl Hardware: Other Status: NEW Version: unspecified Component: SyncEvolution Product: SyncEvolution Timezone for DUE in allday events is unhandled in calendar.xml script ( src/syncevo/configs/scripting/11calendar.xml ) > if (ITEMDATATYPE()=="vCalendar10" && ALLDAYCOUNT(DUE,DUE,TRUE,TRUE)>0) { > DUE = DATEONLY(DUE); > } should probably have: > DUE = CONVERTTOUSERZONE(DUE); before DUE = DATEONLY(DUE); Current code leads to wrong due date of a todo task (at least for me and GMT+2 on both the phone and the pc): > [2012-09-23 12:21:22.795] - Field: DUE = 2012-10-02T22:00:00Z (TZ: UTC) (timestamp) > [2012-09-23 12:21:22.795] - Expression result: 2012-10-02T22:00:00Z (TZ: UTC) (timestamp) > [2012-09-23 12:21:22.795] - Parameter #1 (by value) = 2012-10-02T22:00:00Z (TZ: UTC) (timestamp) > [2012-09-23 12:21:22.795] - DATEONLY() function result = 2012-10-02 (floating) (timestamp) > [2012-09-23 12:21:22.795] - Assigned expression result = 2012-10-02 (floating) (timestamp) BTW - thank you for your effort on the project. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

8 years, 10 months

1
3
0 / 0

[Bug 25562] New: syncevolution.org does not load over IPv6

by bugzilla＠meego.com

https://bugs.meego.com/show_bug.cgi?id=25562 Summary: syncevolution.org does not load over IPv6 Classification: MeeGo Projects Product: SyncEvolution Platform: --- Version: unspecified Platform: Common Architecture: --- Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: niels_ole(a)salscheider-online.de QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 When using IPv6, I can ping syncevolution.org but the page does not load -- wget stops after: wget -6 syncevolution.org --2012-07-18 11:11:55-- http://syncevolution.org/ Resolving syncevolution.org (syncevolution.org)... 2001:19d0:3:5::106 Connecting to syncevolution.org (syncevolution.org)|2001:19d0:3:5::106|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://syncevolution.org/ [following] --2012-07-18 11:11:55-- https://syncevolution.org/ Connecting to syncevolution.org (syncevolution.org)|2001:19d0:3:5::106|:443... connected. Using IPv4 works fine, though. This might be a bug in the web server (configuration). -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: NEW Who: niels_ole(a)salscheider-online.de Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=25562 -- 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.

8 years, 10 months

1
6
0 / 0

[Bug 25594] New: move upstream bug tracking to bugs.freedesktop.org

by bugzilla＠meego.com

https://bugs.meego.com/show_bug.cgi?id=25594 Summary: move upstream bug tracking to bugs.freedesktop.org Classification: MeeGo Projects Product: SyncEvolution Platform: --- Version: unspecified Platform: Common Architecture: --- Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: patrick.ohly(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 SyncEvolution upstream now uses the http://bugs.freedesktop.org (b.fdo) bug tracker. All bugs from meego.com were imported into b.fdo and will get a "see also" link to the copy. All bugs which were not closed already will be set to "resolved/duplicate" of this bug here. This is a workaround for the lack of a "resolved/migrated" in bugs.meego.com. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: NEW Who: patrick.ohly(a)intel.com Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=25594 -- 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.

8 years, 10 months

1
1
0 / 0

[Bug 25596] New: syncevolution fails for users without an active (kde) session

by bugzilla＠meego.com

https://bugs.meego.com/show_bug.cgi?id=25596 Summary: syncevolution fails for users without an active (kde) session Classification: MeeGo Projects Product: SyncEvolution Platform: --- Version: unspecified Platform: Common Architecture: --- Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: niels_ole(a)salscheider-online.de QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 Running syncevolution fails for a user without an active (kde) session: It only outputs "sock_file=/.../socket-hostname/kdeinit4__0". gdb outputs the following: Starting program: /usr/bin/syncevolution Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3200.4-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Program received signal SIGABRT, Aborted. 0x00007ffff5323f55 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff5323f55 in raise () from /lib64/libc.so.6 #1 0x00007ffff53253c7 in abort () from /lib64/libc.so.6 #2 0x00007ffff207da1f in qt_message_output(QtMsgType, char const*) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007ffff1ad930c in QDebug::~QDebug() () from /usr/lib64/../lib64/libkdeui.so.5 #4 0x00007ffff1bc5a6b in KApplicationPrivate::init(bool) () from /usr/lib64/../lib64/libkdeui.so.5 #5 0x00007ffff1bc6ad8 in KApplication::KApplication(bool) () from /usr/lib64/../lib64/libkdeui.so.5 #6 0x00007fffe9691c9c in SyncEvo::KDEInitMainSlot(char const*) () from /usr/lib64/syncevolution/backends/platformkde.so #7 0x00007ffff6dfc740 in boost::signals2::detail::signal1_impl<void, char const*, boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (char const*)>, boost::function<void (boost::signals2::connection const&, char const*)>, boost::signals2::mutex>::operator()(char const*) () from /usr/lib64/libsyncevolution.so.0 #8 0x00007ffff6ded0cd in SyncEvo::SyncContext::initMain(char const*) () from /usr/lib64/libsyncevolution.so.0 #9 0x00000000004135c8 in main () (gdb) quit A debugging session is active. This is an issue for source based distributions that build a new version of syncevolution when an old version is installed. The patching of the README.RST fails in line 2: perl -e '$syncfound=0; $sourcefound=0; $res=0;' \ -e 'sub run { $cmd = shift; $buffer = `env LD_LIBRARY_PATH=src/syncevo/.libs:src/gdbus/.libs:src/gdbusxx/.libs:src/build-synthesis/src/.libs:$ENV{LD_LIBRARY_PATH} $cmd`; die if $?; return $buffer; }' \ -e 'while (<>) {' \ -e 's/^:Version: .*/:Version: 1.2.99.3/;' \ -e 's/:Date: .*/":Date: " . `date +%Y-%m-%d`/e;' \ -e 'if (s;(<< see "syncevolution --sync-property ." >>\n);run("src/syncevolution --daemon=no --sync-property ?") || $1;e) { $syncfound=1; }' \ -e 'if (s;(<< see "syncevolution --source-property ." >>\n);run("src/syncevolution --daemon=no --source-property ?") || $1;e) { $sourcefound=1; }' \ -e 'print;' \ -e '}' \ -e 'die "<<sync-property>> tag not in README.rst?!" unless $syncfound;' \ -e 'die "<<source-property>> tag not in README.rst?!" unless $sourcefound;' \ -e 'exit $res;' \ README.rst >README.patched.rst Died at -e line 2, <> line 674. This problem does not occur when syncevolution is not installed when building it. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: NEW Who: niels_ole(a)salscheider-online.de Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=25596 -- 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.

8 years, 10 months

1
4
0 / 0

[Bug 54547] New: addressbook: backend addressbook is ambiguous, avoid the alias and pick a specific backend instead directly

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54547 Bug #: 54547 Summary: addressbook: backend addressbook is ambiguous, avoid the alias and pick a specific backend instead directly Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: minor Priority: medium Component: SyncEvolution AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: ildar(a)users.sourceforge.net CC: syncevolution-issues(a)syncevolution.org Compile-time checks aren't exhaustive. Building EDS backend together with sqlite finishes OK, but produces unusable installation. syncevolution's complains are in Summary. The least can be made for this is having a table (at Wiki or Doc) showing conflicting backends. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

8 years, 10 months

1
2
0 / 0

[Bug 53813] libsynthesis: separate .tar.gz source code releases

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=53813 Peter <pbrobinson(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Platform| |All OS/Version| |All -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

8 years, 11 months

1
0
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Syncevolution-issues September 2012