I changed the way that the buildbot generates the OSX binaries, so that 
would explain it. Not having a Mac, I can't test the dmgs. This is what the 
buildbot does to produce the binaries:

    def sage_bdist_osx(self, build_factory, env):
        from buildbot.steps.shell import ShellCommand, 
SetPropertyFromCommand
        from buildbot.steps.transfer import FileUpload
        from buildbot.process.properties import Interpolate
        env['SAGE_APP_DMG'] = 'yes'
        env['SAGE_APP_BUNDLE'] = None
        build_factory.addStep(ShellCommand(
            command=['./sage', '-bdist'],
            env=env,
            description=['packaging dmg'],
            descriptionDone=['packaged dmg'],
            usePTY=True))
        build_factory.addStep(SetPropertyFromCommand(
            command='cd dist && ls -1 sage-*.dmg | sed s/\.dmg//', 
            property='bdist_file'))
        src = Interpolate('dist/%(prop:bdist_file)s.dmg')
        osversion = self._osversion.replace(' ', '_')
        dst_dmg = Interpolate('~/binaries/%(prop:bdist_file)s-' + osversion 
+ '.dmg')
        dst_app = Interpolate('~/binaries/%(prop:bdist_file)s-' + osversion 
+ '-app.dmg')
        build_factory.addStep(FileUpload(
            slavesrc=src, masterdest=dst_dmg))
        env['SAGE_APP_BUNDLE'] = 'yes'
        build_factory.addStep(ShellCommand(
            command=['./sage', '-bdist'],
            env=env,
            description=['packaging app'],
            descriptionDone=['packaged app'],
            usePTY=True))
        build_factory.addStep(FileUpload(
            slavesrc=src, masterdest=dst_app))




On Friday, January 17, 2014 10:50:28 AM UTC-5, Hayden Stainsby wrote:
>
> I'm not sure if anyone else has noticed this, but the "normal" MacOS 
> binary DMG contains the Sage.app bundle, rather than a straight sage 
> folder. The "-app" binary DMG also contains the Sage.app bundle. I did 
> check a couple of different mirrors (both in Europe), but Harald assured me 
> that the files are the same across mirrors (I haven't checked the original 
> files at the link below yet due to bandwidth issues).
>
> ,ther than that, the Sage.app bundle itself seems to be working fine. I've 
> never used it before myself, but it executes and doesn't seem to generate 
> any obvious errors on first use.
>
> Hayden
>
> On Thursday, 19 December 2013 12:38:10 UTC+1, Volker Braun wrote:
>>
>> Binary tarballs are now available at
>>
>> http://boxen.math.washington.edu/home/buildbot/binaries/
>>
>> The buildbot has undergone some serious reconfiguration in the switch to 
>> git, so it is possible that there are regressions. In particular, I don't 
>> have a mac to test the dmg's on. Feel free to try them out and post your 
>> experiences.
>>
>> Note that the directory layout changed, the 5.13 binary tarballs are in 
>> the sage subfolder.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to