tag:gpgtools.tenderapp.com,2011-11-04:/discussions/problems/24976-how-to-build-yosemite-branchGPGTools: Discussion 2015-01-28T14:25:18Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-07-30T13:03:51Z2014-07-30T13:03:51ZHow to build Yosemite branch?<div><p>Hi Jonas,</p>
<p>we will update this branch the following days and after that it
should be possible to build it without problems.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-07-30T15:00:16Z2014-07-30T15:00:19ZHow to build Yosemite branch?<div><p>luke, awesome, thank you!</p></div>Jonastag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-08-06T13:32:55Z2014-08-06T13:33:03ZHow to build Yosemite branch?<div><p>Hi,</p>
<p>The problem continues when trying to compile GPGMail:</p>
<p>=== BUILD TARGET GPGMail_Updater OF PROJECT GPGMail_Updater WITH
CONFIGURATION Release ===</p>
<p>Check dependencies<br>
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.</p>
<p>** BUILD FAILED **</p>
<p>The following build commands failed:<br>
Check dependencies (1 failure) make: *** [GPGMail_Updater.app]
Error 65</p>
<p>I am using:<br>
$ git remote -v origin <a href=
"https://github.com/GPGTools/GPGMail.git">https://github.com/GPGTools/GPGMail.git</a>
(fetch)<br>
origin <a href=
"https://github.com/GPGTools/GPGMail.git">https://github.com/GPGTools/GPGMail.git</a>
(push)</p>
<p>Any ETA on a fix?</p>
<p>Thanks,<br>
Lynch</p></div>Lynchtag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-08-06T15:53:40Z2014-08-06T15:53:40ZHow to build Yosemite branch?<div><p>Hi Lynch,</p>
<p>sorry no ETAs. General policy. Soon is all I can give. I know -
not helpful. But we're at it.</p>
<p>cheers, steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-08-06T17:38:02Z2014-08-06T17:38:02ZHow to build Yosemite branch?<div><p>Hi Steve,</p>
<p>As long as someone knows and is tracking it as open, I¹m
good !<br>
I was glad it just wasn¹t only me seeing the problem :)</p>
<p>Thanks !<br>
-Lynch</p></div>Davis, Lynchtag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-08-06T17:39:57Z2014-08-06T17:39:57ZHow to build Yosemite branch?<div><p>Hi Lynch,</p>
<p>the build problem is easily fixed. Simply disable code signing
in xcode setting (will be disabled in the next push)</p>
<p>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.</p>
<p>We're working on it, but as Steve said, can't give an ETA at the
moment.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-09-27T05:45:53Z2014-09-27T05:45:55ZHow to build Yosemite branch?<div><p>No update on this? How do you disable code signing in Xcode?</p></div>Vinny Troiatag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-01T08:35:52Z2014-10-01T08:35:59ZHow to build Yosemite branch?<div><p>@Vinny Run the following one liner in the git repo root:</p>
<p><code>sed -i '' '/CODE_SIGN_IDENTITY = "Developer ID
Application";/d'
GPGMail_Updater.xcodeproj/project.pbxproj</code></p>
<p>... or adjust it in the Xcode GUI:</p>
<p><img src="http://up.frd.mn/xfEnl.png" alt=""></p>
<ol>
<li>Navigate => Shop project navigator<br></li>
<li>Select your project in the left sidebar<br></li>
<li>Click on the "General" tab<br></li>
<li>Select the "GPGMail_Updater" target<br></li>
<li>Choose "None" for the "Signing" configuration</li>
</ol></div>Jonas Friedmanntag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-20T18:20:34Z2014-10-20T18:20:34ZHow to build Yosemite branch?<div><p>Builds successfully under Yosemite but the resulting
GPGMail.mailbundle simply fails to load claiming incompatible:</p>
<p>Mail has disabled the following plug-ins:</p>
<pre>
<code>GPGMail</code>
</pre>
<p>Contact the makers of these plug-ins for versions that are
compatible with Mail 8.0.</p>
<p>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</p>
<p>Ah! GPGMail/UUID Patcher/uuid-patcher</p></div>Jerry Lottotag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T04:52:58Z2014-10-27T04:52:59ZHow to build Yosemite branch?<div><p>Thanks, Jerry Lotto... That little hint got GPGMail working
great on Yosemite! No problems here...</p>
<p>-Justin</p></div>Justintag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T07:15:19Z2014-10-27T07:15:21ZHow to build Yosemite branch?<div><p>@Justin even with the GPGMail bundle for Mail.app? Or everything
but that?</p></div>Jonas Friedmanntag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T07:20:56Z2014-10-27T07:20:56ZHow to build Yosemite branch?<div><p>Hi,</p>
<p>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.<br>
A public beta will be out soon.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T07:35:40Z2014-10-27T07:35:41ZHow to build Yosemite branch?<div><p>@Luke alright, will wait. :)</p></div>Jonas Friedmanntag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T16:10:48Z2014-10-27T16:10:50ZHow to build Yosemite branch?<div><p>Looking forward to that. Fee or donation fbm :)</p></div>johntag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-10-27T16:14:27Z2014-10-27T16:14:29ZHow to build Yosemite branch?<div><p>Apologies wrong topic post j</p></div>johntag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-11-13T06:00:27Z2014-11-21T08:59:11ZHow to build Yosemite branch?<div><p>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".<br>
Cf MacGPG2/source/gnupg2/common/keyserver.h<br>
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 ...<br>
Thanks<br>
<a href="http://defensetax.com/">Website</a></p></div>editor.buzzfeedtag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-12-07T14:07:26Z2014-12-07T14:07:27ZHow to build Yosemite branch?<div><p>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.</p></div>Ville Määttätag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222014-12-23T16:31:55Z2014-12-23T16:31:56ZHow to build Yosemite branch?<div><p>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.</p>
<p>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 <em>pseudo
open source</em> project where you release paid only binaries and
the source code is only released after months or <em>even
years</em> behind binaries.</p></div>Ville Määttätag:gpgtools.tenderapp.com,2011-11-04:Comment/339600222015-01-16T16:18:25Z2015-01-16T16:18:25ZHow to build Yosemite branch?<div><p>Hi all,</p>
<p>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.<br>
You can now find the most current code in the dev branch and from
now on it will be updated whenever we change it.</p></div>Luke Le