Hello Steve McIntyre, As you might have noticed I've taken the liberty to NMU strace into *experimental*.
I've done so based on my past experience that strace can have many architecture specific problems, to give me a picture of what the situation is for the latest upstream 6.1 release. (And since it's experimental we have the posisibily to just RM it and act like it never happened.) It seems like mips* has test failures (as usual?!). I've filed https://github.com/strace/strace/issues/235 with my limited conclusions about the issues. Given that strace has not been updated for the entire release cycle and that it's currently RC-buggy, I think it would be useful to try to update it before the 12 Feb freeze. The time window is however very small. Additionally ppc64el seems to have a huge build backlog, so if we want to make it during the limited time window before the freeze we can't wait for the results. (I could possibly build on a ppc64el porterbox to see if I can spot any problems there.) I would like to know what you think about a potential NMU of strace 6.1 to unstable at this point. Probably with mips* tests set to not fail the build (`|| true`). Possibly the same for ppc64el just to make sure it doesn't give any surprises once it finally builds (and the upload is old enough to migrate to testing). If I'm going to do the NMU I'll need to proceed very soon so your input on this would be very appreciated if you could give it ASAP! What do you think? Regards, Andreas Henriksson
