Re: [R-pkg-devel] Warnings and notes while building package with nimble

2025-04-07 Thread Uwe Ligges



On 05.04.2025 00:29, Halder,Aritra wrote:

Hi,

I am trying to submit a package to CRAN built using nimble. It generates 
warnings like so:


Which package?



: no visible global function definition for  'nimDim'


and you have not forgot to import nlmDim()?

Best,
Uwe Ligges







and fails automatic checks by CRAN. Any help is appreciated.

Thanks and regards,

Aritra

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] URLs in DESCRIPTION file

2025-04-07 Thread Kevin R. Coombes

Hi,

I am systematically going through the packages that I maintain on CRAN 
to clean up some administrative details. Specifically, I am (1) changing 
all DESCRIPTION files to use Authirs@R, (2) updating the links in man 
files to include package anchors, and (3) making sure that the output of 
calls to summary in test scripts don't break (i.e., mismatch the saved 
test output) in the 4.5.0 release candidate.


Not surprisingly, this process also finds other issues. Right now,I am 
looking at the package BimodalIndex. The version currently on CRAN (v. 
1.1.9) includes the following URL:

    https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2730180/
On first checking the package, I get informed that this URL has 
"permanently moved" to:

    https://pmc.ncbi.nlm.nih.gov/articles/PMC2730180/

The fix seems simple, so I edited the DESCRIPTION file to use the new 
URL instead of the old one. Then I submitted the newly built version 
(1.1.11) to both the current release and the development release at 
winbuilder before submitting the update to CRAN.  R version 4.4.3 comes 
back with a 00check.log that is absolutely "OK". No errors, warnings, or 
notes. But version R 4.5.0 RC comes back with;

    (possibly) invalid URL. Status: 403  Message: Forbidden
I copied the URL as reported in the error message, pasted it into my 
browser, and it worked just fine.


Can I assume that this is just something weird about the corresponding 
winbuilder server at the moment, and go ahead and submit the package? Or 
is there some mysterious change in R 4.5 lurking somewhere that I need 
to deal with?


Thanks,
   Kevin

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


Re: [R-pkg-devel] URLs in DESCRIPTION file

2025-04-07 Thread Ivan Krylov via R-package-devel
В Mon, 7 Apr 2025 11:10:21 -0400
"Kevin R. Coombes"  пишет:

> But version R 4.5.0 RC comes back with;
>      (possibly) invalid URL. Status: 403  Message: Forbidden
> I copied the URL as reported in the error message, pasted it into my 
> browser, and it worked just fine.
> 
> Can I assume that this is just something weird about the
> corresponding winbuilder server at the moment, and go ahead and
> submit the package?

This is a false positive. R CMD check sends automated requests to all
URLs it finds in the package. PubMed "protects" itself from automated
requests and returns an error code:

$ curl -I https://pmc.ncbi.nlm.nih.gov/articles/PMC2730180/
HTTP/2 403
content-length: 134
content-type: text/html; charset=UTF-8
date: Mon, 07 Apr 2025 15:14:59 GMT
alt-svc: clear

Using a browser instead results in subtly different behaviour visible
to the server, so the page loads successfully when clicking a link.

I see you're already linking to the article's DOI, 10.4137/cin.s2846,
and the article is not paywalled. Is it an option to remove the PubMed
link? There is code that is intended to recommend to only use the DOI,
but currently doesn't include a pattern for the new PubMed URLs:

if(length(y) &&
 any(ind <-
   (grepl(re_or(c("^https://pubmed.ncbi.nlm.nih.gov/[0-9]+";,
  "^https://www.ncbi.nlm.nih.gov/pmc/articles/PMC[0-9]+/$";,
  "^https://academic.oup.com/.*(/[0-9]*){4}$",
  "^https://www.sciencedirect.com/science/article";)),
y$URL {
## 
## Ideally we would complain about such URLs in general
## and not only when the URL checks were not OK.
paste(c("Please use DOIs for the following publisher URLs:",
paste0("  ", y$URL[ind])),
  collapse = "\n")
## 
}

If you don't want to remove the PubMed link, you can explain the
"possibly invalid URL" as a false positive in the submission comment.

-- 
Best regards,
Ivan

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


Re: [R-pkg-devel] URLs in DESCRIPTION file

2025-04-07 Thread Kevin R. Coombes
Thanks. That's what I thought (though I was somewhat confused by the 
different behaviors of winbuilder on the current and development 
versions). I think the original DESCRIPTION file (from 2017?) just had 
the URL. Some time after that, CRAN asked for the inclusion of the DOI, 
but they didn't say to get rid of the URL. The code itself hasn't been 
touched since at least 2019 (since it still works exactly the way it is 
supposed to.)


And, becauseI have been both finding and losing things on the Internet 
for several decades, I am not particularly confident that the DOI is 
going to have a significantly longer stable lifetime than the NCBI URL. 
So, for now at least, I think I will leave them both.


Best,
   Kevin

On 4/7/2025 11:35 AM, Ivan Krylov wrote:

В Mon, 7 Apr 2025 11:10:21 -0400
"Kevin R. Coombes"  пишет:


But version R 4.5.0 RC comes back with;
      (possibly) invalid URL. Status: 403  Message: Forbidden
I copied the URL as reported in the error message, pasted it into my
browser, and it worked just fine.

Can I assume that this is just something weird about the
corresponding winbuilder server at the moment, and go ahead and
submit the package?

This is a false positive. R CMD check sends automated requests to all
URLs it finds in the package. PubMed "protects" itself from automated
requests and returns an error code:

$ curl -I https://pmc.ncbi.nlm.nih.gov/articles/PMC2730180/
HTTP/2 403
content-length: 134
content-type: text/html; charset=UTF-8
date: Mon, 07 Apr 2025 15:14:59 GMT
alt-svc: clear

Using a browser instead results in subtly different behaviour visible
to the server, so the page loads successfully when clicking a link.

I see you're already linking to the article's DOI, 10.4137/cin.s2846,
and the article is not paywalled. Is it an option to remove the PubMed
link? There is code that is intended to recommend to only use the DOI,
but currently doesn't include a pattern for the new PubMed URLs:

if(length(y) &&
  any(ind <-
(grepl(re_or(c("^https://pubmed.ncbi.nlm.nih.gov/[0-9]+";,
   "^https://www.ncbi.nlm.nih.gov/pmc/articles/PMC[0-9]+/$";,
   "^https://academic.oup.com/.*(/[0-9]*){4}$",
   "^https://www.sciencedirect.com/science/article";)),
 y$URL {
 ## 
 ## Ideally we would complain about such URLs in general
 ## and not only when the URL checks were not OK.
 paste(c("Please use DOIs for the following publisher URLs:",
 paste0("  ", y$URL[ind])),
   collapse = "\n")
 ## 
}

If you don't want to remove the PubMed link, you can explain the
"possibly invalid URL" as a false positive in the submission comment.



__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel