<MichaelRaskin>
I remember a change towards doing full nixpkgs-review on each PR, maybe this lead to some more infrastructure work than initially done?
__monty__ has joined #nixos-dev
<adisbladis>
It seems like it got stuck on a stalled build
<adisbladis>
I've restarted the service
FRidh has joined #nixos-dev
<Synthetica>
adisbladis: Awesome :)
<hyperfekt>
since most packaging happens by example i think we could do extremely well in providing an index of packaging styles and packages that implement them 🤔
<hyperfekt>
for example i found no example for an update script for a cargo-built rust package but i'm sure it exists somewhere in nixpkgs
<michaelpj>
hyperfekt: as with all such things, the question becomes "who will write this?" and more importantly "who will maintain it?". Will people who create new styles keep this guide up to date?
alp_ has joined #nixos-dev
alp has quit [Read error: Connection reset by peer]
alp_ is now known as alp
<hyperfekt>
let's see if we can get something going. i'm writing out a few interesting packages but there's no way i can get through all of them
alp has quit [Remote host closed the connection]
<arianvp>
im trying to build the linux kernel; but at the final step of the build it just gets stuck for hours
<gchristensen>
the infra team has to do the images I think
<gchristensen>
but the images were already made and the list was applied to 20.03, so not sure why it isn't updating on the website yet?
<niksnut>
maybe flake.lock needs to be updated?
<gchristensen>
quite probable
<hyperfekt>
This could serve as an intermediary between 'add instructions to the manual' and 'reinvent the wheel for every package': https://nixos.wiki/wiki/Packaging_Examples
<garbas>
niksnut: gchristensen: looking at the problem. looks like update.sh in nixos-homepage is not working (or at least failing for us to notice)
* garbas
first needs to make sure update.sh fails before trying to fix it
phreedom has quit [Ping timeout: 240 seconds]
phreedom_ has joined #nixos-dev
phreedom_ has quit [Quit: No Ping reply in 180 seconds.]
<elvishjerricco>
Ugh, I'm getting very annoyed by the nuke-refs in initrd. I feel like I'd rather not use makeInitrd, considering we're just nuking refs manually anyway. It'd be easier to just copy the files into the archive in their normal positions and avoid having to patch them
ris has joined #nixos-dev
<gchristensen>
meh. nix doesn't even support attribute names containing a thorn. how am I supposed to declaratively manage my midieval Scandinavian machines.
<gchristensen>
oh I can quote it. neat
<cole-h>
(Sorry, but: medieval)
<cole-h>
(Unless your machines produce music)
<gchristensen>
good catch :)
<danderson>
now I want nix to produce MIDI output during evaluation
<danderson>
"man, this machine sounds wrong, I must have missed a piece of config"
<cole-h>
Midi-nix? Midnix? Minix? Wait a second...
<gchristensen>
iirc there was a log-message-to-midi thing so you could "hear" your production system
<clever>
gchristensen: i once had cron configured to beep a different tone every hour, 15mins, and 30mins
<MichaelRaskin>
I think there was something for code, too
<clever>
gchristensen: the same pc was also configured to beep at 15khz any time my name was said on irc, well above my dads hearing, so he couldnt complain when it beeped non-stop for an hour :P
<MichaelRaskin>
Musical profiling of evaluation performance is closer to how debugging on MCUs happen
<gchristensen>
hah!
<danderson>
I've debugged an LCD driver using audio before
<danderson>
turns out it's easy to output register values with dits and dahs
<clever>
danderson: ive seen a blog about dumping the ipod mask rom via the piezo beeper
<clever>
danderson: because they could run custom code, but didnt know how to drive the lcd or get serial
<danderson>
heh, yeah, it's a cool technique. Needs a computer receiving stuff if you want to send lots of data though
<danderson>
I was just dumping a couple bytes at a time
nschoe has joined #nixos-dev
<arianvp>
is the nix.distributedBuilds option in nixos working?
<arianvp>
trying to set up remote builds but cant get it to work
<arianvp>
looking at the nix-daemon.nix code it seems like it's missing a line "builders = @/etc/nix/machines"
<arianvp>
/etc/nix/machines is generated but never passed to nix as an option :/
<clever>
arianvp: what does `nix show-config | grep builders` say?
<arianvp>
ah it does show @/etc/nix/machines
<clever>
arianvp: that would be the default value for when it isnt in nix.conf
<arianvp>
but but when I run nix-build --max-jobs 0 nothing happens :/
<arianvp>
it just says "please enable remote building"
<arianvp>
and I dont see nix-daemon even trying to ssh into the box (no traffic)
<clever>
arianvp: what is the contents of the machines file?
<{^_^}>
#86278 (by adisbladis, 16 hours ago, open): nixos.users-groups: Set up subuid/subgid mappings for all normal users
<infinisil>
Ah you're doing it at runtime now
<adisbladis>
Yeah.. I admitted defeat
<adisbladis>
(Defeat looks a lot like perl)
<cole-h>
Why are some things in perl, others in bash/sh, and yet others in python? "Just because"?
<adisbladis>
cole-h: Reasons ¯\_(ツ)_/¯
<MichaelRaskin>
Because some people think that Perl is more readable than Bash.
<adisbladis>
I think we should at least be semi-consistent about what goes in the minimal installer
<MichaelRaskin>
And for some time Python was not in the mandatory closure
<cole-h>
Alright, that makes sense.
<adisbladis>
Python still has a pretty significant disadvantage over Perl for these type of scripts (and I'm saying this as someone who does a lot of python)
<adisbladis>
Python startup performance is _terrible_
<qyliss>
Is Perl still bad at cross-compiling?
<adisbladis>
qyliss: iirc yes
<adisbladis>
An advantage with Python is that we can get the closure much smaller than Perl, with more in stdlib so we don't need to pull in modules for JSON parsing and such
<adisbladis>
perl == 84.2M
<adisbladis>
python3Minimal == 54.1M
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-dev
<adisbladis>
It'd be interesting to reimplement all of that in a compiled language
<cole-h>
Am I hearing "RiiR"? :P
<qyliss>
what if we rewrote it all in Scheme :P
<adisbladis>
<3 qyliss
<{^_^}>
qyliss's karma got increased to 55
teto has quit [Quit: WeeChat 2.8]
ixxie has quit [Quit: Lost terminal]
FRidh has quit [Quit: Konversation terminated!]
<MichaelRaskin>
Well, if we want simple compilation, reasonable compiled size and readability, that would sound like (modern) Pascal
<MichaelRaskin>
But I agree that rewriting it in Scheme has that benefit of not needing to actually write
<emily>
just rewrite it all in execline. people don't need to be able to read these things right?
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
<arianvp>
I think the remote build is silently failing because the remote builder doesn't have this feature
<clever>
arianvp: nix should be giving an error, saying what features it wants
<arianvp>
oh
<arianvp>
then it's not that. still no clue then
<clever>
arianvp: you can still try adding it to the /etc/nix/machines file though
<ma27[m]>
ahh.... can't you force a remote build using `-j 0`?
<arianvp>
ma27[m]: yes with --max-jobs 0 ' that's what I'm doing
<clever>
ma27[m]: the only machine in /etc/nix/machines lacks the big-parallel flag, so its not a viable one, and then it fails claiming you need to add remote builders
<gchristensen>
is arian the user who nix will be building as?
<gchristensen>
sshing as*
<arianvp>
Ok adding the features got me a step further
<arianvp>
(we should really have an error message for this though? is this a bug?)