Bug 1485628
Summary: | CQRLOG-2.1.0 is available | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | AsciiWolf <mail> | ||||||||
Component: | cqrlog | Assignee: | Richard Shaw <hobbes1069> | ||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | rawhide | CC: | hobbes1069, tscofield | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2017-12-31 17:18:26 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: | 1491788, 1517323 | ||||||||||
Bug Blocks: | |||||||||||
Attachments: |
|
Description
AsciiWolf
2017-08-26 12:20:30 UTC
I have built an RPM for fc26 for cqrlog-2.1.0, attaching spec file, and changes made to patch files. The RPM build, and the program launches, but not further testing has been done. Created attachment 1324319 [details]
Spec file for cqrlog 2.1.0 on fc26
Created attachment 1324320 [details]
Updated patch file
Created attachment 1324322 [details]
Updated desktop patch file
The problem I've been having is upstream seems to have broken debug builds which are required. it has a debug build target but it doesn't work... Any news? Not until the blocker bugs are fixed. I've got a bug report in on Hedgewars too but haven't heard anything. It looks like cqrlog was just updated to 2.2.0 and I don't get any failures when doing a make debug. The debug binary seems to be the same as the default binary, you just add a command line parameter of "debug=1" to enable the debug output. The problem is the arm build which I'm considering disabling for now to work around the problem since I haven't gotten a single response to my two bug reports from the maintainers. I've disabled arm builds for now and built 2.2.0. |