[14:15] hi, could someone please set LP: #1771363 importance to High and also create a bionic task with High importance for both LP: #1771363 and LP: #1739631? [14:15] Launchpad bug 1771363 in ca-certificates-java (Ubuntu) "ca-certificates-java: convert PKCS12 cacerts keystore to JKS" [Undecided,New] https://launchpad.net/bugs/1771363 [14:15] Launchpad bug 1739631 in ca-certificates-java (Ubuntu) "Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file" [Undecided,Fix released] https://launchpad.net/bugs/1739631 [17:24] Hi, I filed a StableReleaseUpdate bug a few days ago for pikopixel.app (pixel-editing app in the universe repo), but there's been no response so far. [17:24] Can someone please take a look, and let me know if I did it right? [17:24] https://bugs.launchpad.net/ubuntu/+source/pikopixel.app/+bug/1770777 [17:24] Ubuntu bug 1770777 in pikopixel.app (Ubuntu) "[SRU] Bionic: PikoPixel 1.0 BETA9b can crash when resizing a document window" [Undecided,New] [17:26] tedge: patience is a virtue, SRUs take time to review [17:26] and there's a bunch of them [17:28] not to mention someone has to download the updated source code, adjust the package, test the package, etc. typically to make sure it all works. [17:28] teward: you should ask in #ubuntu-devel or #ubuntu-motu. This channel is for bug triage only. I don't see prepared packaging for Bionic though? [17:28] tedge: ^ [17:28] i was about to say that as well [17:28] Uh yeah sorry. [17:28] rbasak: No problem :) [17:29] tedge: you can't just "update Bionic to Cosmic's version". It will need a rebuild, and thus a new version number. Therefore updated packaging. Usually sponsors expect this to already be prepared and tested. [17:30] Thanks, teward. This is the first time I've filed a SRU, so I didn't know what to expect in terms of timeframe. [17:30] tedge: rbasak is right though [17:30] *is operating on no coffee right now >.<* [17:35] rbasak: Thanks. I'm the upstream developer, not a packager. Would -devel or -motu be the appropriate place to ask for help rebuilding the package, or should I go to ubuntu-packaging? [17:35] tedge: i think you need someone who knows packaging to volunteer to work on the patching. [17:36] either -devel or -motu would work, but the core question is "Who will prepare the packaging" [17:36] if you don't know how then someone needs to step up to help with that step [17:36] or the SRU goes nowhere. [17:36] tedge: given it's for Ubuntu itself, I think people in -devel and/or -motu would be happy to answer questions. But yeah, it needs someone to be prepared to do the packaging side. [17:43] unfortunately, it hasn't been packaged specifically for Ubuntu before (it's only been inherited directly from Debian), so I don't know anyone yet. [17:43] *yawns from boredom* [17:43] i could use a break, let me see how difficult patching it would be [17:43] I'll ask around in -devel/-motu, thanks for the tip! [17:44] teward: that would be great! let me know if I can answer any questions about the sources. [18:22] provided of course I don't get killed by work :P [18:26] rbasak: making tedge's code work would need an MRE [18:26] since there's no visible upstream VCS repo where the package code can be nitpicked [18:26] so any 'patch' is going to basically be a full MRE [18:28] The Debian GNUstep team has a VCS repo for the package, with a mirror of the upstream sources: https://salsa.debian.org/gnustep-team/pikopixel.app [18:28] well [18:28] kinda [18:28] but not really [18:28] they're just importing the tarballs [18:28] and the taking that source and putting it in the repos [18:28] I'm asking if *you* have a nitpicked patch that doesn't require a full version bump to fix *just* this one issue [18:29] which judging by your changelogs sounds like "more than one issue" at play [18:29] we can continue this discussion in a more valid channel though [18:32] what channel do you want to go to? [18:50] teward, wrt yesterday's thing, I also wrote a trivial patch that enables my system to process emoji domains [18:51] augeus: nice, I'd share that on some page so that others can benefit, even if it's in a gist. [18:51] * augeus uploaded it to launchpad (attch. on the bugreport) [18:52] i've got 50 bugreports on my screen from today and yesterday, mind reminding me which bug report? [18:52] #1771109 [18:53] It's a *very* trivial patch, and it's most probably not the way to do things, but, hey, it works for me :) [20:07] teward, So, what do you think? Am I handling this correctly? [20:21] augeus: has that patch been accepted upstream? [20:21] augeus: if not, I'm not sure it's appropriate for Ubuntu to diverge from upstream behaviour on this. [20:22] I see [20:22] Especially for stuff like IDN because that's very security sensitive. [20:22] Thanks for the info -- I will bring this up upstream [20:22] I'll comment that on the bug. [20:22] I'm not really familiar with the procedures involved [20:22] Sorry if I'm pestering you :) [20:23] No problem. We're always looking for volunteers to help with getting changes landed, and so we're usually quite happy to explain (and take feedback on) procedures. [20:24] Please try to use #ubuntu-devel though. This channel isn't really appropriate, and you're more likely to readily get help there. [20:24] * augeus does not know much about distro politics [20:25] Never had to submit a bug report/patch to a distribution -- I am fairly cautious when choosing hardware and software, so I usually don't run into issues [20:25] So, even though I can code, I never had to go through this [20:26] Imagine, I've been in this ride for some time, too [20:27] So, yeah. I'll be asking upstream, see what they think about this [20:28] I'm not sure this is really about politics. More about which way patches flow through the ecosystem. [20:29] Well, it's a form of formal bureaucracy, which exists for a good reason, but it helps if one obtains some help in navigating it :) [20:48] rbasak: i replied to your PMs, by the way. I may need to do some heavy-duty grinding down to find the specific fixes... [20:48] ... after dinner and voting. *gone*