all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Staying on top of Qt security
Date: Sun, 21 Feb 2016 09:42:43 -0800	[thread overview]
Message-ID: <87ziuuarix.fsf@dustycloud.org> (raw)
In-Reply-To: <20160221072837.GA16855@jasmine>

Leo Famulari writes:

> On Sat, Feb 20, 2016 at 10:27:52AM -0800, Christopher Allan Webber wrote:
>> Andreas Enge writes:
>> 
>> > On Thu, Feb 18, 2016 at 02:53:40PM -0800, Christopher Allan Webber wrote:
>> >> I'm assuming this was directed at me (though I don't work on Pumpa, but
>> >> I could ask the author things... I do *use* it every day though).  What
>> >> am I being asked here... I'm not sure?  Whether Pumpa could be updated
>> >> to QT 5?
>> >
>> > I think so :-)
>> >
>> > The alternative question would have been whether we could remove it,
>> > but I already knew the answer...
>> >
>> > Andreas
>> 
>> From Sazius:
>> 
>>   Hi! Pumpa already works with Qt 5, I'm running it on Qt 5.3.2 in Debian
>>   jessie myself. If you have any problems (e.g. with a newer version of
>>   Qt) I would consider it a bug and try to fix it :-)
>> 
>> So it looks like we just need to update the pacakge?
>
> The blocker is the Pumpa dependency QJson, which has a hard dependency
> on Qt-4. QJson is also used by libdbusmenu-qt.
>
> Apparently QJson's master branch has supported Qt-5 for some time, so I
> asked the maintainers if that is true, and if they plan to issue a new
> release [0]. We could try packaging from git.
>
> [0]
> https://github.com/flavio/qjson/issues/49

Sounds good.  If they don't make a new release, I think packaging from
git is the best option.

  reply	other threads:[~2016-02-21 17:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 20:01 Staying on top of Qt security Leo Famulari
2016-02-18 20:43 ` Andreas Enge
2016-02-18 22:35   ` Leo Famulari
2016-02-20 20:46     ` Efraim Flashner
2016-02-18 22:53   ` Christopher Allan Webber
2016-02-18 22:59     ` Andreas Enge
2016-02-20 18:27       ` Christopher Allan Webber
2016-02-21  7:28         ` Leo Famulari
2016-02-21 17:42           ` Christopher Allan Webber [this message]
2016-02-21 19:27             ` Leo Famulari
2016-02-22 19:53             ` Andreas Enge
2016-02-22 20:19               ` Leo Famulari
2016-02-22 20:40           ` Andreas Enge
2016-02-22 20:36   ` Andreas Enge
2016-02-25  8:35 ` Andreas Enge
2016-02-25  9:04   ` Andreas Enge
2016-02-25  9:06     ` Andreas Enge
2016-02-25  9:36       ` Ricardo Wurmus
2016-03-05 11:41       ` Andreas Enge
2016-03-05 21:16         ` Ricardo Wurmus
2016-03-05 21:18           ` Andreas Enge
2016-03-09  8:46             ` Ricardo Wurmus
2016-02-25  9:38   ` Ricardo Wurmus
2016-02-25 20:22     ` Andreas Enge

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=87ziuuarix.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.