CentOS recently started to provide python3 by default obsoleted python36. Our
manual hack broke the test suite and is no longer required.
(cherry picked from commit e22c97e1cee806b9e7ecf7a06c31dab959c6c31c)
We suddenly started to have some linking issues in the 0.27 branch after
the libcurl packages were updated in the conan-center repositories.
After some experimentation I took the following steps to fix up the
situation:
- Update conan to latest version
- Update of libcurl to the latest version available
- Use libcurl static libraries
Note that the change to use static libraries is just to make the
deployment step as easier as possible in the travis builds.
- Arch migrated their container from the base account to the archlinux account
- The container got severely stripped down: there is no awk, diff, which, grep
=> we need to preinstall these, otherwise the distro detection function fails
(cherry picked from commit 73739735eb636fc9db9dab2606588c7a930e2e8b)
- the script needs to be able to bootstrap everything even on platforms where we
don't have bash
- drop function which is bash specific
(cherry picked from commit 9f01b86d2219d2f4cbb23730bba79c2b779621a2)
CentOS now provides it's own symlink of python3 -> python34, so we either remove
it first or symlink if that file doesn't exist yet.
This fixes#666.
(cherry picked from commit 045c8b32927720ece265e01d8a80ce782692a315)
This is needed in some tests which are using exiv2json.
It seems that during metadata conversion, the dates are converted from the
original timezone (which seems to be saved in xmp) into the local time zone.
- add Vagrantfile to contrib/vms
- add custom provisioning via shell scripts
- move gitlab-ci before_script: to ci/install_dependencies.sh which is also used
by vagrant
- change COPR setup on CentOS 7 (yum-plugin-copr does not seem to work)
- add a GitLab CI configuration file to run a pipeline on the major Linux
distros
- add a build script that builds all build combinations of exiv2 & runs the test
suite
