Re: md5 sum mismatches and mirror syncs

2006-08-12 Thread Goswin von Brederlow
martin f krafft <[EMAIL PROTECTED]> writes: > also sprach Goswin von Brederlow <[EMAIL PROTECTED]> [2006.08.11.2326 +0100]: >> The algorithm used is 2pass. First pass only mirrors pool while the >> second pass mirrors the Release and Packages files. The time a mirror >> is out of sync should alway

Re: md5 sum mismatches and mirror syncs

2006-08-11 Thread martin f krafft
also sprach Goswin von Brederlow <[EMAIL PROTECTED]> [2006.08.11.2326 +0100]: > The algorithm used is 2pass. First pass only mirrors pool while the > second pass mirrors the Release and Packages files. The time a mirror > is out of sync should always be limited to the time it takes to > download th

Re: md5 sum mismatches and mirror syncs

2006-08-11 Thread Goswin von Brederlow
martin f krafft <[EMAIL PROTECTED]> writes: > Failed to fetch > http://ftp.ie.debian.org/debian/dists/sid/main/binary-i386/Packages.gz > MD5Sum mismatch > > I am seeing a lot of this stuff lately, and I've been told it's due > to mirror syncs. As our archive grows bigger, the sync takes longer, >

Re: md5 sum mismatches and mirror syncs

2006-08-11 Thread Alexander Schmehl
Hi! * martin f krafft <[EMAIL PROTECTED]> [060811 13:22]: > Shouldn't we switch to using/advocating a smarter algorithm like > the one debmirror or anonftpsync use, which is to push new package > files to the archive, then synchronise indices, then delete obsolete > package files? We used someth

Re: md5 sum mismatches and mirror syncs

2006-08-11 Thread martin f krafft
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.08.11.1222 +0100]: > Shouldn't we switch to using/advocating a smarter algorithm like > the one debmirror or anonftpsync use, which is to push new package > files to the archive, then synchronise indices, then delete obsolete > package files? s

md5 sum mismatches and mirror syncs

2006-08-11 Thread martin f krafft
Failed to fetch http://ftp.ie.debian.org/debian/dists/sid/main/binary-i386/Packages.gz MD5Sum mismatch I am seeing a lot of this stuff lately, and I've been told it's due to mirror syncs. As our archive grows bigger, the sync takes longer, so this problem will happen more often in the future. I w