| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Merge master into staging-next | nixpkgs-ci[bot] | 2025-04-05 | 1 | -0/+6 |
| |\ |
|
| | * | rubyPackages.ovirt-engine-sdk: fix build | Kirill Radzikhovskyy | 2025-04-05 | 1 | -0/+6 |
| * | | Merge master into staging-next | nixpkgs-ci[bot] | 2025-04-04 | 1 | -7/+2 |
| |\| |
|
| | * | rubyPackages.taglib-ruby: use taglib v2 | Avraham Appel | 2025-04-03 | 1 | -2/+2 |
| | * | rubyPackages.iconv: remove patch for v1.1.0 | Avraham Appel | 2025-04-03 | 1 | -5/+0 |
| * | | Merge remote-tracking branch 'upstream/staging-next' into staging | Silvan Mosberger | 2025-04-02 | 1 | -240/+520 |
| |\| |
|
| | * | treewide: Format all Nix files•••Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](https://github.com/NixOS/nixpkgs/tree/8616af08d915377bd930395f3b700a0e93d08728/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
| Silvan Mosberger | 2025-04-01 | 1 | -240/+520 |
| * | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-03-28 | 1 | -23/+0 |
| |\| |
|
| | * | rubyPackages.libv8: drop•••Project was marked as abandoned, and Python2 is EOL
| Benjamin Sparks | 2025-03-21 | 1 | -23/+0 |
| * | | postgresql: replace pg_config with custom script•••By replacing upstream's pg_config binary with a shell script, we:
- gain the ability to run pg_config easily when cross-compiling,
- can remove the fake pg_config in the default output,
- can remove the pg_config wrapper script dealing with special cases.
Some 20 years ago, pg_config *was* a shell script upstream, too. It was
changed to a binary, when it was made "relocatable", so it would return
paths depending on the location of the "postgres" binary. However, this
is exactly the thing that just hurts us in nixpkgs - we don't want those
paths to change, we want them to always point at the right outputs. By
writing the script ourselves, this becomes a lot less painful.
This approach means more lines of codes, but all of them are dead simple
and we have a lot less complexity overall.
Additionally, pg_config is now made a separate derivation, only exposed
as "postgresql.pg_config". This has the nice side-effect, that all users
of postgresql and libpq in nixpkgs must be very *explicit* about their
dependency on pg_config. This gives a lot more visibility into the state
of affairs regarding pkg-config support for libpq, which ultimately is
the much better solution.
| Wolfgang Walther | 2025-03-21 | 1 | -1/+1 |
| |/ |
|
| * | zammad: move gem config to default gem config | Sandro Jäckel | 2025-03-12 | 1 | -1/+20 |
| * | Merge master into staging-next | nixpkgs-ci[bot] | 2025-03-09 | 1 | -0/+4 |
| |\ |
|
| | * | ruby-modules/gem-config: patch mathematical gem for Darwin (#384539) | Sandro | 2025-03-09 | 1 | -0/+4 |
| | |\ |
|
| | | * | ruby-modules/gem-config: patch mathematical gem for Darwin•••Signed-off-by: Qiming Chu <cchuqiming@gmail.com>
| Qiming Chu | 2025-02-23 | 1 | -0/+4 |
| * | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-02-27 | 1 | -10/+8 |
| |\| | |
|
| | * | | gitlab: 17.8.2 -> 17.9.1•••https://about.gitlab.com/releases/2025/02/20/gitlab-17-9-released/
https://about.gitlab.com/releases/2025/02/26/patch-release-gitlab-17-9-1-released/
* update promeheus-client-mmap to 1.2.9 to fix build (1.2.8 didn't include Cargo.lock)
* remove custom patches in gitlab-container-registry as they are now included
* remove openssl replacement, as it's no longer effective
| Leona Maroni | 2025-02-26 | 1 | -10/+8 |
| | |/ |
|
| * / | taglib: 1.13.1 -> 2.0.2, taglib_1: init at 1.13.1 | OPNA2608 | 2025-02-11 | 1 | -2/+2 |
| |/ |
|
| * | Merge branch 'staging' into staging-next•••Conflicts:
pkgs/by-name/ba/bacon/package.nix
pkgs/by-name/be/beancount-language-server/package.nix
pkgs/by-name/fl/flake-edit/package.nix
pkgs/by-name/fw/fw/package.nix
pkgs/by-name/im/impression/package.nix
pkgs/by-name/in/inori/package.nix
pkgs/by-name/pi/pika-backup/package.nix
pkgs/by-name/ri/rip2/package.nix
pkgs/by-name/sn/sniffnet/package.nix
pkgs/by-name/sy/syndicate_utils/package.nix
pkgs/development/tools/misc/texlab/default.nix
In the cases where an update collided with cargoHash change,
I took the hash from the update.
| Vladimír Čunát | 2025-01-27 | 1 | -3/+3 |
| |\ |
|
| | * | libpq: init at 17.2•••Resolves #61580
| Wolfgang Walther | 2025-01-19 | 1 | -3/+3 |
| * | | defaultGemConfig.prometheus-client-mmap: fetchCargoTarball -> fetchCargoVendor•••Cargo 1.84.0 seems to have changed the output format of cargo vendor
again, once again invalidating fetchCargoTarball FOD hashes. It's
time to fix this once and for all, switching across the board to
fetchCargoVendor, which is not dependent on cargo vendor's output
format.
| Alyssa Ross | 2025-01-26 | 1 | -4/+4 |
| |/ |
|
| * | ruby-grpc: Only apply the GCC 14 patch if it’s not upstream (#368732) | Gaétan Lepage | 2025-01-15 | 1 | -2/+4 |
| |\ |
|
| | * | ruby-grpc: Only apply the GCC 14 patch if it’s not upstream•••It was upstreamed in v1.65.0-pre1~90; attempting to apply it again
after that causes errors.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
| Anders Kaseorg | 2025-01-15 | 1 | -2/+4 |
| * | | gitlab: update prometheus-client-mmap gem to fix aarch64 (#369636) | Leona Maroni | 2025-01-04 | 1 | -3/+6 |
| |\ \ |
|
| | * | | gitlab: update prometheus-client-mmap gem to fix aarch64 | Alexander Sieg | 2025-01-04 | 1 | -3/+6 |
| | |/ |
|
| * / | timetrap: fix build | Weijia Wang | 2024-12-31 | 1 | -0/+4 |
| |/ |
|
| * | ruby-grpc: gcc-14 fixes (#367783)•••* ruby-modules/gem: don't clobber NIX_CFLAGS_COMPILE
* gem-config/grpc: apply patch for gcc-14
https://boringssl.googlesource.com/boringssl/+/c70190368c7040c37c1d655f0690bcde2b109a0d
add -Wno-error=incompatible-pointer-types to NIX_CFLAGS_COMPILE and
remove the other flags as NIX_CFLAGS_COMPILE were getting clobbered since
7121ef61da4ddd36f81480322bc2ae984c575b1d (2021) | Reno Dakota | 2024-12-25 | 1 | -10/+11 |
| * | rubyPackages.ovirt-engine-sdk: set meta.broken | Kenichi Kamiya | 2024-11-19 | 1 | -0/+1 |
| * | rubyPackages.*: Fix build with glib 2.82, clean up•••https://hydra.nixos.org/build/274401072/nixlog/1
Ugh, I am looking at glib-2.0.pc and sysprof-capture-4 is in Requires.private
so I didn't propagate that. Later I decide I will just follow 81e445e508f49daa
adding libsysprof-capture next to every usages of pcre2.
Not sure why gtk2 is still there after b95976f77c86c516, same question for pcre.
| Bobby Rong | 2024-10-14 | 1 | -39/+12 |
| * | Merge master into staging-next | github-actions[bot] | 2024-10-06 | 1 | -0/+5 |
| |\ |
|
| | * | rubyPackages.nokogiri: mark as broken for old libxml2 (#321431) | Stanisław Pitucha | 2024-10-06 | 1 | -0/+5 |
| | |\ |
|
| | | * | rubyPackages.nokogiri: mark as broken for old libxml2 | Stanisław Pitucha | 2024-06-21 | 1 | -0/+5 |
| * | | | Merge branch 'master' into staging-next | Artturin | 2024-09-25 | 1 | -29/+29 |
| |\| | |
|
| | * | | treewide: replace `stdenv.is` with `stdenv.hostPlatform.is`•••In preparation for the deprecation of `stdenv.isX`.
These shorthands are not conducive to cross-compilation because they
hide the platforms.
Darwin might get cross-compilation for which the continued usage of `stdenv.isDarwin` will get in the way
One example of why this is bad and especially affects compiler packages
https://www.github.com/NixOS/nixpkgs/pull/343059
There are too many files to go through manually but a treewide should
get users thinking when they see a `hostPlatform.isX` in a place where it
doesn't make sense.
```
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv.is" "stdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv'.is" "stdenv'.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "clangStdenv.is" "clangStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "gccStdenv.is" "gccStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenvNoCC.is" "stdenvNoCC.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "inherit (stdenv) is" "inherit (stdenv.hostPlatform) is"
fd --type f "\.nix" | xargs sd --fixed-strings "buildStdenv.is" "buildStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "effectiveStdenv.is" "effectiveStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "originalStdenv.is" "originalStdenv.hostPlatform.is"
```
| Artturin | 2024-09-25 | 1 | -29/+29 |
| * | | | rust: Write to .cargo/config.toml instead of .cargo/config•••Seeing the following new warnings pop up on stderr when cargo was bumped
to 1.78:
```
warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
```
which happens to break commitmsgfmt builds in nix (#320294).
closes #320294
| Manuel Mendez | 2024-09-11 | 1 | -1/+1 |
| |/ / |
|
| * | | treewide: fix pg_config / postgresql headers moved to dev output•••This was supposed to happen in #294504, but the commit was accidentally
left out when splitting off some libpq-related changes. Originated in
#179962, by Sandro.
Co-authored-by: Sandro Jäckel <sandro.jaeckel@gmail.com>
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
| Wolfgang Walther | 2024-08-24 | 1 | -1/+1 |
| * | | Merge pull request #330053 from reckenrode/ruby-package-fixes | Randy Eckenrode | 2024-07-30 | 1 | -5/+26 |
| |\ \ |
|
| | * | | rubyPackages.libxml-ruby: fix build on Darwin•••Darwin’s libiconv has separate outputs for the dylib and headers, so it needs to use `lib.getLib` and `lib.getDev`.
| Randy Eckenrode | 2024-07-25 | 1 | -2/+2 |
| | * | | rubyPackages.iconv: fix build on Darwin•••Darwin’s libiconv has separate outputs for the dylib and headers, so it needs to use `lib.getLib` and `lib.getDev`.
| Randy Eckenrode | 2024-07-25 | 1 | -1/+4 |
| | * | | rubyPackages.hpricot: fix build with clang 16 | Randy Eckenrode | 2024-07-25 | 1 | -0/+8 |
| | * | | rubyPackages.gtk3: fix build on Darwin and Linux•••- Add missing Ruby dependency (cairo); and
- Add missing build input (lerc).
| Randy Eckenrode | 2024-07-25 | 1 | -1/+2 |
| | * | | rubyPackages.curses: fix build with clang 16 | Randy Eckenrode | 2024-07-25 | 1 | -1/+10 |
| * | | | tree-wide: enable LTO on Darwin | Randy Eckenrode | 2024-07-20 | 1 | -4/+1 |
| * | | | Revert "rust: Write config.toml not config" | Winter | 2024-06-23 | 1 | -1/+1 |
| * | | | rust: Write to .cargo/config.toml instead of .cargo/config•••Seeing the following new warnings pop up on stderr when cargo was bumped
to 1.78:
```
warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
```
which happens to break commitmsgfmt builds in nix (#320294).
closes #320294
| Manuel Mendez | 2024-06-19 | 1 | -1/+1 |
| |/ / |
|
| * / | rubyPackages.libv8: use nodejs.libv8 | Thomas Gerbet | 2024-05-30 | 1 | -3/+3 |
| |/ |
|
| * | pkgs/development: remove unused fetchpatch arguments | Sigmanificient | 2024-05-24 | 1 | -1/+1 |
| * | rubyPackages_3_{2,3}.nokogiri: add libxml2 to darwin buildInputs; unbreak•••fix build failure on darwin:
```
checking for xmlParseDoc() in -lxml2... no
checking for xmlParseDoc() in -llibxml2... no
checking for libxml-2.0 using `pkg_config`... no
Please install either the `pkg-config` utility or the `pkg-config` rubygem.
checking for xmlParseDoc() in -lxml2... no
checking for xmlParseDoc() in -llibxml2... no
-----
extconf.rb:295:in `ensure_package_configuration'
extconf.rb:704:in `<main>'
xml2 is missing. Please locate mkmf.log to investigate how it is failing.
```
| annalee | 2024-05-13 | 1 | -2/+4 |
| * | treewide: wrapGAppsHook → wrapGAppsHook3•••This was achieved using the following command:
sd 'wrapGAppsHook\b' wrapGAppsHook3 (rg -l 'wrapGAppsHook\b')
And then manually reverted the following changes:
- alias in top-level.nix
- function name in wrap-gapps-hook.sh
- comment in postFixup of at-spi2-core
- comment in gtk4
- comment in preFixup of 1password-gui/linux.nix
- comment in postFixup of qgis/unwrapped-ltr.nix and qgis/unwrapped.nix
- comment in postFixup of telegram-desktop
- comment in postFixup of fwupd
- buildCommand of mongodb-compass
- postFixup of xflux-gui
- comment in a patch in kdePackages.kde-gtk-config and plasma5Packages.kde-gtk-config
- description of programs.sway.wrapperFeatures.gtk NixOS option (manual rebuild)
| Jan Tojnar | 2024-04-27 | 1 | -6/+6 |
| * | gitlab: 16.8.1 -> 16.9.2•••https://gitlab.com/gitlab-org/gitlab/-/blob/v16.8.2-ee/CHANGELOG.md
https://gitlab.com/gitlab-org/gitlab/-/blob/v16.9.2-ee/CHANGELOG.md
Fixes CVE-2023-6386
Fixes CVE-2023-6840
Fixes CVE-2024-0199
Fixes CVE-2024-1066
Fixes CVE-2024-1250
Fixes CVE-2024-1299
Co-Authored-By: ajs124 <git@ajs124.de>
| Yaya | 2024-03-19 | 1 | -2/+2 |
| * | rubyPackages.ovirt-engine-sdk: drop upstreamed patch•••Without the change build fails on` master` as
https://hydra.nixos.org/build/249503515:
Running phase: patchPhase
applying patch /nix/store/9f30k5j6jdmdycfxxkir2vv4zqhfvpvd-b596b919bc7857fdc0fc1c61a8cb7eab32cfc2db.patch
patching file ext/ovirtsdk4c/ov_http_request.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
| Sergei Trofimovich | 2024-02-25 | 1 | -8/+0 |
