[MacPorts] #68192: py39-markupsafe-2.1.1_0.darwin_21.x86_64.tbz2 : Associated rmd160 file possibly corrupted

[MacPorts]

#68192: py39-markupsafe-2.1.1_0.darwin_21.x86_64.tbz2 : Associated rmd160 file
possibly corrupted
------------------------------+--------------------
  Reporter:  ulange-eso-org   |      Owner:  (none)
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.8.1
Resolution:                   |   Keywords:
      Port:  py39-markupsafe  |
------------------------------+--------------------

Comment (by ulange-eso-org):

 If both the signature file and binary archive for 2.1.1 version would have
 disappeared at the same time we would be fine. The ports command would
 fall back to building from source.

 If due to CDN this cannot be guaranteed then perhaps the ports command
 should detect that and fall back to build from source for the older
 version?

 We have our own Macports package building infrastructure:
 https://www.eso.org/sci/software/pipelines/installation/macports.html).

 We build hundreths of Macports packages across different MacOS X versions.
 The basis are VMware VM templates per supported OS version.

 At the time of template creation we bake a snapshot of the then current
 Macports definitions into them.

 Our VMware templates where refreshed on 08-SEP-2023. This was in reaction
 to a similar issue
 we had in August for package https://ports.macports.org/port/py39-yaml
 (older binary
 archive there but matching signature file already gone).

 A new VMware template with updated Macports then triggers a full rebuild
 of **all** packages on our
 side which can take several days to finish and is very straining on our
 infrastructure. In this
 case only a few hours after the rebuild finished we now have to restart
 from the beginning because
 py39-markupsafe 2.1.1 -> 2.1.3.

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