Vagrant and Travis-CI: update to Ubuntu Bionic#6111
Conversation
…it to fill the PDF CreationDate, so as to get reproducible output
|
CC @dmorissette This may impact your updates for your mapml works. If you haven't started refreshing expected result, I presume merging this PR first would make sense |
|
@rouault - wondering how do you get msautotest to use the .alternative results? |
|
Thanks. I didn't realise that was already in place. I might look at a similar approach to getting msautotest to run on Appveyor. |
Hum, I'd be afraid this would result in having a lot of variants, and the issue with AppVeyor/Windows is that it is less easy to update. You actually need to access to the Windows environment to be able to refresh the tests, which would be highly inconvenient from my perspective. At least with Vagrant, I believe anybody is in position to update them. I was a bit hesitant about introducing this .alternative mechanism to start with. My idea is that at some point we use only the PROJ >= 6 code path, and no longer have a need for alternative expected results |
Fixes #5775
By using ubuntugis-unstable, this also upgrades to GDAL 3 & PROJ 7
PHP 5.6 and 7.0 Travis-CI configs are no longer tested as not supported on Bionic
Number of expected results have been regenerated due to changes in libraries (with the build in /vagrant/build_vagrant)
Like previously, the PHP 7.1 and 7.2 configs still use PROJ with the legacy proj_api.h, while PHP 7.3 uses PROJ >= 6 proj.h API.
For that later config, a number of .alternative expected results have been created due to subtle differences in coordinate reprojections between PROJ legacy and modern API (with the build in /vagrant/build_vagrant_proj7)