On Dec 16, 4:10 pm, James Bennett <ubernost...@gmail.com> wrote:
> On Wed, Dec 16, 2009 at 2:13 PM, Michael K <mk...@arikel.net> wrote:
> > Should I take the silence to mean I should open a bug report?
>
> I clicked the "download" link for Django 1.1.1, and the package
> downloaded. On finishing the download, I was able to checksum it and
> get the same results as the signed checksum document provided at the
> time of the release:http://media.djangoproject.com/pgp/Django-1.1.1.checksum.txt
>
> Thus, the problem is most likely not with anything on
> djangoproject.com; instead, it's probably something related to your
> own Internet connection.
>
My first assumption was that it was my network connection, but I've
had no issues downloading from any other site - just
djangoproject.com.
It's been a couple of days, I'll try it again.
Thanks for the response!
--
Michael
On Dec 18, 2:10 pm, Michael K <mk...@arikel.net> wrote:
> On Dec 16, 4:10 pm, James Bennett <ubernost...@gmail.com> wrote:> On Wed, Dec 16, 2009 at 2:13 PM, Michael K <mk...@arikel.net> wrote:
> > > Should I take the silence to mean I should open a bug report?
>
> > I clicked the "download" link for Django 1.1.1, and the package
> > downloaded. On finishing the download, I was able to checksum it and
> > get the same results as the signed checksum document provided at the
> > time of the release:http://media.djangoproject.com/pgp/Django-1.1.1.checksum.txt
>
> > Thus, the problem is most likely not with anything on
> > djangoproject.com; instead, it's probably something related to your
> > own Internet connection.
> It's been a couple of days, I'll try it again.
>
> Thanks for the response!
Still having the same issue. I'm on a windows machine, but even if I
use wget on one of the Solaris machines, the TAR is reported as having
no files and/or is corrupted.
Is there another download location I can try?
--
Michael
James,
Thanks for the response on this, it made me think of something else to
try - a different web browser. It seems Chrome beta doesn't like
something about the delivery of the tar.gz. When I used IE, the file
opened first try.
I also realized the problem with the wget is the same as my SVN issue
- except in this case, the Solaris machines are blocked from using the
proxy server in question. Once I changed the environment to point to
the appropriate one, I also got the file from there.
Sorry to waste the bandwidth, but hopefully someone will search for
download issues - and if they're running Chrome, they'll know what's
up.
--
Michael
PS: Chrome version is 4.0.266.0