Den 13.03.2011 10:49, skrev Stéphane Ducasse: > But we do not publish the changes anymore. > So you think that the packages got corrupted? > > Stef Doesn't matter.
Here's what can happen: - image1 is open, and thinks it's stream on the .changes is at end - image2 is the same image, but just imported lots of methods from an MC package, which you intend to include in an update. - Image1 quits, and writes the "I quit!" message to the place it thinks is the end of the .changes file. -Image2 files out an MC, which fetches the method definitions to write from the .changes file. Presto, you have a corrupt method definition in your package, and will get an error when trying to load it, telling it couldn't parse some nonsensical string that couldn't possibly be the methods true source. Cheers, Henry
