worldofpeace changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 20.09 Nightingale ✨ https://discourse.nixos.org/t/nixos-20-09-release/9668 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.09 RMs: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
alp has quit [Ping timeout: 272 seconds]
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
rajivr has joined #nixos-dev
ris has quit [Ping timeout: 240 seconds]
<ajs124> can I look up a job with the name of a drv on hydra?
Gaelan has quit [Quit: ZNC 1.8.1 - https://znc.in]
Gaelan has joined #nixos-dev
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-dev
<abathur> hmm
<abathur> the change in https://github.com/NixOS/nix/commit/c4b9486f9b20d319a7ac3ac2553bdc0fa63c3899 to let the user specify NIX_SSL_CERT_FILE before running the installer also triggers if you're running the multi-user installer from a shell with active single-user nix envs
<siraben> Does `nixpkgs-review` work on PRs that have merge conflicts?
<infinisil> siraben: Have you tried it?
<siraben> infinisil: Yeah and it failed.
<infinisil> Well there you go :)
<siraben> How would I deal with that? Checkout the PR and run the build manually?
<supersandro2000> I just joined the nixos org and there was a link to opt out from further invites
<supersandro2000> Wouldn't that solve the invite bot issue?
<infinisil> siraben: There's the `wip` subcommand
<infinisil> supersandro2000: What invite bot issues?
<abathur> infinisil: I think he means the one where the invite bot is disabled because it wouldn't quit inviting people who didn't want to join
<infinisil> Oh is this about the nixpkgs maintainers team?
<infinisil> I've never seen an invite bot though
<abathur> I think so; there was some attempt to auto-invite people given some magical prereqs (added to the maintainers file?)
<abathur> not really in the loop, just recall seeing it discussed :)
<supersandro2000> Yeah exactly this invite bot
justan0theruser has joined #nixos-dev
<supersandro2000> Also I got auto subscribed to 4 repos: hardware, pills, weekly and idea
<supersandro2000> I am glad not nixpkgs or my inbox would be full by the end of the month
justanotheruser has quit [Ping timeout: 272 seconds]
<siraben> supersandro2000: what was the process for joining the maintainers team?
<cole-h> (They didn't join the maintainers team, but the committers team.)
<siraben> Ah.
<cole-h> Though the process for joining the maintainers team is (at this time) very manual.
<{^_^}> rfc39#3 (by cole-h, 8 weeks ago, open): Create a database of already-invited users and don't invite them again
<abathur> I guess (re: https://github.com/NixOS/nix/commit/c4b9486f9b20d319a7ac3ac2553bdc0fa63c3899) the installer needs to either 1) install the cert regardless, but only export NIX_SSL_CERT_FILE if it wasn't set, or 2) only respect NIX_SSL_CERT_FILE if it is set to some location outside of /nix?
<abathur> though, looking into trying to canonicalize the path on macOS is making me afraid the latter is a fool's errand with just stock utilities
<abathur> ah, found a clumsy way to do that with $(cd && /bin/pwd -P), at least :)
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
<ashkitten> #102595 was merged without making sure it builds. it does not build because the patches that say "can be removed on next release" were not removed
<{^_^}> https://github.com/NixOS/nixpkgs/pull/102595 (by r-ryantm, 2 weeks ago, merged): libshout: 2.4.3 -> 2.4.4
<ashkitten> how did ofborg tests pass?
<samueldr> ashkitten: which patches? https://github.com/NixOS/nixpkgs/pull/102595/files
<ashkitten> uhh
<ashkitten> hm
<ashkitten> my nixpkgs is screwed isnt it
<samueldr> maybe
<ashkitten> whoops
<ashkitten> nvm
<ashkitten> `git blame`
<ashkitten> ......
<cole-h> hehe
<ryantm> Also, r-ryantm only submits PRs that build on x86_64
<ashkitten> good to know
<ashkitten> i feel very silly now :p
cole-h has quit [Ping timeout: 256 seconds]
MichaelRaskin has quit [Quit: MichaelRaskin]
FRidh has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
<supersandro2000> siraben: I got suggested on the issue and then waited a while and got invited this night
saschagrunert has joined #nixos-dev
lightbulbjim has joined #nixos-dev
lightbulbjim has left #nixos-dev [#nixos-dev]
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-dev
AlwaysLivid has quit [Read error: Connection reset by peer]
AlwaysLivid has joined #nixos-dev
AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
alp has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has quit [Changing host]
sgrunert has joined #nixos-dev
saschagrunert has quit [Ping timeout: 272 seconds]
Jackneill has joined #nixos-dev
kfound has joined #nixos-dev
kfound has quit [Ping timeout: 260 seconds]
Mic92 has quit [Quit: WeeChat 2.9]
Mic92 has joined #nixos-dev
sphalerite has quit [Quit: reboot time!]
sphalerite has joined #nixos-dev
<das_j> Might be a weird question, but can I access the overriden value when using mkForce and friends?
Ericson2314 has quit [Quit: Bridge terminating on SIGTERM]
symphorien[m] has quit [Quit: Bridge terminating on SIGTERM]
mkg20001 has quit [Quit: Bridge terminating on SIGTERM]
bk1603[m] has quit [Quit: Bridge terminating on SIGTERM]
worldofpeace has quit [Quit: Bridge terminating on SIGTERM]
rycee has quit [Quit: Bridge terminating on SIGTERM]
emily has quit [Quit: Bridge terminating on SIGTERM]
Dandellion has quit [Quit: Bridge terminating on SIGTERM]
regnat has quit [Quit: Bridge terminating on SIGTERM]
jonge[m] has quit [Quit: Bridge terminating on SIGTERM]
Ox4A6F has quit [Quit: Bridge terminating on SIGTERM]
Valodim[m] has quit [Quit: Bridge terminating on SIGTERM]
aterius has quit [Quit: Bridge terminating on SIGTERM]
aanderse has quit [Quit: Bridge terminating on SIGTERM]
domenkozar[m] has quit [Quit: Bridge terminating on SIGTERM]
bbigras has quit [Quit: Bridge terminating on SIGTERM]
treed[m] has quit [Quit: Bridge terminating on SIGTERM]
Irenes[m] has quit [Quit: Bridge terminating on SIGTERM]
matthewkenigsber has quit [Quit: Bridge terminating on SIGTERM]
siraben has quit [Quit: Bridge terminating on SIGTERM]
ma27[m] has quit [Quit: Bridge terminating on SIGTERM]
kraem has quit [Quit: Bridge terminating on SIGTERM]
puzzlewolf has quit [Quit: Bridge terminating on SIGTERM]
maralorn has quit [Quit: Bridge terminating on SIGTERM]
rnhmjoj has quit [Quit: Bridge terminating on SIGTERM]
thefloweringash has quit [Quit: Bridge terminating on SIGTERM]
philipp[m] has quit [Quit: Bridge terminating on SIGTERM]
ryantm has quit [Quit: Bridge terminating on SIGTERM]
timokau[m] has quit [Quit: Bridge terminating on SIGTERM]
alexarice[m] has quit [Quit: Bridge terminating on SIGTERM]
zowoq[m] has quit [Quit: Bridge terminating on SIGTERM]
DamienCassou has quit [Quit: Bridge terminating on SIGTERM]
michaelpj has quit [Quit: Bridge terminating on SIGTERM]
roberth has quit [Quit: Bridge terminating on SIGTERM]
jtojnar has quit [Quit: Bridge terminating on SIGTERM]
colemickens has quit [Quit: Bridge terminating on SIGTERM]
danielrf[m] has quit [Quit: Bridge terminating on SIGTERM]
nh2[m] has quit [Quit: Bridge terminating on SIGTERM]
dstzd has quit [Quit: ZNC - https://znc.in]
dstzd has joined #nixos-dev
kraem has joined #nixos-dev
dstzd has quit [Read error: Connection reset by peer]
dstzd has joined #nixos-dev
worldofpeace has joined #nixos-dev
ryantm has joined #nixos-dev
philipp[m] has joined #nixos-dev
symphorien[m] has joined #nixos-dev
Ox4A6F has joined #nixos-dev
emily has joined #nixos-dev
rycee has joined #nixos-dev
maralorn has joined #nixos-dev
regnat has joined #nixos-dev
aterius has joined #nixos-dev
mkg20001 has joined #nixos-dev
roberth has joined #nixos-dev
nh2[m] has joined #nixos-dev
siraben has joined #nixos-dev
colemickens has joined #nixos-dev
bbigras has joined #nixos-dev
bk1603[m] has joined #nixos-dev
matthewkenigsber has joined #nixos-dev
alexarice[m] has joined #nixos-dev
thefloweringash has joined #nixos-dev
jonge[m] has joined #nixos-dev
DamienCassou has joined #nixos-dev
aanderse has joined #nixos-dev
michaelpj has joined #nixos-dev
Dandellion has joined #nixos-dev
Ericson2314 has joined #nixos-dev
timokau[m] has joined #nixos-dev
jtojnar has joined #nixos-dev
JJJollyjim has joined #nixos-dev
Irenes[m] has joined #nixos-dev
danielrf[m] has joined #nixos-dev
puzzlewolf has joined #nixos-dev
Valodim[m] has joined #nixos-dev
domenkozar[m] has joined #nixos-dev
ma27[m] has joined #nixos-dev
rnhmjoj has joined #nixos-dev
zowoq[m] has joined #nixos-dev
treed[m] has joined #nixos-dev
dstzd has quit [Client Quit]
dstzd has joined #nixos-dev
<infinisil> das_j: nope
<mkaito> in the test API, there's a method to copy from the vm, a method to copy TO the vm, but no method to copy between VMs. any way to do that, other than ssh?
<das_j> nice
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-dev
<siraben> Can I make `/nix` be a symlink that points to a different volume?
<siraben> On my reMarkable tablet there's not enough space on the root partition to install Nix
<qyliss> yes, you can
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
<qyliss> I believe Nix will warn about that by default
<siraben> And without it having to rebuild everything?
<qyliss> yes
<qyliss> although the reason it warns is that if anything resolves symlinks on a path in its build directory, it'll get the non-/nix path
<siraben> How do I do that? I have the installation script `install` ready
<qyliss> the install script is probably not going to like this
FRidh has quit [Ping timeout: 268 seconds]
<qyliss> if I were in this situation I'd build Nix from source on the other volume, set up /nix as a symlink pointing to an empty directory, install Nix with the built-from-source Nix, then remove the built-from-source Nix
FRidh has joined #nixos-dev
<siraben> build Nix from source on the device?
<qyliss> yeah
<siraben> it's an armv7l, gonna be awfully slow
<qyliss> at a custom prefix on the other volume
<qyliss> well you could built it on something else as long as you got the prefix right
<qyliss> that's not important
<qyliss> you could _try_ running the installer with /nix being a symlink to an empty directory, but I wouldn't expect it to work
alp has quit [Ping timeout: 272 seconds]
<siraben> Hmm
<siraben> A compromise might be to cross-compile statically as much as possible for now.
<siraben> How can the performance of Nix be improved? What's the current bottlenecks?
alp has joined #nixos-dev
<regnat> siraben: You should be able to install Nix with /nix already existing. So if you make it a symlink (or better a bind-mount) before running the installer it should work
<siraben> regnat: Should I hardlink it?
tilpner has quit [Quit: tilpner]
<qyliss> you can't hardlink a directory
<qyliss> you also can't hardlink between volumes
<siraben> `error: the path '/nix' is a symlink; this is not allowed for the Nix store and its parent directories`
<siraben> `./install: unable to register valid paths`
<regnat> siraben: nah you can't hardlink it indeed, but you can mount a directory (like you'd mount a partition) with mount --bind src dest
<qyliss> siraben: try setting NIX_IGNORE_SYMLINK_STORE
<qyliss> (to "1")
<siraben> Oh, seems to have gone well!
<siraben> heh i only have 500 MB of ram, need to make a swapfile
tilpner has joined #nixos-dev
<domenkozar[m]> ugh
<domenkozar[m]> error: /nix/store/y41vgrya42wlzq8zpywkccaiknzpcraz-xz-5.2.5/lib/liblzma.so: error: undefined reference to 'pthread_sigmask', version 'GLIBC_2.32'
<domenkozar[m]> there we are again, glibc from 20.09 and master don't work together
<siraben> Swapfile added! Hopefully another GB lets me upgrade nix
ehmry_ has joined #nixos-dev
ehmry_ is now known as ehmry
<siraben> regnat: Will the mount survive a rebbot?
<siraben> reboot*
<regnat> siraben: nope, you need to run each at each boot
<regnat> s/each/it
<siraben> I just aborted the upgrade to nix 2.3.8 since it would have spent a lot of time compiling things, time to learn about remote builders I guess?
<sphalerite> siraben: I used a bind-mount to mount nix from the data partition to /nix
<sphalerite> siraben: and cross-compiled everything I use on the remarkable basically
<sphalerite> I don't remember how I made the bind-mount persistent though, maybe by editing /etc/fstab
<siraben> sphalerite: oh, another remarkable user? nice!
<sphalerite> :)
<sphalerite> I think I mostly used nix to get rsync on it, so I can back my notes up
<sphalerite> I love how hackable the software is, not so much how hackable the hardware is…
<infinisil> nixpkgs haskell docs now live in https://haskell4nix.readthedocs.io/ :/
<siraben> Oops, I accidentally bricked the device by messing around in `/etc/fstab` 😅, recovered now.
<siraben> sphalerite: let me know what linei you used in /etc/fstab, because for some reason adding my line prevented it from booting
<siraben> sphalerite: So you cross-compiled to armv7l and copied it over with `nix-copy-closure`?
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-dev
<sphalerite> siraben: ouch. I'll check when I'm home and have access to it
<sphalerite> siraben: yes
<siraben> sphalerite: good thing there's github.com/ddvk/remarkable-uuuflash
<ehmry> I'm getting double output in my builds, each line is repeated once, has anyone else experienced this?
AlwaysLivid has quit [Remote host closed the connection]
<sphalerite> siraben: oooh I didn't know about that, very good! Thanks
red[evilred] has joined #nixos-dev
<red[evilred]> Random Question. Historically I only had an average of maybe one Issue/PR I was working at a time so easy to manage.
<red[evilred]> How do people track when they have tens of issues / PRs to know when stuff gets updated / commented / closed etc?
<sphalerite> red[evilred]: notifications, or https://github.com/pulls
thibm has joined #nixos-dev
abbe__ has quit [Quit: “Everytime that we are together, it's always estatically palpitating!”]
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-dev
<red[evilred]> Thanks - I guess I just need to keep a running count so I know if any have been merged / rejected then I guess
<red[evilred]> not a huge deal
<red[evilred]> since nobody else is going to open a PR in my name - shouldn't be hard to track.
alp has quit [Ping timeout: 272 seconds]
abbe_ has joined #nixos-dev
<siraben> red[evilred]: yeah contributing to nixpkgs was when i started having to juggle dozens of PRs simultaneously, I turned on GitHub email notifications as result and it's quite good
<red[evilred]> I did that but turned on all notifications because I wanted to have automation to track all the things
<red[evilred]> it looks like I may need to set up a separate github account with a separate EMail address to separate the two I guess
<red[evilred]> I mean I could write some code to follow the event stream for all my issues / prs
<red[evilred]> and it's easy to do
<red[evilred]> I just didn't want to reïnvent the wheel if someone had done it alreadu
thibm has quit [Quit: WeeChat 2.6]
<red[evilred]> Question - Do Release Managers continue to manage their release until EOL?
<red[evilred]> or are they just responsible for it until release day?
alp has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
cole-h has joined #nixos-dev
<FRidh> I would like to remove aarch64 as blocker for nixpkgs-unstable https://github.com/NixOS/nixpkgs/pull/104679
<{^_^}> #104679 (by FRidh, 4 minutes ago, open): release.nix: remove aarch64 as blocker, fixes #104550
<hexa-> reposted to #nixos-aarch64
<hexa-> I feel like things were working pretty well until the recent builder downtime
<FRidh> yes
<cole-h> Is there an aarch64 channel that people can use instead of nixpkgs-unstable? I don't remember.
<hexa-> and I honestly cannot build most of the stuff I need on my rpi4 :)
<andi-> No there is no other channel
<andi-> There are jobsets for the stable releases but not for unstable and neither have a channel
alp has quit [Ping timeout: 272 seconds]
__monty__ has joined #nixos-dev
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
FRidh has quit [Ping timeout: 240 seconds]
<siraben> When trying nix-copy-closure I get `bash: nix-store: command not found` as a response, however when I ssh into the device, running nix-store works
<gchristensen> try `ssh foo nix-store`
<cole-h> Sounds like the remote machine isn't sourcing the profile to get Nix in PATH on non-interative sessions
orivej has quit [Ping timeout: 256 seconds]
<cole-h> Maybe the https://nixos.wiki/wiki/Distributed_build wiki page will help
rajivr has quit [Quit: Connection closed for inactivity]
<siraben> gchristensen: yep, `bash: nix-store: command not found`
<gchristensen> cole-h's got the right idea :)
<LnL> I really wonder if nix should just try to fallback to ?remote-program=/nix/var/nix/profile/default/bin/nix-store by default
orivej has joined #nixos-dev
<LnL> 90% of the time that works
sgrunert has quit [Remote host closed the connection]
<red[evilred]> the only thing that scares me about fallbacks is taht you lose a lot of predictability that way.
<red[evilred]> I guess it depends on what is more important to (the wider) you.
<red[evilred]> That it work "Every Time"™, or that every execution of the same input results in the same output.
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
justan0theruser has quit [Ping timeout: 260 seconds]
<siraben> cole-h: Hm, which profile is it sourcing to get Nix in PATH?
<andi-> For starters we could document the remote-program flag somewhere other than just the source code.
justan0theruser has joined #nixos-dev
alp has joined #nixos-dev
<siraben> ` NIX_SSHOPTS="source .profile;" nix-copy-closure` worked
<sphalerite> oh goodness
<gchristensen> beautiful
<siraben> ok, now to corss-compile Nix and upgrade it on the tablet. Maybe I can get remote builds to work so `nix-build` on the tablet would automatically forward it to my computer.
<siraben> If I'm understanding that correctly
<rycee> Howdy, anybody with Nix 3 insights around? I'm curious if the `nix profile {info,install,remove}` commands are considered stable or experimental? In HM we use `nix-env -i`, which apparently is causing errors like "'/nix/var/nix/profiles/per-user/user/profile' is incompatible with 'nix-env'; please use `nix profile` instead" for users who use Nix 3…
<rycee> So I'm wondering if it would be considered safe to use the `nix profile` commands inside an if statement that checks for `nix --version >= 2.4`.
<cole-h> All of nix(1) is experimental, FWIW.
orivej has quit [Ping timeout: 272 seconds]
<rycee> Yeah, that is my impression as well, considering `nix --help` says "Note: this program is EXPERIMENTAL and subject to change." :-) But I was hoping that the profile sub-command might be more stable?
<rycee> Considering that it seems incompatible with the corresponding stable nix-env command.
FRidh has joined #nixos-dev
<gchristensen> anyone available to make a fairly small patch to https://github.com/packethost/terraform-provider-packet for me, (somewhat) related to the aarch64 builders?
<cole-h> As long as it's cool to be unable to test it, sure.
<gchristensen> specifically: making spot_market_request's instance_parameters parameter support ipxe_script_url in the same way https://registry.terraform.io/providers/packethost/packet/latest/docs/resources/device does. shouldn't be tricky, finding references to ipxe_script_url in https://github.com/packethost/terraform-provider-packet/blob/master/packet/resource_packet_device.go and mirroring them (modified
<gchristensen> unable to test is fine, if you can include a shell.nix which gives me terraform 0.12 + the patched plugin, I can test it
ris has joined #nixos-dev
{^_^} has quit [Excess Flood]
{^_^} has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
<gchristensen> cole-h: to confirm: you're hacking on thaht?
<cole-h> Trying, but it doesn't seem like SpotmarketRequestInstanceParameters has an IPXEScriptURL parameter. Adding that would require patching packngo
<gchristensen> *deep sigh*
<gchristensen> can you PR that to packngo, and propose a (obviously broken) patch to the terraform provider linking to the PR to packngo?
* cole-h clones packngo
<cole-h> Ah, the sacred art of yak shaving
<gchristensen> ****sighs intensify****
FRidh has quit [Quit: Konversation terminated!]
<danderson> the derivation builds fine on my local nix (with sandbox, and a clean cache), so I'm not seeing what its problem i.
<danderson> and so, I'm kinda stuck with a red CI that won't tell me what's wrong :(
<samueldr> danderson: originating PR
<{^_^}> #104702 (by grahamc, 29 minutes ago, merged): Revert "influxdb2: init at v2.0.2"
<danderson> er
<samueldr> heh
<{^_^}> #104702 (by grahamc, 29 minutes ago, merged): Revert "influxdb2: init at v2.0.2"
<samueldr> danderson: are you sure?
<danderson> ffs
<cole-h> x2 heh
<{^_^}> #104484 (by danderson, 2 days ago, merged): influxdb2: init at v2.0.2
<danderson> thanks chrome for updating the rendered page but not the URL. Real helpful.
<cole-h> Not just Chrome. Happens to me on Firefox as well.
<samueldr> >> cannot read '/nix/store/aip17cbq5ywh0xp5hkx4kq98g84zhjzd-source/ui/package.json', since path '/nix/store/zcjs42hsvrfqlp4smhdszranpsai3im6-source.drv' is not valid,
<samueldr> mkYarnPackage might do something at eval time causing an "IFD"
<samueldr> ,IFD
<{^_^}> import-from-derivation (IFD) is when you evaluate nix from a derivation result, for example `import (pkgs.writeText "n" "1 + 1")` will evaluate to 2. This is sometimes problematic because it requires evaluating some, building some, and then evaluating the build result. It has been described as "such a nice footgun."
<danderson> hrm. It shouldn't be, given it's how you're supposed to build yarn stuff in general?
<danderson> but yay for me discovering a footgun I guess
<samueldr> I'm looking up the info
<danderson> oh, hmm. I see. It's reading package.json in order to generate a derivation containing the node deps
<samueldr> but IIRC one of the yarn2nix has two modes of operations
<samueldr> yeaj
<samueldr> yeah*
<danderson> yeah, there's a mode where I can pre-generate the .nix
<danderson> so I guess that's what that's for :)
<samueldr> look at pkgs/applications/networking/instant-messengers/element/element-desktop.nix
<danderson> okay, this helps, thanks.
<samueldr> it uses mkYarnPackage, but has the .json and a generated .nix file
<samueldr> >> # NOTE: this is optional and generated dynamically if omitted
<danderson> got it
<danderson> yeah, I saw it was optional and went "well no need to do that then"
<danderson> so, one more question: why did this fail on ofborg and not locally? Does ofborg toggle a special "be mean about IFD" mode that I could also enable?
<samueldr> yes
<samueldr> this is the sneakiest .nix expression ever: it's executable too!
<samueldr> so if you're in your Nixpkgs checkout, calling ~/path/to/ofborg/src/outpaths.nix shoule eval in that manner
<samueldr> hm, I'm not positive it's _this_ eval though
<samueldr> and it might be missing the "strict" bits
<samueldr> yes, it's that eval, might be missing the "strict" bit still
<danderson> yeah, not seeing anything obvious in there that I can steam for my nix config
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
<gchristensen> you can set in your nix.conf allow-import-from-derivation=false
<danderson> awesome, cheers
<danderson> does nixpkgs disallow IFD across the board?
<gchristensen> yeah, no IFD for nixpkgs
<supersandro2000> IFD is dependency hell?
<gchristensen> IFD makes the evaluation phase non-static
<danderson> it's a pity, because it is really nice to do stuff like mkYarnPackage and friends
<danderson> but, oh well
<gchristensen> yeah :(
<danderson> I'm also now curious how come buildGoModule doesn't end up doing that, yet also doesn't require maintaining a yarn lock
<samueldr> I'm not positive for that, but often it's through cheating with FODs (fixed-output derivations)
<samueldr> you have a sha256 of the output of doing the installation through whatever package management method
<samueldr> it works good enough if the output actually is reproducible and stable
<samueldr> but it's not clean and probably (most likely) is an abuse of FODs
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
mkaito has quit [Quit: WeeChat 2.9-dev]
<red[evilred]> uh oh
<cole-h> Also, --no-allow-import-from-derivation on the command line
<cole-h> Or --option allow-import-from-derivation false
__monty__ has quit [Quit: leaving]
<LnL> I had that in my config for a while, but breaks a ton of tools :/
<cole-h> Yeah. I prefer the CLI flag myself.
<cole-h> andi-: Anything blocking https://github.com/NixOS/nixpkgs/pull/104106 still? ;-)
<{^_^}> #104106 (by cole-h, 5 days ago, open): [20.09] crate2nix: init at 0.8.0
<andi-> cole-h: didn't I approve?
<cole-h> Oh yeah. I guess I should ping worldofpeace / jonringer for merge, then.
<andi-> cole-h: I somehow had the impression you were able to merge
<cole-h> Haha. Not yet :P
<cole-h> Thanks!
<cole-h> andi-++
<{^_^}> andi-'s karma got increased to 46
<{^_^}> cole-h's karma got increased to 111
<cole-h> I was wondering what those changes had to do with NixOS :P Guess I should have taken the hint from the fact that Packet was involved.
<samueldr> might be time to get cole-h on the committer train
<cole-h> Right now, that wouldn't really change much, considering my lack of free time haha (despite how often I sit in IRC chatting...)
<samueldr> how many time have you seen me merge things in Nixpkgs proper unprompted? :)
* cole-h thinks really hard.
* cole-h greps #nixos logs.
<samueldr> if there was a quota to keep up with we'd see many long-standing trusted contributors losing their rights :)
<cole-h> Well, the quota seems to be once per year :P
alp has quit [Ping timeout: 260 seconds]
<{^_^}> resolved: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
<gchristensen> "fixed the glitch"
<andi-> samueldr: wasn't there this RFC to retire comitters after 3m of inactivity?
<cole-h> 1y
<cole-h> rfcs#55
<{^_^}> https://github.com/NixOS/rfcs/pull/55 (by tilpner, 1 year ago, merged): [RFC-0055] Retire inactive nixpkgs committers
* andi- goes into deepsleep
orivej has joined #nixos-dev
<danderson> retiring committers after 3 minutes of inactivity seems a bit harsh
<danderson> but hey, you're a true believer or you're not!
<andi-> either you commit to it or not ;-)
<gchristensen> at least it is a duration, after 1 yard is even weirder. 1 yard of patches?
<danderson> samueldr: and yeah, buildGoModule requires the sha256 of the "vendored packages" derivation
<danderson> it would be nice to have some way of making IFD more principled somehow, so that integrating with package managers that have their own locks and hashes doesn't require extra work
<danderson> otoh, it's a minor extra effort to make nixpkgs completely hermetic, so...
* danderson taps the sightglass on https://github.com/NixOS/nixpkgs/pull/104717 , wondering why ofborg isn't evaling
<{^_^}> #104717 (by danderson, 22 minutes ago, open): influxdb2: init at v2.0.2
terrorjack has quit [Ping timeout: 264 seconds]
<abathur> we'll print out your diffs on a dot-matrix printer and if you can't manage a yard...
<samueldr> danderson: most likely because it's doing other evals first :)
<gchristensen> limited budget :)
<danderson> but I want my results nowwwwwwwwwwww
<danderson> but wow, that's a lotta evals
<cole-h> Guess people are busy(?) today
<samueldr> peeps doing stuff
justan0theruser has quit [Ping timeout: 264 seconds]
justan0theruser has joined #nixos-dev