Bug 2059441
| Summary: | Please branch and build libcbor in epel8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Gary Buhrmaster <gary.buhrmaster> | ||||
| Component: | libcbor | Assignee: | Davide Cavalca <davide> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | epel8 | CC: | alakatos, davide, mtamasko, rsroka, zfridric | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | libcbor-0.7.0-6.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-07-17 02:06:56 UTC | Type: | Bug | ||||
| 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: | 1808766 | ||||||
| Bug Blocks: | 1914423, 2059387 | ||||||
| Attachments: |
|
||||||
|
Description
Gary Buhrmaster
2022-03-01 02:55:37 UTC
Will you be able to branch and build libcbor in epel8? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel8. (In reply to Davide Cavalca from comment #1) > Will you be able to branch and build libcbor in epel8? > The EPEL Packagers SIG would be happy to be a co-maintainer > if you do not wish to build it on epel8. And while I am not sure that I am fully qualified to do so (last I looked, building libcbor on epel8 would require a build without docs due to different dependencies that are not going to be easily met), I am willing to be a co-maintainer in order to get libcbor into epel8 (and therefore libfido2 into epel8). Test copr builds of libcbor (without docs) and libfido2 for epel8 can be found at: https://copr.fedorainfracloud.org/coprs/gtb/libfido2/ Please let us know how you wish to proceed. I note that when I tried to add a "needsinfo" from Marek Tamaskovic (mtamasko) I get a message about the account being disabled. I presume that means that the individual is no longer at RedHat. I am not entirely sure how to proceed (is this an unresponsive maintainer case?). As Jan Frieser (jfrieser) has been assigned the ticket for the newest upstream release in Fedora Rawhide, I am going to add them in as a needinfo user for additional advice as to ways to move forward. And I am also willing to be a co-maintainer of libcbor for Fedora if that will help move things forward. (In reply to Davide Cavalca from comment #1) > Will you be able to branch and build libcbor in epel8? > The EPEL Packagers SIG would be happy to be a co-maintainer > if you do not wish to build it on epel8. Hello, I've modified the settings of the project, so you should be able to add commits to the branches. Users: ... dcavalca (commit) ... Thanks, branch requested: $ fedpkg request-branch epel8 https://pagure.io/releng/fedora-scm-requests/issue/43648 We're missing python3-breathe for this Created attachment 1879528 [details]
Patch for libcbor spec file to exclude docs
While getting python3-breathe into epel8 may be useful in the longer term, the following patch to the libcbor spec file allows it to build without docs for epel, and may be sufficient to allow progress.
FEDORA-EPEL-2022-a80a0e383e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a80a0e383e FEDORA-EPEL-2022-a80a0e383e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a80a0e383e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-a80a0e383e has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. |