Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On 17-02-15 19:01:14, Nancy-Anne Cianci wrote: > > At one point, bitmessage did not build in GuixSD - maybe it is fixed > already (I unplugged my guix drive). > > If indeed Bitmessage does build from latest Github commit, all is fine. > > > thanks. It always worked for me, otherwise I wouldn't have packaged and it wouldn't have made it into the tree. If there is / was a bug I suggest opening a bug. I don't monitor all my submissions on hydra all the time. PyBitmessage doesn't build from git commits here. I nfact, there wasn't much public activity in upstream in the last months since the last release. We use the tarballs. > > On 15.02.2017 14:02, ng0 wrote: > > On 17-02-15 12:52:30, Nancy-Anne Cianci wrote: > >> On 23.08.2016 14:03, ng0 wrote: > >>> These 3 patches enable us to have a functional pybitmessage version > >>> 0.6.1, released 2 days ago. > >> I believe some updating had to be done for "msgpack". > >> > >> > >> > > This message is so old I don't even know what you try to answer or ask. > > Can you be more specific? > -- ng0 -- https://www.inventati.org/patternsinthechaos/
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On 17-02-15 12:52:30, Nancy-Anne Cianci wrote: > On 23.08.2016 14:03, ng0 wrote: > > These 3 patches enable us to have a functional pybitmessage version > > 0.6.1, released 2 days ago. > > I believe some updating had to be done for "msgpack". > > > This message is so old I don't even know what you try to answer or ask. Can you be more specific? -- ng0 -- https://www.inventati.org/patternsinthechaos/
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On 23.08.2016 14:03, ng0 wrote: > These 3 patches enable us to have a functional pybitmessage version > 0.6.1, released 2 days ago. I believe some updating had to be done for "msgpack".
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On Thu, Aug 25, 2016 at 09:52:22AM +, ng0 wrote:
> ng0 writes:
>
> > These 3 patches enable us to have a functional pybitmessage version
> > 0.6.1, released 2 days ago.
> >
> > For tests you can use either the test channel which can be found on
> > bitmessage.org (or in the application itself? I don't know, I'm no
> > newcomer to this application) or the channel I did setup a while ago
> > (blame my window manager if there's a typo, the copy & paste is
> > sometimes stuck):
> > BM-2cTPsDEX29yRnrAmyfwZhC3RySsK4wnQUA
> > [chan] gnuguixchan
> >
>
> Just a thought to change the description a tiny bit when someone
> packages another bitmessage client: This is the implementation as found
> on bitmessage.org, but it is not the only implementation.
> --
> ng0
> For non-prism friendly talk find me on http://www.psyced.org
>
I've rebased the patches and applied some '#t' to some of the phases. If
anyone else would like to test them out or comment, they look ready to
me to be pushed.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
From 2a34dccb32340772b91b4e6b6340dcbddad3175b Mon Sep 17 00:00:00 2001
From: ng0
Date: Tue, 23 Aug 2016 10:13:59 +
Subject: [PATCH 1/3] gnu: Add python2-pyqt-4.
* gnu/packages/qt.scm (python2-pyqt-4): New variable.
Signed-off-by: Efraim Flashner
---
gnu/packages/qt.scm | 10 ++
1 file changed, 10 insertions(+)
diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
index 95690fa..a482d75 100644
--- a/gnu/packages/qt.scm
+++ b/gnu/packages/qt.scm
@@ -3,6 +3,7 @@
;;; Copyright © 2015 Sou Bunnbu
;;; Copyright © 2015 Ludovic Courtès
;;; Copyright © 2015, 2016 Efraim Flashner
+;;; Copyright © 2016 ng0
;;;
;;; This file is part of GNU Guix.
;;;
@@ -1069,6 +1070,15 @@ contain over 620 classes.")
%standard-phases)))
(license (list license:gpl2 license:gpl3 ; choice of either license
+(define-public python2-pyqt-4
+ (package (inherit python-pyqt-4)
+ (name "python2-pyqt-4")
+ (native-inputs
+`(("python-sip" ,python2-sip)
+ ("qt" ,qt-4)))
+ (inputs
+`(("python" ,python-2)
+
(define-public qtkeychain
(package
(name "qtkeychain")
--
2.10.0
From c528659cd5291d7d154ce40e2d9125cf2b1d747f Mon Sep 17 00:00:00 2001
From: ng0
Date: Tue, 23 Aug 2016 11:07:17 +
Subject: [PATCH 2/3] gnu: messaging: Use license: prefix.
* gnu/packages/disk.scm (define-module): Import guix licenses with a prefix.
(libotr): Use the license prefix.
(bitlbee): Likewise.
(hexchat): Likewise.
(ngircd): Likewise.
(pidgin): Likewise.
(pidgin-otr): Likewise.
(znc): Likewise.
(python-nbxmpp): Likewise.
(gajim): Likewise.
(prosody): Likewise.
(libtoxcore): Likewise.
Signed-off-by: Efraim Flashner
---
gnu/packages/messaging.scm | 34 --
1 file changed, 16 insertions(+), 18 deletions(-)
diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
index b95239a..c584eaf 100644
--- a/gnu/packages/messaging.scm
+++ b/gnu/packages/messaging.scm
@@ -23,9 +23,7 @@
;;; along with GNU Guix. If not, see
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On Tue, Sep 06, 2016 at 10:09:14PM +, ng0 wrote: > ng0 writes: > > > Upstream Bugreport: > > https://github.com/Bitmessage/PyBitmessage/issues/897 > > So we know this won't be fixed soon and that their priorities weird for > a software of this kind. > I think we have software with more problematic issues packaged, so > considering the fact that you can use this headless (you'll have to read > up how this works, I'venever done it), we can accept this, right? > > If the problems get worse than this, we can always drop it later. The best we can do in this case is try to get upstream to switch over to better supported toolchains. Dianara is on my eventual to-do list and it also is currently qt4. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
ng0 writes: > Upstream Bugreport: > https://github.com/Bitmessage/PyBitmessage/issues/897 So we know this won't be fixed soon and that their priorities weird for a software of this kind. I think we have software with more problematic issues packaged, so considering the fact that you can use this headless (you'll have to read up how this works, I'venever done it), we can accept this, right? If the problems get worse than this, we can always drop it later. -- ng0 For non-prism friendly talk find me on http://www.psyced.org
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
Upstream Bugreport: https://github.com/Bitmessage/PyBitmessage/issues/897 -- ng0 For non-prism friendly talk find me on http://www.psyced.org
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
Andreas Enge writes: > On Sat, Sep 03, 2016 at 04:47:52PM +, ng0 wrote: >> Upstream is aware of this and told me they are working on a port towards >> qt5 and also python3. However there is no deadline. It is their >> choice. As I recently read there are people using Guix who are >> interested in using PyBitmessage. >> This package is usable, license fits, I find this block you create a bit >> harsh. I can understand it, but does it mean that you are against adding >> it at all because of qt4? > > I am not blocking, it is just a bit frustrating to go backwards! If there > is no other solution and no easy replacement for the package you wish to add, > we could revert my previous commit. I am just feeling uneasy about packages > that are not maintained by upstream and do not receive security updates > any more. > > Andreas > Okay, I just wanted to ask. It felt a bit frustrating at first to get such a comment on something I worked on for more than just a few minutes. Thanks for clearing this up. There is no other solution than to contribute to upstream to work towards qt5 port. There's not much difference between pyqt5 and pyqt4, but I don't have the time to investigate and invest into this at the moment. My bugreport was a 1on1 message exchange with one of the developers of PyBitmessage, I'll open official bugreports now because this is not effective (I had a 50% finished setup.py passed along to this developer several months ago as a patch, nothing happened... github reaction was much faster). I know because a repository of it exists, that python2 -> python3 is being worked on. I want to drop qt4, but this application currently leaves me no other choice than to rely on qt4 and pyqt4. -- ng0 For non-prism friendly talk find me on http://www.psyced.org
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
On Sat, Sep 03, 2016 at 04:47:52PM +, ng0 wrote: > Upstream is aware of this and told me they are working on a port towards > qt5 and also python3. However there is no deadline. It is their > choice. As I recently read there are people using Guix who are > interested in using PyBitmessage. > This package is usable, license fits, I find this block you create a bit > harsh. I can understand it, but does it mean that you are against adding > it at all because of qt4? I am not blocking, it is just a bit frustrating to go backwards! If there is no other solution and no easy replacement for the package you wish to add, we could revert my previous commit. I am just feeling uneasy about packages that are not maintained by upstream and do not receive security updates any more. Andreas
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
Andreas Enge writes: > Hello, > > On Tue, Aug 23, 2016 at 12:03:07PM +, ng0 wrote: >> These 3 patches enable us to have a functional pybitmessage version >> 0.6.1, released 2 days ago. >> >> Subject: [PATCH 1/3] gnu: Add python2-pyqt-4. >> * gnu/packages/qt.scm (python2-pyqt-4): New variable. > > if at all possible, we should not add packages that depend on Qt-4. > This one, in particular, would revert my following commit: > > commit 3297deedd1fcfd98641b01b477fad182f70cad61 > Author: Andreas Enge > Date: Mon Feb 22 21:33:29 2016 +0100 > > gnu: Remove python2-pyqt-4. > > * gnu/packages/qt.scm (python2-pyqt-4): Delete variable. It depends on Qt > 4, > which does not receive security updates any more. > > I had removed the package since I realised that nothing depended on it. > > The goal is to get rid of Qt-4 (and also of the monolithic Qt-5). > > Andreas > Upstream is aware of this and told me they are working on a port towards qt5 and also python3. However there is no deadline. It is their choice. As I recently read there are people using Guix who are interested in using PyBitmessage. This package is usable, license fits, I find this block you create a bit harsh. I can understand it, but does it mean that you are against adding it at all because of qt4? -- ng0 For non-prism friendly talk find me on http://www.psyced.org
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
Hello, On Tue, Aug 23, 2016 at 12:03:07PM +, ng0 wrote: > These 3 patches enable us to have a functional pybitmessage version > 0.6.1, released 2 days ago. > > Subject: [PATCH 1/3] gnu: Add python2-pyqt-4. > * gnu/packages/qt.scm (python2-pyqt-4): New variable. if at all possible, we should not add packages that depend on Qt-4. This one, in particular, would revert my following commit: commit 3297deedd1fcfd98641b01b477fad182f70cad61 Author: Andreas Enge Date: Mon Feb 22 21:33:29 2016 +0100 gnu: Remove python2-pyqt-4. * gnu/packages/qt.scm (python2-pyqt-4): Delete variable. It depends on Qt 4, which does not receive security updates any more. I had removed the package since I realised that nothing depended on it. The goal is to get rid of Qt-4 (and also of the monolithic Qt-5). Andreas
Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
ng0 writes:
> These 3 patches enable us to have a functional pybitmessage version
> 0.6.1, released 2 days ago.
>
> For tests you can use either the test channel which can be found on
> bitmessage.org (or in the application itself? I don't know, I'm no
> newcomer to this application) or the channel I did setup a while ago
> (blame my window manager if there's a typo, the copy & paste is
> sometimes stuck):
> BM-2cTPsDEX29yRnrAmyfwZhC3RySsK4wnQUA
> [chan] gnuguixchan
>
> From 8687409cf6f424958e222de9eddf4c77750ecc57 Mon Sep 17 00:00:00 2001
> From: ng0
> Date: Tue, 23 Aug 2016 10:13:59 +
> Subject: [PATCH 1/3] gnu: Add python2-pyqt-4.
>
> * gnu/packages/qt.scm (python2-pyqt-4): New variable.
> ---
> gnu/packages/qt.scm | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
> index a7eee7c..99c12aa 100644
> --- a/gnu/packages/qt.scm
> +++ b/gnu/packages/qt.scm
> @@ -3,6 +3,7 @@
> ;;; Copyright © 2015 Sou Bunnbu
> ;;; Copyright © 2015 Ludovic Courtès
> ;;; Copyright © 2015, 2016 Efraim Flashner
> +;;; Copyright © 2016 ng0
> ;;;
> ;;; This file is part of GNU Guix.
> ;;;
> @@ -1057,6 +1058,15 @@ contain over 620 classes.")
> %standard-phases)))
> (license (list gpl2 gpl3 ; choice of either license
>
> +(define-public python2-pyqt-4
> + (package (inherit python-pyqt-4)
> + (name "python2-pyqt-4")
> + (native-inputs
> +`(("python-sip" ,python2-sip)
> + ("qt" ,qt-4)))
> + (inputs
> +`(("python" ,python-2)
> +
> (define-public qtkeychain
>(package
> (name "qtkeychain")
> --
> 2.9.3
>
> From 523d7da2b50028826de9f306171a60f77d25625e Mon Sep 17 00:00:00 2001
> From: ng0
> Date: Tue, 23 Aug 2016 11:07:17 +
> Subject: [PATCH 2/3] gnu: messaging: Use license: prefix.
>
> * gnu/packages/disk.scm (define-module): Import guix licenses with a prefix.
> (libotr): Use the import prefix.
> (bitlbee): Likewise.
> (hexchat): Likewise.
> (ngircd): Likewise.
> (pidgin): Likewise.
> (pidgin-otr): Likewise.
> (znc): Likewise.
> (python-nbxmpp): Likewise.
> (gajim): Likewise.
> ---
> gnu/packages/messaging.scm | 31 +++
> 1 file changed, 15 insertions(+), 16 deletions(-)
>
> diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
> index de9ac17..b0546f2 100644
> --- a/gnu/packages/messaging.scm
> +++ b/gnu/packages/messaging.scm
> @@ -5,6 +5,7 @@
> ;;; Copyright © 2015 Andreas Enge
> ;;; Copyright © 2015 Ricardo Wurmus
> ;;; Copyright © 2015 Efraim Flashner
> +;;; Copyright © 2016 ng0
> ;;;
> ;;; This file is part of GNU Guix.
> ;;;
> @@ -22,9 +23,7 @@
> ;;; along with GNU Guix. If not, see
