Kernel Build from Custom Git Repo fails with hash-error

Thank you for opening a new issue. To help solve it faster and more easily, please review this check-list, and fill in the sections below. Adapt as needed.

Do not open an issue to request a new feature; instead, post a message to the mailing list.

Note: issues missing any information may get closed without further ado.


Check-list

  • I did not find the issue in the existing issues
  • I can reproduce the issue with unmodified Buildroot from this repository, not from a fork somewhere else
  • I can reproduce the issue on the latest commit of the branch I'm using:
    • master
    • stable (i.e. 20NN.MM.x - please specify)
    • LTS (i.e. 20NN.02.x - please specify)
  • I can reproduce the issue after running make clean; make
  • I attached the full build log file (e.g. make 2>&1 |tee build.log)
  • I attached a minimal defconfig file that can reproduce the issue (make BR2_DEFCONFIG=$(pwd)/issue_defconfig savedefconfig)
  • I also attached the configuration for kconfig-based packages that are enabled (and necessary to reproduce the issue), most notably:
    • busybox
    • linux
    • uclibc
    • uboot

What I did

  • Buildroot commit sha1: Buildroot 2024.08 vs. 2024.02.06 from https://buildroot.org/downloads/
  • Distribution of the build machine: Debian GNU/Linux 12 (bookworm)

Custom Git repository, Kernel source: https://github.com/raspberrypi/linux Custom repository version 1ef86d0


What happensLogAndConfig.ziplinux_tarball

With Buildroot 2024.02.06 the image is compiled without errors. With Buildroot 2024.08 the build fails when trying to bake the Kernel: "GIT_DIR=/home/cellomation/br/dl/linux/git/.git git submodule --quiet foreach 'printf "Deregistering submodule "%s"\n" "{path}" && cd .. && rm -rf "{path##*/}"' GIT_DIR=/home/cellomation/br/dl/linux/git/.git git checkout -f -q '1ef86d0' GIT_DIR=/home/cellomation/br/dl/linux/git/.git git clean -ffdx ERROR: No hash found for linux-1ef86d0-git4.tar.gz"

What was expected

Here, describe the behaviour you expected.


Extra information

Here, you may write additional information that does not fit above