From: naruse@... Date: 2016-06-10T12:43:59+00:00 Subject: [ruby-core:75943] [Ruby trunk Bug#12456][Third Party's Issue] tmpdir.rb raises Errors in Windows 10 Subsystem for Linux Issue #12456 has been updated by Yui NARUSE. Status changed from Open to Third Party's Issue Thank you for reporting with the essential information "on Windows Subsystem for Linux". Unless special condition, such issues are considered issues of Windows Subsystem for Linux. Such a real world compatibility problem will help them ;-) https://github.com/Microsoft/BashOnWindows/issues ---------------------------------------- Bug #12456: tmpdir.rb raises Errors in Windows 10 Subsystem for Linux https://bugs.ruby-lang.org/issues/12456#change-59137 * Author: Mathias Slawik * Status: Third Party's Issue * Priority: Normal * Assignee: * ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Hello, under the new Windows 10 Subsystem for Linux, tmpdir.rb throws Errors, because of the "if stat.world_writable? and !stat.sticky?" check. Under Windows 10, all directories are mode 777 by default. However, directory permissions are still enforced by other parts of the OS, unseen by the Linux subsystem. That means there is little sense in checking for the sticky bit in the new Windows subsystem. This causes problems in Bundler, for example. See here: https://github.com/bundler/bundler/issues/4630 The workaround is adding a sticky bit to the offending directories. I am no expert in this but could you introduce an additional check so that it just ignores Microsofts strange directory modes when run under Windows 10 Subsystem for Linux? Best regards, Mathias -- https://bugs.ruby-lang.org/ Unsubscribe: