about summary refs log tree commit diff
path: root/nixpkgs
Commit message (Collapse)AuthorAge
...
* linux/hardened/patches/4.14: 4.14.185.a -> 4.14.187.aTim Steinbach2021-01-06
| | | | (cherry picked from commit 0ff4f8095a236fb70c939e0f8a91e2d2327ead70)
* linux/hardened/patches/5.6: 5.6.18.a -> 5.6.19.aTim Steinbach2021-01-06
| | | | (cherry picked from commit 9507dfbe8201340d2603040fdeb0f2f860ec405e)
* linux/hardened/patches/5.4: 5.4.46.a -> 5.4.48.aTim Steinbach2021-01-06
| | | | (cherry picked from commit 34393bcf19e3f3e50571ad7b81fe8eeb636c652e)
* linux/hardened/patches/4.19: 4.19.128.a -> 4.19.129.aTim Steinbach2021-01-06
| | | | (cherry picked from commit d6ea499873f7b14fddd190e213919d1b0c3cd4ec)
* linux/hardened/patches/4.14: 4.14.184.a -> 4.14.185.aTim Steinbach2021-01-06
| | | | (cherry picked from commit 91b3fe57531356627d668c50c3da301fafe09520)
* emacsPackages.melpa-packages: 2020-12-09Alyssa Ross2021-01-06
| | | | (cherry picked from commit f493e6264372fd420a9d72d75136a4564e9aca48)
* emacsPackages.org-packages: 2020-12-09Alyssa Ross2021-01-06
| | | | (cherry picked from commit 33ee2f22c633a82be3c9a72770297698b79ebaab)
* emacsPackages.elpa-packages: 2020-12-09Alyssa Ross2021-01-06
| | | | (cherry picked from commit a43c6fc02596c36e7c4aae062a14f6b1bd655ebf)
* emacsWithPackages: don't tell sub-Emacs about pkgsAlyssa Ross2021-01-06
| | | | | | | | | | | | | | If I'm running an Emacs executable from emacsWithPackages as my main programming environment, and I'm hacking on Emacs, or the Emacs packaging in Nixpkgs, or whatever, I don't want the Emacs packages from the wrapper to show up in the load path of that child Emacs. It results in differing behaviour depending on whether the child Emacs is run from Emacs or from, for example, an external terminal emulator, which is very surprising. To avoid this, pass another environment variable containing the wrapper site-lisp path, and use that value to remove the corresponding entry in EMACSLOADPATH, so it won't be propagated to child Emacsen.
* emacsWithPackages: mutate EMACSLOADPATH correctlyAlyssa Ross2021-01-06
| | | | | | | | | | | | | | | | | | | | | An empty entry in EMACSLOADPATH gets filled with the default value. This is presumably why the wrapper inserted a colon after the entry it added for the dependencies. But this naive approach wasn't always correct. For example, if the user ran emacs with EMACSLOADPATH=foo, the wrapper would insert the default value (by adding the trailing `:') even though the user was trying to expressly opt out of it. To do this correctly, here I've replaced makeWrapper with a bespoke script that will actually parse the EMACSLOADPATH provided in the environment (if given), and insert the wrapper's load path just before the default value. If EMACSLOADPATH is given but contains no default value, we respect that and don't add the wrapped dependencies at all. If no EMACSLOADPATH is given, we insert the wrapped dependencies before the default value, just like before. In this way, the wrapped Emacs should now behave as if the wrapped dependencies were part of Emacs's default load-path value.
* nixos/mailman: add services.mailman.serveAlyssa Ross2021-01-06
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: add mailman-web userAlyssa Ross2021-01-06
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/uwsgi: add extraArgs optionAlyssa Ross2021-01-06
| | | | I need this to be able to make my uwsgi socket group-readable.
* nixos/mailman: add mta.configurationAlyssa Ross2021-01-06
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* spamassassin: 3.4.3 -> 3.4.4Alyssa Ross2021-01-06
|
* nixos/fcgiwrap: don't run as rootAlyssa Ross2021-01-02
| | | | | | | | | | | | Previously, fcgiwrap was run as root by default. This was bad because it meant every CGI script was run as root. Changed to set DynamicUser, so instead of having access to everything, CGI scripts will now by default only have access to things that are world-readable. This will probably break things for users, but since we can't know what they want to allow their CGI scripts access to they'll have to fix that themselves, because it would be irresponsible to leave this defaulting to root.
* nixos/nginx: allow overriding fastcgi paramsAlyssa Ross2021-01-02
| | | | | | | | | | | | | | | | | | | | | | By default in Nginx, if you want to override a single fastcgi_param, you have to override all of them. This is less of a big deal if you're editing the Nginx configuration directly, but when you're generating the Nginx configuration with Nix it can be very annoying to bloat your configuration repeating the default values of FastCGI parameters every time. This patch adds a fastcgiParams option to Nginx locations. If any parameters are set through this, all the default values will be included as well, so only the ones that are changing need to be supplied. There's no way to use fastcgiParams to actually override all parameters if that's what you want, but I think that's a niche use case and it's still possible using extraConfig, which up until now was the only option Nginx allows the fastcgi_param directive in http and server scopes as well as location, but here I only support location. It would be possible to support the others, but I don't think it's worth it. It would be a possible future enhancement if somebody has a need for it.
* alacritty: 0.6.0-rc1 -> 0.6.0Cole Helbling2021-01-02
| | | | | https://github.com/alacritty/alacritty/blob/master/CHANGELOG.md#060 (cherry picked from commit 6cea12ccff6e279f0bc1f91aa6a898d642e03320)
* alacritty: 0.5.0 -> 0.6.0-rc1Doron Behar2021-01-02
| | | | (cherry picked from commit f0250226b279983c07cc33c06d0309903dfc1df9)
* nixos/mailman: refactor Hyperkitty's periodic jobsAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: quote some variablesAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: only make hyperkitty service when onAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: add mailman groupAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: fix example formattingAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: make mailman log to /var/logAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: better mailman-web-setup descriptionAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: rename mailman-web.serviceAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: one big systemd.services attrsetAlyssa Ross2020-12-11
| | | | | | | | | Adapted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream. The conditional was added for the case where the directory did not yet exist, and quotes were changed to the more robust escapeShellArg.
* nixos/mailman: one big systemd.services attrsetAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: make mailman-web log to journalAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* nixos/mailman: remove webRoot optionAlyssa Ross2020-12-11
| | | | | | Extracted from b478e0043c53964c99cc9a145c155a673af3c7d8 ("nixos/mailman: refactor"), to bring myself closer to current upstream.
* libhugetlbfs: init at 2.22Alyssa Ross2020-12-11
| | | | (cherry picked from commit 5e7d581ffdba220d088ed92f382a41acb37670e1)
* weechatScripts.colorize_nicks: 26 -> 27Alyssa Ross2020-12-04
|
* weechat: 2.9 -> 3.0Martin Weinelt2020-12-04
| | | | (cherry picked from commit 8928b4bfe9c73e293b32c5a5d138a35817e97d94)
* weechat*: remove myself as maintainerMaximilian Bosch2020-12-04
| | | | | | I don't use this anymore, so I don't bring any value here. (cherry picked from commit 309bcc4d09e6bfabf1ad864b9060d2a4b7411619)
* weechat: 2.8 -> 2.9Martin Weinelt2020-12-04
| | | | (cherry picked from commit c3bf59eefb426ce2dfcccd5da069037de07f4d8c)
* thunderbird: fix build with clang > 7Alyssa Ross2020-12-04
| | | | | | --with-clang-path is unsupported when doing the whole build with Clang. I don't understand why this isn't a problem with clang 7. Maybe it's too old for whatever uses --with-clang-path?
* llvmPackages_latest: llvmPackages_10 -> llvmPackages_11Michael Weiss2020-12-04
| | | | (cherry picked from commit 51e55942cc43917cd57adf94e78b5574ff8400b9)
* rust-cbindgen: 0.14.4 -> 0.15.0R. RyanTM2020-11-27
| | | | (cherry picked from commit 37677080bec5cd26668c9e5f36f0e5787c1aebe3)
* lldb_{10, 11}: polish the cmakeFlags (#100070)Gabor Greif2020-11-27
| | | | | | disable RTTI in a more idiomatic way (cherry picked from commit 35f62abdf86b408daaa6512afea7ae51c13ac298)
* clang_11: forward-port #91293Gabor Greif2020-11-27
| | | | (cherry picked from commit 7a30df9225e3c47080744535ccbb0a1202b36a3a)
* llvmPackages_11: 11.0.0rc5 -> 11.0.0Gabor Greif2020-11-27
| | | | | | | | | | https://lists.llvm.org/pipermail/release-testers/2020-October/001377.html https://lists.llvm.org/pipermail/llvm-announce/2020-October/000089.html Fixes: - builds on Darwin - builds `libcxx` on Linux (cherry picked from commit cffb7cfbf755e5166a3a41594978e838942ef17f)
* llvmPackages_11.compiler-rt: enable support for i486 i586 i686Holger Wünsche2020-11-27
| | | | | | | | | compiler-rt (and as a result clang) can't be build for i686 (as noticed here: #99984). The patch adds the required variables and should result in the same behavior as in the nixpkgs-llvm10. It essentially forces to use i386 buildins when using i486, i586 or i686, which are not supported. Fixes #100392 (cherry picked from commit 6948875e73a855b8a0c665301576dcd9653b9e15)
* gcc: fix manpage symlinks when arch tuple is in the file nameAlexandria Corkwell2020-11-27
| | | | | | | | | | | | | | In some cases, such as when building cross compilers, the binaries and manpages contain the target architecture tuple, such as `i686-w64-mingw32-g++.1`. Ensure the symlink created to save space with the duplicated manpage (`g++.1 -> gcc.1`) properly handles such cases and generates symlinks such as `i686-w64-mingw32-g++.1 -> i686-w64-mingw32-gcc.1`. Previously in such cases, a broken `gcc.1` link would be created instead. (cherry picked from commit eed46887ca8b4b4f0fe473e32e042c0ee3a6eee5)
* buildRustCrate: fix target config environment variables on 32-bit ARMBen Wolsieffer2020-11-27
| | | | (cherry picked from commit f0fdecfbb45c74bfb6f46017563e7ec941b604e9)
* llvm_11: link to the llvm compiler-rt share directory from the wrapper (#100190)TredwellGit2020-11-27
| | | | | | | | | A port of #85925 for LLVM 11 to enable CFI for Chromium. This is required for features such as `-fsanitize=cfi` that (by default) load the file `…/resource-root/share/cfi_blacklist.txt`. (cherry picked from commit 03dd1b355b6c7379500becdf170850a5a1dfea5a)
* firefox: fix build with clangAlyssa Ross2020-11-27
| | | | > ERROR: --with-clang-path is not valid when the target compiler is clang
* firefox: disable LTO by default due to segfaults with waylandAndreas Rammhold2020-11-27
| | | | | | | | | | As discussed in #101429 firefox 82 started crashing when used with wayland. A brief investigation showed that this appears to be rooted within the LTO support that was recently added to the package. For the time being, until someone figures out where the crashes are coming from, we can just disable LTO. (cherry picked from commit bca15c82d89f37f5cb6cacd9b632edff6979e131)
* firefox: 78.3.1esr -> 78.4.0esrAndreas Rammhold2020-11-27
| | | | (cherry picked from commit 6057ea490f185e24ca7b3db564c7a6e8c0a67300)
* firefox: 81.0.2 -> 82.0Andreas Rammhold2020-11-27
| | | | (cherry picked from commit ae2f5cccbb726ad864586b662b5656f73393a3a3)
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-26 08:43:07 +0000