From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: libtorrent-rasterbar: update to 2.0.6.
Date: Thu, 13 Oct 2022 04:15:21 +0200 [thread overview]
Message-ID: <20221013021521.BlQnhSrkLP-FxNG8Icb1ybLT9vIdX4s-Kz7ZBzn-_s4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36926@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
There's a closed pull request on the void-packages repository
libtorrent-rasterbar: update to 2.0.6.
https://github.com/void-linux/void-packages/pull/36926
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture (x86_64-glibc)
I have mainly tested qbittorrent and is working as expected so far.
The patch that I have created for libtorrent-rasterbar is essentially
a revert of upstream commit https://github.com/arvidn/libtorrent/commit/55bbcdc4321dbcd899f783763d9390ecc3a09850.
Without this revert the generated pkg-config file has a bogus
`-l-pthread` flag that then makes linking against libtorrent-rasterbar fail.
Please test :)
Edit: Deluge 2.0.5 seems stable with libtorrent-rasterbar 2.x, but some
tests are failing. For now I've disabled them.
https://git.alpinelinux.org/aports/tree/community/deluge/APKBUILD
https://github.com/deluge-torrent/deluge/pull/312 (this seems in some way related)
prev parent reply other threads:[~2022-10-13 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 17:29 [PR PATCH] " ologantr
2022-04-30 19:55 ` [PR PATCH] [Updated] " ologantr
2022-06-01 15:20 ` ologantr
2022-06-01 20:53 ` ologantr
2022-09-29 2:14 ` github-actions
2022-10-13 2:15 ` github-actions [this message]
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=20221013021521.BlQnhSrkLP-FxNG8Icb1ybLT9vIdX4s-Kz7ZBzn-_s4@z \
--to=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).