Nice find -- you're right, this is a critcal bug. We'll fix this for 2.6.15. The workaround for now is to remove the empty file from your old version and just leave files with more than 0 bytes.
I know enough people have asked you this question already - but is there any news on the 2.6.15 release 😀 ?
Soon -- believe it or not, we want to get it out as fast as you want it out.