From: LucasTavaresA <LucasTavaresA@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tremc: update to 0.9.3
Date: Thu, 12 Jan 2023 14:44:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41595@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
There is a new pull request by LucasTavaresA against master on the void-packages repository
https://github.com/LucasTavaresA/void-packages tremc
https://github.com/void-linux/void-packages/pull/41595
tremc: update to 0.9.3
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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 glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl **cross**
- armv6l-musl **cross**
A patch file from https://github.com/void-linux/void-packages/pull/41595.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tremc-41595.patch --]
[-- Type: text/x-diff, Size: 2052 bytes --]
From 0739a2f9ae6526001805001d257ac1c6036c846a Mon Sep 17 00:00:00 2001
From: LucasTavaresA <tavares.lassuncao@gmail.com>
Date: Thu, 12 Jan 2023 10:44:24 -0300
Subject: [PATCH] tremc: update to 0.9.3
---
srcpkgs/tremc/patches/fix-python3.9.patch | 12 ------------
srcpkgs/tremc/template | 6 +++---
2 files changed, 3 insertions(+), 15 deletions(-)
delete mode 100644 srcpkgs/tremc/patches/fix-python3.9.patch
diff --git a/srcpkgs/tremc/patches/fix-python3.9.patch b/srcpkgs/tremc/patches/fix-python3.9.patch
deleted file mode 100644
index 114db8acad98..000000000000
--- a/srcpkgs/tremc/patches/fix-python3.9.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-# upstream: yes
---- a/tremc
-+++ b/tremc
-@@ -438,7 +438,7 @@ class Transmission(object):
- # TAG_TORRENT_DETAILS, but just passing seems to help.(?)
- try:
- torrent_details = response['arguments']['torrents'][0]
-- torrent_details['pieces'] = base64.decodestring(bytes(torrent_details['pieces'], ENCODING))
-+ torrent_details['pieces'] = base64.decodebytes(bytes(torrent_details['pieces'], ENCODING))
- self.torrent_details_cache = torrent_details
- self.upgrade_peerlist()
- except IndexError:
diff --git a/srcpkgs/tremc/template b/srcpkgs/tremc/template
index 227ca61dc2c5..a5ced7e953e1 100644
--- a/srcpkgs/tremc/template
+++ b/srcpkgs/tremc/template
@@ -1,7 +1,7 @@
# Template file for 'tremc'
pkgname=tremc
-version=0.9.2
-revision=2
+version=0.9.3
+revision=1
build_style=gnu-makefile
depends="python3"
short_desc="Console client for the BitTorrent client Transmission"
@@ -9,4 +9,4 @@ maintainer="Nathan D <dhanas.nathan@gmail.com>"
license="GPL-3.0-only"
homepage="https://github.com/tremc/tremc"
distfiles="https://github.com/tremc/tremc/archive/${version}.tar.gz"
-checksum=ea31ff593c64bbf2c471f6c45ef09129e1e9cb55e8f8bd90e2916976a7053c61
+checksum=9629d1fe3a5a0747563acb15ca904b36ce2984977667d7de25f7786e1189051f
next reply other threads:[~2023-01-12 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 13:44 LucasTavaresA [this message]
2023-01-13 16:50 ` [PR PATCH] [Merged]: " classabbyamp
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-41595@inbox.vuxu.org \
--to=lucastavaresa@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).