Please note: Unlike the wine/ptex-base dependancy issue discussed separately, this one does not constitute a problem to _myself_ at the time of writing. If I just experienced an atypical burst of rare failures, we may quickly drop it. Otherwise, please read on.
On Sat, 19 Dec 2009 22:30:22 +0100, Alexander Hansen <[email protected]> wrote: > Fink isn't really set up to give a failsafe automated download of a > complicated dependency tree. Thank you for this information. I was not aware of this limitation. Wine may well have one of the largest dependency trees, so I understand that the amount of potential problems sums up, as well. Nevertheless I am surprised by the sheer amount of interaction required. > It's almost impossible to tell you definitively what is going on here > just from a short description of the problem. > Some potential reasons for downloads not working are: > > 1) The source isn't available from the original download location any > more, but only from Fink's mirrors. > 2) A package description is too new for the Fink mirrors to have picked > it up (it takes some time to do so) and it's only available from the > original source. > 3) The source file is so new that not all of the mirrors in a network > (like sourceforge.net's download mirrors) have picked it up, and so it's > only available from a reduced set of those. > > Without seeing specific examples as they occur, though, we really can't > tell you anything. $ pbpaste | grep -oEe '( (ht|f)tp://|^curl: \().*$' - I have searched the 192837 lines Fink Commander's buffer could hold for failed URLs and pasted them here (261 lines): http://paste-it.net/public/h83fed9/ There are 150 package URLs in that excerpt. Every line of the form curl: ($exit_code) $error_message denotes a failed download attempt. There are 101 such lines, each of which corresponds to a manual choice I had to make. So, only 49 out of 150 downloads have succeeded. Since this issue does not seem to be constrained to a particular package. I am left to hope there is a systemic reason to it and a more general solution than working through hundreds of download failures one by one. Zoo Loo ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
