Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 451139

Summary:	Unable to sign EPP Mac OSX packages
Product:	[Technology] EPP	Reporter:	Markus Knauer <mknauer>
Component:	Packager	Assignee:	Markus Knauer <mknauer>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	david_williams, jonah, mknauer, stepper, webmaster
Version:	4.5.0
Target Milestone:	4.5.0M7
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	465242

Description Markus Knauer

2014-11-12 08:06:46 EST

First of all, I'm not sure what the real problem is. I had to find out that since a few days (or maybe a two weeks) we are not able to build the EPP packages because the signing service for Mac OSX doesn't work.

As an example see build https://hudson.eclipse.org/packaging/job/mars.epp-tycho-build/70/console:

[ERROR] Error 500: Codesign tool stage2 exit status: 133.
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-macsigner-plugin:1.0.5:sign (sign) on project epp.package.testing: Signer replied HTTP/1.1 500 Codesign tool stage2 exit status: 133. Signer replied HTTP/1.1 500 Codesign tool stage2 exit status: 133.

As a quick fix I disabled signing in the EPP builds today.

Possible reasons that come to my mind:

- Something has changed on the server (e.g. bug 447410) that leads to this error.
- Maybe the CBI / signing module need to be updated (currently <cbi.version>1.0.5</cbi.version>)
- Or our HIPP instance has problems reaching the signing server
- ...?

In any case this is really important in order to build the Mars M3 packages this week.

Comment 1 David Williams

2014-11-12 08:17:01 EST

Sorry, Markus ... I should have announced this issue (and, will after this), but see 

Bug 445050 - Need to update "Mac signing service"
and 
Bug 446390 - Change location of eclipse.ini (for Max OS X signing)

In short, I don't think we can sign Mac executables for M3. 

I know in Platform's case, we disabled that signing part of POM that materializes the products.

Comment 2 Markus Knauer

2014-11-12 08:39:10 EST

(In reply to David Williams from comment #1)
> In short, I don't think we can sign Mac executables for M3. 
> 
> I know in Platform's case, we disabled that signing part of POM that
> materializes the products.

Okay, this sound like I should do the same, i.e. do not use the mac osx signing service in the build.

In the end I'll make it configurable what parts (jar files, windows executable, mac osx) of the build should be signed. That way we can easily configure this for a build and disable it for the parts where we are facing problems (like we do so many times for mac osx).

Comment 3 Markus Knauer

2014-11-12 15:28:39 EST

Moving to EPP.

Comment 4 David Williams

2015-04-24 15:28:49 EDT

Just to be sure ... you know this is possible now, right? 

Would be good if you tried signing, if you haven't yet, just to be sure all is well.

Comment 5 Markus Knauer

2015-05-07 17:34:24 EDT

Thanks for the additional "ping" - I would have missed that one.

I had enabled the eclipse-sign-mac profile in the build, and by looking into the log files I would say that signing is working again and doesn't log any errors. But I'm unable to test the results - we'll see what the package maintainers are saying after testing the packages. Let's see what their feedback is, and then I can think about the next steps... either opening new bugs, working on the build configuration, or closing this bug.

Comment 6 Jonah Graham

2021-05-07 10:21:31 EDT

The EPP project does not have its "own" Packager anymore. EPP uses other technologies, such as Eclipse Tycho, Maven and Eclipse PDE. Therefore any remaining bugs are now being closed as WONTFIX. If this bug is still relevant, please make a comment and we'll move it to the correct project/component for further investigation.

This change was made as part of a bulk change.