[telepathy-gabble/master] caps/advertise-legacy.py: Explicitly check that we cope with what's arguably a bug in MC 5.1.4

Simon McVittie simon.mcvittie at collabora.co.uk
Tue Jul 28 05:55:06 PDT 2009


---
 tests/twisted/caps/advertise-legacy.py |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/tests/twisted/caps/advertise-legacy.py b/tests/twisted/caps/advertise-legacy.py
index e2cad54..434287e 100644
--- a/tests/twisted/caps/advertise-legacy.py
+++ b/tests/twisted/caps/advertise-legacy.py
@@ -20,7 +20,11 @@ def run_test(q, bus, conn, stream):
     # This method call looks wrong, but it's "the other side" of
     # test/twisted/capabilities/legacy-caps.py in MC 5.1 - MC doesn't know
     # how to map Client capabilities into the old Capabilities interface.
+    #
+    # Also, MC sometimes puts the same channel type in the list twice, so
+    # make sure Gabble copes.
     add = [(cs.CHANNEL_TYPE_STREAMED_MEDIA, 2L**32-1),
+            (cs.CHANNEL_TYPE_STREAM_TUBE, 2L**32-1),
             (cs.CHANNEL_TYPE_STREAM_TUBE, 2L**32-1)]
     remove = []
     caps = conn.Capabilities.AdvertiseCapabilities(add, remove)
-- 
1.5.6.5



More information about the telepathy-commits mailing list