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 geoip configuration directives, nginx will fail to restart. Note that this would also happen had we replaced libnginx-mod-http-geoip with libnginx-mod-http-geoip2, as the configuration directives are different
b) If someone has just main enabled, with nginx-code and libnginx-mod-http-geoip installed, and release upgrades to focal, libnginx-mod-http-geoip won't be updated because it's in focal/universe.
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 geoip configuration directives, nginx will fail to restart. Note that this would also happen had we replaced libnginx- mod-http- geoip with libnginx- mod-http- geoip2, as the configuration directives are different
b) If someone has just main enabled, with nginx-code and libnginx- mod-http- geoip installed, and release upgrades to focal, libnginx- mod-http- geoip won't be updated because it's in focal/universe.