Forum Posts

Could you please remove the 'failed' tag off all enlistments for NetBSD going to CVS :pserver:anoncvs:@anoncvs.netbsd.org:/cvsroot? Both those currently enlisted but failed, and the ones not currently ... [More] in the list: Adding them bit by bit seems to work now, and I'd add some more missing pieces once the currently listed parts were imported. [Less]

Hi, do you have any policy regarding deceased developers? regards, spz

I've now thrown a different approach at the problem, which seems to work: pkgsrc is now enlisted as 58 repositories, each category on its own, and I'm doing the same to the directories under src ... [More] (where we will end up with 30 repositories for src unless I need to split src/sys and src/gnu which will make it worse). [Less]

I already tried a traceroute in the opposite direction (assuming www.ohloh.net is the target) and didn't see anything obvious: 1. exit.sf-nbsd.sfo2.isc.org (204.152.190.1) 0.342 ms 0.396 ms 0.243 ... [More] ms 2. int-0-1-0-606.r3.sfo2.isc.org (149.20.65.4) 1.093 ms 0.914 ms 0.976 ms 3. int-0-1-0.r4.sfo2.isc.org (149.20.65.22) 20.845 ms 19.330 ms 19.406 ms 4. int-0-3-0.r5.sfo2.isc.org (149.20.65.26) 4.019 ms 22.739 ms 20.108 ms 5. int-0-1-0.r1.pao1.isc.org (149.20.65.21) 1.531 ms 1.470 ms 1.561 ms 6. ge-1-11.r03.plalca01.us.bb.gin.ntt.net (140.174.21.193) 1.680 ms 1.791 ms 1.846 ms 7. xe-2-1-0.r21.plalca01.us.bb.gin.ntt.net (129.250.4.245) 1.971 ms 1.840 ms 1.851 ms 8. ae-1.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.33) 2.557 ms 2.885 ms 2.723 ms 9. p64-0-0-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.4.22) 21.873 ms 21.924 ms 21.888 ms 10. po-2.r00.sttlwa01.us.bb.gin.ntt.net (129.250.2.205) 21.865 ms 21.891 ms 23.200 ms 11. ge-0.isomedia.r00.sttlwa01.us.ce.gin.ntt.net (204.2.144.10) 21.571 ms 21.561 ms 21.302 ms 12. core-01-ge-0-2.sttl.isomedia.com (207.115.64.163) 21.424 ms 21.145 ms 21.289 ms 13. gate-02-pos-4-0.rdmd.isomedia.com (207.115.66.73) 23.034 ms 22.997 ms 22.337 ms 14. red-ptp.isomedia.com (207.115.64.101) 23.616 ms 23.294 ms 23.798 ms 15. 207.115.86.98 (207.115.86.98) 22.744 ms 24.004 ms 23.953 ms (I don't expect there to be a problem with ISC or NTT. I don't know isomedia.com and wether they have a 'suspicious network activity' filter going, but I'd assume the ohloh.net people would have noticed previously if that was the case.) Also, the data needs to get to ohloh.net somehow, and ftp reget does have its advantages in that it'll let you proceed (and before you're old and gray, too :-P ) [Less]

Andy: the purpose of the tarball would be to get the bulk of the data to you with a protocol that does reget. I'd expect you to be continuing with rsync after; that would only transfer subsequent ... [More] changes (and a bit of meta-info like checksums). Our anoncvs mirrors also use rsync (and sometimes also offer rsync). Give me a nudge when you have time for the ftp job, I'll put up fresh tarballs for you then. [Less]

We don't have cvsync on anoncvs.netbsd.org, and I'm not aware of a mirror offering it either. People wanting the entire repository usually use rsync, like garbled mentioned already. Please consider ... [More] the size of the repository (du -sk) 785269 htdocs/ 28621 othersrc/ 2920266 src/ 958628 xsrc/ Would starting you out with tarballs (for ftp) help? [Less]