| 26 Nov 2025 |
 Mic92 | Jens Petersen: I would be interested, how it came about that Fedora now started packaging Nix, if you want to tell. | 13:32:05 |
| Mic92 | It seems like you put quite a bit of effort into it following the upstream nix history for it. | 13:32:34 |
 Jens Petersen | Mic92: hahaha - well other distros have nix packaged of course - so I think there was a sense we were missing it and also users seem to want to have it available... I had a user repo for a long time, but the /nix was kind of a blocker - but just recently we got an exception to allow use of /nix by nix in fedora.... Coincidently RPM (C version) just turned 30 years recently 😂 | 13:37:00 |
| Mic92 | Nix is also not much younger than that. | 13:37:34 |
| Jens Petersen | But I am not actually a heavy or experienced nix user - but somehow I stepped because I packaged in a user repo and that was quite popular | 13:37:39 |
| Jens Petersen | * But I am not actually a heavy or experienced nix user - but somehow I stepped up because I packaged in a user repo and that was quite popular | 13:37:49 |
| Jens Petersen | * But I am not actually a heavy or experienced nix user - but somehow I stepped up because I packaged it in a user repo and that was quite popular | 13:38:39 |
| Mic92 | Yeah that's always a bit of a challenge with packaging in other distros. Packagers are often not deeply invested, because otherwise they would likely run NixOS. | 13:39:00 |
| 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 |
