Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-11-11 | Merge staging-next into staging | github-actions[bot] | 1 | -1/+12 | |
2023-11-11 | Merge master into staging-next | github-actions[bot] | 1 | -1/+12 | |
2023-11-09 | lib.systems: elaborate Rust metadata | Alyssa Ross | 1 | -3/+2 | |
We need this stuff to be available in lib so make-derivation.nix can access it to construct the Meson cross file. This has a couple of other advantages: - It makes Rust less special. Now figuring out what Rust calls a platform is the same as figuring out what Linux or QEMU call it. - We can unify the schema used to define Rust targets, and the schema used to access those values later. Just like you can set "config" or "system" in a platform definition, and then access those same keys on the elaborated platform, you can now set "rustcTarget" in your crossSystem, and then access "stdenv.hostPlatform.rustcTarget" in your code. "rustcTarget", "rustcTargetSpec", "cargoShortTarget", and "cargoEnvVarTarget" have the "rustc" and "cargo" prefixes because these are not exposed to code by the compiler, and are not standardized. The arch/os/etc. variables are all named to match the forms in the Rust target spec JSON. The new rust.target-family only takes a list, since we don't need to worry about backwards compatibility when that name is used. The old APIs are all still functional with no warning for now, so that it's possible for external code to use a single API on both 23.05 and 23.11. We can introduce the warnings once 23.05 is EOL, and make them hard errors when 23.11 is EOL. | |||||
2023-11-07 | apt-cacher-ng: fix build for glibc >= 2.38 | Yongun Seong | 1 | -1/+12 | |
2023-11-04 | Merge branch 'master' into staging-next | Weijia Wang | 1 | -2/+2 | |
2023-11-04 | tengine: 3.0.0 -> 3.1.0 | R. Ryantm | 1 | -2/+2 | |
2023-11-02 | Merge master into staging-next | github-actions[bot] | 1 | -2/+2 | |
2023-11-02 | lighttpd: 1.4.72 -> 1.4.73 | R. Ryantm | 1 | -2/+2 | |
2023-10-31 | Merge master into staging-next | github-actions[bot] | 1 | -1/+1 | |
2023-10-31 | Merge pull request #262254 from Artturin/nginxsandboxrem | Artturi | 1 | -1/+1 | |
2023-10-29 | Merge master into staging-next | github-actions[bot] | 1 | -3/+3 | |
2023-10-29 | Merge pull request #262238 from avdv/bazel-6.4 | Uri Baghin | 1 | -3/+3 | |
bazel_6: 6.3.2 -> 6.4.0 | |||||
2023-10-29 | envoy: Update hash after bazel_6 upgrade | Claudio Bley | 1 | -3/+3 | |
2023-10-28 | Merge master into staging-next | github-actions[bot] | 2 | -10/+16 | |
2023-10-28 | Merge pull request #263793 from fleaz/update_nginx-videothumb | Martin Weinelt | 1 | -6/+8 | |
nginxModules.videothumb-extractor: unstable -> 1.0.0 and switch to ffmpeg-headless | |||||
2023-10-28 | Merge pull request #263644 from fleaz/update_nginx-vod | Martin Weinelt | 1 | -2/+6 | |
nginxModules.vod: 1.31 -> 1.32 and patch MAX_CLIPS | |||||
2023-10-28 | Merge pull request #262736 from LeSuisse/jetty-12.0.2 | Robert Scott | 1 | -2/+2 | |
jetty: 12.0.1 -> 12.0.2 | |||||
2023-10-27 | nginxModules: Switch from ffmpeg to ffmpeg-headless | fleaz | 1 | -3/+3 | |
2023-10-27 | nginxModules.video-thumbextractor: 92b8064 -> 1.0.0 | fleaz | 1 | -4/+6 | |
Diff: https://github.com/wandenberg/nginx-video-thumbextractor-module/compare/92b8064...e81f850 | |||||
2023-10-26 | nginxModules.vod: Patch MAX_CLIPS variable | fleaz | 1 | -1/+5 | |
The old limit was only 128 and this breaks some applications like e.g. Frigate where playlists become bigger than that. According to upstream you should just change the variable yourself if needed. See this issue: https://github.com/kaltura/nginx-vod-module/issues/238 | |||||
2023-10-26 | nginxModules.vod: 1.31 -> 1.32 | fleaz | 1 | -2/+2 | |
Changelog: https://github.com/kaltura/nginx-vod-module/compare/1.31...1.32 | |||||
2023-10-26 | Merge branch 'staging' into staging-next | Vladimír Čunát | 1 | -1/+1 | |
2023-10-25 | Merge pull request #262718 from LeSuisse/trafficserver-9.2.3 | Robert Scott | 1 | -2/+2 | |
trafficserver: 9.2.2 -> 9.2.3 | |||||
2023-10-25 | Merge pull request #263304 from trofi/nginxMainline-update | Maximilian Bosch | 1 | -2/+2 | |
nginxMainline: 1.25.2 -> 1.25.3 | |||||
2023-10-25 | nginxMainline: 1.25.2 -> 1.25.3 | Sergei Trofimovich | 1 | -2/+2 | |
Changes: https://nginx.org/en/CHANGES | |||||
2023-10-23 | Merge pull request #257336 from ↵ | Mario Rodas | 1 | -6/+7 | |
trofi/nginxModules.http_proxy_connect_module-update nginxModules.http_proxy_connect_module_v{24,25}: new modules for up t… | |||||
2023-10-23 | Merge staging-next into staging | github-actions[bot] | 1 | -2/+2 | |
2023-10-23 | nixosTests.nginx-sandbox: remove broken test and move the sandboxing test to ↵ | Artturin | 1 | -1/+1 | |
the openresty test nginx lua needs resty the enableSandbox option of nginx was removed in 535896671b66d308df3ce467c94f8a9fecfdffea the test fails with ``` vm-test-run-nginx-sandbox> machine # [ 47.753580] nginx[1142]: nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) vm-test-run-nginx-sandbox> machine # [ 47.756064] nginx[1142]: nginx: [alert] failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: module 'resty.core' not found: vm-test-run-nginx-sandbox> machine # [ 57.911766] systemd[1]: Failed to start Nginx Web Server. ``` | |||||
2023-10-23 | Merge pull request #262613 from r-ryantm/auto-update/unit | OTABI Tomoya | 1 | -2/+2 | |
unit: 1.31.0 -> 1.31.1 | |||||
2023-10-22 | jetty: 12.0.1 -> 12.0.2 | Thomas Gerbet | 1 | -2/+2 | |
Fixes CVE-2023-44487. https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.2 | |||||
2023-10-22 | trafficserver: 9.2.2 -> 9.2.3 | Thomas Gerbet | 1 | -2/+2 | |
Fixes CVE-2023-39456, CVE-2023-41752 and CVE-2023-44487. Changelog: https://raw.githubusercontent.com/apache/trafficserver/9.2.x/CHANGELOG-9.2.3 | |||||
2023-10-22 | Merge staging-next into staging | github-actions[bot] | 1 | -2/+2 | |
2023-10-22 | Merge pull request #262329 from SuperSandro2000/nginx-zstd-0-1-0 | Ryan Lahfa | 1 | -2/+2 | |
2023-10-21 | unit: 1.31.0 -> 1.31.1 | R. Ryantm | 1 | -2/+2 | |
2023-10-21 | Merge staging-next into staging | github-actions[bot] | 2 | -3/+3 | |
2023-10-21 | Merge pull request #257262 from dongcarl/2023-09-nginx-fixes | Ryan Lahfa | 1 | -1/+1 | |
nixos/nginx: Allow empty port for listen directive (for unix socket) | |||||
2023-10-21 | tomcat-native: 2.0.5 -> 2.0.6 | R. Ryantm | 1 | -2/+2 | |
2023-10-21 | Merge staging-next into staging | github-actions[bot] | 3 | -50/+4 | |
2023-10-20 | lighttpd: re-enable remaining disabled tests | Bjørn Forsman | 1 | -6/+0 | |
All tests work now. | |||||
2023-10-20 | lighttpd: 1.4.71 -> 1.4.72 | Bjørn Forsman | 2 | -42/+2 | |
The patch to disable legacy crypt tests (which were broken for us) isn't needed anymore, so remove it. | |||||
2023-10-20 | Merge pull request #262075 from ivan/apachehttpd-2.4.58 | Aaron Andersen | 1 | -2/+2 | |
apacheHttpd: 2.4.57 -> 2.4.58 | |||||
2023-10-20 | nginxModules.zstd: 25d88c262be47462cf90015ee7ebf6317b6848f9 -> 0.1.0 | Sandro Jäckel | 1 | -2/+2 | |
2023-10-20 | Merge staging-next into staging | github-actions[bot] | 1 | -4/+12 | |
2023-10-20 | Merge pull request #258652 from trofi/nginx-install-manpages | Artturi | 1 | -4/+12 | |
2023-10-19 | apacheHttpd: 2.4.57 -> 2.4.58 | Ivan Kozik | 1 | -2/+2 | |
2023-10-17 | Merge staging-next into staging | github-actions[bot] | 1 | -30/+0 | |
2023-10-17 | go-camo: migrate to by-name | Stanisław Pitucha | 1 | -30/+0 | |
2023-10-14 | Merge staging-next into staging | github-actions[bot] | 5 | -63/+170 | |
2023-10-13 | envoy: 1.26.4 -> 1.27.1 | Luke Granger-Brown | 5 | -63/+170 | |
2023-10-10 | Merge staging-next into staging | github-actions[bot] | 1 | -2/+2 | |