Hello community,

here is the log from the commit of package telepathy-mission-control for 
openSUSE:Factory checked in at 2013-06-05 13:16:44
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/telepathy-mission-control (Old)
 and      /work/SRC/openSUSE:Factory/.telepathy-mission-control.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "telepathy-mission-control"

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/telepathy-mission-control/telepathy-mission-control.changes
      2013-01-20 14:55:35.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.telepathy-mission-control.new/telepathy-mission-control.changes
 2013-06-05 13:16:46.000000000 +0200
@@ -1,0 +2,69 @@
+Sun May  5 07:36:01 UTC 2013 - [email protected]
+
+- Update to version 5.15.0:
+  + Running this version of Mission Control for the first time will
+    automatically migrate some account data to a new format. If you
+    subsequently downgrade to an older version, it will no longer
+    understand all account data.
+  + Requirements:
+    - GLib 2.32 is now required.
+    - The regression tests now require Python 2.6.
+  + Deprecations:
+    - McpAccountStorage::altered, which appears to have never
+      worked, is now deprecated (fdo#28288). Emit ::altered-one
+      instead.
+    - mcp_account_storage_iface_set_priority() etc. are now
+      deprecated. Use, for instance, "iface->priority = prio"
+      instead.
+  + Enhancements:
+    - Account storage plugins (McpAccountStorageIface) may, and
+      should, implement the new set_attribute(), set_parameter()
+      and owns() methods. These methods allow the plugin to know
+      the type of each attribute or parameter, which is presented
+      as a GVariant. (fdo#54872).
+    - `mc-tool get <account> AutomaticPresence` now works 
+      (fdo#54780).
+    - When running under GNOME 3 or Unity, MC will attempt to
+      enable connections' power-saving features while the session
+      is idle; this is currently effective for Google Talk XMPP
+      connections (fdo#62530).
+  + Fixes:
+    - Update to the current ConnMan D-Bus API (fdo#56600).
+    - If a stored parameter has a value inappropriate for its type
+      (e.g. require-tls=2 where the connection manager expects
+      require-tls to be boolean), invalidate the account, rather
+      than treating the value as 0, "", [] etc. (fdo#54870).
+    - Handle Connection errors better, and in particular, don't try
+      to reconnect on SoftwareUpgradeRequired or ConnectionRefused
+      (fdo#37844).
+    - Handle errors from RequestConnection correctly, rather than
+      as NetworkError (fdo#39334).
+    - If the stored nickname for an account is the same as the
+      normalized name (identifier), don't set it on connect, in
+      case a better nickname is stored on the server (fdo#39381).
+    - Emit Properties.PropertiesChanged for URISchemes, as per the
+      upcoming telepathy-spec 0.27.1 (fdo#40393).
+    - McpAccountStorage::altered-one now works as intended
+      (fdo#54780).
+  + Internal changes:
+    - Refactor avatar and alias handling (fdo#55668).
+    - Refactor account storage (fdo#54870, fdo#54872).
+    - Improve regression test coverage for account storage
+      (fdo#54873).
+    - Start to remove uses of functions deprecated in
+      telepathy-glib 0.20 (fdo#55391).
+- Changes from version 5.14.1:
+  + Fixes:
+    - Only ignore passwords stored in our old gnome-keyring
+      location if Empathy has actually copied them to its new
+      location, fixing use of a gnome-keyring-enabled MC version 
+      with no Empathy or other SASLAuthentication handler (e.g.
+      under Sugar). (fdo#59468).
+    - Build successfully with Automake 1.13 (fdo#59605).
+    - Isolate regression tests better (fdo#63119).
+    - Respect NOCONFIGURE in autogen.sh (fdo#57165).
+- Drop tmc-mailto-is-the-proper-URI-scheme.patch and
+  tmc-fire-PropertiesChanged-on-URISchemes-change.patch, fixed
+  upstream.
+
+-------------------------------------------------------------------

Old:
----
  telepathy-mission-control-5.14.0.tar.gz
  tmc-fire-PropertiesChanged-on-URISchemes-change.patch
  tmc-mailto-is-the-proper-URI-scheme.patch

New:
----
  telepathy-mission-control-5.15.0.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ telepathy-mission-control.spec ++++++
--- /var/tmp/diff_new_pack.qMHeWk/_old  2013-06-05 13:16:47.000000000 +0200
+++ /var/tmp/diff_new_pack.qMHeWk/_new  2013-06-05 13:16:47.000000000 +0200
@@ -19,7 +19,7 @@
 Url:            http://mission-control.sourceforge.net/
 
 Name:           telepathy-mission-control
-Version:        5.14.0
+Version:        5.15.0
 Release:        0
 Summary:        Telepathy Mission Control instant messaging connection manager
 License:        LGPL-2.1
@@ -27,10 +27,6 @@
 Source:         
http://telepathy.freedesktop.org/releases/telepathy-mission-control/%{name}-%{version}.tar.gz
 # PATCH-NEEDS-REBASE lockdown-protocols.patch fdo21699 [email protected] -- 
Sent upstream for discussion, it will need a rewrite for MC5 WAS: 
PATCH-FEATURE-UPSTREAM
 Patch1:         lockdown-protocols.patch
-# PATCH-FIX-UPSTREAM tmc-mailto-is-the-proper-URI-scheme.patch fdo#40393 
[email protected] -- Changes made to sipaccounts does not appear.
-Patch2:         tmc-mailto-is-the-proper-URI-scheme.patch
-# PATCH-FIX-UPSTREAM tmc-fire-PropertiesChanged-on-URISchemes-change.patch 
fdo#40393 [email protected] -- Changes made to sipaccounts does not appear.
-Patch3:         tmc-fire-PropertiesChanged-on-URISchemes-change.patch
 BuildRequires:  dbus-1-glib-devel >= 0.73
 BuildRequires:  fdupes
 BuildRequires:  libgnome-keyring-devel
@@ -82,8 +78,6 @@
 %setup -q
 # NEEDS REBASE
 # %patch1 -p0
-%patch2 -p1
-%patch3 -p1
 
 %build
 %configure --disable-static --with-pic\

++++++ telepathy-mission-control-5.14.0.tar.gz -> 
telepathy-mission-control-5.15.0.tar.gz ++++++
++++ 18386 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to