forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-472) All plugin zip files are corrupt when downloaded
Date Thu, 24 Mar 2005 20:48:18 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Thu, 24 Mar 2005 2:48 PM
This issue appears to have fixed itself. APache were doing some work on their servers over
the last weekend when this issue was first spotted. Perhaps it was as a result of that work.

Anyway, can someone please confirm that everything is now working correctly for you too.

View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-472
    Summary: All plugin zip files are corrupt when downloaded
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Forrest
             Plugins (general issues)

   Reporter: Vincent Bray

    Created: Mon, 21 Mar 2005 6:13 AM
    Updated: Thu, 24 Mar 2005 2:48 PM
Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)

I'm on the -user list but not the -dev list.

[noodl@blackbird forrest]$ svn info
Path: .
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 158452
Node Kind: directory
Schedule: normal
Last Changed Author: crossley
Last Changed Rev: 158414
Last Changed Date: 2005-03-21 05:21:36 +0000 (Mon, 21 Mar 2005)
Properties Last Updated: 2005-03-01 16:05:25 +0000 (Tue, 01 Mar 2005)

[noodl@blackbird forrest]$ zipinfo build/plugins/
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
zipinfo:  cannot find zipfile directory in one of build/plugins/ or
          build/plugins/, and cannot find build/plugins/,

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message