As a possible workaround, an offending package might load on a Mac or Linux system. Some time back, I encountered a package (an older version of RIO) that was broken on Windows, but I was able to install it on Linux, fix the Windows code there, and then it worked. It's better to fix the real problem, but it can nice to be able to continue working. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2@btinternet.com] Sent: Monday, December 06, 2010 11:02 AM To: Pharo Development Subject: [Pharo-project] Bad characters in update package names Seems didn't get sent... Regards, Gary ----- Original Message ----- From: Gary Chambers<mailto:gazzaguru2@btinternet.com> To: Pharo Development<mailto:pharo-project@lists.gforge.inria.fr> Sent: Friday, December 03, 2010 4:02 PM Subject: Bad characters in update package names It seems that having $: in the package name for certain updates is causing the save to local package cache to error on Windows (unsurprisingly). Perhaps worth having a sanity check before the package name is accepted since it eventually gets to the filesystem. Regards, Gary