From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] The path towards Ruby 3
Date: Wed, 14 Jul 2021 12:32:50 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31955@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
New issue by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/31955
Description:
I would like to update Ruby to the new major release 3, and I'd rather not provide a package for 2.7 anymore.
This results in the following implications:
- According to Arch, they have 2.7 around for: facter, hiera, puppet, vagrant
- According to upstream, vagrant 2.2.17 should support Ruby 3.
- The puppet-related packages were not touched since 2019 (by @ndowens), which suggests they are not used.
- Only Puppet 7.8 has experimental support for Ruby 3.
Therefore I'll prepare a PR for Ruby 3 which removes Puppet, unless someone is interested in updating and maintaining them. All other uses of Ruby in Void should work with Ruby 3.
next reply other threads:[~2021-07-14 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 10:32 leahneukirchen [this message]
2021-07-23 13:14 ` [ISSUE] [CLOSED] " leahneukirchen
2022-04-11 17:14 ` kotoko
2023-01-05 8:45 ` Animeshz
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31955@inbox.vuxu.org \
--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).