Bug 1823415 - uboot-tools-2020.04 is available
Summary: uboot-tools-2020.04 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
Depends On:
Blocks: F32FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2020-04-13 15:57 UTC by Upstream Release Monitoring
Modified: 2020-04-14 22:31 UTC (History)
9 users (show)

Fixed In Version: uboot-tools-2020.04-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 22:31:14 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-04-13 15:57:41 UTC
Latest upstream release: 2020.04
Current version/release in rawhide: 2020.04-0.7.rc5.fc33
URL: http://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://fedoraproject.org/wiki/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/

Comment 1 Upstream Release Monitoring 2020-04-13 15:57:52 UTC
The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you.  Please use URLs in your Source declarations if possible.

- arm-boards
- arm-chromebooks
- aarch64-boards
- aarch64-chromebooks
- 10-devicetree.install

Comment 2 Fedora Update System 2020-04-14 12:59:50 UTC
FEDORA-2020-ac1b7d4f91 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ac1b7d4f91

Comment 3 Fedora Blocker Bugs Application 2020-04-14 13:35:34 UTC
Proposed as a Blocker for 32-final by Fedora user pbrobinson using the blocker tracking app because:

 Update U-Boot to the GA 2020.04 release. We're already at the 2020.04 RC5 release but the upstream was delayed by a week due to some issues and hence we missed freeze.

Fixes some issues for us on some arm devices, is a very small delta from rc5 to GA. Would like to also ship the GA as it causes less confusion for users.

Did consider last week going back to 2020.01, the last stable release prior but the work required and change difference from jumping forward from the rc5 to GA was less risk,

Comment 4 Ben Cotton 2020-04-14 14:28:59 UTC
-1 blocker, +1 FE (in case the current RC is no-go)

I don't see that this violates any release criteria, but it would be good to get it in if we have to cut another compose.

Comment 5 Adam Williamson 2020-04-14 14:49:26 UTC
-1/+1, same reason as Ben, unless a clearer reason why this should block the release is given.

Comment 6 Stephen Gallagher 2020-04-14 16:07:59 UTC
-1 blocker, +1 FE as above

Comment 7 Fedora Update System 2020-04-14 16:50:40 UTC
FEDORA-2020-ac1b7d4f91 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ac1b7d4f91`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ac1b7d4f91

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

Comment 8 Adam Williamson 2020-04-14 17:08:28 UTC
That's -3/+3, updating status.

Comment 9 Fedora Update System 2020-04-14 22:31:14 UTC
FEDORA-2020-ac1b7d4f91 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


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