Also updated the release notes regarding the nginx changes:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#nginx
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
[MIR]:
I updated the release notes:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Bind_9.16
** Changed in: ubuntu-release-notes
Status: New => Fix Released
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification
python-maxminddb was promoted, so python-geoip2 can also be promoted
now. See comment #19 for the MIR approval.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
[MIR]:
>> - For 20.04 we really should consider going ahead to the much newer 1.5.2
>> => https://github.com/maxmind/MaxMind-DB-Reader-python/releases
>> @andreas will you take a look at this, just as you did with the other
>> related package that was slightly outdated?
> FFe bug for the update:
> - For 20.04 we really should consider going ahead to the much newer 1.5.2
> => https://github.com/maxmind/MaxMind-DB-Reader-python/releases
> @andreas will you take a look at this, just as you did with the other
> related package that was slightly outdated?
FFe bug for the update:
python-maxminddb MIR request
Availability:
The package must already be in the Ubuntu universe, and must build for the
architectures it is designed to work on.
- package is in universe: https://launchpad.net/ubuntu/+source/python-maxminddb
- package builds for amd64, arm64, armhf, ppc64el, s390x
libmaxminddb was uploaded and migrated, setting task to "fix released".
** Changed in: libmaxminddb (Ubuntu)
Status: New => Fix Released
** Changed in: libmaxminddb (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of
But it's still in universe, so setting back to fix committed until
promotion happens.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
[MIR]: dependency of bind9
To manage
I made a mistake in the python-geoip2 MIR[1]. This second statement is
incorrect:
- dependencies are python3-maxminddb (>= 1.4.0), python3-requests, python3:any
- python3-maxminddb is a subject of this same MIR LP: #1861101 <--- FALSE
python3-maxminddb comes from src:python-maxminddb, not
- nginx was uploaded
(https://launchpad.net/ubuntu/+source/nginx/1.17.9-0ubuntu2)
- libmaxminddb uploaded
(https://launchpad.net/ubuntu/+source/libmaxminddb/1.4.2-0ubuntu1)
- seed change applied
(https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu/+merge/380547)
--
You received
nginx FFe bug for the demotion of libnginx-mod-http-geoip:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1867150
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
== MIR for python-geoip2 bug task ==
Availability:
The package must already be in the Ubuntu universe, and must build for the
architectures it is designed to work on.
- the package is in universe and is an arch all package.
Rationale:
There are two main reasons for this MIR:
- python-geoip for
Adding a task for release notes where we need to document the following
upgrade scenario (and maybe others):
a) Since nginx-core dropped the dependency on libnginx-mod-http-geoip,
an "apt autoremove" might suggest that libnginx-mod-http-geoip can be
removed. If this happens, and there are still
I have a debdiff[1] from Teward to drop libnginx-mod-http-geoip from
nginx-core, which would allow us to demote libnginx-mod-http-geoip to
universe, and thus demote libgeoip(1) too. @cpaelzer, would that satisfy
the requirements?
In the meantime I'll go ahead and prepare nginx packages with this
How about we demote libnginx-mod-http-geoip to universe? Given:
- nginx upstream isn't interested in switching to geoip2 (libbaxminddb). So
much that ubuntu went to great lengths to add a module to support it.
- nginx is relying on obsolete geoip1 library (maxmind, the upstream, calls it
For nginx, I'm unable to push to a new repo in lp at the moment[1], but
the diff is simple:
commit 34f9c1428d2d4eeab01f04e92e54bf311fa859b8 (HEAD ->
focal-nginx-geoip2-in-main)
Author: Andreas Hasenack
Date: Wed Mar 11 10:35:00 2020 -0300
* d/control: have nginx-core pull in the geoip2
Added an nginx task to this bug for the work needed on that package.
This is not about MIR nginx.
** Also affects: nginx (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nginx (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: nginx (Ubuntu)
17 matches
Mail list logo
