From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Ruby 3.1
Date: Fri, 11 Mar 2022 10:58:09 +0100 [thread overview]
Message-ID: <20220311095809.dE3CN-BLyuLqS_4ljffqLzTo_7GVUIpeTrovoLMabig@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34706@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
There is an updated pull request by leahneukirchen against master on the void-packages repository
https://github.com/leahneukirchen/void-packages ruby31
https://github.com/void-linux/void-packages/pull/34706
Ruby 3.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
Due to upstream bug https://bugs.ruby-lang.org/issues/18373 we need a workaround for now: https://bugs.ruby-lang.org/issues/18373
Vagrant required a patch, someone please test whether it still works.
A patch file from https://github.com/void-linux/void-packages/pull/34706.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ruby31-34706.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2022-03-11 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 16:25 [PR PATCH] " leahneukirchen
2022-03-11 9:58 ` [PR PATCH] [Closed]: " leahneukirchen
2022-03-11 9:58 ` leahneukirchen [this message]
2022-03-11 10:00 ` [PR PATCH] [Updated] " leahneukirchen
2022-03-12 14:48 ` leahneukirchen
2022-03-12 15:40 ` [PR PATCH] [Closed]: " leahneukirchen
2022-03-12 15:40 ` leahneukirchen
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=20220311095809.dE3CN-BLyuLqS_4ljffqLzTo_7GVUIpeTrovoLMabig@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).