Re: [R-pkg-devel] Assistance Needed for Resolving Submission Issues with openaistream Package

2024-01-22 Thread Lluís Revilla 
Hi Li Gen,

This NOTE is part of the new checks on CRAN to comply with its policy.
The error message was introduced in c85587 (2023/11/22), when
incorporating this suggestion
https://bugs.r-project.org/show_bug.cgi?id=18611.
You can see the changes and checks in the browser here:
https://github.com/r-devel/r-svn/commit/c82305de4adc1a8ee01aaf3b4c84bd55721e77fc)
But the solution is what Ivan already wrote: simply provide a file
LICENSE that can be read with read.dcf with those two fields.

Best regards,

Lluís


On Mon, 22 Jan 2024 at 15:19, Ivan Krylov via R-package-devel
 wrote:
>
> Hello Li Gen and welcome to R-package-devel!
>
> В Mon, 22 Jan 2024 17:50:33 +0800
>  пишет:
>
> > The specific areas of concern are:License Information: There's a note
> > indicating that the license stub is an "invalid DCF". I've used 'MIT
> > + file LICENSE' as the licensing terms. I would appreciate guidance
> > on how to correctly format this section to meet the DCF standards.
>
> Leave just the following lines in the LICENSE file, as it currently is
> on CRAN [*]:
>
> YEAR: 2023
> COPYRIGHT HOLDER: openaistream authors
>
> Why would you like to change it? CRAN doesn't want packages to provide
> yet another copy of the MIT license inside the tarball. The text of the
> MIT license is always available in an R install at
> file.path(R.home('share'), 'licenses', 'MIT').
>
> If you need a copy of the MIT license inside your GitHub repository,
> store it elsewhere (e.g. LICENSE.md) and list it in .Rbuildignore [**].
>
> Since you composed your e-mail in HTML and left your mailer to generate
> a plain text equivalent, we only got the latter, somewhat mangled:
> https://stat.ethz.ch/pipermail/r-package-devel/2024q1/010356.html
>
> Please compose your messages to R mailing lists in plain text.
>
> --
> Best regards,
> Ivan
>
> [*]
> https://cran.r-project.org/web/packages/openaistream/LICENSE
>
> [**]
> https://cran.r-project.org/doc/manuals/R-exts.html#Building-package-tarballs
>
> __
> 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

Re: [R-pkg-devel] Assistance Needed for Resolving Submission Issues with openaistream Package

2024-01-22 Thread Ivan Krylov via R-package-devel 
Hello Li Gen and welcome to R-package-devel!

В Mon, 22 Jan 2024 17:50:33 +0800
 пишет:

> The specific areas of concern are:License Information: There's a note
> indicating that the license stub is an "invalid DCF". I've used 'MIT
> + file LICENSE' as the licensing terms. I would appreciate guidance
> on how to correctly format this section to meet the DCF standards.

Leave just the following lines in the LICENSE file, as it currently is
on CRAN [*]:

YEAR: 2023
COPYRIGHT HOLDER: openaistream authors

Why would you like to change it? CRAN doesn't want packages to provide
yet another copy of the MIT license inside the tarball. The text of the
MIT license is always available in an R install at
file.path(R.home('share'), 'licenses', 'MIT').

If you need a copy of the MIT license inside your GitHub repository,
store it elsewhere (e.g. LICENSE.md) and list it in .Rbuildignore [**].

Since you composed your e-mail in HTML and left your mailer to generate
a plain text equivalent, we only got the latter, somewhat mangled:
https://stat.ethz.ch/pipermail/r-package-devel/2024q1/010356.html

Please compose your messages to R mailing lists in plain text.

-- 
Best regards,
Ivan

[*]
https://cran.r-project.org/web/packages/openaistream/LICENSE

[**]
https://cran.r-project.org/doc/manuals/R-exts.html#Building-package-tarballs

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

[R-pkg-devel] Assistance Needed for Resolving Submission Issues with openaistream Package

2024-01-22 Thread libingfei 
Hi,I am writing to seek guidance regarding some challenges I've encountered 
while submitting my package, openaistream, to CRAN. I have recently received 
feedback from the CRAN team, and I'm looking for assistance to address the 
issues noted.The package in question aims to provide streaming capabilities for 
OpenAI API interactions and is based on the 'httr2' framework. While the last 
released version's CRAN status is marked as 'OK: 12', I have been advised to 
fix certain problems and resubmit a revised version.The specific areas of 
concern are:License Information: There's a note indicating that the license 
stub is an "invalid DCF". I've used 'MIT + file LICENSE' as the licensing 
terms. I would appreciate guidance on how to correctly format this section to 
meet the DCF standards.General Submission: I've been directed to win-builder 
pretest for more details. However, I'm finding it challenging to pinpoint the 
exact issues that need rectification. Any insights or suggestions on common pi
 tfalls or areas to focus on would be immensely helpful.I have thoroughly 
reviewed the provided links and documentation but would greatly benefit from 
the community's expertise and experience in addressing these specific concerns. 
If there are any resources, examples, or advice you can share, it would be 
greatly appreciated.Windows: 
Status:
 2 NOTEsDebian: 
Status:
 2 NOTEs
Best regards,Li Gen
Email: libingfei@sina.comGitHub: https://github.com/libingfei/openaistream
[[alternative HTML version deleted]]

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