Thanks for the comments everyone. This vote fails. Here's how I think we
should proceed:
- [SPARK-20197] - SparkR CRAN - appears to be resolved
- [SPARK-] - Python packaging - Holden, please file a JIRA and report
if this is a regression and if there is an easy fix that we should wait for.
Hi,
https://issues.apache.org/jira/browse/SPARK-20202?jql=priority%20%3D%20Blocker%20AND%20affectedVersion%20%3D%20%222.1.1%22%20and%20project%3D%22spark%22
Indicates there is another blocker (SPARK-20197 should have come in
the list too, but was marked major).
Regards,
Mridul
On Tue, Apr 4,
This is maybe a blocker. See my suggested action about voting on the
current artifact to, I believe, eliminate the possible blocking part of the
issue in the short term.
On Tue, Apr 4, 2017, 22:02 Mridul Muralidharan wrote:
> Hi,
>
>
> https://issues.apache.org/jira/browse/SPARK-20202?jql=priori
So the fix is installing pandoc on whichever machine is used for packaging.
I thought that was generally done on the machine of the person rolling the
release so I wasn't sure it made sense as a JIRA, but from chatting with
Josh it sounds like that part might be on of the Jenkins workers - is there
See SPARK-20216, if Michael can let me know which machine is being used for
packaging I can see if I can install pandoc on it (should be simple but I
know the Jenkins cluster is a bit on the older side).
On Tue, Apr 4, 2017 at 3:06 PM, Holden Karau wrote:
> So the fix is installing pandoc on whi
