Skip to content

joined R-today

12 messages · Simon Pickett, Liviu Andronic, Dimitri Liakhovitski +3 more

#
Hi,

Check out the FAQ on the home page about installing packages.

You need to
1. Install the package from a local mirror, you can do this from the drop 
down menu ("Install packages")
2. then call the package using "library(name of the package)"

It helps to know where your R library directory is on your computer.

HTH Simon.


----- Original Message ----- 
From: "Bala subramanian" <bala.biophysics at gmail.com>
To: <r-help at r-project.org>
Sent: Tuesday, April 21, 2009 9:34 AM
Subject: [R] joined R-today
#
On Tue, Apr 21, 2009 at 11:57 AM, Bala subramanian
<bala.biophysics at gmail.com> wrote:
Does ncdf depend on netcdf [1]? If so, perhaps it is missing, or is
not up-to-date. Also, it's a good habit to install.packages('ncdf',
dep=TRUE).
Regards,
Liviu

[1] http://www.unidata.ucar.edu/software/netcdf/
#
Try to install from scratch from a different mirror.
Dimitri

On Tue, Apr 21, 2009 at 6:21 AM, Bala subramanian
<bala.biophysics at gmail.com> wrote:

  
    
#
Bala subramanian wrote:
Nothing to do with the download. I think SElinux is getting in your way
(so your unstated system could be RedHat Enterprise Linux?).

Contact your sysadm or google for the error message.

(One of the hits suggests that you might need to run

chcon -t texrel_shlib_t ncdf.so

but, well, no warranties...)

  
    
#
On Apr 21, 2009, at 9:28 AM, Peter Dalgaard wrote:

            
The OP did indicate that F10 was the platform:

   https://stat.ethz.ch/pipermail/r-help/attachments/20090421/65ee5d6e/attachment.pl

so I would agree here that SELinux is almost certainly the culprit as  
it does control relocation.

If you have the SE Troubleshoot daemon running, you should get a  
yellow star/badge symbol on one of your desktop dock panels.  
Typically, if you click on this, it will bring up a dialog window that  
will have some specific suggestions for resolving the problem. You can  
see some visual examples here:

   https://fedoraproject.org/wiki/Design/SETroubleshootUsabilityImprovements

More info on SETroubleshoot here:

   https://fedorahosted.org/setroubleshoot/

HTH,

Marc Schwartz
#
Bala,

I would not advocate disabling SELinux entirely to resolve this issue.  
SELinux is one of the key security features of Fedora Linux and some  
other Linux distributions that have adopted it. It has already been  
demonstrated to be robust with respect to so-called zero-day attacks.

I would first look to take a more surgical approach to resolve this  
particular issue with this package. Using the SETroubleshoot daemon is  
the easiest way to accomplish this as it will provide specific  
instructions.

As with any security approach, there are trade-offs between security  
and usability, but SELinux as a mandatory access control system is  
well worthwhile keeping in place.

BTW, as a future reference, there is a r-sig-fedora list:

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

HTH,

Marc
On Apr 21, 2009, at 9:56 AM, Bala subramanian wrote: