From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libtd: update to 1.8.0.
Date: Mon, 10 Jan 2022 07:12:45 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34976@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages pkg/libtd
https://github.com/void-linux/void-packages/pull/34976
libtd: update to 1.8.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- ppc64le-musl
A patch file from https://github.com/void-linux/void-packages/pull/34976.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/libtd-34976.patch --]
[-- Type: text/x-diff, Size: 1543 bytes --]
From f27eba09b40dd502b066f342c8ff9759163b2a5f Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Mon, 10 Jan 2022 17:10:29 +1100
Subject: [PATCH] libtd: update to 1.8.0.
---
common/shlibs | 2 +-
srcpkgs/libtd/template | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/common/shlibs b/common/shlibs
index 999d3ad714b8..f5e92014becc 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3940,7 +3940,7 @@ libcglm.so.0 cglm-0.7.6_1
libfcft.so.3 fcft-2.2.2_1
libaml.so.0 aml-0.1.0_1
libneatvnc.so.0 neatvnc-0.3.2_1
-libtdjson.so.1.7.0 libtd-1.7.0_2
+libtdjson.so.1.8.0 libtd-1.8.0_1
libJudy.so.1 judy-1.0.5_1
libsignal-protocol-c.so.2 libsignal-protocol-c-2.3.3_2
libKSeExprUI.so.4 seexpr-krita-4.0.4.0_1
diff --git a/srcpkgs/libtd/template b/srcpkgs/libtd/template
index f719ab4d3f1e..fe42d43f904a 100644
--- a/srcpkgs/libtd/template
+++ b/srcpkgs/libtd/template
@@ -1,7 +1,7 @@
# Template file for 'libtd'
pkgname=libtd
-version=1.7.0
-revision=2
+version=1.8.0
+revision=1
wrksrc="td-${version}"
build_style=cmake
build_helper=qemu
@@ -12,7 +12,7 @@ maintainer="Ivan Sokolov <ivan-p-sokolov@ya.ru>"
license="BSL-1.0"
homepage="https://core.telegram.org/tdlib"
distfiles="https://github.com/tdlib/td/archive/v${version}.tar.gz"
-checksum=3daaf419f1738b7e0ac0e8a08f07e01a1faaf51175a59c0b113c15e30c69e173
+checksum=30d560205fe82fb811cd57a8fcbc7ac853a5b6195e9cb9e6ff142f5e2d8be217
if [ "$XBPS_TARGET_ENDIAN" = "be" ]; then
broken="Unsupported tl-schema version -1"
next reply other threads:[~2022-01-10 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 6:12 unspecd [this message]
2022-01-11 20:00 ` [PR PATCH] [Merged]: " ericonr
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-34976@inbox.vuxu.org \
--to=unspecd@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).