[01:12] <Eickmeyer> bryceh: Just saw the most recent update on argyll. Just for clarification, is the point there to proceed forward with that MIR? It's part of the ubuntustudio packageset, so that's why it has my attention.
[05:53] <bryceh> Eickmeyer, I ran across it as part of my +1 duty this week.  So my motive was just to get the MIR connected to the migration issue via an update-excuse bug.
[05:55] <bryceh> Eickmeyer, RAOF is probably the person worth consulting here; he had enabled argyll in colord on the debian side.
[07:02] <arraybolt3> Is there any place where people coordinate who's working on what parts of proposed-migration clusters? I was going to see if I could get bpython to work right but would rather avoid that if someone else is already working on it.
[07:08] <arraybolt3> It looks easy enough, so I'm just going to dive in and go for it.
[07:09] <Skuggen> rbasak: Looks like there's some useragent blocking in place. Tested with --useragent="Safari/602.1" as a workaround and was able to fetch the files
[07:16] <arraybolt3> Uh... tar. I've hit a bit of a problem.
[07:16] <arraybolt3> Now that NotAutomatic is set for Lunar -proposed, I'm not able to reproduce the bpython build failure locally.
[07:17] <arraybolt3> I know I could use apt pinning to work around it in my source schroot, but I don't want to do that to my source schroot.
[07:18] <arraybolt3> And changing my non-source schroot obviously results in any changes vanishing upon exit :P so that doesn't work.
[07:19] <arraybolt3> Bah. I'll just do this manually without using sbuild directly.
[07:21] <arraybolt3> Actually... wait just a minute, what if I hack the local PPA directions into an "enable proposed" script...
[07:27] <arraybolt3> I think this is going to work.
[07:37] <arraybolt3> IT WORKS!
[07:37] <arraybolt3> I have a way of enabling -proposed on lunar within sbuild.
[07:38] <arraybolt3> Frustratingly, the autopkgtest for bpython is still passing locally though >_<
[07:50] <arraybolt3> lol, ok so it works but doesn't do what I want at all, so... now I learn how to use autopkgtest manually :P
[07:59] <arraybolt3> Alright... so bpython is already fixed. Ha ha. Thus why I can't reproduce the problem.
[07:59] <arraybolt3> But hey, I learned a lot.
[12:28] <bluca> enr0n: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992178 was fixed with a workaround in autopkgtest, but we are still seeing the crashes
[12:28] -ubottu:#ubuntu-devel- Launchpad bug 1992178 in systemd (Ubuntu) "autopkgtest: upstream tests that run in qemu hang on ppc64el" [Medium, Fix Released]
[12:29] <bluca> this only happens on ppc64el, and only on ubuntu (not seen on fedora)
[12:29] <bluca> there's a corrupted pointer that somehow appears
[12:29] <bluca> we suspect a toolchain issue
[12:29] <bluca> lots of details here: https://github.com/systemd/systemd/issues/25091#issuecomment-1401824195
[12:29] -ubottu:#ubuntu-devel- Issue 25091 in systemd/systemd "Spurious assertions in the ppc64el Ubuntu Jammy job" [Open]
[12:29] <bluca> can I reopen that bug and get some help from a ppc expert please?
[12:29] <bluca> none of us speak ppc assembly
[12:41] <rbasak> Skuggen: thanks - I can work around for now then. But could you follow up internally please, so that it does work?
[12:58] <Skuggen> Yeah, I've sent a query about it
=== diddledani_ is now known as diddledani
=== frickler_ is now known as frickler
[13:56] <ahasenack> sru team, I have a question. update-notifier in bionic has the autoconf generated files (configure, etc) in the source package
[13:56] <ahasenack> but in later releases they are autogenerated at build time using ./autogen.sh
[13:57] <ahasenack> there is a branch making the same change to bionic, so that it also generates those files at build time
[13:57] <ahasenack> but done today, the generated files are different than the ones that are part of the source package
[13:57] <ahasenack> I think there is risk in there, as it's hard to interpret the diff
[13:58] <ahasenack> you know what a configure file looks like
[13:59] <ahasenack> the situation is that the bionic package in the archive currently builds fine, but the bionic branch in the upstream project already does not have the generated files checked in, and is an ftbfs (see https://bugs.launchpad.net/bugs/1999897)
[13:59] -ubottu:#ubuntu-devel- Launchpad bug 1999897 in update-notifier (Ubuntu) "bionic upstream branch fails to build: missing autoconf files" [Undecided, New]
[13:59] <ahasenack> the less risky option I think is to just grab the generated files from the bionic package currently in the archive and check them in
[13:59] <ahasenack> but that's a hammer, and I can see the appeal to just use ./autogen.sh as it's done in all other ubuntu releases in this update-notifier package
[13:59] <ahasenack> opinions?
=== leftyfb_ is now known as leftyfb
[14:24] <enr0n> bluca: hey, yeah I was out last week but saw lots of updates on the upstream bug. I'll poke around internally to find out who can help on the ppc specifics.
=== bdmurray_ is now known as bdmurray
[14:35] <bluca> thanks, can I reopen the launchpad ticket?
[14:35] <bluca> or should I open a new one?
[14:44] <enr0n> bluca: I think for now I'll just add a jammy task to the bug. I don't think we need a separate bug, but it's not quite right to "re-open" for kinetic either
[14:47] <bluca> ok
[15:16] <waveform> mwhudson, if you want to try uploading it, the diff against unstable is in LP: #2003201 but sbuild's in main :)
[15:16] -ubottu:#ubuntu-devel- Launchpad bug 2003201 in sbuild (Ubuntu) "Please merge sbuild 0.85.0 from Debian unstable." [Undecided, New] https://launchpad.net/bugs/2003201
[15:45] <ginggs> waveform: you should become a core dev
=== genii_ is now known as genii
=== pizzaiolo is now known as pizza
[22:53] <bdmurray> bryceh: How do I use this new tool to run an autopkgtest for a package I just uploaded to my ppa?
[23:22] <bryceh> bdmurray, ppa tests -r <release> <ppa-name>
[23:22] <bryceh> bdmurray, what ppa are you testing?
[23:24] <bdmurray> I already ended up running the test manually
[23:34] <bdmurray> bryceh: Oh actually I could run through the process for another release too. Are all the steps (upload, wait, test) documented somehwere?
[23:42] <bryceh> bdmurray, the README has a run-thru of the commands, although it may be a bit terse
[23:42] <bryceh> I'm in process of adding --help text for each of the commands but in the current release that's a bit hit or miss (more miss)
[23:44] <bryceh> bdmurray, if you find friction in any particular steps, please file a bug (https://bugs.launchpad.net/ppa-dev-tools) and I'll prioritize that for the next release.
[23:46] <bdmurray> bryceh: and should I install the snap or use the git branch?
[23:49] <bryceh> @bdmurray, your preference.  snap will upgrade automatically when next release is out, so is better if you want a stable experience.  git will of course get my latest changes