=== cpaelzer_ is now known as cpaelzer
[07:34] <schopin> sudip: re the version number thing, IMHO consistency is well worth the extra keystrokes ;)
[07:45] <sudip> schopin: I slept on it and now I can think of another reason why suggested version numbers in the wiki are safe and mine are unsafe, can potentially cause problem. maybe not in this package, but there can be other packages where this can lead to a future problem
[07:45] <sudip> waveform: I will update the debdiff
[10:44] <adrien> a short status about openssl 3.2: I'm working on it; I was off for a few days and before that I hit a snag due to the way packages had been uploaded to unstable
[10:45] <adrien> since I can't merge through git, I'm going in depth through the current delta and it's taking a bit more time but it's probably worth it
[11:13] <schopin> adrien: are you saying that the DDs maintaining openssl somehow broke git-ubuntu?
[11:24] <adrien> g-u hasn't been broken: all the versions are imported correctly, but the branch tips have sometimes been force-pushed
[11:26] <adrien> and the result is some disjointment which makes merging/rebasing meaningless (we "went" on one branch with 3.0.x during noble while unstable went on another branch)
[12:03] <rbasak> schopin: the issue is that packaging development for openssl in Debian was apparently non-linear. git-ubuntu created a commit graph according to what debian/changelog said each upload was based on, but that results in some confusion since it means the progression of debian/sid (for example) is non-linear and therefore was "force pushed" along the way.
[12:20] <adrien> git-ubuntu did the right things and did that very well, even extracting actual meaning out of the various uploads that all happened in unstable
[12:21] <adrien> and overall it's not a big issue; the main aspect were the surprises and needing time to realize that it wasn't a situation I could really use "git" as usual (well, without making weird things)
[14:15] <Eickmeyer> Any chance I can get a core-dev to look at bug 2067338 and sponsor? It's a nasty MIDI bug in PipeWire only present in noble with an easy fix, debidff all ready to go.
[14:15] -ubottu:#ubuntu-devel- Bug 2067338 in pipewire (Ubuntu Noble) "Long SysEx messages are skipped by Midi-Bridge" [High, In Progress] https://launchpad.net/bugs/2067338
[16:27] <rbasak> Could someone moderate u-d-a@ for me please. Who can still do this? bdmurray maybe?
[16:45] <Eickmeyer> rbasak: It probably wouldn't be a horrible idea to post in Discourse under Community as well (thinking that's the only appropriate category since it's an election).
[18:11] <rbasak> Eickmeyer: good idea - thanks!
[18:11] <Eickmeyer> rbasak: yw
[18:19] <rbasak> (done)
[18:20] <arraybolt3> not going to be applying for that this year - maybe once I get Core Dev (if that ever happens).
[19:05] <Eickmeyer> rbasak: I can't move it to announcements, but I know others who can. Rejected your flag because it requires either a delete or other disciplinary action, for lack of a better term. XD
[19:05] <rbasak> Eickmeyer: OK thank you for looking. I tried to post it directly in Announcements but it didn't let me.
[19:06] <Eickmeyer> Right, requires admin or higher. I posted in the Staff category requesting someone with a better pay grade than me move it.
[19:06] <arraybolt3> lol @ disciplinary action XD
[19:08]  * rbasak is looking forward to being "disciplined" :-P
[19:08] <Eickmeyer> HAHAHAHAHA
[19:08] <rbasak> seb128 and athos: scroll up for Eickmeyer's sponsorship escalation request please - bug 2067338 - asking you both because you're scheduled to patch pilot tomorrow? Thanks!
[19:08] -ubottu:#ubuntu-devel- Bug 2067338 in pipewire (Ubuntu Noble) "Long SysEx messages are skipped by Midi-Bridge" [High, In Progress] https://launchpad.net/bugs/2067338
[19:17] <Eickmeyer> rbasak: Aaron Prisk has moved it to announcements and pinned it.
[19:18] <rbasak> Thanks to both!
[19:19] <Eickmeyer> rbasak: You're quite welcome. Glad to help out!
[19:20] <seb128> Eickmeyer, rbasak, I can handle that one tomorrow morning if nobody else does it before
[19:25] <rbasak> Thanks!
[19:33] <Eickmeyer> seb128: Thanks!
[20:07] <athos> thanks, seb128! rbasak, thanks for the heads-up! I will not be around tomorrow. I forgot to update the schedule. I will push my shift to next week :)