Hi, I already fixed this bug, on cocoa vm's (5 minutes ago). I hope igor will check my changes and propagate them to unix/windows (it was, at least, present too on unix machines, but as I don't know which uuid library is correct for unix machines, I can not fix it myself)
Philippe... I know it is lame... but if you want to recover your packages, all I can think is to re-save packages with new vm (or with primitive call removed) as I previous suggested. I'm sorry for the mess, I hope this is not drawing back the good energy all of us are putting in our projects. cheers, Esteban El 20/07/2011, a las 11:20a.m., Igor Stasenko escribió: > On 20 July 2011 14:29, Esteban Lorenzano <[email protected]> wrote: >> Hi Philippe, >> There is no need to be so dramatic :) >> it was not a *known* issue. >> Better: *I* knew it, because I found same problem last week. I thought it >> was a problem with my virtual machines, which is still not production >> released, just collecting issues -like this-, that's why I didn't ran to >> solve it. When you described the problem, I thought it was same bug... and >> that's why I started think it was a general UUID plugin bug... >> we are collecting this problems, and solving them as soon as we can... >> >> please, be a little patient, your feedback is very important to us. >> > > Esteban, i think this bug is introduced after merging the plugin > codebase by Andreas (cog-->squeak trunk) > >> cheers, >> Esteban >> >> El 20/07/2011, a las 3:36a.m., Philippe Marschall escribió: >> >>> On 07/19/2011 09:41 PM, Esteban Lorenzano wrote: >>>> yes... there is a problem in latest vm's and UUID generation (I don't know >>>> if it is present at any vm or just mines, but well...). For the moment, >>>> faster solution is by deactivating uuid primitive, at: >>>> >>>> UUID>>#primMakeUUID >>>> <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> >>>> UUIDGenerator default generateBytes: self forVersion: 4. >>>> >>>> just comment the primitive call. >>> >>> Guys, srsly? Is this some kind of practical joke? You have been shipping >>> with a known bug that has a trivial fix and eats peoples code? You are >>> wondering why nobody takes you seriously and you don't have more users? >>> You teach software engineering? >>> >>> This is exactly the kind of shit that makes me want to never again use >>> Pharo in production. This is the reason why I don't recommend Pharo to >>> other people. >>> >>> Cheers >>> Philippe >>> >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >
