Ubuntu
libmaxminddb package

FFe: libmaxminddb update to 1.4.2 (MIR requirement)

Bug #1867624 reported by Andreas Hasenack on 2020-03-16

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	libmaxminddb (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Hello,

I would like to update libmaxminddb to a new upstream version of 1.4.2, going ahead of debian. This is a requirement[4] for its own MIR (#1861101) which will unblock fixing bind9's bug #1866875.

The upstream release notes for libmaxminddb 1.4.2 can be seen at [3], and are basically the same as for 1.4.0 minus the release bugs (as 1.4.0 and 1.4.1 were broken releases):

Of interest to the update, as requested in the MIR[4], is this fix:
"""
Fix a memory leak that occurred when freeing an MMDB_s where the
database had no languages defined in the metadata. If you are using an
official MaxMind database, this leak does not affect you. Pull request
by Kókai Péter. GitHub #180.
"""

This is the diff[5] between 1.3.2 (current release in ubuntu and debian) and 1.4.2.

A debdiff is attached, produced from the branch at [6]. I might still add review requests.

A PPA with test builds is available at [7]. No rebuild was needed for bind9, and as the soname remains the same, the same is expected for the other reverse dependencies.

1. https://bugs.launchpad.net/ubuntu/+source/libmaxminddb/+bug/1861101
2. https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875
3. https://github.com/maxmind/libmaxminddb/releases
4. https://bugs.launchpad.net/ubuntu/+source/libmaxminddb/+bug/1861101/comments/5
5. https://github.com/maxmind/libmaxminddb/compare/1.3.2...1.4.2
6. https://code.launchpad.net/~ahasenack/ubuntu/+source/libmaxminddb/+git/libmaxminddb/+ref/focal-maxminddb-update-ahead-debian
7. https://launchpad.net/~ahasenack/+archive/ubuntu/bind9-geoip/

Related branches

~ahasenack/ubuntu/+source/libmaxminddb:focal-maxminddb-update-ahead-debian

Merged into ubuntu/+source/libmaxminddb:ubuntu/devel at revision c96ae4742fe8b61a31199f738dac32a0f9ed0a14

Christian Ehrhardt  (community): Approve on 2020-03-16

Canonical Server: Pending requested 2020-03-16

Canonical Server MOTU reviewers: Pending requested 2020-03-16

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2020-03-16:

Ok, since this is required for the MIR to happen and that the MIR itself already got a +1, I'll approve this FFe. I was a bit worried since those versions were apparently tagged "DO NOT USE" by upstream, but I trust the MIR team's judgment here.

Please proceed.

Changed in libmaxminddb (Ubuntu):
status:	New → Triaged

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-03-16:

This bug was fixed in the package libmaxminddb - 1.4.2-0ubuntu1

---------------
libmaxminddb (1.4.2-0ubuntu1) focal; urgency=medium

  * New upstream release: 1.4.2 (LP: #1867624)
  * manpages are no longer rebuilt:
    - d/p/0001-Remove-Pandoc-version-from-manpages.patch: removed, as the
      upstream tarball only ships generated manpages now and no script
      to rebuild them.
    - d/control: drop b-d on pandoc, as it was only needed to rebuild
      the manpages.
    - d/rules: drop clean and autobuild overrides
  * d/rules: add +now hardening
  * d/compat, d/control: use debhelper 12 (d/compat removed)
  * d/libmaxminddb0.install: add defined.3 manpage

-- Andreas Hasenack <email address hidden> Mon, 16 Mar 2020 10:16:02 -0300

Changed in libmaxminddb (Ubuntu):
status:	Triaged → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulibmaxminddb package