From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT Date: Fri, 17 Feb 2017 16:41:31 +0000 Message-ID: <20170217164131.qqcv5mzvmihg6agi@wasp> References: <20170216163803.GA12299@mutt.economicsofbitcoin.com> <20170217110502.GC8688@mutt.economicsofbitcoin.com> <20170217162534.GD8688@mutt.economicsofbitcoin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57484) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1celZM-0006Pn-FE for guix-devel@gnu.org; Fri, 17 Feb 2017 11:39:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1celZJ-0004oZ-Cv for guix-devel@gnu.org; Fri, 17 Feb 2017 11:39:40 -0500 Received: from latitanza.investici.org ([2001:888:2000:56::19]:46546) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1celZJ-0004lx-3D for guix-devel@gnu.org; Fri, 17 Feb 2017 11:39:37 -0500 Content-Disposition: inline In-Reply-To: <20170217162534.GD8688@mutt.economicsofbitcoin.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Peter =?utf-8?B?xaB1cmRh?= Cc: guix-devel@gnu.org, chicks@getbackinthe.kitchen I don't really feel part of this conversation, but since you keep CC'ing me I have to reply. On 17-02-17 17:25:34, Peter =C5=A0urda wrote: > (crossposting to the mailing list and participants) >=20 > I managed to get Guix running in a VM and updated the instructions > on the bitmessage wiki for Guix: > https://bitmessage.org/wiki/Compiling_instructions#Resolve_dependencies This is not accesible from behind restrictive proxies and networks like tor, so I have to pass on this. =20 I did the initial packaging of PyBitmessage on GuixSD but there is no maintainer per package, whoever wants to update can update it. Since all my questions, improvements, and attempts to contribute have been blocked and/or forgotten by the PyBitmessage project I don't want to have this discussion in my inbox longer than necessary. LibreSSL support is at least one improvement I welcome. Any news on the use of setuptools, and the move to PyQt5? > (last row in the table). Based on this, whoever maintains the package > should be able to update it. >=20 > I haven't actually tested OpenCL because building pyopencl requires > opencl libraries and I have no idea how to install them on Guix. I don'= t > even think that open source drivers are compatible with the current CL > kernel, I was only ever able to get it running on closed source drivers > (AMD/Nvidia/Intel). >=20 > PyBitmessage is now compatible with both openssl 1.0.x and 1.1.x > (actually it should work back until 0.9.8b but I haven't tested it), an= d > in the next days I'll merge LibreSSL support so if you have to choose a > particular version or something, it doesn't matter, it will work with > whatever is installed. >=20 > On Fri, Feb 17, 2017 at 12:05:02PM +0100, Peter =C5=A0urda wrote: > > On Wed, 15 Feb 2017 19:33:05, ng0 wrote: > > > PyBitmessage doesn't build from git commits here. I nfact, there wa= sn't > > > much public activity in upstream in the last months since the last > > > release. We use the tarballs. >=20 > --=20 > Peter =C5=A0urda > Bitmessage core developer --=20 ng0 -- https://www.inventati.org/patternsinthechaos/