On Thu, 6 Oct 2011 07:20:50 +0200, Robert Millan wrote:
2011/10/6 Adam D. Barratt <a...@adam-barratt.org.uk>:
test -e ./tmp/cdrom/tree/boot/zfs || rmdir ./tmp/cdrom/tree/boot/
rmdir: failed to remove `./tmp/cdrom/tree/boot/': Directory not
empty
[...]
$ debdiff kernel-image-8.1-1-486-di_0.6_kfreebsd-i386.udeb
kernel-image-8.1-1-486-di_0.6+b1_kfreebsd-i386.udeb
[...]
Files in second .deb but not in first
-------------------------------------
-rw-r--r-- root/root /boot/acpi.ko
This appears to be due to the fact that the new kfreebsd-8 +squeeze1
kernel on -i386 builds acpi.ko as a module, which is then picked up
by
existing "install this module if it exists" rules in kernel-wedge.
Actually, the problem is not presence of acpi.ko itself, but the fact
that a symlink to this file exists in /boot/. This is due to an old
postinst kludge from pre-GRUB time.
Okay.
A quick fix would be appreciated, whether from the kfreebsd or d-i
side,
given the increasingly short period of time we have remaining until
the
point release is scheduled.
Attached patch should fix the problem. I can upload a fixed
kfreebsd-8 this evening (feel free to NMU if someone has time to
verify earlier than that).
Forgive my ignorance on the precise mechanics, but is it correct that
the /boot/kernel/kernel.gz symlink creation was also removed?
Would you be able to also upload a kfreebsd-i386 build? That would
help reduce the turnaround time before we can schedule a rebuild of
kfreebsd-kernel-di-i386.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/ac1933eacf629d91a4529827b879e...@adsl.funky-badger.org
