From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-telegram: update to 0.15.0
Date: Sun, 01 May 2022 10:44:54 +0200 [thread overview]
Message-ID: <20220501084454.0yL--eacLE7-XJFeIAb1bADCFZoNriZYzm6W5OyAI8E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36826@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
There is an updated pull request by paper42 against master on the void-packages repository
https://github.com/tuxliban/void-packages python3-telegram
https://github.com/void-linux/void-packages/pull/36826
python3-telegram: update to 0.15.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (musl)
- I built this PR locally for architecture:
- x86_64
A patch file from https://github.com/void-linux/void-packages/pull/36826.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-telegram-36826.patch --]
[-- Type: text/x-diff, Size: 1536 bytes --]
From 8618cd3b4ceb7689dd0a6624afcb61ef2d94cd76 Mon Sep 17 00:00:00 2001
From: Tuxliban Torvalds <tenshalito@gmail.com>
Date: Sat, 23 Apr 2022 03:02:01 -0500
Subject: [PATCH] python3-telegram: update to 0.15.0
---
srcpkgs/python3-telegram/template | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-telegram/template b/srcpkgs/python3-telegram/template
index b9eebe0fde9a..13b971bbd6b9 100644
--- a/srcpkgs/python3-telegram/template
+++ b/srcpkgs/python3-telegram/template
@@ -1,20 +1,23 @@
# Template file for 'python3-telegram'
pkgname=python3-telegram
-version=0.14.0
-revision=3
+version=0.15.0
+revision=1
wrksrc=python-telegram-${version}
build_style=python3-module
-hostmakedepends="python3"
+hostmakedepends="python3-setuptools"
depends="libtd python3-setuptools"
+checkdepends="python3-pytest $depends"
short_desc="Python library for building Telegram clients"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://github.com/alexander-akhmetov/python-telegram"
distfiles="https://github.com/alexander-akhmetov/python-telegram/archive/${version}.tar.gz"
-checksum=11b0a2387bae642eb7f134fe35b9ef67b8183aa961412bcdfa86ff404beed897
+checksum=eaa9c883e9a6415590eaada88b39817247361ee2ba959526081a14f3e66ecc0b
post_extract() {
- rm -r telegram/lib
+ # mocked_resource.assert_called_once_with('telegram', 'lib/linux/libtdjson.so')
+ # AssertionError: Expected 'mock' to be called once. Called 0 times.
+ rm tests/test_tdjson.py
}
post_install() {
next prev parent reply other threads:[~2022-05-01 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 8:06 [PR PATCH] " tuxliban
2022-05-01 8:27 ` [PR PATCH] [Updated] " paper42
2022-05-01 8:44 ` paper42 [this message]
2022-05-01 8:45 ` paper42
2022-05-01 8:48 ` [PR PATCH] [Merged]: " paper42
2022-05-02 6:02 ` tuxliban
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=20220501084454.0yL--eacLE7-XJFeIAb1bADCFZoNriZYzm6W5OyAI8E@z \
--to=paper42@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).