From owner-freebsd-current@freebsd.org Sat Jul 11 21:26:33 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCBE89979CA for ; Sat, 11 Jul 2015 21:26:33 +0000 (UTC) (envelope-from marcus@odin.blazingdot.com) Received: from odin.blazingdot.com (odin.blazingdot.com [204.109.60.170]) by mx1.freebsd.org (Postfix) with ESMTP id C82CF18FA for ; Sat, 11 Jul 2015 21:26:33 +0000 (UTC) (envelope-from marcus@odin.blazingdot.com) Received: by odin.blazingdot.com (Postfix, from userid 1001) id 9B4D91320ED; Sat, 11 Jul 2015 14:26:27 -0700 (PDT) Date: Sat, 11 Jul 2015 14:26:27 -0700 From: Marcus Reid To: freebsd-current@freebsd.org Subject: libarchive / bsdtar bug Message-ID: <20150711212627.GA48892@blazingdot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 11 Jul 2015 21:26:34 -0000 Hi, I just got bit by this bug in bsdtar: https://github.com/libarchive/libarchive/issues/464 Since libarchive 3.1.2 is over 2 years old now and there have not been any more releases, what is the right way of going about reporting a fixed bug so that the FreeBSD version gets a patch downstream? Marcus