[03:44] <liushuyu> Hi, can someone help me retry some autopkgtests? The links follow:
[03:44] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=armhf&package=django-sass-processor&trigger=django-sass-processor%2F1.2.2%2Brepack-1
[03:44] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libtest2-harness-perl&trigger=migration-reference/0
[03:44] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=dcfldd&trigger=dcfldd%2F1.9-1
[03:45] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=jruby&trigger=ruby-rspec%2F3.12.0c0e1m1s0-1
[03:45] <liushuyu> --- end of links. Thank you in advance!
[04:26] <amurray> liushuyu: .
[04:27] <amurray> liushuyu: done
[04:27] <liushuyu> amurray: Thank you!
[04:27] <amurray> yw :)
[07:17] <adrien> hey, I'm not sure this is the best place to ask; I have two PPA armhf builds that can be killed ( https://launchpad.net/~adrien-n/+archive/ubuntu/ghc-llvm-backend-s390x/+builds?build_state=building ) if resources are needed
[07:39] <ginggs> adrien: i think only launchpad-buildd-admins can kill other people's builds, so try # launchpad?
[07:40] <laney> if it's your own build, there should be a 'cancel build' button on the build page
[07:42] <adrien> oh, you're absolutely right; I really had troubles spotting it but it's there
[07:42] <ack> hi, anyone happens to know whether building a python package via pyproject.toml should work in 22.04?
[07:42] <adrien> and I'll remember to ask in #launchpad instead for such things in the future
[13:14] <seb128> bdrung, hey, thanks for the apport merge. Do you have other changes pending/plan an upload? if not I will do one since I would like to see the hook update in place
[13:20] <bdrung> seb128, i expect a new upstream release very soon (this or next week).
[13:25] <seb128> bdrung, I would like the hook to be in place before the long week and the upload isn't expensive, is that ok if I push a new revision to lunar with that today?
[13:50] <seb128> bdrung, in fact it can wait, talking to the Dan we need a similar change in subiquity also since the crash reports are generated from it and not using the apport hook
[13:51] <dbungert> while people can report bugs through a more traditional apport flow, it appears that most Subiquity bugs are genereated by the reports that Subiquity creates by using the apport python module
[13:52] <dbungert> so I intend to recreate Seb's change there, but we also need to fix the comically out of date subiqutiy apport hook
[13:54] <rbasak> xnox: sorry, I thought the email notification would be sufficient. I'll leave an annotation next time.
[23:18] <bdmurray> We were having different issues with the bos01 workers (fun!) and I've disabled them now. So if there is something that you think needs retesting on arm64, s390x or ppc64el now is the time.