gwibber-bugs team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

Hello Mark, or anyone else affected,

Accepted gwibber into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/gwibber/3.4.2-0ubuntu2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from
verification-needed to verification-done.  If it does not, change the
tag to verification-failed.  In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gwibber (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/1012231

Title:
  Recent changes in Foursquare's API result in plugin failing to parse
  results

Status in Gwibber:
  Confirmed
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “gwibber” source package in Precise:
  Fix Committed

Bug description:
  Impact:

  Foursquare recently introduced a website redesign, with accompanying
  changes in their API.  As a result of this, the Foursquare plugin can
  no longer parse results correctly and wll not display any.

  Test case:

  ensure the gwibber-service process has been restarted since apply the
  update then verify foursquare check-ins are showing up in your stream.

  Regression potential:

  There isn't really any regression potential, since foursquare changed
  the API without this change it isn't working at all.

  ---

  The 'canonicalurl' key has been removed from the API result.
  Currently, the plugin uses this to determine the sender url.  Instead,
  the user id must be used to construct an sender url.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/1012231/+subscriptions