commit 25545e60e16c8e3dba8ef90fa4621173d44ffea7 (HEAD -> gnome-3-12)
Author: Michael Catanzaro <[email protected]>
Date:   Fri Aug 25 19:17:52 2017 -0500

   Prepare 3.12.14

NEWS         | 19 +++++++++++++++++++
configure.ac |  4 ++--
2 files changed, 21 insertions(+), 2 deletions(-)

commit cd71a62d2a106b608b4bc8c5c037e79c45f9721c
Author: Michael Catanzaro <[email protected]>
Date:   Wed Aug 16 15:03:34 2017 -0500

   tests: dist certificate-authority.pem

tests/certificates/Makefile.am | 1 +
1 file changed, 1 insertion(+)

commit 80192f7f9bd96b5f9950303544bb6dfb9652519e
Author: Debarshi Ray <[email protected]>
Date:   Mon Mar 20 19:51:42 2017 +0100

   tests: Retain the PEM formatted root certificate

   In the subsequent commit, we will use GIO's GnuTLS backend to verify
   the chain of TLS certificates instead of Gcr. This means that a
   GckModule can no longer be used to feed our mock root certificates via
   a PKCS#11 module. Instead we will have to create a mock GTlsDatabase,
   and that needs the PEM formatted root certificate.

   We will continue using the GckModule for pinned certificates.

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

tests/certificates/Makefile.am               |   3 +--
tests/certificates/certificate-authority.cer | Bin 466 -> 466 bytes
tests/certificates/certificate-authority.pem |  12 ++++++++++++
tests/certificates/server-cert.cer           | Bin 448 -> 448 bytes
4 files changed, 13 insertions(+), 2 deletions(-)

commit 0675aab11415799700033fe7fd0777f50dc9fe16 (origin/gnome-3-12)
Author: Michael Catanzaro <[email protected]>
Date:   Wed Aug 16 18:11:49 2017 -0500

   Fix theme installation during distcheck

   Looks like this package has not passed distcheck in at least the past
   five years. OK then....

data/themes/Makefile.am | 33 +--------------------------------
1 file changed, 1 insertion(+), 32 deletions(-)

commit 1040646704e72a5c2da994d9dbdf9d216146faac
Author: Michael Catanzaro <[email protected]>
Date:   Wed Aug 16 13:12:33 2017 -0500

   Stop using -Werror

   It will never build if -Werror is passed by default, and nobody has
   fixed five years worth of compiler warnings.

configure.ac | 9 ---------
1 file changed, 9 deletions(-)

commit 43685775f65415334f61f2a9800854d0cee42865
Author: Debarshi Ray <[email protected]>
Date:   Wed Jul 26 15:26:32 2017 +0200

   telepathy-account-widgets: Update submodule

   Adds a missing chain-up in constructed, drops Facebook XMPP and adds
   skypeweb.

telepathy-account-widgets | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

commit 33bd6ee7a5be50bd042b74d37df6ab63f7c5af9d
Author: Fabrice Bellet <[email protected]>
Date:   Tue Dec 20 20:59:58 2016 +0100

   rounded-effect: make the rounded rectangle coarser

   The effective size of the preview window allows to significantly
   increase the angle step used to compute the rounded rectangle cogl
   shape, without visual impact. This also gives up a nice speed
   improvement, as internal cogl-path functions are rather expensive
   with a fine grained angle step (parameter unit is degrees).

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

src/empathy-rounded-texture.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)

commit a5cd3088c9548839ca58dd628e470a319547e05a
Author: Michael Catanzaro <[email protected]>
Date:   Tue Aug 30 12:26:18 2016 -0500

   Replace crap desktop notifications with crap GTK+ dialogs

   mcatanzaro:  I am going to remove the "display events in notification
   area" crap
   mcatanzaro:  Because the notification goes away and then you can never
   see it again or join the room
   mcatanzaro:  It's BS
   mcatanzaro:  If you toggle it off, you get a GtkDialog from nowhere
   instead, which is also crap but better!

   To be clear: it's totally unacceptable to display GtkDialogs without a
   parent window, and this patch makes us do that by default. But I don't
   plan to spend more effort on this myself, and it's a lot better than
   giving users a two second window to rush to click the buttons in the
   notification before it disappears. Better hope no other notification
   gets sent during that time, and you have fast reflexes, else
   you're not
   gonna be able to join the chat you're invited to....

