Hello community, here is the log from the commit of package telepathy-mission-control for openSUSE:Factory checked in at Tue Dec 8 12:27:54 CET 2009. -------- --- GNOME/telepathy-mission-control/telepathy-mission-control.changes 2009-09-28 17:06:59.000000000 +0200 +++ /mounts/work_src_done/STABLE/telepathy-mission-control/telepathy-mission-control.changes 2009-12-03 00:04:18.000000000 +0100 @@ -1,0 +2,163 @@ +Thu Dec 3 00:03:49 CET 2009 - vuntz@opensuse.org + +- Do not use bindir for libexecdir. + +------------------------------------------------------------------- +Sat Nov 14 11:47:52 CET 2009 - vuntz@opensuse.org + +- Update to version 5.3.2: + + Enhancements: + - mc-wait-for-name: give up after 5 minutes and exit + EX_TEMPFAIL. Also exit with EX_UNAVAILABLE (instead of 1) if + the session bus doesn't work, EX_USAGE (instead of 1) on + wrong arguments, and EX_USAGE (instead of g_critical() and + never terminating) if the requested bus name is not valid + - fdo#23651: strongly prefer the PreferredHandler for a channel + request, and try dispatching to it even if its + HandlerChannelFilters do not indicate that it could handle + the channel, since this is very useful for clients like + nautilus-sendto + - fdo#24120: refactor McdDispatcher quite extensively: + . always have a McdDispatchOperation for each + McdDispatcherContext, even if no approval is needed + . migrate the dispatching state machine into the dispatch + operation + . move client logic into McdClientProxy, removing the + McdClient struct + . migrate Client discovery and the client registry into a new + class McdClientRegistry + . remove many unused signals + . use McdDispatcherContext for the plugin API and nothing + else + - McdHandlerMap: operate in terms of TpChannel, not McdChannel, + to make the code less tightly coupled; watch for channels + closing and client crashing internally, rather than relying + on other modules + - Run the regression tests with GLib and GObject warnings set + to fatal + + Fixes: + - fdo#23687: if all Handlers with BypassApproval fail, notify + approvers and wait for approval before trying other Handlers + - fdo#24474: notify Observers about channels that were + requested without going via MC, e.g. by Empathy 2.28.x + - fdo#21003: delay the return from HandleWith until + HandleChannels has succeeded or failed, and pass on errors; + do not consider HandleWith(H) to be general approval for the + channel to be handled with handlers other than H + - fdo#24637: don't emit Finished until the channel dispatch + operation has really finished + - Fix a possible use-after-free when noting that a client has + gone away + - Avoid re-dispatching a re-requested channel to a different + handler + - When calling HandleChannels, use the most recent user-action + time from among all requests that led to this channel, and + all HandleWith() calls for this channel dispatch operation + - Don't call ReloadConfig() on the dbus-daemon (reopening + fdo#23921), to avoid triggering fdo#24350 in dbus-daemon and + causing service-activations to fail + - mc_account_conditions_call_when_ready: explain why it's OK to + ignore the result of mc_iface_call_when_ready_int, which was + a Coverity false-positive + - Consider calls to be potentially-missed if they terminate for + reason ERROR, even if we're the actor, because that's what + happens in Gabble >= 0.8.4 if the streaming implementation + (i.e. telepathy-farsight) discovers that none of the + candidates work and calls Error() + - Fix a race condition in the test + account-manager/make-valid.py, which would sometimes + incorrectly make it fail + - Add a regression test for dispatching and requests being + delayed while waiting for a plugin to make an asynchronous + request for permission + - Don't leak check_parameters_get_param_cb closure on error + - In libmcclient, invoke callbacks for GetAll() in the right + order +- Changes from version 5.3.1: + + Dependencies: + - Python >= 2.5 is now required for compilation + - telepathy-glib >= 0.7.37 is now required + + Enhancements: + - Automatically migrate passwords and other secrets from + accounts.cfg into the GNOME keyring (if enabled and + available) on MC startup + + Fixes: + - Deal with the user's alias in a race-free way by calling + GetAliases as well as binding to the AliasesChanged signal + - Fix some race conditions in the regression tests + - Fix mcd_dispatcher_get_channel_type_usage sometimes counting + aborted channels, by introducing MCD_CHANNEL_STATUS_ABORTED + - If we see too many transitions from CONNECTED to DISCONNECTED + state (i.e. we get kicked off by the server more than 3 + times in 2 minutes), stop reconnecting; also, don't reset the + exponential backoff until we've been connected for 2 minutes. + This avoids reconnecting in a tight loop if the server lets + us connect, then immediately drops our connection. + - Fix some minor memory leaks +- Changes from version 5.3.0: + + Dependencies: + - The GNOME Keyring library is a new optional dependency. If it + is enabled, having the library at runtime is required, but + having the daemon itself is optional - the current plain-text + storage will be used for passwords if the keyring daemon is + not available. + + Enhancements: + - fdo#20903: support the final version of ContactCapabilities, + from telepathy-spec 0.17.28 + - fdo#22231: add optional gnome-keyring integration. This is + off by default, but distributions should consider configuring + MC with --enable-gnome-keyring to get this functionality. + - mc-tool: show full Presence information + - Use the "mcd" G_LOG_DOMAIN + - fdo#23501: support TpDebugSender + - Stop #define'ing g_object_ref, g_object_unref + - fdo#22705: support MC_DEBUG=all + + Fixes: + - Escape "-" in protocol names in Account names, as required by + the Telepathy spec + - fdo#23818: if HandleChannels fails, try all Handlers in + sequence before giving up + - Refactor client locking in McdDispatcher to be more obviously + correct + - Don't define macros used in glibc feature-test internals, + possibly fixing failure to build from source on Debian + GNU/kFreeBSD + - Fix a reference leak when shooting down an unwanted + Connection + - fdo#23921: force dbus-daemon to re-detect .service files on + MC startup, as a partial workaround for D-Bus bug fdo#23925 + - fdo#23935: call AddRequest if appropriate even on clients + that match only channels with Requested=true, and use + requested channels' complete properties in preference to the + properties that were requested + - Make signed values in .client files work instead of g_critical'ing +- Add gnome-keyring-devel BuildRequires and pass + --enable-gnome-keyring to configure. + +------------------------------------------------------------------- +Thu Oct 8 19:02:17 CEST 2009 - vuntz@opensuse.org + +- Update to version 5.2.6: + + Enhancements: + - mc-wait-for-name: give up after 5 minutes and exit + EX_TEMPFAIL. Also exit with EX_UNAVAILABLE (instead of 1) if + the session bus doesn't work, EX_USAGE (instead of 1) on + wrong arguments, and EX_USAGE (instead of g_critical() and + never terminating) if the requested bus name is not valid + + Fixes: + - mc_account_conditions_call_when_ready: explain why it's OK to + ignore the result of mc_iface_call_when_ready_int, which was + a Coverity false-positive + - Consider calls to be potentially-missed if they terminate for + reason ERROR, even if we're the actor, because that's what + happens in Gabble >= 0.8.4 if the streaming implementation + (i.e. telepathy-farsight) discovers that none of the + candidates work and calls Error() + - Fix a race condition in the test + account-manager/make-valid.py, which would sometimes + incorrectly make it fail + - Add a regression test for dispatching and requests being + delayed while waiting for a plugin to make an asynchronous + request for permission + +------------------------------------------------------------------- calling whatdependson for head-i586 Old: ---- telepathy-mission-control-5.2.5.tar.bz2 New: ---- telepathy-mission-control-5.3.2.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ telepathy-mission-control.spec ++++++ --- /var/tmp/diff_new_pack.ZdlKBa/_old 2009-12-08 12:26:48.000000000 +0100 +++ /var/tmp/diff_new_pack.ZdlKBa/_new 2009-12-08 12:26:48.000000000 +0100 @@ -1,5 +1,5 @@ # -# spec file for package telepathy-mission-control (Version 5.2.5) +# spec file for package telepathy-mission-control (Version 5.3.2) # # Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany. # @@ -19,13 +19,14 @@ Url: http://mission-control.sourceforge.net/ Name: telepathy-mission-control -Version: 5.2.5 +Version: 5.3.2 Release: 1 -License: LGPL v2.1 only +License: LGPLv2.1 BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: gconf2-devel libxslt-devel BuildRequires: dbus-1-glib-devel >= 0.73 BuildRequires: fdupes +BuildRequires: gnome-keyring-devel BuildRequires: python-xml BuildRequires: telepathy-glib-devel >= 0.7.1 Group: System/Libraries @@ -44,7 +45,7 @@ and to manage presence statuses. %package devel -License: LGPL v2.1 only +License: LGPLv2.1 Group: Development/Libraries/C and C++ Summary: Telepathy Mission Control instant messaging connection manager Requires: %{name} = %{version} @@ -66,7 +67,7 @@ %build %configure --disable-static --with-pic\ - --libexecdir=%{_bindir} + --enable-gnome-keyring %__make %{?jobs:-j %jobs} %install @@ -87,7 +88,7 @@ %files %defattr(-,root,root) %{_bindir}/mc-* -%{_bindir}/mission-control-5 +%{_libexecdir}/mission-control-5 %{_datadir}/dbus-1/services/org.freedesktop.Telepathy.*.service # No soversion at the moment %{_libdir}/*.so ++++++ telepathy-mission-control-5.2.5.tar.bz2 -> telepathy-mission-control-5.3.2.tar.bz2 ++++++ ++++ 28248 lines of diff (skipped) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Remember to have fun... -- To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-commit+help@opensuse.org