=== arraybolt3_ is now known as arraybolt3
=== guiverc2 is now known as guiverc
[16:07] <Eickmeyer> bdrung: So... audacity... s390x... yikes.
[16:18] <arraybolt3[m]> Eickmeyer: Audacity on s390x?!?!?!?! /me thinks maybe that architecture shouldn't be an Audacity build target, since I don't think those things even have GUIs
[16:19] <Eickmeyer> arraybolt3[m]: Debian still wants it to build there if possible.
[16:20] <Eickmeyer> On Ubuntu, we don't care as much, but Debian is a bit more pedantic about that sort of thing.
[16:20] <Eickmeyer> Especially if it built there before.
[16:22] <arraybolt3[m]> :(
[16:23] <arraybolt3[m]> I guess it will come in handy the fateful day that Audacity has a headless mode, or a gamer and hardware developer gets their hands on an IBM mainframe.
[16:44] <JanC> you can run X11 on s390x, don't need a creen attached to it...
[16:44] <JanC> *screen*
[16:54] <tumbleweed> s390x is the only big-endian arch left, so it gets to catch all the endian bugs
[17:17] <tsimonq2> vorlon: Heya, as TIL for dput I just wanted to draw your attention to bug 1991569 whenever you're able to take a look. Thanks.
[17:17] <ubottu> Bug 1991569 in dput (Ubuntu) "Promote python3-paramiko to Recommends in the Ubuntu delta" [Medium, New] https://launchpad.net/bugs/1991569
[17:33] <vorlon> tsimonq2: I don't think TIL has much bearing here
[17:33] <tsimonq2> fair enough :)
[18:51] <utkarsh2102> !dmb-ping
[18:51] <ubottu> bdmurray, kanashiro, rbasak, seb128, sil2100, teward, utkarsh2102: DMB ping
[18:52] <utkarsh2102> Brian and Lukasz are out
[18:52] <utkarsh2102> are we still quorate?
[18:52] <rbasak> o/
[18:52] <teward> utkarsh2102: stuck in call with ceo and my boss at work - i'm jnavailable at this time
[18:52] <teward> ceo, my boss, and a partner.  unavailable.  *
[18:52] <utkarsh2102> teward: ok, thanks for letting us know! \o
[18:53] <seb128> utkarsh2102, I'm around
[18:53] <utkarsh2102> nice, kanashiro?
[18:53] <kanashiro[m]> o/
[18:54] <utkarsh2102> nice, 4 of us
=== popey0 is now known as popey
[20:05] <arraybolt3[m]> OK, so I just watched the DMB meeting, and watching the versioning stuff raised a question. Take the hypothetical example of coffegrinder 1.2.3-4ubuntu1 being bugfixed in Kinetic, Jammy, and Focal. I know that the version in Focal will be 1.2.3-4ubuntu1.20.04.1, and the version in Jammy will be 1.2.3-4ubuntu1.22.04.1... but what happens in Kinetic? 1.2.3-4ubuntu1.22.10.1? 1.2.3-4ubuntu2? Or 1.2.3-4ubuntu1.1? I think the second one
[20:05] <arraybolt3[m]> is right.
[20:05] <arraybolt3[m]> (This is assuming Kinetic is still in development, but knowing what will happen after it is released would also be handy.)
[20:06] <arraybolt3[m]> If there's a link to a doc that explains it, that would be best so I can refer to it later - https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation doesn't seem to give me the info I'm looking for.
[20:07] <arraybolt3[m]> (Heh, I misspelled coffeegrinder, missing an e. Blah.)
[20:09] <rbasak> arraybolt3[m]: nothing special for Kinetic - just follow the normal pattern. So it'd probably be 1.2.3-4ubuntu2. If after release, then it's the same as the SRU pattern because it'd be an SRU.
[20:10] <arraybolt3[m]> Makes sense, I just don't know for sure what "the normal pattern" is. I think it's 1.2.3-4 when synced from Debian, 1.2.3-4ubuntu1 for an upload in devel, then 1.2.3-4ubuntu2, etc. Is that right?
[20:10] <rbasak> Right! :)
[20:11] <arraybolt3[m]> Thanks :) (May as well do all the "cheating" now while I'm not the one getting grilled by the DMB, right?)
[20:11] <arraybolt3[m]> (Then I'll be ready when I am getting grilled.)
[20:11] <rbasak> That sounds like learning rather than cheating :)
[20:12] <arraybolt3[m]> True. :P
[20:12] <rbasak> It's not possible to cover everything in a DMB meeting. All I do is look at an application's specifics and try to intelligently probe to see if I'm satisfied.
[20:13] <rbasak> Often that means similar questions!
[20:13] <arraybolt3[m]> Makes sense. But this is the second time I've watched versioning eat someone's application, so I figure I may as well prep well in advance.
[20:14] <arraybolt3[m]> (It's really tricky to figure out.)
[20:14] <rbasak> Unfortunately there's a lot of arcanity in Ubuntu development :-/
[20:15] <rbasak> I'm trying to make that better with git-ubuntu. There's code that works out the correct SRU version for you, for example, and I want to add automatic linting and CI to flag it up. Then, when everyone's using that, it shouldn't need to be necessary knowledge any more. Because having to know this kind of thing sucks :-/
[20:15] <arraybolt3[m]> Oh wow, that sounds handy.
[22:42] <jbicha> yeah, it's not cheating. The meetings are intentionally public 😉
[22:43] <arraybolt3[m]> jbicha: I know, I was making a joke. Any way to learn this stuff is good. It's not a competition, we just want to make sure everyone knows what they're doing before they break things.