[12:48] <IPv2> kanashiro: Very big thanks again for pointing me in the right direction twice now, with ruby-ncurses SRU, and on the Debian channel. :-)
[12:49] <kanashiro> you're welcome IPv2 :)
[12:49] <IPv2> kanashiro: Because package sup-mail is already in bionic and eoan (and will be sync'd to groovy), are we perhaps in scope for an "Other safe cases" SRU for focal? "For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations (e. g. entirely new packages are usually fine)."
[12:49] <IPv2> https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
[12:50] <IPv2> kanashiro: My thinking is that an existing user on (say) bionic, upgrading to focal, would break their existing installation. (Failure to launch sup-mail at run-time after the upgrade to Ruby 2.7)?
[12:52] <kanashiro> IPv2: after reading this paragraph of the doc I believe we can try to introduce sup-mail in Focal, it should not break anything else
[12:53] <IPv2> kanashiro: I agree, risk of regressions should be very low, and could dramatically improve user experience on upgrade from an earlier release. Should I file a new bug in the SRU format?
[12:53] <kanashiro> an opinion from someone in the SRU team would be great
[12:53] <kanashiro> rbasak: ^
[12:59] <rbasak> kanashiro: I need more context please
[13:00] <kanashiro> rbasak: sup-mails is not available in Focal in Focal, IPv2 wants to introduce it via SRU to avoid breakages when sup-mail bionic users upgrade their systems
[13:00] <kanashiro> s/sup-mails/sup-mail/
[13:01] <rbasak> What's its status now?
[13:02] <kanashiro> specially because in Focal we moved to ruby 2.7, so the sup-mail in bionic would not work
[13:03] <kanashiro> It is fixed in bionic and now it was re-introduced in Debian and back in sync in Groovy
[13:03] <rbasak> We'd want it well-maintained in Ubuntu to prevent flip-flopping. Looks like it's stuck in proposed.
[13:04] <kanashiro> IPv2 has been putting some effort on this since he is now one of the upstream maintainers, I believe we can count on him to keep it well maintained, right? :)
[13:05] <rbasak> I agree it'd be pretty harmless SRU-wise to fix it in Focal, though I'd want to consult with other SRU team members to make a final decision. *However* if the purpose is to avoid users regressing because it is gone in Focal, I think we should also do our best to make sure it will be well-maintained in the future. Otherwise we'd only be deferring the inevitable pain for user later.
[13:05] <rbasak> So that's what I was going to ask :)
[13:05] <rbasak> Can we have a commitment to maintain the package in Ubuntu going forwards?
[13:05] <rbasak> Some track record of that would be nice too.
[13:06] <rbasak> If we have that, then I'd be supportive of an SRU to Focal, subject to the opinions of other SRU team members and assuming I'm not missing anything.
[13:06] <kanashiro> IPv2 is now one of the uploaders of sup-mail in Debian
[13:07] <IPv2> rbasak / kanashiro: I'm one of two new upstream maintainers for Sup. The other upstream maintainer has maintained it for years in Fedora, but is new to upstream. I'm brand new to maintenance in Debian/Ubuntu, but am one of the Debian uploaders now. I'm happy to commit to keep it supported. (I'm a long-term Sup user, over 10 years, and volunteered to pick up the maintenance after I saw it was broken on
[13:07] <IPv2> Ruby 2.7)
[13:07] <rbasak> IPv2: thank you for volunteering! We appreciate your help.
[13:07] <IPv2> rbasak: So short version: yes, I am happy to commit to that. :-)
[13:07] <rbasak> IPv2: can I suggest that you subscribe to bugs for the package?
[13:08] <IPv2> rbasak: I will do right now
[13:08] <rbasak> In that case I'm supportive of your request. Can you file a bug to request the SRU please, and detail the rationale and your commitment etc in here? kanashiro can help you with that as needed.
[13:09] <rbasak> I will still want to consult with others before making a final decision though.
[13:09] <rbasak> Also, the package needs fixing in Groovy as it's not in the release pocket yet.
[13:09] <rbasak> Though it's a very recent upload so maybe that's still in progress?
[13:09] <IPv2> rbasak: Thank you, I greatly appreciate your help (and kanashiro's). I will file the bug later today. I understand that it's not a final decision.
[13:09] <kanashiro> rbasak: great, thanks for your input. I can help IPv2 to move this forward
[13:10] <IPv2> rbasask: Yes - perhaps we should give it a few days then to land in groovy, before filing the SRU bug?
[13:10] <rbasak> Having a track record of good maintenance would be very helpful
[13:11] <kanashiro> IPv2: you can start to prepare the SRU bug and when it lands in Groovy we subscribe the SRU team
[13:11] <rbasak> Normally Ubuntu prefers to see an established team, but I think it's probably proportionately OK here as it's a leaf package and there's no major harm potential by adding it to Focal
[13:12] <IPv2> kanashiro: Thank you - good idea. Will do. I'm at $DAYJOB just now, but will start to prepare the SRU bug later today (and I'll subscribe you when I do, but not the SRU team at this stage).
[13:12] <rbasak> Note that you can file a bug now and only ask for it to be looked at later. No reason to delay starting. You can mark a bug "Incomplete" to communicate that you're not ready for it to be looked at yet
[13:13] <IPv2> rbasak: The Debian maintainer is an established team, and I'm one of two uploaders in Debian now (one very established in Debian). I'll include that when raising. Thank you!
[13:13] <kanashiro> IPv2: feel free to ping me in case of any doubt
[13:14] <IPv2> kanashiro: Thank you, I really appreciate all your help.
[13:16] <kanashiro> you are more than welcome!
[13:56] <coreycb> hello, please can an archive admin take a look at accepting intervals from the groovy new queue? it's a new dependency for python-sqlalchemy-utils.
[15:08] <dgadomski> hi bdmurray, could I have your opinion on the patches for https://bugs.launchpad.net/bugs/1881976?
[15:10] <bdmurray> dgadomski: I'm in a meeting now but I've opened a tab about it
[15:11] <dgadomski> thanks, that's nothing super urgent
[16:51] <bdmurray> xnox: did you test bug 1870813 on groovy?
[17:14] <xnox> bdmurray:  i search for it in gnome shell, it launches, i can execute help command, and exit command, without crashing. It's "operational" to me, on smoketesting basis in groovy.
[17:15] <bdmurray> xnox: can you update the bug then?
[17:22] <rafaeldtinoco> ddstreet: xnox: to which repo should I do a PR for systemd (udev) ?
[17:22] <rafaeldtinoco> want to reword a patch for groovy to backport as SRU to focal/bionic
[17:23] <rafaeldtinoco> or should I just go ahead and dput the change as its small ?
[17:23] <rafaeldtinoco> rbalint: ^ might be the right person to ask
[17:25] <rafaeldtinoco> nm, ill dput it, its faster =)
[17:27] <bdmurray> juliank: How is Ubuntu.mirrors from python-apt-common used?
[17:34] <bdmurray> juliank: I think I've sorted it out
[17:37] <juliank> bdmurray: software properties mirror selection
[17:38] <bdmurray> juliank: yeah, that's what I remembered
[18:18] <xnox> bdmurray:  done.
[18:19] <xnox> rafaeldtinoco:  whatever is in Vcs- header of the source package. It is something like lp:~ubuntu-core-dev/ubuntu/+source/systemd maybe?
[18:22] <rafaeldtinoco> https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd
[18:23] <rafaeldtinoco> tku
[19:36] <xnox> i guessed right! win!
[19:38] <sarnold> ooh ooh! what's your prize?