[MacPorts] #65567: py38-locket @1.0.0: bad archive signature for 10.6

[MacPorts]

#65567: py38-locket @1.0.0: bad archive signature for 10.6
-----------------------------+---------------------
  Reporter:  jmroot          |      Owner:  admin@…
      Type:  defect          |     Status:  closed
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:  fixed           |   Keywords:
      Port:  py-locket       |
-----------------------------+---------------------
Changes (by ryandesign):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I'm not sure what happened but it could be the problem you anticipated in
 comment:ticket:62977:11; I still need to deploy your solution to the
 server. The
 [https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/101590
 previous]
 [https://build.macports.org/builders/ports-10.6_i386-builder/builds/67288
 builds] happened in April so their logs have already been deleted but the
 [https://ports.macports.org/port/py38-locket/builds/ ports web page] shows
 the two builds did start only ten seconds apart so they could have
 finished at the same time.

 I removed the files from the server and purged them on the CDN. I rebuilt
 [https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/116940
 py38-locket] and
 [https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/116944
 py38-dask] and
 [https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/116945
 py38-distributed]
 which depend on it.
 py38-partd which depends on it was already built and py38-sparse which
 depends on it cannot build because of its dependency py38-llvmlite.

-- 
Ticket URL: <https://trac.macports.org/ticket/65567#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS