Perl 5.30 upgrade

[Jitka Plesnikova]

Hello,

Perl 5.30 was released on May 22 2019 and Perl 5.30 change is almost
approved by FESCo [1].

I have required `f31-perl' build-root for this purpose [2] and it was
created.

To prevent possible conflict with Python 3.8 rebuild, I start the
rebuild today
and you can be notified via mail about commits/builds in next days.
The merge to rawhide won't be done before approving changes by FESCo.

Please do not build anything into `f31-perl'. Boot-strapping core modules
is very peculiar. I also track all changes. You can do your upgrades into
rawhide freely in parallel.

You can check status on Perl 5.30 change page [3]

Regards,
Jitka Plesnikova

[1] https://pagure.io/fesco/issue/2134
[2] https://pagure.io/releng/issue/8384
[3] https://fedoraproject.org/wiki/Changes/perl5.30#Current_Status

[Jitka Plesnikova]

On 5/30/19 8:16 AM, Jitka Plesnikova wrote:
> Hello,
>
> Perl 5.30 was released on May 22 2019 and Perl 5.30 change is almost
> approved by FESCo [1].
>
> I have required `f31-perl' build-root for this purpose [2] and it was
> created.
>
> To prevent possible conflict with Python 3.8 rebuild, I start the
> rebuild today
> and you can be notified via mail about commits/builds in next days.
> The merge to rawhide won't be done before approving changes by FESCo.
>
> Please do not build anything into `f31-perl'. Boot-strapping core modules
> is very peculiar. I also track all changes. You can do your upgrades into
> rawhide freely in parallel.
>
> You can check status on Perl 5.30 change page [3]
>
> Regards,
> Jitka Plesnikova
>
> [1] https://pagure.io/fesco/issue/2134
> [2] https://pagure.io/releng/issue/8384
> [3] https://fedoraproject.org/wiki/Changes/perl5.30#Current_Status

We have successfully built all packages except 14 of them. I requested to
merge f31-perl tag back into f31 tag
https://pagure.io/releng/issue/8384#comment-573592 recently. Once rel-engs
do that, Perl 5.30.0 will become available in Fedora 31. If you built your
Perl package in the mean time, you would have to rebuild your package after
the merge again.

Regards,
Jitka