From: Carlo Arenas <carenas@gmail.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: git@vger.kernel.org, "Ed Maste" <emaste@freebsd.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] ci: update Cirrus-CI image to FreeBSD 13.0
Date: Tue, 24 May 2022 21:35:02 -0700 [thread overview]
Message-ID: <CAPUEspi0q_vNeQ9qYfNzCt7w1noBdNRWZ2dM1hqJroH4zt2x=g@mail.gmail.com> (raw)
In-Reply-To: <6a3aecf1-1c0d-f4fc-7d0e-455eb0ccc92c@gmail.com>
On Tue, May 24, 2022 at 1:53 PM Philippe Blain
<levraiphilippeblain@gmail.com> wrote:
>
> Hi Carlo,
>
> Le 2022-05-24 à 15:20, Carlo Marcelo Arenas Belón a écrit :
> > did you try to use 12.3 which should be supported for a little longer?
>
> Yes, I tested 12.3 and it also works. We could switch to that and
> keep 13.0 for later.
This seems like the better option overall; feel free to include
whatever footer you decide to use with my name in your next reroll.
> >> The FreeBSD image we use is FreeBSD 12.2, which is unsupported since
> >> March 31st, 2022 [1]. Switching to a supported version, 13.0,
> >> makes this error disappear [2].
> >
> > I think 13.1 might be better, since with this change we are also implicitly
> > making a move to say that we don't really care about the old (but still
> > supported) maintenance branch, but will only look at the "latest" version
> > instead.
>
> I agree with your reasoning, but 13.1 was not listed in the list of images on Cirrus-CI [1]. They
> say they support all Google Compute Engine images, but I could not find a public list
> of these images ([2] seems to be it but I don't want to create an account just
> to see a list!).
Good point; BTW I'd noticed before that the easiest way is to "try it"
since the Cirrus documentation seems to lag behind for a little while,
and so as you can
see in this[0] run, it is working fine as well.
[0] https://github.com/carenas/git/runs/6584764718
> [1] https://cirrus-ci.org/guide/FreeBSD/
> [2] https://console.cloud.google.com/compute/images
next prev parent reply other threads:[~2022-05-25 4:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 16:58 [PATCH] ci: update Cirrus-CI image to FreeBSD 13.0 Philippe Blain
2022-05-24 19:20 ` Carlo Marcelo Arenas Belón
2022-05-24 20:52 ` Philippe Blain
2022-05-25 4:35 ` Carlo Arenas [this message]
2022-05-24 19:24 ` Ævar Arnfjörð Bjarmason
2022-05-24 20:56 ` Philippe Blain
2022-05-25 10:37 ` Johannes Schindelin
2022-05-25 12:51 ` [PATCH v2] ci: update Cirrus-CI image to FreeBSD 12.3 Philippe Blain
2022-05-25 15:50 ` Junio C Hamano
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='CAPUEspi0q_vNeQ9qYfNzCt7w1noBdNRWZ2dM1hqJroH4zt2x=g@mail.gmail.com' \
--to=carenas@gmail.com \
--cc=avarab@gmail.com \
--cc=emaste@freebsd.org \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.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;
as well as URLs for NNTP newsgroup(s).