From: Maxime Devos <maximedevos@telenet.be>
To: Remco van 't Veer <remco@remworks.net>, 56303@debbugs.gnu.org
Subject: [bug#56303] [PATCH] gnu: ruby: Update to 3.0.4 [security fixes].
Date: Thu, 30 Jun 2022 13:17:41 +0200 [thread overview]
Message-ID: <057aef5e94b2c535cd32f9b3b0a061c7ea77d914.camel@telenet.be> (raw)
In-Reply-To: <b93a38c77b375c2c9e226c5b7616c1f9291eec8e.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Maxime Devos schreef op do 30-06-2022 om 12:07 [+0200]:
> Remco van 't Veer schreef op wo 29-06-2022 om 17:55 [+0200]:
> > (define-public ruby-3.0
> > (package
> > (inherit ruby-2.7)
> > - (version "3.0.2")
> > + (version "3.0.4")
> > (source
> > (origin
> > (method url-fetch)
> > @@ -198,7 +199,7 @@ (define-public ruby-3.0
> > "/ruby-" version ".tar.xz"))
> > (sha256
> > (base32
> > -
> "0h2w2ms4gx2s96v3lzdr3add94bd2qqkhdjzaycmaqhg21rpf3jp"))))))
> > +
> "1w7jpq3flnm007z5kj8kixgm8l4smb80w8ak4993a12j0irzq8lf"))))))
>
> Hash matches what I get locally (without fallbacks).
> The download matches the hashes at
> <https://www.ruby-lang.org/en/news/2022/04/12/ruby-3-0-4-released/>.
>
> Next step: compare diff ...
Aside from some old bundling & generated file issues (for which I've
made another (non-blocking) bug report), diff didn't seem ‘suspicious’
while scrolling through it, though it would be rather easy to hide
something there.
So assuming it builds, I don't expect problems with this update.
(Also, it doesn't have any dependents.)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-30 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 15:55 [bug#56303] [PATCH] gnu: ruby: Update to 3.0.4 [security fixes] Remco van 't Veer
2022-06-30 10:07 ` Maxime Devos
2022-06-30 11:17 ` Maxime Devos [this message]
2022-08-29 14:49 ` bug#56303: " Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=057aef5e94b2c535cd32f9b3b0a061c7ea77d914.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56303@debbugs.gnu.org \
--cc=remco@remworks.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.