| 8 Jan 2025 |
 Salt | kay, will try to be a bit more patient before checking whether a specific extension is breaking | 22:25:15 |
 Alyssa Ross | (assuming backport to a release branch, not to staging) | 22:25:18 |
| Salt | yeah, it appears to be a release backport | 22:25:51 |
| Salt | * yeah, it appears to be a release backport, merged 2 days ago | 22:27:16 |
| Salt | I just saw this comment while trying to track down a different package's backport state and was wondering it is the general consensus?
I don't think any of the GNOME packagers use stable so you are on your own testing the changes :-)
| 23:45:29 |
| Salt | hmm, is there a good reference for how packages pass through nix generally so I can potentially avoid some of these questions?
For instance I notice that when updating extensions the bot automatically opened a backport PR, however there is a large set of updates that was merged a couple weeks ago that doesn't appear to have a PR. And I presume without the backports PR things will only be available in unstable until the next release. So what steps can be taken to open a backports PR if one wasn't automatically generated? | 23:51:12 |
| 9 Jan 2025 |
 ElvishJerricco | Is there a way to tell gnome to wake the screen from a udev rule? I've got a udev rule that does loginctl lock-sessions when I unplug my yubikey, but I also want it to wake the display when I plug it in. This particular machine would not be expected to be suspended. | 07:51:12 |
 uep | https://nixpk.gs/pr-tracker.html is very helpful for such cases | 21:31:02 |
| 10 Jan 2025 |
 Jan Tojnar | yes, that is correct. I try to add labels for auto-backports when it makes sense and when someone pings me, merge PRs to stable, but otherwise I avoid stable-related stuff | 00:38:31 |
| Jan Tojnar | I also usually ignore extension PRs for the same reason (testing them is time consuming) | 00:40:43 |
| Jan Tojnar | I would expect some D-Bus API to work. There is SimulateUserActivity on org.freedesktop.ScreenSaver but it appears g-s-d does not implement it | 00:47:36 |
| Jan Tojnar | maybe Inhibit would disable the screensaver even if already active? | 00:48:32 |
|  SigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11). | 22:15:45 |
| Salt | very cool, thanks | 22:36:10 |
| Salt | okay, well what would the best steps be for getting the changes made in this PR to be backported? | 22:38:13 |
| Salt | most importantly, Nautilus 74.1 fixes a fairly major bug that is triggered when resized using keys | 22:39:31 |
| Jan Tojnar | added a tag, let’s see if auto-backport works | 22:39:37 |
| Salt | * most importantly, Nautilus 47.1 fixes a fairly major bug that is triggered when resized using keys | 22:39:44 |
| Jan Tojnar | it did https://github.com/NixOS/nixpkgs/pull/372770, if someones test it, I can merge | 22:40:11 |
| SigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-11) to SigmaSquadron (Away until 2025-01-11). | 22:43:17 |
| 11 Jan 2025 |
| SigmaSquadron changed their display name from SigmaSquadron (Away until 2025-01-11) to SigmaSquadron. | 15:06:39 |
| 13 Jan 2025 |
 Jeff | What's the NixOS policy on updating GTK4 and libadwaita. Unstable is quite a bit behind the current stable releases. | 19:25:07 |
| Jeff | * What's the NixOS policy on updating GTK4 and libadwaita? Unstable is quite a bit behind the current stable releases. | 19:25:20 |
 K900 | GTK updates have to go through staging | 19:26:34 |
| K900 | I assume libadwaita too though I have not checkd | 19:26:40 |
| K900 | * I assume libadwaita too though I have not checked | 19:26:41 |
| K900 | But we have a GTK update in staging-next and it should be landing soon-ish | 19:26:51 |
| Jeff | ah ok, i'm finding the PRs now. my GH search-fu was failing me earlier | 19:30:48 |
| Jeff | Except that I'm not seeing any evidence that GTK4 or libadwaita are being updated. They are still at 4.16.3 and 1.6.2 in master and none of the recent "Gnome update" PRs touch them. | 19:44:06 |
| K900 | GTK4 is 4.16.7 on staging-next | 19:45:00 |
