Bug 571441
| Summary: | Please do not push incompatible changes into EPEL | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Lubomir Rintel <lkundrak> |
| Component: | mock | Assignee: | David Cantrell <dcantrell> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | el5 | CC: | dcantrell, mebrown, williams |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | mock-1.0.7-1.el5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-04-26 23:26:44 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: | |||
|
Description
Lubomir Rintel
2010-03-08 14:47:09 UTC
(In reply to comment #0) > If not, please just > acknowledge that you're okay with EPEL policies and close this... Well, I'm not really sure if there's a policy for this. Probably s/policies/customs/ ... In hindsight this probably wasn't the best idea to push, however I was not expecting many people to have many custom configs, and would have noticed the .rpmnew file to look into. We have a problem though. The default will either be acceptable for EPEL or acceptable for Fedora, but it can't work for both, so one set has to be overridden in config files. What can we do here? Is there anything wrong with pushing a package with different default into EPEL than into Fedora? By the way createrepo_on_rpms could also be False by default, since it breaks setups where two concurrently running mocks share the same resultdir (not questioning the sanity of such setup, it's still a regression in behavior). (In reply to comment #3) > Is there anything wrong with pushing a package with different default into EPEL > than into Fedora? That doesn't work, because if you used your EL5 box to build Fedora packages, the fedora build root configs would all have to be modified. The command in question is ran /inside/ the buildroot, so it's not a matter of what host it's ran on, it's a matter of what contents are inside the buildroot. (In reply to comment #4) > By the way createrepo_on_rpms could also be False by default, since it breaks > setups where two concurrently running mocks share the same resultdir (not > questioning the sanity of such setup, it's still a regression in behavior). Yeah, this wasn't well thought through on my part, I'm going to disable it by default at least in EL5, maybe the released Feodras too, and only leave it enabled on rawhide. mock-1.0.7-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/mock-1.0.7-1.el5 mock-1.0.7-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/mock-1.0.7-1.el5 mock-1.0.7-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |