=== genii is now known as genii-meeting
=== genii-meeting is now known as genii
=== genii is now known as genii-core
=== DarkTrick_ is now known as DarkTrick
[12:52] <slyon> hey utkarsh2102! whats the status on bug #1958235 ? I just ran into it, too. Is there anything I can help with?
[12:52] <ubottu> Bug 1958235 in cmark-gfm (Ubuntu) "auto-synced transition to 0.29.0.gfm.2-1 left various packages behind broken" [Critical, Confirmed] https://launchpad.net/bugs/1958235
[12:54] <utkarsh2102> slyon: I'm uploading a fix soon.
[12:54] <utkarsh2102> will do within ~90 minutes, roughly.
[12:55] <slyon> ok, thank you! That's good to know
=== genii-core is now known as genii
=== ginggs_ is now known as ginggs
[16:37] <bdmurray> kanashiro: What is the status of ruby-defaults migrating?
[16:38] <kanashiro> bdmurray, we (server team) are going to get back to that today or tomorrow, some packages still do not support ruby 3.0
[16:39] <kanashiro> i.e. puppet
[16:45] <bdmurray> kanashiro: okay, thanks for the update
[16:46] <michagogo> Hi, quick question - how do MIRs and SRUs intersect?
[16:47] <michagogo> e.g. wrt bug #1935082, assuming I’m correct that the correct action would be adding the MIR’d package as a dependency of the Nvidia graphics drivers, would the correct course of action then be to SRU the graphics drivers in older releases to depend on the package as well?
[16:48] <ubottu> Bug 1935082 in egl-wayland (Ubuntu) "[MIR] egl-wayland" [Undecided, In Progress] https://launchpad.net/bugs/1935082
[17:01] <bdmurray> slyon: What importance should bug 1958284 have? I think we (Foundations) should do a better job of setting the importance of bug tasks.
[17:01] <ubottu> Bug 1958284 in systemd (Ubuntu Focal) "shutdown hangs at 'Waiting for process: ...' for 90s, ignoring DefaultTimeoutStopSec" [Undecided, Confirmed] https://launchpad.net/bugs/1958284
[17:02]  * slyon setting the importance to Medium
[17:23] <jawn-smith> rbasak: Do you know who maintains the git-ubuntu snap?
[17:53] <rbasak> jawn-smith: I do
[17:55] <jawn-smith> rbasak: I found what I needed, just hadn't realized it was part of usd-importer. I've been instructed however to remind you about an arm build for the snap :)
[17:55] <bdmurray> You maintain or you know who does? ;-)
[17:55] <rbasak> :)
[17:56] <rbasak> jawn-smith: see https://bugs.launchpad.net/usd-importer/+bug/1915507 on the arm build. I have no plans to fix it unless the snap people fix their end.
[17:56] <ubottu> Launchpad bug 1915507 in usd-importer "git-ubuntu unavailable on non-amd64 architectures" [Wishlist, Triaged]
[17:57] <rbasak> So nothing to remind me about really. I'd love to do it, but I'm not dropping git-ubuntu CI to do it.
[19:13] <tyhicks> bdmurray: Hey there! Are you aware of any reported issues with 5.10 (and newer) kernels not including the first page of shared object libraries in userspace coredumps?
[19:14] <tyhicks> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=429a22e776a2b9f85a2b9c53d8e647598b553dd1 started only including pages from inodes that are marked executable but Debian-based distros don't mark shared object libraries executable (per Debian Policy)
[19:14] <ubottu> Commit 429a22e in kernel/git/torvalds/linux.git "coredump: rework elf/elf_fdpic vma_dump_size() into common helper"
[19:17] <tyhicks> I don't see any apport bugs on this topic but I figured it would be affected in Hippo and newer. I can see that GNU build ID's of (non-executable) shared object libs aren't included in Hippo core dumps but maybe apport doesn't rely on any of the ELF headers of libraries?
[19:18] <tyhicks> Anyways, just wanting to see if it was a known problem for apport as I dig a little more
[19:22] <bdmurray> tyhicks: Its not one I am aware of
[19:24] <tyhicks> bdmurray: Ok, thanks. I'm a little stumped as to why this hasn't popped up on anyone's radar.
=== mwhudson_ is now known as mwhudson
[23:38] <Deepspeed> I need some help with ubuntu packaging.
[23:40] <Deepspeed> I was given an old package to maintain as a test and it's fairly complex and done the 'right' way, but out of date.  I need to find things to update about it.  Can anyone point me at some things I need to study, aside from just pointing to the broken official packaging guide?
[23:45] <ahasenack> Deepspeed: see if this helps: https://github.com/canonical/ubuntu-maintainers-handbook
[23:46] <sarnold> https://manpages.debian.org/testing/debhelper/debhelper.7.en.html and https://www.debian.org/doc/debian-policy/ch-relationships.html are perhaps more useful references than guides, but depending upon the state of the package, might be pretty decent starting points
[23:46] <bdmurray> Given that its a debian package you might find debian new maintainer's guide useful
[23:46] <sarnold> lintian output might give you concrete things to do
[23:47] <ahasenack> lintian is a good tip indeed
[23:48] <ahasenack> dep8 tests seem stalled
[23:49] <ahasenack> look at the log of all running tests here: https://autopkgtest.ubuntu.com/running
[23:49] <ahasenack> all the logs end with "autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds..."
[23:49] <ahasenack> can someone here give it a kick?
[23:49] <ahasenack> in terms of privileges/access, I mean
[23:51] <bdmurray> ahasenack: I think all the people who can are not at work at the moment
[23:51] <ahasenack> :(
[23:52] <bdmurray> Yeah, I'd like to be a part of that group since I'm so far west
[23:52] <ahasenack> what about vorlon?
[23:52] <sarnold> same here, I've thought I should be in that group just for the button clicking..
[23:53] <sarnold> but it's a *lot* of power just to click the button
[23:53] <ahasenack> there might not be a button
[23:53] <ahasenack> I mean, it could be more involved than that
[23:53] <sarnold> ohhhhh
[23:53] <sarnold> clicking buttons is one thing
[23:53] <ahasenack> but pulling levers!
[23:54] <sarnold> rofl
[23:54] <bdmurray> I think it requires access to the juju environment to sort out
[23:54] <ahasenack> whole different level