[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#794849: marked as done (linux: custom linux-image packages fail to install)

Your message dated Fri, 07 Aug 2015 18:21:09 +0100
with message-id <1438968069.7315.71.camel@decadent.org.uk>
and subject line Re: Bug#794849: linux: custom linux-image packages fail to install
has caused the Debian Bug report #794849,
regarding linux: custom linux-image packages fail to install
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 owner@bugs.debian.org
immediately.)


-- 
794849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794849
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

   * What led up to the situation?

I was trying to create a custom kernel package by following the steps at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.

I changed the ABI version from "4" to "4-s2e". I customized the kernel configuration using "make localmodconfig".  Then, I built the dpkg packages for the 586 subarchitecture (both linux-image and linux-headers).


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Subsequently, I also tried using make-kpkg, but the result was the same. The resulting dpkg package behaved the same (see below).


   * What was the outcome of this action?

Building the dpkg packages went OK. However, when I ran "sudo dpkg -i linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb", I got a warning "WARNING: missing /lib/modules/3.16.0-4-s2e-586", followed by another set of errors, including some error messages originating from the kernel. At the end, the package was left in an inconsistent state:

$ sudo dpkg -i linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb 
(Reading database ... 31856 files and directories currently installed.)
Preparing to unpack linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb ...
Unpacking linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) over (3.16.7-ckt11-1+deb8u3) ...
Setting up linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-s2e-586
WARNING: missing /lib/modules/3.16.0-4-s2e-586
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/3.16.0-4-s2e-586: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.builtin: No such file or directory
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-s2e-586
Found initrd image: /boot/initrd.img-3.16.0-4-s2e-586
Found linux image: /boot/vmlinuz-3.16.0-4-686-pae
Found initrd image: /boot/initrd.img-3.16.0-4-686-pae
done

I checked the contents of /lib/modules, and found that there is a 3.16.0-4-586 directory, but not an "-s2e" one, in addition to the one corresponding to the current kernel:

$ ls -l /lib/modules
total 8
drwxr-xr-x 3 root root 4096 Aug  7 12:19 3.16.0-4-586
drwxr-xr-x 3 root root 4096 Aug  7 11:17 3.16.0-4-686-pae

   * What outcome did you expect instead?

I would have expected the dpkg package to install successfully on the machine.


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Fri, 2015-08-07 at 12:30 +0200, Stefan Bucur wrote:
> Source: linux
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> I was trying to create a custom kernel package by following the steps 
> at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.
> 
> I changed the ABI version from "4" to "4-s2e". I customized the 
> kernel configuration using "make localmodconfig".  Then, I built the 
> dpkg packages for the 586 subarchitecture (both linux-image and linux
> -headers).
[...]

It sounds like you've done things in the wrong order or the wrong
directory, because this package can be and is being built from source. 
 If there's any bug here, it would be in the kernel-handbook package,
but I'm pretty sure it's stil correct.

It is generally easier to build custom kernels using this approach:
<http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building>.

Ben.

-- 
Ben Hutchings
Computers are not intelligent.	They only think they are.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: