[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#534750: marked as done (ITP: telepathy-mission-control-5 -- management daemon for Telepathy real-time communication framework)

Your message dated Fri, 07 Aug 2009 15:36:53 +0000
with message-id <E1MZRUz-00074l-UX@ries.debian.org>
and subject line Bug#534750: fixed in telepathy-mission-control-5 5.1.3-1
has caused the Debian Bug report #534750,
regarding ITP: telepathy-mission-control-5 -- management daemon for Telepathy real-time communication framework
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
534750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534750
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: wnpp
Severity: wishlist
Owner: Simon McVittie <smcv@debian.org>

* Package name    : telepathy-mission-control-5
  Version         : 5.1.2
  Upstream Author : the Telepathy project (© Nokia Corporation, Collabora Ltd.)
* URL             : http://mission-control.sourceforge.net/
* License         : variously LGPL (= 2.1) and LGPL (>= 2.1)
  Programming Lang: C with GObject
  Description     : management daemon for Telepathy real-time communication framework

Telepathy Mission Control 5 is an account manager and channel dispatcher for
the Telepathy framework, allowing user interfaces and other clients
to share connections to real-time communication services without conflicting.
It implements the AccountManager and ChannelDispatcher D-Bus APIs as described
by telepathy-spec.

The account manager part stores real time communication account details,
connects to the stored accounts on request, and sets the accounts' presence,
nickname and avatar according to requests from Telepathy user interfaces and
other components.

The channel dispatcher part responds to incoming communication channels
(message streams, voice/video calls, file transfers etc.) by dispatching
them to suitable user interfaces, and requests outgoing communication
channels according to requests from a Telepathy UI.

This is not a compatible replacement for Mission Control 4 (in the
telepathy-mission-control package), but they can be installed in parallel.

- ------

Notes regarding this ITP:
* MC 4 will be removed when the programs that use it (I think that's just
  Empathy) have been ported to MC 5. That porting will take a while, though,
  so this is a new source package and the versions will exist in parallel for
  a bit.
* There's packaging for 5.1.0 on git.debian.org already; I just need to update
  it for a couple of new upstream releases, which should be pretty easy.
-----BEGIN PGP SIGNATURE-----

iD8DBQFKRThFWSc8zVUw7HYRAjStAJ9If6vzQb7oX2Tcxr52CQjpK5glhwCg8D+e
ZN69rkuCKHJt9rVE1lSIfpQ=
=KExX
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Source: telepathy-mission-control-5
Source-Version: 5.1.3-1

We believe that the bug you reported is fixed in the latest version of
telepathy-mission-control-5, which is due to be installed in the Debian FTP archive:

telepathy-mission-control-5-dbg_5.1.3-1_i386.deb
  to pool/main/t/telepathy-mission-control-5/telepathy-mission-control-5-dbg_5.1.3-1_i386.deb
telepathy-mission-control-5_5.1.3-1.diff.gz
  to pool/main/t/telepathy-mission-control-5/telepathy-mission-control-5_5.1.3-1.diff.gz
telepathy-mission-control-5_5.1.3-1.dsc
  to pool/main/t/telepathy-mission-control-5/telepathy-mission-control-5_5.1.3-1.dsc
telepathy-mission-control-5_5.1.3-1_i386.deb
  to pool/main/t/telepathy-mission-control-5/telepathy-mission-control-5_5.1.3-1_i386.deb
telepathy-mission-control-5_5.1.3.orig.tar.gz
  to pool/main/t/telepathy-mission-control-5/telepathy-mission-control-5_5.1.3.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 534750@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@debian.org> (supplier of updated telepathy-mission-control-5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 01 Jul 2009 16:33:16 +0100
Source: telepathy-mission-control-5
Binary: telepathy-mission-control-5 telepathy-mission-control-5-dbg
Architecture: source i386
Version: 5.1.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Telepathy maintainers <pkg-telepathy-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Description: 
 telepathy-mission-control-5 - management daemon for Telepathy real-time communication framework
 telepathy-mission-control-5-dbg - management daemon for Telepathy (debug symbols)
Closes: 534750
Changes: 
 telepathy-mission-control-5 (5.1.3-1) unstable; urgency=low
 .
   * Initial upload of Mission Control 5 (Closes: #534750), which will
     eventually replace telepathy-mission-control. It's basically a rewrite of
     MC 4, and is incompatible but parallel-installable, so I've packaged it
     from scratch.
   * Don't package libmcclient headers, development symlink or docs, but just
     bundle the shared library (which has -release versioning) with the daemon:
     it's not ABI-stable, and shouldn't be used in mainstream distributions
     (use telepathy-glib instead). The shared library has to remain shared,
     since it has symbols that collide with the daemon itself (albeit with the
     same implementations; this is in the process of being fixed upstream).
   * Don't package mc-account-convert, since it's the only thing in this
     package that needs gconf, and Empathy will probably ship its own
     MC 4 to MC 5 converter (perhaps based on mc-account-convert).
Checksums-Sha1: 
 5d5bfe5fae7580f0aa9f78f053b1e3262acc2e04 1593 telepathy-mission-control-5_5.1.3-1.dsc
 4ae105c7863cfed64787cac6d805c2f573b81402 1014834 telepathy-mission-control-5_5.1.3.orig.tar.gz
 b49d88832200799b04c38eec72545581f893a5a2 4027 telepathy-mission-control-5_5.1.3-1.diff.gz
 37deec780085e50bc94876ba1c592cc455f152b7 322158 telepathy-mission-control-5_5.1.3-1_i386.deb
 6c4cccb9b8d2fd71c19b9ec960e77b38d1b65b6e 326404 telepathy-mission-control-5-dbg_5.1.3-1_i386.deb
Checksums-Sha256: 
 f3253558e63fc5c5553b7ae4fd54ebf6cb913c2b3caf2ea10dbc3ee73c589c8c 1593 telepathy-mission-control-5_5.1.3-1.dsc
 dc936b5223f4cb7726893daa6b4710e4b15df39a9c592bbf8890e69fcba2b172 1014834 telepathy-mission-control-5_5.1.3.orig.tar.gz
 31a4457450c6376eb4110ab443b0d02d6b596e2a22f94cfec0a92f2951466dd4 4027 telepathy-mission-control-5_5.1.3-1.diff.gz
 8c76d0e151bd958a915b4e482836334c151efab6b7f4080500be5632ac542ba0 322158 telepathy-mission-control-5_5.1.3-1_i386.deb
 ebc479b22da37a404b909bd3edce26eb672624468373c229ecb168d8b87a3b98 326404 telepathy-mission-control-5-dbg_5.1.3-1_i386.deb
Files: 
 ba89063d4e35a13df22ed382622afe37 1593 net optional telepathy-mission-control-5_5.1.3-1.dsc
 b322d6705713553f4975a935086c15c1 1014834 net optional telepathy-mission-control-5_5.1.3.orig.tar.gz
 bd1aa35f8f43c5497de0d42c68c9c2e4 4027 net optional telepathy-mission-control-5_5.1.3-1.diff.gz
 8ab701fdfb29ad39ffeae827a6cd13a3 322158 net optional telepathy-mission-control-5_5.1.3-1_i386.deb
 ca930e48de5616f70ce6d66134feff06 326404 debug extra telepathy-mission-control-5-dbg_5.1.3-1_i386.deb

-----BEGIN PGP SIGNATURE-----

iD8DBQFKS5w2WSc8zVUw7HYRAmoLAKDd7RG0LGVRy5C/4dMUHB769PHGoQCfeK/u
gUy5Atg9IdD8mrtnwMa8/V0=
=H6PS
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: