From: zimoun <zimon.toutoune@gmail.com>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates?
Date: Tue, 16 Mar 2021 17:34:34 +0100 [thread overview]
Message-ID: <CAJ3okZ3+Zc1_g_5WFPCFNYUt4mD5ZVUky+epcPDkMcjrG0NK_w@mail.gmail.com> (raw)
In-Reply-To: <91998d12df3c4a279f46cf50b15d47c99e064a46.camel@zaclys.net>
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
Hi,
This commit 6f873731a030dd7ecbd8a5e756b38b26306f6966:
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6f873731a030dd7ecbd8a5e756b38b26306f6966>
fixes CVE-2021-24032 which says: "Beginning in v1.4.1 and prior to
v1.4.9, output files were created with default permissions. [...]".
The mentioned commit replaces zstd@1.4.4 by zstd@1.4.9 which seems
more than just grafting. Well,1.4.4 was released on Nov 2019 and
1.4.9 some days ago.
I agree that security is important but we lived more than one and half
year with 1.4.4 so the upgrade to 1.4.9 should only go to
core-updates, not as a 'replacement' graft. IMHO.
The consequence of this change was the breakage of "guix pull" on
master for at least i686. Which leads to the commit
2bcfb944bdd2f476ef8d34802fed436e4fdda0ab disabling the zstd test-suite
for all the architectures.
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=2bcfb944bdd2f476ef8d34802fed436e4fdda0ab>
Noting that "guix pull" should be still failing for at least i686 on
core-updates because of the test suite of zstd@1.4.9.
The question is: should the next release 1.2.1 contain zstd@1.4.9 as
graft? Or do we revert the commit and simply fix it on core-updates
and wait for the next core-updates cycle. Personally, I am in favor
of the latter. WDYT?
The issue is the test:
roundTripTest -g8M "19 -T0 --long"
which fails for the value 19 but not other values as 18 or 20 or many
others. After a quick reading of the doc, I am not sure to understand
the meaning of such value. Input welcome.
BTW, on my machine the attached patch builds for both x86_64 and i686
(emulated).
./pre-inst-env guix build zstd@1.4.9 --system=i686-linux --no-grafts
Depending on the answer of the previous question, the patch should go
to master or core-updates. And other architectures should be examined
with care.
Cheers,
simon
[-- Attachment #2: fix-zstd-i686.patch --]
[-- Type: text/x-patch, Size: 1059 bytes --]
diff --git a/gnu/packages/compression.scm b/gnu/packages/compression.scm
index 827ad43dc2..86ce3a697d 100644
--- a/gnu/packages/compression.scm
+++ b/gnu/packages/compression.scm
@@ -32,6 +32,7 @@
;;; Copyright © 2020 Léo Le Bouter <lle-bout@zaclys.net>
;;; Copyright © 2021 Antoine Côté <antoine.cote@posteo.net>
;;; Copyright © 2021 Vincent Legoll <vincent.legoll@gmail.com>
+;;; Copyright © 2021 Simon Tournier <zimon.toutoune@gmail.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -1483,7 +1484,13 @@ speed.")
(base32 "14yj7309gsvg39rki4xqnd6w5idmqi0655v1fc0mk1m2kvhp9b19"))))
(arguments
(substitute-keyword-arguments (package-arguments zstd)
- ((#:tests? _ #t) #f)))))
+ ((#:phases phases)
+ `(modify-phases ,phases
+ (add-after 'unpack 'fix-test-i686
+ (lambda _
+ (substitute* "tests/playTests.sh"
+ (("roundTripTest -g8M \"19 -T0 --long\"")
+ "roundTripTest -g8M \"22 -T0 --long\""))))))))))
(define-public pzstd
(package
next prev parent reply other threads:[~2021-03-16 16:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 5:09 GNU Guix (pull?) on i686 broke after zstd grafting Léo Le Bouter
2021-03-06 5:30 ` Léo Le Bouter
2021-03-10 10:37 ` Ludovic Courtès
2021-03-10 10:43 ` Léo Le Bouter
2021-03-11 2:11 ` Léo Le Bouter
2021-03-11 9:37 ` zimoun
2021-03-11 9:40 ` Léo Le Bouter
2021-03-11 9:58 ` zimoun
2021-03-11 10:05 ` Léo Le Bouter
2021-03-16 16:34 ` zimoun [this message]
2021-03-16 17:06 ` Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates? Léo Le Bouter
2021-03-16 17:48 ` Leo Famulari
2021-03-16 18:03 ` Léo Le Bouter
2021-03-16 17:59 ` zimoun
2021-03-16 17:55 ` Leo Famulari
2021-03-16 18:08 ` Léo Le Bouter
2021-03-16 18:46 ` zimoun
2021-03-16 18:50 ` Léo Le Bouter
2021-03-16 19:04 ` zimoun
2021-03-16 18:19 ` zimoun
2021-03-16 18:26 ` Léo Le Bouter
2021-03-16 19:18 ` Leo Famulari
2021-03-16 19:25 ` zimoun
2021-03-16 19:29 ` Leo Famulari
2021-03-16 21:46 ` Security-czar needed? WAS: " Bengt Richter
2021-03-16 22:03 ` Leo Famulari
2021-03-17 6:24 ` Léo Le Bouter
2021-03-17 14:00 ` zimoun
2021-03-16 21:47 ` Maxime Devos
2021-03-16 20:53 ` Tobias Geerinckx-Rice
2021-03-16 21:18 ` Vincent Legoll
2021-03-16 21:56 ` Leo Famulari
2021-03-17 6:40 ` Léo Le Bouter
2021-03-30 0:35 ` Léo Le Bouter
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=CAJ3okZ3+Zc1_g_5WFPCFNYUt4mD5ZVUky+epcPDkMcjrG0NK_w@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@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).