COPR builds against CentOS, EPEL builds against RHEL, which can lead to
differences. Bringing in the EPEL list to see what others have to say.
But my RHEL7 seven machine can see it:
python2-oauthlib.noarch 2.0.1-8.el7 rhel-7-server-rpms
On 2/23/19 2:36 PM, Chris wrote:
> Perhaps a link to the koji build might be helpful?
Certainly,
Here is a working Copr link:
https://copr.fedorainfracloud.org/coprs/build/861900/
Same .src.rpm, here is a failing Koji one:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32993375
Here is the COPR post output:
copr-cli build apprise python-apprise-0.7.3-1.el7.nuxref.src.rpm
Uploading package python-apprise-0.7.3-1.el7.nuxref.src.rpm
100% |################################| 589kB 1.4MB/s eta 0:00:00
Build was added to apprise:
https://copr.fedorainfracloud.org/coprs/build/861900/
Created builds: 861900
Watching build(s): (this may be safely interrupted)
15:58:20 Build 861900: pending
15:58:51 Build 861900: running
16:02:25 Build 861900: succeeded
Where as here is the Koji one:
koji build --scratch epel7 python-apprise-0.7.3-1.el7.nuxref.src.rpm
Uploading srpm: python-apprise-0.7.3-1.el7.nuxref.src.rpm
[====================================] 100% 00:00:00 566.16 KiB 756.73
KiB/sec
Created task: 32993375
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=32993375
Watching tasks (this may be safely interrupted)...
32993375 build (epel7, python-apprise-0.7.3-1.el7.nuxref.src.rpm): free
32993375 build (epel7, python-apprise-0.7.3-1.el7.nuxref.src.rpm): free
-> open (buildvm-ppc64-06.ppc.fedoraproject.org
<http://buildvm-ppc64-06.ppc.fedoraproject.org>)
32993376 buildArch (python-apprise-0.7.3-1.el7.nuxref.src.rpm,
noarch): open (buildvm-28.phx2.fedoraproject.org
<http://buildvm-28.phx2.fedoraproject.org>)
32993376 buildArch (python-apprise-0.7.3-1.el7.nuxref.src.rpm,
noarch): open (buildvm-28.phx2.fedoraproject.org
<http://buildvm-28.phx2.fedoraproject.org>) -> FAILED: BuildError: error
building package (arch noarch), mock exited with status 30; see root.log
for more information
0 free 1 open 0 done 1 failed
32993375 build (epel7, python-apprise-0.7.3-1.el7.nuxref.src.rpm): open
(buildvm-ppc64-06.ppc.fedoraproject.org
<http://buildvm-ppc64-06.ppc.fedoraproject.org>) -> FAILED: BuildError:
error building package (arch noarch), mock exited with status 30; see
root.log for more information
0 free 0 open 0 done 2 failed
32993375 build (epel7, python-apprise-0.7.3-1.el7.nuxref.src.rpm) failed
Chris
On Sat, Feb 23, 2019 at 4:29 PM Orion Poplawski <orion@xxxxxxxx
<mailto:orion@xxxxxxxx>> wrote:
On 2/23/19 1:02 PM, Chris wrote:
> The error:
>
> DEBUG util.py:490: BUILDSTDERR: Error:
> DEBUG util.py:490: BUILDSTDERR: Problem: conflicting requests
> DEBUG util.py:490: BUILDSTDERR: - nothing provides
python2-oauthlib needed by python2-requests-oauthlib-0.8.0-5.el7.noarch
> DEBUG util.py:634: Child return code was: 1
>
> This same package builds fine using copr (done so here):
> https://copr.fedorainfracloud.org/coprs/lead2gold/apprise/
>
> The spec file entry (that works fine for epel7 on Copr) is:
> BuildRequires: python2-requests-oauthlib
> BuildRequires: python2-oauthlib
>
> This entry just produces an error that all requirements couldn't
be met
> and the scratch build aborts then too.
> BuildRequires: python-oauthlib
>
> It appears to be an upstream issue... a missing entry in the
> python-oauthlib such as:
> Provides: python2-oauthlib
>
> I originally thought maybe i should be filing an issue with the
oauthlib
> group, but then if that were the case, it wouldn't have worked
perfectly
> fine on Copr.
>
> Thoughts? Advice?
>
> Chris
Perhaps a link to the koji build might be helpful?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxx <mailto:orion@xxxxxxxx>
Boulder, CO 80301 https://www.nwra.com/
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxx
Boulder, CO 80301 https://www.nwra.com/
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
