I just got a reply from the developers, reportedly there are no real difference
and they will try to take care of this, so the problem might be gone soon. For
the moment, I workaround the problem by using the bzip2 tarball which is not
effected.
~petr
On Dec 12, 2013, at 15:45 , "Daniel J. Lu
you may also want to download both and diff them yourself to see if there are
any 'real' differences.
On Dec 12, 2013, at 9:38 AM, Jeremy Lavergne wrote:
>
> It's entirely up to you, as there's already a split on which one to use. I'd
> personally go upstream since its the official host of the
It's entirely up to you, as there's already a split on which one to use.
I'd personally go upstream since its the official host of the software.
Peter Danecek wrote:
But which one would you consider "correct" than?
Apache because it is upstream, or PyPI because it is probably the one more
freq
But which one would you consider "correct" than?
Apache because it is upstream, or PyPI because it is probably the one more
frequently installed.
On Dec 12, 2013, at 15:27 , Jeremy Lavergne wrote:
> Choose to get rid of one of the master sites.
>
> Peter Danecek wrote:
>> The published chec
Choose to get rid of one of the master sites.
Peter Danecek wrote:
The published checksums correspond for each source, but do not match, so the
tarball is effectively different. I filed a ticket for this, but how would you
deal with such an situation in general or if there is no reply.
__
Hi all,
I have a problem with matching checksums and realise that the "same" tarball
(by name) is actually different depending on the download sites. This is from
my Apache libcloud port:
master_siteswww.apache.org/dist/libcloud/ \
https://pypi.python.org/packages/s
