binary packages missing

Joshua Root jmr at macports.org
Wed Mar 15 01:39:02 UTC 2017


Yes, it takes some time for the primary mirror to sync from the master 
server. At least some of the packages are there now.

- Josh

On 2017-3-15 11:48 , Mark Moll wrote:
> Hi,
>
> I finally created a workaround [1] that lets the build bot know the
> build is not stuck and after several hours the builds now terminate [2]!
> However, I still don’t see the newly built binaries appear
> in http://packages.macports.org/ompl/. Is this just a matter of mirrors
> having to catch up?
>
> Mark
>
> [1] https://github.com/macports/macports-ports/commit/f110e5ed3d7ad46f47ad64042f150bcfc07f8c17
> [2] https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/21544
>
>
>> On Mar 4, 2017, at 2:52 PM, Mojca Miklavec <mojca at macports.org
>> <mailto:mojca at macports.org>> wrote:
>>
>> On 4 March 2017 at 20:20, Mojca Miklavec wrote:
>>> On 4 March 2017 at 20:12, Mark Moll wrote:
>>>> Hi,
>>>>
>>>> For one of the packages I maintain, ompl, there are no recent binary
>>>> packages, despite the port being redistributable. I suspect it’s due
>>>> to a build time-out. The Python binding generation for the C++
>>>> library can take an hour or two during which very little output is
>>>> generated. Is it possible to force an increase in build time for a
>>>> particular build?
>>>
>>> Let's wait for a quiet moment at buildbots, rerun a build of that port
>>> and see what happens.
>>
>> https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/4029
>> https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/22307
>>
>> Mojca
>>
>



More information about the macports-dev mailing list