unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Florian Bruhin <me@the-compiler.org>
To: Jaft <wamm_kd_schmelingski@yahoo.com>
Cc: 53011@debbugs.gnu.org
Subject: bug#53011: Possible to Update qtbase-5 to v5.15.8?
Date: Tue, 4 Jan 2022 19:04:57 +0100	[thread overview]
Message-ID: <20220104180457.tgkrnle4nc6ougdr@aragog> (raw)
In-Reply-To: <28974452.1530175.1641317754644@mail.yahoo.com>

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

Hey,

qutebrowser upstream here.

On Tue, Jan 04, 2022 at 05:35:54PM +0000, Jaft wrote:
> Partially because it's the latest version but primarily because there's a bug in the current version for QTwebengine.

Note that qtbase releases after 5.15.2 are commercial-only
unfortunately:

https://www.qt.io/blog/qt-offering-changes-2020
https://www.qt.io/blog/commercial-lts-qt-5.15.3-released

However, QtWebEngine source releases are exempt from that, due to
containing third-party LGPL code, so its source for newer releases is
publicly available:
https://code.qt.io/cgit/qt/qtwebengine.git/refs/tags

Most distributions I'm aware of are still keeping updated with those
releases, as they should work just fine against an older qtbase.

Alternatively, to fix the issues with missing text, backporting this
patch should suffice:
https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/374232

However, newer QtWebEngine releases come with a variety of security
fixes and even a Chromium upgrade (from 83 to 87), so I'd highly
recommend keeping it up to date.

Florian

-- 
            me@the-compiler.org | https://www.qutebrowser.org 
       https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
       GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
             I love long mails! | https://email.is-not-s.ms/

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

  parent reply	other threads:[~2022-01-04 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28974452.1530175.1641317754644.ref@mail.yahoo.com>
2022-01-04 17:35 ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Jaft via Bug reports for GNU Guix
2022-01-04 18:03   ` Leo Famulari
2022-01-04 18:04   ` Leo Famulari
2022-01-04 18:04   ` Florian Bruhin [this message]
2022-01-05  7:07     ` Philip McGrath
2022-01-05 19:08     ` Leo Famulari
2022-01-05 19:09       ` Leo Famulari
2022-02-02 19:15         ` Jaft via Bug reports for GNU Guix
2022-01-04 20:32   ` Florian Bruhin
2022-01-05 19:10   ` bug#53011: [PATCH] gnu: Fix text rendering in QtWebEngine Leo Famulari
2022-07-01 22:08   ` bug#53011: Qt patches for 5.15.5 phodina via Bug reports for GNU Guix
2023-03-29  0:38   ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Maxim Cournoyer

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=20220104180457.tgkrnle4nc6ougdr@aragog \
    --to=me@the-compiler.org \
    --cc=53011@debbugs.gnu.org \
    --cc=wamm_kd_schmelingski@yahoo.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 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).