[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 strk):

 > I think the other way that this issue happens is that debbie builds a
 > release tar ball twice.

 It would be interesting to understand WHY doing so would result in
 different tarballs. Is it two different commits, you're talking about ?

 > Can you think of an easy way to prevent tagged builds being built
 > from branches?

 It could use `git describe --exact-match --tags HEAD`, if that exits
 with a success code we've checked out a tag and decide what to do
 about that.

 But couldn't we only have tags trigger that debbie build ?

 Adding a log of Jenkins operations could be useful to tell more about
 what's going on, btw.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5736#comment:22>
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.