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 -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
