| 26 Nov 2025 |
 Mic92 | * Yeah that's always a bit of a challenge with packaging in other distros. Packagers are often not deeply in the Nix ecosystem, because otherwise they would likely run NixOS. | 13:39:16 |
 Jens Petersen | I hope it settles down because it has been plenty of work both upstream and downstream | 13:39:18 |
| Jens Petersen | Indeed | 13:39:33 |
| Jens Petersen | At least I think we have better manpages than upstream now haha | 13:40:11 |
| Mic92 | I can potentially also include in security announcements in the future. What is the normal fedora workflow for this? | 13:40:14 |
| Mic92 | * I can potentially also include you in security announcements in the future. What is the normal fedora workflow for this? | 13:41:18 |
| Jens Petersen | Good question - we kind of have our own security (Red Hat) but it is more focused on RHEL packages of course | 13:41:19 |
| Jens Petersen | * Good question - we kind of have our own security team (Red Hat) but it is more focused on RHEL packages of course | 13:41:30 |
| Jens Petersen | Mic92: but yeah heads-up would be appreciated sure | 13:42:21 |
| Mic92 | Do you have access to infra where you can prepare builds/patches in private in Fedora/ | 13:43:10 |
| Jens Petersen | Mic92: I need to check but not that I am aware of for fedora - I guess we would just hold back up until embargo is lifted | 13:44:33 |
| Mic92 | Okay, with nixos we are in a similar situation. | 13:45:00 |
| Jens Petersen | Okay right | 13:45:13 |
| Mic92 | what we did so far is using a seperate nix org that we invited people into | 13:45:14 |
| Jens Petersen | Ah I see | 13:45:23 |
| Jens Petersen | But we do have private bugs in bugzilla that the security team uses for example | 13:46:50 |
| Jens Petersen | * But we do have private tracking bugs in bugzilla that the security team uses for example - that can only be seen by the package maintainer | 13:47:27 |
| Jens Petersen | Also right now I am blocked on 2.32 because we have an older boost library version still :-/
The maintainer is being jolly slow | 13:48:46 |
| Jens Petersen | * Also right now I am blocked on 2.32 because we have an older boost library version still :-/
The maintainer is being jolly slow - anyway I guess it is not stable yet anyway | 13:51:18 |
| Mic92 | How long is the maintenance cycle for fedora? | 13:55:13 |
| Jens Petersen | 6 months - but I already built nix for current releases too | 13:55:40 |
| Jens Petersen | So similar to nixos actually - maybe just a few weeks earlier | 13:56:30 |
| Jens Petersen | * So similar to nixos actually - maybe just a month earlier | 13:56:56 |
| Jens Petersen | * So similar to nixos actually - maybe just a month earlier: we released F43 at the end of Oct (with gnome 49 etc) | 13:57:20 |
| Jens Petersen | Also extra difficulty is I am trying to support both nix-daemon and without also | 13:58:30 |
| Jens Petersen | * 6 months - but I already built nix for current releases too: should go into the testing repo maybe tomorrow | 13:59:07 |
| Mic92 | 6 months would align well with NixOS. | 14:04:42 |
| Jens Petersen | Right - assuming we can keep up with the deps 😅👅 | 14:10:32 |
| Jens Petersen | * Right - assuming we can keep up with the deps 😅😛 | 14:10:42 |
| Mic92 | Actually we are often quiet behind with the deps because we build nix with the current nixos stable release :) | 14:11:45 |
