<clever>
samueldr: this loads ipxe (packaged as a linux kernel) into qemu, to test the ipxe scripts
<clever>
samueldr: the romfile= stuff from the PR you linked, is qemu emulating a dhcp+tfto server, that does basically the same thing as netboot_server.nix
<clever>
so you dont need a seperate VM
Guanin has quit [Remote host closed the connection]
<clever>
samueldr: most of the changes there look good, main thing i can think of is to check the bittorrrent tests
<clever>
[clever@system76:~/nixpkgs]$ nix-build nixos/release.nix -A tests.bittorrent.x86_64-linux
<clever>
running...
<clever>
samueldr: it fails
<samueldr>
can you document the failure on the PR?
<samueldr>
(and thank you)
<clever>
samueldr: done
<samueldr>
clever++
<{^_^}>
clever's karma got increased to 158
<thefloweringash>
hmm, passes for me
<clever>
thefloweringash: from the same git rev?
<thefloweringash>
yep
<clever>
fun, non-deterministic failures!
<clever>
client1: running command: test -e /tmp/test.tar.bz2
<clever>
client1: exit status 1
<clever>
thefloweringash: mine just loops this forevr
<samueldr>
(after all, this is AFAIUI the nixpkgs tarball for that nixos [channel] eval)
orivej has quit [Ping timeout: 245 seconds]
<joko>
samueldr: it seems to be built, thanks once again!
Drakonis has quit [Quit: WeeChat 2.4]
Drakonis has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis_ has quit [Ping timeout: 258 seconds]
Drakonis has quit [Ping timeout: 252 seconds]
Drakonis has joined #nixos-dev
drakonis1 has quit [Ping timeout: 244 seconds]
Drakonis has quit [Ping timeout: 250 seconds]
webster23 has joined #nixos-dev
__monty__ has joined #nixos-dev
<pierron>
hum … I don't know where to find my windows manager stderr … so I went into strace-ing it while reproducing the error and looking for write(2, …)
pierron is now known as nbp
orivej has joined #nixos-dev
Jackneill has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 258 seconds]
tilpner has quit [Quit: WeeChat 2.4]
<gchristensen>
it would be cool for https://r13y.com/ to provide a link back to a github issue, but I can't really do a "search or create new" workflow
tilpner has joined #nixos-dev
Drakonis has joined #nixos-dev
<infinisil>
(Reminder that 19.09 is coming up soon and there is no new release manager yet afaik)
<samueldr>
reminder that 20.03 is coming next and there's no new release manager yet :)
<gchristensen>
definitely
phreedom has quit [Ping timeout: 260 seconds]
<worldofpeace>
hmmmm......
* gchristensen
waggles eyebrows at worldofpeace
<worldofpeace>
I must admit it's something I've been, looking into... just thinking of a good timing
<infinisil>
worldofpeace: It's kinda hard to predict what you'll be doing in half a year
<infinisil>
Well for me at least :)
<worldofpeace>
infinisil: exactly
<infinisil>
Who knows, maybe we'll become Guix people in that time!
<worldofpeace>
lol, I don't think that's likely though
<worldofpeace>
I just know if I get an opportunity in that time frame I'd have to drop everything and just do that
<infinisil>
Maybe yeah
<samueldr>
tbf, with disasm we spoke of it at last nixcon, he already showed interest and I told him to wait until closer to the release to reaffirm, same reasons: no way to know what will happen in close to a year
<gchristensen>
it is a lot of work and a big commitment, for sure
<samueldr>
so I figure the RMs for 19.09 can do the same, and get back to you later
<gchristensen>
I feel we need to find a way to delegate more of the work
<worldofpeace>
gchristensen: totally, thinking the same
<infinisil>
Maybe have a set of ~5 "release-helpers"
<gchristensen>
we would not want to distribute the responsibility though. important to have one (or two) people at the top.
magnetophon has quit [Ping timeout: 246 seconds]
<worldofpeace>
do you mean "at the top" or "at most" gchristensen
<gchristensen>
at the top
<samueldr>
maybe we need a better way to show "ready to help" for good people around the release
<gchristensen>
a person needs to be responsible andfinal in charge for decisions. the rest ofthe people are tohelp
<samueldr>
so the RMs can somehow get their attention of needed
<gchristensen>
samueldr: that sounds good
<gchristensen>
mayb ewe could make a team which is very easy to join as a way to ping "willing and able"
<infinisil>
I personally like the idea of having a small team of dedicated release helpers
<gchristensen>
metoo
<infinisil>
Because otherwise people aren't really feeling any dedication
<infinisil>
Or so
<worldofpeace>
I'd say the people "ready to help" are just the ones who are able to be active at the current time
<gchristensen>
not so loose, I think
<worldofpeace>
and that rotates because of changing circumstances
<gchristensen>
I think there is a number of people who are largely interested in helping a lot
<samueldr>
I'm thinking people like srhb who have been really helpful in getting things going along last two releases in the ZHF thread
<worldofpeace>
i keep a list :)
<gchristensen>
worldofpeace: OH then I should just shut up and let you be the subject matter expert :P
<infinisil>
Idea: Split the release management up into smaller sections. E.g. a NixOS module section, one for docs, one for python packages, ...
<worldofpeace>
gchristensen: oh nope, I don't shut anyone up. experts gotta learn too :)
<worldofpeace>
but on topic with the ZHF thread, it works because it's a sign of a collective effort going on where people can figure how they can insert themselves
<gchristensen>
it is a clear way to participate, with a direct need
<infinisil>
worldofpeace: Hehe, "To prevent massive breakage, ...". We don't have that problem as much with nix because people can just use an older nixpkgs version to get back whatever they need :)
Drakonis has quit [Ping timeout: 248 seconds]
* gchristensen
hopes the big nixops PR will be in 19.09
<worldofpeace>
link gchristensen ?
<infinisil>
Ah, the big nixops PR we all know about which is completely obvious to everybody