Dear team, I have submitted the package GreymodelsPackage_1.0.tar.gz to CRAN and it's a shiny app. However, I received the following * using log directory 'd:/RCompile/CRANincoming/R-devel/GreymodelsPackage.Rcheck' * using R Under development (unstable) (2022-09-25 r82916 ucrt) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: UTF-8 * checking for file 'GreymodelsPackage/DESCRIPTION' ... OK * checking extension type ... ERROR Extensions with Type 'Shiny application' cannot be checked. * DONE Status: 1 ERROR I am not sure how to fix the problems and I would appreciate your help on how to resolve this issue. Thanks and regards, Havisha Jahajeeah
[R-pkg-devel] Help - Shiny app on CRAN
9 messages · Ivan Krylov, Uwe Ligges, Jahajeeah, Havisha +1 more
? Mon, 26 Sep 2022 19:14:04 +0400 "Jahajeeah, Havisha" <hjahajeeah at utm.ac.mu> ?????:
* checking extension type ... ERROR Extensions with Type 'Shiny application' cannot be checked.
Since you're writing a package, you can either specify Type: Package in the DESCRIPTION file, or omit the field entirely: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Package-types
Best regards, Ivan
On 26.09.2022 17:14, Jahajeeah, Havisha wrote:
Dear team, I have submitted the package GreymodelsPackage_1.0.tar.gz to CRAN and it's a shiny app. However, I received the following * using log directory 'd:/RCompile/CRANincoming/R-devel/GreymodelsPackage.Rcheck' * using R Under development (unstable) (2022-09-25 r82916 ucrt) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: UTF-8 * checking for file 'GreymodelsPackage/DESCRIPTION' ... OK * checking extension type ... ERROR Extensions with Type 'Shiny application' cannot be checked.
You apparently declared it as Type "Shiny application" rather than "Package" in the DESCRIPTION field? Simply omit the Type field or decalre it as Package. Best, Uwe Ligges
* DONE Status: 1 ERROR I am not sure how to fix the problems and I would appreciate your help on how to resolve this issue. Thanks and regards, Havisha Jahajeeah [[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Dear team, My second attempt at submitting the package GreymodelsPackage_1.0.tar.gz to CRAN. Grateful if you could please assist me with the following issues: CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm' dbgm12: no visible global function definition fo lotegm: no visible global function definition for 'geom_point' plotegm: no visible global function definition for 'aes' plotegm: no visible binding for global variable 'x' plotegm: no visible binding for global variable 'y' plotegm: no visible global function definition for 'geom_line' plotegm: no visible global function definition for 'scale_color_manual' plotegm: no visible global function definition for 'ggplot Also, Objects in \usage without \alias in documentation object 'Multivariable': 'dbgm12' Objects in \usage without \alias in documentation object 'Plots': 'plots' Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0) Bad \usage lines found in documentation object 'CombinedModels': ngbm11(x0), ggvm11(x0), tfdgm11(x0) Thanks and Regards, Havisha Jahajeeah On Mon, Sep 26, 2022 at 7:14 PM Jahajeeah, Havisha <hjahajeeah at utm.ac.mu> wrote:
Dear team, I have submitted the package GreymodelsPackage_1.0.tar.gz to CRAN and it's a shiny app. However, I received the following * using log directory 'd:/RCompile/CRANincoming/R-devel/GreymodelsPackage.Rcheck' * using R Under development (unstable) (2022-09-25 r82916 ucrt) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: UTF-8 * checking for file 'GreymodelsPackage/DESCRIPTION' ... OK * checking extension type ... ERROR Extensions with Type 'Shiny application' cannot be checked. * DONE Status: 1 ERROR I am not sure how to fix the problems and I would appreciate your help on how to resolve this issue. Thanks and regards, Havisha Jahajeeah
Hello, are you aware of https://win-builder.r-project.org/? It'll allow you to validate that your package passes all the requirements before submitting it to CRAN. My $.02 /Henrik On Mon, Sep 26, 2022 at 11:23 AM Jahajeeah, Havisha
<hjahajeeah at utm.ac.mu> wrote:
Dear team, My second attempt at submitting the package GreymodelsPackage_1.0.tar.gz to CRAN. Grateful if you could please assist me with the following issues: CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm' dbgm12: no visible global function definition fo lotegm: no visible global function definition for 'geom_point' plotegm: no visible global function definition for 'aes' plotegm: no visible binding for global variable 'x' plotegm: no visible binding for global variable 'y' plotegm: no visible global function definition for 'geom_line' plotegm: no visible global function definition for 'scale_color_manual' plotegm: no visible global function definition for 'ggplot Also, Objects in \usage without \alias in documentation object 'Multivariable': 'dbgm12' Objects in \usage without \alias in documentation object 'Plots': 'plots' Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0) Bad \usage lines found in documentation object 'CombinedModels': ngbm11(x0), ggvm11(x0), tfdgm11(x0) Thanks and Regards, Havisha Jahajeeah On Mon, Sep 26, 2022 at 7:14 PM Jahajeeah, Havisha <hjahajeeah at utm.ac.mu> wrote:
Dear team, I have submitted the package GreymodelsPackage_1.0.tar.gz to CRAN and it's a shiny app. However, I received the following * using log directory 'd:/RCompile/CRANincoming/R-devel/GreymodelsPackage.Rcheck' * using R Under development (unstable) (2022-09-25 r82916 ucrt) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: UTF-8 * checking for file 'GreymodelsPackage/DESCRIPTION' ... OK * checking extension type ... ERROR Extensions with Type 'Shiny application' cannot be checked. * DONE Status: 1 ERROR I am not sure how to fix the problems and I would appreciate your help on how to resolve this issue. Thanks and regards, Havisha Jahajeeah
[[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
It might be easier to help you if you show us your package by publishing the source code somewhere. On Mon, 26 Sep 2022 22:22:48 +0400
"Jahajeeah, Havisha" <hjahajeeah at utm.ac.mu> wrote:
CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm'
It sounds like your NAMESPACE file isn't properly set up to import the functions you're using. For the package to work correctly, it should contain lines importFrom(stats, qt) importFrom(utils, tail) importFrom(shiny, shinyApp) and so on for every function you use that's not in base. See Writing R Extensions section 1.5: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Specifying-imports-and-exports
Objects in \usage without \alias in documentation object 'Plots': 'plots'
A single Rd file can describe multiple functions, but they should be
both mentioned in the \usage{} section and as an \alias{}. Do you
export two different objects (functions?) named "plots" and "Plots", or
is one of those an error?
Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0)
The \usage{} section must exactly match the definition of the function
(but you can omit default values of the arguments if they're too large
and not very informative), without any other words or punctuation.
Once your package passes the automated tests, a human volunteer will go
over your package to make sure that it fits the CRAN policy (not
providing a link because you've already read it when you submitted the
package), which includes having good documentation for every function
you export.
See Writing R Extensions section 2 for more information on this:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Writing-R-documentation-files
I've also noticed that you're showing us an error message from the CRAN
pre-test infrastructure. You can get these errors (and start fixing
them) faster without spending time waiting for the test result by
running R CMD check --as-cran your_package.tar.gz on your own machine.
Best regards, Ivan
2 days later
Dear team, I am having trouble submitting my package to CRAN because the link https://win-builder.r-project.org/ is not accessible. Please advise. Thank you Havisha Jahajeeah
On Mon, Sep 26, 2022 at 11:17 PM Ivan Krylov <krylov.r00t at gmail.com> wrote:
It might be easier to help you if you show us your package by publishing the source code somewhere. On Mon, 26 Sep 2022 22:22:48 +0400 "Jahajeeah, Havisha" <hjahajeeah at utm.ac.mu> wrote:
CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm'
It sounds like your NAMESPACE file isn't properly set up to import the functions you're using. For the package to work correctly, it should contain lines importFrom(stats, qt) importFrom(utils, tail) importFrom(shiny, shinyApp) and so on for every function you use that's not in base. See Writing R Extensions section 1.5: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Specifying-imports-and-exports
Objects in \usage without \alias in documentation object 'Plots': 'plots'
A single Rd file can describe multiple functions, but they should be
both mentioned in the \usage{} section and as an \alias{}. Do you
export two different objects (functions?) named "plots" and "Plots", or
is one of those an error?
Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0)
The \usage{} section must exactly match the definition of the function
(but you can omit default values of the arguments if they're too large
and not very informative), without any other words or punctuation.
Once your package passes the automated tests, a human volunteer will go
over your package to make sure that it fits the CRAN policy (not
providing a link because you've already read it when you submitted the
package), which includes having good documentation for every function
you export.
See Writing R Extensions section 2 for more information on this:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Writing-R-documentation-files
I've also noticed that you're showing us an error message from the CRAN
pre-test infrastructure. You can get these errors (and start fixing
them) faster without spending time waiting for the test result by
running R CMD check --as-cran your_package.tar.gz on your own machine.
--
Best regards,
Ivan
Hi, it's not just you; the win-builder server is down for all of us (e.g. https://downforeveryoneorjustme.com/win-builder.r-project.org?proto=https). Uwe Ligges, who maintains this, mentioned (in another thread somewhere) that there were networking issues at his university that are being worked on. FWIW, this is a rare event - the win-builder and CRAN incoming services/servers have a quite solid track record. /Henrik
On Wed, Sep 28, 2022 at 2:07 PM Jahajeeah, Havisha <hjahajeeah at utm.ac.mu> wrote:
Dear team, I am having trouble submitting my package to CRAN because the link https://win-builder.r-project.org/ is not accessible. Please advise. Thank you Havisha Jahajeeah On Mon, Sep 26, 2022 at 11:17 PM Ivan Krylov <krylov.r00t at gmail.com> wrote:
It might be easier to help you if you show us your package by publishing the source code somewhere. On Mon, 26 Sep 2022 22:22:48 +0400 "Jahajeeah, Havisha" <hjahajeeah at utm.ac.mu> wrote:
CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm'
It sounds like your NAMESPACE file isn't properly set up to import the functions you're using. For the package to work correctly, it should contain lines importFrom(stats, qt) importFrom(utils, tail) importFrom(shiny, shinyApp) and so on for every function you use that's not in base. See Writing R Extensions section 1.5: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Specifying-imports-and-exports
Objects in \usage without \alias in documentation object 'Plots': 'plots'
A single Rd file can describe multiple functions, but they should be
both mentioned in the \usage{} section and as an \alias{}. Do you
export two different objects (functions?) named "plots" and "Plots", or
is one of those an error?
Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0)
The \usage{} section must exactly match the definition of the function
(but you can omit default values of the arguments if they're too large
and not very informative), without any other words or punctuation.
Once your package passes the automated tests, a human volunteer will go
over your package to make sure that it fits the CRAN policy (not
providing a link because you've already read it when you submitted the
package), which includes having good documentation for every function
you export.
See Writing R Extensions section 2 for more information on this:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Writing-R-documentation-files
I've also noticed that you're showing us an error message from the CRAN
pre-test infrastructure. You can get these errors (and start fixing
them) faster without spending time waiting for the test result by
running R CMD check --as-cran your_package.tar.gz on your own machine.
--
Best regards,
Ivan
[[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Hello, Thank you for the clarification. Havisha On Thu, 29 Sep 2022 at 01:24, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote:
Hi, it's not just you; the win-builder server is down for all of us (e.g. https://downforeveryoneorjustme.com/win-builder.r-project.org?proto=https ). Uwe Ligges, who maintains this, mentioned (in another thread somewhere) that there were networking issues at his university that are being worked on. FWIW, this is a rare event - the win-builder and CRAN incoming services/servers have a quite solid track record. /Henrik On Wed, Sep 28, 2022 at 2:07 PM Jahajeeah, Havisha <hjahajeeah at utm.ac.mu> wrote:
Dear team, I am having trouble submitting my package to CRAN because the link https://win-builder.r-project.org/ is not accessible. Please advise. Thank you Havisha Jahajeeah On Mon, Sep 26, 2022 at 11:17 PM Ivan Krylov <krylov.r00t at gmail.com>
wrote:
It might be easier to help you if you show us your package by publishing the source code somewhere. On Mon, 26 Sep 2022 22:22:48 +0400 "Jahajeeah, Havisha" <hjahajeeah at utm.ac.mu> wrote:
CIvalue2: no visible global function definition for 'qt' andgm11: no visible binding for global variable 'ParticleSwarm' andgm11: no visible global function definition for 'tail' app: no visible global function definition for 'shinyApp' dbgm12: no visible binding for global variable 'ParticleSwarm'
It sounds like your NAMESPACE file isn't properly set up to import the functions you're using. For the package to work correctly, it should contain lines importFrom(stats, qt) importFrom(utils, tail) importFrom(shiny, shinyApp) and so on for every function you use that's not in base. See Writing R Extensions section 1.5:
Objects in \usage without \alias in documentation object 'Plots': 'plots'
A single Rd file can describe multiple functions, but they should be
both mentioned in the \usage{} section and as an \alias{}. Do you
export two different objects (functions?) named "plots" and "Plots", or
is one of those an error?
Bad \usage lines found in documentation object 'BackgroundValues': gm11(x0), epgm11(x0), tbgm11(x0), igm11(x0), gm114(x0)
The \usage{} section must exactly match the definition of the function
(but you can omit default values of the arguments if they're too large
and not very informative), without any other words or punctuation.
Once your package passes the automated tests, a human volunteer will go
over your package to make sure that it fits the CRAN policy (not
providing a link because you've already read it when you submitted the
package), which includes having good documentation for every function
you export.
See Writing R Extensions section 2 for more information on this:
I've also noticed that you're showing us an error message from the CRAN pre-test infrastructure. You can get these errors (and start fixing them) faster without spending time waiting for the test result by running R CMD check --as-cran your_package.tar.gz on your own machine. -- Best regards, Ivan
[[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel