ProposedMigrationNotes
|
Size: 5759
Comment:
|
Size: 4570
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| === re2c === | 2020-02-12: Passes on everything but i386 now. Migration is blocked because of that. |
| Line 14: | Line 14: |
| [[https://bugs.launchpad.net/ubuntu/+source/re2c/+bug/1859980|LP: #1859980]] This is blocked on i386 due to a bunch of test failures, including some relating to "stadfa", and a scattering other others. Debian ran into a [[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934697|build issue]] due to a build date in the manual page which they've fixed in this version. Debian has an unreleased 1.3-2 that contains a build-dep for python3-pygments (this doesn't appear related to the test failure afaict --bryce.) The autopkgtest essentially just runs the upstream testsuite, which passes fine on i386, so the issue presumably is due to something distinct about the autopkgtest platform/hardware/set-of-x86-features...? === python-cffi === TBD? |
|
| Line 30: | Line 19: |
| === Qemu === There is a qemu 4.0 with some CVEs hanging on failed build. But Christian has a qemu 4.2 soon to be ready that works and will fix the same issues (and more). |
|
| Line 37: | Line 22: |
Appears part of python2 work? cjwatson appears to be giving attention to this. |
|
| Line 42: | Line 29: |
| === nss === Is blocked by some JDK tests on arm Two of them seem odd and always fail or skip. The only one that sometimes works is http://autopkgtest.ubuntu.com/packages/o/openjdk-lts/focal/arm64 The result is literally "jdk FLAKY timed out" For now Christian restarted, but maybe the test should be masked. @Doko - from the uploader it seems you handle openjdk-lts opinions on how to handle its tests? |
|
| Line 55: | Line 32: |
=== crmsh === tests block on new python3-default "crmsh.minieval.FeatureNotAvailable: Sorry, Constant is not available in this evaluator" The issue is reproducible outside the test environment. It seems ast processing changed in py3.8 Found other changes like "py3.8 uses ast.Constant instead of ast.Num, ast.Str, ast.NameConstant" in [[https://github.com/mommothazaz123/simpleeval/commit/65ab6c510563a490f22b7307b7370457cd839afe|other projects]]. Seems crmsh needs [[https://docs.python.org/3/library/ast.html#ast.AST|py3.8 fixes for ast]]. Christian came up with a fix and [[https://github.com/ClusterLabs/crmsh/issues/518|submitted it upstream]] for review and integration |
|
| Line 70: | Line 37: |
| '''<andreas 2020-01-30>''' The samba stack is done (samba, sssd, ldb, talloc, tdb) wrt the python 3.8 transition. |
|
| Line 74: | Line 43: |
| '''<andreas 2020-01-30>''' This is fixed. |
|
| Line 76: | Line 47: |
| TBD? | Missing build for i386. Depends on python3-defaults. |
| Line 80: | Line 52: |
| TBD? === postgresql-12 === TBD? |
Depends on python3-defaults |
| Line 90: | Line 58: |
| === DPDK === | === mecab === |
| Line 92: | Line 60: |
| DPDK breaks indirectly on the new python as well. The tests have a unversioned python dependency that e.g. breaks pciutils now. Christian has a [[https://salsa.debian.org/debian/dpdk/commit/bda4445c38450c38adb45a7f833155eaff3e3bf0|fix in Debian]] already - needs an upload to debian to merge it from there. |
From log, looks like there was a timeout at 84% done while the test was running, following main.perror. The previous run failed similarly but at 92% following test case main.subselect. Guessing this needs an adjustment to allow for longer running tests, or to shorten the test run? === kronosnet === Failure on i386 Appears due to unmet dependencies for gcc:i386 and make:i386 This is likely fixable by replacing the test dependencies on gcc and make with a test dependency on build-essential (the autopkgtest cross-test implementation special-cases build-essential, mapping it to build-essential:native + crossbuild-essential-$arch:native). === ruby2.7 === TBD? === apache2 === TBD? === rubygems-integration === TBD? |
| Line 98: | Line 87: |
| === cluster-glue === Andreas recently rebuilt cluster-glue, which was still using python3.7, but more is needed. |
|
| Line 104: | Line 88: |
| * php7.4 transition upcoming, but hasn't started yet * ruby transition upcoming, but hasn't started yet |
|
| Line 121: | Line 107: |
| See https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195 |
Server Team - Proposed Migration Notes
This collects notes and findings from the server team's proposed migration page for the current development release. This page lists packages that are stuck in proposed due to a variety of issues, some of which are in-scope for the server team, others of which may have broader causes.
Blocked Packages
Below are the server team's collective guesses as to what's going on with some of the packages listed as .
Pacemaker
Pacemaker has been stuck for a while. Andreas believes the current blockage is due to python3.8. He somewhat traced it down to: pacemaker -> pacemaker-resource-agents -> resource-agents -> cluster-glue -> python3.8 -> libpython3.8-stdlib -> libffi
2020-02-12: Passes on everything but i386 now. Migration is blocked because of that.
ruby2.5
TBD?
six
TBD?
Appears part of python2 work? cjwatson appears to be giving attention to this.
ruby-defaults
TBD?
mysql-8.0
TBD?
Samba
Regarding samba, Andreas had to merge two i386 hints (for samba/i386 and tdb/i386), trigger rebuilds after ldb/talloc/tdb were uploaded, and kick new test runs with specific triggers to sort out tdb runs with plinth and samba itself.
<andreas 2020-01-30> The samba stack is done (samba, sssd, ldb, talloc, tdb) wrt the python 3.8 transition.
sssd
sssd has an FTBFS with python3.8, which Andreas started to troubleshoot last night (Mon Jan 27, 2020) and will continue today. That rebuild needs to work to unblock all of this.
<andreas 2020-01-30> This is fixed.
rdma-core
Missing build for i386. Depends on python3-defaults.
unbound
Depends on python3-defaults
ldb
ldb is stuck because of python3-defaults, which still has many reds.
mecab
From log, looks like there was a timeout at 84% done while the test was running, following main.perror. The previous run failed similarly but at 92% following test case main.subselect.
Guessing this needs an adjustment to allow for longer running tests, or to shorten the test run?
kronosnet
Failure on i386
Appears due to unmet dependencies for gcc:i386 and make:i386
This is likely fixable by replacing the test dependencies on gcc and make with a test dependency on build-essential (the autopkgtest cross-test implementation special-cases build-essential, mapping it to build-essential:native + crossbuild-essential-$arch:native).
ruby2.7
TBD?
apache2
TBD?
rubygems-integration
TBD?
Current Transitions Notes
* php7.4 transition upcoming, but hasn't started yet * ruby transition upcoming, but hasn't started yet
Cluster Stack Transition
There may be some residual items from this migration.
Python 2 Deprecation
Doko writes, "One more update, the unversioned python packages are now gone in focal. There will be some cleanup to do for NBS and build dependencies. A more complete follow-up will be sent next week. I removed a lot of packages from focal to get this done. Apologies if that affects any derivative. Please contact me on irc or via email to restore those package. However I don't have the resources to actively port these packages to Python3."
Python 3.8 Transition
These items appear blocked due to the https://people.canonical.com/~ubuntu-archive/transitions/html/python3.7-8.html python 3.8 transition.
On Focal tests related to python Christian has seen a zillion of these "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used". None in server packages, but some cleanup for that is likely to follow.
See https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195
Final Notes
The proposed migration list is highly volatile; packages come and go on a regular basis. So, if this page's last update is more than a few days ago it is probably outdated. If it hasn't been updated in a few weeks, it's probably obsolete. (And if it hasn't been updated in a few months, please feel free to delete it since it's evidently no longer used.)
ServerTeam/ProposedMigrationNotes (last edited 2020-02-20 23:02:00 by bryce)