Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission. Best, Tiago Olivoto
[R-pkg-devel] Time for CRAN response
10 messages · Tiago Olivoto, Uwe Ligges, Duncan Murdoch +2 more
On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission.
If it is not in incoming/, something went wrong. The most common thing to go wrong is that the maintainer didn't respond to the confirmation message. That message looks like this for a resubmission. I assume first time submissions have a similar message:
Dear Duncan Murdoch Someone has submitted the package rgl to CRAN. You are receiving this email to confirm the submission as the maintainer of this package. To confirm the submission to CRAN, follow or copy & paste the following link into your browser: ...
When you confirm submission, you'll get another message that looks like this:
[This was generated from CRAN.R-project.org/submit.html] The following package was uploaded to CRAN: =========================================== Package Information: Package: rgl Version: 0.100.26
> ... After that, it goes into a queue for checking, and usually within a few days you'll be told about problems with it or it will be accepted to CRAN. (Sometimes you'll be told very quickly, if the automated checks find a problem.) Duncan Murdoch
Thank you for the response. As far I remember, I've responded that message by following the link and selecting "I have read the CRAN policies and would like to submit this package to CRAN" and " I have checked the submission using R CMD check --as-cran and a current version of r-devel, as mandated by the CRAN Repository Policy. (You could do so using the win-builder service at https://win-builder.r-project.org)", and then clicking on "upload package to CRAN" These same steps were followed in the first submission, but at that time I received the following message that was not received in the last submission.
Dear maintainer, package metan_1.0.0.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days.
Should I try to re-submit it again? Best, Tiago Olivoto -----Mensagem original----- De: Duncan Murdoch <murdoch.duncan at gmail.com> Enviada em: domingo, 15 de dezembro de 2019 17:35 Para: tiagoolivoto at gmail.com; r-package-devel at r-project.org Assunto: Re: [R-pkg-devel] Time for CRAN response
On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission.
If it is not in incoming/, something went wrong. The most common thing to go wrong is that the maintainer didn't respond to the confirmation message. That message looks like this for a resubmission. I assume first time submissions have a similar message:
Dear Duncan Murdoch Someone has submitted the package rgl to CRAN. You are receiving this email to confirm the submission as the maintainer of this package. To confirm the submission to CRAN, follow or copy & paste the following link into your browser: ...
When you confirm submission, you'll get another message that looks like this:
[This was generated from CRAN.R-project.org/submit.html] The following package was uploaded to CRAN: =========================================== Package Information: Package: rgl Version: 0.100.26
> ... After that, it goes into a queue for checking, and usually within a few days you'll be told about problems with it or it will be accepted to CRAN. (Sometimes you'll be told very quickly, if the automated checks find a problem.) Duncan Murdoch
On 15/12/2019 4:57 p.m., Tiago Olivoto wrote:
Thank you for the response. As far I remember, I've responded that message by following the link and selecting "I have read the CRAN policies and would like to submit this package to CRAN" and " I have checked the submission using R CMD check --as-cran and a current version of r-devel, as mandated by the CRAN Repository Policy. (You could do so using the win-builder service at https://win-builder.r-project.org)", and then clicking on "upload package to CRAN" These same steps were followed in the first submission, but at that time I received the following message that was not received in the last submission.
Dear maintainer, package metan_1.0.0.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days.
Should I try to re-submit it again?
Probably. I'd wait 24 hours, to see if someone from CRAN replies with more information. Duncan Murdoch
Best, Tiago Olivoto -----Mensagem original----- De: Duncan Murdoch <murdoch.duncan at gmail.com> Enviada em: domingo, 15 de dezembro de 2019 17:35 Para: tiagoolivoto at gmail.com; r-package-devel at r-project.org Assunto: Re: [R-pkg-devel] Time for CRAN response On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission.
If it is not in incoming/, something went wrong. The most common thing to go wrong is that the maintainer didn't respond to the confirmation message. That message looks like this for a resubmission. I assume first time submissions have a similar message:
Dear Duncan Murdoch Someone has submitted the package rgl to CRAN. You are receiving this email to confirm the submission as the maintainer of this package. To confirm the submission to CRAN, follow or copy & paste the following link into your browser: ...
When you confirm submission, you'll get another message that looks like this:
[This was generated from CRAN.R-project.org/submit.html] The following package was uploaded to CRAN: =========================================== Package Information: Package: rgl Version: 0.100.26 > ...
After that, it goes into a queue for checking, and usually within a few days you'll be told about problems with it or it will be accepted to CRAN. (Sometimes you'll be told very quickly, if the automated checks find a problem.) Duncan Murdoch
On 15.12.2019 23:39, Duncan Murdoch wrote:
On 15/12/2019 4:57 p.m., Tiago Olivoto wrote:
Thank you for the response. As far I remember, I've responded that message by following the link and selecting "I have read the CRAN policies and would like to submit this package to CRAN" and " I have checked the submission using R CMD check --as-cran and a current version of r-devel, as mandated by the CRAN Repository Policy. (You could do so using the win-builder service at https://win-builder.r-project.org)", and then clicking on "upload package to CRAN" These same steps were followed in the first submission, but at that time I received the following message that was not received in the last submission.
Dear maintainer, package metan_1.0.0.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days.
Should I try to re-submit it again?
Probably.? I'd wait 24 hours, to see if someone from CRAN replies with more information.
Thanks, Duncan, here we got: 1. I did not spot a request for help from Nov 25 in the many messsages we receive. That one has now been answered. 2. I do not see a submission fom Nov 25. Can you simply resubmit and make sure you click on the confirmation link? Best, Uwe Ligges
Duncan Murdoch
Best, Tiago Olivoto -----Mensagem original----- De: Duncan Murdoch <murdoch.duncan at gmail.com> Enviada em: domingo, 15 de dezembro de 2019 17:35 Para: tiagoolivoto at gmail.com; r-package-devel at r-project.org Assunto: Re: [R-pkg-devel] Time for CRAN response On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission.
If it is not in incoming/, something went wrong.? The most common thing to go wrong is that the maintainer didn't respond to the confirmation message. That message looks like this for a resubmission.? I assume first time submissions have a similar message:
Dear Duncan Murdoch Someone has submitted the package rgl to CRAN. You are receiving this email to confirm the submission as the maintainer of this package. To confirm the submission to CRAN, follow or copy & paste the following link into your browser: ...
When you confirm submission, you'll get another message that looks like this:
[This was generated from CRAN.R-project.org/submit.html] The following package was uploaded to CRAN: =========================================== Package Information: Package: rgl Version: 0.100.26
? > ... After that, it goes into a queue for checking, and usually within a few days you'll be told about problems with it or it will be accepted to CRAN.? (Sometimes you'll be told very quickly, if the automated checks find a problem.) Duncan Murdoch
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Thanks, Duncan and Uwe, for the answers! I'll resubmit it as soon as possible. Best regards, Tiago Olivoto -- M.Sc. Tiago Olivoto Doutorando em Agronomia Departamento de Fitotecnia Universidade Federal de Santa Maria Av. Roraima, 1000, Camobi Santa Maria, RS, 97105-340 E-mail: tiagoolivoto at gmail.com Cel: +55 54 999187863 Research Gate Curr?culo Lattes -----Mensagem original----- De: Uwe Ligges <ligges at statistik.tu-dortmund.de> Enviada em: domingo, 15 de dezembro de 2019 22:27 Para: Duncan Murdoch <murdoch.duncan at gmail.com>; tiagoolivoto at gmail.com; r-package-devel at r-project.org Assunto: Re: [R-pkg-devel] RES: Time for CRAN response
On 15.12.2019 23:39, Duncan Murdoch wrote:
On 15/12/2019 4:57 p.m., Tiago Olivoto wrote:
Thank you for the response. As far I remember, I've responded that message by following the link and selecting "I have read the CRAN policies and would like to submit this package to CRAN" and " I have checked the submission using R CMD check --as-cran and a current version of r-devel, as mandated by the CRAN Repository Policy. (You could do so using the win-builder service at https://win-builder.r-project.org)", and then clicking on "upload package to CRAN" These same steps were followed in the first submission, but at that time I received the following message that was not received in the last submission.
Dear maintainer, package metan_1.0.0.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days.
Should I try to re-submit it again?
Probably. I'd wait 24 hours, to see if someone from CRAN replies with more information.
Thanks, Duncan, here we got: 1. I did not spot a request for help from Nov 25 in the many messsages we receive. That one has now been answered. 2. I do not see a submission fom Nov 25. Can you simply resubmit and make sure you click on the confirmation link? Best, Uwe Ligges
Duncan Murdoch
Best, Tiago Olivoto -----Mensagem original----- De: Duncan Murdoch <murdoch.duncan at gmail.com> Enviada em: domingo, 15 de dezembro de 2019 17:35 Para: tiagoolivoto at gmail.com; r-package-devel at r-project.org Assunto: Re: [R-pkg-devel] Time for CRAN response On 15/12/2019 1:29 p.m., Tiago Olivoto wrote:
Dear all, I've submitted my package 'metan' to CRAN for the first time a few weeks ago and received some suggestions to improve the code. After fixing some bugs, I've resubmitted it on November 25, but I still don't have any response and the package was not found in incoming/ dir on CRAN cran ftp site. Since it is my first experience, I would like to have an idea about how long the CRAN team usually decides about a package submission.
If it is not in incoming/, something went wrong. The most common thing to go wrong is that the maintainer didn't respond to the confirmation message. That message looks like this for a resubmission. I assume first time submissions have a similar message:
Dear Duncan Murdoch Someone has submitted the package rgl to CRAN. You are receiving this email to confirm the submission as the maintainer of this package. To confirm the submission to CRAN, follow or copy & paste the following link into your browser: ...
When you confirm submission, you'll get another message that looks like this:
[This was generated from CRAN.R-project.org/submit.html] The following package was uploaded to CRAN: =========================================== Package Information: Package: rgl Version: 0.100.26 > ...
After that, it goes into a queue for checking, and usually within a few days you'll be told about problems with it or it will be accepted to CRAN. (Sometimes you'll be told very quickly, if the automated checks find a problem.) Duncan Murdoch
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
2 days later
Dear List, Today I submitted a package to CRAN, and after correcting some NOTEs, I got the following automatic message: "package mypackage_0.1-2.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days. For technical reasons you may receive a second copy of this message when a team member triggers a new check." Could somebody give a short explanation about what type of checkings are made in this "manual inspection" ? Thak in advance for your help, Mauricio Mauricio Zambrano-Bigiarini, PhD ===================================== Department of Civil Engineering Faculty of Engineering and Sciences Universidad de La Frontera, Temuco, Chile http://hzambran.github.io/ ===================================== mailto : mauricio.zambrano at ufrontera.cl work-phone : +56 45 259 2812 ===================================== "Success is not final, failure is not fatal. It is the courage to continue that counts. (Winston Churchill) ===================================== Linux user #454569 -- Linux Mint user
La informaci?n contenida en este correo electr?nico y cualquier anexo o respuesta relacionada, puede contener datos e informaci?n confidencial y no puede ser usada o difundida por personas distintas a su(s) destinatario(s). Si usted no es el destinatario de esta comunicaci?n, le informamos que cualquier divulgaci?n, distribuci?n o copia de esta informaci?n constituye un delito conforme a la ley chilena. Si lo ha recibido por error, por favor borre el mensaje y todos sus anexos y notifique al remitente.
On 18/12/2019 5:01 p.m., Mauricio Zambrano-Bigiarini wrote:
Dear List, Today I submitted a package to CRAN, and after correcting some NOTEs, I got the following automatic message: "package mypackage_0.1-2.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days. For technical reasons you may receive a second copy of this message when a team member triggers a new check." Could somebody give a short explanation about what type of checkings are made in this "manual inspection" ?
Basically they're checking whether you are following the guidelines at https://cran.r-project.org/web/packages/policies.html. Not all of those things can be checked automatically, and many people claim to be following them when they actually are not. Duncan Murdoch
Thank you very much Duncan for the information. BTW, it is incredible to me how the quality control of packages submitted to CRAN has improved in the last decade. Now the automatic procedures are able to identify even "little" things (e.g., broken links, misspelled words, size of vignettes, etc). Thank you very much for all the effort and dedication of the CRAN Repository Maintainers. Kind regards, Mauricio ===================================== "Success is not final, failure is not fatal. It is the courage to continue that counts. (Winston Churchill) ===================================== Linux user #454569 -- Linux Mint user
On Wed, 18 Dec 2019 at 19:50, Duncan Murdoch <murdoch.duncan at gmail.com> wrote:
On 18/12/2019 5:01 p.m., Mauricio Zambrano-Bigiarini wrote:
Dear List, Today I submitted a package to CRAN, and after correcting some NOTEs, I got the following automatic message: "package mypackage_0.1-2.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days. For technical reasons you may receive a second copy of this message when a team member triggers a new check." Could somebody give a short explanation about what type of checkings are made in this "manual inspection" ?
Basically they're checking whether you are following the guidelines at https://cran.r-project.org/web/packages/policies.html. Not all of those things can be checked automatically, and many people claim to be following them when they actually are not. Duncan Murdoch
La informaci?n contenida en este correo electr?nico y cualquier anexo o respuesta relacionada, puede contener datos e informaci?n confidencial y no puede ser usada o difundida por personas distintas a su(s) destinatario(s). Si usted no es el destinatario de esta comunicaci?n, le informamos que cualquier divulgaci?n, distribuci?n o copia de esta informaci?n constituye un delito conforme a la ley chilena. Si lo ha recibido por error, por favor borre el mensaje y todos sus anexos y notifique al remitente.
Mauricio, I appreciate the manual inspection. I am waiting for the second time on a manual inspection. The first inspection found a fairly severe error of mine where I was writting out an error file to the user?s home directory space. It was code I had written over two years ago and long before I considered submission to CRAN. The code is only exercised with an specific data error when manually exercising the API of the Shiny application included in the package. I was certainly embarrashed by my error but I am more grateful for the work of Kurt Hornik and Uwe Ligges who found the mistake. Mark R. Mark Sharp, Ph.D. Data Scientist and Biomedical Statistical Consultant 7526 Meadow Green St. San Antonio, TX 78251 mobile: 210-218-2868 rmsharp at me.com
On Dec 18, 2019, at 7:26 PM, Mauricio Zambrano-Bigiarini <mauricio.zambrano at ufrontera.cl> wrote: Thank you very much Duncan for the information. BTW, it is incredible to me how the quality control of packages submitted to CRAN has improved in the last decade. Now the automatic procedures are able to identify even "little" things (e.g., broken links, misspelled words, size of vignettes, etc). Thank you very much for all the effort and dedication of the CRAN Repository Maintainers. Kind regards, Mauricio ===================================== "Success is not final, failure is not fatal. It is the courage to continue that counts. (Winston Churchill) ===================================== Linux user #454569 -- Linux Mint user On Wed, 18 Dec 2019 at 19:50, Duncan Murdoch <murdoch.duncan at gmail.com <mailto:murdoch.duncan at gmail.com>> wrote:
On 18/12/2019 5:01 p.m., Mauricio Zambrano-Bigiarini wrote:
Dear List, Today I submitted a package to CRAN, and after correcting some NOTEs, I got the following automatic message: "package mypackage_0.1-2.tar.gz has been auto-processed and is pending a manual inspection of this new CRAN submission. A CRAN team member will typically respond to you within the next 10 working days. For technical reasons you may receive a second copy of this message when a team member triggers a new check." Could somebody give a short explanation about what type of checkings are made in this "manual inspection" ?
Basically they're checking whether you are following the guidelines at https://cran.r-project.org/web/packages/policies.html. Not all of those things can be checked automatically, and many people claim to be following them when they actually are not. Duncan Murdoch
-- La informaci?n contenida en este correo electr?nico y cualquier anexo o respuesta relacionada, puede contener datos e informaci?n confidencial y no puede ser usada o difundida por personas distintas a su(s) destinatario(s). Si usted no es el destinatario de esta comunicaci?n, le informamos que cualquier divulgaci?n, distribuci?n o copia de esta informaci?n constituye un delito conforme a la ley chilena. Si lo ha recibido por error, por favor borre el mensaje y todos sus anexos y notifique al remitente.
______________________________________________ R-package-devel at r-project.org <mailto:R-package-devel at r-project.org> mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel <https://stat.ethz.ch/mailman/listinfo/r-package-devel>