Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
Martin Steigerwald - 13.02.24, 00:24:35 CET: > This breaks compiling my own kernel with: > > time eatmydata make -j16 bindeb-pkg LOCALVERSION=-t14 Work-around: […]etc/apt/preferences.d% cat kmod Explanation: Bug #1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory Package: kmod libkmod2 Pin: version * Pin-Priority: -3 Install kmod and libkmod2 31-1 from snapshot.debian.org. Best, -- Martin
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
Hi! This breaks compiling my own kernel with: time eatmydata make -j16 bindeb-pkg LOCALVERSION=-t14 Likely going to downgrade and pin kmod to a working version as I am seriously fed up with usr-merge related bugs. (Yeah, it is called unstable for a reason and if I use it unstable is what I may get. But I really don't see how any possible benefit justifies that immense and error-prone effort. Anyway it is not me doing that work.) Best, -- Martin
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
Control: reassign -1 kmod On Mon, Feb 12, 2024 at 10:37:46PM +0100, Marco d'Itri wrote: > On Feb 12, Salvatore Bonaccorso wrote: > > --with-module-directory=/usr/lib/modules > I can revert it if it causes too much trouble, but maybe this is just > the right time to switch the kernel packages to /usr/lib/modules/ as well? We can't change this on our own. The usage of $BASE/lib/modules is baked in pretty deep into the kernel build. | MODLIB = $(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE) and | depmod -b "$INSTALL_MOD_PATH" depmod need to learn to work with MODLIB to even be able to change this value. The main linux build does not break, because we skip depmod during build. But any other, including manual linux builds, will break. Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, "Day of the Dove", stardate unknown
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
On Mon, Feb 12, 2024 at 10:26:07PM +0100, Salvatore Bonaccorso wrote: > On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote: > > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > > > depmod: ERROR: could not open directory > > > /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: > > > No such file or directory > > I would say depmod changed the API from /lib/modules to > > /usr/lib/modules. Re-assign? > A right, the last upload of kmod changed to use: > --with-module-directory=/usr/lib/modules The problem is, this now ties linux, kernel-wedge and kmod together. And with backports and the implicit nature of dh_movetousr, this is not a good idea right now. So we need to - make /usr usage explicit (in linux-signed-* it is still completely disabled, because of this implicit usage) - teach kernel-wedge to not assume Bastian -- A Vulcan can no sooner be disloyal than he can exist without breathing. -- Kirk, "The Menagerie", stardate 3012.4
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
On Feb 12, Salvatore Bonaccorso wrote: > --with-module-directory=/usr/lib/modules > > Looping in Marco for comments. I can revert it if it causes too much trouble, but maybe this is just the right time to switch the kernel packages to /usr/lib/modules/ as well? Please let me know if I am missing anything... -- ciao, Marco signature.asc Description: PGP signature
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
Hi Bastian, On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote: > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > > depmod: ERROR: could not open directory > > /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: > > No such file or directory > > I would say depmod changed the API from /lib/modules to > /usr/lib/modules. Re-assign? A right, the last upload of kmod changed to use: --with-module-directory=/usr/lib/modules Looping in Marco for comments. Regards, Salvatore
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > depmod: ERROR: could not open directory > /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: > No such file or directory I would say depmod changed the API from /lib/modules to /usr/lib/modules. Re-assign? Bastian -- Every living thing wants to survive. -- Spock, "The Ultimate Computer", stardate 4731.3
Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
Source: linux-signed-amd64 Version: 6.6.15+2 Severity: serious Justification: FTBFS X-Debbugs-Cc: car...@debian.org, wa...@debian.org, k...@debian.org The linux-signed-amd64 (and arm64 one) currently FTBFS (only filling one for amd64, as the same for arm64): https://buildd.debian.org/status/fetch.php?pkg=linux-signed-amd64=amd64=6.6.15%2B2=1707701442=0 [...] dh_builddeb -- -Zxz dpkg-deb: building package 'linux-image-6.6.15-amd64' in '../linux-image-6.6.15-amd64_6.6.15-2_amd64.deb'. make[2]: Leaving directory '/<>' /usr/bin/make -f debian/rules.real binary_installer ABINAME='6.6.15' ARCH='amd64' COMPILER='gcc-13' DESTDIR='/<>/debian/tmp' DH_OPTIONS='-pacpi-modules-6.6.15-amd64-di -pata-modules-6.6.15-amd64-di -pbtrfs-modules-6.6.15-amd64-di -pcdrom-core-modules-6.6.15-amd64-di -pcrc-modules-6.6.15-amd64-di -pcrypto-dm-modules-6.6.15-amd64-di -pcrypto-modules-6.6.15-amd64-di -pefi-modules-6.6.15-amd64-di -pevent-modules-6.6.15-amd64-di -pext4-modules-6.6.15-amd64-di -pf2fs-modules-6.6.15-amd64-di -pfat-modules-6.6.15-amd64-di -pfb-modules-6.6.15-amd64-di -pfirewire-core-modules-6.6.15-amd64-di -pi2c-modules-6.6.15-amd64-di -pinput-modules-6.6.15-amd64-di -pisofs-modules-6.6.15-amd64-di -pjfs-modules-6.6.15-amd64-di -pkernel-image-6.6.15-amd64-di -ploop-modules-6.6.15-amd64-di -pmd-modules-6.6.15-amd64-di -pmmc-core-modules-6.6.15-amd64-di -pmmc-modules-6.6.15-amd64-di -pmouse-modules-6.6.15-amd64-di -pmtd-core-modules-6.6.15-amd64-di -pmultipath-modules-6.6.15-amd64-di -pnbd-modules-6.6.15-amd64-di -pnic-modules-6.6.15-amd64-di -pnic-pcmcia-modules-6.6.15-amd64-di -pnic-shared-modules-6.6.15-amd64-di -pnic-usb-modules-6.6.15-amd64-di -pnic-wireless-modules-6.6.15-amd64-di -ppata-modules-6.6.15-amd64-di -ppcmcia-modules-6.6.15-amd64-di -ppcmcia-storage-modules-6.6.15-amd64-di --modules-6.6.15-amd64-di -prfkill-modules-6.6.15-amd64-di -psata-modules-6.6.15-amd64-di -pscsi-core-modules-6.6.15-amd64-di -pscsi-modules-6.6.15-amd64-di -pscsi-nic-modules-6.6.15-amd64-di -pserial-modules-6.6.15-amd64-di -psound-modules-6.6.15-amd64-di -pspeakup-modules-6.6.15-amd64-di -psquashfs-modules-6.6.15-amd64-di -pudf-modules-6.6.15-amd64-di -puinput-modules-6.6.15-amd64-di -pusb-modules-6.6.15-amd64-di -pusb-serial-modules-6.6.15-amd64-di -pusb-storage-modules-6.6.15-amd64-di -pxfs-modules-6.6.15-amd64-di' FEATURESET='none' FLAVOUR='amd64' IMAGE_FILE='arch/x86/boot/bzImage' IMAGE_INSTALL_STEM='vmlinuz' IMAGE_PACKAGE_NAME='kernel-image-6.6.15-amd64-di' KCONFIG='debian/config/config debian/config/kernelarch-x86/config debian/config/amd64/config' KCONFIG_OPTIONS=' -o "BUILD_SALT=\"6.6.15-amd64\""' KERNEL_ARCH='x86' LOCALVERSION='-amd64' LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-amd64' SOURCEVERSION='6.6.15-2' SOURCE_BASENAME='linux' SOURCE_SUFFIX='' UPSTREAMVERSION='6.6' VDSO='True' VERSION='6.6' make[2]: Entering directory '/<>' dh_testroot dh_prep dh_installdirs DH_OPTIONS="-pkernel-image-6.6.15-amd64-di --sourcedir=debian/linux-image-6.6.15-amd64" dh_install boot/vmlinuz-6.6.15-amd64 DH_OPTIONS="-pkernel-image-6.6.15-amd64-di --sourcedir=debian/linux-image-6.6.15-amd64" dh_install lib/modules/6.6.15-amd64/modules.builtin DH_OPTIONS="-pkernel-image-6.6.15-amd64-di --sourcedir=debian/linux-image-6.6.15-amd64" dh_install lib/modules/6.6.15-amd64/modules.order kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 depmod: ERROR: could not open directory /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: No such file or directory depmod: FATAL: could not search modules: No such file or directory No module interdependencies found. This probably means your modules.dep is broken. If this is intentional, touch /<>/debian/installer/no-modules make[2]: *** [debian/rules.real:95: binary_installer] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules.gen:14: binary-arch_amd64_none_amd64_installer] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:19: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Regards, Salvatore
