Bug 2335562

Summary: Please branch and build yq in epel10
Product: [Fedora] Fedora Reporter: Romain Geissler <romain.geissler>
Component: yqAssignee: Michel Lind <michel>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 42CC: go-sig, michel, riehecky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: yq-4.47.1-2.el10_1 yq-4.47.1-2.el10_2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-09-02 01:06:27 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:

Description Romain Geissler 2025-01-04 13:35:44 UTC
Hi,

Please branch and build yq in epel10.

Reproducible: Always

Comment 1 Fedora Admin user for bugzilla script actions 2025-01-27 01:48:30 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Romain Geissler 2025-02-20 23:47:40 UTC
Checking right now, it seems we do miss many go dependancies:

No matching package to install: 'golang(github.com/a8m/envsubst/parse)'
No matching package to install: 'golang(github.com/elliotchance/orderedmap)'
No matching package to install: 'golang(github.com/goccy/go-json)'
No matching package to install: 'golang(github.com/goccy/go-yaml)'
No matching package to install: 'golang(github.com/goccy/go-yaml/ast)'
No matching package to install: 'golang(github.com/goccy/go-yaml/lexer)'
No matching package to install: 'golang(github.com/goccy/go-yaml/printer)'
No matching package to install: 'golang(github.com/goccy/go-yaml/token)'
No matching package to install: 'golang(github.com/jinzhu/copier)'
No matching package to install: 'golang(github.com/pkg/diff)'
No matching package to install: 'golang(github.com/pkg/diff/write)'
No matching package to install: 'golang(github.com/yuin/gopher-lua)'
No matching package to install: 'golang(golang.org/x/net/html/charset)'
No matching package to install: 'golang(golang.org/x/text/unicode/norm)'
No matching package to install: 'golang(gopkg.in/op/go-logging.v1)'

Comment 3 Aoife Moloney 2025-02-26 13:21:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 4 Romain Geissler 2025-07-28 18:49:50 UTC
These dependencies can be avoided if we migrate to go-vendor-tools. Two pending pull requests are already available, targetting rawhide.

Comment 5 Romain Geissler 2025-08-29 12:06:18 UTC
*** Bug 2388662 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2025-08-29 14:41:05 UTC
FEDORA-EPEL-2025-9c2c6608ee (yq-4.47.1-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9c2c6608ee

Comment 7 Fedora Update System 2025-08-30 00:21:51 UTC
FEDORA-EPEL-2025-60ad5cf1c5 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-60ad5cf1c5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-08-30 04:00:48 UTC
FEDORA-EPEL-2025-9c2c6608ee has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9c2c6608ee

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-09-02 01:06:27 UTC
FEDORA-EPEL-2025-9c2c6608ee (yq-4.47.1-2.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-09-07 00:24:27 UTC
FEDORA-EPEL-2025-60ad5cf1c5 (yq-4.47.1-2.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.