From: Andreas Enge <andreas@enge.fr>
To: ng0 <ng0@we.make.ritual.n0.is>
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: Sat, 3 Sep 2016 17:54:56 +0200 [thread overview]
Message-ID: <20160903155456.GA3519@solar> (raw)
In-Reply-To: <878tvnk804.fsf@we.make.ritual.n0.is>
Hello,
On Tue, Aug 23, 2016 at 12:03:07PM +0000, 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 <andreas@enge.fr>
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
next prev parent reply other threads:[~2016-09-03 15:55 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 [this message]
2016-09-03 16:47 ` ng0
2016-09-03 19:43 ` Andreas Enge
2016-09-04 12:24 ` ng0
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160903155456.GA3519@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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.