                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of daniele.varra...@gmail.com designates 209.85.215.43 as permitted sender) client-ip=209.85.215.43;
MIME-Version: 1.0
In-Reply-To: <1914550.zLLheb3vXl@ropc>
References: <1b128157-6168-413e-8605-187568afbaf0@googlegroups.com>
 <1942020.6JzFNb2sZb@ropc> <CA+mi_8bkZjNKN1L9niDdQg+VQsQYoBsfpaJhvFqVy9HwEzQ...@mail.gmail.com>
 <1914550.zLLheb3vXl@ropc>
From: Daniele Varrazzo <daniele.varra...@gmail.com>
Date: Wed, 10 Oct 2012 14:03:16 +0100
Message-ID: <CA+mi_8ZB8=N_bdW2UY3Cp2hsW6_pPfV2UQHxp=d1zg=kqPH...@mail.gmail.com>
Subject: Re: Semver and prerelease
To: Ronan Dunklau <ronan.dunk...@kozea.fr>
Cc: pgxn-users@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 10, 2012 at 1:57 PM, Ronan Dunklau <ronan.dunk...@kozea.fr> wrote:
>> I would also tell you: don't bother with the issue and release
>> 1.0.0beta. If we'll have a purge we can wait for you to release 1.0.0
>> before that.
>
> That's all I wanted to read ! Thank you.
>
> However, I don't know if my file is malformed or anything else, but I get
> errors in the pgxn manager.
>
> Either a full perl traceback, or a message informing me that PGXN is not
> capable of parsing my JSON file due to an "illegal character".
>
> I've tested the JSON file directly from the zip file I want to upload, and it is
> parsable with the python json module.
>
> Is there any known problem on pgxn ?

Not a known one. I think posting your META.json would help David
debugging the issue.

-- Daniele