| Summary: | require new RPM functionality (patch) in build system for Fedora 17 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kay Sievers <kay> |
| Component: | koji | Assignee: | Dennis Gilmore <dennis> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | dcantrell, dennis, harald, mikem |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 14:01:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Kay Sievers
2011-12-21 15:42:57 UTC
In the build system, we use rpm (via yum and mock) to install our chroots for building in. Each build gets a freshly installed chroot. They are never recycled. I think this use counts as a case of "new installation," which this patch claims to not be required for. Are you still sure this is required in the build system? If so please explain why in more detail. RPM will export a 'virtual' rpmlib() provides, where filesystem.rpm will depend on. The rpmlib() thing is evaluated at runtime before the RPM transaction is started. This acts as a guard, and makes sure, that filesystem.rpm >= 3 can not be installed on systems which are not freshly installed or have not been converted to match the new layout. If RPM in the buildroot can not provide the rpmlib() stuff, filesystem.rpm from Fedora 17 can not be installed in the buildroot, unless the initial buildroot setup uses --nodeps or a special filsesystem.rpm for the buildsystem is used. Any ideas how to solve that problem? we would need a patched rpm on the buildserver This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |