Unfortunately bileto decided to rate all tests as "always failed" and due to that doesn't even link the result to check it on our own :-/ Usually those are direct links to the logs with keys and tokens in the URL, I doubt that we can recover that easily.
The actual merge LGTM thou.
(Not part of the merge): dpkg-shlibdeps seems to have some issues with this.
Could you take a look at "dpkg-shlibdeps: warning:" in the build log and check if that is a yet to be discovered problem or not?
+1 on the merge, maybe run some tests in local qemu before uploading ?
Unfortunately bileto decided to rate all tests as "always failed" and due to that doesn't even link the result to check it on our own :-/ Usually those are direct links to the logs with keys and tokens in the URL, I doubt that we can recover that easily.
The actual merge LGTM thou.
(Not part of the merge): dpkg-shlibdeps seems to have some issues with this.
Could you take a look at "dpkg-shlibdeps: warning:" in the build log and check if that is a yet to be discovered problem or not?
+1 on the merge, maybe run some tests in local qemu before uploading ?