telegram-desktop: 5.14.3 -> 5.15.2

[dtomvan]

• telegram-desktop.tg_owt: 0-unstable-2024-10-28 -> 0-unstable-2025-06-02
• telegram-desktop: 5.14.3 -> 5.15.0

tg_owt revision is the one upstream uses in their docker build environment as of now.

Release: https://github.com/telegramdesktop/tdesktop/releases/tag/v5.15.0
Diff: telegramdesktop/tdesktop@v5.14.3...v5.15.0

No tdlib update, so I assume I don't need to update the forks at the same time?

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[dtomvan]

For good measure I rebuilt materialgram on this branch, which worked.

[ilya-fedin]

Change that "broke" the build (hence new deps): telegramdesktop/tdesktop#29371

It's not even merged

[dtomvan]

Oh, sorry for my ignorance. Wasn't really paying attention... I assumed that was the change that did it as it referenced a lot of the same libraries I needed to add. Then I don't know what is the breaking change, but it isn't really that important anyways. I know that it doesn't build without adding them, and that I got a working build this way.

[NickCao]

LGTM, do we want to create a symlink telegram-desktop -> Telegram for compatibility?

[dtomvan]

Don't know, most people launch it from the desktop files anyways, which have been updated upstream. I think the installPhase (which references mainProgram, which might be a bad thing) should also work on MacOS since they also did the rename for that platform upstream.

[ilya-fedin]

since they also did the rename for that platform

Other platforms didn't change binary name. telegram-desktop was linux-with-non-hardcoded-path-mode-specific.

which references mainProgram, which might be a bad thing

This feels natural, that way you don't have to change multiple places