After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601209 - install fail: "strong name cannot be verified..."
install fail: "strong name cannot be verified..."
Status: RESOLVED DUPLICATE of bug 556704
Product: gmime
Classification: Other
Component: general
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: Jeffrey Stedfast
Jeffrey Stedfast
Depends on:
Blocks:
 
 
Reported: 2009-11-09 03:12 UTC by Frank Solensky
Modified: 2009-11-09 03:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frank Solensky 2009-11-09 03:12:19 UTC 
Attempting jhbuild on current s/w.  Things are going fine until the gmime-2-2 module when the install fails in the following manner:

make[3]: Entering directory `/opt/gnome2/usr/src/gmime/mono'
/opt/gnome2/bin/gacutil /i gmime-sharp.dll /f /package gmime-sharp /gacdir /opt/gnome2/lib
Failure adding assembly gmime-sharp.dll to the cache: Strong name cannot be verified for delay-signed assembly
make[3]: *** [install-data-hook] Error 1
make[3]: Leaving directory `/opt/gnome2/usr/src/gmime/mono'

I came across a page that described the same issue (http://blog.flameeyes.eu/2009/01/13/for-a-parallel-world-case-study-n-6-parallel-install-versus-install-hooks) and suggests editing mono/Makefile.am so that the rule for install-data-local is renamed as install-data-hook.  After doing "make distclean", wiping out the Makefile.in file, rerunning autogen.sh, verifying that the resulting mono/Makefile was changed in the manner suggested, then running "make" and "make install", I ran into the same error message.
Comment 1 Frank Solensky 2009-11-09 03:23:56 UTC 
Nuts... just found 556704 which at first glance is the same problem.

After adding "skip = [ 'gmime-2-2' ]" to my .jhbuildrc I started another build; found that rather than attempting to build 233 modules it's going to attempt to build 232.  Is it possible that the reference to gmime-2-2 just doesn't need to be there anymore?

*** This bug has been marked as a duplicate of bug 556704 ***