Raring is released. Updates for it don't just happen automatically. To
get this patch backported into raring it has to go through a thorough
and lengthy review process that we call an SRU (Stable Release Update).
This process was put in place in order to prevent new bugs from getting
pushed back into older releases (ie, we want to be really sure that
patch we're SRUing is actually just one single fix, and doesn't
introduce a bunch of new problems like new software often does).

Considering that this bug seems to only affect you, and ought to be
easily fixed by simply deleting one file every now and again, I don't
personally feel that this problem warrants an SRU. If we suddenly had
hundreds of people reporting this, or if it wasn't so easy to just
delete that json file (very few bugs have such an easy workaround), then
I might be more inclined to SRU this fix.

As it stands, Saucy will be out in 3 months and Raring will EOL by
January. If this problem *really* bothers you a lot, just update to
Saucy when it comes out, and you'll get the fix then. Or if you're
really impatient, update to saucy after the beta freeze in September and
you'll be fine.

Also, I just had a second look at the patch that fixed this issue, and
it turns out that it's not even really compatible with the Raring
version anyway, due to other changes that have happened in the affected
file since then. Not to say that backporting it is impossible, just that
the patch would need to be completely re-written, which would make the
SRU process even longer and more difficult than it normally is.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1189229

Title:
  UnicodeDecodeError in friends-dispatcher with corrupted
  facebook_ids.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1189229/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to