| 9 Jan 2025 |
 hexa |
Update - We have identified the root cause and have deployed a fix. Service are recovering.
| 02:10:07 |
 Ainz Ooal Gown | In reply to @hexa:lossy.network
sent an image. GitHub be like: testing in production | 05:42:13 |
 pveierland | What is the scope of the by-name path in nixpkgs? Is this used for all new packages, or only certain types of packages? | 06:38:44 |
 ElvishJerricco | pveierland: all new packages, I believe | 06:42:57 |
| ElvishJerricco | I think there are exceptions. Like I think there are some language specific package sets that remain organized the way they were before | 06:43:52 |
 Emma [it/its] | is there a tracking issue for pysaml2? | 07:43:26 |
| Emma [it/its] | seems there is, but hasnt been updated since last week | 07:44:19 |
 Emmanuel Genga | https://github.com/NixOS/nixpkgs/pull/371449
Anyone who can restart the eval for me, it failed all checks | 09:53:05 |
 adisbladis | Annoyingly it seems that you have to go check by check and trigger it. I'd rebase and push again. | 09:57:54 |
| Emmanuel Genga | In reply to @adis:blad.is
Annoyingly it seems that you have to go check by check and trigger it. I'd rebase and push again. I've done that twice already, I'll try again | 10:48:15 |
|  Dirk Van Haerenborgh @ FOSDEM joined the room. | 17:09:32 |
| ElvishJerricco | emily, hexa: I'm really tempted to just send it on the hyperv PR so we can merge the ISO specialisation / linux_latest PR. I don't really think anyone's going to come out of the woodwork to test the hyperv thing for me, and it seems unlikely to break anything anyway. | 20:01:43 |
| ElvishJerricco | does that sound ok to you two? | 20:01:59 |
 emily | just do it | 20:02:07 |
| emily | or disable it entirely and let it break | 20:02:18 |
| emily | so that the people who care about it know they need to step up to test stuff | 20:02:26 |
| ElvishJerricco | I think what I did will work, so I'll just send it rather than disabling it. | 20:02:52 |
| ElvishJerricco | if it breaks, then I guess it'll have the same effect of getting the people who care to show up :P | 20:03:37 |
| ElvishJerricco | Ok. Merged the hyperv one. | 20:04:18 |
| ElvishJerricco | I would like to get someone's explicit github approval on the ISO PR though: https://github.com/NixOS/nixpkgs/pull/355893 | 20:04:29 |
| emily | well, the flipside is that it might break in a more subtle way, and that people who use it might have no idea it's endangered :) | 20:07:38 |
| emily | but merging is good too | 20:07:43 |
| emily | how does the entry show up in the menu btw? | 20:08:37 |
| emily | quick scan of the code looks good to me but do you need to explicitly specify the latest kernel if using nixos-generate-config? I think it should be default when booted into the latest kernel ISO | 20:09:32 |
| emily | or, ah, I guess you inject a config file, ok | 20:09:48 |
| ElvishJerricco | 
Download image.png | 20:10:31 |
| ElvishJerricco | looks like this | 20:10:34 |
| ElvishJerricco | The latest kernel entry is a submenu that has all the same sub-options, but of course no "latest kernel" specialisation entr | 20:10:57 |
| ElvishJerricco | * The latest kernel entry is a submenu that has all the same sub-options, but of course no "latest kernel" specialisation entry | 20:10:58 |
| ElvishJerricco | 
Download image.png | 20:11:35 |
