On Mon, Jan 26, 2009 at 5:37 PM, H.J. Lu <hjl.to...@gmail.com> wrote: > On Mon, Jan 26, 2009 at 7:49 AM, Richard Guenther > <richard.guent...@gmail.com> wrote: >> On Mon, Jan 26, 2009 at 4:23 PM, Andrew Walrond <and...@walrond.org> wrote: >>> I've tried two mirrors with the same results: >>> >>> $ cat md5.sum | grep gcc-4.3.3.tar.bz2 >>> >>> d3338b75fa6f83be08908b1eed56d439 gcc-4.3.3.tar.bz2 >>> >>> $ md5sum gcc-4.3.3.tar.bz2 >>> cc3c5565fdb9ab87a05ddb106ba0bd1f gcc-4.3.3.tar.bz2 >>> >>> Can someone confirm/fix this? >> >> Appearantly the md5.sum file is autogenerated somehow and >> this happened before the upload was complete. >> > > One way to solve it to have a staging area on the same filesystem. > After upload to staging area is done, you do a "mv staging dest".
Sure. The gcc_release script does not do that though. The file is owned by root, so I cannot delete it either ... Richard.
