unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Remco van 't Veer <remco@remworks.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56302@debbugs.gnu.org
Subject: [bug#56302] Acknowledgement ([PATCH] gnu: ruby: Update to 2.7.6 [security fixes].)
Date: Wed, 29 Jun 2022 18:13:38 +0200	[thread overview]
Message-ID: <875ykjh2h9.fsf@remworks.net> (raw)
In-Reply-To: <975d34406b3e636414efdeb2ff1d7dbd4e95d944.camel@telenet.be>

2022/06/29 18:04, Maxime Devos:

> core-updates probably won't be merged for a long time, so a graft might
> be needed in the meantime.

So, keep this bug and make a new patch / bug for the graft?

> Basically, what you need to do is:
>
>   * keep the old ruby@2.7.4 package definition
>   * add a ruby@2.7.6 package (as (define-public ruby-2.7-fixed [...]))
>   * in ruby@2.7.4, add a field
>     (replacement ruby-2.7-fixed) ; security fixes
>
> and verify that some Ruby-using dependents still seem to work.
>
> That way, we can use a fixed ruby@2.7.6 on master.
>
> (This assumes that ruby is graftable -- this assumes that ruby is
> ABI-compatible, otherwise the grafted dependents won't work.)

Thanks for the explanation! I'll give it a try.

Cheers,
Remco




  reply	other threads:[~2022-06-29 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 15:55 [bug#56302] [PATCH] gnu: ruby: Update to 2.7.6 [security fixes] Remco van 't Veer
     [not found] ` <handler.56302.B.165651815228055.ack@debbugs.gnu.org>
2022-06-29 15:58   ` [bug#56302] Acknowledgement ([PATCH] gnu: ruby: Update to 2.7.6 [security fixes].) Remco van 't Veer
2022-06-29 16:04     ` Tobias Geerinckx-Rice via Guix-patches via
2022-06-29 16:04     ` Maxime Devos
2022-06-29 16:13       ` Remco van 't Veer [this message]
2022-06-29 18:18         ` Maxime Devos
2022-06-29 18:00 ` [bug#56302] [PATCH v2] gnu: ruby: Update to 2.7.6 [security fixes] Remco van 't Veer
2022-08-29 14:48   ` bug#56302: " Marius Bakke
2022-06-29 18:29 ` [bug#56302] [PATCH] " Maxime Devos
2022-06-29 18:57   ` Maxime Devos
2022-08-29 14:51     ` 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

  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=875ykjh2h9.fsf@remworks.net \
    --to=remco@remworks.net \
    --cc=56302@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).