Rust-pyo3 FTBFS and dependent packages

[Hans Joachim Desserud]

Mainly filed to keep track of connected build failures. I expect most to be resolved sooner or later, unblocking other packages in the chain.

Starting with rust-pyo3 [1] this package is currently waiting for missing build dependencies librust-pyo3-ffi-0.17.3+default-dev and librust-pyo3-macros-0.17.3+default-dev.

Both rust-pyo3-macros [2] and rust-pyo3-ffi [3] have built successfully, these packages are waiting for autopkgtests to run so that they can migrate from lunar-proposed to -release. I believe once both are in place, rust-pyo3 should automatically rebuild with the available dependencies.

In turn, python-cryptography [4] is currently waiting for librust-pyo3-0.17-dev to build, which is one of the binary packages from rust-pyo3. Once built successfully, this should provide the binary package python3-cryptography with which a sufficiently high version should resolve the build wait for pyopenssl [5] and problems for diffoscope [6]. (Though the latter version requirement is a bit odd, since it is not in the control file, so I don't see why it requires a newer version [7])

As one can see, most of these issues should resolve themselves in time. In the meantime, I want to keep track of why the builds are failing as well as how they are chained together. In any case, I'll cross out each item as they are resolved.

[1] https://bugs.launchpad.net/ubuntu/+source/rust-pyo3
[2] https://bugs.launchpad.net/ubuntu/+source/rust-pyo3-macros
[3] https://launchpad.net/ubuntu/+source/rust-pyo3-ffi
[4] https://launchpad.net/ubuntu/+source/python-cryptography
[5] https://launchpad.net/ubuntu/+source/pyopenssl
[6] https://launchpad.net/ubuntu/+source/diffoscope
[7] https://launchpadlibrarian.net/641029781/buildlog_ubuntu-lunar-amd64.diffoscope_229_BUILDING.txt.gz

[Hans Joachim Desserud (hjd)]

Looks like these have been resolved and are all building successfully now.

python-cryptography and pyopenssl seems to wait on results for autopkgtests, but any problems there is likely a separate issue.