xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH OSSTEST 1/6] Debian: Uninstall flash-kernel when creating our own boot.scr
Date: Tue, 29 Sep 2015 10:44:53 +0100	[thread overview]
Message-ID: <1443519898-24444-1-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1443519883.16718.23.camel@citrix.com>

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.campbell@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

  reply	other threads:[~2015-09-29  9:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  9:44 [PATCH OSSTEST 0/6] Fixes for switching to Jessie as base OS for test hosts Ian Campbell
2015-09-29  9:44 ` Ian Campbell [this message]
2015-09-29 14:05   ` [PATCH OSSTEST 1/6] Debian: Uninstall flash-kernel when creating our own boot.scr Ian Jackson
2015-09-29  9:44 ` [PATCH OSSTEST 2/6] Debian: Search for kernel in /boot as well as / when making u-boot script Ian Campbell
2015-09-29 14:07   ` Ian Jackson
2015-09-29  9:44 ` [PATCH OSSTEST 3/6] Debian: uboot: Use di_vg_name() and lv_dev_mapper() for root= Ian Campbell
2015-09-29 14:08   ` Ian Jackson
2015-09-29 14:18     ` Ian Campbell
2015-09-29 15:04       ` Ian Jackson
2015-09-29  9:44 ` [PATCH OSSTEST 4/6] ts-freebsd-install: Use $gho->{Lvdev} instead of target_guest_lv_name Ian Campbell
2015-09-29 14:09   ` Ian Jackson
2015-09-30 14:48   ` Roger Pau Monné
2015-09-30 15:06     ` Ian Jackson
2015-10-01 10:45   ` Ian Campbell
2015-10-01 10:48     ` Ian Campbell
2015-10-02  9:36     ` Ian Campbell
2015-10-05 16:31       ` Ian Jackson
2015-09-29  9:44 ` [PATCH OSSTEST 5/6] TestSupport: Remove now unused target_guest_lv_name Ian Campbell
2015-09-29 14:10   ` Ian Jackson
2015-09-29  9:44 ` [PATCH OSSTEST 6/6] Switch to Debian 8.0 (jessie) as OS for test hosts Ian Campbell
2015-09-29 14:11   ` Ian Jackson
2015-09-29 10:27 ` [PATCH OSSTEST 0/6] Fixes for switching to Jessie as base " Ian Campbell
2015-09-29 14:12   ` Ian Jackson
2015-09-29 14:11 ` Ian Jackson
2015-09-30 14:30 ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1443519898-24444-1-git-send-email-ian.campbell@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).