From: ng0 <ng0@we.make.ritual.n0.is>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.
Date: Sun, 04 Sep 2016 12:24:35 +0000 [thread overview]
Message-ID: <87d1kjvon0.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160903194304.GA16155@solar>
Andreas Enge <andreas@enge.fr> writes:
> On Sat, Sep 03, 2016 at 04:47:52PM +0000, 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
next prev parent reply other threads:[~2016-09-04 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:03 [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix ng0
2016-08-25 9:52 ` ng0
2016-09-07 8:20 ` Efraim Flashner
2016-09-03 15:54 ` Andreas Enge
2016-09-03 16:47 ` ng0
2016-09-03 19:43 ` Andreas Enge
2016-09-04 12:24 ` ng0 [this message]
2016-09-04 12:39 ` ng0
2016-09-06 22:09 ` ng0
2016-09-07 6:27 ` Efraim Flashner
2017-02-15 11:52 ` Nancy-Anne Cianci
2017-02-15 13:02 ` ng0
[not found] ` <23d678c8-feaf-f7eb-2d08-5ccfb1ea9b92@getbackinthe.kitchen>
2017-02-15 19:33 ` ng0
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1kjvon0.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=andreas@enge.fr \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).