Monday 28 August 2023

+1 maintenance report

# +1 Maintenance Report

I was on +1 maintenance on the week of 2023-08-21.

The previous +1 maintenance report (by Shenjing Zhu) is here: https://lists.ubuntu.com/archives/ubuntu-devel/2023-August/042759.html.

## Details

- budgie-desktop: needs to test with mutter in -proposed
- node-yaml: succeeded with an autopkgtest retry
- node-tap-parser: succeeded with an autopkgtest retry
- node-foreground-child: needs a bigger VM instance to run the tests. I have opened an MP to add this package to the big_packages list: https://code.launchpad.net/~liushuyu-011/autopkgtest-cloud/+git/autopkgtest-package-configs/+merge/449652.
- node-signal-exit: needs to be migrated last. I have worked with Steve to solve the migration sequencing issue. The following Node.js packages were also correctly migrated due to this order correction:
  - node-istanbul
  - node-execa
  - node-foreground-child
  - node-gauge
  - node-loud-rejection
  - node-proper-lockfile
  - node-tap
  - node-write-file-atomic
- rust-block-buffer-0.9: Now got auto-removed in Debian (due to RC bugs). It might need to be removed in Ubuntu as well.
- rust-sval-derive: fixed in Debian, now synced back to Ubuntu
- rust-minijinja: impossible to fix in both Debian and Ubuntu. None of the dependencies are currently in the archive.
- slic3r-prusa: there is a race condition with the updater thread. Unfortunately, it's very difficult to fix this correctly: the WX object is a non-nullable reference according to C++ semantics, but it's `nullptr` during the runtime. A simple null check is impossible since the compiler will optimize your check away (the compiler believes the null check is useless).
- rust-cargo-mutants: The section of this package is incorrect. The issue was Debian upstream used the debcargo generator incorrectly. Fixed in Ubuntu: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/rust-cargo-mutants/+git/rust-cargo-mutants/+merge/449874. The patch is not forwardable to Debian (Debian is using a generator to generate the packaging files).
- rust-uom: The test failure was due to how PowerPC architecture handles floatpoint math. Ubuntu currently uses IBM long double, which is different from what the tests expect (IEEE 754R long double).
- librust-femme-dev, librust-kv-log-macro-dev: worked with Steve and evicted those two packages from the archive (Debian did the same) since they are no longer installable due to dependency issues.
- rust-log: for some reason, I can't get the autopkgtest to be queued (you can use https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=s390x&package=rust-async-std&trigger=migration-reference%2F0 to retry).

Thanks,
Zixing
Posted by at