Hi Johannes, Thanks for the follow-ups. I'll combine my replies to both mails into this one.
On 13 December 2006 at 14:10, Johannes Ranke wrote: | > Works for me on my testing box with 3.1.77-1 -- see below. | > | > Could you please grep for R_LIBS in | > /etc/R/ | | jazzy:/etc/R# grep R_LIBS * | Renviron:R_LIBS=${R_LIBS-'/usr/local/lib/R/site-library:/usr/lib/R/site-library:/usr/lib/R/library'} | Renviron.dpkg-dist:R_LIBS=${R_LIBS-'/usr/local/lib/R/site-library:/usr/lib/R/site-library:/usr/lib/R/library'} | | > /usr/lib/R/etc/ | | jazzy:/usr/lib/R/etc# grep R_LIBS * | Renviron:R_LIBS=${R_LIBS-'/usr/local/lib/R/site-library:/usr/lib/R/site-library:/usr/lib/R/library'} Defaults, so it finds the package. | > and it should come up once in | | ??? | | I had the thought that the help index is not built in the postrm script | (there are a few lines commented out that would probably do this), but | this would not explain why the R packages can not be loaded... The help index has nothing to do with how library() works. The help index now gets rebuilt once you say help.start() in R. | | > Weird. Let's check -- we obviously need to fix this if it is a generic issue. | | Yes, definitely. For now I can only use packages installed directly from | CRAN via install.packages() on this box, or use my Windows XP instance in | Xen which also works nicely ... Ah. I still haven't tried Xen, but I do like vmware... On 13 December 2006 at 16:06, Johannes Ranke wrote: | I investigated some more and was able to solve the problem | by purging (!) r-cran-nlme + r-cran-lattice and reinstalling them. | | I am as yet unable to reproduce the problem. I will do another upgrade | from sarge to etch, and will report if the problem reappears. Sounds like a good idea. Please try to note which versions of r-cran-nlme et al you are upgraing from, and to, and under which R version. I may have a hard time replicating this but I can try .... Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]