As far as I can see librsvg doesn't use it any longer.

See GNOME/librsvg!407

Install gitlab-clippy into /opt/cargo and adjust the PATH environment
so that it can be run from there easily. Do the same for cargo-c on
debian:testing.

Also rename the Dockerfiles for opensuse and fedora as it was done
for debian:testing recently.

Adding this package was a mistake and the issue is now fixed otherwise.

This reverts commit 728413cf.

Sven Neumann authored Oct 23, 2020 and Jordan Petridis committed Oct 28, 2020

* Remove obselete ubuntu and i386 builds
* Move the scripts inline the dockerfile
* rename the dockerfile so syntax highliting in editors works
* add openssl to the builddeps
* remove ccache from the deps as its no longer used

* Export GDK_PIXBUF_QUERYLOADERS var so autotools doesn't complain
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907306

* build the image with a usernamespace by default so it
works with our unpriv gitlab runners
similar to c19a8634

We will need it for GNOME/librsvg!407

It can be installed from package on opensuse and fedora.

Build and install it by means of cargo on debian and ubuntu. This
is untested as these images are currently disabled.

Closes #2

They are broken till they get ported to
user namespaces like opensuse and fedora images.

They broke somewhere along the line and became outdated
and obsolete.

similar to c19a8634

the stable fedora is barerly getting maintained,
and rawhide has tendancy to be breaking on its own
and its almost always broken and dated.

The CI runners can no longer run priviledged namespaces due to
security concenrs.

Adapted the Opensuse image since its the only one we are using atm
but the rest need to be fixed in the future as well.

We need this for the "cargo fmt" step in librsvg's CI.

Following https://github.com/containers/libpod/issues/1534, let's try
passing the `--cgroup-manager=cgroupfs` flag.

Otherwise, experimental feature branches might break librsvg's actual
CI.

This reverts commit 0e405c09.

The published oci image is still rawhide and hasn't been updated
to the branched f31 version yet

Previous one got depricated it seems.

Probably confused dockerfiles with compose files at some point

They are not relative to the context dir for some
reason... ¯\_(ツ)_/¯

fixup of c4c24d23

they just were not working