Skip to content

R 2.15.2 is released

6 messages · Sam Steingold, Bert Gunter, R. Michael Weylandt +1 more

#
Cool.
I have some packages installed using install.packages().
Do I need to reinstall them?

https://r-forge.r-project.org/tracker/?func=detail&atid=294&aid=2224&group_id=61
   Not a bug: This only happens under the circumstance of a Matrix
   package installation *not* matching your R installation. In other
   words: One way to fix your problem is to re install the Matrix
   package in the version of R you are using.

So, will the bug reappear now?
#
?update.packages

-- Bert
On Sun, Nov 4, 2012 at 7:01 AM, Sam Steingold <sds at gnu.org> wrote:

  
    
#
It is not obvious to me that this is the answer to my question.
Specifically, I have package X version 1.2.3 installed and built against
R version 2.15.1.
If 1.2.3 is the current latest version of X, then update.packages() will
_not_ try to update it, but, apparently, at least for some packages, I
do need to rebuild them against the new R version 2.15.2.

Thanks.

  
    
#
On Sun, Nov 4, 2012 at 6:22 PM, Sam Steingold <sds at gnu.org> wrote:
If I remember correctly (and I may well not) it's somewhat OS
dependent, with OS X being rather strict about package updates (2.15.1
not being so compatible with 2.15.2) while linuxen are nicer about it.

Certainly packages with significant compiled code (like Matrix) are
more prone to versioning mis-matches.

Michael
#
On Nov 4, 2012, at 12:22 PM, Sam Steingold <sds at gnu.org> wrote:

            
Take note of the 'checkBuilt' argument, which defaults to FALSE...

Regards,

Marc Schwartz
#
Thanks a lot!

So, what I need to do is:

update.packages(checkBuilt=TRUE, ask=FALSE,
                lib.loc=.libPaths()[grep("^/home/",.libPaths())])