summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2013-06-11gabbletest: add hooks for hazetestHEADmasterWill Thompson1-9/+14
I need these so that hazetest can just override what it needs, rather than actually modifying the copy of gabbletest. https://bugs.freedesktop.org/show_bug.cgi?id=65658
2013-06-11Merge branch 'telepathy-gabble-0.16' and update NEWSSimon McVittie1-1/+9
2013-06-11NEWS for recent changestelepathy-gabble-0.16Simon McVittie1-1/+15
2013-06-11Avoid having two of the same set of commands run in parallelSimon McVittie1-9/+19
A rule like this: _gen/x.c _gen/x.h: prerequisites $(AM_V_GEN)x-generator doesn't consider x.c and x.h together. Instead, it expands to two rules, one to generate x.c and one to generate x.h, which happen to run the same commands. This means that in the worst case, you can end up running x-generator twice in parallel, and they'll race with each other and overwrite or delete each other's output. Based on commit 36c2a545c from telepathy-glib. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=64285 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk> Conflicts: extensions/Makefile.am
2013-06-11Use run-test.sh to run uninstalled testsSimon McVittie1-15/+8
2013-06-11Adapt run-test.sh to be able to run the tests uninstalledSimon McVittie2-13/+40
When autoreconfiscated with Automake 1.13, the way in which we were (ab?)using Automake's test driver no longer works. We can't just switch back to the old serial test driver without a dependency on at least Automake 1.12, either. However, run-test.sh (which was already used for installed tests) is quite capable of running uninstalled tests, with a bit of adjustment: * if GABBLE_TEST_UNINSTALLED is set, expect GABBLE_ABS_TOP_SRCDIR, GABBLE_ABS_TOP_BUILDDIR and optionally GABBLE_TEST_SLEEP in the environment * look for installed or uninstalled files, as appropriate * use TEST_PYTHON (which might differ from PYTHON) * use python -u (unbuffered stdout) for better debugging Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65290 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-11.gitignore: automake 1.13 installs test-driverSimon McVittie1-0/+1
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65290 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-11Remove obsolete GLib < 2.32 code pathsSimon McVittie2-15/+0
We now depend on 2.32. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65290 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-11Officially depend on GLib 2.32Simon McVittie3-5/+5
In practice we depend on it anyway, via telepathy-glib 0.19.9. Also update the telepathy-glib dependency in the .pc files to match configure.ac. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65290 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-06Merge branch 'telepathy-gabble-0.16'Simon McVittie0-0/+0
Conflicts: NEWS configure.ac
2013-06-06nano versionSimon McVittie2-1/+6
2013-06-06Disable unreliable test-caseSimon McVittie1-0/+4
It has a race condition or something. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=49595 Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
2013-06-06Initialize libdbus for thread-safetySimon McVittie1-0/+5
libdbus is not thread-safe by default. This is a long-standing design flaw (<https://bugs.freedesktop.org/show_bug.cgi?id=54972>). We call into GIO, which calls into glib-networking, which can (at least in recent versions) invoke libproxy in a thread. libproxy apparently has a Network-Manager plugin, which uses libdbus in that thread; meanwhile, we use libdbus in the main thread and everything goes badly for us. (It's possible that this crash is only reproducible with broken connectivity: I wrote this patch on a train, with intermittent mobile broadband coverage.) In libdbus < 1.7.4, libraries cannot safely initialize libdbus for multi-threading, because that initialization is not itself thread-safe (!); in particular, glib-networking cannot safely initialize libdbus. So, we have to do it. I have written patches to make libdbus thread-safe-by-default, but they haven't all been reviewed and merged yet, and in any case they won't be in a stable libdbus until 1.8. Until then, each application has to discover and fix this bug individually. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65296 Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-06Prepare 0.17.5telepathy-gabble-0.17.5Simon McVittie2-3/+9
2013-06-05Disable unreliable test-caseSimon McVittie1-0/+4
It has a race condition or something. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=49595 Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
2013-06-04Initialize libdbus for thread-safetySimon McVittie1-0/+5
libdbus is not thread-safe by default. This is a long-standing design flaw (<https://bugs.freedesktop.org/show_bug.cgi?id=54972>). We call into GIO, which calls into glib-networking, which can (at least in recent versions) invoke libproxy in a thread. libproxy apparently has a Network-Manager plugin, which uses libdbus in that thread; meanwhile, we use libdbus in the main thread and everything goes badly for us. (It's possible that this crash is only reproducible with broken connectivity: I wrote this patch on a train, with intermittent mobile broadband coverage.) In libdbus < 1.7.4, libraries cannot safely initialize libdbus for multi-threading, because that initialization is not itself thread-safe (!); in particular, glib-networking cannot safely initialize libdbus. So, we have to do it. I have written patches to make libdbus thread-safe-by-default, but they haven't all been reviewed and merged yet, and in any case they won't be in a stable libdbus until 1.8. Until then, each application has to discover and fix this bug individually. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65296 Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-06-04NEWSSimon McVittie1-1/+14
2013-06-04Update Wocky to fix a regression caused by #65131Simon McVittie1-0/+0
2013-06-04Avoid having two of the same set of commands run in parallelSimon McVittie1-9/+19
A rule like this: _gen/x.c _gen/x.h: prerequisites $(AM_V_GEN)x-generator doesn't consider x.c and x.h together. Instead, it expands to two rules, one to generate x.c and one to generate x.h, which happen to run the same commands. This means that in the worst case, you can end up running x-generator twice in parallel, and they'll race with each other and overwrite or delete each other's output. Based on commit 36c2a545c from telepathy-glib. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=64285 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-05-30Update Wocky for fd.o #65131, and test itSimon McVittie2-2/+7
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65131 Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-05-30nano version and retroactive release nameSimon McVittie2-1/+8
2013-05-30nano versionSimon McVittie2-1/+6
2013-05-30prepare 0.17.4telepathy-gabble-0.17.4Simon McVittie2-4/+10
2013-05-30vcard/supported-fields: catch up with fd.o #64319Simon McVittie1-0/+1
Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
2013-05-30Merge branch 'telepathy-gabble-0.16'Simon McVittie5-1/+53
Conflicts: NEWS configure.ac lib/ext/wocky
2013-05-29Prepare version 0.16.6telepathy-gabble-0.16.6Simon McVittie2-3/+5
2013-05-29Add a regression test for fd.o #65036Simon McVittie2-0/+37
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65036 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
2013-05-29tests: fix JabberAuthenticator when self.emit_events is FalseSimon McVittie1-1/+1
We don't currently use JabberAuthenticator in this mode, so nobody noticed that it didn't work. I'm about to add a test that does use it.
2013-05-29NEWS: update and describe configuration changes for fd.o #65036Simon McVittie1-0/+21
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65036 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk> [added CVE ID now that we have one -smcv]
2013-05-29Update Wocky for fd.o #65036Simon McVittie1-0/+0
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65036
2013-05-08X-TELEPATHY-PASSWORD is not supported if username isn't knownXavier Claessens1-12/+13
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=64354
2013-05-07Google vcard can now have an URL fieldXavier Claessens1-2/+3
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=64319
2013-04-04Merge branch 'telepathy-gabble-0.16'Simon McVittie1-0/+6
2013-04-04Merge with-session-bus.sh changes from telepathy-glibSimon McVittie1-0/+6
We also have local changes, which should go "upstream" to telepathy-glib at some point. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=63119
2013-03-18Update Wocky for #61792Simon McVittie2-1/+4
2013-03-04Bump nano-versionWill Thompson2-1/+7
2013-03-01Update Wocky to fix distchecktelepathy-gabble-0.17.3Will Thompson1-0/+0
2013-03-01Version 0.17.3Will Thompson1-2/+2
2013-03-01NEWS for 0.17.3Will Thompson1-3/+9
2013-03-01Merge branch 'telepathy-gabble-0.16'Will Thompson2-1/+14
Conflicts: NEWS configure.ac lib/ext/wocky
2013-03-01Merge branch '43166-muc-rate-limit'Will Thompson6-82/+219
2013-03-01Bump nano-version to 0.16.5.1Will Thompson1-1/+1
2013-03-01Version 0.16.5telepathy-gabble-0.16.5Will Thompson1-2/+2
2013-03-01NEWS for 0.16.5Will Thompson1-0/+19
2013-03-01Update Wocky snapshot to fix 61433Will Thompson1-0/+0
2013-02-22MUC: stop sending chat states after <error type=wait>43166-muc-rate-limitWill Thompson2-7/+57
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=43166#c0
2013-02-22muc/chat-states: fix and uncomment commented chunkWill Thompson1-16/+16
This didn't work as-is because the <presence type='unavailable'> had no <x> child. Using make_muc_presence() does the job nicely.
2013-02-22muc/chat-states: tidy up checking message bodiesWill Thompson1-8/+4
2013-02-22muc: test resource-constraint is exposed reasonablyWill Thompson1-0/+10
https://bugs.freedesktop.org/show_bug.cgi?id=43166#c7
2013-02-22Test Prosody's MUC's rate limit is exposed correctly nowWill Thompson1-12/+59
There were a combination of problems before: * The server's error message was not exposed in the delivery report; * Wocky didn't recognise policy-violation; * There was a bug in Wocky's error parsing code which clobbered the message type. So many bugs for such a small stanza!