From: hi@alyssa.is
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95188] [Ruby master Bug#16198] Packaging regression in ruby-2.4.8
Date: Wed, 02 Oct 2019 10:37:20 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-81819.20191002103720.da63aee8f0cb21db@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16198.20191002103310@ruby-lang.org
Issue #16198 has been updated by qyliss (Alyssa Ross).
This can be closed — I see now that it’s a duplicate.
----------------------------------------
Bug #16198: Packaging regression in ruby-2.4.8
https://bugs.ruby-lang.org/issues/16198#change-81819
* Author: qyliss (Alyssa Ross)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.4.8
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
In the ruby-2.4.8 tarball, the ruby-2.4.8/gems directory does not
contain the extracted default gems. This is a change from 2.4.7, and is
also not the case in 2.5.7. I would not expect this to change for a
teeny release, and suspect it was a packaging error.
Compare the output of `tar tf ruby-2.4.8.tar.gz ruby-2.4.8/gems` with
`tar tf ruby-2.4.7.tar.gz ruby-2.4.7/gems` and you'll see what I mean.
This broke our packaging scripts in Nixpkgs, and I suspect it will
affect other packagers as well.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-10-02 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16198.20191002103310@ruby-lang.org>
2019-10-02 10:33 ` [ruby-core:95187] [Ruby master Bug#16198] Packaging regression in ruby-2.4.8 hi
2019-10-02 10:37 ` hi [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-81819.20191002103720.da63aee8f0cb21db@ruby-lang.org \
--to=ruby-core@ruby-lang.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 read-only IMAP folder(s) and NNTP newsgroup(s).