| 10 May 2024 |
 Weijia | https://nixos.github.io/release-wiki/Feature-Freeze-Announcement.html#pre-release-cleanup | 09:52:52 |
 Alyssa Ross | aha okay | 09:53:21 |
| Alyssa Ross | I'm thinking of https://github.com/NixOS/nixpkgs/pull/308820 and https://github.com/NixOS/nixpkgs/pull/310170, so I guess both of those would be fine? | 09:53:44 |
| Weijia | Yeah | 09:54:48 |
 hexa | thunderbird 102 is a big security nono 🙂 | 15:58:47 |
| hexa | we can't keep it around | 15:58:54 |
| hexa | the alternative would be to mark it vulnerable and remove it post branchoff | 15:59:25 |
| Alyssa Ross | it's been marked vulnerable since september IIRC | 16:02:22 |
| Alyssa Ross | i.e. we forgot to remove it after the last branch-off | 16:03:02 |
| 12 May 2024 |
|  NixOS Moderation Bot unbanned  nrdxp. | 17:09:18 |
| 13 May 2024 |
 vcunat | Hydra queue looks like today or tomorrow we'd be able to start a new staging-next iteration. Schedule says that in two days we should start the last staging-next iteration (the last one reaching 24.05 at least). | 16:38:02 |
| vcunat | Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just delay by one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) | 16:39:45 |
| vcunat | * Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just make Hydra wait one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) | 16:40:11 |
| Weijia | In reply to @vcunat:matrix.org
Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just make Hydra wait one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) I prefer what's between the parentheses | 16:56:00 |
| Weijia | What about you, Mic92? | 16:58:27 |
 Mic92 | Looks like we don't have too much stuff left queued staging that is zhf related? https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+is%3Apr+label%3A%2210.rebuild-linux%3A+5001%2B%22 | 17:05:28 |
| Mic92 | But I also think we can trigger now and than merge stuff on Wednesday if there is important things in there. | 17:06:00 |
| 14 May 2024 |
| vcunat | Janne Heß: zh.fail is broken (also git.helsinki.tools where it was running, I think) | 04:43:48 |
 Janne Heß | In reply to @vcunat:matrix.org
Janne Heß: zh.fail is broken (also git.helsinki.tools where it was running, I think) It's back, sorry :/ | 06:24:45 |
|  @azahi:azahi.cc joined the room. | 10:29:21 |
|  infinisil changed their profile picture. | 17:44:24 |
 Arian | I'm not planning on fixing the amazonImageZfs image. I don't have any experience with ZFS and i don't think we ever uploaded the ZFS ones to Amazon in the past. Perhaps we can remove it from the release channel? | 18:20:58 |
| Arian | Happy to review a fix for it though. (Sorry I just need to be very aware of my bandwidth) | 18:21:19 |
| Arian | Same for the ec2-nixops test. That can probably just be removed. I can't maintain support for nixops as I never used it | 18:23:37 |
| Arian | (I'll make some PRs so they don't affect ZHF) | 18:24:52 |
 @stablejoy:matrix.org | In reply to @arianvp:matrix.org
I'm not planning on fixing the amazonImageZfs image. I don't have any experience with ZFS and i don't think we ever uploaded the ZFS ones to Amazon in the past. Perhaps we can remove it from the release channel? How important is this? I only have experience with having local zfs and eas looking into this. This just looks interesting | 18:53:06 |
| @stablejoy:matrix.org | In reply to @arianvp:matrix.org
I'm not planning on fixing the amazonImageZfs image. I don't have any experience with ZFS and i don't think we ever uploaded the ZFS ones to Amazon in the past. Perhaps we can remove it from the release channel? * How important is this? I only have experience with having local zfs and was looking into this. This just looks interesting | 18:53:21 |
| Arian | My feeling it is not important given we never uploaded ZFS AMIs to Amazon in the first place so only affects people who were manually uploading them? But i know some people do rely on them. Please have a look! Maybe its just something very simple and trivial | 18:59:39 |
| @stablejoy:matrix.org | In reply to @arianvp:matrix.org
My feeling it is not important given we never uploaded ZFS AMIs to Amazon in the first place so only affects people who were manually uploading them? But i know some people do rely on them. Please have a look! Maybe its just something very simple and trivial Oh great, I could try in couple days | 19:04:34 |
 Bryan Honof | In reply to @arianvp:matrix.org
My feeling it is not important given we never uploaded ZFS AMIs to Amazon in the first place so only affects people who were manually uploading them? But i know some people do rely on them. Please have a look! Maybe its just something very simple and trivial I would very much appreciate if there were NixOS AMI images that at least included the kernel package. In the past I've had to set up my own pipeline to create NixOS images, just to enable that. Let me know if I can help out in any way! 😁 | 22:13:17 |
