Hi Lesile,
I provided a patch to fix the problem occured in the 0.9.1->1.02a
upgrade process.
The issue occurs when doing migrate with SBCL. The deserialization
exception is reported.
The latest email chain includes more details.
If the failure symtom is similar, you may want to use the latest codes
and have another try.
cheers
Quan
2009/2/24 Leslie P. Polzer <s...@viridian-project.de>
>
> I've upgraded from
>
> Sun Nov 30 17:33:14 CET 2008 pol...@stardawn.org
> * Fix DROP-INSTANCES called with an atom. Add tests for it.
>
> to 1.0a2 and experienced a deserialization error in one place.
>
> Has something in the serializer changed in an incompatible manner?
>
> Leslie
>
> --
> LinkedIn Profile: http://www.linkedin.com/in/polzer
> Xing Profile: https://www.xing.com/profile/LeslieP_Polzer
> Blog: http://blog.viridian-project.de/
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel@common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
