| 27 Nov 2025 |
 @eveeifyeve:matrix.org | I will have to backport manually the specific commit. | 02:11:22 |
| @eveeifyeve:matrix.org | Also please check this comment: https://github.com/NixOS/nixpkgs/issues/443568#issuecomment-3583858495 | 02:11:58 |
| @eveeifyeve:matrix.org | * Would I sitll be able to backport to 25.05 to remove nim1 because at this point it's EOL? | 02:12:41 |
| @eveeifyeve:matrix.org | * 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:matrix.org | * 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:matrix.org | 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:matrix.org | It's not maintained. | 13:34:16 |
| @eveeifyeve:matrix.org | * 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 |
