Bug 530170 - mono 2.2 tarball inconsistent with upstream
Summary: mono 2.2 tarball inconsistent with upstream
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-21 18:49 UTC by Christian Krause
Modified: 2009-11-10 17:54 UTC (History)
3 users (show)

Fixed In Version: 2.2-3.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-10 17:54:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christian Krause 2009-10-21 18:49:11 UTC
Description of problem:

During the last days I've searched a bug in f-spot where it sometimes
crashed with really weird backtraces like this (Fedora 10, mono 2.2):

ERROR:mini-exceptions.c:768:get_exception_catch_class: assertion failed:
(class->generic_class->container_class == method_container_class)
Stacktrace:

  at (wrapper managed-to-native)
System.Reflection.MonoMethod.InternalInvoke
(object,object[],System.Exception&) <0x00004>
  at (wrapper managed-to-native)
System.Reflection.MonoMethod.InternalInvoke
(object,object[],System.Exception&) <0xffffffff>2

I've found some upstream bug reports about the problem:
https://bugzilla.novell.com/show_bug.cgi?id=459285 and they claimed that
it got fixed in mono 2.2.

Currently, F10 uses mono-core-2.2-2.fc10.i386
I've checked out the corresponding tag (mono-2_2-2_fc10) and did a "make
local" which retrieved the tarball as it is in Fedora's packaging system:

md5sum mono-2.2.tar.bz2
a311545a0003f1a599297d57e4e27916  mono-2.2.tar.bz2

cat sources
a311545a0003f1a599297d57e4e27916  mono-2.2.tar.bz2

Then I've downloaded the official 2.2 tarball as it is linked on mono's
web page: http://ftp.novell.com/pub/mono/sources/mono/mono-2.2.tar.bz2

md5sum mono-2.2.tar.bz2
da147e24d14a73d8ad52775dd4a3d165  mono-2.2.tar.bz2

Version-Release number of selected component (if applicable):
mono-core-2.2-2.fc10.i386

A diff between the two tarballs indeed revealed that the mentioned bug was fixed.

I suggest to update F10's mono to the official 2.2 release.

Comment 1 Fedora Update System 2009-10-22 19:15:06 UTC
mono-2.2-3.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/mono-2.2-3.fc10

Comment 2 Fedora Update System 2009-10-27 06:40:15 UTC
mono-2.2-3.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update mono'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-10749

Comment 3 Fedora Update System 2009-11-10 17:54:33 UTC
mono-2.2-3.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.