How to build Yosemite branch?
When i try to compile my own Yosemite version of GPG Tools: https://github.com/GPGTools/GPGMail/tree/yosemite i get the following error:
Check dependencies
Code Sign error: No code signing identites found: No valid signing
identities (i.e. certificate and private key pair) matching the
team ID “PKV8ZPD836” were found.
** BUILD FAILED **
The following build commands failed:
Check dependencies (1 failure)
make: *** [GPGMail_Updater.app] Error 65
Who can help me to compile my own version without error?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Luke Le on 30 Jul, 2014 01:03 PM
Hi Jonas,
we will update this branch the following days and after that it should be possible to build it without problems.
2 Posted by Jonas on 30 Jul, 2014 03:00 PM
luke, awesome, thank you!
3 Posted by Lynch on 06 Aug, 2014 01:32 PM
Hi,
The problem continues when trying to compile GPGMail:
=== BUILD TARGET GPGMail_Updater OF PROJECT GPGMail_Updater WITH CONFIGURATION Release ===
Check dependencies
Code Sign error: No code signing identites found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “PKV8ZPD836” were found.
** BUILD FAILED **
The following build commands failed:
Check dependencies (1 failure) make: *** [GPGMail_Updater.app] Error 65
I am using:
$ git remote -v origin https://github.com/GPGTools/GPGMail.git (fetch)
origin https://github.com/GPGTools/GPGMail.git (push)
Any ETA on a fix?
Thanks,
Lynch
Support Staff 4 Posted by Steve on 06 Aug, 2014 03:53 PM
Hi Lynch,
sorry no ETAs. General policy. Soon is all I can give. I know - not helpful. But we're at it.
cheers, steve
5 Posted by Davis, Lynch on 06 Aug, 2014 05:38 PM
Hi Steve,
As long as someone knows and is tracking it as open, I¹m good !
I was glad it just wasn¹t only me seeing the problem :)
Thanks !
-Lynch
Support Staff 6 Posted by Luke Le on 06 Aug, 2014 05:39 PM
Hi Lynch,
the build problem is easily fixed. Simply disable code signing in xcode setting (will be disabled in the next push)
Unfortunately, while the current version in yosemite branch didn't crash in DP2, it crashes immediately in DP5, since A LOT of stuff has changed again.
We're working on it, but as Steve said, can't give an ETA at the moment.
7 Posted by Vinny Troia on 27 Sep, 2014 05:45 AM
No update on this? How do you disable code signing in Xcode?
8 Posted by Jonas Friedmann on 01 Oct, 2014 08:35 AM
@Vinny Run the following one liner in the git repo root:
sed -i '' '/CODE_SIGN_IDENTITY = "Developer ID Application";/d' GPGMail_Updater.xcodeproj/project.pbxproj... or adjust it in the Xcode GUI:
9 Posted by Jerry Lotto on 20 Oct, 2014 06:20 PM
Builds successfully under Yosemite but the resulting GPGMail.mailbundle simply fails to load claiming incompatible:
Mail has disabled the following plug-ins:
Contact the makers of these plug-ins for versions that are compatible with Mail 8.0.
10/20/14 2:04:45.378 PM Mail[57760]: Plugin compatibility check failed for GPGMail.mailbundle. The plugin's Info.plist must have a SupportedPluginCompatibilityUUIDs key whose value is an array of strings that contains the compatibility UUIDs for the supported versions of Mail. The compatibility UUID value is found in the PluginCompatibilityUUID key of Mail's Info.plist
Ah! GPGMail/UUID Patcher/uuid-patcher
10 Posted by Justin on 27 Oct, 2014 04:52 AM
Thanks, Jerry Lotto... That little hint got GPGMail working great on Yosemite! No problems here...
-Justin
11 Posted by Jonas Friedmann on 27 Oct, 2014 07:15 AM
@Justin even with the GPGMail bundle for Mail.app? Or everything but that?
Support Staff 12 Posted by Luke Le on 27 Oct, 2014 07:20 AM
Hi,
please don't use the Yosemite branch code as it is just yet. There's a lot of stuff missing and still broken. The worst thing that could happen is, that messages which are sent in plain text, even though you think they will be encrypted.
A public beta will be out soon.
13 Posted by Jonas Friedmann on 27 Oct, 2014 07:35 AM
@Luke alright, will wait. :)
14 Posted by john on 27 Oct, 2014 04:10 PM
Looking forward to that. Fee or donation fbm :)
15 Posted by john on 27 Oct, 2014 04:14 PM
Apologies wrong topic post j
16 Posted by editor.buzzfeed on 13 Nov, 2014 06:00 AM
if i'm not mistaken, the error message is selected based on the return value of the helper which on most case i think called gpg2keys_hkp. But the return value is almost alway 1 which is "INTERNAL_ERROR".
Cf MacGPG2/source/gnupg2/common/keyserver.h
I've try by denying acces with my firewall and it returned 1, even if "KEYSERVER_UNREACHABLE=9" is defined. So i'm not sure how to make a message which change depending on the reason why it doesn't worked ...
Thanks
Website
17 Posted by Ville Määttä on 07 Dec, 2014 02:07 PM
Where in fact is the source code for Beta / 2.5 / Yosemite branch. The one that build and is compatible with release version Yosemite Mail 8.1 and soon 8.2. The 'yosemite' branch in GitHub does not seem to be it. And there commit at the HEAD of the branch in fact breaks the build and the previous commit is from July.
18 Posted by Ville Määttä on 23 Dec, 2014 04:31 PM
Anyone? The source code is clearly not being provided and development is happening somewhere other that in the stated repository. Specifically I am looking for the source of Yosemite branch of GPGMail but I am concerned about the project in general.
I do appreciate the need to make support of this project paid only. I very much understand and hope it makes the project stand on a better foundation. I most certainly hope though that you are not trying to turn this into some sort of a delayed-release pseudo open source project where you release paid only binaries and the source code is only released after months or even years behind binaries.
Support Staff 19 Posted by Luke Le on 16 Jan, 2015 04:18 PM
Hi all,
we've very sorry it took so long to push the most current code. We wanted to cleanup a lot of the code, since the yosemite branch was kind of a hack for the longest time.
You can now find the most current code in the dev branch and from now on it will be updated whenever we change it.
Steve closed this discussion on 28 Jan, 2015 02:25 PM.