NixOS GNOME | 394 Members | |
| A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...) | 91 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Apr 2024 | ||
| uh, real-life events have kinda taken over suddenly the past couple of weeks. I can still look at it but please don't let that stop someone else jumping in first if they can. | 03:16:12 | |
| bobby285271: What's the current state of gnome-adjacent desktops? Are there any blockers there? | 11:22:51 | |
| Hey, I'm also affacted by https://github.com/NixOS/nixpkgs/pull/300933#issuecomment-2061380389 - do you think we should try to patch/backport on our own (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3475#note_2088824) or wait for gnome-v46? | 21:38:58 | |
| SebTM: I'd like to say we'll be merging next week, I just need to check with people what the right process is to make sure it doesn't cause mass disruption | 21:40:15 | |
| Fwiw the branch right now should be fully cached, so if you switch your system to using 46 you won't even be faced with major rebuilds | 21:40:46 | |
| Thanks will do that to test 🙂 | 21:41:12 | |
| Jan Tojnar: I guess related to that, I feel pretty satisfied with the current state of the branch, there's afaik no regressions, open questions/issues in the PR aren't IMO blockers, the jobset finished building just fine. What's next, requesting the jobset get enabled for all platforms, waiting for that to finish, and then hitting merge? Anything else to watch out for? | 21:49:47 | |
| And related related, Lily Foster would you mind if we still include the gst changes as part of the gnome PR, if it can be merged soon? Or would you rather I drop those commits? | 21:50:34 | |
In reply to @maxeaubrey:matrix.orgif it'll be merged soon, sure i suppose you can leave them there. i didn't get to opening gst PR friday, but i did get my laptop out a few minutes ago and am working on it right now | 21:51:48 | |
| (worst case i can still rebase my local changes on top of merged gnome PR, it's not much of a bother if that's preferable for y'all) | 21:52:21 | |
| Hmpf it seems I'm doing something wrong - do you just use the gnome-46 branch as nixpkgs-input or overlay only gnome.* in your nixpkgs from the branch? I tried the first as I'm currently not depend on any commits on top of unstable or sth but the rebuild cycle directly started for me. Sorry to bother you with this my first time in a that big nixpkgs project ✌🏻 | 21:59:52 | |
| I am running from the branch directly, a lot of the libraries aren't in the gnome namespace so overlaying would be a fair bit more complicated | 22:02:08 | |
In reply to @lily:lily.flowersMostly saves some rebuilds all around, but I'll leave the decision up to you | 22:03:46 | |
In reply to @maxeaubrey:matrix.orgis the gnome PR going to staging? | 22:04:49 | |
| if so, it won't be any more rebuilds if gst PR makes it into staging before next staging-next cycle | 22:05:07 | |
| I think it's more likely to go directly to master? Unless I'm told to do so otherwise | 22:05:29 | |
| even if it's a mass rebuild? 👀 | 22:06:06 | |
| oh well i guess gnome pr has hydra jobsets, so it's already built | 22:06:52 | |
| never mind | 22:06:56 | |
| it should be going to master, yeah | 22:07:01 | |
| (sorry, am rather tired right now... maybe i shouldn't be trying to test stuff and open a PR...) | 22:07:25 | |
| so yeah leave it in gnome PR and i'll just PR gst changes to staging after merge (and 6h periodic merge from master -> staging) | 22:08:48 | |
| Cool, and thanks for understanding | 22:09:10 | |
In reply to @maxeaubrey:matrix.orgyeah sorry, i took several weeks to get around to the gst stuff and didn't mean to step on any toes with the gnome stuff | 22:09:37 | |
| Likewise, I should have checked with you as the maintainer about it, or even opened it as a separate PR a few weeks ago when doing this work first. I think I've learned some rather useful lessons about how to make all of this way less painful in the future, if I ever do iy again | 22:17:10 | |
| * Likewise, I should have checked with you as the maintainer about it, or even opened it as a separate PR a few weeks ago when doing this work first. I think I've learned some rather useful lessons about how to make all of this way less painful in the future, if I ever do it again | 22:17:16 | |
In reply to @maxeaubrey:matrix.org(i mean i would expect ofborg to ping me on changes too, and you didn't really do anything wrong in this case, i do appreciate that you let me know when you noticed i was working on it <3) | 22:18:59 | |
| 23:27:38 | ||
| 22 Apr 2024 | ||
In reply to @maxeaubrey:matrix.org Hmm, somehow I'm doing something wrong 🥴 I changed my nixpkgs input to the gnome-46 branch and tested it with other inputs that usually follow nixpkgs to still follow or to follow the up2date unstable - both cases I get about 800 rebuilds (https://cryptpad.fr/pad/#/2/pad/edit/4HKcyfJOyUEbhFHG-v007u1g/) - this is my nix flake info: https://cryptpad.fr/pad/#/2/pad/edit/nwvRpENNeZgk135et1A6slLa/ (Would be awesome if we can figure out my issue if that's ok for you...) | 00:19:42 | |
In reply to @maxeaubrey:matrix.org* Hmm, somehow I'm doing something wrong 🥴 I changed my nixpkgs input to the gnome-46 branch and tested it with other inputs that usually follow nixpkgs to still follow or to follow the up2date unstable - both cases I get about 800 rebuilds (https://cryptpad.fr/pad/#/2/pad/edit/4HKcyfJOyUEbhFHG-v007u1g/) - this is my nix flake info: https://cryptpad.fr/pad/#/2/pad/edit/nwvRpENNeZgk135et1A6slLa/ (Would be awesome if we can figure out my issue here if that's ok for you...) | 00:23:12 | |