public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Question about updating python to 3.10
Date: Fri, 17 Dec 2021 11:55:19 +0100	[thread overview]
Message-ID: <d745d934-c8f7-9458-f80e-b9d48d07a73d@ipfire.org> (raw)

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

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

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.

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.

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 appreciate any help on what I need to do for these programs that 
have had changes only in their rootfiles.


Regards,

Adolf.

-- 
Sent from my laptop


             reply	other threads:[~2021-12-17 10:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 10:55 Adolf Belka [this message]
2021-12-17 11:41 ` Michael Tremer
2021-12-26 14:38   ` Adolf Belka
2021-12-26 20:55     ` Michael Tremer
2022-01-02 13:44       ` Adolf Belka
2022-01-03 10:52         ` Michael Tremer
2022-01-03 11:31           ` Adolf Belka
2022-01-03 11:32             ` Michael Tremer
2022-01-04 12:49               ` Adolf Belka
2022-01-07 16:49                 ` Michael Tremer
2022-01-11 14:32                   ` Adolf Belka
2022-01-12 18:10                     ` Michael Tremer
2022-01-12 21:08                       ` Adolf Belka
2022-01-13  9:32                         ` Michael Tremer
2022-01-18 15:02                           ` Michael Tremer
2022-01-18 16:42                             ` Adolf Belka
2022-01-18 18:51                               ` Michael Tremer
2022-01-18 21:21                                 ` Adolf Belka
2022-01-19  8:25                                   ` Michael Tremer
2022-01-19 12:33                                     ` Adolf Belka
2022-01-19 19:52                                       ` Adolf Belka
2022-01-20 16:51                                         ` Michael Tremer
2022-01-24 12:46                                           ` Adolf Belka
2022-01-24 16:24                                             ` Michael Tremer

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=d745d934-c8f7-9458-f80e-b9d48d07a73d@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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