Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/misc/Vagrantfile: move to Debian bullseyes (12)
Date: Tue, 10 Sep 2024 22:44:56 +0200	[thread overview]
Message-ID: <20240910224456.52a90479@windsurf> (raw)
In-Reply-To: <20240909152748.3876779-1-peter@korsgaard.com>

On Mon,  9 Sep 2024 17:27:46 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:

> Ubuntu Bionic (18.04) was EOL'ed in June 2023:
> 
> https://ubuntu.com//blog/18-04-end-of-standard-support
> 
> And the VM image is only available in virtualbox format:
> 
> https://app.vagrantup.com/ubuntu/boxes/bionic64
> 
> So move to Debian bullseye (12), matching what we do for the docker image.
> This is available in virtualbox and libvirt (qemu) format:
> 
> https://app.vagrantup.com/debian/boxes/bullseye64
> 
> Bullseye does not come with rsync out of the box, so install it.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  support/misc/Vagrantfile | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)

Both applied to master, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-09-10 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 15:27 [Buildroot] [PATCH 1/2] support/misc/Vagrantfile: move to Debian bullseyes (12) Peter Korsgaard
2024-09-09 15:27 ` [Buildroot] [PATCH 2/2] support/misc/Vagrantfile: support libvirt provider Peter Korsgaard
2024-09-10 20:44 ` Thomas Petazzoni via buildroot [this message]

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=20240910224456.52a90479@windsurf \
    --to=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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