commit 26954c0a5128d74d8dc6031a9397365ec9620e4e Author: Travis Reitter Date: Tue Apr 26 10:33:47 2011 -0700 Release version 0.4.3 configure.ac | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) commit 6ba5584d196cb61e815bf541e15f14f3a8d36a70 Author: Travis Reitter Date: Tue Apr 26 10:07:09 2011 -0700 Fix the location of bug fixes since 0.4.2. NEWS | 13 +++++++++---- 1 files changed, 9 insertions(+), 4 deletions(-) commit 29ab3e525540ee83960f132a9e2a18ea4b2f3eac Author: Philip Withnall Date: Tue Apr 12 20:42:06 2011 +0100 Don't remove the wrong Individuals from IndividualAggregator In IndividualAggregator._individual_removed_cb(), don't remove the individual from IndividualAggregator.individuals unless it is actually the individual which is emitting the "removed" signal. Closes: bgo#647121 NEWS | 2 ++ folks/individual-aggregator.vala | 8 ++++---- 2 files changed, 6 insertions(+), 4 deletions(-) commit 8cc9064a2516b82e984e098c48568e6cf4613fe0 Author: Philip Withnall Date: Sat Jan 22 11:34:53 2011 +0000 Fix Tpf.Persona to use its store's ID in persona UIDs It was previously (incorrectly) not using the PersonaStore's ID as the middle component in its UID, which meant that the same IM address as added on two different accounts using the same protocol would have the same UID, undermining the concept of a UID as a globally unique identifier for a Persona. Closes: bgo#647121 backends/telepathy/lib/tpf-persona.vala | 2 +- tests/folks/aggregation.vala | 15 ++++++++++----- tests/telepathy/individual-properties.vala | 3 ++- tests/telepathy/individual-retrieval.vala | 3 ++- 4 files changed, 15 insertions(+), 8 deletions(-) commit 41a374324c60eb46548a894fc37a1eece62375ab Author: Philip Withnall Date: Tue Apr 12 16:08:40 2011 +0100 Bug 647562 — Don't crash on duplicate group channels NEWS | 1 + backends/telepathy/lib/tpf-persona-store.vala | 17 +++++++++++++++++ 2 files changed, 18 insertions(+), 0 deletions(-) commit 8203422ce88df80c1c3c40cf715d959359e1cfa8 Author: Philip Withnall Date: Mon Jan 17 15:42:24 2011 +0000 Bug 645680 — Use random integer IDs for Kf.Personas Using consecutive integer IDs meant that IDs often got re-used as Personas were deleted and added, meaning that the same ID could, over time, be applied to several different Personas which contained completely different IM addresses. Any external references to such IDs which weren't updated over time with the IDs themselves (such as the to-be-added anti-links) would end up pointing to effectively the wrong Persona. A perfect solution would be to hash the IM addresses in each Persona and use that as the Persona's ID, but that's not possible as the set of IM addresses in a Kf.Persona can change over time, while the ID has to remain constant. Consequently, the use of a random integer evenly distributed over the space of unsigned 32-bit integers will do. Closes: bgo#645680 NEWS | 1 + backends/key-file/kf-persona-store.vala | 14 ++++++-------- 2 files changed, 7 insertions(+), 8 deletions(-) commit fa10cf2365ce8f06a95caac3f1ca1eb3f535e925 Author: Philip Withnall Date: Sun Nov 21 14:15:36 2010 +0000 Clarify immutability of Persona.uid folks/persona.vala | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) commit dd64b74bcd723345c7475f5d5af48303d3694e83 Author: Travis Reitter Date: Wed Mar 23 12:44:22 2011 -0700 Post-release version bump. configure.ac | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)