| 26 Nov 2025 |
leona | I would also say that dropping it now is fine | 12:52:07 |
xanderio | Adding the backport release-25.11 should be enough than? | 13:00:43 |
leona | Yes | 13:00:53 |
leona | (And security) | 13:00:57 |
xanderio | Should a release note entry regarding this be added to the nixpkgs or nixos notes? Personally I'm not even sure if this needs a release note entry. | 13:18:40 |
leona | Nixpkgs release notes in that case, as not a modification to a NixOS module | 13:20:06 |
| 27 Nov 2025 |
| Kacper Uminski joined the room. | 00:27:42 |
eveeifyeve | Would I sitll be able to back port to 25.11 to remove nim1? | 02:10:34 |
eveeifyeve | * Would I sitll be able to backport to 25.11 to remove nim1 because at this point it's EOL? | 02:10:47 |
eveeifyeve | I will have to backport manually the specific commit. | 02:11:22 |
eveeifyeve | Also please check this comment: https://github.com/NixOS/nixpkgs/issues/443568#issuecomment-3583858495 | 02:11:58 |
eveeifyeve | * Would I sitll be able to backport to 25.05 to remove nim1 because at this point it's EOL? | 02:12:41 |
eveeifyeve | * Would I sitll be able to backport to 25.05 & 25.05 to remove nim1 because at this point it's EOL? | 02:12:58 |
eveeifyeve | * Would I sitll be able to backport to 25.05 & 25.11 to remove nim1 because at this point it's EOL? | 02:13:06 |
leona | I can say, that I now quite a lot of machines booting with 25.11+6.17+systemd-boot perfectly fine (all of mine e.g.) | 08:28:44 |
leona | with such a issue that takes a unknown amount of time to debug, no not a release blocker. | 08:29:30 |
eveeifyeve | Also could you please answer the nim question above? | 13:11:51 |
leona | sorry, I don't know what I should answer again. In https://github.com/NixOS/nixpkgs/pull/460946#issuecomment-3526986437 you said that nim1 is still in LTS mode, now you said it's not. With that I cannot give you a clear answer.
If nim1 is not maintained, you can probably now remove it from 25.11. If you need more time, mark it as vulnerable in 25.11. Please don't remove it in 25.05, just mark it as vulnerable if it's not maintained
| 13:20:32 |
leona | If it's still maintained I would prefer keeping it for 25.11 | 13:24:58 |
eveeifyeve | It's not maintained. | 13:34:16 |
eveeifyeve | * It's not maintained so I will mark it vulnerable in 25.05 and remove it in 25.11. | 13:38:24 |
| 28 Nov 2025 |
| Grimmauld (any/all) changed their display name from grimmauld (any/all) to musl-official | Grimm | any/all. | 11:35:37 |
| Grimmauld (any/all) changed their display name from musl-official | Grimm | any/all to Grimmauld (any/all). | 11:36:00 |
leona | hi, getchoo , dish [Fox/It/She] do you need anything regarding the release notes? We plan to release sometime on Sunday | 12:43:21 |
leona | also how would you like to be named in the release blogpost? ^^ | 12:44:21 |
leona | I started modifying the original release announcement at https://md.leona.is/ec3cH-kcThye6UGIhO-gqA#. It still needs some work before it will be a draft PR in the marketing repo | 12:49:40 |
leona | especially I'm unhappy with the
NixOS is already known as the most up to date distribution while also being the distribution with the most packages.
this sounds exactly like we want every possible package in Nixpkgs, which we should really not. If anything has a good idea..
| 12:50:19 |
soenke | maybe focus on fairly up to date with possibility to use newest packages where needej | 12:55:20 |
soenke | * maybe focus on fairly up to date with possibility to use newest packages where needed | 12:55:40 |
jopejoe1 (4094@39c3) | Note that that is not even fully true, we have the most in absolute numbers, but in the precantage count we are not even that good. | 12:57:03 |