New patches posted with correctly formatted changelog.
Failures: budgie-extras/1.0.2-0ubuntu1 (arm64, amd64, armhf, i386, ppc64el, s390x) update-manager/1:20.04.10.1 (arm64, amd64, armhf, ppc64el, s390x) ubuntu-release-upgrader/1:20.04.23 (arm64, amd64, armhf, ppc64el, s390x)
Are all related to code style errors caught by the updated linter. These are not regressions.
Failures: python-b2sdk/1.0.2-1 (armhf) update-manager/1:20.04.10.1 (armhf) mu-editor/1.0.2+dfsg-4build1 (amd64)
python-b2sdk failure is due to a segfault after its test suite has completed, not related to this update update-manager is again the same style error as above mu-editor appears to be a timeout, likely a transient failure
Failures: elpy/1.32.0-2 (amd64)
Are transient (timeout in profiling), a manual re-run succeeded https://autopkgtest.ubuntu.com/packages/e/elpy/focal/amd64
New patches posted with correctly formatted changelog.
Failures: extras/ 1.0.2-0ubuntu1 (arm64, amd64, armhf, i386, ppc64el, s390x) manager/ 1:20.04. 10.1 (arm64, amd64, armhf, ppc64el, s390x) release- upgrader/ 1:20.04. 23 (arm64, amd64, armhf, ppc64el, s390x)
budgie-
update-
ubuntu-
Are all related to code style errors caught by the updated linter. These are not regressions.
Failures: b2sdk/1. 0.2-1 (armhf) manager/ 1:20.04. 10.1 (armhf) 1.0.2+dfsg- 4build1 (amd64)
python-
update-
mu-editor/
python-b2sdk failure is due to a segfault after its test suite has completed, not related to this update
update-manager is again the same style error as above
mu-editor appears to be a timeout, likely a transient failure
Failures:
elpy/1.32.0-2 (amd64)
Are transient (timeout in profiling), a manual re-run succeeded https:/ /autopkgtest. ubuntu. com/packages/ e/elpy/ focal/amd64