Package: dracut,dracut-network Followup-For: Bug #657754 Hi Thomas,
in 013-5 the installation in a chroot no longer fails, but it still seems to create an initrd and spews a lot of error messages: Selecting previously unselected package dracut. (Reading database ... 6909 files and directories currently installed.) Unpacking dracut (from .../archives/dracut_013-5_all.deb) ... Setting up dracut (013-5) ... dracut: Generating /boot/initramfs-3.2.0-1-amd64.img E: Directories consolefonts, consoletrans, keymaps, unimaps not found. Please inform us about the issue including your OS name and version. find: `/lib/modules/3.2.0-1-amd64/': No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory F: No modules.builtin.bin and modules.builtin found! E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory find: `/lib/modules/3.2.0-1-amd64/': No such file or directory find: `/lib/modules/3.2.0-1-amd64/': No such file or directory find: `/lib/modules/3.2.0-1-amd64/': No such file or directory find: `/lib/modules/3.2.0-1-amd64/': No such file or directory E: FATAL: Could not load /lib/modules/3.2.0-1-amd64/modules.dep: No such file or directory and in the end after package purge an initrd is left behind: 0m22.1s ERROR: FAIL: Package purging left files on system: /boot/initramfs-3.2.0-1-amd64.img not owned Using hook scripts and triggers like initramfs-tools might be a solution. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
