ProposedMigrationNotes
|
Size: 6491
Comment: pacemaker has made progress, but is still on proposed migration for i386 issue
|
Size: 3825
Comment: Added a few new packages showing up in the server team proposed migration page today
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| == memcached FTBFS == The FTBFS is on s390x only [1] Broken in Debian the same way [2] Fail on unittest assertion: ``` ok 10 - stats_prefix_record_set testapp: testapp.c:355: test_stats_prefix_dump: Assertion `strcmp(expected, stats_prefix_dump(&length)) == 0' failed. ``` I checked the latest tarball from upstream and it is reproducible without any Debian/Ubuntu delta. So it is an issue in the recent 1.5.21 release. The same is true for their git-master branch. Seems like a swap of the tests on big-endian? I filed [3] for now [1]: https://launchpadlibrarian.net/462233770/buildlog_ubuntu-focal-s390x.memcached_1.5.21-1_BUILDING.txt.gz [2]: https://buildd.debian.org/status/fetch.php?pkg=memcached&arch=s390x&ver=1.5.21-1&stamp=1580041692&raw=0 [3]: https://github.com/memcached/memcached/issues/606 === re2c === [[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...? Debian doesn't run i386 tests https://ci.debian.net/packages/r/re2c/ Lets mask it on i386 as it is autopkgtest env related and only showing up there. => https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-re2c/+merge/378381 === python-cffi (1.13.2-1build2) === Latest changes are attempts to build with the i386 packages restored. Depends on libffi 3.3-3, which is stuck in proposed. libffi appears to have both py2 and py3 dependencies, so presumably this is part of the python2 work? |
|
| Line 60: | Line 18: |
=== 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). Also checked with security Team and they are ok to handle that in the 4.2 upload. I added a update-excuse bug for qemu => 1861482 Mostly for the sake of avoiding others to work on it while it is solved already. |
|
| Line 77: | Line 28: |
=== 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 113: | Line 54: |
| Line 118: | Line 58: |
| == mecab == TBD? == kronosnet == TBD? == ruby2.7 == TBD? == apache2 == TBD? == rubygems-integration == TBD? |
|
| Line 119: | Line 81: |
| * php7.4 transition upcoming, but hasn't started yet * ruby transition upcoming, but hasn't started yet |
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
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
TBD?
kronosnet
TBD?
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.
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)