Bug 1269624
Summary: | bcfg2 does not build correctly anymore | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | bcfg2 | Assignee: | Fabian Affolter <mail> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | dan, dhorak, hannsj_uhl, jkachuck, john, mail, yselkowi |
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: | 2016-07-14 13:20:09 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: | 1267648, 1285484 |
Description
IBM Bug Proxy
2015-10-07 19:03:00 UTC
The EPEL 7 SRPM for bcfg2 https://dl.fedoraproject.org/pub/epel/7/SRPMS/b/bcfg2-1.3.4-1.el7.src.rpm does not build correctly in Mock on s390x. 6 out of 2078 tests failed and prevented RPM from being built in Mock. They are caused by either 1. "NameError: global name 'Bcfg2' is not defined" or 2. "OperationalError: unable to open database file" Some of the tests are skipped because the following modules were not found: 1. django "Ensure that we a) can connect to the database; b) start ... SKIP: Django not found, skipping" 2. augeas "test_BundleNotUpdated (Testlib.TestClient.TestTools.TestPOSIX.TestAugeas.TestPOSIXAugeas) ... SKIP: Python Augeas libraries not found" 3. YAML "test_yaml (Testlib.TestServer.TestPlugins.TestProbes.TestProbeData) ... SKIP: YAML libraries not found, skipping YAML tests" On the build phase of spec file, python was not found when trying to execute setup.py, which could be the root cause of all these errors. The same occurs on aarch64. Note that this package has been retired in Fedora due to FTBFS during the last two Fedora mass rebuilds. If this will not be fixed, it needs to be retired from EPEL as well. (In reply to Yaakov Selkowitz from comment #2) > The same occurs on aarch64. Note that this package has been retired in > Fedora due to FTBFS during the last two Fedora mass rebuilds. If this will > not be fixed, it needs to be retired from EPEL as well. Fabian, In light of the above, do you have any plans to fix this package for Fedora and/or EPEL? Package is retired. |