Hi, On 23:11, Michael Gilbert wrote: > Wouldn't this be fixed somewhat simply if freebsd-net-tools had a > depends: kfreebsd-image-10? So even though freebsd-image-9 gets > removed due the breaks, the user will at least have the newer kernel > and a bootable system.
That would work, except any chroot or jail would install a kernel. I think, even sbuild running on the buildds would then install a kernel image and modules inside the build chroot, and that's obviously wrong. APT understands it should remove kfreebsd-image-9 but just doesn't know to install kfreebsd-image-10; I wonder if a Linux dist-upgrade from squeeze to wheezy pulls in linux-image-3.2 automatically, and how it does that? I know Linux packaging does show a prompt if you try to remove the last kernel image from the system; something similar would at least alert users if a dist-upgrade is going wrong, although there must be a way to fix this to do it right. Perhaps kfreebsd-image-10 needs to 'Provide' a newer kfreebsd-image-9 version (and adjust the Breaks to << that version), or something ugly like that? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140926115953.gb15...@squeeze.pyro.eu.org
