Bug 2443052 - Latest two chromium builds are missing from epel10 branch
Summary: Latest two chromium builds are missing from epel10 branch
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: chromium
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-26 17:55 UTC by Tuomo Soini
Modified: 2026-02-27 08:52 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:
than: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-3232 0 None None None 2026-02-27 08:52:37 UTC

Description Tuomo Soini 2026-02-26 17:55:54 UTC
Description of problem:

Latest two builds of chromium:

https://koji.fedoraproject.org/koji/buildinfo?buildID=2946339

and

https://src.fedoraproject.org/rpms/chromium/commits/rawhide

Are missing build for epel10 branch.

According upgrade_path_policy epel10 branch need to be the primary build target for epel10*

https://docs.fedoraproject.org/en-US/epel/epel-policy/#upgrade_path_policy

Comment 1 Carl George 🤠 2026-02-26 18:58:10 UTC
On a related note, I noticed that chromium-145.0.7632.109-1.el10_2 was created during the mass branching window.

2026-02-23 15:23 UTC - branching started
2026-02-23 17:34 UTC - chromium build started
2026-02-23 22:33 UTC - branching finished
2026-02-24 00:54 UTC - chromium build finished

During that time we temporarily removed the epel10-candidate target (what is used when you run `fedpkg build` from the epel10 branch), so I'm curious how this build was created?

https://koji.fedoraproject.org/koji/buildinfo?buildID=2946339


Note You need to log in before you can comment on or make changes to this bug.