Hi,
On Mon, 2018-01-22 at 10:46 +0000, Greg Clough wrote:
> Unless the PostGIS team have checked this first, it's probably their issue to
> resolve. Please re-submit it there:
This is (now, was) definitely a repo issue. Kurt, updated repo a few days ago.
Can you please confirm that it works now?
Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR