[PostGIS] #5736: latest releases md5 mismatch

[PostGIS]

#5736: latest releases md5 mismatch
-------------------------+--------------------------------------
  Reporter:  strk        |      Owner:  robe
      Type:  defect      |     Status:  reopened
  Priority:  medium      |  Milestone:  Website Management, Bots
 Component:  management  |    Version:  3.4.x
Resolution:              |   Keywords:
-------------------------+--------------------------------------
Comment (by robe):

 I think this was mostly my fault, when Paul was releasing, debbie failed
 to generate the tarballs, cause I had recently upgraded her which broke
 the webhook that instructs her to build the tarballs. After Paul had
 alerted me to the issue, I fixed but I think he was done with the tarball
 generations. But I'm not absolutely sure what happened in the 3.3.6 case.

 At anyrate assuming we have determined no rogue actors we should just
 assume the one on download.osgeo.org is right and fix the md5/etc on
 postgis.net.

 I was debating if we should just automate this whole process entirely.  I
 think the only reason we don't is, we want to test the tarballs before
 they hit download.osgeo.org cause at that point it's technically too late
 since  packagers (I'm know debian, possibly others) have bots watching
 that location waiting to pounce to release so once it's up there, we can't
 take it down since it would violate the release and require a new release.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5736#comment:10>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.