[jira] [Commented] (HADOOP-15912) start-build-env.sh still creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802

[ https://issues.apache.org/jira/browse/HADOOP-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680433#comment-16680433 ] Jon Boone commented on HADOOP-15912: Agreed.  That is the most general solution. >

[jira] [Commented] (HADOOP-15802) start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry

[ https://issues.apache.org/jira/browse/HADOOP-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649226#comment-16649226 ] Jon Boone commented on HADOOP-15802: It doesn't appear that there are any tests for

[jira] [Updated] (HADOOP-15802) start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry

[ https://issues.apache.org/jira/browse/HADOOP-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Boone updated HADOOP-15802: --- Attachment: HADOOP-15802.001.patch Status: Patch Available (was: Open) > start-build-env.s

[jira] [Commented] (HADOOP-15802) start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry

[ https://issues.apache.org/jira/browse/HADOOP-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648900#comment-16648900 ] Jon Boone commented on HADOOP-15802: My first thought was to add the '-e' option to

[jira] [Created] (HADOOP-15802) start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry

Jon Boone created HADOOP-15802: -- Summary: start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry Key: HADOOP-15802 URL: https://issues.apache.org/jira/browse/HADOOP-15802