[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE 3.0.4 MD5checksum



'fraid not.  No proxy here.

Todd


On Thu, 2002-10-10 at 18:47, Nick Boyce wrote:
> On 10 Oct 2002 17:16:18 -0400, Todd Charron wrote:
> 
> >I got that error from that server as well.  Switched download.uk.kde.org
> >and everything went through fine.  Not sure what's up with
> >download.us.kde.org though...
> >
> >Todd
> >
> >On Thu, 2002-10-10 at 17:14, Alexander Opitz wrote:
> >> Hi,
> >> 
> >> I'll update KDE from 3.0.3 to 3.0.4 but I get following MD5 error.
> >> 
> >> Get:1 http://download.us.kde.org ./ konqueror 4:3.0.4-1 [1749kB]
> >> Get:2 http://download.us.kde.org ./ noatun-plugins 4:3.0.4-1 [260kB]
> >> Get:3 http://download.us.kde.org ./ kdeartwork-theme-desktop 4:3.0.4-1 
> >> [6572kB]
> >> Fetched 8581kB in 1m37s (88.1kB/s)
> >> Failed to fetch 
> >> http://download.us.kde.org/pub/kde/stable/latest/Debian/sid/./i386/kdebase/konqueror_3.0.4-1_i386.deb  
> >> MD5Sum mismatch
> 
> Interestingly, I've been getting exactly the same symptom (and various
> other file content failures and connection failures) for a couple of
> weeks, on our two Woody systems inside our company network behind a
> proxy firewall.
> 
> But I think I've just fixed it all (today) by setting :
>    acquire::http::queue-depth="0"
> in apt.conf - certainly I had no failures after making this change. I
> may be wrong about the parameter being called "queue-depth" - I'm not
> at a Woody system at the moment - but check out the apt.conf man page,
> where reference is made to this setting being required if your HTTP
> proxy doesn't handle idling a connection properly (or something like
> that) - with data corruption being the result otherwise.
> 
> Are you guys behind a proxy firewall ?
> 
> Sorry if this is off-track.
> 
> Nick Boyce
> Bristol, UK
> --
> There is no spoon.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-kde-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 




Reply to: