Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 252426

Summary: merging dev-libs/gmime-2.2.23 fails with unkown reasons
Product: Gentoo Linux Reporter: flukebox <gentoomail.dell>
Component: [OLD] DevelopmentAssignee: Net-Mail Packages <net-mail+disabled>
Status: RESOLVED DUPLICATE    
Severity: normal CC: gnome, pchrist
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: complete build log
emerge --info

Description flukebox 2008-12-24 22:26:05 UTC
merging dev-libs/gmime-2.2.23 fails with unkown reasons 

Reproducible: Always

Steps to Reproduce:
1. emerge -av1 =dev-libs/gmime-2.2.23
2.
3.

Actual Results:  
merge fails !

Expected Results:  
successful merge !
Comment 1 flukebox 2008-12-24 22:27:27 UTC
Created attachment 176329 [details]
complete build log 

build log for same.
Comment 2 flukebox 2008-12-24 22:29:45 UTC
Created attachment 176330 [details]
emerge --info

my emerge info
Comment 3 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2008-12-24 23:48:55 UTC
There are some errors but they are scattered over the log file because of your MAKEOPTS.
Please re-run your emerge but this time with 
  MAKEOPTS="-j1"
Then attach the resulting build log please.
Comment 4 Rafał Mużyło 2008-12-25 01:53:46 UTC
Looks like this is the first problem:
/usr/bin/gacutil /i gmime-sharp.dll /f /package gmime-sharp /root /var/tmp/portage/dev-libs/gmime-2.2.23/image//usr/lib
 /bin/install -c -m 644 'gmime-api.xml' '/var/tmp/portage/dev-libs/gmime-2.2.23/image//usr/share/gapi-2.0/gmime-api.xml'
 /bin/install -c -m 644 'gmime-sharp.pc' '/var/tmp/portage/dev-libs/gmime-2.2.23/image//usr/lib/pkgconfig/gmime-sharp.pc'
Failure adding assembly gmime-sharp.dll to the cache: Strong name cannot be verified for delay-signed assembly

Not that I know anything about mono, but I think I saw this error in a few bugs.
Comment 5 Gilles Dartiguelongue (RETIRED) gentoo-dev 2008-12-25 11:22:01 UTC

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