flash-kernel will run from various kernel postinst hooks and overwrite
our own boot scripts. While this might be tollerable for the initial
installation we don't want to risk it occuring after we have created
our own boot.scr to boot xen.
dpkg --purge succeeds if the package wasn't installed.
This happened to show up with Jessie since it now supports the two
boards in our test lab while Wheezy didn't (so flash-kernel didn't
know about them and did nothing).
Signed-off-by: Ian Campbell <ian.campb...@citrix.com>
---
Osstest/Debian.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
index a158f34..f7275de 100644
--- a/Osstest/Debian.pm
+++ b/Osstest/Debian.pm
@@ -1106,6 +1106,8 @@ echo Booting
bootz \\\${kernel_addr_r} \\\${ramdisk_addr_r}:\\\${filesize} \\\${fdt_addr}
EOF
+in-target dpkg --purge flash-kernel
+
in-target mkimage -A arm -T script -d /boot/boot.deb /boot/boot.scr.deb
in-target cp /boot/boot.scr.deb /boot/boot.scr
END
--
2.5.3
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
