# HG changeset patch
# User Paul Aurich <paul@darkrain42.org>
# Date 1250882268 0
# Node ID d905474475dc6af1aacc42812005c38bddfb8fd7
# Parent  adf7dc41770dbf7f2811a47f2133167d6a512cb9
jabber: Print out the expected/generated caps hashes.

This is useful for arguments about which implementation isn't generating
proper hashes according to the spec. ;-)

diff -r adf7dc41770d -r d905474475dc libpurple/protocols/jabber/caps.c
--- a/libpurple/protocols/jabber/caps.c	Fri Aug 21 07:54:43 2009 +0000
+++ b/libpurple/protocols/jabber/caps.c	Fri Aug 21 19:17:48 2009 +0000
@@ -468,8 +468,10 @@
 		}
 
 		if (!hash || strcmp(hash, userdata->ver)) {
-			purple_debug_warning("jabber", "Could not validate caps info from %s\n",
-			                     xmlnode_get_attrib(packet, "from"));
+			purple_debug_warning("jabber", "Could not validate caps info from "
+			                     "%s. Expected %s, got %s\n",
+			                     xmlnode_get_attrib(packet, "from"),
+			                     userdata->ver, hash ? hash : "(null)");
 
 			userdata->cb(NULL, NULL, userdata->cb_data);
 			jabber_caps_client_info_destroy(info);