[07:10] <mitya57> arraybolt3: thank you! I did not find that package somehow.
[07:11] <mitya57> A wishlist for future, it would be nice to make it consistent with Debian eventually.
[14:17] <rbasak> git-ubuntu is published in edge for arm64, armhf, ppc64el and s390x now. riscv64 is still building. It passes the as-installed snap self-test for arm64. For those developing on these arches, please test!
[15:56] <arraybolt3> Is there a simple way to skip running pkgstripfiles PNG optimization when I build a package using sbuild? I like the solidity of builds done using sbuild but hate that anything with a PNG in it takes like a minute longer to build (sometimes many minutes if there are lots of PNGSs).
[15:56] <arraybolt3> *PNGs
[15:59] <rbasak> I wonder if it responds to noopt
[16:05] <rbasak> !dmb-ping
[16:05] <ubottu> bdmurray, bdrung, rbasak, schopin, teward, tsimonq2, utkarsh2102: DMB ping
[16:06] <bdrung> schopin apologized for missing the meeting
=== okgxiukfxedaomwk is now known as jljpehjvotioojhp
=== jljpehjvotioojhp is now known as georgiag
[17:06] <asciiwolf> Hi! I have prepared a Stable Release Update for the "chirp" package for Ubuntu 24.04. This package crashes on launch on Ubuntu 24.04 because of a regression caused by refactoring.
[17:06] <asciiwolf> The fix is an one line change that is already present in latest CHIRP stable release. Here is the SRU ticket (with debdiff for Noble): https://bugs.launchpad.net/ubuntu/+source/chirp/+bug/2071563
[17:06] -ubottu:#ubuntu-devel- Launchpad bug 2071563 in chirp (Ubuntu) "[SRU - Noble] Backport crash fix" [Undecided, New]
[17:07] <ahasenack> asciiwolf: do you need sponsoring?
[17:07] <ahasenack> looks like
[17:07] <asciiwolf> Correct! :-) I am looking for someone to sponsor this SRU and upload it into noble-proposed.
[17:07] <ahasenack> and looks like I forgot to remove myself from the #topic as patch pilot, uhoh
[17:07] <ahasenack> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Feature Freeze, UI Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: N/A
[17:08] <ahasenack> I see the bug in the report: http://sponsoring-reports.ubuntu.com/general.html
[17:09] <ahasenack> so should be good for picking up
[17:09] <asciiwolf> Great, thanks a lot! :-)
[17:10] <rbasak> <insert pilot jumping out of aircraft leaving passengers behind meme>
[17:11] <rbasak> (but more seriously, the patch pilot programme is pretty good now so it should be picked up soon)
[17:11] <rbasak> If it's not, then please do ping here.
[17:14] <asciiwolf> Will do, thanks again!
[18:29] <doko> arraybolt3: remove the pkgbinarymangler
[18:48] <arraybolt3> doko: I don't know what that is or where I'd remove it from.
[18:52] <ginggs> arraybolt3: export NO_PKG_MANGLE=1
[18:52] <ginggs> in debian/rules
[18:53] <arraybolt3> ah, ok, thank you!
[18:55] <ginggs> if you are building locally, you can do: apt remove pkgbinarymangler
=== lesbraz is now known as sbraz
=== not_phunyguy is now known as phunyguy
=== arif-ali_ is now known as arif-ali
=== lucyllewy_ is now known as lucyllewy
=== lool_ is now known as lool
=== kenyon_ is now known as kenyon
=== Rubennn7 is now known as Rubennn
[19:50] <arraybolt3> Weird thing is pkgbinarymangler isn't even installed on my builder VM
[20:30] <adrien_> interesting tidbit btw: I recently found out that pkgbinarymangler doesn't run for PPAs which will lead to different behavior compared to normal archive builds :)
[20:31] <ahasenack> that's true
[20:31] <ahasenack> I encountered that in an SRU review that was dealing with pkgbinarymangler, and couldn't verify the intended behavior in a ppa
=== gusnan_ is now known as gusnan
[20:36] <liushuyu> ubuntu-sru: Is there anyone available to review https://bugs.launchpad.net/ubuntu/+source/dh-cargo/+bug/2028153?
[20:36] -ubottu:#ubuntu-devel- Launchpad bug 2028153 in dh-cargo (Ubuntu) "[SRU] dh-cargo: Backport vendored dependencies support to Jammy" [Medium, Confirmed]
[20:40] <mfo> liushuyu, hey o/ i'll add it to the list, but I may not be able to handle it today.
[20:43] <liushuyu> mfo: Thanks!