text:
llvmPackages_15: init at 15.0.6

Description of changes
I've tested that all of the llvmPackages_15 set builds on x86_64-linux, aarch64-linux, x86_64-darwin, and aarch64-darwin. I have not (yet) checked that cross compilation still works.
Working through getting this to build on the above platforms again, now that this PR targets staging.

This PR contains a few different kinds of changes:

introduces llvmPackages_15, the first six commits
switches to ninja where possible, the next two commits
other LLVM package updates, unrelated to fixing build issues, the next two commits
updates for the lit package, the next commit
mechanical changes to make it easier to override the monorepo source used in the package set, the next commit
bumps llvmPackages_latest
...

If required, I can split these changes up into separate PRs.

TODOs:

[x] rebase onto updated staging from upstream
[x] bump to LLVM 15.0.3
[x] bump to LLVM 15.0.4
[x] bump to LLVM 15.0.5
[x] bump to LLVM 15.0.6
[ ] bump to LLVM 15.0.7
[x] move back to targeting master
[ ] follow up PR bump llvmPackages_latest (targeting staging); 9088010e23bda5fb156901d8f577cbfad1e6530c was dropped from this PR
[ ] backport llvmPackages_15
[x] fix the libcxxabi build on non-x86 (https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990300128)
[x] fix the LLDB manpages package (https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990583868)
[x] fix the compiler-rt build on macOS (https://github.com/NixOS/nixpkgs/pull/194634#issuecomment-1272116014)

[ ] follow up PR now that we're targeting staging, try dropping this patch (postponed)

[x] fix the LLDB build on x86_64-darwin (https://github.com/NixOS/nixpkgs/pull/194634#issuecomment-1272129132)

[x] backport to llvmPackages_{13,14} (#195013)

[x] fix the skipped LIT tests (https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990397994)
[x] update lit
[ ] follow up PR spin off the monorepo source changes into a separate PR against llvmPackages_{13,14,15} (https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990569370)
[x] enable LLVM tests on darwin
[x] enable polly by default again and test (see this comment)

[ ] follow up PR test/fix enablePolly in llvmPackages_{12,13,14}

[ ] update this PR with the changes from:

[x] #190908
[x] #181764
[ ] #186575

[x] verify still needed; add a regression passthru test?

appears to be still needed
[ ] follow up PR can add a regression test that links against a symbol in libclang-rt and test against clangNoLibc (with lsan/asan/ubsan/fuzzer variants tested too)

[ ] #193636

[ ] verify still needed
[ ] follow up PR add a regression passthru test?

[x] #185766

[x] verify still needed; add a regression passthru test?

appears to be no longer needed; libc++abi.so didn't seem to be linked against older libc++abi on non-darwin anyways (where the default stdenv wasn't LLVM based) and now we unconditionally use the clang from the same package set which has libcxx set to null and thus doesn't try to link in any libc++abi
[ ] follow up PR can still add a regression test (gated on enabledShared in libcxxabi) that looks at the output of llvm-readelf --needed-libs lib++abi.{dylib/so} and scans it for libc++abi deps that aren't the libc++abi being scanned

[x] #196909
[x] #191372 ?
[x] #190936

[ ] TODO: test

[x] #82131

[ ] TODO: test

[x] #199844

[ ] follow up PR could do with a regression test or two

[x] #197674

[ ] TODO: test

[x] #184408
[x] #205355
[x] #193004
[x] #201268? need to double check but like #185766 I don't think this is needed
[x] #201485? don't think this is needed either, need to verify
[ ] #211401
[ ] #211230
[ ] #211161
[ ] #206742

https://github.com/NixOS/nixpkgs/commit/33afbf39f6f2a6b37e99f070ba7d17a28c416d02#diff-8ebeb076fd6d6845a2a4af53beeeed54b5e15b0e28d79a32cb15db0fa394b645

[ ] #211687

https://github.com/NixOS/nixpkgs/commit/f5e63a0e9e4b1846964dcaa61a5325b7b70a3a39#diff-3e0243503064c4638bf30720e8c271b4589a7bf114b4e92ebbee2f708040b2e4

[ ] inflight PRs (if these are merged before this PR we should duplicate their changes onto llvmPackages_15; if this PR is merged first we should update these PRs to change llvmPackages_15) — not an exhaustive list:

[ ] #207863
[ ] #173498
[ ] #163314
[ ] #207325
[ ] #155489
[ ] #144302 (also not in _14 yet)
[ ] #163878
[ ] #181108
[ ] #211728

https://github.com/NixOS/nixpkgs/pull/125132/commits/8f80568885d1b37cccbede85143c00711b19390c

Checks:

[ ] llvmPackages_15.*
[ ] passthru tests
[ ] pkgsStatic? stdenv tests? pkgsCross for freeBSD?
[ ] rdeps with nixpkgs-review

Closes #191132.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

With https://github.com/NixOS/nixpkgs/pull/194634/commits/ab9d3df63862da93d8a229ea379efb7b50e8692b, libcxx-abi (and the rest of llvmPackages_15) builds fine on aarch64-linux. Darwin is now hitting an unrelated issue in compiler-rt; I'll tackle that next.
After that:

[ ] the skipped LLVM lit tests https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990348787
[ ] lldb-manpages https://github.com/NixOS/nixpkgs/pull/194634#discussion_r990452271

Fixed one compiler-rt build issue, hit another one.
compiler-rt's build now attempts to detect whether the ld used automatically does codesigning, based on version. Our cctools ld is too old for this but postLinkSignHook handles codesigning for us, regardless.
Unfortunately there doesn't seem to be a way to communicate this to the compiler-rt build machinery. In the interest of avoiding making another patch, I tried to add sigtool to the derivation and just let the compiler-rt build sign some dylibs twice but unfortunately compiler-rt's build uses --sign instead of -s which the sigtool in nixpkgs has not been updated to support.
I opened a PR for this (#194994) but given that sigtool has many transitive deps and that that PR is likely to trigger many rebuilds I think it's probably faster to just add a compiler-rt patch.

With https://github.com/NixOS/nixpkgs/pull/194634/commits/974ea1c842744909fff714babe740dabd4d2e67e this now builds on aarch64-darwin.
Testing x86_64-darwin now; hopefully it Just Works 🤞.

As of now, the llvmPackages_15 set seems to build fully on x86_64-linux, x86-64-darwin, aarch64-linux, and aarch64-darwin.
Getting lit to discover psutil so it doesn't skip tests is the last item on my TODO list for this PR but given that this isn't a regression, this probably isn't worth blocking merging this PR over.
I'm marking this PR as ready to review and I'll take a look at psutil tomorrow.

Earlier today I realized that there have been some changes to llvmPackages_git (which this PR uses as a starting point for llvmPackages_15) since this PR was opened.
From master it's just:

[x] #190908; I've rebased this PR to include these changes

From staging (i.e. git log feature/llvm-15..origin/staging  --oneline -- pkgs/development/compilers/llvm/) currently it looks like:

[ ] #186575

uses a common patch file

[ ] #193636
[ ] #185766

AFAICT all of these PRs were merged into staging instead of master because of rebuild concerns due to affected stdenvs/packages (a constraint this PR doesn't have since we're not bumping llvmPackages_latest yet) and not because they depend on other changes in staging.
So, we can either replicate the changes above on llvmPackages_15 in follow up PRs after this package is merged (seems suboptimal), replicate the changes now while still targeting master (this is fine for the latter two PRs linked above but will cause a merge conflict for #186575 in staging if we want to continue to use a common patch file), or we can replicate the changes now after switching this PR to target staging (no merge conflicts).
The latter solution (switching this PR to target staging) seems cleanest to me but I'm not sure what the convention is here.
@lovesegfault do you have an opinion?

@rrbutani Targeting staging is unfortunate since it'll make this PR take longer to hit master, but I think it might be the easiest thing for us to do. Besides, a week or so of wait time isn't the end of the world.
If you chose to retarget this PR to staging, also add a commit bumping _latest, since you might as well eat the rebuilds in that case :)

mesa 22.1.7 doesn't like LLVM 15: https://gist.github.com/ivan/326b2ee262f816a74e9d682bd6654175#file-gistfile1-txt-L2096-L2184 and this might need
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index cb3eee5ddd2f..abf174d3f777 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -20950,7 +20950,7 @@ with pkgs;
   libGLU = mesa_glu;

   mesa = callPackage ../development/libraries/mesa {
-    llvmPackages = llvmPackages_latest;
+    llvmPackages = llvmPackages_14;
     inherit (darwin.apple_sdk.frameworks) OpenGL;
     inherit (darwin.apple_sdk.libs) Xplugin;
   };

@lovesegfault apologies for the delay. The TODO list is still accurate; I'll try to finish these tasks and get this PR ready for merge today.

Can we merge this PR as is and do the minor version bumps and other improvements in separate PR-s ?
My motivation is to have rustc with llvm15 available as soon as possible.
Thank you for your efforts @rrbutani !

Apologies for the delay, again.
@lblasc I do want to try to incorporate the changes that have landed in llvmPackages_14/git in the interim before this PR is merged but I agree that adding regression tests and some of the other checklist items can be done in follow up PRs.
I've got llvmPackages_15 bumped to 15.0.6 and building, locally, on x86_64-linux; I'm still waiting on Darwin/aarch64-linux before I push (I was running into unrelated issues in dependencies on those platforms yesterday — hopefully pulling in new changes from staging will fix).
I think we've got a little bit of time before the next staging-next cycle starts anyways: #203426

You should drop bumping the default from this PR.  That means much easier merge, directly to master, without needing to care for all possible regressions.
And bump the default separately later.  I'd even say that bumping llvm default is worth a separate jobset; ping me to create that when you want it.
Also note that there were multiple changes to llvm 14 expressions (some even in staging-next..staging right now) and they probably should be included in 15 as well.  It feels like the copying workflow might be more trouble than worth in the past few years, but...

Result of nixpkgs-review pr 194634 run on x86_64-linux 1

1 package marked as broken and skipped:

jucipp

3 packages failed to build:

faustStk
hqplayerd
magnetophonDSP.ConstantDetuneChorus

76 packages built:

Literate
binaryen
btdu
cheesecutter
clang-tools_15
clang_15 (llvmPackages_15.clang ,llvmPackages_15.libstdcxxClang)
dtools
dub
emscripten
faust (faust2)
faust2alqt
faust2alsa
faust2csound
faust2firefox
faust2jack
faust2jackrust
faust2jaqt
faust2ladspa
faust2lv2
faustPhysicalModeling
faustlive
gtkd
guitarix
halide
kapitonov-plugins-pack
klee
ldc
lit
lld_15 (llvmPackages_15.lld)
lldb (lldb_14 ,llvmPackages_14.lldb ,llvmPackages_latest.lldb)
lldb_10 (llvmPackages_10.lldb)
lldb_11 (llvmPackages.lldb ,llvmPackages_11.lldb)
lldb_12 (llvmPackages_12.lldb)
lldb_13 (llvmPackages_13.lldb)
lldb_15 (llvmPackages_15.lldb)
lldb_9 (llvmPackages_9.lldb)
llvmPackages_14.openmp (llvmPackages_latest.openmp)
llvmPackages_15.bintools
llvmPackages_15.bintools-unwrapped
llvmPackages_15.bintoolsNoLibc
llvmPackages_15.clang-manpages
llvmPackages_15.libclang (llvmPackages_15.clang-unwrapped)
llvmPackages_15.clangNoCompilerRt
llvmPackages_15.clangNoCompilerRtWithLibc
llvmPackages_15.clangNoLibc
llvmPackages_15.clangNoLibcxx
llvmPackages_15.clangUseLLVM
llvmPackages_15.compiler-rt (llvmPackages_15.compiler-rt-libc ,llvmPackages_15.compiler-rt-no-libc)
llvmPackages_15.libcxx
llvmPackages_15.libcxxClang
llvmPackages_15.libcxxStdenv
llvmPackages_15.libcxxabi
llvm_15 (llvmPackages_15.llvm)
llvmPackages_15.libunwind
llvmPackages_15.lldb-manpages
llvmPackages_15.llvm-manpages
llvmPackages_15.openmp
llvmPackages_15.stdenv
magnetophonDSP.CharacterCompressor
magnetophonDSP.CompBus
magnetophonDSP.LazyLimiter
magnetophonDSP.MBdistortion
magnetophonDSP.RhythmDelay
magnetophonDSP.VoiceOfFaust
magnetophonDSP.faustCompressors
magnetophonDSP.pluginUtils
magnetophonDSP.shelfMultiBand
mooSpace
onedrive
open-music-kontrollers.mephisto
rund
sambamba
tambura
tilix
tinygo
vscode-extensions.vadimcn.vscode-lldb

New inflight PR #207863

Any updates here? It would be nice to have this in the next staging cycle so Mesa works correctly on RDNA3.

Are some of the files just copied over?

Yes a big chunk is copied because we reproduce what is done when adding a new version:

Packaging new LLVM versions as soon as the first RC is out (that's pretty simple/straightforward as it's basically just copying llvmPackages_git and switching to the right version

https://github.com/NixOS/nixpkgs/issues/171047#issue-1221879536

Does this need anything else before merge to staging? As long as it's not moving to default, it seems like this is a good thing to get into staging at this point -- especially if now alternate PRs are popping open assuming this isn't already in progress!

Couple of things I noticed.

llvmPackages_latest needs to be set to 15
mesa won't build with llvm 15 because it needs spirv-llvm-translator to be version 15, and even with that it seems to fail to build for some reason.
Also that spirv-llvm-translator thing has the wrong download hash for version 15 in pkgs/development/compilers/spirv-llvm-translator/default.nix. I got hash = "sha256-OsDohXRxovtEXaWiRGp8gJ0dXmoALyO+ZimeSO8aPVI=";

llvmPackages_latest needs to be set to 15

I think we want this PR to go into master and if we’re happy with things working (like mesa), a follow-up PR that bumps llvmPackages_latest can go into staging.

Does this need anything else before merge to staging?

I think we want this PR to go into master and if we’re happy with things working (like mesa), a follow-up PR that bumps llvmPackages_latest can go into staging.

Yup, as @vcunat suggested this PR targets master and doesn't bump llvmPackages_latest.

There are still changes I want to make (adding regression tests, fixing cross-compilation and use of the llvmPackages_15's stdenv as a cross-compiler) but all of that can happen in follow up PRs; the last things blocking this PR are:

[ ] getting llvmPackages_15.* to build again

currently .llvm builds but dependent packages fail during configure when trying to find libPollyISL.a (a mixup between the out and lib outputs; just needs a patch)

[ ] adding in the remaining changes that have been made to llvmPackages_14 in the interim

#186575 (and possibly #193636) are what's left on my list
but I'm not super confident I caught everything; I'd appreciate it if others could verify that there's nothing missing in the list in the OP

I'm planning to finish the above today; I'll keep this post updated with the current status.

Any news on it?

There is a similar PR at https://github.com/NixOS/nixpkgs/pull/209536. Can we combine the changes somehow?

There is a similar PR at #209536. Can we combine the changes somehow?

We have one commit in common: https://github.com/NixOS/nixpkgs/pull/194634/commits/f6b76b7a47831c041b9f031955ebbe8bcaf7acd8

[ ]  llvm on x86_64-darwin
[ ]  waiting on llvmPackages_15.* to build on:

[ ]  x86_64-darwin: 3 failing LLVM tests

So I assume it does build on x86_64-darwin with doCheck set to false, as does the other PR and even llvmPackages_14?

I was struggling to build llvmPackages_15 with 15.0.7 to use as my stdenv. Is there an easy way to do that?
I've tried various combinations of llvmPackages_15.override with gitRelease, officialRelease, and monorepoSrc without any luck. Any suggestions?
I appreciate the refactoring you've done here and hope to be able to easily build LLVM (including wrapping bintools, providing everything necessary to use it as a stdenv, etc.) from arbitrary commits.

I was struggling to build llvmPackages_15 with 15.0.7 to use as my stdenv. Is there an easy way to do that?
I've tried various combinations of llvmPackages_15.override with gitRelease, officialRelease, and monorepoSrc without any luck. Any suggestions?

Ah, I guess this could use some better documentation.
@ConnorBaker Unless you're trying to grab LLVM from somewhere other than the llvm/llvm-project repo, you shouldn't need to set monorepoSrc; just officialRelease (to grab a release like 15.0.7) OR gitRelease (to grab a commit like https://github.com/llvm/llvm-project/commit/d5cbaa047004335a29dc3bcaf6aaa1c26fc27f36).
For 15.0.7 I think this should do the trick:
(nixpkgs.llvmPackages_15.override {
  officialRelease = {
    version = "15.0.7";
    sha256 = "sha256-wjuZQyXQ/jsmvy6y1aksCcEDXGBjuhpgngF3XQJ/T4s=";
  };
}).libcxxStdenv

Is there a reason for this pull request to be a draft?

Is there a reason for this pull request to be a draft?

It is a bit complicated, complex and it still does not compile all tier-1 architectures.

it still does not compile all tier-1 architectures.

I think it does, if we disable the LLVM tests as in LLVM 14.

This is still blocking support for RDNA3 hardware in Mesa, and the hardware itself is becoming widely available. Can we do anything to speed this up so we catch the next staging train?

@ofborg build llvmPackages_15.compiler-rt llvmPackages_15.compiler-rt.passthru.tests llvmPackages_15.libcxx llvmPackages_15.libcxx.passthru.tests llvmPackages_15.libcxxabi llvmPackages_15.libcxxabi.passthru.tests llvmPackages_15.lldb llvmPackages_15.lldb.passthru.tests llvmPackages_15.llvm llvmPackages_15.llvm.passthru.tests llvmPackages_15.openmp llvmPackages_15.openmp.passthru.tests

Rebuilding as there seems to be an aarch64-linux regression on the other PR: https://github.com/NixOS/nixpkgs/pull/209536#issuecomment-1402579137

@ofborg build llvmPackages_15

It's OK for me if you push.

I'd say get the last 1-2 things done if they really can't be done afterwards, run tests if necessary, and then land this - dealing with fallout afterwards directly on master.
The upside to this is, that while contributing a fix for a specific issue to this large changeset is not very ergonomic for other users, fixing whatever they need in a PR themselves is very doable for downstream packages in nixpkgs.

Agreed. I've got all of the remaining things (bump to 15.0.7, fixing the license, "fixing" x86_64-darwin LLVM tests, applying the changes from the 5 PRs that merged since I last checked) resolved in my local checkout with the exception of #193636 which I still haven't been able to reproduce (I think I need to be on a Linux host; I'll have access to one in a couple of hours).
@wegank is it okay if I push or should I wait for the ofborg run you kicked off to finish?

Apologies for the delay, again.
I couldn't reproduce #193636 (the test case in #151879 passes and I don't see the extra header dirs on macOS or Linux) so I think this PR is pretty much ready.
I'm waiting on builds to finish for:

[x] aarch64-linux
[ ] aarch64-darwin
[ ] x86_64-linux
[ ] x86_64-darwin
[ ] i686-linux
[ ] armv7l-linux

building on a Pi so this will take me a while; if anyone has access to a machine capable of running 32-bit ARM code (like the nix community aarch64 build box)  and is willing to test building the package set it'd be much appreciated!

Additionally, I'm testing that:

[x] the packages in this script eval (cross compiling LLVM + using LLVM as a cross-compiler)

with the exception of using LLVM as a cross-compiler on darwin which runs into infinite recursion issues that I haven't been able to get to the bottom of

[ ] pkgsCross.x86_64-freebsd.boost builds from an x86_64-linux host where llvmPackages has been overridden to point to llvmPackages_15

this builds as of #211230 and I want to make sure I replicated those changes correctly

I've opened a tracking issue for the follow-up work to this PR: #213033; I'll fill in that issue and open a (draft, contingent on this PR getting merged) follow-up PR bumping llvmPackages_latest on staging later today.

@rrbutani

Is there a reason for this pull request to be a draft?

It is a bit complicated, complex and it still does not compile all tier-1 architectures.

I believe this PR is ready to be reviewed. Can you remove the draft status? I understand that it's not 100% completed, but it's ready to be reviewed (I believe).
Personally I really want this PR to be merged (in my case because of Zig), and I know many people IRL that feel similar. Since almost all issues are resolved, I believe it shouldn't be a draft (for example, #209536 is not a draft).

@rrbutani

Is there a reason for this pull request to be a draft?

It is a bit complicated, complex and it still does not compile all tier-1 architectures.

I believe this PR is ready to be reviewed. Can you remove the draft status? I understand that it's not 100% completed, but it's close enough (I believe, based on my undestanding of this thread).
Personally I really want this PR to be merged (in my case because of Zig), and I know many people IRL that feel similar. Since almost all issues are resolved, I believe it shouldn't be a draft (for example, #209536 is not a draft).

For Zig, I think we need assistance from the darwin maintainers, since (last time I tried) I ran into errors in rrbutani's #191152, and even applying the fix there didn't help (?).

Result of nixpkgs-review pr 194634 run on x86_64-linux 1

25 packages built:

clang-tools_15
clang_15 (llvmPackages_15.clang ,llvmPackages_15.libstdcxxClang)
lld_15 (llvmPackages_15.lld)
lldb_15 (llvmPackages_15.lldb)
llvmPackages_15.bintools
llvmPackages_15.bintools-unwrapped
llvmPackages_15.bintoolsNoLibc
llvmPackages_15.clang-manpages
llvmPackages_15.libclang (llvmPackages_15.clang-unwrapped)
llvmPackages_15.clangNoCompilerRt
llvmPackages_15.clangNoCompilerRtWithLibc
llvmPackages_15.clangNoLibc
llvmPackages_15.clangNoLibcxx
llvmPackages_15.clangUseLLVM
llvmPackages_15.compiler-rt (llvmPackages_15.compiler-rt-libc ,llvmPackages_15.compiler-rt-no-libc)
llvmPackages_15.libcxx
llvmPackages_15.libcxxClang
llvmPackages_15.libcxxStdenv
llvmPackages_15.libcxxabi
llvm_15 (llvmPackages_15.llvm)
llvmPackages_15.libunwind
llvmPackages_15.lldb-manpages
llvmPackages_15.llvm-manpages
llvmPackages_15.openmp
llvmPackages_15.stdenv

wegank said:

I think I'll merge it if Zig builds on my (slow) aarch64-linux machine.

I built the following packages on my Linux AArch64 machine. They all built successfully at commit d231d18e4aa5e1d00f86b4f484f9e4344538e3ea + my two Zig patches (#210324):
30 packages built:
cargo-lambda
cargo-zigbuild
clang-tools_15
clang_15
clipbuzz
lld_15
lldb_15
llvmPackages_15.bintools
llvmPackages_15.bintools-unwrapped
llvmPackages_15.bintoolsNoLibc
llvmPackages_15.clang-manpages
llvmPackages_15.libclang
llvmPackages_15.clangNoCompilerRt
llvmPackages_15.clangNoCompilerRtWithLibc
llvmPackages_15.clangNoLibc
llvmPackages_15.clangNoLibcxx
llvmPackages_15.clangUseLLVM
llvmPackages_15.compiler-rt
llvmPackages_15.libcxx
llvmPackages_15.libcxxClang
llvmPackages_15.libcxxStdenv
llvmPackages_15.libcxxabi
llvmPackages_15.llvm
llvmPackages_15.libunwind
llvmPackages_15.lldb-manpages
llvmPackages_15.llvm-manpages
llvmPackages_15.openmp
llvmPackages_15.stdenv
zig
zig_0_9

Linux ubuntu-linux-22-04-desktop 5.15.0-41-generic #44-Ubuntu SMP Thu Jun 23 11:20:13 UTC 2022 aarch64 GNU/Linux

Also built Zig 0.10.1 on top of f80ac848e3d6f0c12c52758c0f25c10c97ca3b62 with the two PRs applied:
$ nix-build -A zig
/nix/store/g9kixfg3cy0nxpv19z8b4i8dbn8zbsxb-zig-0.10.1

authors: AndersonTorres ConnorBaker ElvishJerricco Et7f3 Flakebi K900 LunNova ivan lblasc lovesegfault misuzu msm-code rrbutani strager vcunat wegank willcohen


text:
calibre: fix epub-viewer

Description of changes
Fixes an issue with epub-viewer after the recent major version bump of calibre ( #194912 )
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Sorry for the inconvenience, i missed that when updating calibre and thanks for fixing the issue.
I think we can remove the fallowing reference to pyqtwebengine because it only provides python bindings for Qt5:
https://github.com/NixOS/nixpkgs/blob/ef0ed284ea6ce8d14de9575d1962e70590c29bfe/pkgs/applications/misc/calibre/default.nix#L127-L131

Hi, this is causing calibre (specifically qtwebengine-6.4.0) to be built from source, but I'm not sure why. This takes more than a few hours and results in OOM errors on a 16gb machine. I'm not sure why hydra didn't build qtwebengine-6.4.0 and I don't know how to check

There is some discussion at discourse about this issue.
For a quick fix you can just remove pyqt6-webengine from the build inputs (most of the functionality should work without it).

Hi, this is causing calibre (specifically qtwebengine-6.4.0) to be built from source, but I'm not sure why. This takes more than a few hours and results in OOM errors on a 16gb machine. I'm not sure why hydra didn't build qtwebengine-6.4.0 and I don't know how to check

It causes qtwebengine-6 to be built because it is a dependency of calibre-6, specifically epub-viewer and other binaries.
If you don't need epub-viewer or other binaries that depend on qtwebengine-6 you could remove that dependency on a nixpkgs fork or override.

Sorry for the inconvenience, i missed that when updating calibre and thanks for fixing the issue.

No worries, thanks for the version upgrade :3

source: gharchive/pull-request

authors: fabianhjr khrj kilianar

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
plex: 1.29.0.6244-819d3678c -> 1.29.1.6316-f4cdfea9c

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 196978 run on x86_64-linux 1

2 packages built:

plex
plexRaw

authors: maxeaubrey rhoriguchi


text:
python3Packages.pywick: mark broken due to missing dependencies

Description of changes
pywick is broken due to missing dependencies but somehow wasn't marked as such when  #189209 was merged.
@SuperSandro2000
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Why not try adding the dependencies?

If I remember, albumentations has added even more dependencies since the stale PR adding it (#165715).
I have a PR to add prodict in #189748 but it was never reviewed.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1755


text:
python310Packages.winacl: 0.1.5 -> 0.1.6

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 204662 run on x86_64-linux 1

15 packages built:

crackmapexec
python310Packages.aesedb
python310Packages.aiosmb
python310Packages.aiowinreg
python310Packages.lsassy
python310Packages.msldap
python310Packages.pypykatz
python310Packages.winacl
python39Packages.aesedb
python39Packages.aiosmb
python39Packages.aiowinreg
python39Packages.lsassy
python39Packages.msldap
python39Packages.pypykatz
python39Packages.winacl


text:
coqPackages.VST: 2.10 → 2.11.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Does anyone know why VST is gone? https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=coqPackages.VST I would've thought that I could find a PR that removed it (for any major deprecation events)

The VST package is still there. It is available for Coq versions from 8.12 to 8.16; in particular not available for Coq 8.17. Give a try to the coqPackages_8_16.VST attribute path.

authors: quinn-dougherty vbgl


text:
seaweedfs: 3.34 -> 3.38

Description of changes
Repo is now under the seaweedfs org.

Changelog: https://github.com/seaweedfs/seaweedfs/compare/3.34...3.38
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 208950 run on x86_64-linux 1

1 package built:

seaweedfs

authors: azahi wozeparrot


text:
python310Packages.plugwise: 0.27.3 -> 0.27.4

Diff: https://github.com/plugwise/python-plugwise/compare/refs/tags/v0.27.3...v0.27.4
Changelog: https://github.com/plugwise/python-plugwise/releases/tag/v0.27.4
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 213132 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.plugwise
python310Packages.plugwise
python311Packages.plugwise


text:
nvidia-{docker,podman}: update

Description of changes

NOTE: The source code for the nvidia-container-runtime binary has been moved to the nvidia-container-toolkit repository.

The repo source has been changed to https://gitlab.com/nvidia/container-toolkit/container-toolkit.

nvidia-container-toolkit: 1.5.0 -> 1.9.0

removed nvidia-container-runtime

Fixed missing bin path

The scripts for the test are provided by @cpcloud

podman run --runtime nvidia --rm docker.io/nvidia/cudagl:10.1-runtime-centos7 nvidia-smi
Sun Mar 26 07:54:37 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.89.02    Driver Version: 525.89.02    CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
|  0%   44C    P8     9W / 180W |    530MiB /  8192MiB |     24%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

test_nvidia_podman_simple

podman run --runtime nvidia --rm nvidia/cuda:11.7.0-base-ubi7 nvidia-smi --list-gpus
GPU 0: NVIDIA GeForce GTX 1070 Ti (UUID: GPU-8972156c-b68f-5a85-d0fc-32c6b0bb4abf)

test_nvidia_podman_tensorflow

+ podman run -e TF_CPP_MIN_LOG_LEVEL=1 -e LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu --runtime nvidia --rm tensorflow/tensorflow:2.11.0-gpu python -c 'import tensorflow as tf

devices = tf.config.list_physical_devices("GPU")
assert devices, "no GPU devices found"

print("\n".join(map(repr, devices)))
'
2023-03-26 07:55:22.532364: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvrtc.so.11.0: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib/x86_64-linux-gnu
2023-03-26 07:55:22.537779: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvrtc.so.11.0: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib/x86_64-linux-gnu
2023-03-26 07:55:22.537791: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@cpcloud Do you have any plan to update the libnvidia-container to 1.12X ?

@cpcloud Do you have any plan to update the libnvidia-container to 1.12.X ?

No, I don't have the time to do so right now.

+1 does this fix the /usr/bin/nvidia-container-runtime-hook issue?

authors: GTrunSec adrosa cpcloud


text:
[riscv] Fix compilation error of libjxl 0.8.1 on riscv

Description of changes
libjxml v0.8.1 currently fails to build on riscv due to a missing include of <atomic>. Upstream has this fixed but not merged into any release yet, so pulling in the patch for now to allow riscv to build.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Successfully built on pkgsCross.riscv64 and on riscv64 hardware.

Did the same in https://github.com/NixOS/nixpkgs/pull/222282

Closing as duplicate of @NickCao

authors: NickCao kangaroo


text:
sslscan: 2.0.15 -> 2.0.16, ssldump: 1.6 -> 1.7

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 226325 run on x86_64-linux 1

2 packages built:

ssldump
sslscan


text:
typst-fmt: init at 0.1.0

Description of changes
close #224797
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 226469 run on aarch64-darwin 1

1 package failed to build:

typst-fmt


text:
python311Packages.simplisafe-python: 2023.04.0 -> 2023.05.0

Diff: https://github.com/bachya/simplisafe-python/compare/refs/tags/2023.04.0...2023.05.0
Changelog: https://github.com/bachya/simplisafe-python/releases/tag/2023.05.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232596 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.simplisafe
python310Packages.simplisafe-python
python310Packages.simplisafe-python.dist
python311Packages.simplisafe-python
python311Packages.simplisafe-python.dist


text:
jackett: 0.21.17 -> 0.21.34

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: API Support for your favorite torrent trackers
meta.homepage for jackett is: https://github.com/Jackett/Jackett/
meta.changelog for jackett is: https://github.com/Jackett/Jackett/releases/tag/v0.21.34
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.21.34 with grep in /nix/store/q9d3pbys7k5m0qfnlzsvvnvr0103ck7v-jackett-0.21.34
found 0.21.34 in filename of file in /nix/store/q9d3pbys7k5m0qfnlzsvvnvr0103ck7v-jackett-0.21.34

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q9d3pbys7k5m0qfnlzsvvnvr0103ck7v-jackett-0.21.34 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/df85fc53a33775735f87c32ea9204bfe792805b9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q9d3pbys7k5m0qfnlzsvvnvr0103ck7v-jackett-0.21.34
ls -la /nix/store/q9d3pbys7k5m0qfnlzsvvnvr0103ck7v-jackett-0.21.34/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Result of nixpkgs-review pr 234121 run on aarch64-darwin 1

1 package built:

jackett

authors: r-ryantm wegank


text:
telegram-desktop: patch for failing to open links on wayland

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Tested this for a day, seem to fix the issue.


text:
bwa-mem2: init at version 2.2.1

Description of changes
New bioinformatics package bwa-mem2.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I think I need to limit the platform to x86_64-linux, I'll modify when I have time.

Good to see you again! I have left some comments, could you please check them?
Then feel free to ping me for anything related to bioinformatics or python packages.

Good to see you again too and thanks for the comments

thanks for your help!


text:
rune: init at 0.12.4

https://rune-rs.github.io/
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 250432 run on x86_64-linux 1

1 package built:

rune

authors: figsoda matthiasbeyer


text:
python311Packages.yolink-api: 0.3.0 -> 0.3.1

Diff: https://github.com/YoSmart-Inc/yolink-api/compare/refs/tags/v0.3.0...v0.3.1
Changelog: https://github.com/YoSmart-Inc/yolink-api/releases/tag/v0.3.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 255528 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.yolink
python310Packages.yolink-api
python310Packages.yolink-api.dist
python311Packages.yolink-api
python311Packages.yolink-api.dist


text:
nu_scripts: unstable-2023-10-07 -> unstable-2023-10-19

Description of changes
For compatibility with the latest Nushell release.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@CardboardTurkey

Result of nixpkgs-review pr 262649 run on x86_64-linux 1

1 package built:

nu_scripts


text:
mmj2: init at 2.5.2-unstable-2023-06-27

Description of changes

Add mmj2 package. This can be run with ./result/bin/mmj2 -d set.mm, where set.mm is the file https://github.com/metamath/set.mm/blob/develop/set.mm.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[x] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Looks like you didn't test your changes :p by changing the version you broke it when you are copying the jar file.
Other stuff:

No runHook in installPhase
You didn't set meta.maintainers, please add yourself as a maintainer and then set that field
Did you really test this package on all platforms ? Otherwise just specify the platform on which you tested in meta.platforms

Here's a patch to make it work and with runHooks:
diff --git a/pkgs/by-name/mm/mmj2/package.nix b/pkgs/by-name/mm/mmj2/package.nix
index f851baa33d94..65f60af716fd 100644
--- a/pkgs/by-name/mm/mmj2/package.nix
+++ b/pkgs/by-name/mm/mmj2/package.nix
@@ -1,11 +1,13 @@
 { lib, maven, fetchFromGitHub, jre, makeWrapper }:

-maven.buildMavenPackage {
+let
+  lastVersion = "2.5.2";
+in maven.buildMavenPackage {
   pname = "mmj2";

   # The latest stable version is from 2017 and doesn't include the mmj2jar/mmj2
   # wrapper script, so use the unstable one for now
-  version = "2.5.2-unstable-2023-06-27";
+  version = "${lastVersion}-unstable-2023-06-27";

   src = fetchFromGitHub {
     owner = "digama0";
@@ -20,13 +22,17 @@ maven.buildMavenPackage {
   nativeBuildInputs = [ makeWrapper ];

   installPhase = ''
+    runHook preInstall
+
     local jar=$out/share/$pname/$pname.jar
     local bin=$out/bin/$pname
-    install -Dm644 target/$pname-$version-SNAPSHOT-jar-with-dependencies.jar $jar
+    install -Dm644 target/$pname-${lastVersion}-SNAPSHOT-jar-with-dependencies.jar $jar
     install -Dm744 mmj2jar/$pname $bin
     wrapProgram $bin \
       --set MMJ2_JAR $jar \
       --set JAVA ${jre}/bin/java
+
+    runHook postInstall
   '';

   meta = with lib; {

Thanks @TheBrainScrambler, I fixed all the problems.

Result of nixpkgs-review pr 265991 run on x86_64-linux 1

1 package built:

mmj2

@ofborg build mmj2

authors: FliegendeWurst TheBrainScrambler io12


text:
cosmic-comp: unstable-2023-10-04 -> unstable-2023-11-09

Description of changes
Formatting, move cosmic-comp to by-name, updating, and fixed package (xwayland was broken)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

For the same reason as in https://github.com/NixOS/nixpkgs/pull/266378#pullrequestreview-1723096205, are there user-visible changes in this update?

For the same reason as in #266378 (review), are there user-visible changes in this update?

Yes, theming support and also xwayland was broken in the derivation before.

xwayland was broken in the derivation before.

I mean, we can fix that one without committing a new Cargo.lock.
But theming support is a good reason!

Please don't set repo = pname;. It adds indirection, which reduces cognitive overhead when reading, but isn't going to ever safe us any work. It was fine as it was.

Aw alright :3

authors: Nyabinary alyssais


text:
python311Packages.bimmer-connected: 0.14.2 -> 0.14.3

Diff: https://github.com/bimmerconnected/bimmer_connected/compare/refs/tags/0.14.2...0.14.3
Changelog: https://github.com/bimmerconnected/bimmer_connected/releases/tag/0.14.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 268902 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.bmw_connected_drive
python310Packages.bimmer-connected
python310Packages.bimmer-connected.dist
python311Packages.bimmer-connected
python311Packages.bimmer-connected.dist


text:
pkgsStatic.stdenv: fix custom CMake LINKER_LANGUAGE

Description of changes
If a CMake target has a non-default LINKER_LANGUAGE set, CMake will manually add the libraries it has detected that language's compiler as linking implicitly.  When it does this, it'll pass -Bstatic and -Bdynamic options based on the vibes it gets from each such detected library.  This in itself isn't a problem, because the compiler toolchain, or our wrapper, or something, seems to be smart enough to ignore -Bdynamic for those libraries.  But it does create a problem if the compiler adds extra libraries to the linker command line after that final -Bdynamic, because those will be linked dynamically.  Since our compiler is static by default, CMake should reset to -Bstatic after it's done manually specifying libraries, but CMake didn't actually know that our compiler is static by default.  The fix for that is to tell it, like so.
Until recently, this problem was difficult to notice, because it would result binaries that worked, but that were dynamically linked.  Since e08ce498f03f ("cc-wrapper: Account for NIX_LDFLAGS and NIX_CFLAGS_LINK in linkType"), though, -Wl,-dynamic-linker is no longer mistakenly passed for executables that are supposed to be static, so they end up created with a /lib interpreter path, and so don't run at all on NixOS.
This fixes pkgsStatic.graphite2.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Alright, the yellow lozenge says "linux 100-500" which is not nothing but I'm gonna declare that to be "not mass-rebuild".

authors: alyssais amjoseph-nixpkgs


text:
nixos/kea: set StateDirectory (fixes #265826)

Description of changes
Using #265826 as a starting point, add both a service-specific state
directory and the the example state directory (/var/lib/kea). This
addresses error messages like:
kea-dhcp4[xx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Tested, as applicable:

[x] tests.kea
[x] 2h running DHCP server

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)
[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Aww.. Should have tested longer. Problem still exists:
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: 2023-11-28 20:20:25.246 INFO  [kea-dhcp4.dhcpsrv/763383.139900198662208] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: 2023-11-28 20:20:25.248 INFO  [kea-dhcp4.dhcpsrv/763383.139900198662208] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /nix/store/f79ssf41ksw9ddsb9afrll6nl5mcn2c2-kea-2.4.0/sbin/kea-lfc -4 -x /var/lib/kea/dhcp4.leases.2 -i /var/lib/kea/dhcp4.leases.1 -o /var/lib/kea/dhcp4.leases.output -f /var/lib/kea/dhcp4.leases.completed -p /var/lib/kea/dhcp4.leases.pid -c ignored-path
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile
Nov 28 20:20:25 xxx kea-dhcp4[xxx]: Unable to use interprocess sync lockfile (Read-only file system): /var/run/kea/logger_lockfile

I'll test out the systemd units with ReadWritePaths="/var/lib/kea";


text:
libdrm: 2.4.117 -> 2.4.118

Hyprland requires version 2.4.118 as a dependency

Reword the commit:

libdrm: 2.4.117 -> 2.4.118

Also rebase to staging.
Read the docs on how to do this - or else the world will be pinged.

I only forked master, should I delete this fork and start again?

I only forked master, should I delete this fork and start again?

This is the easiest form. Feel free if you are not feeling so brave.
Usually the change to staging requires a cherry-pick and a modification here in GitHub.
However, when done wrong it injects too many commits from other branches, and the planet is pinged.

Alright, I'll delete this and start again. To clarify, I fork the whole repo and then make changes to the "staging" branch, right? This is my first time contributing to any kind of open source, thanks for helping

ok, how do I do that?

This was already updated and is now in master and unstable

https://github.com/NixOS/nixpkgs/pull/269129

Oh, great. Thanks

I'll delete this pr then

authors: AndersonTorres Lenny0939 qubitnano


text:
python311Packages.gpy: 1.10.0 -> 1.13.0

Description of changes
Routine update/unbreak package.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 277654 at 19f9c600 run on x86_64-linux 1

2 packages built successfully:

python310Packages.gpy
python311Packages.gpy

authors: bcdarwin natsukium


text:
tmux-sessionizer: 0.3.0 -> 0.3.2

Description of changes

https://github.com/jrmoulton/tmux-sessionizer/releases/tag/v0.3.2
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 280383 run on x86_64-linux 1

1 package built:

tmux-sessionizer

authors: junglerobba mrcjkb


text:
electron: 1.6.6 -> 1.7.5

Motivation for this change
New minor version, needed for my package of riot-desktop (which I still haven't managed to package suitably for merging into nixpkgs; one of these days...)
I'm not sure how much impact this might have on other electron packages in nixpkgs; input from someone with more electron knowledge would be very welcome.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Only nix-tour seems to use this package, which seems to work fine after the update.


text:
dokuwiki: 2023-04-04a -> 2024-02-06

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dokuwiki/dokuwiki/releases.
meta.description for dokuwiki is: Simple to use and highly versatile Open Source wiki software that doesn't require a database
meta.homepage for dokuwiki is: https://www.dokuwiki.org
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024-02-06 with grep in /nix/store/12rbn35xq3cy7f2j5vm1vaapkxj2szxi-dokuwiki-2024-02-06
found 2024-02-06 in filename of file in /nix/store/12rbn35xq3cy7f2j5vm1vaapkxj2szxi-dokuwiki-2024-02-06

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dokuwiki

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/12rbn35xq3cy7f2j5vm1vaapkxj2szxi-dokuwiki-2024-02-06 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dokuwiki https://github.com/r-ryantm/nixpkgs/archive/0441eb9da3de8b9cfe6e6cc0623e4258f0f405b0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0441eb9da3de8b9cfe6e6cc0623e4258f0f405b0#dokuwiki

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/12rbn35xq3cy7f2j5vm1vaapkxj2szxi-dokuwiki-2024-02-06
ls -la /nix/store/12rbn35xq3cy7f2j5vm1vaapkxj2szxi-dokuwiki-2024-02-06/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dokuwiki

Maintainer pings
cc @1000101 for testing.

@grahamcofborg test dokuwiki

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dokuwiki/dokuwiki/releases.
meta.description for dokuwiki is: Simple to use and highly versatile Open Source wiki software that doesn't require a database
meta.homepage for dokuwiki is: https://www.dokuwiki.org
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024-02-06a with grep in /nix/store/qwhfnxsmcln1656h9wxqvqcdhkkxx16d-dokuwiki-2024-02-06a
found 2024-02-06a in filename of file in /nix/store/qwhfnxsmcln1656h9wxqvqcdhkkxx16d-dokuwiki-2024-02-06a

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dokuwiki

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qwhfnxsmcln1656h9wxqvqcdhkkxx16d-dokuwiki-2024-02-06a \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dokuwiki https://github.com/r-ryantm/nixpkgs/archive/f235fcfd5ffa45d9a3e9697473553bc26883710d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f235fcfd5ffa45d9a3e9697473553bc26883710d#dokuwiki

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qwhfnxsmcln1656h9wxqvqcdhkkxx16d-dokuwiki-2024-02-06a
ls -la /nix/store/qwhfnxsmcln1656h9wxqvqcdhkkxx16d-dokuwiki-2024-02-06a/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dokuwiki

Maintainer pings
cc @1000101 for testing.


text:
pipewire: Fix libdrm dependency

Description of changes
The libdrm dependency is required for Vulkan, not libcamera support. See the requirement in the source code here. Fixes #293060.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Needs to be retargeted to staging.

Done.

Thanks!


text:
[23.11] hercules-ci, cachix: nix 2.18

Description of changes
Update to Nix 2.18

hercules-ci-agent nix evaluator

reinstating the original attribute, ie without conditions for using it safely outside of a NixOS context

cachix store access library, hercules-ci-cnix-store

fixing channel blocking build problem

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build hercules-ci-agent
@ofborg build cachix
@ofborg build haskellPackages.hercules-ci-cnix-expr

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/error-setup-the-pkg-config-package-nix-store-version-2-4-2-17-is-required-but-the-version-installed-on-the-system-is-version-2-18-1/41082/3

authors: nixos-discourse roberth


text:
cffconvert: init at 2.0.0-unstable-2024-02-12

This PR:

[x] introduce cffconvert: https://github.com/citation-file-format/cffconvert
[x] Uses the unstable version because version 2.0.0 is using an old version of python package jsonschema

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thank you, I've learned something new!


text:
glib-networking: 2.50.0 → 2.54.0

Motivation for this change
Updates translations, improves gnutls compatibility and error messages.
Cherry-picked from #29392 (GNOME 3.26).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @vcunat

I think I will also cherry-pick the rest of the library updates from GNOME 3.26 first.


text:
python312Packages.periodiq: Relax pendulum dependency

Description of changes
Due to a pendulum update the perodiq build broke. The package still works while relaxing the dependency
Broken by #294305
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 300086 run on x86_64-linux 1

10 packages built:

fit-trackee
fit-trackee.dist
python311Packages.flask-dramatiq
python311Packages.flask-dramatiq.dist
python311Packages.periodiq
python311Packages.periodiq.dist
python312Packages.flask-dramatiq
python312Packages.flask-dramatiq.dist
python312Packages.periodiq
python312Packages.periodiq.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3786

authors: nixos-discourse traxys


text:
python312Packages.ring-doorbell: 0.8.8 -> 0.8.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.ring-doorbell is: Python library to communicate with Ring Door Bell
meta.homepage for python312Packages.ring-doorbell is: https://github.com/tchellomello/python-ring-doorbell
meta.changelog for python312Packages.ring-doorbell is: https://github.com/tchellomello/python-ring-doorbell/releases/tag/0.8.9
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.9 with grep in /nix/store/89vfxqjl6qazp17igy4d6yj33860ycd9-python3.12-ring-doorbell-0.8.9
found 0.8.9 in filename of file in /nix/store/89vfxqjl6qazp17igy4d6yj33860ycd9-python3.12-ring-doorbell-0.8.9

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.ring
python311Packages.ring-doorbell
python312Packages.ring-doorbell

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/89vfxqjl6qazp17igy4d6yj33860ycd9-python3.12-ring-doorbell-0.8.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.ring-doorbell https://github.com/r-ryantm/nixpkgs/archive/e36fb7832165b2848a6f05146d598a2e04371221.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e36fb7832165b2848a6f05146d598a2e04371221#python312Packages.ring-doorbell

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/89vfxqjl6qazp17igy4d6yj33860ycd9-python3.12-ring-doorbell-0.8.9
ls -la /nix/store/89vfxqjl6qazp17igy4d6yj33860ycd9-python3.12-ring-doorbell-0.8.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.ring
python311Packages.ring-doorbell
python311Packages.ring-doorbell.dist
python312Packages.ring-doorbell
python312Packages.ring-doorbell.dist

Maintainer pings
cc @graham33 for testing.

Result of nixpkgs-review pr 300985 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.ring
python311Packages.ring-doorbell
python311Packages.ring-doorbell.dist
python312Packages.ring-doorbell
python312Packages.ring-doorbell.dist

authors: fabaff r-ryantm


text:
bruno: 1.12.3 -> 1.13.1, use --replace-fail

Description of changes
Changelogs:

https://github.com/usebruno/bruno/releases/tag/v1.13.0
https://github.com/usebruno/bruno/releases/tag/v1.13.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 304378 run on x86_64-linux 1

1 package built:

bruno

authors: gepbird lucasew


text:
kernel: Build Tegra PCI support.

This enables Nvidia Tegra dev kits (e.g., Jetson TX1) to boot from PCIe devices, such as NVMe boards.
/cc @dezgeg

Thanks. I will also poke the upstream Tegra maintainers to have this on by default...

authors: dezgeg dhess


text:
fcitx5-chewing: 5.1.2 -> 5.1.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/fcitx5-chewing/versions.
meta.description for fcitx5-chewing is: Chewing wrapper for Fcitx5
meta.homepage for fcitx5-chewing is: https://github.com/fcitx/fcitx5-chewing
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
fcitx result is not automatically checked because some binaries stick around

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fcitx5-chewing

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8qxrvn1v8p499l2sjvzsgn3ljz3y9f28-fcitx5-chewing-5.1.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fcitx5-chewing https://github.com/r-ryantm/nixpkgs/archive/e70f330b1c342dda7ab30f32bbd0dd28fb848e6e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e70f330b1c342dda7ab30f32bbd0dd28fb848e6e#fcitx5-chewing

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8qxrvn1v8p499l2sjvzsgn3ljz3y9f28-fcitx5-chewing-5.1.3
ls -la /nix/store/8qxrvn1v8p499l2sjvzsgn3ljz3y9f28-fcitx5-chewing-5.1.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

fcitx5-chewing

Maintainer pings
cc @xrelkd for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

authors: r-ryantm xrelkd


text:
rapidyaml: 0.5.0 -> 0.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/biojppm/rapidyaml/releases.
meta.description for rapidyaml is: A library to parse and emit YAML, and do it fast.
meta.homepage for rapidyaml is: https://github.com/biojppm/rapidyaml
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.0 with grep in /nix/store/ffzwbmdhwn556l5a22whfqp1slqqmfsk-rapidyaml-0.6.0
found 0.6.0 in filename of file in /nix/store/ffzwbmdhwn556l5a22whfqp1slqqmfsk-rapidyaml-0.6.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

rapidyaml

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ffzwbmdhwn556l5a22whfqp1slqqmfsk-rapidyaml-0.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rapidyaml https://github.com/r-ryantm/nixpkgs/archive/3e5c43ea72e41e596634ae925143ce70430e7f74.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3e5c43ea72e41e596634ae925143ce70430e7f74#rapidyaml

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ffzwbmdhwn556l5a22whfqp1slqqmfsk-rapidyaml-0.6.0
ls -la /nix/store/ffzwbmdhwn556l5a22whfqp1slqqmfsk-rapidyaml-0.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

rapidyaml

Maintainer pings
cc @SuperSamus for testing.

I originally added this package for PCSX2, but now it forcefully vendors it. (https://github.com/PCSX2/pcsx2/commit/a9b6f8976e84b5e4874b3343156ce85b867b5ce9#diff-070f9711d42593f839e9cb29c2bcb31f999939af11125c208965891a2ba1617c)
So... I'm not doing anything with it, and currently it has no dependents.
Is the package simple enough that leaving it here doesn't hurt, or not?

authors: SuperSamus r-ryantm


text:
man-db: explicitly pass section string

Work around a bug in the autoconf setup of man-db: The
list of default sections does not include section 0 (zero)
despite ./configure --help advertising it. This causes
header man pages (e. g. time.h from package posix_man_pages)
to be ignored by man(1):
$ file /run/current-system/sw/share/man/man0p/time.h.0p.gz
/run/current-system/sw/share/man/man0p/time.h.0p.gz: gzip compressed data, from Unix
$ man 0p time.h
No manual entry for 0p
No manual entry for time.h

Override the default (as defined in m4/man-arg-sections.m4)
until this is fixed upstream.
Motivation for this change
A category of man pages is not addressable by default.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Patch to man-db has been sent upstream, it rally is their bug. But for
now we can bypass it by forcing the correct list in configure.


text:
dotnet: 9.0.0-preview.4 -> 9.0.0-preview.5

Description of changes
Upgrades both binary and source dotnet packages to 9.0.0-preview.5.
FYI @NixOS/dotnet
I'm not sure why this is out of sync with 6/7/8 releases.

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[x] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319645 run on x86_64-linux 1

9 packages built:

dotnetCorePackages.aspnetcore_9_0
dotnetCorePackages.dotnet_9.aspnetcore
dotnetCorePackages.dotnet_9.runtime
dotnetCorePackages.dotnet_9.sdk
dotnetCorePackages.dotnet_9.sdk.artifacts
dotnetCorePackages.dotnet_9.sdk.packages
dotnetCorePackages.dotnet_9.vmr
dotnetCorePackages.runtime_9_0
dotnetCorePackages.sdk_9_0

Result of nixpkgs-review pr 319645 run on x86_64-linux 1

9 packages built:

dotnetCorePackages.aspnetcore_9_0
dotnetCorePackages.dotnet_9.aspnetcore
dotnetCorePackages.dotnet_9.runtime
dotnetCorePackages.dotnet_9.sdk
dotnetCorePackages.dotnet_9.sdk.artifacts
dotnetCorePackages.dotnet_9.sdk.packages
dotnetCorePackages.dotnet_9.vmr
dotnetCorePackages.runtime_9_0
dotnetCorePackages.sdk_9_0 (dotnetCorePackages.sdk_9_0_1xx)

authors: GGG-KILLER corngood