ProposedMigrationNotes
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
re2c
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 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?
ruby2.5
TBD?
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).
six
TBD?
ruby-defaults
TBD?
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?
mysql-8.0
TBD?
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 other projects. Seems crmsh needs py3.8 fixes for ast. Christian came up with a fix and submitted it upstream for review and integration
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.
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.
rdma-core
TBD?
unbound
TBD?
postgresql-12
TBD?
ldb
ldb is stuck because of python3-defaults, which still has many reds.
DPDK
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 fix in Debian already - needs an upload to debian to merge it from there.
cluster-glue
Andreas recently rebuilt cluster-glue, which was still using python3.7, but more is needed.
Current Transitions Notes
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.
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.)