forked from NixOS/nixpkgs
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] master from NixOS:master #151
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nginx adds a `content-type: application/octet-stream` header by default, and `add_header` does not supplant it. By setting `default_type` instead we avoid the extraneous header.
Change-Id: I5d8efc99cf565b68279458a86977026c57a18c46
Change-Id: I14500fc1711a018b03d1ddcf3acc108ee3f731dc
Change-Id: I601e71c15e80a1cc8aa86cfa56b1ed5b1ea7ec52
Fixes security issues MMSA-2023-00242, MMSA-2023-00240, MMSA-2023-00246 and MMSA-2023-00203. Changelog: https://docs.mattermost.com/install/self-managed-changelog.html#release-v8-1-extended-support-release
This will allow buliding bootstrap tools for platforms with non-default libcs, like *-unknown-linux-musl. This gets rid of limitedSupportSystems/systemsWithAnySupport. There was no need to use systemsWithAnySupport for supportDarwin, because it was always equivalent to supportedSystems for that purpose, and the only other way it was used was for determining which platforms to build the bootstrap tools for, so we might as well use a more explicit parameter for that, and then we can change how it works without affecting the rest of the Hydra jobs. Not affecting the rest of the Hydra jobs is important, because if we changed all jobs to use config triples, we'd end up renaming every Hydra job. That might still be worth thinking about at some point, but it's unnecessary at this point (and would be a lot of work). I've checked by running nix-eval-jobs --force-recurse pkgs/top-level/release.nix that the actual bootstrap tools derivations are unaffected by this change, and that the only other jobs that change are ones that depend on the hash of all of Nixpkgs. Of the other jobset entrypoints that end up importing pkgs/top-level/release.nix, none used the limitedSupportedSystems parameter, so they should all be unaffected as well.
This will allow us to regenerate our woefully out-of-date aarch64-unknown-linux-gnu musl bootstrap tools, which can't compile lots of modern code. We could technically also do i686-unknown-linux-musl bootstrap tools, but I don't know if there's demand for that, so it's best to wait and see if somebody asks for it before we commit Hydra to it.
containerlab: 0.45.1 -> 0.46.0
apktool: 2.8.1 -> 2.9.0
fzf-make: 0.7.0 -> 0.8.0
poethepoet: 0.24.0 -> 0.24.1
leptosfmt: 0.1.14 -> 0.1.15
tui-journal: 0.3.2 -> 0.3.3
cargo-binstall: 1.4.2 -> 1.4.3
zulu17, zulu21: init
wine-staging: 8.17 -> 8.17.1
liblinphone: add back QR support
python310Packages.pglast: 5.4 -> 5.5
iosevka: 27.1.0 -> 27.2.0
terragrunt: 0.51.7 -> 0.52.0
photoqt: 3.3 -> 3.4
dxvk: migrate to by-name
tfupdate: 0.7.2 -> 0.8.0
searxng: move to pkgs/by-name, unstable-2023-07-19 -> unstable-2023-10-01
invidious: unstable-2023-09-18 -> unstable-2023-10-07
passky-desktop: 7.1.0 -> 8.1.1
gbar: init at unstable-2023-09-21
flow: 0.217.2 -> 0.218.0
python3Packages.irctokens: 2.0.1 -> 2.0.2, python3Packages.ircstates: 0.11.8 -> 0.12.1, python3Packages.ircrobots: 0.4.6 -> 0.6.6
flyctl: 0.1.102 -> 0.1.104
docker-distribution: 2.8.2 -> 2.8.3
fwupd: 1.9.5 -> 1.9.6
nixos/locate: rename option `locate` -> `package`
prometheus-pgbouncer-exporter: vendorSha256 -> vendorHash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )