On Wed, 2006-09-27 at 14:05 +0100, stan wrote:
> Hi,
>
> Here is my output of the command
>
> COLUMNS=250 dpkg -l | grep mono
> ii libmono-corlib1.0-cil
> 1.1.13.8-1 Mono core
> ii libmono0
Version: 1.1.17.1-4
On Wed, Sep 27, 2006 at 02:56:30PM +0200, Mirco Bauer wrote:
> PS: This problem can't happen with the current Mono in unstable, because
> libmono0 is statically linked (as of mono 1.1.17.1-2)
That being the case, I believe the correct action is to close the bug with
version t
Hi all,
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).
This could happen by mixing Mono packages between testing and unstable,
still this situation shou
3 matches
Mail list logo