I'm checking that the last kernel from the repo [1] have the postinst
different than the package done by the "make deb-pkg". I attached both.
I think that the file located under
"linux-source-4.9/debian/tmp/DEBIAN/postinst" must have the logic for
manage linux-update-symlinks like the original package from the repo do.
In this particular case, the symlinks are update using:
# linux-update-symlinks install 4.9.30id /boot/vmlinuz-4.9.30id
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.9.0-3-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.9.0-3-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.9.30id
I: /initrd.img is now a symlink to boot/initrd.img-4.9.30id
Thanks,
[1] - https://packages.debian.org/stretch/linux-image-4.9.0-3-amd64
El 2017-06-20 15:11, Ben Hutchings escribió:
> Control: severity -1 wishlist
> Control: tag -1 upstream
> Control: found -1 4.11.6-1
>
> This is because the upstream Debian packaging doesn't (yet) run linux-
> update-symlinks.
>
> Ben.
#!/bin/sh -e
version=4.9.0-3-amd64
image_path=/boot/vmlinuz-$version
if [ "$1" != configure ]; then
exit 0
fi
depmod $version
if [ -f /lib/modules/$version/.fresh-install ]; then
change=install
else
change=upgrade
fi
linux-update-symlinks $change $version $image_path
rm -f /lib/modules/$version/.fresh-install
if [ -d /etc/kernel/postinst.d ]; then
DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \
--arg=$image_path /etc/kernel/postinst.d
fi
exit 0
#!/bin/sh
set -e
# Pass maintainer script parameters to hook scripts
export DEB_MAINT_PARAMS="$*"
# Tell initramfs builder whether it's wanted
export INITRD=Yes
test -d /etc/kernel/postinst.d && run-parts --arg="4.9.30id" --arg="/boot/vmlinuz-4.9.30id" /etc/kernel/postinst.d
exit 0