FFe: python-maxminddb 1.5.2 update (MIR requirement)

Bug #1867919 reported by Andreas Hasenack
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-maxminddb (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

As a requirement[1] for the python-maxminddb MIR[2], we want to update it to version 1.5.2 (from 1.4.1 in focal currently). This is the long tail of re-enabling GeoIP support[5] in bind9 9.16.x.

The upstream releases page[3] has release notes for each version. We are going from 1.4.1 in focal to 1.5.2.

1.5.0 is the one that introduces changes that need an FFe, while 1.5.1 and 1.5.2 are just bug fixes.

The MP that is updating this in focal is at [4]. It has a good description of the packaging changes and their reasoning.

Anyway, here are some helpful links to see the changes upstream:

1.5.1->1.5.2: https://github.com/maxmind/MaxMind-DB-Reader-python/compare/v1.5.1...v1.5.2
1.5.0->1.5.1: https://github.com/maxmind/MaxMind-DB-Reader-python/compare/v1.5.0...v1.5.1

1.4.1->1.5.0: https://github.com/maxmind/MaxMind-DB-Reader-python/compare/v1.4.1...v1.5.2

PPA with a test package, with all supported architectures enabled, and focal-proposed enabled as well: https://launchpad.net/~ahasenack/+archive/ubuntu/python-maxminddb-update

Reverse dependencies of python3-maxminddb:
Reverse-Depends
* python3-geoip2

python-geoip2 was alread MIRed[6]

1. https://bugs.launchpad.net/ubuntu/+source/python-maxminddb/+bug/1861101/comments/27
2. https://bugs.launchpad.net/ubuntu/+source/python-maxminddb/+bug/1861101
3. https://github.com/maxmind/MaxMind-DB-Reader-python/releases
4. https://code.launchpad.net/~ahasenack/ubuntu/+source/python-maxminddb/+git/python-maxminddb/+merge/380854
5. https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875
6. https://bugs.launchpad.net/ubuntu/+source/python-geoip2/+bug/1861101/comments/19

Related branches

description: updated
description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Ok, I guess it makes no sense to stop since we already started going this route - if the MIR team feels that a newer version would be recommended, let's do it. I glimpsed through the changes between v1.4.1 and v1.5.2 and didn't see anything that could potentially break anybody. That being said, let's keep a look out for people reporting new bugs against python-maxminddb suddenly acting crazy.

I approve of this FFe.

Changed in python-maxminddb (Ubuntu):
status: New → Triaged
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Thanks, I'm subscribed to the package here in LP and in Debian, and am also watching upstream for new releases. I'll change my upstream subscription to also watch for new bugs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python-maxminddb - 1.5.2-0ubuntu1

---------------
python-maxminddb (1.5.2-0ubuntu1) focal; urgency=medium

  * New upstream release: 1.5.2 (LP: #1867919)
  * Rebuild sphinx docs to avoid shipping other copies of several
    javascript files, like jquery.js, in the doc package:
    - d/p/rebuild-sphinx-docs.patch: pull in upstream's sphinx-build conf.py
    - d/rules: use docs-source for building docs
    - d/rules: remove the index.rst file from docs-source during clean
  * d/control: add Rules-Requires-Root: no
  * d/rules: update dh_auto_clean override

  [ Faidon Liambotis]
  * d/copyright: Switch the copyright format URI to https

 -- Andreas Hasenack <email address hidden> Wed, 18 Mar 2020 17:57:58 -0300

Changed in python-maxminddb (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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