search

CompEvol / beast2

Bayesian Evolutionary Analysis by Sampling Trees
www.beast2.org
GNU Lesser General Public License v2.1
241 stars 84 forks source link

Deployment error: "corrupted DMG" message in OS X Mavericks after download #177

Closed alexeid closed 9 years ago

alexeid commented 10 years ago

This is a deployment problem with the latest Mac OS X operating system:

From Tracy Heath:

"There were some initial issues getting started because some people who had downloaded the Mac version got some message when they clicked on anything in the BEAST2 folder saying it came from a "corrupted DMG". It seemed that this was a Mavericks problem (though not for all Mavericks users)."

This problem arises because we haven't registered as Apple developers and the latest OS X operating system is militant about such things (although the error message could be clearer!). I will register as an Apple Developer so we can create certificates for future releases.

rbouckaert commented 10 years ago

This looks like a duplicate of issue #129.

On Mon, 2014-08-04 at 14:11 -0700, Alexei Drummond wrote:

This is a deployment problem with the latest Mac OS X operating system:

From Tracy Heath:

"There were some initial issues getting started because some people who had downloaded the Mac version got some message when they clicked on anything in the BEAST2 folder saying it came from a "corrupted DMG". It seemed that this was a Mavericks problem (though not for all Mavericks users)."

This problem arises because we haven't registered as Apple developers and the latest OS X operating system is militant about such things (although the error message could be clearer!). I will register as an Apple Developer so we can create certificates for future releases.

— Reply to this email directly or view it on GitHub.

alexeid commented 10 years ago

Issue #129 looks like something different. Something to do with Java 6 versus Java 7 rather than the DMG packaging.

On 5/08/2014, at 9:30 am, rbouckaert notifications@github.com wrote:

This looks like a duplicate of issue #129.

On Mon, 2014-08-04 at 14:11 -0700, Alexei Drummond wrote:

This is a deployment problem with the latest Mac OS X operating system:

From Tracy Heath:

"There were some initial issues getting started because some people who had downloaded the Mac version got some message when they clicked on anything in the BEAST2 folder saying it came from a "corrupted DMG". It seemed that this was a Mavericks problem (though not for all Mavericks users)."

This problem arises because we haven't registered as Apple developers and the latest OS X operating system is militant about such things (although the error message could be clearer!). I will register as an Apple Developer so we can create certificates for future releases.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

tgvaughan commented 10 years ago

How could "corrupted DMG" be a certificate problem? Especially considering its non-deterministic nature. To me it sounds more like a problem with the downloading process (which is giving me flashbacks to problems I had with my 14.4kb modem in the early 90s).

rbouckaert commented 10 years ago

Max OS only opens apps downloaded from the internet if they are certified by Apple. Currently, our packages are not certified. With default settings, the misleading error message is displayed to users (it is an attempt to fight malware).

From: Tim Vaughan [notifications@github.com] Sent: Tuesday, 5 August 2014 9:41 a.m. To: CompEvol/beast2 Cc: rbouckaert Subject: Re: [beast2] Deployment error: "corrupted DMG" message in OS X Mavericks after download (#177)

How could "corrupted DMG" be a certificate problem? Especially considering its non-deterministic nature. To me it sounds more like a problem with the downloading process (which is giving me flashbacks to problems I had with my 14.4kb modem in the early 90s).

— Reply to this email directly or view it on GitHubhttps://github.com/CompEvol/beast2/issues/177#issuecomment-51121733.

tgvaughan commented 10 years ago

I understand this, and have found my way around this GateKeeper-induced craziness before. (E.g. the MASTER stand-alone was causing similar issues.) The "corrupted DMG" message is new to me though.

rbouckaert commented 10 years ago

Further along in the discussion the certification process is discussed. I suggest we close either #129 or this one then.

On Mon, 2014-08-04 at 14:35 -0700, Alexei Drummond wrote:

Issue #129 looks like something different. Something to do with Java 6 versus Java 7 rather than the DMG packaging.

On 5/08/2014, at 9:30 am, rbouckaert notifications@github.com wrote:

This looks like a duplicate of issue #129.

On Mon, 2014-08-04 at 14:11 -0700, Alexei Drummond wrote:

This is a deployment problem with the latest Mac OS X operating system:

From Tracy Heath:

"There were some initial issues getting started because some people who had downloaded the Mac version got some message when they clicked on anything in the BEAST2 folder saying it came from a "corrupted DMG". It seemed that this was a Mavericks problem (though not for all Mavericks users)."

This problem arises because we haven't registered as Apple developers and the latest OS X operating system is militant about such things (although the error message could be clearer!). I will register as an Apple Developer so we can create certificates for future releases.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

alexeid commented 10 years ago

The DMG problem has nothing to do with Java versions as far as I know.

129 is about Java 6 versus Java 7 in the main text, not about corrupted DMGs.

If it isn't totally clear that two issues are identical then both should be left open until they are fixed.

On 5/08/2014, at 9:50 am, rbouckaert notifications@github.com wrote:

Further along in the discussion the certification process is discussed. I suggest we close either #129 or this one then.

On Mon, 2014-08-04 at 14:35 -0700, Alexei Drummond wrote:

Issue #129 looks like something different. Something to do with Java 6 versus Java 7 rather than the DMG packaging.

On 5/08/2014, at 9:30 am, rbouckaert notifications@github.com wrote:

This looks like a duplicate of issue #129.

On Mon, 2014-08-04 at 14:11 -0700, Alexei Drummond wrote:

This is a deployment problem with the latest Mac OS X operating system:

From Tracy Heath:

"There were some initial issues getting started because some people who had downloaded the Mac version got some message when they clicked on anything in the BEAST2 folder saying it came from a "corrupted DMG". It seemed that this was a Mavericks problem (though not for all Mavericks users)."

This problem arises because we haven't registered as Apple developers and the latest OS X operating system is militant about such things (although the error message could be clearer!). I will register as an Apple Developer so we can create certificates for future releases.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

walterxie commented 10 years ago

But according http://stackoverflow.com/questions/8929124/do-dmg-files-need-to-be-signed, it seems no need to sign a dmg.

alexeid commented 10 years ago

Have you replicated the error? I don't see what that stackoverflow question has to do with this problem. The problem is that we get a corrupted DMG message on some (but not all) OS X Mavericks machines.

On 26/08/2014, at 11:57 am, Walter notifications@github.com wrote:

But according http://stackoverflow.com/questions/8929124/do-dmg-files-need-to-be-signed, it seems no need to sign a dmg.

— Reply to this email directly or view it on GitHub.