[R-pkg-devel] Problem with "additional repository".

I have submitted a new package to CRAN, and this package has been
knocked back on the basis of a NOTE:
* checking package dependencies ... NOTE
Package suggested but not available for checking: 'ionChannelData'
This suggested package consists of data sets, the size of which is too
large to satisfy CRAN's constraints. I put this package in a repository
on github, from which it can be accessed by users.

My DESCRIPTION file contains the line:
Additional_repositories: https://rolfturner.r-universe.dev
The given URL seems to work, in that users can indeed load the
ionChannelData package via the command
install.packages("ionChannelData",repos="https://rolfturner.r-universe.dev")
I was under the impression that this was all that I needed to do.  The
CRAN checking process acknowledges the existence of the repository in
question:
Suggests or Enhances not in mainstream repositories:
  ionChannelData
Availability using Additional_repositories specification:
  ionChannelData   yes   https://rolfturner.r-universe.dev
So CRAN knows about this repository.  Why can it not make use of it?

What can/should I do to resolve this problem?

I guess I could simply *not* Suggest ionChannelData.  But what then, is
the point of the option of including an Additional_repositories field in
the DESCRIPTION file?

cheers,

Rolf Turner
Honorary Research Fellow
Department of Statistics
University of Auckland
Stats. Dep't. (secretaries) phone:
         +64-9-373-7599 ext. 89622
Home phone: +64-9-480-4619
The packages in additional repositories are not installed on the CRAN
checking machines. The NOTE is expected, but it's not a warning, so your
package should still be allowed to upload to CRAN. You should not remove
ionChannelData from Suggests because then the reference to that package in
your documentation will become a WARNING and your package will not be
uploaded to CRAN.

I have submitted a new package to CRAN, and this package has been
knocked back on the basis of a NOTE:

* checking package dependencies ... NOTE
Package suggested but not available for checking: 'ionChannelData'
This suggested package consists of data sets, the size of which is too
large to satisfy CRAN's constraints. I put this package in a repository
on github, from which it can be accessed by users.

My DESCRIPTION file contains the line:

Additional_repositories: https://rolfturner.r-universe.dev
The given URL seems to work, in that users can indeed load the
ionChannelData package via the command

