Bug 2077742
| Summary: | KeePassXC needs rebuild for EPEL 8 Next due to Qt Upgrade | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Christian Dersch <lupinix.fedora> |
| Component: | keepassxc | Assignee: | Mukundan Ragavan <nonamedotc> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel8 | CC: | germano.massullo, nonamedotc |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | keepassxc-2.7.1-3.el8.next | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-08 04:34:35 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: | |||
|
Description
Christian Dersch
2022-04-22 06:01:48 UTC
To everybody reading. Please help me fixing the epel8 / epel8-next build because I am very busy at the moment. Please commit changes to rawhide and then git checkout epel8 && git merge -X theirs rawhide && git push && fedpkg build --nowait this looks like something needing just a rebuild. I will take a look. FEDORA-EPEL-NEXT-2022-db08a8eb9e has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-db08a8eb9e FEDORA-EPEL-NEXT-2022-db08a8eb9e has been pushed to the Fedora EPEL 8 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-db08a8eb9e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-NEXT-2022-db08a8eb9e has been pushed to the Fedora EPEL 8 Next stable repository. If problem still persists, please make note of it in this bug report. |