[08:21] <ginggs> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: ginggs
[09:51] <jbicha> could someone with a script retry the oracular riscv64 builds from about 3 days ago? there were a lot of failed builds with no logs then
[10:29] <ginggs> jbicha: doing...
[10:50] <ginggs> 449 builds without logs given back
[10:51] <ginggs> mostly riscv64, but a handful on the other architectures as well
[11:07] <waveform> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: waveform, ginggs
[11:08] <ginggs> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: waveform
[11:08]  * ginggs steps out of the plane for a breath of fresh air
[11:10] <ginggs> i'm not suggesting that waveform smells funny
[11:10]  * waveform looks at his socks...
[11:47] <bdrung> ginggs, opening a window on the plane wasn't an option?
[12:02] <nteodosio> waveform, a simple patch you might like to sponsor: https://code.launchpad.net/~hsbasu/update-manager/+git/update-manager/+merge/465575
[12:08] <waveform> nteodosio, looks good and I see it's got a couple of approvals already but that's a package in main (I'm only MOTU) so that'll have to wait for another sponsor
[12:09] <waveform> However, I do see it on the sponsorship list (although it's a fair way down because it's grown a bit in the last few weeks), so it won't be forgotten about but the best I can do for now is to try and clear out the stuff above it
[12:11] <nteodosio> waveform, I see the corresponding bug has ubuntu-sponsors subscribed, it's just a small improvement so it can certainly wait.
=== tom-tom-0 is now known as tom-tom-324
=== tom-tom-324_ is now known as tom-tom-324
[15:46] <waveform> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: N/A
[17:12] <asikrom> Hi all, I am a prospect/wannabe-maintainer who would like to contribute bug fixes. LP #2063936 might be a good first (SRU) candidate.
[17:12] -ubottu:#ubuntu-devel- Launchpad bug 2063936 in merkuro (Ubuntu) "[noble] merkuro-calendar fails to start" [Undecided, New] https://launchpad.net/bugs/2063936
[17:12] <asikrom> Initially I attached a plain diff to the report, but to be more useful I understand I also need to provide an entry in debian/changelog, provide test steps for reviewers, and maybe submit the work in the form of a merge proposal instead of a patch/diff file.
[17:12] <asikrom> However, it is unclear to me whether I should use quilt, how to bump the pkg version properly, which branch to checkout + commit to, and which info is expected in merge prop texts.
[17:13] <asikrom> Web searches mainly lead me to the GitWorkflow wiki page (parts of which appear irrelevant as merkuro is not in Debian), and the WIP pkging guide which does not have the info I need yet.
[17:13] <asikrom> Would anybody be willing to mentor me through the process?
[17:13] <asikrom> I promise I will pay attention and try to be more useful next time.
[18:14] <asikrom> Guess not. I will try again another day.
[19:09] <john-cabaj> vorlon: I see there's a new ZFS release upstream. Does the LTS release usually keep with these releases, or are they generally locked to the GA release version?
[21:49] <vorlon> john-cabaj: https://launchpad.net/ubuntu/+source/zfs-linux shows that we largely stay with the GA release version; there may be reasons for SRUs but they don't fall under a general exception policy