From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 47231@debbugs.gnu.org
Subject: bug#47231: sqlite package is vulnerable to CVE-2020-11655, CVE-2020-11656, CVE-2020-13434, CVE-2020-13435, CVE-2020-13630, CVE-2020-13631, CVE-2020-13632, CVE-2020-15358 and CVE-2020-9327
Date: Wed, 24 Mar 2021 23:54:52 +0100 [thread overview]
Message-ID: <b8543b82478ccf61691186795f331f6ff9679862.camel@zaclys.net> (raw)
In-Reply-To: <e38a431d1fe6bd5b2a79746b04497cc3fec49c59.camel@zaclys.net>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
I could test the graft with GNU Guix's test suite by manually replacing
the sqlite input with sqlite/fixed like so:
diff --git a/gnu/packages/package-management.scm
b/gnu/packages/package-management.scm
index 888f54322d..70f5c2dad3 100644
--- a/gnu/packages/package-management.scm
+++ b/gnu/packages/package-management.scm
@@ -389,7 +389,7 @@ $(prefix)/etc/init.d\n")))
(inputs
`(("bzip2" ,bzip2)
("gzip" ,gzip)
- ("sqlite" ,sqlite)
+ ("sqlite" ,sqlite/fixed)
("libgcrypt" ,libgcrypt)
("guile" ,guile-3.0-latest)
It worked fine.
Is that enough of a test to graft in master?
Let me know and I will push.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-24 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 11:42 bug#47231: sqlite package is vulnerable to CVE-2020-11655, CVE-2020-11656, CVE-2020-13434, CVE-2020-13435, CVE-2020-13630, CVE-2020-13631, CVE-2020-13632, CVE-2020-15358 and CVE-2020-9327 Léo Le Bouter via Bug reports for GNU Guix
2021-03-23 23:37 ` Léo Le Bouter via Bug reports for GNU Guix
2021-03-24 22:54 ` Léo Le Bouter via Bug reports for GNU Guix [this message]
2021-03-25 11:27 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-25 15:56 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-26 1:23 ` Mark H Weaver
2021-03-26 1:36 ` Léo Le Bouter via Bug reports for GNU Guix
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=b8543b82478ccf61691186795f331f6ff9679862.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47231@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/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).