search for: read_descript

Hello useRs I am trying to build a package for personal use and for making easier working with other people but I keep getting the same error message about the DESCRIPTION file not existing. when trying to install from a source tar.gz file: Error in .read_description(dfile) : file 'C:/Users/Propriétaire/AppData/Local/Temp/RtmpHFMONb/R.INSTALL647a3535/mypkg/DESCRIPTION' does not exist when trying to build a binary version: Error in .read_description(dfile) : file 'C:/Users/Propriétaire/Documents/RETROBIRD/mypkg/DESCRIPTION' does not...

...update.gamlss text html latex example usair text html latex example wp text html latex example zipping help files hhc: not found preparing package gamlss for lazy loading Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of gamlss failed *** Removing 'c:/TEMP/Rbuild.1520/gamlss' ERROR * installation failed * building 'gamlss_0.4-0.zip' Can't stat gamlss: No such file or...

...pow (the daily package check on CRAN gave warnings due to .Rd problems, fixed). Now it PASSED Rcmd check (WindowsXP home edition, rw2000dev, on a new toshiba laptop, if that matters.) but then Rcmd build --binary gives problems: . . . preparing package asypow for lazy loading Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of asypow failed *** Removing 'C:/DOCUME~1/HALVOR~1/LOCALS~1/Temp/Rbuild.852/asypow' ERROR * installation failed . . . but as it passed make check, DESCRIPTION obviuosl...

...DESCRIPRION file. If I do that then everything proceeds smoothly. R CMD check proceeds smoothly in either case. Is there something I should be aware of that is causing this message when I do not turn off lazy loading? I am using Windows XP and R 2.0.1 beta dated 2004-11-04. Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of zoo failed *** Removing 'C:/PROGRA~1/R/RW2001~1/library/zoo' Restoring previous 'C:/PROGRA~1/R/RW2001~1/library/zoo'

