summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* ecal: Add camel and libedataserver to the library search path for the girwip/ecal-gir-search-pathIain Lane2019-07-251-1/+4
| | | | They are needed to build it
* Update Brazilian Portuguese translationRafael Fontenelle2019-07-221-857/+848
|
* Update Romanian translationDaniel Șerbănescu2019-07-211-374/+318
| | | | (cherry picked from commit 8b0ca6beb2878b0eaeaf95122125986dd1225f0a)
* I#112 - Credentials prompter re-asks for credentials of disabled accounts ][Milan Crha2019-07-161-0/+3
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/112
* EWebDAVDiscover can report failure on success and hide collectionsMilan Crha2019-07-161-13/+22
| | | | | | | | | | | | | | Two issues: a) when the server returns success on the given URL PROPFIND, but doesn't support /.well-known/ addresses, then the try on the /.well-known/ could overwrite the success of the given URL PROPFIND, causing return failure without setting the GError; b) when the given URL is a collection of the type the output is filtered for, the URL could be skipped from consideration and not included in the output discovered resources. Reported downstream as a gnome-calendar crash: https://bugzilla.redhat.com/show_bug.cgi?id=1287073
* I#137 - POSIX locale tests fail with ICU 64.xMilan Crha2019-07-161-0/+5
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/137
* Post-release version bumpMilan Crha2019-07-151-1/+1
|
* NEWS update for 3.33.43.33.4Milan Crha2019-07-151-0/+27
|
* M!22 - Ignore the return value of g_string_append()Дилян Палаузов2019-07-127-45/+36
| | | | | | | | | | | | | | | | | Calling “x = g_string_append (x, y)” is equivalent to “g_string (x, y)”. Or take it into account, when this leads to shorter code. Likewise for g_string_append_unichar(). Use the return value fo g_string_append(), when this makes the code sherter. In camel_content_disposition_format: skip a realloc() call. In camel-sasl-ntlm.c: skip a g_string_append_len() call. Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/22
* M!26 - Fix a possible memory leak in e_cal_client_get_component_as_string()Дилян Палаузов2019-07-111-12/+2
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/26
* M!23 - Use the return value of g_string_free(*, FALSE)Дилян Палаузов2019-07-1113-133/+40
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/23
* M!24 - e-vcard.c:read_attribute_params(): Remove unneeded if()Дилян Палаузов2019-07-101-4/+2
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/24
* M!20 - camel-search-sql-sexp.c:func_and() memory leakДилян Палаузов2019-07-081-5/+3
| | | | | | When string->len == 4, the value of string->str was leaked. Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/20
* M!19 - e-book-backend-ldap.c:address_populate(): avoid g_strdup+g_free callДилян Палаузов2019-07-081-3/+1
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/19
* M!18 - Prefer g_string_append_c() over g_string_append()Дилян Палаузов2019-07-0828-50/+49
| | | | | | Likewise for g_string_prepend_c() and g_string_prepend(). Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/18
* Update Indonesian translationKukuh Syafaat2019-07-081-993/+978
|
* Update Friulian translationFabio Tomat2019-06-301-72/+91
|
* Miscellaneous changes in ecmb_modify_object_sync()Milan Crha2019-06-281-6/+7
| | | | | The first chunk to not clash with top-block variable of the same name. The second to always return a new component instance on success.
* Fix a memory leak in e_cal_recur_generate_instances_sync()Milan Crha2019-06-281-1/+1
|
* evo-I#479 - Call mail account refresh also after going online ][Milan Crha2019-06-271-8/+6
| | | | | | | The CamelOfflineStore did not reconnect once it disconnected, only after whole CamelSession went offline and online. Related to https://gitlab.gnome.org/GNOME/evolution/issues/479
* Prefer built-in timezone component in e_cal_util_copy_timezone()Milan Crha2019-06-261-0/+9
| | | | | This way also latitude and longitude properties are provided. It also makes the copied timezone more accurate to the built-in.
* I#130 - [CamelOfflineFolder] Multiple downsync operations can run simultaneouslyMilan Crha2019-06-211-6/+65
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/130
* Updated Spanish translationDaniel Mustieles2019-06-191-55/+72
|
* [LDAP] Fix several memory leaksMilan Crha2019-06-181-4/+14
|
* I#128 - [LDAP] Claim an error when a Contact List might be saved incompleteMilan Crha2019-06-181-37/+107
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/128
* Update Dutch translationNathan Follens2019-06-181-761/+725
|
* Post-release version bumpMilan Crha2019-06-171-1/+1
|
* NEWS update for 3.33.33.33.3Milan Crha2019-06-171-0/+32
|
* evo-I#479 - Call mail account refresh also after going onlineMilan Crha2019-06-141-0/+9
| | | | Related to https://gitlab.gnome.org/GNOME/evolution/issues/479
* Remove forgotten debug print from an LDAP book backendMilan Crha2019-06-131-2/+0
|
* Correct e_cal_component_get_start_plus_duration()Milan Crha2019-06-131-1/+3
| | | | | | | The returned duration can be a _null_duration or a _bad_duration, even when the returned ICalDuration object is not NULL. Reported as part of the https://gitlab.gnome.org/GNOME/evolution/issues/484
* [IMAPx] Prefer local search in folders fully synchronized for offlineMilan Crha2019-06-121-3/+23
| | | | | When a folder is fully synchronized for offline, any search can be done with local data, without issuing SEARCH command on the server.
* Change how CamelOfflineStore goes onlineMilan Crha2019-06-111-3/+6
| | | | | | As it was, when the store went online, it just connected, even the code tried to do some things when going online, like synchronizing messages for offline use. The change allows to do what was meant to be done.
* Updated Spanish translationDaniel Mustieles2019-06-111-830/+793
|
* Update Friulian translationFabio Tomat2019-06-111-829/+790
|
* evo-I#476 - Hide "Server handles meeting invitations" for VJOURNAL/CalDAVMilan Crha2019-06-071-2/+4
| | | | Related to https://gitlab.gnome.org/GNOME/evolution/issues/476
* Memos cannot have set reminders according to RFC 5545Milan Crha2019-06-071-5/+0
|
* M!17 - Use Media Type from RFC 8551 for S/MIME creationTom Kranz2019-06-063-15/+30
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/17
* I#121 - CalDAV-advertised subscribed WebCal is not importedMilan Crha2019-06-046-19/+54
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/121
* CamelOperation can be used by other thread while in its finalize()Milan Crha2019-06-041-5/+5
| | | | Related to https://gitlab.gnome.org/GNOME/evolution/issues/471
* Update Hungarian translationBalázs Meskó2019-06-011-755/+718
|
* Add ESourceLocal::writable extension propertyMilan Crha2019-05-313-13/+129
| | | | | | This is used for calendar backends referencing custom files and it allows to tell the backend whether the calendar should be opened in writable way. It doesn't force writable open for files which cannot be open in write mode.
* I#123 - [SMTP] Ignore 8BITMIME extension for Yahoo! serversMilan Crha2019-05-303-18/+85
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/123
* I#108 - [IMAPx] Folder changes could be claimed in a wrong folder after APPENDMilan Crha2019-05-291-4/+8
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/108
* Fix typo in Ukrainian translation of Download wordIh0rko2019-05-281-2/+2
|
* M!15 - Fix typos in CMake modulesДилян Палаузов2019-05-272-6/+2
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/15
* Update overdue time immediately after the reminders' window is mappedMilan Crha2019-05-241-0/+2
| | | | | Otherwise the window shows incorrect time until the first overdue update is invoked in a timeout callback.
* Expose E-Book/Cal-BackendSExp lockMilan Crha2019-05-236-7/+101
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ECalBackendSExp usage could cause a deadlock when one thread had been starting the view, while another thread had been notifying existing views about created/modified/removed objects with the file backend, which uses its internal lock within tzcache_get_timezone() function. Exposing the Backend SExp lock into the public and locking it before starting the view helps to avoid this deadlock. Similar lock had been added to the EBookBackendSExp too. The backtrace of the two threads follows: Thread 2 (Thread 0x7f4735fab700 (LWP 11567)): 0 in syscall () at /lib64/libc.so.6 1 in g_mutex_lock_slowpath () at /lib64/libglib-2.0.so.0 2 in e_cal_backend_sexp_match_comp (sexp=0x7f47c80682a0, comp=comp@entry=0x7f47c0018920, cache=0x2c65b00) at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c 3 in match_object_sexp_to_component (value=0x7f47c0018920, data=0x7f4735faab40) at ..../src/calendar/backends/file/e-cal-backend-file.c 4 in g_list_foreach () at /lib64/libglib-2.0.so.0 5 in e_cal_backend_file_start_view (backend=0x2c65b00, query=0x7f477c01a5b0) at ..../src/calendar/backends/file/e-cal-backend-file.c 6 in calview_start_thread (data=0x7f477c01a5b0) at ..../src/calendar/libedata-cal/e-data-cal-view.c 7 in g_thread_proxy () at /lib64/libglib-2.0.so.0 8 in start_thread () at /lib64/libpthread.so.0 9 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4820dcba80 (LWP 5054)): 0 in __lll_lock_wait () at /lib64/libpthread.so.0 1 in _L_lock_941 () at /lib64/libpthread.so.0 2 in pthread_mutex_lock () at /lib64/libpthread.so.0 3 in cal_backend_file_get_cached_timezone (cache=0x2c65b00, tzid=0x2cbc790 "America/New_York") at ..../src/calendar/backends/file/e-cal-backend-file.c 4 in func_occur_in_time_range (user_data=0x2cbab10, tzid=<optimized out>) at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c 5 in func_occur_in_time_range (esexp=0x2c4e100, argc=<optimized out>, argv=<optimized out>, data=0x2cbab10) at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c 6 in e_sexp_term_eval (sexp=sexp@entry=0x2c4e100, t=0x2c4a400) at ..../src/libedataserver/e-sexp.c 7 in e_sexp_eval (sexp=0x2c4e100) at ..../src/libedataserver/e-sexp.c 8 in e_cal_backend_sexp_match_comp (sexp=0x7f47c80682a0, comp=comp@entry=0x7f47c0018f20, cache=<optimized out>) at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c 9 in e_data_cal_view_component_matches (view=view@entry=0x7f477c01a5b0, component=component@entry=0x7f47c0018f20) at ..../src/calendar/libedata-cal/e-data-cal-view.c 10 in e_cal_backend_notify_component_created (backend=<optimized out>, component=0x7f47c0018f20) at ..../src/calendar/libedata-cal/e-cal-backend.c 11 in e_cal_backend_create_objects_finish (backend=0x2c65b00, result=result@entry=0x7f47f80648a0, out_uids=out_uids@entry=0x7fff7bd8d200, error=error@entry=0x7fff7bd8d1f8) at ..../src/calendar/libedata-cal/e-cal-backend.c 12 in data_cal_complete_create_objects_cb (source_object=0x2c65b00, result=0x7f47f80648a0, user_data=0x2c31d80) at ..../src/calendar/libedata-cal/e-data-cal.c 13 in g_simple_async_result_complete () at /lib64/libgio-2.0.so.0 14 in complete_in_idle_cb () at /lib64/libgio-2.0.so.0 15 in g_idle_dispatch () at /lib64/libglib-2.0.so.0 16 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 17 in g_main_context_iterate.isra.19 () at /lib64/libglib-2.0.so.0 18 in g_main_loop_run () at /lib64/libglib-2.0.so.0 19 in main (argc=1, argv=0x7fff7bd8d518) at ..../src/calendar/libedata-cal/evolution-calendar-factory-subprocess.c
* Add workaround for D-Bus property change into get-revision testsMilan Crha2019-05-232-0/+26
| | | | | | | Even with the previous commit there still could happen some issue with D-Bus property change notifications, thus add a workaround to the related book and calendar tests, because it's not a problem on the evolution-data-server side, but somewhere deeper.
* EDataBook/EDataCal: Flush GDBus connection on backend property changeMilan Crha2019-05-232-0/+12
| | | | | This should make sure the client side will receive property changes as soon as possible.