On Fri, Feb 19, 2021 at 10:41:44AM +0000, Peter Maydell wrote: > On Fri, 19 Feb 2021 at 10:39, Alex Bennée <alex.ben...@linaro.org> wrote: > > > > > > Hi, > > > > It looks like the build has been broken on Cirrus since at least 7b2c4c: > > > > https://cirrus-ci.com/github/qemu/qemu > > > > I did attempt to have a look but "vm-build-freebsd" seems to be failing > > with a different error > > FWIW the vm-build-freebsd build-and-test works for me, as I > continue to run it as part of the merge tests. Is this something > to do with whether you already have a freebsd image cached > as opposed to it getting re-built from scratch (perhaps with > a newer FreeBSD)?
The base image should be the same no matter what (updating that needs a tests/vm/freebsd update which in turn triggers a rebuild). The addon package versions may differ though, so in case a broken package enters the freebsd package repos it may happen that old, existing vm images continue to work whereas newly created images don't ... Trying to rebuild the freebsd image here results in this: [ ... ] ### Installing packages ... Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly, please wait... Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done Installing pkg-1.16.1... Newer FreeBSD version for package pkg: To ignore this error set IGNORE_OSVERSION=yes - package: 1202000 <- freebsd 12.2 expected ? - running kernel: 1201000 <- freebsd 12.1 running ? Ignore the mismatch and continue? [y/N]: So it seems the freebsd 12.1 images tries to fetch 12.2 packages when running "pkg install -y <list>", which would explain why they don't work. Switching to freebsd 12.2 should solve this, at least until 12.3 is released, but I'm wondering why the freebsd pkg utility fetches incompatible packages in the first place and whenever there is any way to avoid this ... take care, Gerd
