Summary: | Various roster fixes | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Will Thompson <will> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | guillaume.desmottes |
Version: | unspecified | Keywords: | patch |
Hardware: | Other | ||
OS: | All | ||
URL: | http://git.collabora.co.uk/?p=user/wjt/telepathy-gabble-wjt.git;a=shortlog;h=refs/heads/i-hate-rosters | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Will Thompson
2009-07-20 12:32:41 UTC
The branch looks fine according my (very limited) understanding of the Google roster and all its mysteries. 2 typo in the NEWS: "who which" ? for another JID). You are closing a not opened parenthesis. (In reply to comment #1) > 2 typo in the NEWS: I've updated the branch accordingly. Think this is okay to go? The Google roster is not all that mysterious, and I've tried to add enough information in comments that people in the future touching this stuff won't have to re-reverse-engineer the bugs being worked around. :) Merged, will be in 0.7.31. Thanks for the review! The problem still occurs with version 0.8.12-0ubuntu1.1 on Ubuntu Lucid 10.04 LTS. We (Telepathy upstream) do not support Gabble 0.8.x any more. So, does the bug occur with a more modern version of Gabble? If so, please attach debug logs from Gabble as per <http://telepathy.freedesktop.org/wiki/Debugging>, and describe which aspect of “the problem” you are referring to. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/45. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.