public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] xfstests-bld: document how to add debian packages to GCE image
Date: Thu, 22 Dec 2016 12:04:33 -0500	[thread overview]
Message-ID: <20161222170433.cbyrt2phsapq2tr7@thunk.org> (raw)
In-Reply-To: <1482343592-135031-2-git-send-email-ebiggers3@gmail.com>

On Wed, Dec 21, 2016 at 10:06:28AM -0800, Eric Biggers wrote:
> +build your own image, you must first build a 64-bit (amd64) xfstests
> +tarball as described in the [instructions for building
> +xfstests](building-xfstests.md).  Then copy any additional Debian
> +packages, for the amd64 architecture, you want to include in the GCE
> +image into the root directory of GS_BUCKET.

This is phrased a bit awkwardly.  The official way is to put the
debian packages in kvm-xfstests/test-appliances/debs.  This works for
both building gce-xfstests and kvm-xfstests images.

And in general, you would need to use whatever debian packages for
whatever architecture is compatible for the image or chroot tarball
you are building.  For gce-xfstests, it is always amd64, since GCE
currently only supports 64-bit x86.  (But for kvm-xfstests or chroot
tarballs, it might be i386 or armhf.)

So how about,

   If you want to include any additional Debian packages, or you want
   to override the default Jessie packages with newer versions from
   jessie-backports, place them in the directory
   kvm-xfstests/test-appliances/debs.  For gce-xfstests, the packages
   must be for the amd64 architecture.

We might want break up the paragraph into multiple smaller paragraphs
just to make it easier to read.

				- Ted

  reply	other threads:[~2016-12-22 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 18:06 [PATCH] xfstests-bld: document how to add debian packages to GCE image Eric Biggers
2016-12-22 17:04 ` Theodore Ts'o [this message]
2016-12-28 21:21   ` Eric Biggers
2016-12-31 15:52     ` Theodore Ts'o
2017-01-07 17:00       ` Theodore Ts'o

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=20161222170433.cbyrt2phsapq2tr7@thunk.org \
    --to=tytso@mit.edu \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=fstests@vger.kernel.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