From: Thomas Huth <thuth@redhat.com>
To: Brad Smith <brad@comstyle.com>,
Philippe Mathieu-Daud?? <philmd@redhat.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] tests/vm: update openbsd to release 6.8
Date: Mon, 9 Nov 2020 09:13:52 +0100 [thread overview]
Message-ID: <db2e674b-7d8b-850c-1b55-880529ee601f@redhat.com> (raw)
In-Reply-To: <2f27fba1-d5e6-6734-e608-36406e6fe00a@comstyle.com>
On 07/11/2020 07.07, Brad Smith wrote:
> ping.
It's not directly my turf, but I can add it to my next testing-related pull
request if nobody else picks this patch up before.
Thomas
> On 10/27/2020 6:22 AM, Brad Smith wrote:
>> On Tue, Oct 27, 2020 at 11:05:20AM +0100, Philippe Mathieu-Daud?? wrote:
>>> On 10/27/20 6:30 AM, Brad Smith wrote:
>>>> tests/vm: update openbsd to release 6.8
>>>>
>>>> A double dash at the end of a package name removes ambiguity
>>>> when the intent is to install a non-FLAVORed package.
>>>>
>>>> Signed-off-by: Brad Smith <brad@comstyle.com>
>>>> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>>>> Tested-by: Gerd Hoffmann <kraxel@redhat.com>
>>>> Reviewed-by: Philippe Mathieu-Daud?? <philmd@redhat.com>
>>> I confirm Brad sent us this patch off-list, and
>>> - our review comments are addressed,
>>> - the tags are correct.
>>>
>>> The patch format itself seems broken... Like a copy/paste
>>> into an email client...
>> Well, git diff vs a format-patch.
>>
>>
>> Subject: [PATCH] tests/vm: update openbsd to release 6.8
>>
>> A double dash at the end of a package name removes ambiguity
>> when the intent is to install a non-FLAVORed package.
>>
>> Signed-off-by: Brad Smith <brad@comstyle.com>
>> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>> Tested-by: Gerd Hoffmann <kraxel@redhat.com>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> tests/vm/openbsd | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/vm/openbsd b/tests/vm/openbsd
>> index 8356646f21..5ffa4f1b37 100755
>> --- a/tests/vm/openbsd
>> +++ b/tests/vm/openbsd
>> @@ -22,8 +22,8 @@ class OpenBSDVM(basevm.BaseVM):
>> name = "openbsd"
>> arch = "x86_64"
>> - link = "https://cdn.openbsd.org/pub/OpenBSD/6.6/amd64/install66.iso"
>> - csum =
>> "b22e63df56e6266de6bbeed8e9be0fbe9ee2291551c5bc03f3cc2e4ab9436ee3"
>> + link = "https://cdn.openbsd.org/pub/OpenBSD/6.8/amd64/install68.iso"
>> + csum =
>> "47e291fcc2d0c1a8ae0b66329f040b33af755b6adbd21739e20bb5ad56f62b6c"
>> size = "20G"
>> pkgs = [
>> # tools
>> @@ -36,10 +36,10 @@ class OpenBSDVM(basevm.BaseVM):
>> "bash",
>> "gmake",
>> "gsed",
>> - "gettext",
>> + "gettext-tools",
>> # libs: usb
>> - "libusb1",
>> + "libusb1--",
>> # libs: crypto
>> "gnutls",
>
next prev parent reply other threads:[~2020-11-09 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 5:30 [PATCH] tests/vm: update openbsd to release 6.8 Brad Smith
2020-10-27 10:05 ` Philippe Mathieu-Daudé
2020-10-27 10:22 ` Brad Smith
2020-11-07 6:07 ` Brad Smith
2020-11-09 8:13 ` Thomas Huth [this message]
2020-11-10 8:59 ` Brad Smith
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=db2e674b-7d8b-850c-1b55-880529ee601f@redhat.com \
--to=thuth@redhat.com \
--cc=brad@comstyle.com \
--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).