[Telepathy] Announce: telepathy-mission-control 5.13.1
Simon McVittie
simon.mcvittie at collabora.co.uk
Thu Sep 6 11:04:53 PDT 2012
Here is telepathy-mission-control 5.13.1, the "Triceratops" release.
This is a development release with all the fixes from the
recently-released 5.12.2, plus some new opportunities for bugs :-)
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.13.1.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.13.1.tar.gz.asc
Here's what's happened since 5.13.0.
Changes:
• On Unix platforms, umask() is now required. (Simon)
• If a connection manager announces two or more channels in the same
NewChannels signal, behave as if it had announced each channel
separately. Simplify things that previously had to cope with
multiple channels at a time. (fd.o #52305, Simon)
• Improve mc-tool: display Account.Storage settings, add Supersedes,
add "dump" subcommand (fd.o #53202; Guillaume, Xavier)
• More internal reorganisation (fd.o #54151, Simon)
Fixes:
• Passwords are now deleted from gnome-keyring correctly (fd.o #42088,
Simon)
• When migrating Butterfly accounts to Haze, do the migration even if
Butterfly isn't installed, and copy the password as well as the
username (Debian #686835, Simon)
• If compiled with UPower support, do not attempt to connect while going
to sleep (Guillaume)
• Set up the altered-one signal for account storage backends correctly
(fd.o #52231, Xavier)
• If service-activated under both names o.fd.Telepathy.MissionControl5
and o.fd.Telepathy.AccountManager simultaneously, avoid one or both
failing to activate due to a race condition (fd.o #53220, Simon)
• When built for Android, don't use GSettings (fd.o #53497, Simon)
Regards,
S
More information about the telepathy
mailing list