[sync request] rpy 1.0~rc1-5 from Debian unstable (main)

Binary package hint: python-rpy

Installation on Ubuntu Feisty (I think this problem is in Edgy too) has version of R 2.4.1. When one installs python-rpy, however, it only intalls _rpy2040.so, which is useless for this version of R. The solution is to include _rpy2041.so in the package.

Rpy email thread below.

------------------------------------------------------------------------------------------------------

> No, that doesn't seem to be it. Both folders only have _rpy2040.so, when my
> version of R is clearly 2.4.1. My python2.5 site-packages actually has more
> files related to rpy than 2.4.
>
> In any case, this is a simple problem to remedy. Just include the
> _rpy2041.so with the package. I imagine it will help a lot of people out.

Yes, that is what we do for Debian.

If you file an Ubuntu bug report for rpy, an updated (and corrected)
Ubuntu package may get produced,

Dirk

> j
> -------------------------------------------------------------------------------------------------
> Try using python2.4, not python2.5. Python 2.5 is not yet suppported by the
>
> automated build of Python modules from Python module sources.
>
> At least not on Debian. I am not entirely sure exactly what Ubuntu does to
> the RPy and R packages I maintain for Debina ... as they never communicate
> back. It *may* well be that they try to support Python 2.5 automatically; I
> just don't know if include RPy. On my Debian testing system, the directory
>
> /usr/lib/python2.5/site-packages
>
> is empty whereas
>
> /usr/lib/python2.4/site-packages
>
> contains the on-install autobuilt files, incl rpy's. What does Feisty have?
>
> Dirk
> | The rpy2041 module does not exist. My solution is to google an rpm with
> the
> | file inside, extract it, and place it in the approprate folder on my
> | installation. Everything works after that. I do not, however, think this
> | should be the default behaviour.
> |