Merge ~bryce/ubuntu/+source/nginx:merge-v1.22.0-1-kinetic into ubuntu/+source/nginx:ubuntu/devel
Status: | Merged |
---|---|
Merge reported by: | Bryce Harrington |
Merged at revision: | 85684fad836080922d74619f82ec0a57f6a41229 |
Proposed branch: | ~bryce/ubuntu/+source/nginx:merge-v1.22.0-1-kinetic |
Merge into: | ubuntu/+source/nginx:ubuntu/devel |
Diff against target: |
34 lines (+7/-3) 2 files modified
debian/changelog (+7/-0) debian/control (+0/-3) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Christian Ehrhardt (community) | Needs Information | ||
Canonical Server Reporter | Pending | ||
git-ubuntu import | Pending | ||
Review via email: mp+428193@code.staging.launchpad.net |
Description of the change
nginx 1.22.0 introduces a new binary, nginx-dev, into the main archive. This pulls in various dependencies, including three items from universe. This causes a migration failure.
Since nginx-dev is new, no risk of regression. I considered instead of dropping the packages, making them Suggests, however looking at how dovecot and apache handle their -dev packages it seems more typical to just drop the problematic universe packages. Appreciate other opinions on this though.
quilt has been in universe since xenial at least, and I don't think any -dev packages include it, so I wonder if Debian could drop that too. The other two packages probably go along with other parts of our delta, so would stay on our end.
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
Hi Bryce,
1. quilt would not end up in the final dependencies I guess - would it?
If not it is fine to keep it around at build time.
The other two libgd-dev and libgeoip-dev make sense
2. nginx-dev since nothing is depending on it, there is some magic /git.launchpad. net/~ubuntu- core-dev/ ubuntu- seeds/+ git/ubuntu/ tree/supported# n112
Any package that is -dev, -doc, ... of a source in main is also included
automatically into main.
That often works fine, but if it causes trouble - for example due
to dependencies - you can exclude it via
https:/
That would be independent to this merge.
I feel I struggle to explain, is that sufficient to go forward?