Hi Gabriele, On 23-08-2020 17:07, Gabriele wrote: > I believe this migration issue is caused by the build failure of > Austin on a couple of architectures. Unfortunately, I do not have the > means to debug on such platforms and therefore I am unlikely to be > able to provide a fix. Austin is guaranteed to work on the arm65, i368 > and amd64 architectures. If tests pass on other platforms that's a > bonus, but given that I cannot develop nor test on other platforms, I > cannot guarantee broader support. > > Please let me know if there's anything that I can do to address this issue. The simplest way (but not the nicest way) is to ask the ftp-master to remove the binaries from the architectures where the FTBFS happens. If you don't want this to happen you should prevent the builds on "unsupported" architectures. Another way is to use the porterboxes [1] to debug the situation on those architectures. A third way is to contact the porters of the failing architectures and ask for their help. Paul [1] https://wiki.debian.org/PorterBoxHowToUse
Attachment:
signature.asc
Description: OpenPGP digital signature