On Mon, Oct 20, 2014 at 07:31:50PM -0400, Greg Freemyer wrote:
> Greg Freemyer
> On Mon, Oct 20, 2014 at 7:08 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> > On Mon, Oct 20, 2014 at 08:54:47AM -0500, Eric Sandeen wrote:
> >> On 10/20/14 6:55 AM, Greg Freemyer wrote:
> >> > Opensuse is building rpms of 1.1.1 so the build infrastructure isn't
> >> > too badly broken. I don't know if they are following FHS, but I
> >> > doubt they use /opt.
> >> The build works fine, it's the "Makepkgs" that I think is a bit odd,
> >> at least for RPM packaging.
> > It's just odd, regardless of what it is packaging.
> >> Also, if we really want to encourage packaging, we should probably start
> >> sticking official version numbers on it. "1.1.1" was tagged in Dec 2012,
> >> and there have been no "releases" since.
> > There are more recent tags than that. There were some linux-v3.[6-8]
> > tags added when kernels v3.[6-8] we released. Those tags are
> > basically meaningless from a release perspective, though.
> > As it is, for the purpose of the discussion I'll argue that we don't
> > need official release versions or tarballs and that anyone who needs
> > packages for xfstests is Doing it Wrong(tm).
> A potential use case with openSUSE and why I "think" they packaged it
> is to include a subset of xfstest in there automated testing.
Sure - i'm just pointing out that you don't need RPM to do that -
git it just as good for deploying automated testing infrastructure
> Notice for example that ext4 is a testsuite selection in the testsuite
> pull down. I assume that testsuite uses xfstests to exercise ext4
> prior to an automated release of factory.
> The 2014-10-17 build of a couple days ago is an example of a build
> that failed the ext4 testsuite:
That doesn't appear to anything to do with xfstests. It appears to
be a "can we install opensuse" installer test that happens to be run
on ext4. i.e. it's really product level testing (i.e. whether the
opensuse build worked) not whether the filesystem works as it's
> I don't see automated tests for xfs or btrfs which is a surprise since
> both of them are default filesystem choices for factory. (btrfs is
> the default choice for / and xfs is the default for /home).
Seeing as it's not actually doing filesystem level testing, it
probably doesn't matter at all.