Hi all, I have commited a new release of my package and waited for more than one day. After that "install.packages("tests",repos="http://r-forge.r-projet.org")" still returns "package 'tests' is not available". I have done the local build & check and the package seems ok. Also have mofified the Title in the DESCRIPTION file. What can be wrong? Is there any tool or recomendation to validade my package before submit it? -- Cristiano Strieder S?o Jos? dos Campos - SP
Cristiano Strieder <cstrieder <at> gmail.com> writes:> > Hi all, > > I have commited a new release of my package and waited for more than > one day. After that > "install.packages("tests",repos="http://r-forge.r-projet.org")" still > returns "package 'tests' is not available". I have done the local > build & check and the package seems ok. Also have mofified the Title > in the DESCRIPTION file. > > What can be wrong? > > Is there any tool or recomendation to validade my package before submit it? >I don't think there is any way to check before submitting beyond R CMD build and check with an up-to-date R. Have you checked the build and check logs on R-forge? The build environment on r-forge can often be slightly different from your "home" build environment.
a typo in r-projeCt.org? install.packages("tests",repos="http://r-forge.r-project.org") -- View this message in context: http://r.789695.n4.nabble.com/Why-my-package-is-not-being-generated-tp3255111p3258202.html Sent from the R help mailing list archive at Nabble.com.