From: alihardan <alihardan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telegram-desktop: update to 3.0.1.
Date: Sat, 04 Sep 2021 09:08:33 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32828@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
There is a new pull request by alihardan against master on the void-packages repository
https://github.com/alihardan/void-packages patch-1
https://github.com/void-linux/void-packages/pull/32828
telegram-desktop: update to 3.0.1.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/32828.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-32828.patch --]
[-- Type: text/x-diff, Size: 678 bytes --]
From a6531e0e56cc8e54c83d66e357d00cbbcd83efa7 Mon Sep 17 00:00:00 2001
From: Ali Hardan <ali.hardan76@gmail.com>
Date: Sat, 4 Sep 2021 11:38:16 +0430
Subject: [PATCH] telegram-desktop: update to 3.0.1.
---
srcpkgs/telegram-desktop/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/telegram-desktop/template b/srcpkgs/telegram-desktop/template
index 57bee005ddd2..d4718c5c6339 100644
--- a/srcpkgs/telegram-desktop/template
+++ b/srcpkgs/telegram-desktop/template
@@ -1,6 +1,6 @@
# Template file for 'telegram-desktop'
pkgname=telegram-desktop
-version=2.9.3
+version=3.0.1
revision=1
wrksrc="tdesktop-${version}-full"
build_style=cmake
next reply other threads:[~2021-09-04 7:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 7:08 alihardan [this message]
2021-09-04 7:13 ` alihardan
2021-09-04 7:33 ` [PR PATCH] [Updated] " alihardan
2021-09-04 9:18 ` paper42
2021-09-04 12:04 ` [PR PATCH] [Updated] " alihardan
2021-09-04 12:16 ` alihardan
2021-09-04 15:54 ` alihardan
2021-09-04 16:03 ` paper42
2021-09-04 16:05 ` paper42
2021-09-04 16:20 ` alihardan
2021-09-04 17:58 ` [PR PATCH] [Updated] " alihardan
2021-09-05 12:39 ` [PR PATCH] [Merged]: " 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-32828@inbox.vuxu.org \
--to=alihardan@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).