From: "Thompson, David" <dthompson2@worcester.edu>
To: Kei Kebreau <kkebreau@posteo.net>
Cc: 30876@debbugs.gnu.org
Subject: [bug#30876] [PATCH] gnu: ruby-sanitize: Update to 4.6.3.
Date: Tue, 20 Mar 2018 10:50:52 -0400 [thread overview]
Message-ID: <CAJ=Rwfa-35BJfsjnO1chh-dNJJ2g8pnbCRPb5Mv+79XKKaEC7w@mail.gmail.com> (raw)
In-Reply-To: <20180320140907.27847-1-kkebreau@posteo.net>
On Tue, Mar 20, 2018 at 10:09 AM, Kei Kebreau <kkebreau@posteo.net> wrote:
> This fixes CVE-2018-3740.
>
> * gnu/packages/ruby.scm (ruby-sanitize): Update to 4.6.3.
> ---
> gnu/packages/ruby.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm
> index dcf4cda26..010dedde2 100644
> --- a/gnu/packages/ruby.scm
> +++ b/gnu/packages/ruby.scm
> @@ -3082,7 +3082,7 @@ access the result as a Nokogiri parsed document.")
> (define-public ruby-sanitize
> (package
> (name "ruby-sanitize")
> - (version "4.0.0")
> + (version "4.6.3")
> (source (origin
> (method url-fetch)
> ;; The gem does not include the Rakefile, so we download the
> @@ -3092,7 +3092,7 @@ access the result as a Nokogiri parsed document.")
> (file-name (string-append name "-" version ".tar.gz"))
> (sha256
> (base32
> - "055xnj38l60gxnnng76kpy2l2jbrp0byjdyq17jw79w7l4b40znr"))))
> + "1fmqppwif3cm8h79006jfzkdnlxxzlry9kzk03psk0d5xpg55ycc"))))
> (build-system ruby-build-system)
> (propagated-inputs
> `(("ruby-crass" ,ruby-crass)
> --
> 2.16.2
Looks good, thanks!
- Dave
next prev parent reply other threads:[~2018-03-20 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 14:09 [bug#30876] [PATCH] gnu: ruby-sanitize: Update to 4.6.3 Kei Kebreau
2018-03-20 14:50 ` Thompson, David [this message]
2018-03-20 15:21 ` bug#30876: " Kei Kebreau
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='CAJ=Rwfa-35BJfsjnO1chh-dNJJ2g8pnbCRPb5Mv+79XKKaEC7w@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=30876@debbugs.gnu.org \
--cc=kkebreau@posteo.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.