You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cran-comments.md
+19-15Lines changed: 19 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
6
6
## R CMD check results
7
7
8
-
There were no ERRORs or WARNINGs. I see one NOTE:
8
+
There were no ERRORs or WARNINGs. I see two NOTEs:
9
9
10
10
* Found the following (possibly) invalid URLs:
11
11
URL: http://fueleconomy.gov
@@ -16,24 +16,28 @@ There were no ERRORs or WARNINGs. I see one NOTE:
16
16
`curl http://fueleconomy.gov` works, but `curl -I http://fueleconomy.gov`
17
17
(which sends a HEAD request) does not.
18
18
19
+
* checking DESCRIPTION meta-information ... NOTE
20
+
Authors@R field gives persons with non-standard roles:
21
+
RStudio [cph, fnd]: fnd
22
+
23
+
I would rely like to capture the signficant funders in the authors list
24
+
so that can be correctly acknowledged.
25
+
19
26
## Reverse dependencies
20
27
21
28
* I ran `R CMD check` on 954 all reverse dependencies
22
29
(summary at https://github.com/hadley/ggplot2/blob/master/revdep/).
23
30
24
31
* Maintainers with NOTEs, WARNINGs, or ERRORS were notified on Oct 6,
25
-
Oct 6, and again today.
32
+
Oct 25, and again today.
26
33
27
34
* There are a lot of WARNINGS/ERRORs, but I've carefully reviewed them
28
35
all and as far as I can tell they are either deliberate changes to
29
36
the ggplot2 API, or unrelated problems. I'm sorry there are so many -
30
37
I don't know how to better encourage package authors to submit
31
-
updates. Every maintainer has been personally emailed at least twice.
32
-
33
-
* I given a more detailed breakdown of ERRORs/WARNINGs
34
-
(but not NOTEs below). Please let me know if there's anything else I
35
-
can do to make this more helpful.
36
-
38
+
updates. Every maintainer has been personally emailed at least twice
39
+
before today.
40
+
37
41
### ggproto mistake
38
42
39
43
I unfortunately made an implementation error in ggproto (the OO system that ggplot2 uses) that inadvertently introduced a build-time dependency on ggplot2. I've fixed the problem and added a clear error message, but to fix a number of downstream failures will require a rebuild of the following packages against the new version of ggplot2:
@@ -67,14 +71,14 @@ This problem affects the following downstream packgaes:
67
71
68
72
### ggplot2 changes
69
73
70
-
Need dev version of plotly: the maintainer is planning on submitting ASAP.
74
+
Need dev version of plotly: the maintainer is planning on submitting ASAP:
Copy file name to clipboardExpand all lines: revdep/email.md
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Hi,
2
2
3
-
This is an automated email to let you know about the upcoming release of {{{ my_package }}}, which will be submitted to CRAN next week. I'm aiming for {{{ date }}}, but that date may move backwards if significant problems are uncovered. To check for potential problems, I ran `R CMD check` on your package {{{your_package}}} ({{{your_version}}}).
3
+
This is an automated email to let you know that I have submitted {{{ my_package }}}to cran today {{{ date }}}. To check for potential problems, I ran `R CMD check` on your package {{{your_package}}} ({{{your_version}}}).
4
4
5
5
I found: {{{your_summary}}}.
6
6
@@ -9,8 +9,6 @@ I found: {{{your_summary}}}.
9
9
10
10
If I got an ERROR because I couldn't install your package (or one of it's dependencies), my apologies. Unfortunately I don't have the time to diagnose installation failures so you'll need to run the check yourself.
11
11
12
-
Compared to the last set of checks, there is one big change: I discovered a major issue with ggproto which made it unexpectedly fragile. I have fixed the bug, but any package that provides an extension will need to be rebuilt. I will ask CRAN to do this for all packages on CRAN, but when checking your own package you will need to do it yourself.
13
-
14
12
Otherwise, please determine if this is a problem with my code or your code. If you think it's a problem with {{ my_package}}, please file an issue on github that attempts to recreate the problem with as little code as possible. If it's a problem with your code, please prepare an updated package for CRAN as soon as possible. The ERRORs and WARNINGs might not be caused by the update to {{{my_package}}}, but it really makes life easier (for both me and CRAN) if you also fix any other problems that may have accumulated over time. Please also try to minimise the NOTEs. It's not essential you do this, but the fewer the false positives the more likely we are to detect a real problem with your package.
15
13
16
14
To get the development version of {{{ my_package }}} so you can run the checks yourself, you can run:
0 commit comments