From: nagachika00@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:99294] [Ruby master Bug#16662] lchmod available in linux since glibc 2.31.9000
Date: Thu, 23 Jul 2020 08:23:02 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-86683.20200723082301.703@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16662.20200228104231.703@ruby-lang.org
Issue #16662 has been updated by nagachika (Tomoyuki Chikanaga).
Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: REQUIRED to 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: DONE
ruby_2_7 c53cee7a0e7b3e87ba3fbafa86bd74460af18d93 merged revision(s) 72c02aa4b79731c7f25c9267f74b347f1946c704.
----------------------------------------
Bug #16662: lchmod available in linux since glibc 2.31.9000
https://bugs.ruby-lang.org/issues/16662#change-86683
* Author: vo.x (Vit Ondruch)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 2.8.0dev (2020-02-26 master 83705c42ce) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: DONE
----------------------------------------
Testing of Fedora Rawhide, it seems that lchmod(2) is available and therefore the `TestNotImplement#test_respond_to_lchmod` test fails. You can check the build here [1] or the full build log including dumped configure.log is in attachment, because it will be garbage collected
[1]: https://koji.fedoraproject.org/koji/taskinfo?taskID=41967785
---Files--------------------------------
build.log.tar.gz (308 KB)
root.log.tar.gz (11.2 KB)
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2020-07-23 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:42 [ruby-core:97302] [Ruby master Bug#16662] lchmod available in linux since 2.31.9000 v.ondruch
2020-02-28 11:11 ` [ruby-core:97303] " v.ondruch
2020-04-01 15:43 ` [ruby-core:97659] [Ruby master Bug#16662] lchmod available in linux since glibc 2.31.9000 v.ondruch
2020-07-23 8:23 ` nagachika00 [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-86683.20200723082301.703@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).