Bug 1384111 - R-core-devel not available on Fedora 26 (Rawhide) builders
Summary: R-core-devel not available on Fedora 26 (Rawhide) builders
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 15:04 UTC by John Ellson
Modified: 2019-04-02 09:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-02 09:30:32 UTC


Attachments (Terms of Use)

Description John Ellson 2016-10-12 15:04:43 UTC
Description of problem:
DEBUG util.py:421:  Error: package R-devel-3.3.1-3.fc26.i686 requires R-core-devel = 3.3.1-3.fc26, but none of the providers can be installed


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. graphviz build
2.
3.

Actual results:
https://copr-be.cloud.fedoraproject.org/results/johnellson/graphviz/fedora-rawhide-x86_64/00464372-graphviz/root.log.gz

Expected results:


Additional info:

Comment 1 Miroslav Suchý 2016-10-13 09:13:38 UTC
Each project is owned by individual user. There is nothing we can do about it.
You have to contact the owner of this project.

Go to:
  https://copr.fedorainfracloud.org/coprs/johnellson/
click on FAS account and once you log in, you should be able to retrieve email of the owner.

Comment 2 John Ellson 2016-10-13 17:39:28 UTC
I am the project owner.

The problem is that the docker machine, or whatever is being used to do the build, is not picking up the package dependencies that are available in Redhat's yum repositories for Rawhide.

The graphviz spec contains:

    BuildRequires: R-devel 

and R-core-devel is supposed to be pulled in as a subdependency, but its missing.


The same rpm build works on a local Rawide host,  so the problem is with the build host.


There seem to be other problems with these Rawhide builders.

Now I have a build that completes in 8min on other distros, but which is still "running" after 50min on the Rawhide builds:


https://copr.fedorainfracloud.org/coprs/johnellson/graphviz/build/464766/

Comment 3 John Ellson 2016-12-20 15:37:53 UTC
I see recent R builds in Koji:
    https://koji.fedoraproject.org/koji/buildinfo?buildID=825702

but I still get the same problem in Copr with Fedora26 builds:
     https://copr.fedorainfracloud.org/coprs/johnellson/graphviz/build/491438/

    DEBUG util.py:421:  Error: package R-devel-3.3.2-3.fc26.i686 requires R-core-devel = 3.3.2-3.fc26, but none of the providers can be installed

Perhaps the issue is that Copr has installed an i686 package ?


This is not a graphviz issue, its either an issue with Copr, or with R.   I need your help directing the issue to the right person.

Comment 4 clime 2017-02-02 12:05:33 UTC
Sorry for late response. Is this still a problem?

Comment 5 Miroslav Suchý 2017-02-02 12:41:30 UTC
I suppose this was the cause:
  https://www.scrye.com/wordpress/nirik/2017/01/21/kojipkgs-what-it-is-and-how-it-works/

Comment 6 Elliott Sales de Andrade 2017-02-17 10:22:58 UTC
I think this is still broken due to a GCC rebuild. See this log [1]:

> DEBUG util.py:435:  Error: nothing provides libgfortran.so.3()(64bit) needed by R-core-3.3.2-4.fc26.x86_64.

However, koji is up to -8 in Rawhide [2] so I'm not sure why it's pulling in such an old version.


[1] https://copr-be.cloud.fedoraproject.org/results/qulogic/IRkernel/fedora-26-x86_64/00513120-R-withr/root.log.gz
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=859245

Comment 8 Pavel Raiskup 2019-04-02 09:30:32 UTC
If I interpret this issue correctly, the build failure was because copr builder
picked a slightly outdated mirror at the time of building your package.  It is
not guaranteed that you'll have the latest built package version available
in Rawhide chroot in copr (we don't do mock --enablerepo local).

The bug 1638048 might be related.  If you feel this should be kept open, please
reopen (I'm new to this bug, so I might have missed something important).

Thank you!


Note You need to log in before you can comment on or make changes to this bug.