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
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
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
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
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
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
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
> 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,
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
On Sat, 2 Mar 2019 at 13:22, 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)
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
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
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:
13 matches
Mail list logo