| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
Similar to https://gitlab.gnome.org/GNOME/evolution/issues/196
when intltool-merge is called in parallel, it could either rewrite
the ongoing attempt to build it or use an incomplete data, which
results in broken output files (.desktop, .metainfo and so on).
This change ensures the intltool-merge cache is created only once
and any other requests which would use it will wait until it's created.
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/196
|
| |
|
|
|
|
| |
Related to https://bugzilla.gnome.org/show_bug.cgi?id=658742
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When there had been two requests to download one message at the same time
the later waits for the former to finish, then it reads the message
from the local cache. The problem is that the later can use the same
stream as the former, but this stream is re-winded at the end, thus
the later attempt doesn't read anything and produces basically empty
message, instead of the proper content.
This could be sometimes observed when viewing message source of
a message which was not downloaded yet.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/49
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/50
|
| |
|
|
|
|
| |
Closes https://bugzilla.gnome.org/show_bug.cgi?id=606071
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/48
|
|
|
|
|
|
|
| |
There had been logged only headers even when the user requested to
log everything due to use of SoupRequest. The added code logs also
the response body when requested. The order of the headers and
the body can be opposite, due to libsoup internals.
|
|
|
|
|
|
|
|
|
|
|
| |
When the test creates a new ESource and saves it, then it waits
for an "source-added" signal on an ESourceRegistry instance to know
that it had been "registered" in the registry. It could sometimes
happen that the client received this signal before the factory,
which means that trying to open this ESource fails with a NOT_FOUND
error due to the factory's ESourceRegistry instance wasn't updated yet.
This change tries again for three times with a one second delay, which
should be enough to have the factory's list of known sources updated.
|
|
|
|
|
|
| |
Do not localize a config entry text which is an empty string, because
localizing empty string means getting information about the localization
itself.
|
|
|
|
|
| |
Otherwise the CamelSettings are not properly used. This had been
caused by the changes from the previous commit.
|
|
|
|
|
|
| |
Also introduce and use e_util_strcmp0(), which can avoid the most common mistake
of comparing a NULL with an empty string, which are equal after e_util_strdup_strip(),
but which caused a false property change notification.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/44
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/43
|
|
|
|
|
|
| |
sources
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/42
|
|
|
|
| |
Closes https://bugzilla.gnome.org/show_bug.cgi?id=228772
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution-data-server/issues/40
|
| |
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/40
|
|
|
|
|
| |
When an interface contains a D-Bus subtree, then proxy it too, thus
the caller has available everything the interface provides.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/38
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/36
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/35
|
|
|
|
| |
Found when looking on https://gitlab.gnome.org/GNOME/evolution-ews/issues/18
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 'parent' property of the GDataTasksTask object is exposed
through ICAL_RELATEDTO_PROPERTY, which matches the practices
of GNOME To Do and NextCloud and other ICal-based providers.
The position, however, is exposed through an X ICal property
named X-EVOLUTION-GTASKS-POSITION. This doesn't affect Evolution
in any form, but will still allow external consumers of EDS to
retrieve the position of the task. Since GData tasks themselves
aren't backed by ICal components, we have some creative freedom
to use X properties.
Updating the task position and parent requires [1], but a compile
check was added to not force EDS to bump the libgdata version.
[1] https://gitlab.gnome.org/GNOME/libgdata/merge_requests/4
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/2
|
|
|
|
|
|
| |
It had been moved to https://gitlab.com/accounts-sso/evolution-data-server-signon
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/34
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/31
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/32
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/30
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/29
|
|
|
|
| |
(cherry picked from commit 380a6f1a4a0889dd020ca39367bc99d65bfe51f0)
|
|
|
|
|
|
|
|
| |
One change, when the status stream ends an ongoing decrypt_state,
still read the stdout data as valid decrypted data, otherwise
the real output could be truncated.
Related to https://gitlab.gnome.org/GNOME/evolution-data-server/issues/3
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/29
|
| |
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/24
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
src/camel/providers/nntp/camel-nntp-store.c:2252: deref_ptr: Directly dereferencing pointer "nntp_stream"
src/camel/providers/nntp/camel-nntp-store.c:2355: check_after_deref: Null-checking "nntp_stream" suggests that it may be null, but it has already been dereferenced on all paths leading to the check.
2353|
2354| if (ret == -1) {
2355|-> if (nntp_stream)
2356| camel_nntp_stream_unlock (nntp_stream);
2357|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tool runs an isolated D-Bus session, but it also passes D-Bus
messages between the "parent" D-Bus session and the isolated
D-Bus session. It can be used for example by Flatpak applications
to run an isolated D-Bus session for recent evolution-data-server
D-Bus services, while still being able to talk to requested
D-Bus interfaces from the "parent" D-Bus session.
Its build can be enabled with -DENABLE_DBUS_SESSION_TOOL=ON CMake
command argument.
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/86
|
| |
|