Bug 1225250

BTW, something similar happened with F21, too.  I had to remove and reinstall sagemath several times and force the proper architecture because yum kept selecting i686.  This is happening with dnf, how, too for this package.

I have the same issue :(

Hi, can you confirm it is working now?

I am afraid the issue is not sagemath but R/rpy or dnf.

You may try to force install of rpy manually before,
or download it first from some mirror and install
with rpm, for example:

http://mirrors.kernel.org/fedora/releases/22/Everything/x86_64/os/Packages/r/rpy-2.5.6-2.fc22.x86_64.rpm

[link may be short lived]

(In reply to Paulo Andrade from comment #3)
> Hi, can you confirm it is working now?
> 
> I am afraid the issue is not sagemath but R/rpy or dnf.
> 
> You may try to force install of rpy manually before,
> or download it first from some mirror and install
> with rpm, for example:
> 
> http://mirrors.kernel.org/fedora/releases/22/Everything/x86_64/os/Packages/r/
> rpy-2.5.6-2.fc22.x86_64.rpm
> 
> [link may be short lived]

Right now it doesn't work. First, I tried to install sagemath with dnf but:
'Error: package sagemath-6.4.1-4.fc22.i686 requires rpy, but none of the providers can be installed'

Then, with rpy: 'Error: package rpy-2.5.6-2.fc22.i686 requires R-core = 3.1.3, but none of the providers can be installed'

I haven't tried to install rpy manually with rpm.

So, rpy-2.5.6-2 is compatible with R-core 3.2, but the RPM's dependencies are incorrect.  Is that what you're saying?

I don't know how to force dnf to install rpy, just not familiar with options, yet.  But, I did find this route: dnf --allowerasing install sagemath.  This sets up a path that dnf will do.  I haven't let it do that, but I just wanted to say that it will do it.  It says it's going to downgrade R* to 3.1.3, then install rpy and sagemath.  Is this a good option?  Or, do you think I'd be better off forcing rpy to install with R 3.2.

Hi Paul,
Sorry for the delay, I checked what is available, and pending updates.
What happens is that an update of R-3.2 did not update rpy.
Previous updates were done updating dependencies, so, this bug
is actually on rpy.
I suggest for the moment to use R 3.1.3 until an rpy that supports
R-3.2 is made available as an update.

I will change component of this bug report.

Hi Paulo,

I also came across this same issue, and dug a bit deeper into it:

1. The rpy-2.5.6 package in repo depends on R-3.1.3, and is not compatible with R-3.2.0. I checked out rpy-2.5.6 from upstream, it compiled and installed, but failed the unittest (python -m rpy2.tests ... ... FAILED (errors=4, skipped=9, expected failures=1) ).
2. The upstream of rpy just updated a new version of rpy-2.6.0 which works fine with R-3.2.0, at least on my box. The unittest also pass (python -m rpy2.tests ... ... OK (skipped=10, expected failures=1) ).
3. BTW, the meta data of rpy package is outdated, the upstream url is now
    https://bitbucket.org/rpy2/rpy2/
  instead of
    https://bitbucket.org/lgautier/rpy2

Hope it helps.


(In reply to Paulo Andrade from comment #6)
> Hi Paul,
> Sorry for the delay, I checked what is available, and pending updates.
> What happens is that an update of R-3.2 did not update rpy.
> Previous updates were done updating dependencies, so, this bug
> is actually on rpy.
> I suggest for the moment to use R 3.1.3 until an rpy that supports
> R-3.2 is made available as an update.
> 
> I will change component of this bug report.

I am closing this report as rpy has been built for F22 for some time. :-)