GeoIP returns RS for Serbia which is the correct new iso code

Bug #218753 reported by Edwin Grubbs
24
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jeroen T. Vermeulen

Bug Description

The xx-person-editlanguages.txt test has been failing on systems running hardy. The GeoIP python module is now returning "RS" instead of "CS" for Serbia, but the Country table in the database only has an entry for "CS".

 This has apparently been the new iso3166 abbreviation since September 2006.
http://www.iso.org/iso/newsletter_v-12_serbia_montenegro.pdf

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Since geoip is correct, the bug is in the test (which is a rosetta one).

Changed in launchpad:
assignee: nobody → jtv
importance: Undecided → High
status: New → Confirmed
Changed in rosetta:
milestone: none → 1.2.5
Changed in rosetta:
milestone: 1.2.5 → 1.2.4
status: Confirmed → In Progress
Changed in rosetta:
milestone: 1.2.4 → 1.2.5
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Bjorn suggested in the internal launchpad@ list: "Using live data makes the tests quite fragile, as already shown. I'd suggest registering a new GeoIP utility for tests, which would replace self._gi with a libGeoIP-like object. That object would return what we want it to return, and not depend on external data."

Revision history for this message
Steve Alexander (stevea) wrote :

That is a valid approach.

Another approach is that we have a test that tests all our expectations about using the external data in our test suite.

That way, when the geoip data changes, then our test suite breaks. However, it's very obvious exactly what expectation has been broken.

Revision history for this message
Curtis Hovey (sinzui) wrote :

My partial fix, that address the immediate problem of the failing test landed in RF 6247. Should we unduplicate my bug from this one? There are two issues here: One is a failing test that is inconsequential to Launchpad users, and the GeoIP issue that does affect users.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Curtis: I beg to differ.

The only user-affecting issue reported in this bug is that something has become correct. That does not need fixing. The flip side of that coin is "the correction isn't in production yet," which is indeed a separate problem with a separate solution—but it's to upgrade production systems, and that was never a part of either of these bugs. It's being handled elsewhere.

Changed in rosetta:
status: In Progress → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.