Wiadomość napisana przez Bartłomiej Rutkowski <r...@robakdesign.com> w dniu 26 
maj 2014, o godz. 22:23:

> 
> Wiadomość napisana przez John Marino <freebsd.cont...@marino.st> w dniu 26 
> maj 2014, o godz. 22:18:
> 
>> On 5/26/2014 22:12, Bartłomiej Rutkowski wrote:
>>> SHA256 (demjson-2.0.tar.gz) = 
>>> 24f638daa0c28a9d44db2282d46ea3edfd4c7d11a656e38677b741620bf1483d
>>> SIZE (demjson-2.0.tar.gz) = 115914
>>> 
>>> what perfectly matches what the author says it should be. I've asked him if 
>>> he can check his release system and distfiles providers to see if he can 
>>> spot any changes and if he can by any chance match our sum/size that's 
>>> incorrect to anything around there.
>>> 
>>> Any chance you or anyone else have the 'bad' distfiles available on their 
>>> system for inspection?
>> 
>> I have the original 2.0 (One of the ones upstream says never existed):
>> http://muscles.dragonflybsd.org/misc/demjson-2.0.tar.gz
>> 189103 May 26 13:15 demjson-2.0.tar.gz
>> 
>> So 2.0 built once, but then the distfile changed not once but twice and
>> the 115k version is the at least the 3rd iteration.  I never got the
>> intermediate iteration.
>> 
>> Regards,
>> John
>> 
> 
> Thanks - I've passed that to the author and I am waiting for his thoughts on 
> what's happening here. I'll inspect the distfile on my own as soon as 
> possible, most probably tomorrow - I'll update you if I find anything.
> 
> Kind regards,
> Bartek Rutkowski

John, would you still have the logs showing from which distribution channgel 
this file was fetched on your system? That would help to figure out what's 
happening, if we could track down where it is happening. 

So far the author said your distfile 'looks like his code with some additional 
debug files included, that should not be there'.

Kind regards,
Bartek Rutkowski
_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"

Reply via email to