* retried autopkgtests using "./retry-autopkgtest-regressions
--log-regex 'Temporary failure resolving'" and simliar patterns
* retriggered fdroidserver/armhf for ruamel.yaml 0.16.10-2 which had
new temprorary failure cause 'Could not resolve proxy: squid.internal'
* rebuilt hoel glewlwyd to finish orcania transition, but finally the
sync of hoel fixed the ftbfs of glewlwyd and ulfius still needs to be
fixed
* dropped Python 2 PyCryptodome support from kodi to let pycryptodome migrate
* NMUd wordpress-shibboleth to finish shibboleth-sp transition
* retriggered several tests for node-boom
* prepared MP against britney1 to support hints in Git:
https://code.launchpad.net/~rbalint/britney/britney1-ubuntu-hints-from-git/+merge/386856
* prepared a few hints for regressions:
https://code.launchpad.net/~rbalint/britney/hints-ubuntu/+merge/386878
* updated python-cogent to new upstream release to fix autopkgtest,
but there are new failures so it stayed in Salsa
(https://salsa.debian.org/med-team/python-cogent) for now and I added
a hint for it
I had some issues reproducing autopkgtest failures on exotic
architectures because autopkgtest-build-lxd fails on bos01 vms due to
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225 but it
can be worked around by logging into the lxc container being prepared
before the timeout and stopping snapd and snapd.seeded services.
Cheers,
Balint
--
Balint Reczey
Ubuntu & Debian Developer
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
