From: Efraim Flashner <efraim@flashner.co.il>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/3] gnu: python-pyqt-5.5: Use non-inherited "configure" phase.
Date: Fri, 09 Dec 2016 12:30:13 +0000 [thread overview]
Message-ID: <8EBFDFEF-77D6-4D84-A333-BA005F0E0628@flashner.co.il> (raw)
In-Reply-To: <584AA37C.2080501@crazy-compilers.com>
On December 9, 2016 2:28:44 PM GMT+02:00, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
>Am 08.12.2016 um 22:19 schrieb Efraim Flashner:
>> Currently the only package that relies on python-pyqt-5.5 and
>> python2-pyqt-5.5 is calibre. I would consider upgrading calibre and
>> seeing if it can be built with pyqt-5.6 or pyqt-5.7 and then just
>> removing python[2]-pyqt-5.5
>
>I updated calibre to the newest version 2.74 (will post the patch
>later). It still requires Qt 5.5.
Are you sure? I built 2.63 with pyqt-5.6 on top of your patch and it built fine. I didn't try actually running it though
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2016-12-09 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 17:10 [PATCH] gnu: python-pyqt: Fix build by explicitly setting the stubsdir Hartmut Goebel
2016-12-03 16:12 ` Ricardo Wurmus
2016-12-05 8:53 ` Hartmut Goebel
2016-12-05 9:12 ` [PATCH 0/3] Fixes for python-pyqt Hartmut Goebel
2016-12-05 9:12 ` [PATCH 1/3] gnu: python2-pyqt-4: Change package name to python2-pyqt Hartmut Goebel
2016-12-08 21:17 ` Efraim Flashner
2016-12-05 9:12 ` [PATCH 2/3] gnu: python-pyqt-5.5: Use non-inherited "configure" phase Hartmut Goebel
2016-12-05 12:44 ` Hartmut Goebel
2016-12-08 21:19 ` Efraim Flashner
2016-12-09 12:28 ` Hartmut Goebel
2016-12-09 12:30 ` Efraim Flashner [this message]
2016-12-09 12:54 ` Hartmut Goebel
2016-12-05 9:12 ` [PATCH 3/3 v2] gnu: python-pyqt: Fix build by explicitly setting the stubsdir Hartmut Goebel
2016-12-08 21:20 ` Efraim Flashner
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=8EBFDFEF-77D6-4D84-A333-BA005F0E0628@flashner.co.il \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.