Debbie failing on all runs of postgis 3.0

[robe]

Even after the postgrsql 12 fix, debbie is still failing. But it seems this change is affecting all postgres branches, not just the 12. The 12 install issues were fixed.

Loading PostGIS into 'postgis_reg' 
  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis.sql
  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis_comments.sql
  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis_proc_set_search_path.sql
PostgreSQL 11.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.2.0-9) 8.2.0, 64-bit
  Postgis 3.0.0dev - r17032 - 2018-11-19 01:43:53
  scripts 3.0.0dev r17032
  GEOS: 3.8.0dev-CAPI-1.12.0 70a9773c
  PROJ: Rel. 5.2.0, September 15th, 2018


 tickets .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/tmp/3_0_pg12w64/test_95_diff)
-----------------------------------------------------------------------------
--- tickets_expected	2018-11-08 12:15:17.205801173 +0000
+++ /var/lib/jenkins/workspace/postgis/tmp/3_0_pg12w64/test_95_out	2018-11-19 16:33:01.165535816 +0000
@@ -125,8 +125,8 @@
 #696|010f000080060000000103000080010000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f03f0000000000000000000000000000f03f000000000000f03f0000000000000000000000000000f03f0000000000000000000000000000000000000000000000000000000000000000010300008001000000050000000000000000000000000000000000000000000000000000000000000000000000000000000000f03f0000000000000000000000000000f03f000000000000f03f0000000000000000000000000000f03f0000000000000000000000000000000000000000000000000000000000000000000000000000000001030000800100000005000000000000000000000000000000000000000000000000000000000000000000f03f00000000000000000000000000000000000000000000f03f0000000000000000000000000000f03f00000000000000000000000000000000000000000000f03f00000000000000000000000000000000000000000000000001030000800100000005000000000000000000f03f000000000000f03f0000000000000000000000000000f03f000000000000f03f000000000000f03f000000000000f03f0000000000000000000000000000f03f000000000000f03f00000000000000000000000000000000000000000000f03f000000000000f03f0000000000000000010300008001000000050000000000000000000000000000000000f03f00000000000000000000000000000000000000000000f03f000000000000f03f000000000000f03f000000000000f03f000000000000f03f000000000000f03f000000000000f03f00000000000000000000000000000000000000000000f03f00000000000000000103000080010000000500000000000000000000000000000000000000000000000000f03f000000000000f03f0000000000000000000000000000f03f000000000000f03f000000000000f03f000000000000f03f0000000000000000000000000000f03f000000000000f03f00000000000000000000000000000000000000000000f03f
 #720|MULTIPOINT(-1113194.91 4838471.4,-1113194.91 7326837.72,-1113194.91 11028513.63,556597.45 4838471.4,556597.45 7326837.72,556597.45 11028513.63,2226389.82 4838471.4,2226389.82 7326837.72,2226389.82 11028513.63,3896182.18 4838471.4,3896182.18 7326837.72,3896182.18 11028513.63,5565974.54 4838471.4,5565974.54 7326837.72,5565974.54 11028513.63)
 #723|0101000020e61000006284f068e33826c00000000000004440
-#723|0107000020e610000000000000
-#723|0107000020e610000000000000
+#723|0101000020e6100000000000000000f87f000000000000f87f
+#723|0101000020e6100000000000000000f87f000000000000f87f
 #723|0101000020e61000006284f068e33826c00100000000804b40
 #804|<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos srsDimension="2">0 0</gml:pos></gml:Point>
 #845|t
-----------------------------------------------------------------------------

I'm not sure how my fix for #4231 or if its just some other chagnes going on.

I haven't patched 2.5 yet with 12 fix, will see if that blows up too when Ido. That one is passing at the moment.