On 2025-05-01, Vagrant Cascadian wrote: Control: tag 1102690 -pending -patch > Bug #1102690 in flash-kernel reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/installer-team/flash-kernel/-/commit/9817c7cc5c06074a48507497662df123f54f80ec
Well, while that solved the problem, it introduced upgrade problems from older versions with dpkg trigger loops... so removing the patch and pending tags. :( Help? :) live well, vagrant > ------------------------------------------------------------------------ > Avoid a double run of handle_dtb and --force with no kvers > (Closes: #1102690) > > The logic surrounding $kvers deals with three scenarios: kvers is blank > (we want to flash the latest kernel), kvers is non-blank and is the > latest kernel, and kvers is non-blank and is *not* the latest kernel. > > In the second case (typical during a kernel upgrade), f-k runs > handle_dtb twice (redundantly). At the top of main() after checking > kvers is non-blank and then later after checking for --force and whether > kvers is not the latest version. > > The existing logic also permits the (rather nonsensical) case of being > called with --force but with no kernel version specified. This commit > re-works the logic to avoid running handle_dtb redundantly, and to error > out with an appropriate message if called with --force but with no > kernel version. > ------------------------------------------------------------------------ > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/1102690
signature.asc
Description: PGP signature