data/org.gnome.Empathy.gschema.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

commit 60e6466726841ce94f9eabb07b93c441cbf3d764
Author: Lionel Landwerlin <[email protected]>
Date:   Mon Nov 30 15:19:39 2015 +0000

   call: port to clutter-gst 3.0

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

configure.ac              |  2 +-
src/empathy-call-window.c | 28 ++++++++++++++--------------
2 files changed, 15 insertions(+), 15 deletions(-)

commit 581be902720691c4b134526afdb32c4b8a61090a
Author: Michael Catanzaro <[email protected]>
Date:   Thu Jul 21 20:28:51 2016 -0500

   Honor autoaway setting even in GNOME Shell

   GNOME stopped handling presence ages ago... I think it was GNOME 3.8.

   Based on work by Christoph Lenggenhager.

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

src/empathy.c | 28 ++++++++++++----------------
1 file changed, 12 insertions(+), 16 deletions(-)

commit decddabbfd758a83e454e2e038ba287714cdb970
Author: Michael Catanzaro <[email protected]>
Date:   Thu Jul 21 20:13:45 2016 -0500

   Always notify presence manager on exit

   Even when running in GNOME Shell. It's been years since this made
   sense.

src/empathy.c | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)

commit 1e232c9a7330e5d048b89619deffa78b5db87fae
Author: Debarshi Ray <[email protected]>
Date:   Thu Mar 16 19:50:40 2017 +0100

   Remove the GnuTLS dependency

   GIO, backed by glib-networking, has everything that we need.

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

configure.ac               |  2 --
libempathy/empathy-utils.c | 35 -----------------------------------
libempathy/empathy-utils.h |  3 ---
src/empathy-auth-client.c  |  2 --
tests/empathy-tls-test.c   |  2 --
5 files changed, 44 deletions(-)

commit d4d8e7e854eecc6aae121fe497f131207c29c672
Author: Debarshi Ray <[email protected]>
Date:   Wed Mar 15 20:24:08 2017 +0100

   tls-verifier: Use GIO to verify the chain of TLS certificates

   Gcr has its own hand rolled code to complete the certificate chain and
   validate it, which predates the equivalent functionality in GIO. These
   days, GIO's GnuTLS backend is a better option because it defers to
   GnuTLS to do the right thing. It benefits automatically from any
   improvements made to GnuTLS itself.

   However, GIO doesn't support certificate pinning. Gcr continues to
   provide that feature.

   Note:

   (a) We don't set "certificate-hostname" when we encounter
   TP_TLS_CERTIFICATE_REJECT_REASON_HOSTNAME_MISMATCH. The resulting loss
   of verbosity in EmpathyTLSDialog is balanced by no longer relying on a
   specific encryption library.

   (b) glib-networking doesn't differentiate between
   GNUTLS_CERT_SIGNER_NOT_FOUND and GNUTLS_CERT_SIGNER_NOT_CA. Hence, we
   club them together as TP_TLS_CERTIFICATE_REJECT_REASON_UNTRUSTED
   and we
   no longer return TP_TLS_CERTIFICATE_REJECT_REASON_SELF_SIGNED.

   (c) Unlike Gcr, GnuTLS doesn't seem to provide a way to load a PKCS#11
   module that's built into the code, as opposed to being a shared
   object.
   This makes it hard for us to load our mock PKCS#11 module. Therefore,
   we have disabled the test case that relies on using PKCS#11 storage to
   complete the certificate chain.

   Bump required GLib version to 2.48. We really do need 2.48 because we
   rely on the improvements to GIO's GnuTLS backend.

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

configure.ac                      |   6 +-
libempathy/empathy-tls-verifier.c | 419
++++++++++++++++++--------------------
libempathy/empathy-tls-verifier.h |   3 +
tests/empathy-tls-test.c          |  35 +++-
4 files changed, 232 insertions(+), 231 deletions(-)

