Bug 2401964

Summary:	uboot-tools-2025.10 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	uboot-tools	Assignee:	Peter Robinson <pbrobinson>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dan, dennis, jean, jordan, kparal, lruzicka, nrevo, pbrobinson, pwhalen, robatino
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	RejectedBlocker
Fixed In Version:	uboot-tools-2025.10-1.fc44 uboot-tools-2025.10-1.fc43	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-10-14 06:42:36 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 Upstream Release Monitoring 2025-10-06 19:27:06 UTC

Releases retrieved: 2025.10
Upstream release that is considered latest: 2025.10
Current version/release in rawhide: 2025.10-0.7.rc5.fc44
URL: https://www.denx.de/wiki/U-Boot/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/5022/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/uboot-tools

Comment 1 Upstream Release Monitoring 2025-10-06 19:27:12 UTC

Scratch build failed. Details below:

FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/thn-tquxifc2/https://src.fedoraproject.org/repo/pkgs'
Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 206, in build
    output["message"] = self._compare_sources(old_sources, new_sources)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 373, in _compare_sources
    with open(file_path, "rb") as fd:
         ^^^^^^^^^^^^^^^^^^^^^

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 2 Fedora Blocker Bugs Application 2025-10-07 08:53:51 UTC

Proposed as a Blocker for 43-final by Fedora user pbrobinson using the blocker tracking app because:

 The traditional U-Boot GA release bug for arm platforms

Comment 3 Kamil Páral (Red Hat) 2025-10-09 13:12:31 UTC

(In reply to Fedora Blocker Bugs Application from comment #2)
> Proposed as a Blocker for 43-final by Fedora user pbrobinson using the
> blocker tracking app because:
> 
>  The traditional U-Boot GA release bug for arm platforms

Should it be a freeze exception request instead? Why is it a blocker request?

Comment 4 Lukas Ruzicka (Red Hat) 2025-10-13 18:45:34 UTC

AGREED RejectedFinalBlocker

Discussed at the 2025-10-13 (blocker / freeze exception) review meeting:

There's no clear justification why this should be a blocker. At least one problem currently violating our release criteria needs to be shown, in order to accept this update as a blocker. We're open to giving it a freeze exception, if at least some details are provided - what important things are improved that should be part of install media.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-10-13/f43-blocker-review.2025-10-13-16.00.txt

Comment 5 Fedora Update System 2025-10-13 23:38:05 UTC

FEDORA-2025-a367024bc9 (uboot-tools-2025.10-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a367024bc9

Comment 6 Fedora Update System 2025-10-14 06:42:36 UTC

FEDORA-2025-a367024bc9 (uboot-tools-2025.10-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2025-10-14 09:51:08 UTC

FEDORA-2025-5e69656e63 (arm-trusted-firmware-2.13.0-4.fc43 and uboot-tools-2025.10-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e69656e63

Comment 8 Fedora Update System 2025-10-15 01:17:09 UTC

FEDORA-2025-5e69656e63 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5e69656e63`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e69656e63

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

Comment 9 Fedora Update System 2025-10-23 23:53:36 UTC

FEDORA-2025-5e69656e63 (arm-trusted-firmware-2.13.0-4.fc43 and uboot-tools-2025.10-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.