| 2 Mar 2026 |
|  boa_86 joined the room. | 20:38:20 |
| 3 Mar 2026 |
|  whispers [& it/fae] joined the room. | 19:20:08 |
| 8 Mar 2026 |
|  winston joined the room. | 01:44:23 |
|  @ayatsfer:matrix.org removed their profile picture. | 09:02:46 |
| @ayatsfer:matrix.org removed their display name Fernando. | 09:02:53 |
| @ayatsfer:matrix.org left the room. | 09:02:54 |
 Capypara | Hi! I develop an app for the GNOME Platform. Since NixOS gets GNOME updates very late, I've been wondering if there are any other app devs using NixOS around here. How do you work with new GTK and Adwaita releases before they land in nixpkgs? | 11:04:15 |
| Capypara | last time (with 49) I switched to Fedora for this, but I'd like to avoid using a VM or dual booting | 11:05:50 |
| Capypara | is there like a Flake for something? Or a guide on how to update GNOME in nixpkgs? I wouldn't mind just helping with the update, but last time I tried and couldn't figure out how. | 11:06:32 |
 Ainz Ooal Gown | You can point your nixpkgs input to gnome development branch | 11:08:05 |
| Ainz Ooal Gown | The people who handle the update work on it for a while and then is merged to nixpkgs master | 11:08:34 |
| Capypara | Ohhh okay I didn't realize that was a thing. Sorry then! | 11:38:25 |
| Capypara | It's also not a gigantic issue since GNOME app development happens via Flatpaks, but there's always some things you can't quite test the interactions of in pure sandbox environments | 11:39:49 |
| Capypara | * It's also not a gigantic issue since GNOME app development happens primarily via Flatpaks, but there's always some things you can't quite test the interactions of in pure sandbox environments | 11:40:03 |
| Capypara | (plus it's all a bit buggy and slow) | 11:40:15 |
| 10 Mar 2026 |
|  amadaluzia -> 4d2.org joined the room. | 01:45:58 |
| 14 Mar 2026 |
| amadaluzia -> 4d2.org changed their display name from amadaluzia to amadaluzia[uorg]. | 18:50:24 |
|  amadaluzia joined the room. | 19:29:26 |
| amadaluzia -> 4d2.org changed their display name from amadaluzia[uorg] to amadaluzia -> 4d2.org. | 21:22:04 |
| 15 Mar 2026 |
 hustlerone | i kinda don't cuz gtk4 abstracts it all away doesn't it? | 16:25:21 |
| hustlerone | oh i thought this was a gnome channel not a nixos channel my bad | 16:25:41 |
| 18 Mar 2026 |
 enzu.ru | are there a set of steps for porting GNOME 50 to NixOS that people can see and help out with? | 17:47:34 |
| enzu.ru | * | 20:50:51 |
| 19 Mar 2026 |
|  kirillrdy joined the room. | 09:07:16 |
|  niklaskorz joined the room. | 09:17:26 |
| niklaskorz | repeating my question from #staging:nixos.org here:
Is anyone from the Gnome team already working on a Gnome 50 PR? There doesn't seem to be one yet, but I'd rather double check before giving it a try myself
| 09:17:58 |
| niklaskorz | And if that is not the case and you are possibly willing to let me have a try at it, is the workflow described in nonemast still up to date?
Nixpkgs GNOME maintainers have the following workflow: When an alpha of a new GNOME release is published, they use update.nix script to automatically bump all GNOME packages in Nixpkgs on the gnome branch. After that, they walk through the commits, reading the release notes and modifying the package expressions as necessary. To have clean Git history where each commit points to a non-broken tree, maintainers push fixup/squash commits. Those are then periodically integrated by rebasing with auto-squashing.
| 09:37:01 |
 Alyssa Ross | I couldn't even find the gnome branch earlier | 09:46:02 |
|  Miles Dyson set a profile picture. | 18:06:08 |
|  @freedbeats:the-lamp.net left the room. | 20:50:08 |
