[01:47] <teward> paride: fyi RE: #1992653 it's reproducible as written by you on Jammy amd64.  I don't have any bare metal Kinetic amd64 so unless a VM would be sufficient for testing I'm not going to be able to provide much better.  (just an FYI)
[02:18] <teward> paride: confirmed also in a Kinetic VM on the Jammy amd64 hostl
[02:18] <teward> same steps as you except chrooting into the chroot explodes
[02:18] <teward> (fresh VM install too)
[08:33] <paride> teward, interesting, thanks
[09:17] <paride> I just tried again and again it worked fine for me. Also tried on another machine using a Kinetic VM and still worked
[09:17] <paride> commented to the bug
[10:26] <caribou> rbasak: Hi, given the Final Freeze, this means that the upload for LP: #1992454 will have to wait ?
[10:26] -ubottu:#ubuntu-devel- Launchpad bug 1992454 in iptables (Ubuntu Kinetic) "iptables: segfault when renaming a chain" [Undecided, In Progress] https://launchpad.net/bugs/1992454
[10:35] <caribou> iptables beings seeded
[10:43] <seb128> caribou, hey. It's a freeze, you can always upload, there is just a queue the upload might not be accepted from
[10:44] <seb128> caribou, you can make your case on  #ubuntu-release about why it should be accept in the release, we haven't got ISOs yet and there will be probably be respin early next week still
[10:45] <seb128> caribou, also if there is a bug reference and it's not accepted for the release it can then still be accepted as a SRU and kept in proposed until kinetic is out (and be released as a 0 day SRU if needed)
[11:03] <rbasak> Sorry I missed your update.
[11:04] <rbasak> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2022-October/001324.html says we can upload, just like Seb says
[11:04] <rbasak> DId you check that the test actually runs in the latest version please?
=== mfo_ is now known as mfo
[12:00] <caribou> rbasak: let me double-check but last I ran, it only ran once including the new test
[12:13] <caribou> rbasak: FYI I just updated the bug with the latest autopkgtest run
[12:13] <rbasak> Thanks!
[12:13] <rbasak> Looking
[12:21] <rbasak> Sponsored. Thanks!
[12:32] <caribou> Great thanks! I have the debdiffs ready for the SRUs
[12:42] <rbasak> Personally I'm a little reluctant to sponsor SRUs immediately because the upstream commit hasn't seen a release yet, AFAICT. I'd want to review the patch more thoroughly, or let some time pass for any issues to become known. Especially given that this bug has presumably existed for years users without issue. Breaking iptables would be bad!
[13:12] <caribou> rbasak: that's not what I meant. Just wanted to let you know that they were ready.
[13:13] <caribou> I don't think it's advisable to rush things in : there is a workaround for that on our side so we have time
[13:28] <rbasak> caribou: sorry I didn't mean to imply that you're rushing. It's fine and apprpropriate to have the SRUs ready - thanks :)
=== justHaunted is now known as ffffffradiofree
=== ffffffradiofree is now known as jusFffffffradiof
=== jusFffffffradiof is now known as justThumbs
=== justThumbs is now known as justVain
[20:42] <bdmurray> tsimonq2: I thought you'd mentioned working on a ubiquity fix yesterday. Did you get anywhere?
[22:16] <tsimonq2> bdmurray: I did, but ran out of open source time. I passed along all of my findings to Eickmeyer.