search for: etchcran

...ackages Hit http://ftp.au.debian.org etch Release Get:5 http://ftp.au.debian.org testing Release [78.3kB] Get:6 http://ftp.au.debian.org unstable Release [94.4kB] Then my apt-get upgrade complains about: Failed to fetch http://cran.ms.unimelb.edu.au/bin/linux/debian/etch-cran/r-base-core_2.9.0-1~etchcran.1_amd64.deb 404 Not Found Failed to fetch http://cran.ms.unimelb.edu.au/bin/linux/debian/etch-cran/r-cran-rodbc_1.2.5-1~etchcran.2.9.0_amd64.deb 404 Not Found Failed to fetch http://cran.ms.unimelb.edu.au/bin/linux/debian/etch-cran/r-mathlib_2.9.0-1~etchcran.1_amd64.deb 404 Not Found E: Una...

I have recently upgraded to Ubuntu Gutsy and, for the first time, am using a 64-bit installation. After failing miserably to install R from source, not a problem for me in the past with a 32-bit install, I went the route of using the Debian Etch build. This went smoothly, but I am unable to update my numerous R and BioConductor packages, getting non-zero exit status errors on each package. Is

.... > > | > > > | > It looks like the package and your R version are out of sync. What R > > | > version are you using? Did you get it from Debian like r-cran-rodbc > > | > ? > > | > > | The version of the packages is: > > | r-base-core 2.7.1-1~etchcran.0 > > | r-cran-rodbc 1.1.7-1 1.1.7-1 > > > > Ah, yes, "it is our fault" -- you are using the new R via the CRAN repos > > (which is the Right Thing if you want newer R). > > > > But it turns out that that version is no longer compatible with the RODBC...