From: baalajimaestro <baalajimaestro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telegram-desktop: update to 4.6.1.
Date: Tue, 07 Feb 2023 07:38:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42126@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
There is a new pull request by baalajimaestro against master on the void-packages repository
https://github.com/baalajimaestro/void-packages update/tdesktop/4.6.1
https://github.com/void-linux/void-packages/pull/42126
telegram-desktop: update to 4.6.1.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, amd64, glibc
A patch file from https://github.com/void-linux/void-packages/pull/42126.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/tdesktop/4.6.1-42126.patch --]
[-- Type: text/x-diff, Size: 1242 bytes --]
From 27ce3199d3b56dc2761543f0e6e0d452bd0cb393 Mon Sep 17 00:00:00 2001
From: baalajimaestro <me@baalajimaestro.me>
Date: Sat, 4 Feb 2023 12:59:41 +0530
Subject: [PATCH] telegram-desktop: update to 4.6.1.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
---
srcpkgs/telegram-desktop/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/telegram-desktop/template b/srcpkgs/telegram-desktop/template
index 03bc7806f54f..ba0947762311 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.5.3
+version=4.6.1
revision=1
build_style=cmake
build_helper="qemu"
@@ -25,7 +25,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=3e338607708751813df36b677904e2e652f8adfac669da418c8dab4588a4f70f
+checksum=96fc517036bea908fb31b456aeb2950296e98965241bab318faa7641fb506f2f
build_options="spellcheck"
build_options_default="spellcheck"
next reply other threads:[~2023-02-07 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 6:38 baalajimaestro [this message]
2023-02-07 6:57 ` kruceter
2023-02-07 6:57 ` kruceter
2023-02-07 6:58 ` kruceter
2023-02-07 11:33 ` [PR PATCH] [Merged]: " Johnnynator
2023-02-08 2:23 ` baalajimaestro
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-42126@inbox.vuxu.org \
--to=baalajimaestro@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).