[00:28] <arraybolt3> https://bugs.launchpad.net/debian/+source/manuskript/+bug/1989203 I just finished backporting a bugfix for this bug from upstream, and would like to request sponsorship and review whenever possible. I have attached the debdiffs of my changes and ensured that the SRU template is correct.
[00:28] -ubottu:#ubuntu-devel- Launchpad bug 1989203 in manuskript (Ubuntu Kinetic) "Manuskript crashes on start" [High, Confirmed]
[00:29] <arraybolt3> (is ubuntu-sponsors a tag that I can ping?)
[00:30] <sarnold> wild /debian/ in there, heh
[00:30] <arraybolt3> lol, well a Debian bug report is attached, I guess the link I clicked and pasted may have been the one that pointed there.
[00:30] <sarnold> yeah, launchpad does that kiund of thing once in a while
[00:30] <arraybolt3> It works just as well if I do https://bugs.launchpad.net/ubuntu/+source/manuskript/+bug/1989203 :)
[00:30] -ubottu:#ubuntu-devel- Launchpad bug 1989203 in manuskript (Ubuntu Kinetic) "Manuskript crashes on start" [High, Confirmed]
[00:31] <sarnold> https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscrib
[00:31] <sarnold> er=&field.structural_subscriber=&field.component-empty-marker=1&field.tag=ubuntu-sponsors&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_bluep
[00:31] <sarnold> rints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search
[00:32] <sarnold> holymoly look at that url
[00:32] <sarnold> I thought that should find all the ubuntu-sponsors bugs, but the point of pasting it is to show that it doesn't find *any* bugs at all
[00:32] <arraybolt3> Great Resource Locator, Batman!
[00:32] <sarnold> lol
[00:32] <sarnold> so, uh, I have no idea how to find them all :(
[00:32] <arraybolt3> heh, I can't even use Canonical Mode in Weechat to be able to click that :P
[00:33] <sarnold> https://bugs.launchpad.net/ubuntu/?advanced=1  -- type "ubuntu-sponsors" into the tags: field, click search, see nothing useful :)
[00:33] <arraybolt3> Anyway I just meant, how do I get the attention of whatever sponsor happens to be free without having to manually ping random people with $powers and hope I'm not being a thorn in their side?
[00:33] <sarnold> ohhhhh
[00:33] <arraybolt3> I mean, I could just do tsimonq2, teward: LOUD PING HI :)
[00:34] <sarnold> oh tsimonq2 and teward love saying HI very LOUDLY :)
[00:35] <tsimonq2> Enotatacomputer
[00:35] <tsimonq2> Hah
[00:35] <tsimonq2> 🎉
[00:35] <arraybolt3> No problem, thanks for checking :)
[00:35] <teward> *throws arraybolt3 and sarnold into the rubbish bin*
[00:36] <arraybolt3> teward: Oh hey, sponsor my bug and give me coffee.
[00:36] <teward> in a meeting with CCT
[00:36] <arraybolt3> Ah, nevermind then.
[00:36] <arraybolt3> (And this is why I hoped there was a "ping all sponsors in the hopes that one of them is available" button. Didn't there used to be some #ubuntu-sponsors channel?)
[00:37] <tsimonq2> Nah, but you used to be able to #pilot in/out to show you were available to sponsor stuff, heh
[00:38] <arraybolt3> Hmm, that would be handy.
[00:46] <rbasak> @, not #
[00:46] <rbasak> I don't know if that still works or not
[00:51] <amurray> arraybolt3: a bit nitpicky but lintian complains you have a spelling error in your changelog entry - commmit - also I would usually list the filename of the new patch in the changelog as well
[00:51] <arraybolt3> Can fix both in just a sec, thanks!
[00:51] <sarnold> "commmit the froggg here"
[00:51] <sarnold> (sorry, the thought came into my head so now it's gotta be in your head, too)
[00:52] <amurray> arraybolt3: np
[01:07] <arraybolt3> amurray: Fixed.
[01:14] <amurray> arraybolt3: thanks - sorry I should have been clearer - when I said the filename of the new patch I meant something more like: https://paste.ubuntu.com/p/X53J5Gcyyk/
[01:15] <arraybolt3> Oh. Oops. OK, thanks, I will know that for in the future. Would you like me to fix that, or do you already have it changed?
[01:18] <arraybolt3> Fixing the patches now.
[01:27] <arraybolt3> amurray: Alright, third time's the charm. Thank you for your help!
[01:27] <amurray> arraybolt3: I was going to fix it but you beat me to it - thanks again - sorry for the run-around
[01:29] <arraybolt3> Heh, no problem. I'm happy to fix things as much as needed to get them just right.
[01:39] <amurray> arraybolt3: done - https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=manuskript and https://launchpad.net/ubuntu/kinetic/+queue?queue_state=1&queue_text=manuskript
[01:40] <arraybolt3> Thank you so much!
[01:42] <amurray> you're welcome :)
[01:42] <krytarik> rbasak: No, ever since switching networks the @pilot feature isn't available currently, mostly for lack of interest in using it - but there is an updated and improved version of the plugin that could be run on ubottu and the likes.
[01:48] <rbasak> krytarik: ah, thanks. Some people inside Canonical are working on getting some Canonical uploaders patch piloting on a schedule again, so it would be useful to have the bot again if that goes ahead. Is there someone we could coordinate that with, please?
[01:48] <sarnold> oh cool
[01:49] <rbasak> I'm trying not to promise what I'm not responsible for delivering, but there are people trying :)
[01:51] <arraybolt3> It would be cool if there was some channel where sponsors only joined the channel if they were available for sponsoring things, and that the bot had factoids like "!motuping", "!coreping", "!securityping" (maybe?), and pings for PPUs "!lubuntuping", "!serverping", etc.
[01:51] <arraybolt3> That way hitting !lubuntuping would ping me and the other Lubuntu Developers, hitting !motuping would signal all the MOTUs, etc. Any of them who were available would be in the channel, and would be able to pop out and help.
[01:52] <arraybolt3> I'd be happy to make such a channel (probably called #ubuntu-sponsors) if it's something people would be interested in. Obviously it would be under IRCC governance.
[01:53] <rbasak> I think the challenge there would be to get sponsors to join. Because if they're in there, they'd basically be committing to taking interrupts, and that's not a great way to get things done. I'd prefer to have a scheduled slot where I focus on piloting, which is how it used to work.
[01:53]  * arraybolt3 now wonders how founding an #ubuntu- channel works
[01:53] <JackFrost> What are we going to do?  Tell you "No, you've got your quota of channels"? :>
[01:53] <JackFrost> (Downside is that is Yet Another Channel to join.)
[01:54] <rbasak> People did have suggestions internally when we were talking about what we could do to get contributions landed more effectively.
[01:54] <arraybolt3> JackFrost: lol, everything under the #ubuntu namespace is IRCC territory, so you could just tell me "no".
[01:54] <arraybolt3> rbasak: Hmm. I don't know how piloting used to work, so maybe that's something I should look into.
[01:54] <rbasak> My suggestion was to cut through the bikeshedding by resuming what we used to do, because IIRC it generally used to work, and then once established only then discuss improvements.
[01:55] <rbasak> For Canonical pilots, we had a schedule and a nominated day about once a month.
[01:55] <rbasak> During that time, we were supposed to check in here (with @pilot in) and spend that time focusing on the sponsorship queue and being available to contributors in this channel for real time help.
[01:55] <arraybolt3> Oh, that makes a lot of sense.
[01:55] <rbasak> From a contributor's perspective, that meant that they could check this channel's topic and hopefully have a person to ping.
[01:56] <rbasak> I think that was effective when it worked, at least in getting sponsorship queue processing going.
[01:56] <rbasak> Maybe not so much for volunteers looking to find someone, especially if coverage was proportionally low.
[01:56] <rbasak> But it was better than nothing.
[01:56] <rbasak> That method was probably better suited to people being employed to do this though
[01:57] <rbasak> Maybe your interrupt channel would work better for unpaid volunteers.
[01:57] <arraybolt3> I wonder how that would work for people outside of Canonical who had the needed privileges? I notice you talk about Canonical pilots, but obviously there's a lot of devs out there who aren't in Canonical.
[01:57] <arraybolt3> Yeah, maybe. Like I'd love to be in there (though then again not many people have things to contribute to the Lubuntu packageset so I wouldn't be getting flooded with work :P)
[01:57] <rbasak> Inside Canonical I wanted to focus on that side first because that's what we could actually influence and achieve.
[01:58] <rbasak> For non-Canonical Ubuntu devs, I'm sure they'd be welcome to integrate into a rota if they were happy to work with that.
[01:58] <arraybolt3> Makes sense. I might try the interrupt channel thing and see if it catches on (sponsorship requests are rare enough in here that it might not be a big deal, or maybe I'm just not reading closely enough).
[01:59] <rbasak> I'm total open to alternatives, though to avoid bikeshedding _within_ Canonical I'd really just like to get the old thing going again first, as that's better than the nothing we have right now.
[01:59] <rbasak> And we can always adjust later.
[01:59] <arraybolt3> +1
[02:00] <rbasak> arraybolt3: btw, are you https://askubuntu.com/users/1598467/arraybolt3-leftseforcodidact?
[02:00] <arraybolt3> I am.
[02:00] <arraybolt3> I've been considering changing that back to just arraybolt3 though.
[02:01] <rbasak> So we wrote up https://ubuntu.com/server/docs/about-apt-upgrade-and-phased-updates, FYI
[02:01] <rbasak> Based on your answer from askubuntu.com
[02:01] <arraybolt3> Oh wow!
[02:02] <rbasak> So thank you for that, and feedback appreciated :)
[02:02] <arraybolt3> I loved doing stuff on there and the rest of SE and then got really upset when I did research into the 2019 mess around SE and did that, but I think I probably overreacted and besides all that stuff is long past so maybe I'll just go back.
[02:02] <arraybolt3> rbasak: Glad to help! I'll read it and see if there's anything I notice that could use changed.
[02:02] <rbasak> Please!
[02:03] <rbasak> You will notice that we tweaked it. I hope all our tweaks make sense :)
[02:03] <arraybolt3> I'm sure they do, since you guys know how it works better than I do most likely.
[02:09] <krytarik> rbasak: Yeah, I've heard of recent efforts to revive the patch piloting scheme.  And my suggestion would indeed be to just run the plugin on ubottu alongside its other ones, since it doesn't need to be opped all the time for this anymore - in which case, or in any case really, JackFrost would be the one to talk to.
[02:11] <teward> arraybolt3: i'm assuming you're still alive :P
[02:11] <teward> still need help or are you good?
[02:11] <arraybolt3> rbasak: I changed back to just ArrayBolt3 on SE (including AskUbuntu), so if you could change my username in that page that would be great.
[02:11] <arraybolt3> teward: Already finished, thanks!
[02:11] <teward> cool cool i have info for you anyways so see incoming DMs
[02:12] <arraybolt3> rbasak: I did want to mention, "and the message will disappear when the phasing has reached 100%." - this isn't totally true - the message will come back when new packages start phasing, and if some packages finish phasing and others are still phasing, they'll still see the message. Perhaps "the package will not be held back once the phasing system deems your system ready for receiving the
[02:12] <arraybolt3> update" would be better?
[02:26] <rbasak> arraybolt3: I've updated your attribution since that's a no brainer. On your edit suggestion, would you mind making it at https://discourse.ubuntu.com/t/about-apt-upgrade-and-phased-updates/33649 please? We have a technical writer taking care of the editing, and I don't want to undermine her efforts there.
[02:26] <arraybolt3> Sure thing.
[02:26] <rbasak> Thanks!
[13:57] <jbicha> cpaelzer: is pkgconf ready for promotion to main? bug 1998095
[13:57] -ubottu:#ubuntu-devel- Bug 1998095 in pkgconf (Ubuntu) "[MIR] pkgconf, replacement for pkg-config" [Medium, In Progress] https://launchpad.net/bugs/1998095
[16:43] <enr0n> I am looking for a sponsor (MOTU or core dev) for a couple of bugs from +1 maintenance: bug 2006617 and bug 2006501.
[16:43] -ubottu:#ubuntu-devel- Bug 2006617 in aseba (Ubuntu) "aseba missing builds on s390x and ppc64el" [Undecided, New] https://launchpad.net/bugs/2006617
[16:43] -ubottu:#ubuntu-devel- Bug 2006501 in openlibm (Ubuntu) "FTBFS on armhf with ‘-mfloat-abi=hard’: selected architecture lacks an FPU" [Undecided, New] https://launchpad.net/bugs/2006501
[16:46] <enr0n> utkarsh21021: ^ pinging you as promised :)
[17:07] <bdmurray> sarnold: you want 'ubuntu-sponsors' in the subscriber box not tag
[20:13] <sarnold> bdmurray: aha! thanks :)
[20:26] <vpa1977> Hi, Beagle and chromhmm packages are published for Architecture all, and depends on sra-sdk (libngs-jni). libngs-jni is a native library built for arm and amd64, but not for ppc64el. This is causing a regression https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/ppc64el/b/beagle/20230207_230613_01522@/log.gz. https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/ppc64el/c/chromhmm/20230207_234119_f25a8@/log.gz. I wonder if
[20:26] <vpa1977> sra-sdk needs to be built for all applicable architectures?
[22:29] <MacSlow> Greetings everybody!