flash-kernel (3.109) [PTS] [DDPO]

COMMITS: VCS has seen 5 commits since the 3.109 tag

Git: https://salsa.debian.org/installer-team/flash-kernel.git
JSON
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: master
Path: debian/changelog
Repo size: 1523712
Browser: https://salsa.debian.org/installer-team/flash-kernel
Last scan: 2025-08-10 21:11:58+00
Next scan: 2025-08-17 07:09:00+00
Merge requests: 18
CI pipeline status: failed

Debian changelog in Git:

flash-kernel (3.109) unstable; urgency=medium

  [ Heinrich Schuchardt ]
  * flash-kernel.8: describe /etc/default/flash-kernel

  [ D-I role ]
  * [l10n]  Commit changed/added po files (from l10n-sync run at dillon)

  [ Vagrant Cascadian ]
  * Add Pine64 Pinebook.

  [ Johannes Schauer Marin Rodrigues ]
  * add support for MNT Reform 2 with RCORE RK3588 Module

  [ Josua Mayer ]
  * Add machine db entries for solidrun am64 based hummingboard-t

  [ Alex Lowe ]
  * db: add Pine64 Star64 (Closes: #1092359)

  [ Heinrich Schuchardt ]
  * db: add entry for Wandboard rev D1 board

  [ Tobias Heider ]
  * Add X Elite devices:
    HP Omnibook X 14
    Lenovo Yoga Slim 7x
    Asus Vivobook S 15
    Dell XPS 13 9345
    Lenovo Thinkpad T14s Gen6
    Microsoft Surface Laptop 7 variants

  [ Vagrant Cascadian ]
  * flash-kernel.8: Fix spelling of "command".
  * debian/control: Update Standards-Version to 4.7.2.

 -- Vagrant Cascadian <vagrant@debian.org>  Tue, 08 Apr 2025 15:56:42 -0700

This branch is 5 commits ahead of tag 3.109

Git log:

commit ac37bed0db1d6aa834ccb683bfdc62a3e05e97dc
Author: D-I role <debian-boot@lists.debian.org>
Date:   Sun Aug 10 20:20:27 2025 +0000

    [l10n]  Commit changed/added po files (from l10n-sync run at dillon)

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