Dear R-devel list, I would like to enquire about the existence of blank lines in the DESCRIPTION file. Testing different possibilities with tools:::.read_description suggests that starting or ending with blank lines is acceptable while blank lines in the middle of the file get caught by out <- tryCatch(read.dcf(dfile, keep.white = .keep_white_description_fields), error = function(e) stop(gettextf("file '%s' is not in valid DCF forma...

...1.9.0. The operation system is Win2000 5.00.2195, Service Pack 3 When I do: c:\stat\r\rw2000\bin\Rcmd install --docs=normal --build --library=c:\stat\R\bxc\library c:\stat\R\bxc\library.sources\xx then after updating help pages I get: preparing package xx for lazy loading Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of xx failed *** (Yes, I have a DESCRIPTION file). Having made a few changes here and there in some of the functions I transferred them one at a time to a new folder...

...1.9.0. The operation system is Win2000 5.00.2195, Service Pack 3 When I do: c:\stat\r\rw2000\bin\Rcmd install --docs=normal --build --library=c:\stat\R\bxc\library c:\stat\R\bxc\library.sources\xx then after updating help pages I get: preparing package xx for lazy loading Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of xx failed *** (Yes, I have a DESCRIPTION file). Having made a few changes here and there in some of the functions I transferred them one at a time to a new folder...

...de to read the annotated source files and return the ordered file names. (2) After all, when I put the ordered file list in front of Collade in the DESCRIPTION file, I got this error induring installation: ---------- Making package vtkr ------------ adding build stamp to DESCRIPTION Error in .read_description(dfile) : file 'DESCRIPTION' is not in valid DCF format Execution halted make[2]: *** [frontmatter] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-vtkr] Error 2 *** Installation of vtkr failed *** After a bit playing with th enumber of th efiles, it seems to me Collade cannot handle...

...all them. Current definition > of the \packageAuthor macro is > > \newcommand{\packageAuthor}{\Sexpr[results=rd,stage=build]{t > ools:::Rd_package_author("#1")}} > > and the function is defined as > > function (pkg, dir = ".") > { > desc <- .read_description(file.path(dir, "DESCRIPTION")) > if (pkg != desc["Package"]) > stop(gettextf("DESCRIPTION file is for package '%s', not '%s'", > desc["Package"], pkg)) > desc["Author"] > } > > So P...

When I include the macros \packageAuthor, \packageDescription, \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf fails with $ R CMD Rd2pdf mpra Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist This does not happen if I comment out 4 occurrences of these 4 macros in mpra-package.Rd.

...-minor *** ### outline-regexp: "### [*]+" *** Index: src/library/tools/R/build.R =================================================================== --- src/library/tools/R/build.R (revision 87545) +++ src/library/tools/R/build.R (working copy) @@ -1165,9 +1165,11 @@ desc <- .read_description(file.path(pkgname, "DESCRIPTION")) Rdeps <- .split_description(desc)$Rdepends2 hasDep350 <- FALSE + hasDep410 <- FALSE for(dep in Rdeps) { if(dep$op != '>=') next if(dep$version >= "3.5.0") has...

...: "### [*]+" *** > Index: src/library/tools/R/build.R > =================================================================== > --- src/library/tools/R/build.R (revision 87545) > +++ src/library/tools/R/build.R (working copy) > @@ -1165,9 +1165,11 @@ > desc <- .read_description(file.path(pkgname, "DESCRIPTION")) > Rdeps <- .split_description(desc)$Rdepends2 > hasDep350 <- FALSE > + hasDep410 <- FALSE > for(dep in Rdeps) { > if(dep$op != '>=') next > if(dep$versio...

...+" *** >> Index: src/library/tools/R/build.R >> =================================================================== >> --- src/library/tools/R/build.R (revision 87545) >> +++ src/library/tools/R/build.R (working copy) >> @@ -1165,9 +1165,11 @@ >> desc <- .read_description(file.path(pkgname, "DESCRIPTION")) >> Rdeps <- .split_description(desc)$Rdepends2 >> hasDep350 <- FALSE >> + hasDep410 <- FALSE >> for(dep in Rdeps) { >> if(dep$op != '>=') next >> if(dep$version >= "3.5.0") ha...

...Index: src/library/tools/R/build.R >>> =================================================================== >>> --- src/library/tools/R/build.R (revision 87545) >>> +++ src/library/tools/R/build.R (working copy) >>> @@ -1165,9 +1165,11 @@ >>> desc <- .read_description(file.path(pkgname, "DESCRIPTION")) >>> Rdeps <- .split_description(desc)$Rdepends2 >>> hasDep350 <- FALSE >>> + hasDep410 <- FALSE >>> for(dep in Rdeps) { >>> if(dep$op != '>=') next >>> if(dep$version &gt...

...functions, because the system-defined macros call them. Current definition of the \packageAuthor macro is \newcommand{\packageAuthor}{\Sexpr[results=rd,stage=build]{tools:::Rd_package_author("#1")}} and the function is defined as function (pkg, dir = ".") { desc <- .read_description(file.path(dir, "DESCRIPTION")) if (pkg != desc["Package"]) stop(gettextf("DESCRIPTION file is for package '%s', not '%s'", desc["Package"], pkg)) desc["Author"] } So Peter is right, this would like...

...tools/R/build.R >>>> =================================================================== >>>> --- src/library/tools/R/build.R (revision 87545) >>>> +++ src/library/tools/R/build.R (working copy) >>>> @@ -1165,9 +1165,11 @@ >>>> desc <- .read_description(file.path(pkgname, "DESCRIPTION")) >>>> Rdeps <- .split_description(desc)$Rdepends2 >>>> hasDep350 <- FALSE >>>> + hasDep410 <- FALSE >>>> for(dep in Rdeps) { >>>> if(dep$op != '>=') next >>&gt...

...de the R folder and "DESCRIPTION" file, But I wrote nothing in the "DESCRIPTION" file. Actually, I don't know what I should write in it. Well, there are still aother error: ---------- Making package example ------------ adding build stamp to DESCRIPTION error happened.read_description(dfile) : file 'D:/example/DESCRIPTION' is not in valid DCF format Stop execute make[2]: *** [frontmatter] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-example] Error 2 *** Installation of example failed *** Removing 'D:/PROGRA~1/R/rw2011/library/example' Please tell m...

...>>> =================================================================== > >>>> --- src/library/tools/R/build.R (revision 87545) > >>>> +++ src/library/tools/R/build.R (working copy) > >>>> @@ -1165,9 +1165,11 @@ > >>>> desc <- .read_description(file.path(pkgname, "DESCRIPTION")) > >>>> Rdeps <- .split_description(desc)$Rdepends2 > >>>> hasDep350 <- FALSE > >>>> + hasDep410 <- FALSE > >>>> for(dep in Rdeps) { > >>>> if(dep$op != '&gt...

Dear Gabor, Thank your for helping me so much! I have loaded R the newest version 2.1.1. Then I setup it in the path of D:\program files\R\ 1. unpack tools.zip into c:\cygwin 2. install Active perl in c:\Perl 3. install the mingw32 in c:\mingwin 4. add "c:\cygwin; c:\mingwin\bin" in "Control Panel -> System -> Advanced -> Environment Variables -> Path ->

Dear all, I have done every step as the previous mail. 1. unpack tools.zip into c:\cygwin 2. install Active perl in c:\Perl 3. install the mingw32 in c:\mingwin 4. add "c:\cygwin; c:\mingwin\bin" in "Control Panel -> System -> Advanced -> Environment Variables -> Path -> Variable" , and they are in the beginning of the "Path" Because I install R in