Bug 417201
| Summary: | unresolved deps from bodhi-server | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Thorsten Leemhuis <fedora> |
| Component: | bodhi | Assignee: | Luke Macken <lmacken> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | el5 | CC: | a.badger, pfrields, tim.lauridsen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-13 01:48:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 425821 | ||
I far as i remember so i bodhi user a recent added command line option to repoquery, i will look into backport it into yum-utils 1.0.x and make a 1.0.5 release, so can bodhi depend on yum-utils-1.0.5 in EPEL5. (In reply to comment #1) > I far as i remember so i bodhi user a recent added command line option to > repoquery, i will look into backport it into yum-utils 1.0.x and make a 1.0.5 > release, so can bodhi depend on yum-utils-1.0.5 in EPEL5. thx tim -- but actually the situation is a bit more complicated: yum-utils will be dropped from EPEL5 soon, as it's now in RHEL since 5.1 and we don#t want to replace it in EPEL. So we'd need to get the patch (once one exists) into RHEL, which I suppose is way more complicated and likely something that will take a while. (In reply to comment #2) > thx tim -- but actually the situation is a bit more complicated: yum-utils will > be dropped from EPEL5 soon, as it's now in RHEL since 5.1 and we don#t want to > replace it in EPEL. > > So we'd need to get the patch (once one exists) into RHEL, which I suppose is > way more complicated and likely something that will take a while. I had forgot about that Luke: how important is the 'repoquery --repofrompath=repo,path' for the bodhi operation, can we live without it ??. Some solutions: 1. distribute a special repoquery with bodhi ( in /usr/share/bodhi), this will remove the yum-utils dependency. 2. remove bodhi from EPEL5, this will not be a good choice. It don't think it make sense to remove the bodhi server parts only, it is the server parts there is most interesting on a EL system. (In reply to comment #3) > Luke: how important is the 'repoquery --repofrompath=repo,path' for the bodhi > operation, can we live without it ??. The --repofrompath is used during the updateinfo.xml.gz generation to get the rpm checksums. However, there is currently a ticket open requesting that we remove them, as they don't seem to be very useful, and it's duplicate information in the repodata. https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/262 So, I'd be happy to remove this strict dependency from bodhi by no longer fetching the checksums. This will also make pushing a lot faster :) Waiting for python-elixir to grow an EL-5 branch. This bug will be resolved soon. I've been using EL-5 bodhi for a while now, with no issues. Closing... |
Not all deps from bodhi-server are in EL5 and EPEL5: package: bodhi-server - 0.4.4-1.el5.noarch from epel5-testing unresolved deps: yum-utils >= 0:1.1.7 mash Note that yum-utils 1.0.4 is part of RHEL since 5.1; I'd say it's unlikely that 1.1.7 makes it into it in the near future Maybe just ship bodhi in EPEL without the server bits?