You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2010/03/18 22:34:53 UTC

Re: JCC 2.5.1 tarball broken

On Mon, 8 Mar 2010, Ludovico Cavedon wrote:

> Hi Andi,
> looks like the latest tarball for JCC (JCC-2.5.1.tar.gz) uploaded on [1]
> is broken, i.e. there are some files missing:
> -DESCRIPTION
> -CHANGES
> -all  (or at least most) .h files
>
> [1] http://pypi.python.org/pypi/JCC/

Indeed, the tar archive for JCC 2.5.1 on pypi - as produced by setup.py 
sdist - was woefully incomplete. I can reproduce the problem but only on 
this branch. This is rather strange. On trunk, sdist produces a correct 
archive.

Not having too much time to debug this, I manually corrected the archive and 
uploaded it again to pypi. Sorry for taking so long to do this, I was 
offline last week and only remembered now.

Andi..

Re: JCC 2.5.1 tarball broken

Posted by Andi Vajda <va...@apache.org>.
On Thu, 18 Mar 2010, Ludovico Cavedon wrote:

> On Thu, Mar 18, 2010 at 2:34 PM, Andi Vajda <va...@apache.org> wrote:
>> Indeed, the tar archive for JCC 2.5.1 on pypi - as produced by setup.py
>> sdist - was woefully incomplete. I can reproduce the problem but only on
>> this branch. This is rather strange. On trunk, sdist produces a correct
>> archive.
>>
>> Not having too much time to debug this, I manually corrected the archive and
>> uploaded it again to pypi. Sorry for taking so long to do this, I was
>> offline last week and only remembered now.
>
> No problem. Thank for updating the tarball.
> I uploading the updated packge in Debian.
> I have two comments:
> - the JCC.egg-info/SOURCES.txt is still incomplete (missing .h files),
> but AFAIK it is not a problem.

I found a way around the problem by adding all the missing stuff to 
MANIFEST.in, something I never had to do before. The problem also started 
happening on trunk :(

This also fixes the SOURCES.txt problem. I uploaded a new archive again to 
pypi produced from this new MANIFEST.in file. I verified that the list of 
files is the same as yesterday's. The only changes in content are the 
MANIFEST.in file and SOURCES.txt.

> - the "--home" option is not documented in the help

That's now fixed in trunk rev 925304 (ie, not in 2.5.1).

Andi..

Re: JCC 2.5.1 tarball broken

Posted by Ludovico Cavedon <lu...@gmail.com>.
On Thu, Mar 18, 2010 at 2:34 PM, Andi Vajda <va...@apache.org> wrote:
> Indeed, the tar archive for JCC 2.5.1 on pypi - as produced by setup.py
> sdist - was woefully incomplete. I can reproduce the problem but only on
> this branch. This is rather strange. On trunk, sdist produces a correct
> archive.
>
> Not having too much time to debug this, I manually corrected the archive and
> uploaded it again to pypi. Sorry for taking so long to do this, I was
> offline last week and only remembered now.

No problem. Thank for updating the tarball.
I uploading the updated packge in Debian.
I have two comments:
- the JCC.egg-info/SOURCES.txt is still incomplete (missing .h files),
but AFAIK it is not a problem.
- the "--home" option is not documented in the help

Thanks,
Ludovico