R SIG Debian - May 2010 - 2.11.0 on ubuntu (hardy) inadvertently installed

Hi-

Looks like this morning, I did the ultimate in foobar to a main prod 
box. I was using apt-get upgrade on the box and totally missed the fact 
that my entire R installation went from 2.10.0 to 2.11.0.

I now have a bunch of pkgs that aren't loading due to the fact that they 
were built before 2.10.0 -- There's some *ancient* packages, like (sma) 
that I was able to figure out what we were using, and pull out the 
relevant functions and just temporarily do a "source('xxx.r')"
until I
can re-build those things into new 2.11 packages.

Am I totally SOL today or is there a way to "reverse" what the heck I 
did this morning to the entire R installation?

thx,c

Hi Cedrick,

Wrong list -- r-sig-debian may be better so I am redirecting. Hope you don't
mind.

On 28 May 2010 at 11:25, Cedrick W. Johnson wrote:
| Hi-
| 
| Looks like this morning, I did the ultimate in foobar to a main prod 
| box. I was using apt-get upgrade on the box and totally missed the fact 
| that my entire R installation went from 2.10.0 to 2.11.0.
| 
| I now have a bunch of pkgs that aren't loading due to the fact that they 
| were built before 2.10.0 -- There's some *ancient* packages, like (sma) 
| that I was able to figure out what we were using, and pull out the 
| relevant functions and just temporarily do a
"source('xxx.r')" until I
| can re-build those things into new 2.11 packages.
| 
| Am I totally SOL today or is there a way to "reverse" what the heck
I
| did this morning to the entire R installation?

Comment out the /etc/apt/sources.list entry for the Ubuntu R port via CRAN
and pick the R version that came with Ubuntu's Hardy release.

You could use Ubunti Karmic's R from last fall; as I recall that was 2.9.2.

Lastly, you can always pick 2.10.0 and build a local package to recreate what
you just upgraded away from.

Or: just stick with 2.11.0 and populate /usr/local/lib/R/site-library/ with
the CRAN packages you need.  Just force a re-install, the install.r example
from littler may be of help.

Good luck.

-- 
  Regards, Dirk

You might want to ask on R-SIG-Debian

https://stat.ethz.ch/mailman/listinfo/r-sig-debian

Cedrick W. Johnson wrote:
> Hi-
> 
> Looks like this morning, I did the ultimate in foobar to a main prod 
> box. I was using apt-get upgrade on the box and totally missed the fact 
> that my entire R installation went from 2.10.0 to 2.11.0.
> 
> I now have a bunch of pkgs that aren't loading due to the fact that
they
> were built before 2.10.0 -- There's some *ancient* packages, like (sma)
> that I was able to figure out what we were using, and pull out the 
> relevant functions and just temporarily do a
"source('xxx.r')" until I
> can re-build those things into new 2.11 packages.
> 
> Am I totally SOL today or is there a way to "reverse" what the
heck I
> did this morning to the entire R installation?
> 
> thx,c
> 
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide 
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

Am 28.05.2010 17:25, schrieb Cedrick W. Johnson:
> I now have a bunch of pkgs that aren't loading due to the fact that 
> they were built before 2.10.0 -- There's some *ancient* packages, like 
> (sma) that I was able to figure out what we were using, and pull out 
> the relevant functions and just temporarily do a
"source('xxx.r')"
> until I can re-build those things into new 2.11 packages.
Am I misssing something or what speaks against 
update.packages(checkBuilt=TRUE) ?

Stefan