<lukegb>
adisbladis: do you have an example of something that was broken before that's fixed now?
<clever>
[root@amd-nixos:~]# nix-shell '<nixpkgs>' -A libudev
<clever>
anonymous function at /nix/store/1v1jczwm2d4wff3yq5j3zrknifpk8m77-nixos-21.03pre243434.e0759a49733/nixos/pkgs/top-level/default.nix:20:1 called with unexpected argument 'inNixShell'
<clever>
not sure how, but nix-shell seems broken for me now
<adisbladis>
lukegb: Not a minimal one, but something along these lines: `python3.override { packageOverrides = self: super: { wheel = super.wheel.overridePythonAttrs(old: rec { name = "${old.pname}-${version}"; version = "0.33.3"; src = {...}; }) } }`
<adisbladis>
Where the wheel override wouldn't get picked up by pythotFromBuild and the build-time version checks fail
* lukegb
nods
<FRidh>
don't forget to pass `self = mypython;` to `python3.override`
<FRidh>
note overrideScope' is now also available, if you prefer that
<adisbladis>
FRidh: [overrideScope'] Oh, good to know :)
<adisbladis>
FRidh: Do you mean to add pythonPackagesBuildHost as a nested set under the regular python3.pkgs?
<hexa->
FRidh: so what's the deal with merging stuff into staging. Can I do that myself? If so, is there anything I need to watch out for?
<hexa->
i regularly have some security stuff, that should go in rather sooner than later
<hexa->
AFAIU there is a stabilization period and merging something in will certainly extend that period, if not done at the right time
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-dev
<hexa->
17:08 <hexa-> FRidh: so what's the deal with merging stuff into staging. Can I do that myself? If so, is there anything I need to watch out for?
<hexa->
17:08 <hexa-> i regularly have some security stuff, that should go in rather sooner than later
<hexa->
17:09 <hexa-> AFAIU there is a stabilization period and merging something in will certainly extend that period, if not done at the right time
<hexa->
but I'm seeing this every once in a while from you
<supersandro2000>
me not paying attention what build on darwin and what not
<supersandro2000>
basically means there are no builds for darwin.
<supersandro2000>
sometimes this also happens when ofborg tells you that there are darwin rebuilds
<hexa->
but the package does not seem to exclude darwin?
<supersandro2000>
maybe on dependency. Didn't look further into this
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
<supersandro2000>
I am currently regenerating the node packages in nixpkgs. Going to merge that later into master. I would appreciate it if no one could merge something in the next hour or two
<samueldr>
what does this mean?
<samueldr>
shouldn't this go through a PR?
<cole-h>
^
<cole-h>
Here's how it should go: 1) Open PR 2) Wait for ofborg to finish eval 3) If all looks good and no conflicts, merge. 4) Else, resolve conflicts, push, and return to step 2