On 26 June 2007 at 11:19, captp bdcht wrote:
| Package: python-rpy
| Version: 1.0~rc1-6
|
| In debian-i386 unstable:
| The python rpy module imports a _rpy$RVER
| wrapper module (.so file) where RVER is
| obtained by running R --version (see rpy_tools.py).
|
| Currently R is 2.5.1 but .so file in python-rpy
| is only 2.5.0 such that "import rpy" leads to
Yes, that is a problem each time the R version changes, Will fix, now that R
2.5.1 is about to be released (and that I already made a RC release last
weekend).
| RHOME= /usr/lib/R
| RVERSION= 2.5.1
| RVER= 2051
| RUSER= /home/axel
| Loading Rpy version 2051 ..
| Traceback (most recent call last):
| File "<stdin>", line 1, in ?
| File "/usr/lib/python2.4/site-packages/rpy.py", line 112, in ?
| exec("import _rpy%s as _rpy" % RVER)
| File "<string>", line 1, in ?
| ImportError: No module named _rpy2051
| >>>
|
| Either build python-rpy against R 2.5.1 or
| make python-rpy depend exactly on r-base-core=2.5.0
| not >=2.5.0.
I don't really like these 'hard blockers' but I guess they are preferable to
me breaking your working system with R upgrades.
Thanks for the bug report, Dirk
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
