From: timas130 <timas130@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telegram-desktop: update to 4.4.1.
Date: Tue, 13 Dec 2022 17:43:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41063@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
There is a new pull request by timas130 against master on the void-packages repository
https://github.com/timas130/void-packages timas130/telegram-desktop-4.4.1
https://github.com/void-linux/void-packages/pull/41063
telegram-desktop: update to 4.4.1.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/41063.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-timas130/telegram-desktop-4.4.1-41063.patch --]
[-- Type: text/x-diff, Size: 1808 bytes --]
From 7018465757f064159af7ee3bfe8ed8c9ed98d671 Mon Sep 17 00:00:00 2001
From: sitting33 <me@sit.sh>
Date: Tue, 13 Dec 2022 19:39:54 +0300
Subject: [PATCH] telegram-desktop: update to 4.4.1.
---
srcpkgs/telegram-desktop/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/telegram-desktop/template b/srcpkgs/telegram-desktop/template
index 42a0ac05a1c9..74ae00e136d4 100644
--- a/srcpkgs/telegram-desktop/template
+++ b/srcpkgs/telegram-desktop/template
@@ -1,6 +1,6 @@
# Template file for 'telegram-desktop'
pkgname=telegram-desktop
-version=4.3.1
+version=4.4.1
revision=1
build_style=cmake
build_helper="qemu"
@@ -18,7 +18,7 @@ makedepends="alsa-lib-devel ffmpeg-devel libdbusmenu-glib-devel libopenal-devel
qt6-svg-devel libva-devel rapidjson liblz4-devel liblzma-devel gtk+3-devel
MesaLib-devel qt6-wayland-devel qt6-qt5compat-devel libatomic-devel
xcb-util-keysyms-devel $(vopt_if spellcheck hunspell-devel)
- glibmm2.68-devel tg_owt webkit2gtk-devel rnnoise-devel jemalloc-devel qt6-declarative-devel"
+ glibmm2.68-devel tg_owt webkit2gtk-devel rnnoise-devel jemalloc-devel qt6-declarative-devel protobuf"
depends="qt6-imageformats ttf-opensans"
short_desc="Telegram Desktop messaging app"
maintainer="John <me@johnnynator.dev>"
@@ -26,7 +26,7 @@ license="GPL-3.0-or-later, OpenSSL"
homepage="https://desktop.telegram.org/"
changelog="https://github.com/telegramdesktop/tdesktop/blob/v${version}/changelog.txt"
distfiles="https://github.com/telegramdesktop/tdesktop/releases/download/v${version}/tdesktop-${version}-full.tar.gz"
-checksum=3c1d8c09b72db5c9f5e2d3b467b451a6ba94c3ba8295b9880842a4e3496153dd
+checksum=76981e32541c42b3212427e9abb4db2a6f55a14eaba31b3d7ad7d3d5ed8008b1
build_options="spellcheck"
build_options_default="spellcheck"
next reply other threads:[~2022-12-13 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 16:43 timas130 [this message]
2022-12-14 12:46 ` [PR PATCH] [Updated] " timas130
2022-12-18 11:34 ` classabbyamp
2022-12-18 11:34 ` classabbyamp
2022-12-18 12:39 ` [PR PATCH] [Updated] " timas130
2022-12-18 12:40 ` timas130
2022-12-18 12:45 ` [PR PATCH] [Updated] " timas130
2022-12-18 12:46 ` timas130
2022-12-18 14:17 ` timas130
2023-01-06 14:52 ` [PR PATCH] [Closed]: " Johnnynator
2023-01-06 14:52 ` Johnnynator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41063@inbox.vuxu.org \
--to=timas130@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).