From owner-freebsd-current@FreeBSD.ORG Fri Apr 17 21:56:07 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 6CB09106564A; Fri, 17 Apr 2009 21:56:07 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD418FC18; Fri, 17 Apr 2009 21:56:06 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: by fxm11 with SMTP id 11so1106904fxm.43 for ; Fri, 17 Apr 2009 14:56:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type :content-transfer-encoding; bh=B2ceqMPPzL4xUFMZ6kGWcz1O9cxdjsfw2FgwFqSOz/E=; b=hhR0ZAa4okGryeUWLXs2g4JKAKFyY3rRrgS6igvzFcPE2emtPqimrV1NIS+R9ys8Zq 2Ke5y6VVIfhghMoHMmCLmA+tylxCGoHJSz2fQcpSzfp/eeANjuDATDAH3dK2y5qN3d7X I0B5VCobgOzdpvrW7iUDw5DU4g9O6+/lLAuIM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; b=vqaiQfn+W8pMIUDAUbrJmtqmw9MWa/ZnR/g2TpdeqPLaPg4gUKnbb/Okde2Cv49avI MPPrW/Oy46o2Owj1h5uXhE5z8nMhkydh3qxQqU/VVDp9c388krs/Txw7IpSxGA9fNuOk n2hebGR/uZMyBkjCB9DsR9wcykQ17pCIBolG8= Received: by 10.86.60.15 with SMTP id i15mr2336068fga.5.1240005365544; Fri, 17 Apr 2009 14:56:05 -0700 (PDT) Received: from localhost (95-24-70-84.broadband.corbina.ru [95.24.70.84]) by mx.google.com with ESMTPS id 3sm36626fge.20.2009.04.17.14.56.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 17 Apr 2009 14:56:04 -0700 (PDT) From: Anonymous To: Tim Kientzle References: <57200BF94E69E54880C9BB1AF714BBCB5DE72E@w2003s01.double-l.local> <49E8C1E4.8050608@freebsd.org> <200904172107.15616.mel.flynn+fbsd.current@mailing.thruhere.net> <49E8DB50.2060606@freebsd.org> Date: Sat, 18 Apr 2009 01:56:00 +0400 In-Reply-To: <49E8DB50.2060606@freebsd.org> (Tim Kientzle's message of "Fri, 17 Apr 2009 12:41:04 -0700") Message-ID: <86ocuvrllb.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org 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 21:56:08 -0000 Tim Kientzle writes: > 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=3Dmtree --options=3Dsha512 . > > 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=3Dmtree --options=3Dsha512 @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. Can you document mtree writing support in libarchive=E2=80=90formats(5) ? Ah, and fix section in that file, too .Dt libarchive-formats 3 > > 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.