Re: [Rd] r-forge down?
On 10/16/2010 10:27 AM, Ben Bolker wrote: anyone have a status report on r-forge ... ? From here (Hamilton, ON) I can't ping ... PING r-forge.wu-wien.ac.at (137.208.57.38) 56(84) bytes of data. The machine was restarted today morning. We are sorry for the downtime. We need to migrate R-Forge to a better equipped system in order to improve reliability. Back then in 2007 when we designed R-Forge we didn't expect so much interest like we observe now (>2600 users, almost 900 projects). Thus the current system is quite undersized compared to its responsibilities. Best, st cheers Ben Bolker __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] r-forge down?
On 10/18/2010 01:07 PM, Philippe Grosjean wrote: Thanks anyway for all your work on R-Forge... We will probably survive this thread ;-) Once you will got an hardware upgrade, I think we will all be happy to recover complete testing of developed packages (Linux 32/64bit, Mac 32/64bit, Windows 32/64bit), ... if possible. Sure, on my todo list. Multi-arch binaries are long promised (for Windows) and we are close to releasing them. Best, Stefan Best, Philippe ..<°}))>< ) ) ) ) ) ( ( ( ( (Prof. Philippe Grosjean ) ) ) ) ) ( ( ( ( (Numerical Ecology of Aquatic Systems ) ) ) ) ) Mons University, Belgium ( ( ( ( ( .. On 18/10/10 12:33, Stefan Theussl wrote: On 10/16/2010 10:27 AM, Ben Bolker wrote: anyone have a status report on r-forge ... ? From here (Hamilton, ON) I can't ping ... PING r-forge.wu-wien.ac.at (137.208.57.38) 56(84) bytes of data. The machine was restarted today morning. We are sorry for the downtime. We need to migrate R-Forge to a better equipped system in order to improve reliability. Back then in 2007 when we designed R-Forge we didn't expect so much interest like we observe now (>2600 users, almost 900 projects). Thus the current system is quite undersized compared to its responsibilities. Best, st cheers Ben Bolker __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] R-Forge Downtime
To all R-Forge developers/users: Please note the short (<30min.) R-Forge downtime today at 18:00 CET. Details: We need to extend disk space of the system hosting the core R-Forge components. This will lead to a short (<30min.) downtime of R-Forge today at 18:00 CET. This is necessary due to the unreliability of R-Forge especially on weekends, when log files have to be copied to a backup location. Sometimes the system got unresponsive for a couple of hours from sunday late evening to monday morning. We are sorry for the inconvenience caused. Best regards, The R-Forge Administration and Development Team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R-Forge down
On 03/16/2011 05:43 PM, Max Kuhn wrote: Web page and svn, but you probably already know this. Thanks a lot for the note. This is due to a network system failure at WU. From the intranet we cannot connect to services outside and vice versa. I hope the guys at IT services will fix this soon. CRAN and r-project.org in general might also be affected. Interestingly, we can access every service hosted by WU from the intranet but obviously not from outside... Best, st Thanks for all the hard work, Max __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Does anybody successfully built latest R on AIX 5.3?
We successfully built R on AIX 6.1 but the following instructions should also work for 5.3. We mainly used the software from OSS4AIX but also from the "AIX Toolbox for Linux Applications" obtainable directly from IBM. Attached you'll find our list of installed rpms. This and the instructions provided in the "R Installation and Administration" manual should be all you need to build R on AIX systems. hth, st cdrecord-1.9-7 mkisofs-1.13-4 libtiff-3.6.1-4 bash-3.0-1 bash-doc-3.0-1 less-382-1 vim-enhanced-6.3-1 vim-common-6.3-1 screen-3.9.10-2 wget-1.9.1-1 rsync-2.6.2-1 emacs-nox-21.3-1 emacs-leim-21.3-1 expat-2.0.1-1 neon-0.28.2-1 openssl-0.9.8h-1 sqlite-3.6.1-1 readline-5.2-1 gdbm-1.8.3-2 info-4.6-1 emacs-el-21.3-1 apr-1.3.2-1 apr-util-1.3.2-1 gmp-4.2.3-1 readline-devel-5.2-1 zlib-1.2.3-6 emacs-21.3-1 subversion-1.4.6-2 tar-1.14-2 mpfr-2.3.1-1 mpfr-devel-2.3.1-1 xft-2.1.6-5 libstdc++-4.2.4-1 python-2.3.4-4 joe-3.5-1 libXpm-3.5.7-2 gmp-devel-4.2.3-1 m4-1.4.11-1 gcc-cpp-4.2.4-2 freetype2-2.3.7-1 libgomp-4.2.4-2 gcc-c++-4.2.4-2 zlib-devel-1.2.3-6 gdb-6.8-1 libgcc-4.2.4-2 libxml2-2.6.32-1 gcc-4.2.4-2 gcc-gfortran-4.2.4-2 make-3.80-1 pkg-config-0.19-6 t1lib-5.1.2-1 nano-2.0.7-1 cairo-1.0.2-6 popt-1.7-2 unzip-6.0-1 lynx-2.8.4-2 tightvnc-1.3.10-1 urw-fonts-2.0-1 xpdf-3.02-3 atk-1.10.3-2 fontconfig-2.5.0-2 glib2-2.8.1-3 libjpeg-6b-7 libpng-1.2.30-1 pango-1.10.0-2 xcursor-1.1.7-2 xrender-0.9.1-2 AIX-rpm-6.1.0.0-2 gtk2-2.8.3-9 libxml2-devel-2.6.32-1 sudo-1.6.9p17-1 gd-2.0.35-4 gd-devel-2.0.35-4 fontconfig-devel-2.5.0-2 freetype2-devel-2.3.7-1 expat-devel-2.0.1-1 libpng-devel-1.2.30-1 libjpeg-devel-6b-7 libXpm-devel-3.5.7-2 librsvg2-2.4.0-1 librsvg2-devel-2.4.0-1 glib2-devel-2.8.1-3 pango-devel-1.10.0-2 cairo-devel-1.0.2-6 gtk2-devel-2.8.3-9 atk-devel-1.10.3-2 libart_lgpl-2.3.20-1 libart_lgpl-devel-2.3.20-1 tightvnc-server-1.3.10-1 gettext-0.17-1 coreutils-6.12-1 libstdc++-devel-4.2.4-2 lapack-3.1.1-1 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Does anybody successfully built latest R on AIX 5.3?
On 06/08/2011 02:02 PM, XiaoboGu wrote: Hi Stefan, Thanks for replying! I have just managed to installed gcc 4.2.4.2 on AIX this evening, and will try to install gfortran tomorrow, there are a few more questions great. 1. Are you running R 2.13.0 Currently we are running 2.12.0 (works with both GNU and IBM compilers). I was not able to compile 2.13 with GNU compilers yet, IBM compilers work though (are preferable anyway, since performance is higher): R version 2.13.0 Patched (2011-06-08 r56086) Copyright (C) 2011 The R Foundation for Statistical Computing ISBN 3-900051-07-0 Platform: powerpc-ibm-aix6.1.0.0 (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > sessionInfo() R version 2.13.0 Patched (2011-06-08 r56086) Platform: powerpc-ibm-aix6.1.0.0 (64-bit) locale: [1] EN_US.UTF-8 EN_US.UTF-8 C C EN_US.UTF-8 EN_US.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base > However recommended package Matrix gives an error upon loading. 2. Can you share all the environment variables we have to set before running the configure script. See the manual and https://r-forge.r-project.org/scm/viewvc.php/install_scripts/install_R_AIX.sh?view=markup&root=aix You may download this script (and patches), modify the paths accordingly, run it (e.g., ./install_R_AIX.sh --ibm for 2.13) and R should build fine. There are a couple of notes and patches provided in the R/AIX repository on R-Forge (e.g., how to get IBM BLAS linked etc., missing third-party libs installed, etc.). 3. Can you share the full command line of configure script. see above. 4. According to your experience, is there a huge performance lift compared to X86 CPUS, what's the clock speed of you Power CPU? No there isn't. One can use the IBM BLAS library (ESSL), then one will observe a significant speedup for linear algebra tasks. Note however, ESSL does not incorporate the full BLAS specification (thus the patch). In general, R runs slower on the power architecture than on x86. We have a Power 6 8core CPU @ 3.5 GHz. Actually, we use our system mainly for memory-demanding applications (<=128GB RAM). Best, st Regards, Xiaobo Gu -Original Message- From: Stefan Theussl [mailto:stefan.theu...@wu.ac.at] Sent: Wednesday, June 08, 2011 7:07 PM To: guxiaobo1...@gmail.com Cc: r-devel@r-project.org Subject: Re: [Rd] Does anybody successfully built latest R on AIX 5.3? We successfully built R on AIX 6.1 but the following instructions should also work for 5.3. We mainly used the software from OSS4AIX but also from the "AIX Toolbox for Linux Applications" obtainable directly from IBM. Attached you'll find our list of installed rpms. This and the instructions provided in the "R Installation and Administration" manual should be all you need to build R on AIX systems. hth, st __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] CRAN Master Server Upgrade - Advance Notice
To all CRAN-users/uploaders/mirror-Providers: The CRAN master server will be upgraded on Nov., 2nd. Technology never stands still, so there comes a point when we need to upgrade our hardware to keep up with todays market. At the moment we are migrating data to the new server and test it as best as possible. The server will provide exactly the same content that CRAN already provides, but faster, and hopefully saver and better. The move is being done for several reasons: - There is better hardware technology available. - Better technology means faster processing to meet the requirements. - Hardware devices have a finite life. The move will take place on Nov.,2nd in the afternoon (~2pm EST). Thus keep in mind that the web and ftp service will not be available at that time. Best regards, CRAN staff __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] CRAN will be down for 15 minutes
Dear R Community, Due to maintenance work CRAN will not be available at 30th January around 10 o'clock in the morning CET. Best regards, Stefan Theussl __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] R-Forge
Hello Gregor, Yes, R-Forge.R-project.org will be the official forge for the R Community. But we have to fix a few things before we are going public. If you like you can participate and help us testing. If you have a package or a devel version of your package you're welcome to use SVN provided by R-Forge. For further questions please contact me or [EMAIL PROTECTED] Regards, Stefan --- Begin Message --- --- Begin Message --- Hello! I have recently found RForge.net (http://www.rforge.net/) by Simon Urbanek and found out today that the site is accepting subscriptions. Great! However, browsing a bit on the site I found a link to another forge: R-Forge (http://r-forge.r-project.org/). Is/will the last one be the "offcial" forge for R packages, given that it has domain r-project.org? Regards, Gregor __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel --- End Message --- --- End Message --- __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R-Forge?
hadley wickham wrote:
>> > I have recently found RForge.net (http://www.rforge.net/) by Simon
>> > Urbanek and found out today that the site is accepting subscriptions.
>> > Great! However, browsing a bit on the site I found a link to another
>> > forge: R-Forge (http://r-forge.r-project.org/).
>> >
>> > Is/will the last one be the "offcial" forge for R packages, given that
>> > it has domain r-project.org?
>>
>> Yes, we're currently still testing the functionality and improving the
>> documentation, but an article for R News that announces the
>> functionality
>> is under preparation. There is already a user's manual available on the
>> main page which explains how you can register and set up your project
>> etc.
>> Just as Simon's site this already offers an SVN and nightly builds in a
>> CRAN-style repository, and additionally there is the whole GForge system
>> with other features such as project forums, mailing lists etc.
>
> Is it possible to use r-forge just for the nightly builds? (ie. with
> svn hosted elsewhere) That would be really handy.
>
> Hadley
We have never thought about it, but this would be technically difficult.
But you may migrate your svn (or the part which contains the package) to
R-Forge and have the advantage of daily build and checked packages with
the possibility to install it directly from R-Forge:
|install.packages("/packagename/",repos="http://r-forge.r-project.org";)|
Best,
Stefan
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R-Forge
Henrik Bengtsson wrote: > Hi, > > thanks for working on this and offering us this service. One thing I > wonder is about backup. What kind of backup do you use or plan to > use? We plan to daily backup the svn repositories and the database (which contains R-Forge specific data). The files are stored on a RAID 5 on a separate server. We also have the option to use a tape storage. But we have to discuss this issue in more detail first. Best, Stefan > > Best, > > Henrik > > On 4/6/07, Stefan Theussl <[EMAIL PROTECTED]> wrote: >> Hello Gregor, >> >> Yes, R-Forge.R-project.org will be the official forge for the R >> Community. But we have to fix a few things before we are going public. >> If you like you can participate and help us testing. If you have a >> package or a devel version of your package you're welcome to use SVN >> provided by R-Forge. >> For further questions please contact me or [EMAIL PROTECTED] >> >> Regards, >> Stefan >> >> >> >> -- Forwarded message -- >> From: Kurt Hornik <[EMAIL PROTECTED]> >> To: Stefan Theussl <[EMAIL PROTECTED]> >> Date: Fri, 6 Apr 2007 14:38:40 +0200 >> Subject: forwarded message from Gregor Gorjanc >> >> >> -- Forwarded message -- >> From: Gregor Gorjanc <[EMAIL PROTECTED]> >> To: r-devel@r-project.org >> Date: Fri, 06 Apr 2007 12:53:07 +0200 >> Subject: [Rd] R-Forge? >> Hello! >> >> I have recently found RForge.net (http://www.rforge.net/) by Simon >> Urbanek and found out today that the site is accepting subscriptions. >> Great! However, browsing a bit on the site I found a link to another >> forge: R-Forge (http://r-forge.r-project.org/). >> >> Is/will the last one be the "offcial" forge for R packages, given that >> it has domain r-project.org? >> >> Regards, Gregor >> >> __ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel >> >> >> __ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel >> >> __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Possible improvements/clarifications for R-forge (Was: Re: Using SVN + SSH on windows)
On 03/28/2010 07:28 PM, Christophe Genolini wrote: Wahou! I did not plan to start such a debate... It is really not hard to set it up. I am using a vanilla ssh (rather than putty) and that works fine all the time... The problem is not how hard or easy it is, the problem is how time consuming it is. I am pretty sur that I will manage to make it work. But when? I allready lose three hours Friday and two hour on saturday... That's definitly too much. Because I am not an engeneer in computing, I am a researcher. To make my research, I have to be expert in longitudinal data, in clustering, in anorexia, I have to speak english, I have to know R, and C, and package managing, and LaTeX, and gimp, and... and... and... There is so many things to know... I can not be expert in all. So I do not have time to (and I do not want to) explore all the ssh subtulties... Worse, I have a project, I manage to find some people that want to work on the projet (but that also have a lot of other staff to do), I do not want them to give up because it will take to much time for them to make ssh run. Generalier, I think that anything should be done to make tools easy to use for non-expert, because more and more R user are occasional user. They are not experts, they don't want to become expert. They are just feed up to pay a lot of money for SPSS or Stata... But I guess this is another debate. As far as R-Forge is concerned, developers don't need to know how SSH works. Only the SVN client needs to be aware of it. One can always use passwords, private/public key authentication is not necessary here. Entering passwords multiple times is the only drawback of the keyless approach. I think question 5 is answered. Now, an attempt to answer the other questions: Christophe I wonder why nobody included the R-forge maintainer in this thread so far. Let me add Stefan now. Best wishes, Uwe On 28.03.2010 18:34, Henrik Bengtsson wrote: Hi, first, r-forge.r-project.org is filling a need and provides a great service to the community. Please read this thread as sincere feedback for making it even better, not as a complaint. I fully understand that r-forge is ran by limited resources and on a volunteer basis. I'll list some points about r-forge that I think could be improved/clarified. Not expecting anything, just sharing my experience. 1. Part of the R-forge services runs on a schedule, e.g. building and checking packages. As a user you do not really know when this happens. Some of this is documented at http://site.r-forge.r-project.org/, but not everything, e.g. as seen in another message on r-devel, the cron job for updating SSH keys is not specified. Moreover, all static documentation tends to become outdated. In other words, as a user I am not certain that http://site.r-forge.r-project.org/ is up to date. Providing some kind of online log of what the r-forge servers are doing would help the user to plan, troubleshoot etc. Right now there are too many degrees of freedom to figure out what and when things happens. The Bioconductor project provides a small log summary/status with timestamps of the last run, cf. small box at the top of http://bioconductor.org/checkResults/2.6/bioc-LATEST/. I have to admit, there may be documentation for some part of the R-Forge system missing. But a) Section 3.2. of the R-Forge manual actually specifies very clearly when the cron job for updating SSH keys is run (namely once every full hour), b) the schedule at http://site.r-forge.r-project.org/ is usually up-to-date and c) I'm open to work with you together on a fancy status report similar to the bioconductor project. 2. It is not possible to check the R CMD build/check log files for other people's packages. The log files are considered private to the project members. This means that I cannot troubleshoot other packages part of projects that I am not a member. This limits my chances to troubleshoot problems I have when my package depends on an external package. It also limits my chances to contribute with troubleshooting/bug reports for other packages. This is one of the features that makes the Bioconductor repository a success. Making these log files public would improve lots of things. This was based on historic reasons. It seems indeed reasonable to drop this limitation. From now on, only the "Submit to CRAN button" is hidden from non-members of a project. 3. For some OSes, the log files for the build and check of packages are missing. For instance, none of my packages has log files for Linux x86_32, e.g. "Logfile for R.batch not available.". It is not clear if this is because I made something wrong, or this is the flavor of the day, or a permanent error. (I looks permanent for "Linux x86_32", but not sure about the others). This is because the 32bit system has been replaced and is not set up correctly yet. I hope we can fix this soon. Being able to access the r-forge server logs, si
[Rd] R-Forge SVN repositories: R CMD build/check error on Windows machines
Dear R-devel, One of our R-Forge developers pointed out that it is not possible to build packages under Windows using the R-Forge repository structure: a package resides in ./pkg - not in a directory with the same name as the package name. Under Linux 'R CMD build pkg' or 'R CMD check pkg' work pretty well (I think Kurt Hornik fixed that in R 2.5.1 or so) whereas under Windows one gets the following error (this is the example sent by the user): c:\work\packages\spdep>R CMD check pkg * checking for working pdflatex ... OK * using log directory 'C:/work/packages/spdep/pkg.Rcheck' * using R version 2.7.0 (2008-04-22) * using session charset: ISO8859-1 * checking for file 'pkg/DESCRIPTION' ... OK * this is package 'spdep' version '0.4-21' * package encoding: latin1 * checking package name space information ... OK * checking package dependencies ... OK * checking if this is a source package ... WARNING Subdirectory 'pkg/src' contains object files. * checking whether package 'spdep' can be installed ... ERROR Installation failed. See 'C:/work/packages/spdep/pkg.Rcheck/00install.out' for details. which is: installing R.css in C:/work/packages/spdep/pkg.Rcheck -- Making package pkg adding build stamp to DESCRIPTION installing NAMESPACE file and metadata making DLL ... ... DLL made installing DLL installing R files installing inst files installing data files preparing package pkg for lazy loading Loading required package: tripack Loading required package: sp ... Error in findpack(package, lib.loc) : *there is no package called 'pkg'* Calls: -> findpack Execution halted make[2]: *** [lazyload] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-pkg] Error 2 *** Installation of pkg failed *** I could verify this on our 'Windows package building machine' not only for this package but also for others. Therefore, it seems to me that the (Windows) R CMD build/check scripts are not considering the package name in the DESCRIPTION file but rather take the directory name as package name. Or are we just doing something completely wrong? I used R-patched 2.7.0 on R-Forge to reproduce this error. Best regards, Stefan __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R-Forge SVN repositories: R CMD build/check error on Windows machines
Duncan Murdoch wrote: On 28/04/2008 12:22 PM, Stefan Theussl wrote: Dear R-devel, One of our R-Forge developers pointed out that it is not possible to build packages under Windows using the R-Forge repository structure: a package resides in ./pkg - not in a directory with the same name as the package name. Under Linux 'R CMD build pkg' or 'R CMD check pkg' work pretty well (I think Kurt Hornik fixed that in R 2.5.1 or so) whereas under Windows one gets the following error (this is the example sent by the user): c:\work\packages\spdep>R CMD check pkg * checking for working pdflatex ... OK * using log directory 'C:/work/packages/spdep/pkg.Rcheck' * using R version 2.7.0 (2008-04-22) * using session charset: ISO8859-1 * checking for file 'pkg/DESCRIPTION' ... OK * this is package 'spdep' version '0.4-21' * package encoding: latin1 * checking package name space information ... OK * checking package dependencies ... OK * checking if this is a source package ... WARNING Subdirectory 'pkg/src' contains object files. * checking whether package 'spdep' can be installed ... ERROR Installation failed. See 'C:/work/packages/spdep/pkg.Rcheck/00install.out' for details. which is: installing R.css in C:/work/packages/spdep/pkg.Rcheck -- Making package pkg adding build stamp to DESCRIPTION installing NAMESPACE file and metadata making DLL ... ... DLL made installing DLL installing R files installing inst files installing data files preparing package pkg for lazy loading Loading required package: tripack Loading required package: sp ... Error in findpack(package, lib.loc) : *there is no package called 'pkg'* Calls: -> findpack Execution halted make[2]: *** [lazyload] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-pkg] Error 2 *** Installation of pkg failed *** I could verify this on our 'Windows package building machine' not only for this package but also for others. Therefore, it seems to me that the (Windows) R CMD build/check scripts are not considering the package name in the DESCRIPTION file but rather take the directory name as package name. Or are we just doing something completely wrong? You're right, on Windows there's an assumption that package foo is in directory foo. But I don't see why this is a big problem. Can't you just check out pkg into foo, e.g. svn co svn://svn.r-forge.r-project.org/svnroot/foo/pkg foo (Not that I'd be against accepting a patch to remove this restriction; occasionally it might be nice to have two versions of the same package side-by-side.) Yes, you're right. Actually we do it this way when exporting the R-Forge packages. We just look for the package name in the DESCRIPTION file and do an 'svn export' using this information. The other possibility on R-Forge would be to have the package in a directory ./pkg/foo in the repository. This is supported by our build process. Therefore this is no problem at all for us. Nevertheless, I think that this is a useful convenience feature (indeed I use that very often under Linux). E.g., one wants to have his or her packages in different directories like foo-devel, foo-release and just say R CMD build/check on them. Best, Stefan Duncan Murdoch I used R-patched 2.7.0 on R-Forge to reproduce this error. Best regards, Stefan __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R-Forge SVN repositories: R CMD build/check error on Windows machines
Deepayan Sarkar wrote: On 4/28/08, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: The difference is in INSTALL, not build/check. You are right that the Unix INSTALL was changed in r25808 (Aug 2003), but AFAICS this was not documented at the time in [O]NEWS, nor anywhere else. Can you point me to the documentation you used to implement this? FWIW, the NEWS for 2.5.0 [1] has o R CMD build now takes the package name from the DESCRIPTION file and not from the directory. (PR#9266) and that does seem to work on Windows. Indeed, this works but with the side effect of getting the error message Error in findpack(package, lib.loc) : there is no package called 'pkg' Calls: -> findpack Execution halted make[2]: *** [lazyload] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-pkg] Error 2 *** Installation of pkg failed *** which comes from R CMD INSTALL as Brian Ripley pointed out already. Nevertheless, the package gets built and you can handle the tarball with no further problems as always. Stefan [1] https://stat.ethz.ch/pipermail/r-announce/2007/000828.html -Deepayan __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
