SELinux Security Module development
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: Ondrej Mosnacek <omosnace@redhat.com>, selinux@vger.kernel.org
Subject: Re: [PATCH userspace 2/2] scripts/ci: use F34 image instead of F33
Date: Wed, 12 May 2021 18:18:11 +0200	[thread overview]
Message-ID: <87wns4lyd8.fsf@redhat.com> (raw)
In-Reply-To: <20210512102529.122753-3-omosnace@redhat.com>

Ondrej Mosnacek <omosnace@redhat.com> writes:

> Now that F34 has been released, it's time to update the CI Vagrantfile
> to use the new Fedora version. This also fixes the failure in the
> recently added vsock_socket test that depends on a bugfix, which made it
> to the F34 image's kernel, but is not in the F33 image's.
>
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>

Acked-by: Petr Lautrbach <plautrba@redhat.com>


> ---
>  scripts/ci/Vagrantfile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/ci/Vagrantfile b/scripts/ci/Vagrantfile
> index d7c7bb39..20c523a0 100644
> --- a/scripts/ci/Vagrantfile
> +++ b/scripts/ci/Vagrantfile
> @@ -34,7 +34,7 @@ SCRIPT
>  # backwards compatibility). Please don't change it unless you know what
>  # you're doing.
>  Vagrant.configure("2") do |config|
> -  config.vm.box = "fedora/33-cloud-base"
> +  config.vm.box = "fedora/34-cloud-base"
>    config.vm.synced_folder "../..", "/root/selinux"
>  
>    config.vm.provider "virtualbox" do |v|
> -- 
> 2.31.1


  reply	other threads:[~2021-05-12 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 10:25 [PATCH userspace 0/2] Bump testsuite CI image to F34 Ondrej Mosnacek
2021-05-12 10:25 ` [PATCH userspace 1/2] libselinux: fix invalid free in store_stem()/load_mmap() Ondrej Mosnacek
2021-05-12 10:56   ` Christian Göttsche
2021-05-18 18:43     ` Petr Lautrbach
2021-05-12 10:25 ` [PATCH userspace 2/2] scripts/ci: use F34 image instead of F33 Ondrej Mosnacek
2021-05-12 16:18   ` Petr Lautrbach [this message]
2021-05-18  8:05     ` Petr Lautrbach

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=87wns4lyd8.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=omosnace@redhat.com \
    --cc=selinux@vger.kernel.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