Re: Question about updating python to 3.10

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]

Hello Adolf,

> On 17 Dec 2021, at 11:55, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> 
> I am working on updating python from 3.8 to 3.10. Python itself is okay after some other python related programs were also updated due to their older versions not working with 3.10

Thank you for working on this.

> I am working through all the programs that reference python-3.8 in their rootfiles, or wherever, to change them to 3.10
> 
> My question comes with regard to the changes to the rootfiles to ensure they will be included properly in an update.

We will have to ship everything that puts anything into /usr/lib*/python3.*/site-packages again with the release of Python 3.10.

This isn’t fun, but not as much of a pain in the rear as shipping a new Perl release.

> For the addons then when I change the rootfile I am also incrementing the PAK_VER number in the lfs files and that ensures that they will be properly updated.

Yes. That is required for Pakfire to find a new version.

> I don't know what to do for the core programs where I have updated the rootfile. The lfs files for these programs don't have a PAK_VER number to increment and the actual package version number is not being changed so I don't know what I need to change in the lfs to ensure that the rootfile changes will be properly included in the update?

I would say committing everything into a “python-3.10” branch and submitting it all as a patchset is fine. All packages that have been touched in that branch will have to be shipped again which should be easy to identify if it all comes in one large branch.

> I would appreciate any help on what I need to do for these programs that have had changes only in their rootfiles.

Absolutely. Did you find anything that didn’t build yet?

-Michael

> 
> Regards,
> 
> Adolf.
> 
> -- 
> Sent from my laptop
>