All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v3] Arrange to upgrade microcode on x86 test hosts.
Date: Mon, 15 Jun 2015 13:22:59 +0100	[thread overview]
Message-ID: <1434370979.13744.20.camel@citrix.com> (raw)
In-Reply-To: <21886.49560.964814.826704@mariner.uk.xensource.com>

On Mon, 2015-06-15 at 13:14 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v3] Arrange to upgrade microcode on x86 test hosts."):
> > ---
> > v3:
> > - iucode-tool is iucode_tool in Wheezy, Jessie has both names
> > - This exact version mg-cpu-microcode-update has been run in colo,
> >   updated production-config*
> > - Avoid proxy with wget, since it was pointing at the apt-cache which
> >   gave "403 Sorry, not allowed to fetch that type of file:
> >   fiano0_microcode-cpio"
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> 
[...]
> Perhaps wget in much of this should become $di_wget which contains
> `wget -Y off' ?

I sent a separate patch to add -Y off everywhere. I could make it use
$di_wget instead.

> We don't really want to be fetching any of this stuff through the
> apt-cache.  Currently it's presumably it's working by chance, either
> because of what might be thought of as a bug in the apt cacher, or
> because d-i's setting of http_proxy to the supplied cache is not quite
> universal.

Right.

      reply	other threads:[~2015-06-15 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  8:36 [PATCH OSSTEST v3] Arrange to upgrade microcode on x86 test hosts Ian Campbell
2015-06-15 12:14 ` Ian Jackson
2015-06-15 12:22   ` Ian Campbell [this message]

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=1434370979.13744.20.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.