install.packages("ionChannelData",repos="
https://rolfturner.r-universe.dev")

I was under the impression that this was all that I needed to do.  The
CRAN checking process acknowledges the existence of the repository in
question:

Suggests or Enhances not in mainstream repositories:
  ionChannelData
Availability using Additional_repositories specification:
  ionChannelData   yes   https://rolfturner.r-universe.dev
So CRAN knows about this repository.  Why can it not make use of it?

What can/should I do to resolve this problem?

I guess I could simply *not* Suggest ionChannelData.  But what then, is
the point of the option of including an Additional_repositories field in
the DESCRIPTION file?

cheers,

Rolf Turner

--
Honorary Research Fellow
Department of Statistics
University of Auckland
Stats. Dep't. (secretaries) phone:
         +64-9-373-7599 ext. 89622
Home phone: +64-9-480-4619

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

I have submitted a new package to CRAN, and this package has been
knocked back on the basis of a NOTE:

* checking package dependencies ... NOTE
Package suggested but not available for checking: 'ionChannelData'
This suggested package consists of data sets, the size of which is too
large to satisfy CRAN's constraints. I put this package in a repository
on github, from which it can be accessed by users.

My DESCRIPTION file contains the line:

Additional_repositories: https://rolfturner.r-universe.dev

Is that web site set up as a repository?  My impression was that it 
needed to be, so people could do

   install.packages("ionChannelData", repos = 
"https://rolfturner.r-universe.dev")

You can use the "drat" package to set up a tiny repository quickly.

Duncan
The given URL seems to work, in that users can indeed load the
ionChannelData package via the command

install.packages("ionChannelData",repos="https://rolfturner.r-universe.dev")
I was under the impression that this was all that I needed to do.  The
CRAN checking process acknowledges the existence of the repository in
question:

Suggests or Enhances not in mainstream repositories:
   ionChannelData
Availability using Additional_repositories specification:
   ionChannelData   yes   https://rolfturner.r-universe.dev
So CRAN knows about this repository.  Why can it not make use of it?

What can/should I do to resolve this problem?

I guess I could simply *not* Suggest ionChannelData.  But what then, is
the point of the option of including an Additional_repositories field in
the DESCRIPTION file?

cheers,

Rolf Turner

Whoops, I just read the next line.  Sorry!
I have submitted a new package to CRAN, and this package has been
knocked back on the basis of a NOTE:

* checking package dependencies ... NOTE
Package suggested but not available for checking: 'ionChannelData'
This suggested package consists of data sets, the size of which is too
large to satisfy CRAN's constraints. I put this package in a repository
on github, from which it can be accessed by users.

My DESCRIPTION file contains the line:

Additional_repositories: https://rolfturner.r-universe.dev
The given URL seems to work, in that users can indeed load the
ionChannelData package via the command

install.packages("ionChannelData",repos="https://rolfturner.r-universe.dev")
I was under the impression that this was all that I needed to do.  The
CRAN checking process acknowledges the existence of the repository in
question:

Suggests or Enhances not in mainstream repositories:
   ionChannelData
Availability using Additional_repositories specification:
   ionChannelData   yes   https://rolfturner.r-universe.dev
So CRAN knows about this repository.  Why can it not make use of it?

What can/should I do to resolve this problem?

I guess I could simply *not* Suggest ionChannelData.  But what then, is
the point of the option of including an Additional_repositories field in
the DESCRIPTION file?

cheers,

Rolf Turner

Certainly there was more in the output that caused rejection as the 
stuff you describe below seems to be fine.
I do not know which package this refers to, so cannot easily look.

Best,
Uwe
Whoops, I just read the next line.? Sorry!

On 15/10/2023 9:34 p.m., Rolf Turner wrote:
I have submitted a new package to CRAN, and this package has been
knocked back on the basis of a NOTE:

* checking package dependencies ... NOTE
Package suggested but not available for checking: 'ionChannelData'
This suggested package consists of data sets, the size of which is too
large to satisfy CRAN's constraints. I put this package in a repository
on github, from which it can be accessed by users.

My DESCRIPTION file contains the line:

Additional_repositories: https://rolfturner.r-universe.dev
The given URL seems to work, in that users can indeed load the
ionChannelData package via the command

install.packages("ionChannelData",repos="https://rolfturner.r-universe.dev")
I was under the impression that this was all that I needed to do.? The
CRAN checking process acknowledges the existence of the repository in
question:

Suggests or Enhances not in mainstream repositories:
?? ionChannelData
Availability using Additional_repositories specification:
?? ionChannelData?? yes?? https://rolfturner.r-universe.dev
So CRAN knows about this repository.? Why can it not make use of it?

What can/should I do to resolve this problem?

I guess I could simply *not* Suggest ionChannelData.? But what then, is
the point of the option of including an Additional_repositories field in
the DESCRIPTION file?

cheers,

Rolf Turner

______________________________________________
R-package-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
On Mon, 16 Oct 2023 17:08:28 +0200

I do not know which package this refers to, so cannot easily look.
This seems to be about the eglhmm package. It seems to pass --as-cran
checks on my machine, but I know it's not the full set of checks
performed for new packages.
Best regards,
Ivan
It was 0.0-20 that had another issue now explained privately. 0.0-21 
passes cleanly.

Best,
Uwe
On Mon, 16 Oct 2023 17:08:28 +0200
Uwe Ligges <ligges at statistik.tu-dortmund.de> wrote:

I do not know which package this refers to, so cannot easily look.
This seems to be about the eglhmm package. It seems to pass --as-cran
checks on my machine, but I know it's not the full set of checks
performed for new packages.