Re: Koji Build Failure Due To Dependency EPEL Dependency Issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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 <kevin@xxxxxxxxx> 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 -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux