Indeed, doing:
 SMSqueakMap default loadUpdates.
appears to have fixed the problem.

After that, both
(Installer sm package: 'OCompletion'; versions) explore.
and
Installer sm install: 'OCompletion(head)'. then work in a fresh image.

Why was that necessary? Something seems to have changed in the Installer in trunk. I'm pretty sure it used to work.
Is it because something needs to be loaded into a fresh image, and I was attempting the two little doIts without ever yet opening the SqueakMap Catalog browser in the fresh image?
I've opened the SqueakMap Catalog browser many times in other images so the sm folder is there, and I've been running out of the same folder for awhile.
That is completely non-intuitive to me.

Ken

At 1:41 PM -0500 5/8/11, Chris Muller apparently wrote:
>Hmm, both of those work for me..
>
>It looks like maybe you need to update your SqueakMap from the net..?
>
>  SMSqueakMap default loadUpdates
>
>
>
>On Sat, May 7, 2011 at 8:46 PM, Ken G. Brown <kbrown at mac.com> wrote:
>> What is the latest way to script SqueakMap functionality in Sq 4.3 alpha 11393?
>>
>> For example we used to be able to do:
> > (Installer sm package: 'OCompletion'; versions) explore.
>> and
> > Installer sm install: 'OCompletion(head)'.
>>
>> See <http://installer.pbwiki.com/Installer>
>>
>> Now
>> Installer sm install: 'OCompletion(head)'.
>> fails with the following:
>>
>> UndefinedObject(Object)>>doesNotUnderstand: #releases
>> InstallerSqueakMap>>smReleasesForPackage:
>> InstallerSqueakMap>>smThing
>> [] in InstallerSqueakMap>>basicInstall
>> [] in BlockClosure>>valueSupplyingAnswers:
>>
>> Thx for any insight,
>> Ken G. Brown
>>
>>