Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of
 robertburrelldonkin@blueyonder.co.uk designates 195.188.213.9 as permitted
 sender)
Subject: Re: [codec] invalid source tarball on www.apache.org/dist
From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <loom.20060107T211437-149@post.gmane.org>
References: <loom.20060107T211437-149@post.gmane.org>
Content-Type: text/plain
Date: Sun, 08 Jan 2006 22:49:06 +0000
Message-Id: <1136760546.31032.50.camel@knossos.elmet>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sat, 2006-01-07 at 20:18 +0000, Tim O'Brien wrote:
> This file 
> 
> http://www.apache.org/dist/jakarta/commons/codec/source/commons-codec-1.3-src.tar.gz
> 
> doesn't have the appropriate commons-codec-1.3/ directory in front of each
> entry.  When you unpack it in a directory, it just throws the contents of the
> source distro into the current directory.
> 
> So, to fix this, I propose re-releasing this one file.  I wasn't the release
> manager for the 1.3 release, but I'd be happy enough to repackage just this
> release from source, sign and seal it.
> 
> Does anyone have any objections to replacing the 1.3 source release with a file
> that follows the convention?

making changes to existing releases without increasing version numbers
is usually frowned upon (but i won't -1). you may find yourself in
trouble with the release watchers if you do this without letting them
know first. may want to check on repo or infra whether this would be a
good idea.

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org