Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 30F651C315B1
	for <pgsql-announce@postgresql.org>;
	Wed, 18 Apr 2012 11:07:52 -0300 (ADT)
Received: from mail-gx0-f174.google.com ([209.85.161.174])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <markokr@gmail.com>) id 1SKVXv-0004Nu-D1
	for pgsql-announce@postgresql.org; Wed, 18 Apr 2012 14:07:51 +0000
Received: by gghe5 with SMTP id e5so3663209ggh.19
	for <pgsql-announce@postgresql.org>;
	Wed, 18 Apr 2012 07:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=Jr6x6GSxrsrNObH2Caa4N6ladB1xTROlQ7SB/HF58xk=;
	b=EQP78l0Ex5LuuxgaTbrBgj6FVWyHaRDKS/LMLWkgkZgLGyohAqZDspsgY6nIhp1pPc
	O8DL6ZgOjCQYY1NH4GMNinvo9hR5zbipsuh8bhA3mTGs1bswy8vrPSxm5GgU4mYHNxZn
	XhrUgTKBkpiopX04UFW3I3xDf8CFXPUkPDgvVOXpXjusG8TeA70UZ4TvZLxnadUVyfyx
	ybyb98OsrnGxW0JHc21+pJYLyHc92CK/aWlX20J5huS4oFhRt4CTtFi1CQoiNswCkQCe
	FHkqSQ2DLuaVOz0PhlHdoeIIL2lO/J/49oBIrtCS72DuYScQYuQjjELeeNjuoMtggbOd
	SP3g==
MIME-Version: 1.0
Received: by 10.236.79.8 with SMTP id h8mr2367855yhe.79.1334758054732; Wed, 18
	Apr 2012 07:07:34 -0700 (PDT)
Received: by 10.236.111.11 with HTTP; Wed, 18 Apr 2012 07:07:34 -0700 (PDT)
In-Reply-To: <op.wcxilcpt34t2sn@tech304>
References: <20120417145644.GB3667@gmail.com>
 <20120417150059.GA3753@gmail.com>
	<op.wcxilcpt34t2sn@tech304>
Date: Wed, 18 Apr 2012 17:07:34 +0300
Message-ID: 
 <CACMqXC+Q80kmUY7uqY1Rc3VgQHFaYYNzu4HnpL01PAMf4vtjfA@mail.gmail.com>
Subject: Re: PgBouncer 1.5.1
From: Marko Kreen <markokr@gmail.com>
To: Mark Felder <feld@feld.me>
Cc: Postgres Announce <pgsql-announce@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Pg-Spam-Score: -2.6 (--)
X-Archive-Number: 201204/15
X-Sequence-Number: 2218

[Re-reply to keep -announce in the loop..]

On Wed, Apr 18, 2012 at 12:42 AM, Mark Felder <feld@feld.me> wrote:
> I just realized that PgBouncer 1.5 and 1.5.1 have identical checksums, which
> I noticed after I already reported to the maintainer the issue with the
> extracted folder being named pgbouncer-1.5 instead of having the proper
> version.
>
> I guess the real issue is that pgbouncer 1.5.1 is vaporware right now :-)

The .tar.gz on pgfoundry.org looks OK, so this must be some local problem.

-- 
marko