On Wed, Apr 26, 2006 at 09:34:52AM -0400, Chi Shen wrote:
> Hi Dirk,
>
> Thank you for answering so quickly. Is there something that I can
> change in the code of rpy locally to temporarily workaround this? Or
> perhaps you have a better suggestion for a workaround.
Yes, sorry, I should have been more explicit -- install r-base-core from
unstable and you will be fine:
$ apt-get -t unstable install r-base-core
provide you have apt's sources point to unstable too. [ Google about 'apt
pinning' if this is new to you --- very powerful tool to have for situations
like this.
When I did this a few days ago it also upgraded my libc6 -- but fear not, it
all works fine on testing.
Cheers, Dirk
> Thanks,
> Chi
>
> On 4/26/06, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
> >
> > tags 364893 + pending
> > quit
> >
> >
> > Hi Chi Shen
> >
> > On 26 April 2006 at 09:00, Chi Shen wrote:
> > | Package: python2.3-rpy
> > | Version: 0.99.2-1
> > |
> > | I have just installed fresh copies of python, R, and rpy. When
> > | importing rpy in a python script, the package fails to import:
> > |
> > | # python
> > | Python 2.3.5 (#2, Mar 6 2006, 10:12:24)
> > | [GCC 4.0.3 20060304 (prerelease) (Debian 4.0.2-10)] on linux2
> > | Type "help", "copyright", "credits" or "license" for more information.
> > | >>> import rpy
> > | RHOME= /usr/lib/R
> > | RVERSION= 2.2.1
> > | RVER= 2021
> > | RUSER= /root
> > | Loading Rpy version 2021 ..
> > | Traceback (most recent call last):
> > | File "<stdin>", line 1, in ?
> > | File "/usr/lib/python2.3/site-packages/rpy.py", line 112, in ?
> > | exec("import _rpy%s as _rpy" % RVER)
> > | File "<string>", line 1, in ?
> > | ImportError: No module named _rpy2021
> > | >>>
> > |
> >
> > This works for me with the current version of R. As you may know, we have
> > been making pre-releases of R 2.3.0 in Debian unstable to help R Core test
> > and debug 2.3.0 before it was actually releases this past Monday.
> >
> > I guess the bug is that I did not declare rpy to depends on r-base-core (>>
> > 2.2.1) -- as it was built with a pre-release of R 2.3.0, maybe I should have
> > prevented it from reaching testing.
> >
> > In any event, the bug will fix itself once R 2.3.0 moves from unstable to
> > testing. For that reason, I will set the 'pending' tag and close it once R
> > 2.3.0 has moved to testing.
> >
> > I'll CC Greg who may have a good idea.
> >
> > Cheers, Dirk
> >
> > | I believe this is similar to #330213.
> > |
> > | All packages are from "testing".
> > |
> > | Linux debian-server-vm 2.6.15-1-486 #2 Mon Mar 6 15:19:16 UTC 2006 i686
> > | GNU/Linux
> > |
> > | libc version: 2.3.6-3
> > |
> >
> > --
> > Hell, there are no rules here - we're trying to accomplish something.
> > -- Thomas A. Edison
> >
--
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]
