From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34139-done@debbugs.gnu.org
Subject: [bug#34139] Update electrum, add python-aiohttp-socks and python-aiorpcx
Date: Sat, 09 Feb 2019 21:43:31 -0800 [thread overview]
Message-ID: <878syourjw.fsf@ponder> (raw)
In-Reply-To: <87lg2opp84.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On 2019-02-09, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>> Subject: [PATCH 1/3] gnu: Add python-aiohttp-socks.
>> Subject: [PATCH 2/3] gnu: Add python-aiorpcx.
>> Subject: [PATCH 3/3] gnu: electrum: Update to 3.3.3.
...
> I finally applied all three patches with minor tweaks to the
> descriptions; I also added a copyright line for you in python-web.scm.
> Sorry for the delay!
Thanks!
> Unfortunately qtwebkit, a dependency of Electrum, currently fails to
> build on ‘master’:
...
> See
> <https://ci.guix.info/log/901miwpk9srhwq3646v6bm7zni3qda8m-qtwebkit-5.212.0-alpha2>.
FWIW, I was eventually able to build qtwebkit locally after freeing up
some disk space; it takes at *least* 12GB free to build, in my
experience... saw the build go as high as ~11.5GB at one point, don't
know how much it eventually needed.
So I've managed to install the new version of electrum without local
patches!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-10 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 23:49 [bug#34139] Update electrum, add python-aiohttp-socks and python-aiorpcx Vagrant Cascadian
2019-01-25 21:20 ` Ludovic Courtès
2019-01-31 22:35 ` Vagrant Cascadian
2019-02-09 22:32 ` bug#34139: " Ludovic Courtès
2019-02-10 5:43 ` Vagrant Cascadian [this message]
2019-02-11 16:28 ` [bug#34139] " Ludovic Courtès
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=878syourjw.fsf@ponder \
--to=vagrant@debian.org \
--cc=34139-done@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.