[01:06] <axino> hello ! where would I file a bug against the "Daemons using outdated libraries" popup that appears during apt operations ? apt itself ?
[01:11] <sarnold> axino: I think that's the needrestart package
[01:52] <JackFrost> needrestart-session is a different source package I believe.
[01:53] <sarnold> TIL there's a needrestart-session
[10:49] <utkarsh2102> is there a way to get a permalink of lines in a file in LP?
[10:49] <utkarsh2102> I'd like to make this a permalink: https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/config#n937
[10:49] <utkarsh2102> how'd I go about it?
[10:57] <JackFrost> https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/config?h=2.799#n937
[11:01] <JackFrost> utkarsh2102: Maybe I should introduce a ping so you see that.
[11:02] <utkarsh2102> JackFrost: sweeet, thank you! :)
[11:02] <JackFrost> Sure thing!
[12:20] <nteodosio> Can I please have these autopkgtests triggered? https://termbin.com/qeh9h
[12:29] <kyleA> hi all, I am trying live build, when i lb config then update the bootstrap file to use jammy, the lb bootstrap works but lb chroot fails. also lb config then lb build fails based on a package not supported anymore but i am unsure how to correct /usr/share/libe/build/funcions/defaults.sh the theme reffered to there seems to be a alias
[12:29] <kyleA> sorry for the longer message, just wanted to explain as clearly as i no how what i have tried
[12:35] <kanashiro[m]> ahasenack: could you tell me the next steps regarding the docker.io situation? What do you want me to do exactly?
[12:36] <ahasenack> well, my sru shift is over
[12:37] <ahasenack> I would like to know why the kinetic+ lxd needs to be privileged, and jammy doesn't, since both use the same lxd snap
[12:37] <ahasenack> to see if it's a change in the new docker, or something else
[12:38] <ahasenack> and that was a change that was not discussed in the bug, it was just slipped in, that was unconfortable, given that the sru criteria for this type of sru is the dep8 test, and the dep8 test was changed like that
[12:38] <ahasenack> so maybe a new bug that is about this change (lxd must be privileged now in kinetic and later, for <reasons>)
[12:39] <ahasenack> maybe I'm being too strict, that's fine, maybe another sru team member can have another opinion
[12:40] <ahasenack> and this would be the third accept for docker.io in this single bug :)
[12:40] <ahasenack> (if I'm not mistaken)
[12:42] <ogra> ahasenack, probably a silly guess, but did the newer lxd snap stop adding the lxd group (or stop adding users to it)
[12:43] <ahasenack> ¯\_(ツ)_/¯
[12:47] <kanashiro[m]> ahasenack: to be clear I am not asking you to do anything now, I just wanted to understand what are my next steps to make this land
[12:48] <ahasenack> well, if I were preparing this sru, that's what I would do. Get dep8 runs with and without the privileged container, and try to determine why it's suddenly necessary (if it really is)
[12:48] <ahasenack> and I understand that the dep8 infrastructure might not be well enough for these tests :/
[12:48] <kanashiro[m]> and I understand you being strict, however, this is not a regression, the current version in the archive fails in the same way. I'll try to find the answers for you
[12:48] <ahasenack> I tried that locally during my shift, and the test was failing with and without the privileged option
[12:49] <kanashiro[m]> I ran locally with the qemu backend and I was able to reproduce the failure and then verify the fix
[12:49] <ahasenack> I used a qemu vm, with the ssh "backend", like I always do
[12:50] <ahasenack> I was about to create a ppa for myself, upload these packages there, and test myself
[12:50] <ahasenack> but then the day ended
[12:50] <ahasenack> I also agree that the deb x snap situation of lxd made many tests not run in the past, and that was considered "normal" (a mistake, if you ask me)
[12:51] <ahasenack> so we may just be seeing NOW something that was broken a long time ago
[12:51] <ahasenack> but still, the diff between kinetic and jammy is intriguing, given it's the same snap (not installde by the deb-to-snap pacakge)
[12:51] <ahasenack> and in the sru you don't have the extra privileged flag for jammy
[12:51] <ahasenack> so something is going on
[12:52] <kanashiro[m]> but since this is out there for almost a year I would have expected at least a single bug report against docker.io complaining about it
[12:53] <kanashiro[m]> but I understand, I'll try to find what's happening
[13:45] <nteodosio> Can I please have these autopkgtests triggered? https://termbin.com/qeh9h [Repeated in case it has been buried]
[13:49] <sergiodj> sil2100: hey, do you know what's going on with bileto?  I can't login and I'm getting lots of error 500 messages
[13:50] <sil2100> sergiodj: hey. hm, let me ask IS to restart it in a bit
[13:54] <schopin> nteodosio: on it.
[13:54] <nteodosio> Thanks!
[13:55] <sergiodj> sil2100: thanks
[17:08] <nteodosio> Can I please have a re-trigger of https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=arm64&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/110.0.5481.100-0ubuntu0.18.04.1
[17:54] <axino> JackFrost: so "Daemons using outdated libraries" comes from needrestart-session and not needrestart ?
[20:07] <sergiodj> question for the SRU folks: when an MRE upload fixes an existing Ubuntu bug, do we require an SRU text for such bug?  my gut feeling says yes, but I'm not entirely sure
[20:08] <bdmurray> sergiodj: If it is explicitly called out in the changelog (which I'd expect given what you said) yes.
[20:09] <sergiodj> bdmurray: cool, that's what I thought, thanks for confirming, Brian
[23:10] <rbasak> bdmurray: ^ IMHO, it shouldn't be required because it's covered by the MRE, and therefore there's no need for individual verification. Otherwise we're just discouraging uploaders from linking everything together with good bug reference, automatic closure of bugs as the fix lands, etc. I would ask for a note in the SRU bug explaining that it's covered by the MRE bug though, and for the person driving
[23:10] <rbasak> the SRU to mark the appropriate verification-done tags with a comment explaining, to avoid any confusion.