Bug 1759358
| Summary: | uboot-tools-2019.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: | awilliam, dan, dennis, jdisnard, kevin, mboddu, pbrobinson, robatino |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | uboot-tools-2019.10-2.fc31 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-11 23:18:13 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: | |||
| Bug Blocks: | 1644939 | ||
|
Description
Upstream Release Monitoring
2019-10-07 23:24:43 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 FEDORA-2019-d9b994c6bc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9b994c6bc Proposed as a Blocker for 31-final by Fedora user pbrobinson using the blocker tracking app because: This is the GA release of U-Boot 2019.10. It was released today. We currently have the RC4 pre release of it. This just moves us from the last RC release of 2019.10 to the GA release. This fixes issues on a number of issues on a number of key Arm devices including NXP i.MX6, Rockchips, BeagleBone and Tegra devices. Are you saying that going from RC4 to GA fixes those issues? How bad are the issues? I can see a freeze exception, but unless the uboot we currently have is flat out not booting on a supported device, I don't see that it's a blocker. uboot-tools-2019.10-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9b994c6bc (In reply to Adam Williamson from comment #4) > Are you saying that going from RC4 to GA fixes those issues? How bad are the > issues? > > I can see a freeze exception, but unless the uboot we currently have is flat > out not booting on a supported device, I don't see that it's a blocker. There are devices that don't boot with that U-Boot hence the request for Blocker. FEDORA-2019-d9b994c6bc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9b994c6bc uboot-tools-2019.10-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9b994c6bc I'd like to know *which* devices and if they're on the supported platforms list before voting on blocker, but certainly +1 FE if it fixes boot issues. (In reply to Adam Williamson from comment #9) > I'd like to know *which* devices and if they're on the supported platforms > list before voting on blocker, but certainly +1 FE if it fixes boot issues. * Rock960 (IoT reference device) * RockPro64, Rock64 and possibly other rockchips devices * Hummingboard2 (and likely it's other related siblings such as various CuBox-i devices) and Wanboard - these are quite widely used ARMv7 devices * Udoo Neo * Possibly a number of other i.MX6 devices we support that I don't have to test * The NVidia Jetson TX series of devices - arm64 based, including the Jetson TX1, TX2 and Nano. At least those, there's a bunch of other possibilities that were fixed that I can't actually verify. Definitely +1 FE. I guess I am a weak +1 blocker too based on some of those devices being on our supported arm hardware list. Based on number of boards its affecting, I am inclined towards +1 Blocker +1 blocker, since it affects an IoT reference device well, the supported hardware page does specify "RockChips based devices" - https://fedoraproject.org/wiki/Architectures/ARM - so I guess I can go +1 on that basis. That's +4ish, so let's say accepted. (In reply to Adam Williamson from comment #15) > well, the supported hardware page does specify "RockChips based devices" - > https://fedoraproject.org/wiki/Architectures/ARM - so I guess I can go +1 on > that basis. That's +4ish, so let's say accepted. The IoT Reference device page explicitly mentions the Rock960: https://docs.fedoraproject.org/en-US/iot/reference-platforms/ The upstream docs git repo for reference: https://pagure.io/fedora-iot/iot-docs/commits/master Sure, but AFAIK IoT is not release blocking. No IoT deliverable is listed at https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking . uboot-tools-2019.10-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |