debmirror is the same either way, it selects what it wants and only rsyncs the files it needs. However, it only makes one connection for every 300 files or whatever the value of --rsync-batch. I also use the rsync method to probe for various optional components such as installers and upgraders and use the to customise the debmirror arguments. It is simpler for me to use rsync for all, and possibly more efficient.SysAdmin wrote:Why not use debmirror with http? It's how our mirror gets generated. debmirrorsamarium wrote:Can't really agree with "excellent" when I can't use rsync.
Since I can't rsync from the exetel mirror, I probably do 20GB-100GB a month to another mirror that does allow me to use rsync, so I can maintain my own debmirror.
is nicely picky about what files it needs so it's effectively a diff-type
download anyway.
How to you get things like main/dist-upgrader-all main/installer-{i386,amd64} and the various meta-releases?
What debmirror command are you using? Maybe I'm doing things the hard way and debmirror has improved and I can be lazier and my script simpler.
Last time I looked it was probably maverick, or maybe even lucid, and it was simply a case of what I wanted wasn't there so went to look elsewhere, haven't looked since until my post and was pleasantly surprised to find precise already happening.SysAdmin wrote:It's maintainment of policy. I try to keep the current live release versionssamarium wrote: [The other problem with the exetel mirror used to be that it didn't maintain the current development dist, ie currently "precise", so I used to need to look elsewhere for that anyway. Not sure if the current mirror including precise reflects a change of policy or not.
of ubuntu plus the next upcoming one on the mirror. What happened there is
that the site we were feeding off broke. We've changed that and it should be
updating fine.