Hi, I just noticed that Nettle cross ci builds fail, e.g., https://gitlab.com/gnutls/nettle/-/jobs/4791865769
This one fails with $ apt-get update -q Get:1 http://deb.debian.org/debian stable InRelease [151 kB] Get:2 http://deb.debian.org/debian-security stable-security InRelease [48.0 kB] Get:3 http://deb.debian.org/debian stable-updates InRelease [52.1 kB] Reading package lists... E: Repository 'http://deb.debian.org/debian stable InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm' E: Repository 'http://deb.debian.org/debian-security stable-security InRelease' changed its 'Codename' value from 'bullseye-security' to 'bookworm-security' E: Repository 'http://deb.debian.org/debian stable-updates InRelease' changed its 'Codename' value from 'bullseye-updates' to 'bookworm-updates' related to recent debian release. And when trying to find how to upgrade the image used, BUILD_IMAGES_PROJECT: gnutls/build-images DEBIAN_CROSS_BUILD: buildenv-debian-cross [...] image: $CI_REGISTRY/$BUILD_IMAGES_PROJECT:$DEBIAN_CROSS_BUILD I found the recent commit https://gitlab.com/gnutls/build-images/-/commit/268e1060cce9f3532439b7f0d1b9a9eec4afce2b deleting the corresponding docker file. I'm not that familiar with docker images, but I guess some of the options are 1. Switch to the cross-fedora38 image (https://gitlab.com/gnutls/build-images/-/blob/master/docker-cross-fedora38/Dockerfile?ref_type=heads). 2. Use some official debian image (not maintained by gnutls), and install needed cross compilers as part of each job. 3. Maintain a separate image (or images) for use by Nettle ci builds. E.g., I'm considering adding more tests depending on valgrind, so then it would be nice to include valgrind in the image. And it would be nice if all apt commands in the ci scripts could be eliminated. Efficiency could matter: extra work, like installing lots of packages as part of each ci job, makes the ci more expensive, and I don't know what limits there are to the gnutls project on gitlab, but by default. So advice appreciated. Regards, /Niels PS. On the topic on valgrind: Is it possible/practical to use valgrind in a cross setting, e.g., an x86_64 host, cross compiling for arm, and then use qemu-arm to run an arm valgrind binary in turn running the arm binary under test. Or is there some other way to run a cross valgrind? -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
