[01:03] <newbie_melody> Hey...   If your hardware supports it, I'd go 64 of course.
[01:10] <newbie_melody> With the thousands of choices available within a single mirror, how do I know which one is 32-bit? My computer can't handle 64.
[01:11] <Unit193> Then you'd go for something like xubuntu-16.04.3-desktop-i386.iso or xubuntu-17.10-desktop-i386.iso
[01:15] <newbie_melody> Alright. Thanks!
[13:03] <xubuntu01i> how can i install linux.exe on windows 3.11?
[15:53] <f76> Hi folks. I've been installing and setting up Xubuntu and my network indicator applet has disappeared from the system trey. Would anyone know how I get it back?
[15:55] <f76> I need it to connect to my VPN
[16:00] <f76> brb restarting
[16:06] <f76> A system restart seems to have fixed my issue for now. Quite a few bugs I've come across, but I guess I'll have to wok through them alone.
[16:42] <raff> salve
[23:18] <fChanX> Hello


[08:33] <Mirv> sil2100: too much for you? :)
[11:07] <pstolowski> jibel, hello! quick question, the yellow 'next milestone' tag you have on a few silos in the dashboard means they didn't make it for OTA11?
[11:10] <jibel> pstolowski, yes, unless it something critical for OTA11 of course. which silo?
[11:10] <jibel> it is*
[11:10] <pstolowski> jibel, 47
[11:12] <pstolowski> jibel, nothing super critical, a couple of nice-to-have bugfixes. leave it up to you to judge the importance, i understand you're under pressure already
[11:14] <jibel> pstolowski, it will unlikely make it, there are still too many things to land today and testing should have started yesterday.
[11:16] <pstolowski> jibel, i see, ack. thanks!
[11:17] <jibel> pstolowski, besides a fix for bug 1578283 is a good candidate for OTA11
[11:18] <pstolowski> jibel, i know, but atm we still don't know what's causing it and can't reproduce on our devices
[11:19] <jibel> pstolowski, I'll try to reproduce with the upstart job method, I saw it several times
[11:20] <jibel> pstolowski, like right now on arale after a reboot
[11:20] <jibel> (but without debug mode on)
[11:25] <pstolowski> marcustomlinson, ^
[11:28] <marcustomlinson> pstolowski: yeah I'm really stumped with this one
[11:28] <pstolowski> jibel, do you recall when did it start happening (roughly)?
[11:35] <jibel> pstolowski, https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1578283/+attachment/4659168/+files/scope-registry.log
[11:35] <jibel> pstolowski, I don't remember sorry
[11:35] <jibel> marcustomlinson, ^
[11:36] <pstolowski> jibel, thanks
[11:37] <jibel> pstolowski, marcustomlinson All I did is reboot, unlock the SIM then unlock the greeter. the progress bar at the bottom of the app scope is moving a moment then stops and the scope remains blank
[11:37] <pstolowski> jibel, can you also attach unity8-dash.log?
[11:39] <jibel> pstolowski, attached
[11:39] <jibel> these log files really need timestamps
[11:41] <pstolowski> indeed
[12:11] <rvr> ChrisTownsend: bregma: 15 and 56 approved
[12:11] <ChrisTownsend> rvr: Sweet!  Thanks!
[12:11] <rvr> ChrisTownsend: However, I didn't get the gedit icon on the Launcher
[12:11] <rvr> Not even with the new puritine click
[12:12] <ChrisTownsend> rvr: Really?  Did you restart the frieza?  I had to reboot it to get it to work.
[12:12] <rvr> Yes, I rebooted a couple of times
[12:12] <rvr> It doesn't appear in the Libertine scope either (checked 15+56 together).
[12:13] <ChrisTownsend> rvr: Hmm, I'm not really sure why you don't see it then.
[12:14] <ChrisTownsend> rvr: Just to make sure, click list shows version 0.8 of puritine installed?
[12:27] <rvr> ChrisTownsend: Yes, see the trello card
[12:27] <rvr> $ click list | grep puritine
[12:27] <rvr> com.ubuntu.puritine 0.8
[12:29] <ChrisTownsend> rvr: Ok, well, I'm really at a loss as to what is going on.  I see it on my frieza (only after a reboot).  I'll keep on eye on that and thanks for letting me know.
[12:30] <rvr> ChrisTownsend: Which image are you using?
[12:30] <ChrisTownsend> rvr: Let me check
[12:31] <ChrisTownsend> rvr: As another way to see if the icon theme is properly installed in the puritine click, whenever you do open Gedit, do you see proper icons in the gedit menu bar?
[12:32] <rvr> ChrisTownsend: Nope
[12:32] <rvr> ChrisTownsend: Maybe it needs a new gedit click ?
[12:33] <Saviq> plars, hey, I'm afraid krillin-07 is dead on us, lifeboat can't recover it since a few days
[12:34] <Saviq> arale still unstable on the USB connection, too :(
[12:34] <ChrisTownsend> rvr: Well, puritine is all one big click.  That version 0.8 should have the humanity-icon-theme in it.  I wonder if somehow the wrong puritine click was downloaded.  I created a different 0.8 that didn't have the theme in it, and I'm wondering if somehow that was left laying around.
[12:34] <ChrisTownsend> rvr: BTW, I'm using build 97 form rc-proposed.
[12:34] <ChrisTownsend> *from
[12:34] <rvr> Me too
[12:35] <ChrisTownsend> rvr: Do you have time to try downloading the Puritine click again and reinstall it on your frieza?
[12:35] <ChrisTownsend> rvr: I'll give you a different link.
[12:36] <Saviq> jibel, FYI, https://requests.ci-train.ubuntu.com/#/ticket/1381 is ready (just waiting for britney results, but our own were happy - and we've fixed one of the flaky tests we've recently seen)
[12:36] <rvr> ChrisTownsend: Yes
[12:37] <ChrisTownsend> rvr: Ok, cool.  Try this one: https://private-fileshare.canonical.com/~townsend/puritine/com.ubuntu.puritine_0.8_armhf.click
[12:37] <ChrisTownsend> rvr: This is the one I have installed on my frieza and gedit icons work.  *Hopefully* it will work for you.
[12:38] <Saviq> jibel, sorry we've missed the mark on Final Freeze
[12:39] <jibel> Saviq, it is really too late to land it for OTA11
[12:39] <jibel> there are still silos in the queue and several critical bugs to fix
[12:40] <rvr> ChrisTownsend: Downloading
[12:41] <Saviq> jibel, you guys' call - these are all really small fixes for DGU and test stability - if we can't land for OTA11, bummer - maybe we cherry pick some of them that you decide worth it
[12:41] <jibel> Saviq, does it fix anything in this list https://bugs.launchpad.net/canonical-devices-system-image/+bugs?field.tag=lt-blocker ?
[12:42] <Saviq> jibel, no
[12:43] <Saviq> jibel, I'd venture to say a few of the ones it fixes, should be added to that list, though ;) - but again, your call
[12:46] <kdub> do the launchpad ppa's use pbuilder? trying to debug an issues that only happens in the builder
[12:47] <Saviq> kdub, sbuild
[12:47] <kdub> hmm, makes my problem more mysterious, as local sbuild works for me
[12:47] <kdub> thanks for confirming Saviq
[12:52] <ChrisTownsend> sil2100: Hey!  Are you able to ack the packaging changes in https://requests.ci-train.ubuntu.com/#/ticket/1360 and publish?  If so, do you have time to do that?
[12:53] <sil2100> ChrisTownsend: hey! Yes, I have the power, but would need a few minutes
[12:53] <ChrisTownsend> sil2100: No worries if you don't:)
[12:54] <ChrisTownsend> sil2100: Ok, thanks.  A few minutes is fine.  I know you're busy though, so I can find someone else if you need me to.
[13:00] <plars> Saviq: thanks for letting me know. I'll look into it in just a bit
[13:09] <rvr> ChrisTownsend: Installed the new click, same result
[13:10] <rvr> com.ubuntu.puritine	0.8
[13:10] <ChrisTownsend> rvr: Ok, could you do a ls -la on ~/.cache/libertine-container/puritine?
[13:11] <rvr> ChrisTownsend: http://paste.ubuntu.com/16317818/
[13:11] <ChrisTownsend> rvr: Ah, there's the problem.
[13:12] <ChrisTownsend> rvr: So remove ~/.cache/libertine-container/puritine and then do
[13:12] <ChrisTownsend> rvr: initctl --session start purtine-click
[13:12] <ChrisTownsend> rvr: Then send me the ls -la output again,
[13:13] <rvr> initctl: Unknown job: purtine-click
[13:13]  * ChrisTownsend scratches head
[13:13] <rvr> Ah, wrong spelling
[13:14] <rvr> Done
[13:14] <ChrisTownsend> rvr: lol, I misspelled it
[13:14] <rvr> lrwxrwxrwx 1 phablet phablet  110 may  9 14:13 rootfs -><EMAIL_ADDRESS>[13:14] <ChrisTownsend> rvr: Ok, that is better.  Try it again.
[13:16] <ChrisTownsend> rvr: BTW, this won't be a problem on the channel image since penk will be installing the updated click over the old one in /custom
[13:19] <ChrisTownsend> rvr: Another thing, the puritine-click upstart job never took into consideration that the puritine click could be installed in 2 separate places.  In the next Libertine release, I will have working puritine click hook that will replace the upstart job and can handle multiple puritine-type click packages as well as a puritine click being installed in 2 separate places.
[13:20] <rvr> ChrisTownsend: Cool. This looks way better.
[13:21] <ChrisTownsend> rvr: Awesome!
[13:21] <rvr> I can see the icon in the Launcher, in the scope, and gedit displays nice icons.
[13:21] <rvr> Wee!
[13:22] <rvr> ChrisTownsend: So, what will happen to people with old symbolic links like me?
[13:24] <ChrisTownsend> rvr: Well, when the next frieza image is released, it will just work since penk rolls everything up in the custom tarball.
[13:25] <ChrisTownsend> rvr: If someone installed the puritine click via pkcon, then it will still work since puritine is in it's standard place.
[13:25] <rvr> Ok
[13:26] <ChrisTownsend> rvr: Thanks for verifying this.
[13:26] <rvr> You're welcome
[14:16] <tedg> Huh, apparently I can't merge a silo? I thought any lander could do that.
[14:59] <tedg> sil2100: Can you merge this for me? https://requests.ci-train.ubuntu.com/#/ticket/1360
[15:00] <sil2100> tedg: it looks landed to me - what's wrong with it?
[15:02] <tedg> sil2100: Oh, I thought I needed to merge at the end...
[15:02] <tedg> sil2100: Seems that happened automagically. Sorry.
[15:03] <sil2100> tedg: no no, that happens automatically usually, only in some specific cases when the package is blocked etc.
[15:39] <marcustomlinson> faenil, jibel, pmcgowan, popey: Hey guys, could you please install the click scope from this PPA: https://code.launchpad.net/~unity-api-team/+archive/ubuntu/dev-build-1, and let me know if you still get an empty click scope.
[15:40] <faenil> marcustomlinson: ok
[15:45] <kenvandine> sil2100, any idea when we'll get a new turbo image?  we just discovered that bug 1579626 is already fixed in the archive but not in the turbo image
[15:49] <pmcgowan> marcustomlinson, all 3 packages there?
[15:50] <marcustomlinson> pmcgowan: yeah, should be unity-scope-click-departmentsdb, unity-scope-click-init-departments, and unity-scope-clic
[15:52] <pmcgowan> ack
[15:59] <popey> marcustomlinson: ok
[16:00] <popey> marcustomlinson: is there some magic to install that ppa, or just grab the deb and dpkg -i it, enough?
[16:00] <marcustomlinson> popey: that is enough yeah. Ensure you install unity-scope-click-departmentsdb, unity-scope-click-init-departments, and unity-scope-click
[16:01] <popey> ok
[16:04] <rvr> renatu: Is there any way to trigger bug 1577416?
[16:17] <popey> marcustomlinson: hard to say this solved it, given it doesn't always happen for me
[16:18] <marcustomlinson> popey: yeah this is a tricky one. I'm yet to see it at all myself
[16:20] <faenil> marcustomlinson: I don't see departmentsdb here https://code.launchpad.net/~unity-api-team/+archive/ubuntu/dev-build-1/+build/9713691
[16:21] <popey> faenil: https://code.launchpad.net/~unity-api-team/+archive/ubuntu/dev-build-1/+files/unity-scope-click-departmentsdb_0.1.1+16.04.20160415-0~444~ubuntu15.04.1_all.deb
[16:21] <marcustomlinson> faenil: yeah it ends up under the amd64 build (_all.deb): https://code.launchpad.net/~unity-api-team/+archive/ubuntu/dev-build-1/+build/9713690
[16:21] <faenil> ah ok, right
[16:22] <faenil> popey: cheers
[16:27] <faenil> marcustomlinson: at least after 1st reboot no problem, scope was populated
[16:36] <popey> faenil: marcustomlinson yeah, i rebooted a bunch of times and couldn't reproduce it. But typically for me it happens when on slow/rubbish networks
[16:36] <popey> Try it in the canonical office ㋛
[16:36] <marcustomlinson> popey: interesting. let me try edge
[16:37] <popey> Could be a coincidence of course
[16:37]  * faenil is in the office :)
[17:33] <rvr> renatu: re-ping
[17:59] <marcustomlinson> faenil, jibel, pmcgowan, popey: I'm gonna infer by the inability to reproduce an empty apps scope, that it might actually be resolved? Please let me know if you see it again. +This fix (hopefully) is ready in silo 54 now.
[18:00] <pmcgowan> marcustomlinson, just installed the PPA and doing a million reboots
[18:00] <pmcgowan> what did you change?
[18:01] <marcustomlinson> pmcgowan: there was only one significant change to the click scope since March: https://code.launchpad.net/~dobey/unity-scope-click/really-we-want-to-sign-all-the-requests/+merge/290763
[18:01] <pmcgowan> oy did we revert that again?
[18:01] <marcustomlinson> pmcgowan: yeah
[18:01] <marcustomlinson> It's a rocky one
[18:02] <pmcgowan> marcustomlinson, so I occasionally (one in 10) see a black scope then the icon then finally the scope contents
[18:02] <pmcgowan> so some other race as well
[18:03] <marcustomlinson> if you unlock quick enough I guess you'll catch the black screen before unity8-dash even starts
[18:03] <robru> slangasek: meeting?
[18:03] <pmcgowan> marcustomlinson, yeah but sometimes it takes like 10 secs vs no time
[18:03] <marcustomlinson> hmm
[18:03] <marcustomlinson> ok fair point.
[18:04] <pmcgowan> so it just worked but the contents filled in late, as opposed to the silo 71 fix to prepoulate
[18:04] <pmcgowan> its different every boot for me
[18:05] <pmcgowan> marcustomlinson, you didnt revert the prepoulate change did you?
[18:05] <marcustomlinson> pmcgowan: If you were on the lock screen for that 10s, then unlocked say 5s later, you'd have probably seen the scope populated
[18:05] <marcustomlinson> pmcgowan: no I didn'
[18:05] <marcustomlinson> didn't
[18:05] <pmcgowan> ok let me but more patient
[18:06] <pmcgowan> marcustomlinson, hmm still no
[18:06] <pmcgowan> black
[18:06] <pmcgowan> waited 10+secs
[18:07] <marcustomlinson> pmcgowan: that is really odd, the prepopulate is a unity-scopes-shell fix
[18:07] <pmcgowan> not saying its related
[18:07] <marcustomlinson> the only package I changed was the click scope
[18:07] <marcustomlinson> ah ok
[18:07] <pmcgowan> I occasionally saw it wihtout it
[18:07] <pmcgowan> just rebooting a lot right now :)
[18:07] <marcustomlinson> ha
[18:07] <pmcgowan> hmm
[18:08] <pmcgowan> most ervy time
[18:11] <renatu> rvr, hi
[18:12] <rvr> renatu: Hi
[18:12] <rvr> renatu: I am leaving now
[18:12] <rvr> renatu: I was waiting for feedback for silos 71 and 36
[18:13] <renatu> rvr, any problem with the silo 36?
[18:13] <rvr> renatu: I checked silo 71 and sync'd ok
[18:13] <rvr> renatu: ToyKeeper said "Did the fix for lp:1434576 (quick scroll) get left out? I don't see anything attached which looks like a fix for that, and I can still reproduce the issue with the silo installed."
[18:13] <rvr> But I really have to leave now
[18:14] <rvr> renatu: On 71, I was asking for a way to reproduce the fix, or check that it was fixed
[18:15] <rvr> Please, comment and I'll check when I return
[18:15] <renatu> ok
[18:15] <renatu> 71, there is no reliable way to reproduce the error
[19:05] <plars> Saviq: krillin-07 should be back now
[19:05] <Saviq> plars, thank you
[19:06] <plars> Saviq: happy to help
[19:13] <Saviq> plars, I'm afraid to say arale-01 does not have a good track record https://unity8-jenkins.ubuntu.com/computer/arale-01/builds :/
[19:14] <Saviq> all the red ones are some sort of connection issues afaict
[19:15] <Saviq> krillin, when it worked, was in a much better state https://unity8-jenkins.ubuntu.com/computer/krillin-07/builds (the most recent red ones were due to its recent failure, most of the ones before are actually "real" failures due to image issues)
[19:17] <plars> Saviq: same problem that you had with arale-03?
[19:17] <plars> Saviq: or just not recovering correctly?
[19:17] <Saviq> plars, it's difficult to say, the errors as surfaced are of all kinds, happening at random times - sometimes it won't flash, sometimes it will die mid-test
[19:18] <Saviq> plars, I might need to bring back some debugging into those jobs to see what's happening (tail -n100 syslog would maybe tell us if they are indeed usb issues)
[19:25] <plars> Saviq: I'm trying to recover arale-01 now, an it seems to be recovering at least
[19:28] <Saviq> plars, looking at the recent failed runs, none of them successfully flashed anything - be it during ./recover or later u-d-f
[19:29] <plars> Saviq: it seems to be in the middle of flashing a stable image with recover right now, I'll let you know how it goes
[19:29] <Saviq> plars, tx
[19:47] <plars> Saviq: arale-01 recovered just fine for me, but these aren't the only devices exhibiting weird behavior today. Rick will be back in the datacenter tomorrow and may be able to do some more hands-on investigation.
[19:55] <Saviq> plars, ack, let me run something on it
[20:24] <tedg> I thought if I needed a lib version that is in xenial in the vivid overlay I added it to source packages. Is that not correct? It didn't seem to grab it.
[20:28] <Saviq> tedg, you need to copy it, too
[20:28] <Saviq> tedg, trainguards and core devs have the rights to do it
[20:28] <tedg> Saviq: Ah, I didn't think I had a button for that :-)
[20:29] <tedg> Perhaps kenvandine can help me?
[20:29] <Saviq> I vaguely remember there was something like a crazy copy:source:destination syntax, not sure where that was though and/or if it's still available
[20:30] <kenvandine> tedg, you need a xenial package copied to a landing ppa?
[20:30] <tedg> kenvandine: Yes, whoopsie to landing 57 please
[20:33] <kenvandine> tedg, done
[20:33] <tedg> Cool, thanks kenvandine !
[20:33] <kenvandine> np
[20:33] <robru> Saviq: that never worked for this purpose. That was for copying from Ubuntu to ubuntu-rtm. Disabled for now because it stopped working and nobody noticed
[20:38] <tedg> Uhg, pyflakes3 isn't in Vivid :-(
[20:40] <robru> tedg: fun times. IIRC i once backported it to trusty and it built without needing to backport any of its deps so it was relatively easy
[20:41] <ToyKeeper> robru: Early warning, it looks like power use went up in the last couple images.  The increase coincides with the image when network-manager 1.2 landed, but I'm not sure if that's the cause.
[20:41] <tedg> Oh, really, I was figuring that was on the bad list.
[20:42] <tedg> kenvandine: Can you see if copying pyflakes works?
[20:42] <tedg> If not, I'll cut-and-paste the code I need.
[20:43] <robru> Well i dunno if we want pyflakes in the overlay ppa per se...
[20:43] <tedg> robru: It's only a build-dep
[20:43] <robru> ToyKeeper: can you file a bug? Thx
[20:43] <ToyKeeper> robru: Yes, already doing so.  Just wanted to mention that things might get bumpy.
[20:43] <robru> ToyKeeper: OK thanks
[20:44]  * tedg puts his tray table in the stowed position
[20:44] <robru> tedg: can you make it conditionally a build dep? Like only used in xenial or later?
[20:44] <kenvandine> tedg, i can copy it... if we agree we should :)
[20:45] <tedg> robru: Yes, we could.
[20:46] <tedg> That's fine, I don't know that this will really be used much of vivid. More of a desktop feature anyway.
[20:46] <kenvandine> tedg, so you don't need it?
[20:46] <robru> kenvandine: do you have an opinion on pyflakes being in overlay? I guess it wouldn't ship on the phone, not sure about other implications
[20:46] <tedg> Wait, how do I make a build-dep version dependent?
[20:46] <kenvandine> robru, no opinion
[20:46] <kenvandine> tedg, ?????
[20:47] <kenvandine> i've seen you do that many times
[20:47] <robru> tedg: you'd have to use the pre processing si that it appears in xenial but not vivid
[20:47] <kenvandine> oh
[20:47] <kenvandine> you mean series dependent
[20:47] <tedg> Yeah, that's ugly.
[20:47] <tedg> Wish there was a build-suggests
[20:47] <kenvandine> if we don't ship it, i don't mind copying it
[20:48] <tedg> kenvandine: We wouldn't, it is just used to check during the build of whoopsie
[20:48] <kenvandine> tedg, copied to silo 57
[20:48] <kenvandine> tedg, add it to the silo config
[20:49] <tedg> kenvandine: Will do, thanks!
[20:49] <kenvandine> np
[20:49] <kenvandine> i need to go do kid things... so harass me on telegram if needed :)
[20:49] <tedg> Will do, if there's a longer chain here, I'm giving up on this line.
[20:50]  * tedg is ready for the phone to be on Xenial already
[20:51] <Saviq> plars, no dice, it failed as soon as it started talking to it over ssh https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/159/console - /me will add some debugging info
[20:51] <robru> tedg: yeah me too
[20:51] <plars> Saviq: :(
[20:51] <plars> Saviq: rick will be back tomorrow, maybe he can see if there's some physical issue going on with those devices
[20:52] <Saviq> plars, ack, I'll try and get a bit more info about it
[20:55] <Saviq> plars, what else do you think could be useful http://pastebin.ubuntu.com/16324468/ ?
[20:56] <Saviq> adding "adb forward --list"
[20:57] <oSoMoN> ubuntu-qa: silo 38 has a fix for https://launchpad.net/bugs/1576639 , I know it’s past theoretical final freeze but I think the ratio benefit/risk is high, I’ve spent the day testing it extensively on 3 different devices, and if possible would like to have it included in OTA-11. Any chance of that happening?
[20:58] <oSoMoN> autopkgtests are currently running on that silo, it should be ready for QA validation soon
[20:59] <Saviq> plars, oh well, looking at syslog alone it's not looking great https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/161/console
[21:00] <Saviq> sry, wrong link https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/162/console
[21:08] <robru> oSoMoN: beg sil2100 i guess
[21:09]  * oSoMoN bows and begs sil2100
[21:10] <oSoMoN> I think pmcgowan and a bunch of others were keen on seeing that fixed in OTA11, too
[21:11] <ToyKeeper> oSoMoN: I'm probably not the right person to ask.  I don't even have a relevant device to try it on.
[21:12] <oSoMoN> ToyKeeper, any touch device will do (and even a desktop setup with not too much RAM in it, for that matter, as it’s not touch-specific code)
[21:14] <ToyKeeper> oSoMoN: Regardless, you'll need to ask someone who can approve an exception.
[21:14] <oSoMoN> ToyKeeper, understood, thanks
[21:15]  * oSoMoN heads to bed for now
[21:39] <plars> Saviq: it's worth checking, but honestly we don't normally see too much of use even in syslog
[21:40] <Saviq> plars, sure, just saying there's a lot of usb-related problems reported there
[21:41] <Saviq> plars, "Slave went offline" happens too often, too - and that's about heymann IIUC, not about the phone?
[21:41] <Saviq> https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/162/console
[21:41] <Saviq> happened twice today
[21:42] <renatu> rvr, ping
[21:47] <plars> Saviq: I do see that the jenkins slave restarted around that time, but there's no error or crash or anything, so it's not clear why
[21:47] <Saviq> plars, ack
[21:49] <plars> hmm, there's a phone I don't know about plugged into that system
[23:59] <cjwatson> tedg: you can always build-depends: thing-new-in-xenial | base-files
[23:59] <cjwatson> tedg: trade-off is that if it's transiently uninstallable or something then you may (or may not) find the build-dependency just gets (effectively) ignored when you wanted it to fail


[21:07] <hggdh> Q: if I move my c-i bug to private, who will have access to it? Just the c-i team, or others?
[21:44] <powersj> hggdh, if I recall if you change it to "private" the maintainers of cloud-init will have access i.e. https://launchpad.net/~cloud-init-dev
[21:45] <powersj> if you move it to private security, the Canonical security team + maintainers will see it
[21:45] <powersj> I believe that is how it works, but I'm not 100% certain
[21:48] <Odd_Bloke> That matches my understanding, with the addendum that subscribers to a bug are also granted access; I've asked for clarification from LP folks, to be sure.
[21:52] <hggdh> this matches my understanding, but I pretty much only worked on Ubuntu bugs, not with upstream; I was not sure if on upstream bugs the subscribers would also have access
[21:52] <hggdh> thank you
[21:54] <Odd_Bloke> falcojr: I'm going to ask Lucas to review too (because I'm modifying/removing code that he added for a UA use case) but your review from a cloud-init perspective on https://github.com/canonical/pycloudlib/pull/114 would be appreciated.
[22:04] <falcojr> LGTM, but I'll take a closer look tomorrow
[22:28] <Odd_Bloke> Thanks!
[23:34] <AU-S2S> Trying to launch Debian 10 on AWS EC2 via a launch template. I want to keep the user_data as simple as possible by pulling the cloud-config from a URL (Repository).
[23:34] <AU-S2S> Am I missing something or is it really as simple as:
[23:35] <AU-S2S> #cloud-config
[23:35] <AU-S2S> bootcmd:
[23:35] <AU-S2S> - #include <url>
[23:36] <AU-S2S> ??
[23:36] <AU-S2S> where the <url> links to a valid YAML