[05:28] <zhsj> please retry the build https://launchpad.net/ubuntu/+source/acmetool/0.2.2-1
[08:25] <mwhudson> zhsj: done
[08:26] <zhsj> mwhudson: thx
[08:27] <danilogondolfo> Hi there, looking for a friend to trigger this test for me :) https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=sudo&ppa=danilogondolfo/sudo&trigger=sudo/1.9.13p1-1ubuntu1
[09:07] <mwhudson> danilogondolfo: done
[09:08] <danilogondolfo> thank you!
[10:37] <GunnarHj> Hi zhsj! How confident are you about the pkgbinarymangler MR? Is it ready to be uploaded without a review of xnox or cjwatson?
[10:37] <GunnarHj> https://code.launchpad.net/~zhsj/+git/pkgbinarymangler/+merge/437569
[10:38] <zhsj> GunnarHj: at least not bad than before (no test is dropped, and a new test is added). the regression in debhelper for ppa could be treated separately.
[10:39] <zhsj> so i would say it could just be uploaded.
[10:39] <GunnarHj> zhsj: Great, then I'll do that to move things forward.
[10:39] <zhsj> GunnarHj: thx
[10:52] <zhsj> hmm, could someone give back acmetool on riscv64 again. (Unable to connect to ftpmaster.internal:80: [IP: 10.131.66.192 80]) not sure if launchpad will do it self when the build ends in given-back status.
[10:57] <GunnarHj> zhsj: Done.
[10:57] <zhsj> GunnarHj: thx again :)
[10:57] <cjwatson> Launchpad will only automatically retry certain builds in the "Dependency wait" state
[10:57] <cjwatson> (though if there's been a systematic infrastructure failure of some kind, staff will sometimes bulk-retry affected builds manually)
[11:21] <danilogondolfo> Hi again, looking for a reviewer/sponsor for a merge: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698
[11:21] -ubottu:#ubuntu-devel- Launchpad bug 2007698 in sudo (Ubuntu) "Please merge 1.9.13p1-1 into lunar" [Undecided, New]
[11:21] <danilogondolfo> appreciate if someone has a moment to take a look
[11:31] <GunnarHj> danilogondolfo: Shouldn't ubuntu/lunar or ubuntu/devel (not sure why both exist) be the target branch?
[11:39] <danilogondolfo> GunnarHj, so, the MR is the diff between debian/sid and ubuntu/devel, it's basically applying our changes on top of the original debian package (the merge process is new to me so bear with me please :) I might be doing something wrong hehe). And in this case I guess we are not really merging it, the MR is easier to review though.
[11:40] <danilogondolfo> are the steps followed by the sponsor/uploader documented somewhere?
[11:51] <GunnarHj> danilogondolfo: Since it's sudo, I wasn't really going to sponsor it. Think that should be done by someone in the foundations team. Just happened to see the thing with an assumingly wrong target branch. Maybe it doesn't really matter.
[11:56] <danilogondolfo> right. I mean, if the target branch were ubuntu/devel the merge would actually conflict because it contains changes already present there
[12:23] <GunnarHj> danilogondolfo: OTOH, the changes in the debian/ folder between two releases is also an important check point when reviewing a merge.
[14:02] <MacSlow> Greetings everybody!
[14:24] <MacSlow> brb
[14:30] <tobhe> hi, can someone help me classify the error message in https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#libunwind
[14:31] <tobhe> it looks like /bin/sh: 1: python: not found is what causes ubuntu-regression-suite FAIL badpkg so I'm inclined to say this is not related to libunwind at all, but i might be missing somethign
[14:33] <seb128> tobhe, right, it sounds like an issue in the corresponding linux packages or whatever is providing ubuntu-regression-suite
[14:35] <MacSlow> hey seb128, ogra!
[14:35] <ogra> hey hey
[14:35] <seb128> hey MacSlow!
[14:36] <tobhe> seb128: thx! what do I best do with that? can you restart the test to see if it works better on the second try or do I better just comment on the bug?
[14:36] <tobhe> that would be https://bugs.launchpad.net/ubuntu/kinetic/+source/libunwind/+bug/2004039
[14:36] -ubottu:#ubuntu-devel- Launchpad bug 2004039 in libunwind (Ubuntu Kinetic) "libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes" [Undecided, Fix Committed]
[14:37] <seb128> tobhe, the first thing to try would be to retry with a trigger=migration-reference/0
[14:37] <seb128> retry those packages that fail I mean
[14:37] <seb128> if that also fails it will stop considering as a regression from the proposed version
[14:38] <tobhe> sounds good. I don't think I'm allowed to trigger that retry though
[14:57] <danilogondolfo> May I ask someone to trigger this test for me, please? https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=glibc&trigger=glibc/2.37-0ubuntu1&trigger=libgd2/2.3.3-7ubuntu2
[15:03] <ginggs> danilogondolfo: .
[15:04] <danilogondolfo> ginggs: thanks!
[18:45] <MacSlow> bbl
[21:04] <enr0n> Can a core dev please retry the following autopkgtest? https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=crash&trigger=software-properties%2F0.99.32. The test looks flaky recently.
[21:07] <mwhudson> enr0n: done
[21:07] <enr0n> mwhudson: thanks!