[EPEL-devel] Re: Koji Build Failure Due To Dependency EPEL Dependency Issue

2019-03-09 Thread Chris 
Thanks a lot Kevin!

I can confirm it built perfectly! (ref
https://koji.fedoraproject.org/koji/taskinfo?taskID=33328352)

I truly appreciate your help!

Chris

On Sat, Mar 9, 2019 at 1:16 AM Kevin Fenzi  wrote:

> On 3/8/19 6:01 PM, Chris wrote:
> > Hi guys,
> >
> > I apologize if this is a bit premature to revisit this subject.  The
> thing
> > is, the releng ticket Stephen created (
> https://pagure.io/releng/issue/8185)
> > based on my Bugzilla ticket (
> > https://bugzilla.redhat.com/show_bug.cgi?id=1684830) got closed and
> marked
> > resolved, but the build process still continues to fail.
> >
> > Recent Koji Build Fail Source:
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=33310604
> >
> > I sat on this for a week thinking maybe it just took time for this change
> > to propagate, but now that this was week #2 and it was still failing... i
> > should bother you all again :).
> >
> > Is this a RedHat issue? Perhaps just waiting for the Bugzilla issue to
> > close will actually rectify my issue?  i realize this can take months;
> but
> > it's a perfectly acceptable answer.  I guess i'm just looking for closure
> > at this point. I'd love to share my app with the rest of the fedora
> > community.
> >
> > Thanks in advance!
>
> Sorry this has been a pain. ;(
>
> Anyhow, it did get blocked but there was still a version of the package
> tagged into epel7 so that was messing things up. I untagged that one and
> (I hope you don't mind) resubmitted your scratch build... and now it
> completes. :)
>
> So, you should be all good now I hope.
>
> kevin
>
>
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Koji Build Failure Due To Dependency EPEL Dependency Issue

2019-03-08 Thread Kevin Fenzi 
On 3/8/19 6:01 PM, Chris wrote:
> Hi guys,
> 
> I apologize if this is a bit premature to revisit this subject.  The thing
> is, the releng ticket Stephen created (https://pagure.io/releng/issue/8185)
> based on my Bugzilla ticket (
> https://bugzilla.redhat.com/show_bug.cgi?id=1684830) got closed and marked
> resolved, but the build process still continues to fail.
> 
> Recent Koji Build Fail Source:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=33310604
> 
> I sat on this for a week thinking maybe it just took time for this change
> to propagate, but now that this was week #2 and it was still failing... i
> should bother you all again :).
> 
> Is this a RedHat issue? Perhaps just waiting for the Bugzilla issue to
> close will actually rectify my issue?  i realize this can take months; but
> it's a perfectly acceptable answer.  I guess i'm just looking for closure
> at this point. I'd love to share my app with the rest of the fedora
> community.
> 
> Thanks in advance!

Sorry this has been a pain. ;(

Anyhow, it did get blocked but there was still a version of the package
tagged into epel7 so that was messing things up. I untagged that one and
(I hope you don't mind) resubmitted your scratch build... and now it
completes. :)

So, you should be all good now I hope.

kevin




signature.asc
Description: OpenPGP digital signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Koji Build Failure Due To Dependency EPEL Dependency Issue

2019-03-08 Thread Chris 
Hi guys,

I apologize if this is a bit premature to revisit this subject.  The thing
is, the releng ticket Stephen created (https://pagure.io/releng/issue/8185)
based on my Bugzilla ticket (
https://bugzilla.redhat.com/show_bug.cgi?id=1684830) got closed and marked
resolved, but the build process still continues to fail.

Recent Koji Build Fail Source:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33310604

I sat on this for a week thinking maybe it just took time for this change
to propagate, but now that this was week #2 and it was still failing... i
should bother you all again :).

Is this a RedHat issue? Perhaps just waiting for the Bugzilla issue to
close will actually rectify my issue?  i realize this can take months; but
it's a perfectly acceptable answer.  I guess i'm just looking for closure
at this point. I'd love to share my app with the rest of the fedora
community.

Thanks in advance!

Chris



On Sat, Mar 2, 2019 at 4:46 PM Stephen John Smoogen 
wrote:

> I have created https://pagure.io/releng/issue/8185 for the releng
> ticket and referenced the bugzilla.
>
> On Sat, 2 Mar 2019 at 16:23, Chris  wrote:
> >
> > > Can you file a releng ticket to retire the epel7 one?
> > > Thats what needs to happen here.
> >
> > Thank you (and everyone else) very much for your fast responses and
> help!  I created https://bugzilla.redhat.com/show_bug.cgi?id=1684830
> which hopefully covers what was requested of me. :)
> >
> > Chris
> >
> >
> > On Sat, Mar 2, 2019 at 3:00 PM Kevin Fenzi  wrote:
> >>
> >> On 3/2/19 10:22 AM, Chris wrote:
> >> > Hi everyone,
> >> >
> >> > I just wanted to see if anyone had any idea why the EPEL7 repository
> would
> >> > not identify python2-oauthlib package correctly?  It almost appears as
> >> > though the EPEL repository is broken (has been for at least a week -
> maybe
> >> > longer) 'with respect to the this package specifically'.
> >> >
> >> > Here is a failed koji build:
> >> > https://koji.fedoraproject.org/koji/taskinfo?taskID=33139296
> >> >
> >> > If i build using COPR (link:
> >> > https://copr.fedorainfracloud.org/coprs/build/861900/) everything
> works
> >> > fantastic; so it's very specific to how the EPEL7 repositories are
> sourced
> >> > via Koji.
> >> >
> >> > The Koji error i get is:
> >> >
> >> > DEBUG util.py:490:  BUILDSTDERR: No matching package to install:
> >> > 'python2-oauthlib'
> >> > DEBUG util.py:490:  BUILDSTDERR: Not all dependencies satisfied
> >> > DEBUG util.py:490:  BUILDSTDERR: Error: Some packages could not be
> found.
> >> >
> >> >
> >> > Fedora and RedHat based repositories seem unaffected and correctly
> identify
> >> > python2-oauthlib and python3-oauthlib in their respected repositories.
> >> >
> >> > Any thoughts or advice?
> >>
> >> This is because python-oauthlib is in both epel7 and rhel7 base repo.
> >>
> >> Koji operates on source packages, so when both epel7 and rhel7 have the
> >> same package name, epel7 wins. The epel7 python-oauthlib package does
> >> not provide a python2-oauthlib subpackage (it only has python-ouathlib).
> >> Because it's using the epel7 one, it ignores everything the rhel7 one
> >> creates, so you don't get the python2-oauthlib from there either.
> >>
> >> In Copr the newest package wins, so you get the rhel7 one because it's
> >> much newer than the old epel7 one.
> >>
> >> Can you file a releng ticket to retire the epel7 one?
> >> Thats what needs to happen here.
> >>
> >> kevin
> >>
> >> ___
> >> devel mailing list -- de...@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> 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/de...@lists.fedoraproject.org
> >
> > ___
> > devel mailing list -- de...@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > 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/de...@lists.fedoraproject.org
>
>
>
> --
> Stephen J Smoogen.
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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/de...@lists.fedoraproject.org
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:

[EPEL-devel] Re: Koji Build Failure Due To Dependency EPEL Dependency Issue

2019-02-23 Thread Orion Poplawski 
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 
)
   32993376 buildArch (python-apprise-0.7.3-1.el7.nuxref.src.rpm, 
noarch): open (buildvm-28.phx2.fedoraproject.org 
)
   32993376 buildArch (python-apprise-0.7.3-1.el7.nuxref.src.rpm, 
noarch): open (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 
) -> 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 > 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 or...@nwra.com 
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   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org