a) I'm having some trouble with this change in d/control:
-Package: u-boot-amlogic
+Package: u-boot-amlogic-binaries
Architecture: arm64
+Section: contrib/admin
Multi-Arch: same
Depends: ${misc:Depends}
+Breaks: u-boot-amlogic (<= 2024.01+dfsg-3)
+Replaces: u-boot-amlogic (<= 2024.01+dfsg-3)
Recommends: arm-trusted-firmware [arm64]
Description: A boot loader for amlogic systems
Das U-Boot is a cross-platform bootloader for embedded systems,
@@ -73,7 +83,7 @@ Description: A boot loader for amlogic systems
This package includes boot loaders for various amlogic platforms.
.
Included platforms:
- ${u-boot-amlogic:platforms}
+ ${u-boot-amlogic-binaries:platforms}
That is essentially removing u-boot-amlogic without a Provides in the new
u-boot-amlogic-binaries package. That seems to be case #11 of
PackageTransitions[1], but that is across distro release boundaries, not in a
stable update.
There are no reverse-depends of u-boot-amlogic/arm64 in noble, but we
can't say if something out of the archive is installing it. There could
be user scripts, third party tools, etc, depending on this package, and
this SRU is removing it.
b) The test plan is inadequate for the scope of this update
Specifically:
b1) The replacement of u-boot-amlogic with u-boot-amlogic-binaries. Are
these equivalent? Won't we need changes to the tooling that produces
images to now take into account the new package? Besides the point of
there being perhaps a Provides, we should have at least an upgrade smoke
test.
b2) This is a new upstream version, also supposedly affecting many arm64
and armhf boards, and nowhere do I see arm64/armhf tests, just a riscV64
verification in comment #12. What can we do here to test armhf and arm64
boards?
Binaries were released to updates for all architectures except arm64 and armhf,
because of the NEW packages introduced to those two architectures. So as this
SRU stands now, it's inconsistent in terms of binary package availability, but
we also haven't potentially regressed arm64 and armhf.
Point (a) might need a new source upload. Point (b) is about testing and
can be done without a new upload (unless it uncovers bugs).
1. https://wiki.debian.org/PackageTransition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110301
Title:
[SRU] Backport u-boot 2025.01-3 to Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2110301/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
