linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Refreshed rootfs.img for kvm-xfstests
Date: Sat, 23 Jul 2016 11:10:26 -0400	[thread overview]
Message-ID: <20160723151026.GD26664@thunk.org> (raw)
In-Reply-To: <20160721202238.GA1514@localhost.localdomain>

On Thu, Jul 21, 2016 at 04:22:39PM -0400, Eric Whitney wrote:
> I've tested this version of the ARM test appliance using the 4k test config
> on a Pandaboard with a 4.7-rc7 kernel, and have discovered a few problems with
> the file system image as discussed in today's concall (the upshot was that the
> build process might be failing somewhere along the way and producing an
> incomplete image):
> 
> Several files needed to run the appliance are missing from /root - test-env,
> test-conf, /conf (and its contents), and runtests.sh.  Copying them in
> from xfstests-bld solved that.
> 
> /usr/bin/awk points to an executable in Ted's home directory.  Relinking to
> /usr/bin/gawk fixed things up well enough.

The first was caused a bug in how a rsync'ed the source tree to the
armhf build host.  Debian's build systems have a firewall that prevent
git from working correctly, so I have to rsync the source tree up
build host, and this broke the git tree so the automated generation of
the *.ver files broke, which in turn aborted the installation of the
quota tools.

The second problem had to do with how fakechroot (used because I don't
have root on the arm build host) handles symlinks.  Fixed by using the
"symlinks" program rewrite the absolute symlinks to relative symlinks.

I've uploaded an updated armmf_root_fs.tar.gz; please give it a try!

Cheers,

							- Ted

  reply	other threads:[~2016-07-23 15:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 14:05 Refreshed rootfs.img for kvm-xfstests Theodore Ts'o
2016-07-21 20:22 ` Eric Whitney
2016-07-23 15:10   ` Theodore Ts'o [this message]
2016-07-23 23:06     ` Eric Whitney
2016-07-24  8:18       ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2017-01-09 23:14 Theodore Ts'o
2017-01-10  3:38 ` Theodore Ts'o
2017-01-10 12:48   ` Roman Penyaev
2017-01-10 15:07     ` Roman Penyaev
2017-01-11  3:05       ` Theodore Ts'o
2017-01-10 18:50     ` Eric Biggers
2016-06-30 15:28 Theodore Ts'o
2016-07-01 15:54 ` Theodore Ts'o
2016-04-04  6:13 Theodore Ts'o
2015-10-25 21:26 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=20160723151026.GD26664@thunk.org \
    --to=tytso@mit.edu \
    --cc=enwlinux@gmail.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).