Pkgsrc problems [ was: lang/python24 build problems]

[Matthew Dillon]

   Well, one thing I've noticed on pkgbox is that there are very large swaths
   of time where the whole build process seems to just stop, getting stuck
   (or slowed down) on a single ftp line.  For example:

  PID  TT  STAT      TIME COMMAND
17447  p1  ILs    0:00.01 -tcsh (tcsh)
17449  p1  IL     0:00.02 -su (csh)
17455  p1  IL     0:00.02 /bin/csh -i
17461  p1  IL+    0:00.00 /bin/sh /usr/pkg_bulk/libexec/pbulk/build
17462  p1  IL+    0:04.37 /usr/pkg_bulk/bin/pbulk-build -r /bulklog/meta/pbuild -v -b /usr/pkg_bulk/libexec/pbulk/pkg-build /bulklog/meta/presolve /bulklog/meta/success /bulklog/meta/error
67617  p1  IL+    0:00.00 /bin/sh /usr/pkg_bulk/libexec/pbulk/pkg-build
67891  p1  IL+    0:00.21 /usr/pkg/bin/bmake checksum BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/bulklog/mailsync-5.2.1nb2/work.log
68028  p1  IL+    0:00.00 /bin/sh -c set -e;^I^I^I^I unsorted_sites="http://dfn.dl.sourceforge.net/sourceforge/mailsync/ http://easynews.dl.sourceforge.net/sourceforge/mailsync/ http://heanet.dl.sourceforge.net/sourceforge/mailsync/ http://garr.dl.sourceforge.net/sourceforge/mailsync/ http://internap.dl.sourceforge.net/sourceforge/mailsync/ http://jaist.dl.sourceforge.net/sourceforge/mailsync/ http://kent.dl.sourceforge.net/sourceforge/mailsync/ http://mesh.dl.sourceforge.net/sourceforge/mailsy
nc/ http://nchc.dl.sourceforge.net/sourceforge/mailsync/ http://optusnet.dl.sourceforge.net/sourceforge/mailsync/ http://superb-east.dl.sourceforge.net/sourceforge/mailsync/ http://superb-west.dl.sourceforge.net/sourceforge/mailsync/ http://surfnet.dl.sourceforge.net/sourceforge/mailsync/ http://switch.dl.sourceforge.net/sourceforge/mailsync/ http://ufpr.dl.sourceforge.net/sourceforge/mailsync/ http://belnet.dl.sourceforge.net/sourceforge/mailsync/";^I^I^I sites=" $unsorted_sites ftp:/!
 /ftp.fi.NetBSD.org/pub/NetBSD/packages/distfiles/ ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/ http://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/ ftp://ftp.FreeBSD.org/pub/FreeBSD/distfiles/";^I^I cd /distfiles &&^I^I^I /usr/bin/env CHECKSUM=/usr/bin/env\\ DIGEST=/usr/pkg/bin/digest\\ CAT=/bin/cat\\^I\\^I\\ ECHO=echo\\ SED=/usr/bin/sed\\^I\\^I\\^I\\ TEST=test\\^I\\^I\\^I\\^I\\^I\\ /bin/sh\\ /usr/pkgsrc/mk/checksum/checksum^I^I^I CP=/bin/cp^I^I^I^I ECHO=echo^I^I^I^I FETCH_CMD=/usr/bin/
ftp^I^I^I FETCH_BEFORE_ARGS=\\ ^I FETCH_AFTER_ARGS=^I^I FETCH_RESUME_ARGS=-R^I FETCH_OUTPUT_ARGS=-o^I MKDIR=/bin/mkdir MV=/bin/mv^I^I TEST=test TOUCH=/usr/bin/touch^I WC=/usr/bin/wc^I^I^I^I /bin/sh /usr/pkgsrc/mk/fetch/fetch  -c -f /usr/pkgsrc/mail/mailsync/distinfo mailsync_5.2.1.orig.tar.gz $sites
68029  p1  IL+    0:00.00 /bin/sh /usr/pkgsrc/mk/fetch/fetch http://easynews.dl.sourceforge.net/sourceforge/mailsync/ http://heanet.dl.sourceforge.net/sourceforge/mailsync/ http://garr.dl.sourceforge.net/sourceforge/mailsync/ http://internap.dl.sourceforge.net/sourceforge/mailsync/ http://jaist.dl.sourceforge.net/sourceforge/mailsync/ http://kent.dl.sourceforge.net/sourceforge/mailsync/ http://mesh.dl.sourceforge.net/sourceforge/mailsync/ http://nchc.dl.sourceforge.net/sourceforge/mailsync/ htt
p://optusnet.dl.sourceforge.net/sourceforge/mailsync/ http://superb-east.dl.sourceforge.net/sourceforge/mailsync/ http://superb-west.dl.sourceforge.net/sourceforge/mailsync/ http://surfnet.dl.sourceforge.net/sourceforge/mailsync/ http://switch.dl.sourceforge.net/sourceforge/mailsync/ http://ufpr.dl.sourceforge.net/sourceforge/mailsync/ http://belnet.dl.sourceforge.net/sourceforge/mailsync/ ftp://ftp.fi.NetBSD.org/pub/NetBSD/packages/distfiles/ ftp://ftp.NetBSD.org/pub/NetBSD/packages/d!
 istfiles/ http://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/ ftp://ftp.FreeBSD.org/pub/FreeBSD/distfiles/
68030  p1  IL+    0:00.00 /usr/bin/ftp http://dfn.dl.sourceforge.net/sourceforge/mailsync/mailsync_5.2.1.orig.tar.gz

    It has been stuck on fetching mailsync for probably an hour.  That
    can't be good for the bulk build process.

    Justin, if you would like I do have several 700+ GB drives I can put
    into service for archiving the source tarballs, if that would help.
    If you can get rid of all or most of the remote ftp's it would speed
    up the build considerably.

						-Matt