FFe: python-maxminddb 1.5.2 update (MIR requirement)
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:/
1.5.0->1.5.1: https:/
1.4.1->1.5.0: https:/
PPA with a test package, with all supported architectures enabled, and focal-proposed enabled as well: https:/
Reverse dependencies of python3-maxminddb:
Reverse-Depends
* python3-geoip2
python-geoip2 was alread MIRed[6]
1. https:/
2. https:/
3. https:/
4. https:/
5. https:/
6. https:/
Related branches
- Christian Ehrhardt (community): Approve
- Canonical Server: Pending requested
-
Diff: 69325 lines (+16657/-798)42 files modifiedHISTORY.rst (+29/-4)
PKG-INFO (+140/-0)
README.rst (+14/-5)
debian/changelog (+16/-0)
debian/control (+3/-1)
debian/copyright (+1/-1)
debian/patches/rebuild-sphinx-docs.patch (+283/-0)
debian/patches/series (+1/-0)
debian/rules (+5/-4)
dev/null (+0/-528)
docs/html/.buildinfo (+4/-0)
docs/html/_sources/index.rst.txt (+1/-1)
docs/html/_static/basic.css (+768/-0)
docs/html/_static/doctools.js (+314/-0)
docs/html/_static/documentation_options.js (+11/-0)
docs/html/_static/jquery-3.4.1.js (+10598/-0)
docs/html/_static/jquery.js (+2/-0)
docs/html/_static/language_data.js (+297/-0)
docs/html/_static/pygments.css (+69/-0)
docs/html/_static/searchtools.js (+506/-0)
docs/html/_static/sphinxdoc.css (+345/-0)
docs/html/_static/underscore-1.3.1.js (+999/-0)
docs/html/_static/underscore.js (+31/-0)
docs/html/genindex.html (+218/-0)
docs/html/index.html (+439/-0)
docs/html/py-modindex.html (+105/-0)
docs/html/search.html (+91/-0)
docs/html/searchindex.js (+1/-0)
extension/maxminddb.c (+759/-0)
maxminddb.egg-info/PKG-INFO (+140/-0)
maxminddb.egg-info/SOURCES.txt (+74/-0)
maxminddb.egg-info/dependency_links.txt (+1/-0)
maxminddb.egg-info/top_level.txt (+1/-0)
maxminddb/__init__.py (+3/-3)
maxminddb/compat.py (+0/-3)
maxminddb/decoder.py (+64/-51)
maxminddb/file.py (+3/-5)
maxminddb/reader.py (+45/-28)
setup.cfg (+5/-1)
setup.py (+51/-61)
tests/decoder_test.py (+3/-6)
tests/reader_test.py (+217/-96)
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.