Skip to content

Installing R-2.2.0 package

5 messages · Dean, David P, Paul Gilbert, Uwe Ligges +1 more

#
Dear list,

I've just installed R-2.2.0 under Solaris and have a question about
installing packages. If a package fails to install for any reason and I go
to install another package, I get this message:

$ R-2.2.0-64bit --vanilla CMD INSTALL ~/srca/cran/RSQLite_0.4-0.tar.gz 
ERROR: failed to lock directory
'/app/openpkg/lib/R-2.2.0-64bit/lib/R/library' for modifying
Try removing '/app/openpkg/lib/R-2.2.0-64bit/lib/R/library/00LOCK'

I can remove the lock directory by hand, and then the next package installs,
but this makes it quite difficult to download and install a batch of
packages from CRAN or Biocondctor! Is this lock directory a new feature with
R-2.2.0? Is there a work around in the R build itself or the installation
scripts?

Much thanks!!!
--------------------- 
David P Dean
Research Informatics
PGRD Groton Labs
(860)-441-5053
david.p.dean at pfizer.com
----------------------------------------------------------------------
LEGAL NOTICE\ Unless expressly stated otherwise, this messag...{{dropped}}
#
Dean, David P wrote:

            
No, not a new feature in R-2.2.0, it has been there for some time now.
After a *successful* installation, the 00LOCK directory should be 
deleted by the installation tools themselves.
After an unsuccessful installation, the installation tools should 
restore the stuff in the 00LOCK directory.
Do you abort the installtion manually (this is the only way I figured 
out how not to remove 00LOCK automatically)?

Uwe Ligges
#
Uwe Ligges wrote:

            
I have the impression the feature behaves slightly differently as of 
R-2.2.0. Now the 00LOCK file is not removed in Solaris when there is an 
unsuccessful install. (In Linux I think it does get removed.)

Paul Gilbert
#
Paul Gilbert wrote:

            
Yes, under both Linux and Windows it is removed.

Can anybody else check on Solaris, please? Or can David Dean debug on 
his machine?

In particular, we need exact system information, because it seems to be 
an OS/platform specific problem.

Uwe Ligges
#
It works on Solaris 8 for me, and this is checked as part of the 
alpha/beta process.

The code is the same on Linux and Solaris, after all, so this would have 
to be a Solaris shell bug.
On Thu, 13 Oct 2005, Uwe Ligges wrote: