From owner-freebsd-current@FreeBSD.ORG Fri Apr 17 19:41:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24E231065672 for ; Fri, 17 Apr 2009 19:41:10 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id E8D5F8FC15 for ; Fri, 17 Apr 2009 19:41:09 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n3HJf5oE028475; Fri, 17 Apr 2009 12:41:05 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id 8va6eq3ppv6486ey9gq9ua9mxe; Fri, 17 Apr 2009 12:41:05 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49E8DB50.2060606@freebsd.org> Date: Fri, 17 Apr 2009 12:41:04 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Mel Flynn References: <57200BF94E69E54880C9BB1AF714BBCB5DE72E@w2003s01.double-l.local> <49E8C1E4.8050608@freebsd.org> <200904172107.15616.mel.flynn+fbsd.current@mailing.thruhere.net> In-Reply-To: <200904172107.15616.mel.flynn+fbsd.current@mailing.thruhere.net> Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Johan Hendriks Subject: Re: buildworld fails. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2009 19:41:10 -0000 Mel Flynn wrote: > On Friday 17 April 2009 19:52:36 Tim Kientzle wrote: >> This should be fixed in SVN r191196 by my update to >> lib/libarchive/config_freebsd.h, which disabled the >> crypto references here until I can sort out some >> other issues. > > It's fixed. What should we be looking for (if anything) that's now broken with > crypto references disabled? Specifically, I (temporarily) disabled libarchive's ability to generate cryptographic hashes when writing mtree format. This is a new feature that nobody knows about, so I doubt it will affect you. ;-) When I re-enable it, you should be able to: tar -cf - --format=mtree --options=sha512 . and generate an mtree file with sha512 checksums. No big deal, of course, since mtree does this even better. Here's something mtree can't do, though: tar -cf - --format=mtree --options=sha512 @file.tgz to generate an mtree file (with sha512 checksum info) of the contents of a tar file. Of course, libarchive's mtree support is mostly for developers to use in building new tools that use mtree format in innovative ways. Exposing it through tar is primarily to make it easier to test. Tim P.S. I just realized that I probably broke WITHOUT_OPENSSL builds as well. I'm running a series of buildworlds today to try to verify all of this; I hope to have it all settled within 24 hours. Apologies for the turmoil.