Your message dated Tue, 31 May 2016 17:17:24 -0400 with message-id <[email protected]> and subject line Re: linux kernel backports broken has caused the Debian Bug report #814648, regarding initrd missing from backport build (Failed to copy /boot/initrd.img-4.3.0-0.bpo.1-amd64 to /initrd.img) 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.) -- 814648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814648 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-4.3.0-0.bpo.1-amd64 Version: 4.3.3-7~bpo8+1 Severity: normal This version of the backport seems to fail to install properly: $ sudo apt install -t jessie-backports linux-image-4.3.0-0.bpo.1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: linux-doc-4.3 debian-kernel-handbook The following NEW packages will be installed: linux-image-4.3.0-0.bpo.1-amd64 0 upgraded, 1 newly installed, 0 to remove and 210 not upgraded. Need to get 0 B/35.5 MB of archives. After this operation, 173 MB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package linux-image-4.3.0-0.bpo.1-amd64. (Reading database ... 447530 files and directories currently installed.) Preparing to unpack .../linux-image-4.3.0-0.bpo.1-amd64_4.3.3-7~bpo8+1_amd64.deb ... Unpacking linux-image-4.3.0-0.bpo.1-amd64 (4.3.3-7~bpo8+1) ... Setting up linux-image-4.3.0-0.bpo.1-amd64 (4.3.3-7~bpo8+1) ... cp: cannot stat '/boot/initrd.img-4.3.0-0.bpo.1-amd64': No such file or directory Failed to copy /boot/initrd.img-4.3.0-0.bpo.1-amd64 to /initrd.img . dpkg: error processing package linux-image-4.3.0-0.bpo.1-amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-0.bpo.1-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) and indeed, the initrd is not in /boot: [1012]anarcat@angela:~100$ ls -al /boot/ total 73248K drwxr-xr-x 5 root root 1024 Feb 13 12:26 . drwxr-xr-x 26 root root 4096 Feb 13 12:26 .. -rw-r--r-- 1 root root 2676277 Jan 17 16:30 System.map-3.16.0-4-amd64 -rw-r--r-- 1 root root 2889500 Dec 15 05:16 System.map-4.2.0-0.bpo.1-amd64 -rw-r--r-- 1 root root 2949440 Jan 20 18:17 System.map-4.3.0-0.bpo.1-amd64 -rw-r--r-- 1 root root 157726 Jan 17 16:30 config-3.16.0-4-amd64 -rw-r--r-- 1 root root 169935 Dec 15 05:16 config-4.2.0-0.bpo.1-amd64 -rw-r--r-- 1 root root 171928 Jan 20 18:17 config-4.3.0-0.bpo.1-amd64 drwxr-xr-x 5 root root 7168 Feb 13 12:24 grub drwxr-xr-x 2 root root 1024 Sep 24 21:54 images -rw-r--r-- 1 root root 27164630 Jan 23 12:19 initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 28134677 Jan 23 12:20 initrd.img-4.2.0-0.bpo.1-amd64 drwx------ 2 root root 12288 Mar 29 2010 lost+found -rw-r--r-- 1 root root 25372 Sep 24 21:50 memdisk -rw-r--r-- 1 root root 182704 Sep 10 2014 memtest86+.bin -rw-r--r-- 1 root root 184840 Sep 10 2014 memtest86+_multiboot.bin -rw-r--r-- 1 root root 98964 Mar 10 2015 memtest86.bin -rw-r--r-- 1 root root 3119888 Jan 17 16:27 vmlinuz-3.16.0-4-amd64 -rw-r--r-- 1 root root 3480512 Dec 15 05:15 vmlinuz-4.2.0-0.bpo.1-amd64 -rw-r--r-- 1 root root 3566064 Jan 20 18:14 vmlinuz-4.3.0-0.bpo.1-amd64 Heck, it's not even in the package itself: $ dpkg -c /var/cache/apt/archives/linux-image-4.3.0-0.bpo.1-amd64_4.3.3-7~bpo8+1_amd64.deb | grep /boot/ drwxr-xr-x root/root 0 2016-01-20 18:17 ./boot/ -rw-r--r-- root/root 2949440 2016-01-20 18:17 ./boot/System.map-4.3.0-0.bpo.1-amd64 -rw-r--r-- root/root 171928 2016-01-20 18:17 ./boot/config-4.3.0-0.bpo.1-amd64 -rw-r--r-- root/root 3566064 2016-01-20 18:14 ./boot/vmlinuz-4.3.0-0.bpo.1-amd64 Something really wrong happened when this backport was built... a. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (500, 'oldstable'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.3.0-0.bpo.1-amd64 depends on: ii debconf [debconf-2.0] 1.5.56 ii initramfs-tools [linux-initramfs-tool] 0.120 ii kmod 18-3 ii linux-base 3.5 Versions of packages linux-image-4.3.0-0.bpo.1-amd64 recommends: ii firmware-linux-free 3.3 ii irqbalance 1.0.6-3 Versions of packages linux-image-4.3.0-0.bpo.1-amd64 suggests: pn debian-kernel-handbook <none> ii grub-pc 2.02~beta2-22+deb8u1 pn linux-doc-4.3 <none> -- debconf information: linux-image-4.3.0-0.bpo.1-amd64/postinst/depmod-error-initrd-4.3.0-0.bpo.1-amd64: false linux-image-4.3.0-0.bpo.1-amd64/prerm/removing-running-kernel-4.3.0-0.bpo.1-amd64: true linux-image-4.3.0-0.bpo.1-amd64/postinst/mips-initrd-4.3.0-0.bpo.1-amd64:
--- End Message ---
--- Begin Message ---On 2016-05-31 16:30:53, Christian Seiler wrote: > So I just tried this on my system (I actually just did an apt-get upgrade, > because I also run a backports kernel on my desktop, also amd64), and it > worked just fine here. > > Are initramfs-tools installed? (dpkg -l initramfs-tools) > If so, could you do the following: > > update-initramfs -k all -u > > Does that work or give you an error? > > How much space do you have left on your /boot partition? Sigh... /boot was full. i don't quite understand why the postinst script wouldn't tell me that, but removing an old kernel fixed the problem and I was able to build the initrd correctly. > As for your other problem: > >> dpkg-deb: error: parsing file >> '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy/DEBIAN/control' >> near line 8 package 'pbuilder-satisfydepends-dummy': >> `Depends' field, syntax error after reference to package `cpio' > > This is not an issue with the package build, but with pbuilder (and by > extension) cowbuilder only supprt the build profile syntax with > 0.215+nmu4, whereas Jessie only has 0.215+nmu3. So if you either use > pbuilder from testing/sid, or manually install the required build > dependencies on your host system, you can indeed build the package on > a pure jessie + jessie-backports system. (Probably, takes a long time, > I haven't actually tried.) I didn't know that! Thanks for the tip. A. -- Le Québec ne rêve plus de devenir une société modèle: voilà son problème d'environnement. - Pierre Dansereau (1911 - 2011)
--- End Message ---
