←back to thread

283 points move-on-by | 1 comments | | HN request time: 0.383s | source
Show context
roelschroeven ◴[] No.45220367[source]
> The worst part about this is that it didn't get so much as a mention in the Debian 13 release notes. I read through that document before going for it and never encountered it. Indeed, even now, you won't find "tzdata" or "zone" in it.

I had another issue during my upgrade to Debian 13 that also wasn't mentioned in the release notes. I filed a bug report, but I was told that the issue was not important enough to put in the release notes, and I should have instead more closely read NEWS.Debian of the package. So I don't really know anymore what the "Issues to be aware of" chapter in the release notes is for, because apparently it's only a small selection of issues you need to be aware of.

replies(2): >>45221226 #>>45221621 #
styanax ◴[] No.45221621[source]
Sharing undocumented gotcha: nginx default config (/etc/nginx/nginx.conf) now has `server_tokens off` set with a comment that it's "common practice" (agreed). This is not in upstream's git version of the file[1], I therefore presume it's a Debian maintainer change.

The operational upgrade failure is if you have any existing drop-in config that sets `server_tokens off` already a hard fail Nginx error about duplicated keywords will occur, causing the apt process to exit with failure code(s) during the standard upgrade process.

[1] https://github.com/nginx/nginx/blob/master/conf/nginx.conf

replies(1): >>45224213 #
1. JdeBP ◴[] No.45224213[source]
Tip: Debian provides browsable source repositories so it is usually easy to find out whether something is a local Debian change.

* https://packages.debian.org/source/sid/nginx

* https://salsa.debian.org/nginx-team/nginx/-/commit/3e7838a6b...

* https://salsa.debian.org/nginx-team/nginx/-/merge_requests/8...