You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/10/22 04:07:00 UTC

[jira] [Assigned] (SPARK-22327) R CRAN check fails on non-latest branches

     [ https://issues.apache.org/jira/browse/SPARK-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apache Spark reassigned SPARK-22327:
------------------------------------

    Assignee: Apache Spark

> R CRAN check fails on non-latest branches
> -----------------------------------------
>
>                 Key: SPARK-22327
>                 URL: https://issues.apache.org/jira/browse/SPARK-22327
>             Project: Spark
>          Issue Type: Bug
>          Components: SparkR
>    Affects Versions: 1.6.4, 2.0.3, 2.1.3, 2.2.1, 2.3.0
>            Reporter: Felix Cheung
>            Assignee: Apache Spark
>
> with warning
> * checking CRAN incoming feasibility ... WARNING
> Maintainer: 'Shivaram Venkataraman <sh...@cs.berkeley.edu>'
> Insufficient package version (submitted: 2.0.3, existing: 2.1.2)
> Unknown, possibly mis-spelled, fields in DESCRIPTION:
>   'RoxygenNote'
> WARNING: There was 1 warning.
> NOTE: There were 2 notes.
> We have seen this in branch-1.6, branch-2.0, and this would be a problem for branch-2.1 after we ship 2.2.1.
> The root cause of the issue is in the package version check in CRAN check. After the SparkR package version 2.1.2 (is first) published, any older version is failing the version check. As far as we know, there is no way to skip this version check.
> Also, there is previously a NOTE on new maintainer. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org