On Wed, Sep 27, 2006 at 02:56:30PM +0200, Mirco Bauer wrote: > I have a possible cause of this bug you experienced. > The virtual machine (mono-jit), the mono runtime libraries (libmono0) > and the corlib (libmono-corlib*-cil) are not in sync (version wise).
Right, I suspected something like this. > This could happen by mixing Mono packages between testing and unstable, > still this situation should not be possible with strict enough > dependencies. > > mono-jit and libmono-corlib*-cil are forced to be in sync, but not > libmono0. > > To be sure that this is the problem, please reply to this email with > giving me the output of: > COLUMNS=250 dpkg -l | grep mono > > Please reply ASAP, this is a show stopper for Mono in testing. Problem--having pulled mono-jit from unstable the bug has gone away. However I still have my dpkg log which I believe will reveal the versions of the packages that were installed prior to upgrading. I'll go through it tomorrow and see what versions I can pull up. -- Sam Morris http://robots.org.uk/ PGP key id 5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
