Your message dated Fri, 20 Oct 2017 10:36:14 -0400 with message-id <[email protected]> and subject line Re: lttng-modules-dkms: Package install fails on kernel 3.2 has caused the Debian Bug report #743974, regarding lttng-modules-dkms: Package install fails on kernel 3.2 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 [email protected] immediately.) -- 743974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743974 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lttng-modules-dkms Version: 2.4.0-2 Severity: important Hi. Look: dima@shorty:/tmp/lttng-modules-2.4.0$ sudo aptitude reinstall lttng-modules-dkms The following packages will be REINSTALLED: lttng-modules-dkms 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1775 not upgraded. Need to get 0 B/227 kB of archives. After unpacking 0 B will be used. (Reading database ... 290497 files and directories currently installed.) Preparing to replace lttng-modules-dkms 2.4.0-2 (using .../lttng-modules-dkms_2.4.0-2_all.deb) ... ------------------------------ Deleting module version: 2.4.0 completely from the DKMS tree. ------------------------------ Done. Unpacking replacement lttng-modules-dkms ... Setting up lttng-modules-dkms (2.4.0-2) ... Loading new lttng-modules-2.4.0 DKMS files... Building for 3.2.0-4-amd64 and 3.13-1-amd64 Building initial module for 3.2.0-4-amd64 Error! Build of lttng-probe-printk.ko failed for: 3.2.0-4-amd64 (x86_64) Consult the make.log in the build directory /var/lib/dkms/lttng-modules/2.4.0/build/ for more information. The make.log has no failures in it, and the kernel modules did build successfully. The issue is that the set of kernel modules that are built varies with kernel version, but there's a whitelist of modules that the build script makes sure are built, and THIS list is not kernel-version-specific. In the case of Linux 3.2 lttng-probe-printk.ko is not built, but the packaging script expects it, and this is the cause of the failure. The whitelist is in lttng-modules-dkms.in. The actual logic about what gets built is in probes/Makefile. Specifically, here's the printk logic: obj-m += $(shell \ if [ $(VERSION) -ge 3 -a $(PATCHLEVEL) -ge 4 ] ; then \ echo "lttng-probe-printk.o" ; fi;) I'm not sure there's a lot of value in checking anything more than the error code returned by the make process that does the build, but that's out of scope here. dima there's a whitelist o The kernel modules -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages lttng-modules-dkms depends on: ii dkms 2.2.0.3-1.2 Versions of packages lttng-modules-dkms recommends: ii lttng-tools 2.4.0-2 lttng-modules-dkms suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, This was fixed a long time ago, the list of modules is now conditionnal on the kernel version. Cheers, Michael
--- End Message ---
