On 19/03/11 08:58, Jan Steffens wrote:
On Fri, Mar 18, 2011 at 11:59 PM, Allan McRae wrote:
Where can I put a chroot (temporarily) to ensure it will not be deleted
unless I manually do it? I had a bunch of gcc test suite log files from my
last build sitting in my chroots for use in tracking do
On Fri, Mar 18, 2011 at 11:59 PM, Allan McRae wrote:
> Where can I put a chroot (temporarily) to ensure it will not be deleted
> unless I manually do it? I had a bunch of gcc test suite log files from my
> last build sitting in my chroots for use in tracking down failures and these
> have now bee
On 19/03/11 08:42, Jan Steffens wrote:
Our PKGBUILD.com build server is now tentatively running my devtools patchset.
User-visible changes should be:
--- *-build now always requires sudo. This used to be inconsistent,
requiring sudo only for -c.
--- All chroots are now kept in /var/tmp/archbuild
Our PKGBUILD.com build server is now tentatively running my devtools patchset.
User-visible changes should be:
--- *-build now always requires sudo. This used to be inconsistent,
requiring sudo only for -c.
--- All chroots are now kept in /var/tmp/archbuild, a btrfs volume.
--- All chroot copies a
4 matches
Mail list logo
