From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2540 invoked by alias); 8 Sep 2002 07:36:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2512 invoked by uid 71); 8 Sep 2002 07:36:01 -0000 Resent-Date: 8 Sep 2002 07:36:01 -0000 Resent-Message-ID: <20020908073601.2511.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, java-prs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, 116145@bugs.debian.org Received: (qmail 642 invoked by uid 61); 8 Sep 2002 07:27:47 -0000 Message-Id: <20020908072747.641.qmail@sources.redhat.com> Date: Sun, 08 Sep 2002 00:36:00 -0000 From: 116145@bugs.debian.org Reply-To: 116145@bugs.debian.org To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: libgcj/7854: fastjar update (-u) should be implemented X-SW-Source: 2002-09/txt/msg00113.txt.bz2 List-Id: >Number: 7854 >Category: libgcj >Synopsis: fastjar update (-u) should be implemented >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sun Sep 08 00:36:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: 116145@bugs.debian.org >Release: 3.2 / HEAD >Organization: >Environment: >Description: [known, but not in GNATS yet, see http://bugs.debian.org/116145] fastjar's -u option is disabled due to corrupted archives. Per Bothner responded: Yes, I ran into the same problem. Basically the implementation of 'u' is pretty much not there. I looked at trying to fix it, but decided I didn't have time. Until somebody fixes it, we should change fastjar to exit with an error on 'u'. The first question is whether fastjar should try to update in place or create a temporary file and copy it over. The former is faster, especially when just adding files, and is less liable to run out of disk space. However, it is tricky when files are replaced that are not at the end. In that case I guess the solution is to read the archive members that need to be moved into main memory. Then it is just a small matter of programming ... >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: