From owner-freebsd-current@FreeBSD.ORG Thu Sep 23 16:07:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0619B16A4CE; Thu, 23 Sep 2004 16:07:51 +0000 (GMT) Received: from coruscant.rfc1149.org (coruscant.rfc1149.org [217.160.130.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A86F43D48; Thu, 23 Sep 2004 16:07:50 +0000 (GMT) (envelope-from arne@rfc2549.org) Received: by coruscant.rfc1149.org (Postfix, from userid 110) id 927B23F14; Thu, 23 Sep 2004 18:07:48 +0200 (CEST) Received: from kamino.rfc1149.org (kamino.rfc1149.org [2001:8d8:81:11::2]) by coruscant.rfc1149.org (Postfix) with ESMTP id A356A3C85; Thu, 23 Sep 2004 18:07:40 +0200 (CEST) Received: by kamino.rfc1149.org (Postfix, from userid 1001) id D861540F1; Thu, 23 Sep 2004 18:07:36 +0200 (CEST) To: Oliver Lehmann In-Reply-To: <20040923175411.7eeb0ee9.lehmann@ans-netz.de> (Oliver Lehmann's message of "Thu, 23 Sep 2004 17:54:11 +0200") References: <20040923062411.7b5a70d7.lehmann@ans-netz.de> <20040923175411.7eeb0ee9.lehmann@ans-netz.de> From: Arne Schwabe Date: Thu, 23 Sep 2004 18:07:36 +0200 Message-ID: <86r7ot0y0n.fsf@kamino.rfc1149.org> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on coruscant.rfc1149.org X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.60 X-Spam-Level: cc: Tim Kientzle cc: freebsd-current@freebsd.org Subject: Re: bsdtar doesn't detect end of tape X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 23 Sep 2004 16:07:51 -0000 Oliver Lehmann writes: > Tim Kientzle wrote: > >> Try the attached patch to src/lib/libarchive, >> rebuild libarchive and bsdtar and let me >> know if it fixes it for you. > > It looks like the patch is against the wrong file. IT actually will turn > current to stable... But i think wee need the other direction ;) Can you > please "turn it around" and resend it? Look at patch -R :) -R, --reverse tells patch that this patch was created with the old and new files swapped. (Yes, I'm afraid that does happen occasionally, human nature being what it is.) Patch will attempt to swap each hunk around before applying it. Rejects will come out in the swapped format. The -R option will not work with ed diff scripts because there is too little information to reconstruct the reverse opera- tion. If the first hunk of a patch fails, patch will reverse the hunk to see if it can be applied that way. If it can, you will be asked if you want to have the -R option set. If it can't, the patch will continue to be applied normally. (Note: this method cannot detect a reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends always succeed, due to the fact that a null context will match anywhere. Luckily, most patches add or change lines rather than delete them, so most reversed normal diffs will begin with a delete, which will fail, triggering the heuristic.) -- compiling millions of tiny c-programs...done checking for a working configure script... not found