[Backport release-25.11] GNOME updates 2026-01-24

[axodentally]

Backport PR #483366.

Things done

Cherry-picked the commits.

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/gnome-release-strategy-for-nixos-stable/74887/2

Review dismissed automatically

[axodentally]

@jtojnar you reviewed the original PR. Can you maybe also review this one, so that it can be merged?

I am waiting for some important fixes from mutter 49.3

[Mershl]

#490335 may superseed this

[axodentally]

I fat-fingered that force push.
However, by trying to backport all the changes in the mentioned new PR, I came across a problem with libglycin.

Since the last commit on release-25.11, being the backport of version change from 2.0.5 -> 2.0.7, quite some things have changed on master (see here: https://github.com/NixOS/nixpkgs/commits/master/pkgs/by-name/li/libglycin/package.nix).

Now, how shall one handle such a case in a backport? I did not find any documentation on that. Especially trying to backport something like this PR (#481377) does not seem that right to me. Shall I then just change the hash and version value and leave everything as is on release-25.11?

Looking forward to some clues that can lead me in the right direction and help me understand and learn :)

Review dismissed automatically

[axodentally]

sorry for the spam, finally got around to fixing up the commits to how they should be.

So this is now ready for review, although afterwards the changes made in #490335 also need backporting and as said in my last comment: I do not know how to handle some of the commits in there.

In any case, this PR here can, in my view, be merged now.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/6476