Python 3.12 in testing repos

SunRed commented

2024-04-22 20:36:16 +02:00

Just as a heads-up to avoid similar problems as there were from updating from python 3.10 to 11 (#183), python 3.12 landed yesterday in arch's testing repos. Maybe we can also use this thread to document any issues arising and reiterate what has been done that this times migration goes smooth 😅
I only follow the development of the buildbot itself rather loosely so I also don't have an overview regarding this issue right now.

Just as a heads-up to avoid similar problems as there were from updating from python 3.10 to 11 (#183), python 3.12 landed yesterday in arch's testing repos. Maybe we can also use this thread to document any issues arising and reiterate what has been done that this times migration goes smooth 😅 I only follow the development of the buildbot itself rather loosely so I also don't have an overview regarding this issue right now.

👍 1

anonfunc commented

2024-04-22 20:43:19 +02:00

Owner

Once this whole batch is out of testing, I'd recommend not upgrading while it's being built, which could take a few days based on the 3.10 and 3.11 rebuilds.

Upgrading while it is still building could result in any packages linking to the new version 3.12 breaking until 3.12 is ready on our end.

Once this whole batch is out of testing, I'd recommend not upgrading while it's being built, which could take a few days based on the 3.10 and 3.11 rebuilds. Upgrading while it is still building could result in `any` packages linking to the new version `3.12` breaking until 3.12 is ready on our end.

👍 1

anonfunc added the

informational

label 2024-04-22 20:43:25 +02:00

anonfunc commented

2024-04-27 20:50:02 +02:00

Owner

Python moved out of testing today, building is in progress. 2033 packages are in this buildcycle.

anonfunc pinned this 2024-04-28 13:09:40 +02:00

Omlu commented

2024-04-28 16:23:05 +02:00

Hi, hello! Just passing by to report my issue here with your optimized packages in relation to python packages.

pacman -Qo /usr/lib/python3.11
/usr/lib/python3.11/ is owned by protonup-qt 2.9.2-1
/usr/lib/python3.11/ is owned by python-inputs 0.5-4
/usr/lib/python3.11/ is owned by python-pyrunning 0.0.13-1
/usr/lib/python3.11/ is owned by python-pysetting 0.0.6-1
/usr/lib/python3.11/ is owned by python-steam 1.4.4-2
/usr/lib/python3.11/ is owned by python-vdf 3.4-2
/usr/lib/python3.11/ is owned by vapoursynth R66-1.1
/usr/lib/python3.11/ is owned by vidcutter 6.0.5.1-7.1

Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11.

Hi, hello! Just passing by to report my issue here with your optimized packages in relation to python packages. ``` pacman -Qo /usr/lib/python3.11 /usr/lib/python3.11/ is owned by protonup-qt 2.9.2-1 /usr/lib/python3.11/ is owned by python-inputs 0.5-4 /usr/lib/python3.11/ is owned by python-pyrunning 0.0.13-1 /usr/lib/python3.11/ is owned by python-pysetting 0.0.6-1 /usr/lib/python3.11/ is owned by python-steam 1.4.4-2 /usr/lib/python3.11/ is owned by python-vdf 3.4-2 /usr/lib/python3.11/ is owned by vapoursynth R66-1.1 /usr/lib/python3.11/ is owned by vidcutter 6.0.5.1-7.1 ``` Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11.

👎 1

anonfunc commented

2024-04-28 19:16:52 +02:00

Owner

Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11.

Upgrading could result in any packages linking to the new version 3.12 breaking until 3.12 is ready on our end.

That's exactly what I said would happen.

> Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11. > Upgrading could result in `any` packages linking to the new version `3.12` breaking until 3.12 is ready on our end. That's exactly what I said would happen.

SunRed commented

2024-04-29 08:22:05 +02:00

Author

Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11.

Well, one way to fix that is to temporarily comment out the alhp repos in your pacman config and update your system. After that you should perhaps wait until those builds on alhp are ready before enabling those repos again to prevent potentially breaking partial updates of your system. The warnings regarding your local version of a package being newer than the one found in your configured repos can be safely ignored but sadly cannot be disabled afaik.

There is a patch for pacman I am planning on submitting that changes this behavior a bit but I would post here or in a new issue again when it's ready.

The problem last time with the python 3.10 to 11 migration afaik was that python packages even with the newest version/pkgrel were erroneously built with the previous (major) python version so that even doing a system update without enabled alhp repos couldn't fix this. At least that doesn't seem to be the case this time, so hooray for that. 🎉

> Right now, I'm unable to use programs like gpu-screen-recorder and spectacle, because both still are depending on python3.11. Well, one way to fix that is to temporarily comment out the alhp repos in your pacman config and update your system. After that you should perhaps wait until those builds on alhp are ready before enabling those repos again to prevent potentially breaking partial updates of your system. The warnings regarding your local version of a package being newer than the one found in your configured repos can be safely ignored but sadly cannot be disabled afaik. There is a patch for pacman I am planning on submitting that changes this behavior a bit but I would post here or in a new issue again when it's ready. The problem last time with the python 3.10 to 11 migration afaik was that python packages even with the newest version/pkgrel were erroneously built with the previous (major) python version so that even doing a system update without enabled alhp repos couldn't fix this. At least _that_ doesn't seem to be the case this time, so hooray for that. 🎉

🚀 1

anonfunc commented

2024-04-30 21:27:48 +02:00

Owner

First batch is now built and should be available on mirrors. Please report any remaining issues here.

🎉 2

Python 3.12 in testing repos #244