Bug 2045178

Summary: R-jqr: FTBFS in Fedora rawhide/f36
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: jqAssignee: Elliott Sales de Andrade <quantum.analyst>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: awilliam, bhills, davide, david, fpercoco, hguemar, jeroenooms, karlthered, lhh, quantum.analyst
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedFreezeException
Fixed In Version: jq-1.6-13.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-14 21:00:53 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: 2017285    
Bug Blocks: 1953784, 1992484, 2045102    
Attachments:
Description Flags
build.log
none
root.log
none
state.log
none
Test case demonstrating broken jq none

Description Fedora Release Engineering 2022-01-25 16:03:52 UTC
R-jqr failed to build from source in Fedora rawhide/f36

https://koji.fedoraproject.org/koji/taskinfo?taskID=81769518


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix R-jqr at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
R-jqr will be orphaned. Before branching of Fedora 37,
R-jqr will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2022-01-25 16:03:56 UTC
Created attachment 1853590 [details]
build.log

Comment 2 Fedora Release Engineering 2022-01-25 16:03:59 UTC
Created attachment 1853591 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-01-25 16:04:00 UTC
Created attachment 1853592 [details]
state.log

Comment 4 Ben Cotton 2022-02-08 21:04:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Elliott Sales de Andrade 2022-02-27 11:20:50 UTC
Created attachment 1863473 [details]
Test case demonstrating broken jq

Comment 6 Elliott Sales de Andrade 2022-02-27 11:21:29 UTC
This is _apparently_ caused by the decimal number patch in jq (cc'd maintainer.)

Attached is a test program that shows the issue. It creates a jq_state, calls jq_compile on an empty string, then on something numeric-ish (...), then again on an empty string. Without the decimal patch, this errors on the second compile, but works again on the second empty string (just as the first empty string). With the decimal patch, the second empty string is totally broken, and calls error_cb with some errors parsing some unrelated file.

Comment 7 Elliott Sales de Andrade 2022-02-27 11:35:10 UTC
https://github.com/stedolan/jq/pull/2400 seems relevant.

Comment 8 Jeroen 2022-03-08 21:08:44 UTC
I confirmed that 2400 fixes the problem. Davide has created a pull request to port this patch into the rpm: https://src.fedoraproject.org/rpms/jq/pull-request/5#

Comment 9 Fedora Update System 2022-03-11 19:28:46 UTC
FEDORA-2022-19b8a22908 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-19b8a22908

Comment 10 Fedora Blocker Bugs Application 2022-03-11 19:34:00 UTC
Proposed as a Freeze Exception for 36-beta by Fedora user dcavalca using the blocker tracking app because:

 This bug fixes a regression in jq and unbreaks R-jqr

Comment 11 Adam Williamson 2022-03-14 16:10:32 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/657 , marking accepted.

Comment 12 Fedora Update System 2022-03-14 21:00:53 UTC
FEDORA-2022-19b8a22908 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.