Oolite Mac OS X – Trunk nightly builds

[Diziet Sma]

Ah.. that explains it..

[Getafix]

<Getafix turned black & red looking down at his feet, hiding his wings at his back...>

[pagroove]

Hello Getafix. Do I understand it correctly that to upload a mac trunk nightly you have to do all sorts of things because it doesn't build automatically now.?
Because from the Terrastorage link I get a build that is does not have an Oolite app.?
Just asking for better understanding.

[another_commander]

Moved pagroove's post from Oolite-PC nightlies thread to the Mac equivalent as it is directly Mac-nightly related.

[Getafix]

Hello Getafix. Do I understand it correctly that to upload a mac trunk nightly you have to do all sorts of things because it doesn't build automatically now.?

Yes that is the case. The Mac nightly was being built automatically on Ahruman's server but it stopped more than a month ago, March 9 at f9588d2.
Being a complete alien for the Mac world, I thought I had succeeded in replicating Ahruman's nightly builds.

Because from the Terrastorage link I get a build that is does not have an Oolite app.?
Just asking for better understanding.

Thanx for bring it up!
I will try to fix that today.

[Getafix]

@pagroove

I have uploaded an updated package with, from what it seems, the correct folder structure.
Let me know if further issues exist.

Cheers!

[pagroove]

Will try and download and look into it.
If any further issues arise I let you know.

[Getafix]

A different mishap for terrastorage will keep the server down for a couple of days more.
Read here.

[Getafix]

Terrastorage down due to extensive memory check. Read here.

EDIT (2016/05/14):
Test completed successfully.

[SMax]

oolite-trunk-1.85.0.160812-dev.mac cannot download OXP:

[10:20:34.379 [oxz.manager.error]: Error downloading file: Error Domain=NSURLErrorDomain Code=-1022 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." UserInfo={NSUnderlyingError=0x10c952ff0 {Error Domain=kCFErrorDomainCFNetwork Code=-1022 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." UserInfo={NSErrorFailingURLStringKey=http://addons.oolite.org/api/1.0/overview, NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection., NSErrorFailingURLKey=http://addons.oolite.org/api/1.0/overview}}, NSErrorFailingURLStringKey=http://addons.oolite.org/api/1.0/overview, NSErrorFailingURLKey=http://addons.oolite.org/api/1.0/overview, NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.}

Fix (edit info.plist in .app): http://stackoverflow.com/questions/3263 ... licy-requi

Current trunk (oolite-trunk-1.85.0.160914-dev.mac.zip) have broken archive.

[another_commander]

This has been a known issue (and proposed solution) for a long while. Check issue #170 for the related discussion.

Edit: ... and fix commited on revision eef1280.

[Getafix]

...Current trunk (oolite-trunk-1.85.0.160914-dev.mac.zip) have broken archive.

Missed that one...
Going to manual!

[Getafix]

Due to a bizarre mac nightly status page produced... the April Fool's day

an automatic redirect, to an alternative page, has been applied, as a precautionary measure.
The redirect should automatically be removed with the next fresh mac nightly build.

@JensAyton
It seems as if git has been configured to produce short hash having eight chars instead of the usual seven.
As a result, a string comparison condition, such as "31394c50" != "31394c5", triggered a new nightly build for mac.
Considering that for git the two hashes "31394c50" and "31394c5" actually refer to the same commit, the produced change-log was empty.

EDIT
Apologies for the big change-log. The last build, on the alternative build server, was performed some three months ago.