From: "Alex Bennée" <alex.bennee@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Kamil Rytarowski" <kamil@netbsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 3/4] tests/vm: update FreeBSD to 12.1
Date: Tue, 10 Mar 2020 13:40:38 +0000 [thread overview]
Message-ID: <87ftegiazt.fsf@linaro.org> (raw)
In-Reply-To: <87imjcies8.fsf@linaro.org>
Alex Bennée <alex.bennee@linaro.org> writes:
> Gerd Hoffmann <kraxel@redhat.com> writes:
>
>>> > - link = "https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.0/FreeBSD-12.0-RELEASE-amd64-disc1.iso.xz"
>>> > - csum = "1d40015bea89d05b8bd13e2ed80c40b522a9ec1abd8e7c8b80954fb485fb99db"
>>> > + link = "https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/FreeBSD-12.1-RELEASE-amd64-disc1.iso.xz"
>>> > + csum = "7394c3f60a1e236e7bd3a05809cf43ae39a3b8e5d42d782004cf2f26b1cfcd88"
>>
>>> Warning: Permanently added '[127.0.0.1]:39533' (ECDSA) to the list of known hosts.
>>> 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.12.0_1...
>>> Newer FreeBSD version for package pkg:
>>> To ignore this error set IGNORE_OSVERSION=yes
>>> - package: 1201000
>> ^^^^
>> 12.1 package
>>
>>> - running kernel: 1200086
>> ^^^^
>> 12.0 running
>>
>> I saw that too, but only *without* the patch. The upgrade to 12.1 fixes
>> that.
>
> Hmm I wonder if the cached assets got confused? It certainly re-ran the
> install rather than skipping straight to running the test.
OK I'm an idiot... I hadn't correctly updated the branch on my test
machine:
git fetch origin; and git checkout testing/next; and git reset --hard github/testing/next
vs
git fetch github; and git checkout testing/next; and git reset --hard github/testing/next
>
>> We might consider setting IGNORE_OSVERSION=yes, so this doesn't happen
>> again after FreeBSD 12.2 release. Not sure whenever that can have
>> unwanted side effects though, like packages not working properly.
>>
>> Any advise from the bsd guys?
>>
>> cheers,
>> Gerd
--
Alex Bennée
next prev parent reply other threads:[~2020-03-10 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 8:32 [PATCH 0/4] tests/vm: minor install tweaks, update netbsd & freebsd Gerd Hoffmann
2020-03-10 8:32 ` [PATCH 1/4] tests/vm: write raw console log Gerd Hoffmann
2020-03-10 8:48 ` Philippe Mathieu-Daudé
2020-03-16 14:16 ` Alex Bennée
2020-03-16 14:22 ` Philippe Mathieu-Daudé
2020-03-17 22:46 ` Cleber Rosa
2020-03-19 17:13 ` Alex Bennée
2020-03-10 8:32 ` [PATCH 2/4] tests/vm: move vga setup Gerd Hoffmann
2020-03-10 8:46 ` Philippe Mathieu-Daudé
2020-03-10 8:32 ` [PATCH 3/4] tests/vm: update FreeBSD to 12.1 Gerd Hoffmann
2020-03-10 10:38 ` Alex Bennée
2020-03-10 12:02 ` Gerd Hoffmann
2020-03-10 12:18 ` Alex Bennée
2020-03-10 13:40 ` Alex Bennée [this message]
2020-03-10 8:32 ` [PATCH 4/4] tests/vm: update NetBSD to 9.0 Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftegiazt.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=kamil@netbsd.org \
--cc=kraxel@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).