Mailing List Archive: v5.38.0 release branch now exists

v5.38.0 release branch now exists

May 20, 2023, 10:18 AM

Post #1 of 5 (183 views)

Porters,

I have created draft #21108 <https://github.com/Perl/perl5/pull/21108>, which creates a v5.38.0 release branch, which will currently build as v5.38.0-RC0.

There are more (small, I believe) known issues to review, but for now:
• on my laptop, t/porting/libperl.t fails, undefined current object: op.o: at porting/libperl.t line 254, <$nm_fh> line 2.
• the perldelta may yet have errors
• perlhist needs updating
The first worries me: I just updated macOS yesterday, which changed some bits of my build stack, and I wonder if this is now a general "new xcode problems" problem. I haven't tried building on Linux or building an older version. I don't want to ship a new perl that doesn't build on today's macOS.

The second: committers should feel free to push perldelta fixes to my branch, but be aware that I might drop or edit them!

The third: I'll do it soon.

I apologize for my general lack of updates on the release for the last two weeks. Other things, generally much more pressing, have kept piling up. I may be past enough of them now… ????

--
rjbs

Re: v5.38.0 release branch now exists [ In reply to ]

shlomif at shlomifish

May 20, 2023, 6:26 PM

Post #2 of 5 (183 views)

Permalink

hi all,

On Sat, 20 May 2023 13:18:17 -0400
"Ricardo Signes" <perl.p5p@rjbs.manxome.org> wrote:

> Porters,
>
> I have created draft #21108 <https://github.com/Perl/perl5/pull/21108>, which
> creates a v5.38.0 release branch, which will currently build as v5.38.0-RC0.
>

in bleadperl, 'cpanm Software::License' [and ergo dzil] fails on fedora37.

> There are more (small, I believe) known issues to review, but for now:
> • on my laptop, t/porting/libperl.t fails, undefined current object: op.o:
> at porting/libperl.t line 254, <$nm_fh> line 2.
> • the perldelta may yet have errors
> • perlhist needs updating
> The first worries me: I just updated macOS yesterday, which changed some
> bits of my build stack, and I wonder if this is now a general "new xcode
> problems" problem. I haven't tried building on Linux or building an older
> version. I don't want to ship a new perl that doesn't build on today's macOS.
>
> The second: committers should feel free to push perldelta fixes to my
> branch, but be aware that I might drop or edit them!
>
> The third: I'll do it soon.
>
> I apologize for my general lack of updates on the release for the last two
> weeks. Other things, generally much more pressing, have kept piling up. I
> may be past enough of them now… ????
>

--

Shlomi Fish https://www.shlomifish.org/
My Aphorisms - https://www.shlomifish.org/humour.html

If you laugh, Chuck Norris will only laugh with you if the joke is funny.
— https://www.shlomifish.org/humour/bits/facts/Chuck-Norris/

Please reply to list if it's a mailing list post - https://shlom.in/reply .

Re: v5.38.0 release branch now exists [ In reply to ]

haarg at haarg

May 20, 2023, 8:29 PM

Post #3 of 5 (183 views)

Permalink

On Sun, May 21, 2023 at 3:26?AM Shlomi Fish <shlomif@shlomifish.org> wrote:
>
> hi all,
>
> On Sat, 20 May 2023 13:18:17 -0400
> "Ricardo Signes" <perl.p5p@rjbs.manxome.org> wrote:
>
> > Porters,
> >
> > I have created draft #21108 <https://github.com/Perl/perl5/pull/21108>, which
> > creates a v5.38.0 release branch, which will currently build as v5.38.0-RC0.
> >
>
> in bleadperl, 'cpanm Software::License' [and ergo dzil] fails on fedora37.
>

This is a general bug in Software::License, and has nothing to do with blead.

Re: v5.38.0 release branch now exists [ In reply to ]

tony at develop-help

May 21, 2023, 8:19 PM

Post #4 of 5 (183 views)

Permalink

On Sat, May 20, 2023 at 01:18:17PM -0400, Ricardo Signes wrote:
> Porters,
>
> I have created draft #21108 <https://github.com/Perl/perl5/pull/21108>, which creates a v5.38.0 release branch, which will currently build as v5.38.0-RC0.
>
> There are more (small, I believe) known issues to review, but for now:
> • on my laptop, t/porting/libperl.t fails, undefined current object: op.o: at porting/libperl.t line 254, <$nm_fh> line 2.

This probably isn't critical to fully fix, adding a line before the
die like:

skip_all "Darwin needs a fix" if $^V < v5.39 && !defined $symbols->{o};;

should skip the test file on such systems while having it continue to
fail in future development releases.

To diagnose the problem, please run:

./perl porting/libperl.t

before the die you should see something like:

# command: "/usr/bin/nm -m ../libperl.a"

It may not be exactly that, please run whatever that shows and capture
the output. You will probably need to adjust the path to libperl.a.

Ideally open a new ticket with that output included.

Tony

Re: v5.38.0 release branch now exists [ In reply to ]

craig.a.berry at gmail

May 23, 2023, 6:41 PM

Post #5 of 5 (182 views)

Permalink

On Sun, May 21, 2023 at 10:20?PM Tony Cook <tony@develop-help.com> wrote:
>
> On Sat, May 20, 2023 at 01:18:17PM -0400, Ricardo Signes wrote:
> > Porters,
> >
> > I have created draft #21108 <https://github.com/Perl/perl5/pull/21108>, which creates a v5.38.0 release branch, which will currently build as v5.38.0-RC0.
> >
> > There are more (small, I believe) known issues to review, but for now:
> > • on my laptop, t/porting/libperl.t fails, undefined current object: op.o: at porting/libperl.t line 254, <$nm_fh> line 2.
>
> This probably isn't critical to fully fix, adding a line before the
> die like:
>
> skip_all "Darwin needs a fix" if $^V < v5.39 && !defined $symbols->{o};;
>
> should skip the test file on such systems while having it continue to
> fail in future development releases.
>
> To diagnose the problem, please run:
>
> ./perl porting/libperl.t
>
> before the die you should see something like:
>
> # command: "/usr/bin/nm -m ../libperl.a"
>
> It may not be exactly that, please run whatever that shows and capture
> the output. You will probably need to adjust the path to libperl.a.
>
> Ideally open a new ticket with that output included.

I can reproduce it and have reported it at
<https://github.com/Perl/perl5/issues/21117>.