From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: deluge: update to 2.0.3
Date: Sun, 30 Jun 2019 19:31:58 +0200 [thread overview]
Message-ID: <20190630173158.TTAZDOLC6bdxNix_Wps_AzrdFaj353izSyo2hZs2Zu0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12734@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/12734#issuecomment-507053404
Comment:
The `m` is missing here:
```
export PYTHON_LDFLAGS="-L${XBPS_CROSS_BASE}/usr/lib -lpython3.6m"
^
```
Oh and `libtorrent-rasterbar-python` should be renamed to `libtorrent-rasterbar-python3` to follow Void's python naming convention.
This package rename should be safe as only deluge is depending on it:
```
$ xbps-query -RX libtorrent-rasterbar-python
deluge-1.3.15_4
```
Just to make sure this doesn't break anything.
next prev parent reply other threads:[~2019-06-30 17:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 13:49 [PR PATCH] " voidlinux-github
2019-06-29 21:04 ` voidlinux-github
2019-06-29 21:22 ` voidlinux-github
2019-06-29 21:22 ` voidlinux-github
2019-06-29 21:42 ` voidlinux-github
2019-06-29 21:46 ` voidlinux-github
2019-06-30 16:43 ` voidlinux-github
2019-06-30 17:31 ` voidlinux-github [this message]
2019-06-30 17:37 ` voidlinux-github
2019-07-02 12:35 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-02 12:35 ` voidlinux-github
2019-07-02 12:38 ` voidlinux-github
2019-07-03 20:18 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-03 20:18 ` voidlinux-github
2019-07-04 15:42 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190630173158.TTAZDOLC6bdxNix_Wps_AzrdFaj353izSyo2hZs2Zu0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).