| 5 Jan 2024 |
|  obsqrprjkt joined the room. | 14:08:10 |
| 11 Jan 2024 |
 Lily Foster | someone new to the community brought up being surprised by a new release (23.11) in #nix:nixos.org that they didn't know about since they don't check the website or discourse or anything regularly. how would we feel about adding to the release procedure pushing an eval warning of some flavor explaining that there is a new release and the EOL date of their current release to NixOS, maybe 2 weeks before the channels get turned off for a deprecated release? | 16:07:32 |
| Lily Foster | i can come up with technical details for it and make the PR to the release wiki if we're interested in something like that | 16:08:08 |
 Janne Heß | In reply to @lily:lily.flowers
someone new to the community brought up being surprised by a new release (23.11) in #nix:nixos.org that they didn't know about since they don't check the website or discourse or anything regularly. how would we feel about adding to the release procedure pushing an eval warning of some flavor explaining that there is a new release and the EOL date of their current release to NixOS, maybe 2 weeks before the channels get turned off for a deprecated release? systemd somewhat does that now. You need to explicitly continue booting it when the release is unsupported | 17:49:01 |
 raitobezarius | In reply to @lily:lily.flowers
someone new to the community brought up being surprised by a new release (23.11) in #nix:nixos.org that they didn't know about since they don't check the website or discourse or anything regularly. how would we feel about adding to the release procedure pushing an eval warning of some flavor explaining that there is a new release and the EOL date of their current release to NixOS, maybe 2 weeks before the channels get turned off for a deprecated release? Personally I would like to have a companion tray program for NixOS which informs you about various events of your system | 17:54:55 |
| raitobezarius | e.g. new release, EOL, security issues, etc. | 17:55:00 |
| raitobezarius | I don't see it specific to the release stuff but more like a event stream for anything relevant going on in nixpkgs | 17:55:15 |
| Lily Foster | In reply to @raitobezarius:matrix.org
I don't see it specific to the release stuff but more like a event stream for anything relevant going on in nixpkgs would you feel that should replace adding an eval warning when evaluating deprecated releases, or should we maybe look at eventually having both? | 17:57:12 |
| raitobezarius | For an eval warning, I would fear that people would find this a bit obnoxious but I may be wrong though we can of course provide toggles and what not | 17:57:18 |
| Lily Foster | also just curious, are you thinking something like gentoo enews? | 17:57:23 |
| raitobezarius | In reply to @lily:lily.flowers
would you feel that should replace adding an eval warning when evaluating deprecated releases, or should we maybe look at eventually having both? I think eval warning have the problem that you need to eval to find them | 17:57:32 |
| raitobezarius | In reply to @lily:lily.flowers
also just curious, are you thinking something like gentoo enews? Yeah, news items but maybe not by email | 17:57:46 |
 Vladimír Čunát | They're per-package I think. | 17:57:59 |
| raitobezarius | It's not mutually exclusive | 17:58:12 |
| raitobezarius | I think we have per-module, per-package, per-release, per-architecture news | 17:58:23 |
| Lily Foster | In reply to @raitobezarius:matrix.org
For an eval warning, I would fear that people would find this a bit obnoxious but I may be wrong though we can of course provide toggles and what not (i mean i think the point is to be obnoxious given they, uh, need to upgrade. i was more worried it would go unnoticed because many people's systems already generate eval warnings for various reasons) | 17:58:23 |
| raitobezarius | In reply to @lily:lily.flowers
(i mean i think the point is to be obnoxious given they, uh, need to upgrade. i was more worried it would go unnoticed because many people's systems already generate eval warnings for various reasons) Yeah my experience seems to indicate that people are already around some maximum of evaluation warnings and I don't think an extra one will encourage to upgrade because upgrade is more than often a process that requires fixing stuff in your configuration and usually people complain they cannot silence warnings | 17:59:08 |
| raitobezarius | It's hard to navigate in the space of evaluation warnings properly IMHO | 17:59:33 |
| 14 Jan 2024 |
 lennart | hej, I guess I still have the permission to merge in nixpkgs since being Release Editor before. could someone free me of this burden of responsibility? pinging raitobezarius and figsoda | 22:42:57 |
| raitobezarius | done | 22:43:52 |
| lennart | merci beaucoup | 22:43:57 |
| 15 Jan 2024 |
|  tgerbet set a profile picture. | 22:26:18 |
| 18 Jan 2024 |
| Vladimír Čunát | I wonder about this kind of stable backports that look rather large to me:
https://github.com/NixOS/nixpkgs/pull/273040/files | 10:39:03 |
| raitobezarius | I asked a similar question on a similar PR | 11:19:09 |
| raitobezarius | I don't think I got a clear cut answer | 11:19:13 |
| 26 Jan 2024 |
|  trofi joined the room. | 21:32:44 |
| 27 Jan 2024 |
|  @lehmanator:gnulinux.club removed their profile picture. | 16:55:10 |
| @lehmanator:gnulinux.club removed their display name Sam Lehman. | 17:00:26 |
| @lehmanator:gnulinux.club left the room. | 17:04:04 |
| 28 Jan 2024 |
|  @ncfavier:matrix.org changed their profile picture. | 14:04:05 |
