Bug 132436

Summary: best from supplementary fails to start
Product: [openSUSE] SUSE LINUX 10.0 Reporter: James Ogley <riggwelter>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description James Ogley 2005-11-04 22:46:56 UTC
Using the latest beagle & gecko-sharp packages from supplementary/GNOME, best fails to start with the following error:

ogley@riggwelter:~> best

** (/usr/lib/beagle/Best.exe:18144): WARNING **: The following assembly referenced from /usr/lib/mono/gac/gecko-sharp/2.0.0.0__ccf7d78a55e9f021/gecko-sharp.dll could not be loaded:
     Assembly:   gtk-sharp    (assemblyref_index=2)
     Version:    2.0.0.0
     Public Key: 35e10195dab3c99f
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gac/gecko-sharp/2.0.0.0__ccf7d78a55e9f021).


** (/usr/lib/beagle/Best.exe:18144): WARNING **: The class Gtk.Bin could not be loaded, used in /usr/lib/mono/gac/gecko-sharp/2.0.0.0__ccf7d78a55e9f021/gecko-sharp.dll (token 0x0100000e)

** ERROR **: file class.c: line 2119 (mono_class_setup_parent): should not be reached
aborting...
Aborted
Comment 1 Stanislav Brabec 2005-11-07 12:31:00 UTC
Please upgrade gecko-sharp-2_0 to gecko-sharp2 and gtksourceview-sharp-2_0 to gtksourceview-sharp2.

I am not yet sure, how to provide this update automatically. Maybe add proper Requires or Conflicts.
Comment 2 Stanislav Brabec 2005-11-07 13:10:19 UTC
This should be enough:

beagle:
- Renamed gecko-sharp-2_0 to gecko-sharp2 in Requires (#132436).

monodevelop:
- Renamed rename *-sharp-2_0 to *-sharp2 in Requires (#132436).
Comment 3 James Ogley 2005-11-07 16:11:55 UTC
Cool, yes that sorts it.

However, I just noticed that beagled also fails to start with a similar error related to glib-sharp (from gtk-sharp2)

ogley@riggwelter:~> beagled
INFO: Starting Beagle Daemon (version 0.1.1)
DEBUG: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg
DEBUG: Starting main loop
DEBUG: Starting messaging server
DEBUG: Starting QueryDriver

** (beagled:22891): WARNING **: The following assembly referenced from /usr/lib/mono/gac/evolution-sharp/2.0.0.0__457eed85bd9370df/evolution-sharp.dll could not be loaded:
     Assembly:   glib-sharp    (assemblyref_index=1)
     Version:    2.0.0.0
     Public Key: 35e10195dab3c99f
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gac/evolution-sharp/2.0.0.0__457eed85bd9370df).


** (beagled:22891): WARNING **: The class GLib.Object could not be loaded, used in /usr/lib/mono/gac/evolution-sharp/2.0.0.0__457eed85bd9370df/evolution-sharp.dll (token 0x01000012)

** ERROR **: file class.c: line 2119 (mono_class_setup_parent): should not be reached
aborting...
Aborted
Comment 4 Stanislav Brabec 2005-11-07 17:41:46 UTC
Last week I updated, too. Update of gtk-sharp2 (and other packages from complains) did help.

The problem is following:
- Mono RPM packages in 10.0 don't yet generate proper Provides/Requires.
- Mono GAC requires exact version hash.

It means, that if update of other packages is required, RPM does not ask for them. It is already fixed for 10.1.

Things are complicated by the fact, that supplementary scripts provide update only in case of new changelog entry or changed requirements (otherwise it will generate 700MB update after each glib change). In particular case it can fail for mono packages. It it does and update to actual version in supplementary does not help, feel free to ping me via mail and I will do forced update. These problems will disappear in SuSE Linux 10.1.