| 2 Nov 2025 |
 emily | (as in "allowed") | 09:53:07 |
 aloisw | I don't remember the details, but basically I think the contract allows KDE to fork Qt under a permissive license if they fail to release any Qt version as open source with at most 1 year delay. | 09:54:50 |
| emily | right | 09:56:21 |
| emily | I just wasn't sure what was binding them there | 09:56:28 |
| emily | https://kde.org/community/whatiskde/kdefreeqtfoundation/ I knew about this but didn't recall the exact details of the contract. | 09:56:47 |
| emily | haha, Qt are contractually prohibited from dropping X11 support | 09:57:12 |
| emily | I guess they're going to have to amend that at some point?? | 09:57:20 |
| aloisw |
The Foundation has the right to update to supported successor platforms (e.g. from X11 to Wayland) without additional negotiations with Qt Group.
| 09:57:37 |
| emily | whoops | 09:57:49 |
| emily | I didn't get enough sleep | 09:57:52 |
| aloisw | (from that overview page, one would have to read the contract to figure out whether that means they are not allowed to drop either X11 or Wayland in this case or if it only affects Wayland) | 09:59:14 |
 K900 | https://github.com/NixOS/nixpkgs/pull/457760 | 10:10:50 |
 leona | fyi We thought a bit about the release schedule and adapted it to reality, it will probably be something like that. I propose that we'll see how the staging-next cycle that starts in the next 2 days looks like and then decide if a second one still fits | 17:28:29 |
| leona | 
Download image.png | 17:28:32 |
| leona | i think a second cycle will be quite tight, we could decide tho to branch-off a few days (like 2-3) earlier and then already start a staging-next-25.11 cycle | 17:29:41 |
 Vladimír Čunát | I'll start staging-next within a few hours maybe. | 17:31:27 |
| Vladimír Čunát | I wonder if it's worth considering to start "encouraging ZHF fixes" against the staging-next branch in a few days already, before it gets to master. | 17:41:20 |
| Vladimír Čunát | (I don't recall if the workflow instructions would have to get adapted significantly.) | 17:41:57 |
| Vladimír Čunát | There's not too much time before the end of the month. | 17:42:21 |
| Vladimír Čunát | Though two full staging-next cycles might realistically fit. | 17:42:49 |
| Vladimír Čunát | (if we don't get stuck on something) | 17:43:02 |
| Vladimír Čunát | * Though two full staging-next cycles might realistically fit under 4 weeks. | 17:43:23 |
|  @dawnofmidnight:catgirl.cloud changed their display name from whispers to whispers (it/fae). | 17:58:06 |
| Vladimír Čunát | Oh, I didn't realize that ZHF was already announced several minutes before that comment 🤦 | 19:10:30 |
| Vladimír Čunát | Also note that the planned GNOME upgrade is not in the just-starting staging-next. And it's a huge rebuild.
https://github.com/NixOS/nixpkgs/pull/440720#issuecomment-3478235753 | 20:07:54 |
| leona | ack | 20:08:21 |
| Vladimír Čunát | New staging-next:
https://github.com/NixOS/nixpkgs/pull/457894 | 20:08:27 |
 Grimmauld (any/all) | wait is that the one with the glib upgrade? That'll be fun | 20:13:14 |
| Grimmauld (any/all) | also eval error because gradle? Thats not good... | 20:16:03 |
 @wolfgangwalther:matrix.org | I'm currently looking at that Eval error. Seems to be because wrapGradle forces evaluation of more than it should, so accessing meta is not possible without triggering the insecure error immediately. | 20:23:38 |
