On 02/25/2014 12:27 PM, Pharo4Stef wrote: > probably that a changeset was created and it tried to reload a cs with the > same name.
Ah, so probably the changeset that had been created but not completed when the first update was interrupted, I'm guessing? That makes sense. Not crucial, of course, but it would be nice to avoid presenting the user with such vague errors -- either suppress the error or present enough information to understand it. Regards, -Martin > > On 25 Feb 2014, at 20:39, Martin McClure <[email protected]> wrote: > >> This is a bug report of sorts. >> >> I had a Pharo 3.0 image that was last updated about a month ago. I >> started a Software Update, and it was pulling in updates, when I needed >> to sleep my (Linux) laptop. When I re-opened the laptop, there was a >> walkback there, which I didn't find surprising since I'd interrupted the >> update's network connection by sleeping the laptop. It was some kind of >> "can't load" error; I don't remember the details. >> >> Anyway, I abandoned that, and chose "Software update" again. Almost >> immediately I got a little info box in the lower left that said "Sorry >> that name is already in use". This box stayed there until the update was >> complete. There was no other context given, so I have no idea what it >> was complaining about. >>
