+1 maintenance report

[Nick Rosbrook]

Hello,

tl;dr -- In this report, there are three package removal requests
needing AA review, and one upload that is still stuck in -proposed
that would benefit from another set of eyes.

1. Package removal requests (rationale is in the bug report):

https://bugs.launchpad.net/ubuntu/+source/nield/+bug/2079349
https://bugs.launchpad.net/ubuntu/+source/glosstex/+bug/2079355
https://bugs.launchpad.net/ubuntu/+source/sslh/+bug/2079513

2. Upload needing follow up:

- detox FTBFS (https://bugs.launchpad.net/ubuntu/+source/detox/+bug/2079767)

This build was failing due to re-defined _FORTIFY_SOURCE. I removed
defs from upstream makefiles to allow distro build flags to take
precedence. I uploaded this fix and forwarded to Debian, but now there
is a build-time test failure on armhf only. I did not have time to
investigate further.

3. The rest:

- cruft-ng autopkgtest failure
(https://bugs.launchpad.net/ubuntu/+source/cruft-ng/+bug/2079840)

This was failing due to `set -u` and an unset variable in a script
that is called during a test. I patched the script to initialize the
variable to empty if needed, and I forwarded to Debian. This has
already migrated.

- vstream-client FTBFS
(https://bugs.launchpad.net/debian/+source/vstream-client/+bug/2079777)

This FTBFS due to several implicit declarations. I added a patch to
include the necessary headers, uploaded, and forwarded to Debian. This
has already migrated.

- datalad-next FTBFS
(https://bugs.launchpad.net/ubuntu/+source/datalad-next/+bug/2079776)

This FTBFS due to a missing Build-Depends: python3-boto3. Uploaded and
forwarded to Debian.

I wish I could have been more productive, but for $reasons, that's the
best I could do this week.

-NR