vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 9186319d71aabb7f036237a1168a6544d7e0c114
Author: Dave Jones <dave.jones@canonical.com>
Date: Mon Mar 6 15:49:20 2023 +0000
Defer if selected kernel is not fully "installed"
When flash-kernel runs as part of a kernel installation, that kernel may
not be in the fully "installed" state. If it's a newly installed kernel,
it may also be in "triggers-pending" in which case, while the symlinks
for vmlinuz-$ver and initrd.img-$ver exist, the initrd itself does not
yet exist (because the initramfs-tools trigger has not yet run, so the
initrd symlink is "dead").
In this case, depending on the "method" selected for the board, the f-k
run may crash (aborting apt), or may continue but flash a non-functional
boot setup. In the latter case, this usually corrects itself with a
later run of f-k but it still potentially leaves the system in an
unbootable state for some portion of an apt run (which is not ideal).
This commit adds a check on the status of the package which owns the
kernel version requested to be installed. If it is not fully
"installed", it defers the f-k run (under the assumption it will become
installed at some point in the apt run). This can be overridden with
"--force". Tests are included for the new function.
Related issues: LP: #2007827, LP: #1861292, Debian bug #781742
commit 9817c7cc5c06074a48507497662df123f54f80ec
Author: Dave Jones <dave.jones@canonical.com>
Date: Mon Mar 6 14:01:59 2023 +0000
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.
commit 1bc2d294ef32339b8be020cfb94705c0f651ffa7
Author: Dave Jones <dave.jones@canonical.com>
Date: Mon Mar 6 13:53:51 2023 +0000
Always run flash-kernel
When both flash-kernel and the kernel are upgraded together, it is
possible that the f-k trigger is unconfigured when the kernel attempts
to fire it, resulting in the invocation being lost. This change ensures
that the f-k trigger is set during *all* maintscript operations.
Related issue: LP: #1667742
commit 6da92d95fd28b39ecfbeff7c5c6907a4aa5a91fe
Author: Johannes Schauer Marin Rodrigues <josch@debian.org>
Date: Tue Apr 22 06:39:23 2025 +0200
db/all.db: add MNT Reform 2 with BPI-CM4 Module
![[bug history graph]](https://qa.debian.org/data/bts/graphs/f/flash-kernel.png){kind=link}