unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Leo Famulari <leo@famulari.name>
Cc: 50016@debbugs.gnu.org
Subject: [bug#50016] [PATCH] gnu: gnuradio: Don't include QtWebKit in the dependency graph.
Date: Thu, 12 Aug 2021 07:29:28 +0000	[thread overview]
Message-ID: <874kbvce93.fsf@kitej> (raw)
In-Reply-To: <YRRMfgCYM/VoPx4G@jasmine.lan>

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

Leo Famulari <leo@famulari.name> skribis:

> I am proposing this change because:
>
> 1) QtWebKit is hard to keep building:
>
> <https://bugs.gnu.org/50014>
>
> 2) QtWebKit is not really "ready" to be used, being an alpha release
> with a huge caveat from upstream:
>
> "WARNING: This release is based on old WebKit revision with known
> unpatched vulnerabilities. Please use it carefully and avoid visiting
> untrusted websites and using it for transmission of sensitive data.
> Please wait for new release from qtwebkit-dev branch to use it with
> untrusted content."
> https://github.com/qtwebkit/qtwebkit/releases/tag/qtwebkit-5.212.0-alpha4
> https://seclists.org/oss-sec/2021/q3/66
>
> 3) It doesn't seem to be used by gnuradio, although I'm not 100% sure.
> It's not mentioned in the gnuradio build log, anyways.

gr-satellites has some functions using HTTP connections, but it's using
python-requests for that, not qtwebkit.
So it looks like nothing based on gnuradio actually depends on qtwebkit,
and your patch will not cause any issue.

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

  reply	other threads:[~2021-08-12  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 22:11 [bug#50016] [PATCH] gnu: gnuradio: Don't include QtWebKit in the dependency graph Leo Famulari
2021-08-11 22:17 ` Leo Famulari
2021-08-12  7:29   ` Guillaume Le Vaillant [this message]
2021-08-15 18:04     ` bug#50016: " 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=874kbvce93.fsf@kitej \
    --to=glv@posteo.net \
    --cc=50016@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).