On Fri, 15 Mar 2002, Anand Kumria wrote:

Hi, 

please note that parts of this mail refer to the original poster(s) and
others to subsequent followups.

> > Honestly, the best thing I can suggest is not to use mirror.aarnet. It's
> > been stuffed for quite some time, and I don't think it fully recovered.
> > Planetmirror works best for me, and there's also Monash and many other
> > Australian mirrors. Use them. :)
> 
> mirror.aarnet.edu.au and planetmirror.com are maintained by the same group
> of people. So if one is broken, both are. If you do find one or the other
> broken (and it isn't a proxy), since they can't monitor everything, it
> always helps to report the problem.
>
> The problem arises because none, as far as I know, of the .au mirrors are
> being "pushed" when updates happen on the main debian. This means they poll
> the site regularly and sometimes you might download either the Packages files
> or the .deb in the middle of being updated.

actually, thanks to efforts by anthony towns and ryan murray from the debian
group, planetmirror.com (aka ftp.au.debian.org) is now in the list of push
mirrors from the debian master.  in addition it attempts to sync daily if
a push hasn't happened.

mirror.aarnet sync's twice daily from planetmirror.com.  we attempt to
provide the best possible mirror coverage at both sites.


To the original poster:

if there is a problem please _tell_ me and i can attempt to fix it.

<rant>
simply saying "don't use mirror.aarnet" is akin to saying "there is a problem
with some software.  we shouldn't fix it. rather, don't use debian. don't use
linux.  in fact don't use opensource,  it's broken."  
</rant>

i might not be able to get back to you immediately but i tend to start
looking to see if there are any problems straight away.

> Typically you can recover from this by:
>       - deleting the (partial) .deb from /var/cache/apt/archive (or 
>       where it is loacted)
>       - perform: $ apt-get update
>       - try again.
> 
> These kinds of problems tend to also be compounded by having proxies in
> the middle (the proxy caches the incorrect response) so if you can bypass
> the proxy that might also help.

thanks for the followup anand and the suggested solutions.  indeed we've had
a number of people contact us about (non debian related) download issues and
managed to trace it back to a transparent (or otherwise) proxy issue which
is corrupting data, affecting timestamps etc.

regards,

-jason

-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to