commit d3a04cdccc750b4af180fab5be2ec0ffb251c18d
Author: Michael Catanzaro <[email protected]>
Date:   Fri Jan 27 13:12:05 2017 -0600

   Fix default encoding property

libempathy-gtk/empathy-log-window.c  | 4 ++--
libempathy-gtk/empathy-theme-adium.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)

commit 01f753fa5768f854695f57e1e920fe2d342c21e0
Author: György Balló <[email protected]>
Date:   Wed Jan 25 19:56:00 2017 -0600

   Incomplete port to WebKit2

   The work is mostly done by Carlos Garcia, rebase by György. It's got
   FIXMEs and serious bugs, but it's better than no Empathy at all once
   WebKit1 is removed from Fedora in two short months.

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

configure.ac                          |   4 +-
libempathy-gtk/empathy-chat.c         |  61 ++++++---
libempathy-gtk/empathy-log-window.c   | 180 +++++++++++++++----------
libempathy-gtk/empathy-search-bar.c   |  73 ++++------
libempathy-gtk/empathy-theme-adium.c  | 246
++++++++++++++--------------------
libempathy-gtk/empathy-theme-adium.h  |  23 ++--
libempathy-gtk/empathy-webkit-utils.c | 227
++++++++++++-------------------
libempathy-gtk/empathy-webkit-utils.h |  17 ++-
src/empathy-chat-window.c             |  17 ++-
src/empathy-preferences.c             |  14 +-
10 files changed, 407 insertions(+), 455 deletions(-)

commit ee743e56e09a2af03b5644f8aa4690a8e5b16b94
Author: Fabio Tomat <[email protected]>
Date:   Sun Apr 23 14:29:09 2017 +0000

   Update Friulian translation

po/fur.po | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

commit 4bba6354fb20ef5f7ff4728fe526ebc30039ed92
Author: Piotr Drąg <[email protected]>
Date:   Mon Mar 27 21:05:18 2017 +0200

   Update Polish translation

po/pl.po | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)

commit 05d86a3f6e599207918a8d5b871bc3a89660dbab
Author: Debarshi Ray <[email protected]>
Date:   Mon Mar 20 19:31:39 2017 +0100

   tests: Actually test that hostnames of pinned certificates are
   verified

   This test case is about ensuring that a pinned certificate won't be
   validated if the wrong hostname is used.

   If we don't add the pinned certificate to our database, then
   checks for
   pinning are going to fail regardless of the hostname being used. The
   correct certificate-hostname pair needs to be in the database
   to ensure
   that the hostnames are being matched as advertised.

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

tests/empathy-tls-test.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

commit 5cdb6ee13b5c82283c93477af29eca2dd2ee28eb
Author: Debarshi Ray <[email protected]>
Date:   Mon Mar 20 19:20:11 2017 +0100

   tests: Fix comment

   The existing comment was mistakenly copied from
   test_certificate_verify_success_with_full_chain.

   This test case is about a certificate that has been pinned against a
   specific peer. The mock TLS connection doesn't have the full chain,
   but just the leaf-level certificate that has been pinned.

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

tests/empathy-tls-test.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

commit adf7b886fae28a604a59c1032dc5bae2881ce477
Author: Debarshi Ray <[email protected]>
Date:   Wed Mar 15 20:23:43 2017 +0100

   tls-verifier: Handle GNUTLS_CERT_REVOKED

   ... by mapping it to TP_TLS_CERTIFICATE_REJECT_REASON_REVOKED.

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

libempathy/empathy-tls-verifier.c | 2 ++
1 file changed, 2 insertions(+)

commit ee8023763edb37e8d694121a1ee61a9476b3229b
Author: Fabio Tomat <[email protected]>
Date:   Sun Mar 19 21:39:03 2017 +0000

   Update Friulian translation

po/fur.po | 82
+++++++++++++++++++++++++++++++--------------------------------
1 file changed, 40 insertions(+), 42 deletions(-)

commit 0416c6c049085160424e966e9d76693aa78f0888
Author: Debarshi Ray <[email protected]>
Date:   Mon Mar 13 18:52:58 2017 +0100

   remove released flag

configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

commit 90ce49a9c37d01d9861476cc9c5b03e9287d0760 (tag: EMPATHY_3_12_13)

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.