[6475] in Release_7.7_team
schroot 1.3 (with aufs support) is out; how do we proceed?
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Fri Oct 16 21:01:31 2009
Date: Fri, 16 Oct 2009 21:01:05 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: debathena@mit.edu
cc: release-team@mit.edu
Message-ID: <alpine.DEB.2.00.0910162040150.10797@beautiful-katamari.csail.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Spam-Flag: NO
X-Spam-Score: 0.00
schroot 1.3 was released about 2 hours ago. I'm going to want it on
clusters because of its union filesystem / aufs support, which promises to
make logins faster. See the release announcement:
http://lists.alioth.debian.org/pipermail/buildd-tools-devel/2009-October/003739.html
Yesterday was Karmic's FinalFreeze. Since schroot is in 'universe' instead
of 'main', this doesn't actually make it impossible to get a
FeatureFreezeException, it just makes it even more unlikely at this point.
In order to get a backport to Jaunty, we'd need to get this package in
Karmic, or wait until Lucid's archive opens and get it in there, and file
the backport for both Jaunty and Karmic.
Should we attempt to go through with this process, which runs into the
danger of having to wait until Karmic is released (the end of the month)
to be able to file the backport request, or should we more-or-less
"debathenify" schroot 1.3 into our own apt repository as debathena-schroot
for the Jaunty and possibly Karmic release cycles?
Also, for debuild maintainers: should we consider restructuring the build
process to use schroot 1.3 and aufs snapshots instead of LVM snapshots?
--
Geoffrey Thomas
geofft@mit.edu
