I have tested pacman recompiled with a 40 sec fetchTimeout rather than 10. But first I began by recommenting out the XferCommand in /etc/pacman.conf, first rebuild pacman without modifications with abs to get sure the errors was there, then tried to make the modification then use abs, but realized I was changing nothing, so I rechange fetchTimeout in pacman-3.3.3/lib/libalpm/dload.c to 40 then use ./configure prefix=/usr/local, make, #make install, and then used #/usr/local/bin/pacman -Syu I have left it all the night (about 8 hours) and only had one error getting gimp (maybe the package was really not there anymore). That said, I may boost it to 50 secs rather than 40, because a while, I was counting manually about by 1 by 1 second when it seems stopped, and once got up to 33. I hope you will boost the fetchTimeout value for others people using a slow connection like me. Thank you again Jonathan for the hint! 2010/2/16, Nagy Gabor <ngaba@bibl.u-szeged.hu>:
On Tue, Feb 16, 2010 at 3:25 PM, Paul Dufresne <dufresnep@gmail.com> wrote:
Well, I have lots of errors while downloading packages with pacman, and almost never while downloading files from Shiretoko Firefox.
I have tried many mirrors, that's the same for each.
Oh... I use a 56k modem (Intel 536EP Data Fax modem).
But even while downloading in Firefox, it sometimes give me the feeling it has stopped downloading for about 40 secs... while pacman seems to give up after about 20 secs.
I did not tried yet to download with wget or curl (does pacman use one of them?).
Is there a constant I could change in the code, and rebuild it?... I did not download the code of pacman yet.
Using arch with a 56k modem is called masochism :)
Seriously, I would never do that, I would just get a dvd of a linux distribution that already contains a lot of software.
If that doesn't make any sense.. well, curl and wget are indeed known to behave more nicely than libfetch with crap connections.
I used Arch without internet for a while. :-) (-Sp)
Xavier, I am happy to hear that someone uses a slow connection, at least we have a beta-tester for timeout-related patches. Maybe this is a good occasion to test fetchTimeout. ;-)
Bye