[SRU] [20.04] Update NGINX version string to 1.18.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nginx (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* NGINX 1.17.x has been retired in favor of 1.18.x branch
* NGINX 1.18.0 is directly based off of 1.17.10 (already in the repositories) with no other major changes but a version string change and no functional differences
* The server team in the past several LTS cycles has wanted to get latest stable into the LTS as soon as it was able. While attempted to get in before release, it was NACK'd and requested to SRU the version string change.
[Test Case]
* N/A
[Regression Potential]
* None - no code changes except a version string change.
[Other Info]
* During Focal cycle, we have always planned to update nginx to 1.18.0, or SRU it soon after Focal release. This finishes off this plan to get nginx 1.17.0 stable into the repositories.
* This only changes the version string upstream. Other changes are a result of post-Focal configuration issue discoveries, or an updated patch due to the version bump.
tags: | added: verification-done-focal |
Changed in nginx (Ubuntu): | |
status: | Confirmed → Fix Released |
$ git log --pretty=oneline release- 1.17.10. .release- 1.18.0 baf7aded3319b0d ec433b2461 (tag: release-1.18.0) nginx-1. 18.0-RELEASE 054f3bbb23a44ef 2576278f63 Stable branch. 7f01671cd969c90 9dee5e2cde release-1.17.10 tag
e6b3a11581a8040
6acdee5e3213fc6
3ba88365b5acef1
I agree there aren't any changes in between 1.17.10 and 1.18.0.
Unsure about the change though.
nginx dfsg1.orig- 1) certbot- nginx (0.39.0-1)
Reverse Depends: diaspora-common (0.7.6.1+debian1)
Reverse Depends: fusiondirectory (1.3-2)
Reverse Depends: kopano-webapp-nginx (3.5.14+
Reverse Depends: python3-
Reverse Depends: rainloop (1.12.1-2)
as long as there are no hard dependencies on versioning (wonder if you're thinking in changing deb version as well)... Ubuntu SRU team would make the last call anyway.
Let me know if you're pursuing this, I'm flagging as a server team low priority queue item for now.
Thanks @teward!