unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: 33925@debbugs.gnu.org
Subject: bug#33925: Qt 5.11.3 bug-fix update
Date: Mon, 31 Dec 2018 20:44:01 +0200	[thread overview]
Message-ID: <20181231184401.GB16652@macbook41> (raw)
In-Reply-To: <20181230182911.GA5965@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Sun, Dec 30, 2018 at 01:29:11PM -0500, Leo Famulari wrote:
> There is a new release of Qt, 5.11.3, which is strictly a bug-fix
> release:
> 
> https://blog.qt.io/blog/2018/12/04/qt-5-11-3-released-important-security-updates/
> 
> It includes several important security-related fixes.
> 
> We should try updating it.
> 
> `guix refresh -l qtbase` says that 471 packages will need to be rebuilt.
> Maybe we can do the work on a special 'qt-updates' branch.
> 
> Would anyone like to lead this work?

I normally end up doing the qt updates. my work flow is to download the
md5sum file and use grep, awk or parallel, and aria2 to download the files.
After updating all the qt packages building them all (and qtwebkit)
takes hours, and then another day or two to fix build/test errors. If
you check, for example, the source for qtscript¹, it has barely changed
in the past year, so most of the updates are fairly straightforward.

Of course the fun part is figuring out all the dependant packages and
why they suddenly fail.

¹https://code.qt.io/cgit/qt/qtscript.git/log/


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-12-31 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30 18:29 bug#33925: Qt 5.11.3 bug-fix update Leo Famulari
2018-12-31 18:44 ` Efraim Flashner [this message]
2019-01-02 13:46   ` Efraim Flashner
2019-02-25 23:43     ` Leo Famulari

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=20181231184401.GB16652@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=33925@debbugs.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 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).