GitLab

The option is still meant to be used in Flatpak only, to prefix
the D-Bus services with certain prefix (usually the same as the Flatpak
application ID), thus the services do not clash with those installed
in the host system. It fixes many issues in evolution-dbus-session.

Related to evolution#165

Closes https://bugzilla.gnome.org/show_bug.cgi?id=651197

When a filter rule contains action to copy message, this copy cannot be
batched as message move, because the copy doesn't stop further processing,
thus the to-be-copied message can be further modified or even removed,
thus the copy would not be correct.

This had been reported downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1650665

Missed filter's search code, which didn't know about the new
compare-date and make-time functions, causing errors int he UI
when filtering.

Related to GNOME/evolution-data-server#5
and GNOME/evolution#245

When a component/contact is loaded from the server when it's not part
of the local cache (which can happen for example with meeting invitations),
then the fetched object was stored without the href in the local cache,
which made it impossible to edit the object later (it resulted
in an "Invalid Object" error).

There could happen a deadlock when two threads change for example
message info flags, where one threads holds message info's summary lock
and is waiting for the info's property lock, which the other thread
hold's info's property lock and is waiting for the summary lock.
It's safer to hold summary lock before acquiring the message info's
lock when anything will be changed in the message info, which didn't
happen here.

This had been reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1649373

Closes GNOME/evolution-data-server#56

Closes GNOME/evolution-data-server#55

Handle also cases where the fdlist is only a return value, not an input
argument.

Related to GNOME/evolution#169

This is required to have properly propagated calls like OpenFile,
which use it.

Related to GNOME/evolution#169

...and address the newly shown warnings as well.

The test had been mostly working, except cases when the delivery
of a D-Bus property change signal had been delayed. Then the value
on the client side was not the same as the value on the server side.
There's a very similar test for EBookClient, which does slightly more
things, which gives D-Bus enough time to deliver the property change
to the client, thus this change adds the component removal to address it.

Closes GNOME/evolution-data-server#54

Thus it can be used to influence where the needed libraries are
looked for from the outside.

The only two parts using it were GDBus objects for address book and
calendar view, which could be easily transformed to use gdbus-codegen,
the same as the rest of the GDBus objects defined in src/private/.

Related to GNOME/evolution#113

Closes GNOME/evolution-data-server#52

Closes GNOME/evolution-data-server#41

Closes GNOME/evolution-data-server#51

(cherry picked from commit 37e582ad)

Similar to GNOME/evolution#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 GNOME/evolution#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 GNOME/evolution-data-server#49

Closes GNOME/evolution-data-server#50

Closes https://bugzilla.gnome.org/show_bug.cgi?id=606071

Closes GNOME/evolution-data-server#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.