When I download either of the two OS X bundles, from https://pre-release.racket-lang.org/installers/racket-7.1.0.900-i386-macosx.dmg and https://pre-release.racket-lang.org/installers/racket-7.1.0.900-x86_64-macosx.dmg
*by clicking on the respective links in Firefox* … I wind up with a .dmg that makes the OS unhappy. Specifically, trying to open them with open <name-of-file.dmg> results in a dialog stating "“racket-7.1.0.900-i386-macosx.dmg” is damaged and can’t be opened. You should move it to the Trash.” Bizarrely, downloading these files using curl 'https://pre-release.racket-lang.org/installers/racket-7.1.0.900-i386-macosx.dmg' > racket-7.dmg results in a file which opens fine, and for which moreover diff states that there is *no difference* from the dmg that can’t be opened. I know, that sounds nuts. I’ve tried using Chrome, and I get the same result. Furthermore, there are no dot files that appear to contain “resource-fork” kinds of files. … okay, some searching suggests that there are solutions, and that they involve using the ’spctl’ utility to manipulate the "SecAssessment system policy security” subsystem. I’m using OS X 10.14.1 Mojave. when I run ’spctl -a’ on *either* of the dmg files (the one that works, and the one that doesn’t work) I get this result: hardy:/tmp clements> spctl -a racket-7.1.0.900-i386-macosx.dmg racket-7.1.0.900-i386-macosx.dmg: CSSMERR_TP_CERT_EXPIRED hardy:/tmp clements> spctl -a racket-7.dmg racket-7.dmg: CSSMERR_TP_CERT_EXPIRED A bit of further experimentation suggests that ‘cp’ does not solve the problem, but the slightly-more-opaque cat bad-file.dmg > okay-file.dmg produces a file that I can open. This is the first time that I’ve had this particular problem; is this known, and will this be a problem with the release? John > On Jan 18, 2019, at 12:09 PM, Vincent St-Amour > <stamo...@eecs.northwestern.edu> wrote: > > Testing for the v7.2 release > (using the v7.1.0.900 release candidate build) > > Search for your name on the checklist page to find relevant items, either > reply when you finish an item (please indicate which item/s is/are done), > or check it off yourself on the checklist page. Also, if you have any > commits that should have been picked, make sure that the changes are in. > > Be sure to finish your testing by the 25th. Otherwise the release > will move on without your input. > > The checklist page is at: > https://github.com/racket/racket/wiki/Release-Checklist-7.2 > > Release candidates are at: > https://pre-release.racket-lang.org > > Please use these installers (or source bundles) -- don't test from > your own git clone (don't test the `master' branch by mistake!). > To get the tests, you can do this: > > cd ...racket-root... > ./bin/raco pkg install -i --auto main-distribution-test > > -- > You received this message because you are subscribed to the Google Groups > "Racket Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-dev+unsubscr...@googlegroups.com. > To post to this group, send email to racket-dev@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-dev/m2o98d9189.wl-stamourv%40eecs.northwestern.edu. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-dev@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/0de75fa2-7381-4472-9a4c-2da453df4782%40mtasv.net. For more options, visit https://groups.google.com/d/optout.
