Your message dated Tue, 21 Jun 2022 10:54:26 +0200
with message-id <12000826.O9o76ZdvQC@bagend>
and subject line Re: Bug#918097: initramfs-tools-core: Error while building
DKMS modules when kernel has all its modules built in
has caused the Debian Bug report #918097,
regarding mkinitramfs prints error messages when no modules are needed in the
initramfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools-core
Version: 0.132
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
I wanted to build a custom kernel using the linux-source package from the
Debian repository. I haven't changed much, the only thing I wanted to do is to
build in all the modules my machine needs and remove all the others. Such
kernels don't have modules in *.ko files and it looks like mkinitramfs has some
issues with that.
Basically, the problem is in the /usr/share/initramfs-tools/hook-functions
script file with the following line:
find "${DESTDIR}/lib/modules/${version}/kernel" -name '*.ko*'
Since none of the modules listed above in the file were copied to the temp
destination folder, the kernel/ subdir doesn't exist and hence the above
command returns error. The initramfs image is building fine, but DKMS packages
return something similar to the following:
# dpkg --configure -a
Setting up sysdig-dkms (0.24.1-1) ...
Removing old sysdig-0.24.1 DKMS files...
- -------- Uninstall Beginning --------
Module: sysdig
Version: 0.24.1
Kernel: 4.19.13-amd64-morficzny (x86_64)
- -------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
sysdig-probe.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.13-amd64-morficzny/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
- ------------------------------
Deleting module version: 0.24.1
completely from the DKMS tree.
- ------------------------------
Done.
Loading new sysdig-0.24.1 DKMS files...
Building for 4.19.13-amd64-morficzny 4.20.0-amd64-morficzny
Building initial module for 4.19.13-amd64-morficzny
Error! Bad return status for module build on kernel: 4.19.13-amd64-morficzny
(x86_64)
Consult /var/lib/dkms/sysdig/0.24.1/build/make.log for more information.
dpkg: error processing package sysdig-dkms (--configure):
installed sysdig-dkms package post-installation script subprocess returned
error exit status 10
Errors were encountered while processing:
sysdig-dkms
I changed my kernel config a little bit:
# egrep \=m /boot/config-4.19.13-amd64-morficzny
CONFIG_BTRFS_FS=m
CONFIG_XOR_BLOCKS=m
CONFIG_RAID6_PQ=m
And after rebuilding the kernel when I want to created the initramfs image I
can see the the kernel/ subdir:
# tree
/var/tmp/mkinitramfs_p7rDVj/usr/lib/modules/4.19.13-amd64-morficzny/kernel/
/var/tmp/mkinitramfs_p7rDVj/usr/lib/modules/4.19.13-amd64-morficzny/kernel/
├── crypto
│ └── xor.ko
├── fs
│ └── btrfs
│ └── btrfs.ko
└── lib
└── raid6
└── raid6_pq.ko
5 directories, 3 files
Will this qualify as bug or should I fix this in some way myself since it's not
the Debian distribution's kernel?
- -- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (130, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.13-amd64-morficzny (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages initramfs-tools-core depends on:
ii coreutils 8.30-1
ii cpio 2.12+dfsg-6
ii e2fsprogs 1.44.5-1
ii klibc-utils 2.0.4-14
ii kmod 25-2
ii udev 240-2
Versions of packages initramfs-tools-core recommends:
ii busybox 1:1.27.2-3
Versions of packages initramfs-tools-core suggests:
ii bash-completion 1:2.8-5
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5JPPWm5C7TFDUMqpzQRoEHcbZSAFAlwt2AAACgkQzQRoEHcb
ZSDrjg//X6cMtoFjEw3BOAg+1EpKTQ1/yfJSAW611NgsgfvvPurncPx5X3XtQ0sH
/I47mXSB4ds3/KuGIJb96SXgOChBqvfdS/7ajirGL11Ou4Ujfmb9CC0sOpUe3uba
OKNdB+QiwHMDlfKdvDMk0LXN4i7fx9hCUukAkhE1s9xbqCk+veTmHpnv5BomIoX/
AqfdmeN2Y08MDdd5K8S/g1/4fVg9QUSE8+9dP9r1Bw7nqdp4EpSj7ZSKtifSayRb
k+AENOn0nMoXQP9zTYbzIv8k3LvB6+rTBf67ST1uMGGIljuf78VveJqMvJfBgS8P
8VNDdx8O5J2U2Dn9S4j4NOiKJLkQIBELyR+hTF4AQrPJ8BHquPvvCbUyVLL9SV4S
Wz8gylSP9uWwYlEjN/9vfFtMhZIiJ5Maloow4SKYgjw6+5w7BDtpp/f35Vji2+cc
9JKf+xTVuMRmMQn43NAj6a+JcUv6i9n9wy9C9HsC2qt6NnVdTx2+YGdx+vqwAz/0
QewOxkeuHgqLrRD4aUSkrZ4Z2vcfW+5ccXiej0+QsMyHt1gWgMU3DbZcNdpK/k2+
JioqBC2aLN37FfQzAhB/KDFwJ1XmJCqi1GKdk431Z/urtAFlPB/X08aDRUf/QfVq
wwD8hUwzLB3hSHqGDmKCuY0Z/y/uz1tW7B79tPgZIiIneX3loIY=
=G9Xp
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 0.141
On Tuesday, 21 June 2022 02:29:46 CEST Branen Salmon wrote:
> I noticed this bug in bullseye today and found that it's fixed in 0.141,
> the version currently in bookworm. The fix was contributed by Dan
> Streetman in commit 116b5323.
Indeed, thanks for noticing :-)
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
