On 17 September 2013 at 16:15, Yaroslav Halchenko wrote: | Package: python-rpy2 | Version: 2.3.6-1 | Severity: important | | Dear Maintainer, | *** Please consider answering these questions, where appropriate *** | | * What led up to the situation? | | unittesting of python-mvpa2 pkg | | * What exactly did you do (or not do) that was effective (or | ineffective)? | | $> python -c 'import rpy2.robjects' | Error: 'rho' must be an environment not NULL: detected in C-level eval | Segmentation fault | | * What was the outcome of this action? | | segfault | | * What outcome did you expect instead? | | not to segfault ;) | | *** End of the template - remove these lines *** | | this seems to be related to having r-base-core 3.0.1.20130915-1 (ok with | 3.0.1-6) but not sure if that is RPy2's issue or R's, thus filing here as were | produced (R starts fine)
We often need a rebuild for a new R version. And "3.0.1.20130915" is my first build of R 3.0.2 scheduled for Sep 25. Until then, pin your rpy2 to R 3.0.1 from testing. Dirk | | -- System Information: | Debian Release: jessie/sid | APT prefers unstable | APT policy: (500, 'unstable') | Architecture: amd64 (x86_64) | | Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores) | Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) | Shell: /bin/sh linked to /bin/dash | | Versions of packages python-rpy2 depends on: | ii libc6 2.17-92+b1 | ii python 2.7.5-5 | ii python-numpy 1:1.7.1-3 | ii r-base-core 3.0.1.20130915-1 | | python-rpy2 recommends no packages. | | Versions of packages python-rpy2 suggests: | pn python-rpy-docs <none> | | -- no debconf information -- Dirk Eddelbuettel | [email protected] | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
