Locations using bom.gov.au for forecast data no longer can no longer retrieve forecast data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libgweather |
Fix Released
|
Medium
|
|||
libgweather (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
libgweather is unable to parse the HTML data previously returned from the Australian Bureau of Meteorology
[Development Fix]
Fix committed upstream as a80552f51c64175
[Stable Fix]
Debdiffs attached for Lucid (https:/
[Test Case]
1. Login using a session with the gnome-panel (Ubuntu for Lucid, Maverick; Ubuntu Classic for Natty; GNOME Classic on Oneiric)
2. Right-click on the panel (Alt-right click for Oneiric) and select Add to Panel...
3. Choose the Weather Report applet and add it to the panel
4. Right click on the weather applet and choose preferences
5. Go to the Location tab
6. Search for and select "Sydney Airport", then close the preferences window
7. Left-click on the weather applet
8. Click "Update" from the details tab
9. Switch to the "Forecast" tab, and observe that the forecast is not available (or is, with the patch)
[Regression Potential]
Minimal. The patch is isolated, only changes parsing for the affected region (AU), and cherry-picked from upstream
===================
Original bug description:
-------
Issue Description
-------
In relation to "weather-applet" and "libgweather" - over the past several months, the Australian Bureau of Meteorology (BOM) has updated its website to deliver a HTML forecast page for a number of locations around Australia.
Currently - the <zone> tag from "Locations.xml" is used within the "weather-bom.c" to retrieve information from the appropriate bom.gov.au URL which if successful is then parsed in the "bom_parse" function.
With the new HTML forecast pages for various locations however, the data can not be successfully parsed and instead the message "Forecast not currently available for this location." shows up on the Forecast tab of weather-applet.
-------
Area of Interest
-------
Within "weather-bom.c" - the following line of code points to URLs (depending on location) that now have HTML forecast data rather than plain text...
url = g_strdup_printf ("http://
loc->zone + 1);
-------
Suggested Fix
-------
I suggest/propose that the URL above be changed to point to plain text documents on the BOM FTP server (ftp://ftp2.
e.g. for Sydney (Zone IDN10064) - currently the code would point to:
http://
However this is now a HTML forecast, which causes the issue noted above... by pointing the code to:
ftp://ftp2.
The plain text forecast can be used without any modification to the other functions/aspects of the code.
-------
Patches - Untested!
-------
Please see the attached "weather-bom.c" which includes the suggested fix (i.e. patched version). Note it will need to be/should be tested by someone who knows how to recompile the libgweather source.
-------
System information
-------
Description: Ubuntu 10.04.1 LTS
Release: 10.04
libgweather-common:
Installed: 2.30.0-0ubuntu1
Candidate: 2.30.0-0ubuntu1
Version table:
*** 2.30.0-0ubuntu1 0
500 http://
100 /var/lib/
-------
tags: | added: patch |
Changed in libgweather: | |
status: | Unknown → New |
Changed in libgweather: | |
importance: | Unknown → Medium |
Changed in libgweather: | |
status: | New → Confirmed |
Changed in libgweather (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
Changed in libgweather: | |
status: | Confirmed → Fix Released |
description: | updated |
description: | updated |
tags: | added: verification-done-oneiric |
tags: | added: verification-done verification-done-lucid |
This bug is an upstream one and it would be quite helpful if you could send the bug the to the people writing the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance!