| 1 |
Hello, |
| 2 |
|
| 3 |
TL;DR: py3.8 unmasked where possible, py3.9 is ready for package |
| 4 |
testing, arch teams need to finally finish pending keywordreqs. |
| 5 |
|
| 6 |
|
| 7 |
Upstream has recently released Python 3.9.0b1. This means that there |
| 8 |
are no further major changes planned and it is now time to start testing |
| 9 |
packages for real. For this reason, I have added python3_9 target |
| 10 |
and bootstrapped the base package subset that should make it now |
| 11 |
possible to start testing other packages without hitting huge dependency |
| 12 |
cycles. |
| 13 |
|
| 14 |
Please remember to run tests on Python 3.9 when testing packages. |
| 15 |
From my experience, the majority of issues are ImportErrors or |
| 16 |
AttributeErrors due to removed stuff (previously deprecated since 3.1 |
| 17 |
to 3.4). My recommendation is to look into py3.8 reference [1] and find |
| 18 |
the deprecated function there, with recommendation how to replace it. |
| 19 |
The 'What\'s new' [2] may also be helpful, or full changelog [3]. |
| 20 |
|
| 21 |
|
| 22 |
I would like to remind you that all non-amd64 architectures have had |
| 23 |
Python 3.8 target masked due to unresolved ages-old keywordreqs. This |
| 24 |
resulted in 3.9 being masked as well. I've attempted to deal with this, |
| 25 |
and I've been able to keyword and unmask py3.8+3.9 on ppc, ppc64, sparc |
| 26 |
and x86. Sam is working on arm/arm64, and Rolf is working on hppa |
| 27 |
(where the situation is horrible AFAICS). This leaves nobody on alpha |
| 28 |
and ia64. |
| 29 |
|
| 30 |
Therefore, I would like to ask alpha and ia64 arch teams to finally |
| 31 |
start processing Python keywording requests. Given that our package |
| 32 |
manager and large part of tooling is in Python, it is kinda important to |
| 33 |
have working Python in Gentoo. If we can't manage this, we probably |
| 34 |
should remove these arches altogether. |
| 35 |
|
| 36 |
That said, if somebody can give me access to alpha, ia64, hppa, arm, |
| 37 |
arm64 hardware (highest priority listed first), I can help. I can also |
| 38 |
give you a list of urgent bugs if you wish. The highest priority is to |
| 39 |
get depgraph clean after unmasking targets, the final goal is to restore |
| 40 |
all lost keywords on Python packages. Please note that some arches |
| 41 |
might be missing proper bugs due to the whole mess resulting from delays |
| 42 |
(e.g. because arch team keyworded old version and nobody noticed that |
| 43 |
keywords were effectively lost again). |
| 44 |
|
| 45 |
To check what needs to be keyworded to unmask targets, remove the mask |
| 46 |
from your arch profile and run: |
| 47 |
|
| 48 |
pkgcheck scan -c VisibilityCheck -a <arch> |
| 49 |
|
| 50 |
To check all lost keywords: |
| 51 |
|
| 52 |
pkgcheck scan -c DroppedKeywordsCheck -a <arch> |
| 53 |
|
| 54 |
One-liner to get ekeyword invocations: |
| 55 |
|
| 56 |
pkgcheck scan -c DroppedKeywordsCheck -a <arch> -R FormatReporter \ |
| 57 |
--format \ |
| 58 |
'ekeyword {category}/{package}/{package}-{version}.ebuild ~<arch>' |
| 59 |
|
| 60 |
|
| 61 |
Thank you! |
| 62 |
|
| 63 |
|
| 64 |
[1] https://docs.python.org/3.8/library/index.html |
| 65 |
[2] https://docs.python.org/3.9/whatsnew/3.9.html |
| 66 |
[3] https://docs.python.org/3.9/whatsnew/changelog.html |
| 67 |
|
| 68 |
-- |
| 69 |
Best regards, |
| 70 |
Michał Górny |
Archives