From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Ed Maste <emaste@freebsd.org>
Cc: Git mailing list <git@vger.kernel.org>, Carlo Arenas <carenas@gmail.com>
Subject: Re: Investigating Cirrus CI FreeBSD failures
Date: Mon, 30 May 2022 16:15:37 -0400 [thread overview]
Message-ID: <e31d26ad-3b0b-15c0-262f-4eee83220949@gmail.com> (raw)
In-Reply-To: <CAPyFy2AETzTCJUtbxS+RmygajrUS5XUkZvF-1FVbJ67t61bJtg@mail.gmail.com>
Hi Ed,
Le 2022-05-30 à 12:09, Ed Maste a écrit :
> On Fri, 20 May 2022 at 20:38, Philippe Blain
> <levraiphilippeblain@gmail.com> wrote:
>>
>> Hi,
>>
>> I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD.
>> It seems something goes wrong with the Perl installation, as most failures
>> are in t9001-send-email.sh, and the error messages are:
>>
>> ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol "strerror_l@FBSD_1.6"
>
> 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 ?
>
>> I know next to nothing about Perl or FreeBSD, but simply changing our image
>> to FreeBSD 13.0 makes all failures in t9001 disappear [2]:
>>
>> ...
>> Is this something that we should do ? Or should we stick to FreeBSD 12
>> and try to debug this installation problem ?
>
> 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].
Thanks for your answer,
Philippe.
[1] https://lore.kernel.org/git/20220525125112.86954-1-levraiphilippeblain@gmail.com/
next prev parent reply other threads:[~2022-05-30 20:16 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 [this message]
2022-05-31 14:05 ` Junio C Hamano
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=e31d26ad-3b0b-15c0-262f-4eee83220949@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=carenas@gmail.com \
--cc=emaste@freebsd.org \
--cc=git@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