[04:47] <zhsj> could someone help retry these autopkgtests https://paste.ubuntu.com/p/Jb9Hmv9R9P/
[04:48] <zhsj> and retry these builds https://launchpad.net/ubuntu/+source/golang-github-containers-toolbox/0.0.99.3+git20230118+446d7bfdef6a-2
[06:57] <RAOF> Damnit! How do I get sbuild to build against lunar-proposed now?
[06:58] <arraybolt3[m]> RAOF (he/they): I know how :)
[06:58] <arraybolt3[m]> Hang on one moment...
[06:58] <arraybolt3[m]> ```
[06:58]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/003fc6bccf6dbfea89528a24d3711d165cb7da00
[06:58] <arraybolt3[m]> Notice the # Proposed enabler spot in my sbuildrc.
[06:59] <arraybolt3[m]> I have my fstab for sbuild modified like so:
[06:59] <arraybolt3[m]> uh... lemme find it...
[06:59] <RAOF> Launchpad still builds against -proposed, right? sbuild-launchpad-chroot doesn't set up a chroot with the necessary magic???
[06:59] <arraybolt3[m]> Launchpad still builds against it, yes.
[06:59] <arraybolt3[m]> It does so by apt pinning, which is what I'm doing.
[06:59]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/6f673b608a2df8e2f4c953a87e418eb1185d4320
[07:00] <arraybolt3[m]> I have a directory bind-mounted in sbuild that holds my enable-proposed script.
[07:00] <arraybolt3[m]> And then the script itself is just:
[07:00]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/e64e64eec6af0fa022867a1cfcf49258dbac0f9b
[07:00] <arraybolt3[m]> Once all that's in place, sbuild will build against -proposed.
[07:01] <arraybolt3[m]> RAOF (he/they): According to an email sent out by paride, "schroots
[07:01] <arraybolt3[m]> created by mk-sbuild and sbuild-launchpad-chroot may have -proposed in
[07:01] <arraybolt3[m]> sources.list, but that's not going to be used in >= Lunar."
[07:02] <arraybolt3[m]> So no, sbuild-launchpad-chroot doesn't do it, but the above hack should.
[07:02] <arraybolt3[m]> ¯\_(ツ)_/¯
[07:02] <RAOF> Seems like sbuild-launchpad-chroot should do it :P
[07:06]  * RAOF should set up a public LXD image server with preconfigured images for sbuild.
[07:07] <arraybolt3[m]> Heh, that would be handy. Oy, I didn't think about the fact that this was designed for schroot, not lxd - no clue how to make lxd work with it.
[07:33] <arraybolt3> This is just because I'm curious, but why do autopkgtests take *so long* on Canonical's infra? I can run an autopkgtest locally in ~5 minutes, maybe less, and it takes hours or even days in the cloud.
[07:34] <arraybolt3> (I guess more because I'm curious and a bit frustrated :P)
[07:34] <arraybolt3> (And yes, it depends on the autopkgtest, but ones that take ~5 minutes or less take hours or days in the cloud.)
[08:00] <ginggs> arraybolt3: which package in particular?
[08:10] <arraybolt3> ginggs: Mainly lxqt-sudo and lxqt-policykit, I believe.
[08:12] <arraybolt3> lxqt-sudo appears stuck on an autopkgtest for lubuntu-update-notifier, which is a very fast autopkgtest locally, but apparently has managed to tie up lxqt-sudo for two days.
[08:12] <arraybolt3> Then again I remember now that there were some outages recently so maybe I'm just seeing the results of the system still recovering from that.
[08:22] <ginggs> arraybolt3: lxqt-sudo doesn't seem to have an autopkgtest, but i see it
[08:22] <ginggs> it's waiting for an autopkgtest for lubuntu-update-notifier
[08:22] <arraybolt3> Exactly.
 "Heh, that would be handy. Oy..." <- You'd use `sbuild`'s autopkgtest backend.
[08:23] <ginggs> so 'test in progress' on the update_excuses page means the test is in the queue
[08:23] <ginggs> you can see it here https://autopkgtest.ubuntu.com/running
[08:24] <arraybolt3> Oh, but it's not actually actively running, it's just scheduled to run.
[08:24] <ginggs> lubuntu-update-notifier {"triggers": ["lxqt-sudo/1.2.0-1ubuntu1"], "submit-time": "2023-02-17 09:39:16"}
[08:24] <arraybolt3> For some reason I thought it was taking hours or days just to run :P
[08:24] <ginggs> only days before it actually runs
[08:24] <ginggs> https://autopkgtest.ubuntu.com/packages/lubuntu-update-notifier/lunar/arm64
[08:24] <arraybolt3> :facepalm: I even know about that page, I don't know why I didn't check it.
[08:25] <ginggs> ^ shows it doesn't take very long when it actually runs
[08:25] <arraybolt3> That makes sense.
[09:01] <paride> arraybolt3, hi, maybe you found it out already, but here is the bug about sbuild-launchpad-chroot not using proposed with lunar: https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1996205
[09:01] -ubottu:#ubuntu-devel- Launchpad bug 1996205 in sbuild-launchpad-chroot (Ubuntu) "-proposed schroots not really using -proposed in >= Lunar" [Undecided, New]
[09:03] <arraybolt3> Thanks!
[13:22] <mitya57> sil2100: Hi! Bileto gives me 500 today (from https://bileto.ubuntu.com/v2/metadata for example).
[13:22] <sil2100> ah, carp, I was supposed to ask IS to power-cycle it
[13:27] <mitya57> Thank you.
[17:03] <MacSlow> Greetings everybody!
[18:17] <mitya57> sil2100: and now it seems to work, thanks again!
[19:03] <rbasak> !dmb-ping
[22:19] <MacSlow> re