From: Junio C Hamano <gitster@pobox.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: Ed Maste <emaste@freebsd.org>,
Git mailing list <git@vger.kernel.org>,
Carlo Arenas <carenas@gmail.com>
Subject: Re: Investigating Cirrus CI FreeBSD failures
Date: Tue, 31 May 2022 07:05:59 -0700 [thread overview]
Message-ID: <xmqqczftx0e0.fsf@gitster.g> (raw)
In-Reply-To: e31d26ad-3b0b-15c0-262f-4eee83220949@gmail.com
Philippe Blain <levraiphilippeblain@gmail.com> writes:
>> Ah, what happened here is that this is picking up the perl package
>> built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added
>> strerror_l.
>> https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa
>
> OK, so it is expected that the Cirrus 12.2 image would install this newer
> version of the perl package which if I understand correctly is not compatible
> with this version ?
>
> Is there a way to tell pkg not to update packages to incompatible versions,
> or is the FreeBSD policy that as soon as a release is marked as unsupported,
> then no guarantee is made that things (like installing packages) continue working
> on that version ?
Sorry for a noise, but I would also be curious to know, as it is
quite unexpected for a packaging system to miss such a compatibility
issue and for a distro to not care.
>> I expect this could have been addressed also by updating to 12.3.
>> Cirrus also supports "matrix" so both could be tested.
>
> For now we opted to just update to 12.3, see [1].
Indeed we did. Let's make sure we fast-track the topic down to
'master' and possibly to 'maint'. I do not think it is worth
letting it sit in 'next' for a week, like we do for usual topics.
Thanks.
P.S. I'll be offline today (like every other Tuesday).
next prev parent reply other threads:[~2022-05-31 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 0:38 Investigating Cirrus CI FreeBSD failures Philippe Blain
2022-05-21 0:52 ` Carlo Arenas
2022-05-30 16:09 ` Ed Maste
2022-05-30 20:15 ` Philippe Blain
2022-05-31 14:05 ` Junio C Hamano [this message]
2022-06-02 15:22 ` Johannes Schindelin
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=xmqqczftx0e0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=carenas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.