[05:51] <hikiko> hi
[08:20] <flexiondotorg> Morning hikiko
[08:21] <hikiko> morning flexiondotorg
[08:23] <didrocks> hey flexiondotorg, hikiko
[08:23] <flexiondotorg> Morning didrocks
[08:25] <hikiko> hi didrocks
[08:38] <Sweetshark> morning all
[08:40] <hikiko> morning Sweetshark
[08:41] <hikiko> :)p
[08:55] <willcooke> morning all
[08:59] <Laney> hey hey
[08:59] <willcooke> ahoy Laney
[08:59] <willcooke> Beautiful day today
[09:01] <Laney> hey willcooke
[09:01] <Laney> it is!
=== davmor2_ is now known as davmor2
[09:04] <Laney> https://youtu.be/4OESp5Sts4s?t=14s
[09:04] <willcooke> :)
[09:04]  * Laney used to think that was "drinks and gravy in the park"
[09:04] <Laney> ahh, bisto
[09:05] <davmor2> Morning all
[09:05] <willcooke> hi davmor2
[09:06] <seb128> good morning Sweetshark willcooke Laney
[09:06] <davmor2> Laney, seb128, willcooke: was there a new version of software updater pushed out seems the details view is only one line thick again
[09:06] <willcooke> I want to buy an attachment for the hoover for hard floors.  Dyson want 35 quid for a bit of plastic.  True story.
[09:06] <seb128> davmor2, what distro serie?
[09:07] <seb128> willcooke, they know how to make money :-/
[09:07] <Laney> willcooke: 3d printer!
[09:07] <davmor2> seb128: zesty it was fixed to 200px iirc with flexiondotorg patch that barry landed but now it is down to one line again
[09:08] <seb128> davmor2, dpkg -l | grep aptdaemon?
[09:08] <seb128> davmor2, that version is stil in zesty-proposed it seems
[09:08] <seb128> did out test out of proposed before and reinstalled without that pocket?
[09:09] <seb128> libsecret autopkg issues blocking it
[09:10] <davmor2> seb128: ah I might of tested the fixed package that might be the reason
[09:10] <seb128> which probably has nothing to do with the change
[09:10] <seb128> I pinged barry about it
[09:10] <Laney> libsecret isn't blocking aptdaemon, it's aptdaemon itself
[09:10] <desrt> good morning everyone!
[09:11] <Laney> hey seb128!
[09:11] <Laney> hey desrt!
[09:11] <desrt> hi laney :)
[09:11] <seb128> hey Laney :-)
[09:11] <Laney> what's up
[09:11] <seb128> ups
[09:11] <desrt> seb128: hi!
[09:11] <seb128> I hit the wrong line
[09:11] <seb128> Laney is right
[09:12] <desrt> Laney: not much.  looking forward to a relatively relaxing day.  think i will stay home tonight, even
[09:12] <seb128> still probably not due to the change
[09:12] <seb128> but some look real issue, maybe packagekit version changed or bindings did
[09:12] <seb128> barry should sort it out...
[09:22] <Laney> desrt: nice
[09:22] <Laney> we're supposed to be singing at the folk club tonight
[09:27] <seb128> Laney has a busy life :-)
[09:27] <seb128> pub quiz yesterday, climbing and singing tonight
[09:27] <Laney> yep
[09:28] <Laney> won't be doing very much for the rest of the week though (H)
[09:28] <willcooke> Laney, seb128 - what are your thoughts on this bug:  https://bugs.launchpad.net/oem-priority/+bug/1667222
[09:28] <ubot5> Ubuntu bug 1667222 in OEM Priority Project "set password in "user accounts panel' won't remove user from "nopasswdlogin" in all cases" [Critical,Confirmed]
[09:28] <willcooke> low priority ^
[09:30] <seb128> willcooke, it seems a bit annoying ... it's somewhat similar/has to do with the one Laney fixed no?
[09:30] <Laney> I'm sure there are some other problems there
[09:30] <seb128> or at least the "user not removed from nopasswd"
[09:30] <seb128> did we SRU that fix to xenial btw?
[09:30] <Laney> the group thing is okay I think, but switching between the modes is a bit ropey
[09:30] <Laney> yes
[09:30] <seb128> great
[09:31] <Laney> might be waiting verification still
[09:31]  * seb128 looks
[09:31] <seb128> yeah, still in proposed
[09:31] <willcooke> so you think that setting a new password should indeed remove the user from the nopasswd group?
[09:32] <seb128> well if you have a password then you are not *no*passwd...
[09:32] <Laney> I think the testcase I gave in the SRU bug that I fixed is fixed
[09:32] <Laney> I don't claim that all bugs around nopasswdlogin are gone
[09:32] <seb128> right
[09:33] <seb128> that's what is writing on the SRU bug comments
[09:33] <willcooke> yeah, the original problem is fixed
[09:33] <seb128> they made it verification-done and opened the other one as a follow up
[09:33] <Laney> like,
[09:33] <seb128> but the appdata one failed verification
[09:33] <Laney> be in nopasswdlogin, open u-c-c, weird shit happens
[09:33] <seb128> which is what is blocking the SRU :-/
[09:33] <Laney> I can believe that
[09:35] <willcooke> seb128, while we're waiting to see what is going on with livepatch, would you be able to see if we can get that sorted out? ^
[09:35] <Laney> well maybe Robert can have a look at his fix and decide if it should go in anyway or if he can fix it up or if he needs to revert it
[09:36] <seb128> robert_ancell, ^
[09:36] <Laney> woah
[09:36]  * Laney isn't used to that guy being on IRC when he is
[09:36] <seb128> yeah, I was surprised to see his nick on the channel :p
[09:37] <seb128> willcooke, "that" being the stucked SRU or the new problem?
[09:38] <willcooke> seb128, I guess both really :)
[09:38] <seb128> willcooke, but yeah, I'm going to have a look to that new one, it's not an option used often I think and not really a security issue but it could mislead users to think their account is locked when it's not which is not nice
[09:38] <seb128> let's see what robert_ancell says about the SRU
[09:38] <willcooke> thanks chaps
[09:38] <Laney> thx
[09:39] <seb128> yw!
[09:39] <willcooke> I think I worked out whats wrong with my printer
[09:39] <Laney> seb128: all those code paths are a bit annoying btw
[09:39] <willcooke> there is a
[09:39] <Laney> lemme know if you want me to review your fix :-/
[09:39] <seb128> Laney, thanks, reviews are always welcome!
[09:39] <Laney> also I think upstream just removed the nopasswd stuff
[09:39]  * robert_ancell forgot to close XChat...
[09:39] <seb128> lol
[09:39] <Laney> run
[09:40] <seb128> night robert_ancell
[09:40] <seb128> :-)
[09:40] <willcooke> *an electric motor inside which seems to drive some belt connected to the big transfer drum.  It seems to be jammed and getting very hot, so I think it's just broken.   A new part > cost of a new printer.
[09:40] <willcooke> night robert_ancell :)
[09:41] <Laney> willcooke: can you get it out?
[09:41] <robert_ancell> Laney, what was my fix?
[09:41] <Laney> appdata for u-c-c
[09:42] <Laney> the bug got verification-failed
[09:42] <willcooke> Laney, no, it's really annoying - the mounting seems to be moulded in and so getting just the motor out would break the plastic supporting the rest of the gubbins.
[09:42] <robert_ancell> oh, I was looking at the nopasswd bug
[09:42] <Laney> heh
[09:43] <robert_ancell> night all!
[09:46] <davmor2> willcooke: just buy an Air Ram mk2 if you need to vac ceilings get a multi too and be done ;)
[10:12]  * Sweetshark tried kvm/virt-manager and feels stupid about having VirtualBox around still.
[10:23] <seb128> Sweetshark, what's wrong with virtualbox?
[10:23] <seb128> Sweetshark, oh btw how did that ppa upload from yesterday go? build is done?
[10:26] <Sweetshark> seb128: 5.2.6/yakkety is smoketested and moved to the libreoffice ppa, 5.3.1/zesty is uploaded and currently building in a personal ppa. 5.3.1 snap was also updated, succeeded on amd64, broke on armhf due to infra, broke on i386 in a test, but maybe a heisenbug. retried armhf, i386.
[10:27] <seb128> k
[10:27] <seb128> Sweetshark, let me know if/when you need sponsoring for something
[10:30] <Sweetshark> seb128: willdo.
[10:31] <Sweetshark> seb128: compared to vbox, kvm is just much smoother in desktop/video emulation for me for starters. installs were also really quick, so IO might be better too. but that might also just be my new hardware.
[10:31] <seb128> I should give it a try again
[10:34] <Sweetshark> seb128: also thorsten from #libreoffice-dev showed me he can boot into his native windows dual-boot install from the running linux, which is quite cool.
[10:35] <seb128> that sounds useful
[10:36] <Sweetshark> seb128: He said the only tricky thing is not to miss the grub menu, because booting into the linux install that you are currently running causes some confusion between host and guest.
[10:37] <Sweetshark> "Yo dawg, We heard you like linux, so we put your linux in your linux ..."
=== hikiko is now known as hikiko|ln
=== dandrader is now known as dandrader|afk
=== hikiko|ln is now known as hikiko
=== dandrader|afk is now known as dandrader
[13:43] <tedg> Laney: So I have a silo building (failing on PPC) that has UAL without Upstart, but it's still blocked on s390x because of other deps.
[13:44] <tedg> Laney: Do you want my to try to get those in the same silo or do you want to do "archive magic" to do rebuilds later?
[13:44] <xnox> tedg, what silo? =) can i look?
[13:45] <tedg> xnox: No, it's for Laney only.
[13:45] <tedg> xnox: https://bileto.ubuntu.com/#/ticket/2577
[13:45] <Laney> hi tedg
[13:45]  * xnox is *sad*
[13:45] <Laney> Nice one
[13:47] <Laney> tedg: It comes down to u-s-s?
[13:47] <tedg> Laney: Yeah, I've pinged kenvandine about that one and he's looking into it.
[13:47] <xnox> tedg, powerpc should be dropped as an architecture anyway; and s390x should not have ual as we don't support clicks/desktop there at all
[13:48] <Laney> Stop it please
[13:48] <Laney> tedg: Thanks, ok, sounds good
[13:48] <Laney> You can upload the things into the silo to see if they work
[13:48] <tedg> xnox: Well, I'm not going to argue those points. But from an academic perspective, my stuff shouldn't break there either. :-)
[13:48] <kenvandine> on my todo list for this morning
[13:49] <xnox> tedg, right, imho then powerpc/s390x builds should be libertine-less as we don't support graphical desktops on those arches anymore.
[13:49] <tedg> xnox: Also, FWIW, this silo drops click support as well ;-)
[13:49] <xnox> or at least we have for sure not ported libertine, nor tested it on powerpc & s390x
[13:49] <Laney> xnox: We don't add arch-specific hacks all over the archive
[13:50] <Laney> Can you please leave it?
[13:50] <Laney> We're close to getting this fixed now
[13:50] <tedg> For the record, if someone wanted to get me an s390x rack I could use as a desktop, I'd be happy to dogfood it :-)
[13:50] <xnox> lol, ok.
[13:50] <kenvandine> *happily* :-D
[13:50] <xnox> Laney, ok
[13:51] <Laney> thx
[13:52] <Laney> tedg: kenvandine: I'll be off tomorrow and Friday, so if you could check that you can get gtk built against this then please feel free to publish
[13:52] <kenvandine> sure
[13:52] <Laney> after uss is fixed I would hope that libertine and then ual should get builds automatically
[13:52] <Laney> assuming there's no other problem
[13:54] <kenvandine> tedg, does this silo also fix the issues renatu was talking about with app starting when dbus-user-session is installed?
[13:54] <tedg> kenvandine: Yes
[13:55] <kenvandine> woot
[13:55] <renatu> wow \o/
[13:55] <tedg> kenvandine: When it's not installed though, right?
[13:55] <kenvandine> application starting is sort of important :)
[13:55] <kenvandine> the issue was when dbus-user-session was installed
[13:56] <renatu> tedg, yes after install dbus-user-session the apps does not start from content-hub anymore.
[13:56] <tedg> Okay, perhaps I'm confused then. It fixes the issue of dbus-user-session not being installed, which ual needs.
[13:56] <kenvandine> yeah, that's not the issue i was talking about
[13:56] <renatu> tedg, did you remember that you told me that the env vars could be wrong
[13:56] <tedg> Yeah, but that's a content-hub issue.
[13:57] <renatu> tedg, but only happens after install  dbus-user-session
[13:57] <tedg> Yes, it happens when content-hub is using systemd instead of upstart.
[13:57] <tedg> Upstart has the environment of the full graphic session because it is once per session, where systemd is once per user.
[13:58] <renatu> humm I tought that was transparent for content-hub
[13:58] <tedg> So we have to include more environment.
[13:58] <kenvandine> to be clear, content-hub is using UAL
[13:58] <kenvandine> we don't use systemd directly
[13:58] <tedg> That environment is getting taken from the launching process.
[13:58] <kenvandine> or is it the exec-tool?
[13:58] <tedg> Which *should* be the same for everyone. But somehow must be different.
[13:59] <tedg> kenvandine: Wait, are we talking "applicaiton launching" or "untrusted helper launching" ?
[13:59] <kenvandine> i think it's both
[13:59] <kenvandine> renatu, right?
[13:59] <kenvandine> renatu, it's an issue with both importing and exporting?
[13:59] <renatu> kenvandine, let me try. I am not sure
[14:00] <kenvandine> Laney, https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/no_upstart/+merge/319926
[14:00] <kenvandine> Laney, perhaps you can review that
[14:01] <kenvandine> the upstart build depends was synthetic, looks like Mirv added that just to keep it from building on those arches
[14:04] <renatu> kenvandine, tedg: works to pick a file (dbus-user-session)
[14:04] <kenvandine> ok
[14:04] <kenvandine> so the untrusted helper launching does work
[14:04] <renatu> kenvandine, ted: but does not work to export
[14:04] <kenvandine> it's just the app launching that doesn't
[14:05] <renatu> kenvandine, what is the diff?
[14:05] <kenvandine> export just uses UAL to launch the app
[14:05] <kenvandine> importing uses the untrusted helper to setup a trust session and launch the app
[14:05] <kenvandine> it's a little different
[14:05] <kenvandine> so the trust session works, so woot
[14:05] <tedg> So this branch changes that :-)
[14:05] <kenvandine> simple app launching doesn't...
[14:06] <tedg> It makes the helpers use systemd as well.
[14:06] <kenvandine> tedg, so i wonder if you are breaking content-hub :)
[14:06] <kenvandine> i'll test that with the silo
[14:06] <tedg> Cool.
[14:06] <kenvandine> tedg, i'm going to build uss in the silo, want me to rebuild ual too?
[14:06] <tedg> kenvandine: Give me two minutes...
[14:07] <kenvandine> ok
[14:07] <kenvandine> tedg, i'll let you kick the build tne
[14:07] <kenvandine> then
[14:07] <tedg> K, trying to find a fix for these powerpc failures.
[14:24] <davmor2> willcooke: do you know when the new slide artworks is likely to land?  Still got the Yak on installer slides
[14:24] <willcooke> davmor2, I just branched the code
[14:24] <davmor2> willcooke: awesome thanks
[14:25] <willcooke> in anticipation of the graphics hitting my inbox in the next few mins
[14:25] <willcooke> davmor2, should be the next hour or so
[14:25] <davmor2> willcooke: so should be in tomorrows iso right?
[14:26] <willcooke> davmor2, depends on how charitable xnox is feeling :)
[14:27] <davmor2> willcooke: between you saying please and me shouting DO IT NOW DAMN YOU! should be good ;)
[14:27] <xnox> willcooke, did you vote remain?
[14:27] <davmor2> xnox: did you?
[14:27] <xnox> of course
[14:27]  * willcooke is wearing a Union Jack as a shirt and drinking lager at 2:30pm 
[14:28] <xnox> willcooke, with or without scottish flag union jack?
[14:28]  * willcooke <- not a xenophobe 
[14:28]  * xnox wants dragon on top of union jack
[14:29] <davmor2> willcooke: I think you'll find that is a Union Flag unless it is on a ship :P
[14:29] <willcooke> davmor2, damn it, I nearly put "flag"
[14:29] <willcooke> I knew someone would point that out :)
[14:29] <davmor2> xnox: don't give George another target damn you I like dragons
[14:30] <davmor2> willcooke: I like the title pedant :D
[14:34] <davmor2> xnox: https://www.youtube.com/watch?v=86MO-JWTNjo I think that is Mays official response right?
[14:37] <xnox> more like this: https://www.facebook.com/999BABF/posts/1417849411607460:0
[14:44] <tedg> kenvandine: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2577/+build/12129615
[14:44] <tedg> kenvandine: Can we drop U1 auth as well?
[14:44] <tedg> kenvandine: I think it doesn't work...
[14:45] <kenvandine> tedg, in uss?
[14:48] <tedg> kenvandine: I thought all the u1auth stuff was now macaroons.
[14:48] <kenvandine> i haven't looked at any of that
[14:48] <tedg> I might be confused, but I thought dobey was trying to move out of libu1auth everywhere.
[14:48] <kenvandine> i think we only use it in the updates panel
[14:48] <tedg> Yeah, you need to talk to snapd for that now.
[14:48] <kenvandine> right
[14:48] <tedg> Well and apt.
[14:49] <kenvandine> so all of that can be removed for now
[14:49] <kenvandine> jgdx, ^^
[14:49] <kenvandine> tedg, what about system image?
[14:49] <tedg> kenvandine: snapd
[14:49] <tedg> There is no system image
[14:49] <tedg> snapd ate it.
[14:49] <kenvandine> right, i'm thinking we just remove the updates panel completely
[14:50] <kenvandine> for now
[14:50] <tedg> Well, I imagine you'll want the same QML, just a different model.
[14:50] <kenvandine> yeah, but until we have time to port that
[14:50] <kenvandine> we can just disable building it
[14:50] <tedg> The updates made it look really nice, would hate to lose that :-)
[14:50] <jgdx> kenvandine, yes to that
[14:51] <kenvandine> porting that panel isn't on our backlog
[14:51] <jgdx> we want to use some qml bits from it in the apt-based one, but other than that…
[14:51] <kenvandine> but it should be
[14:53] <dobey> do what
[14:54] <dobey> kenvandine: yeah you should just get rid of the updates panel entirely now
[14:54] <kenvandine> i'll prepare a branch that does that
[14:56] <dobey> i don't think we want to spend time writing a bunch of code to have apt updates in u8 system settings do we?
[14:56] <kenvandine> dobey, i don't think we know right now
[14:57] <dobey> current update-manager should work under unity8 i think; might need a little tweaking to ensure it's getting started in that session though
[14:57] <dobey> whatever does the popping up of it and such, that is
[15:16] <dobey> ouch. $600+ for 64GB DDR4 :-/
[15:24] <Laney> tedg: you dont have to care about ppc; it's going away and britney already ignores it
[15:26] <tedg> Laney: I think I fixed it :-)
[15:26] <Laney> good, if it indicated a real bug :P
=== dandrader is now known as dandrader|afk
[15:46] <dobey> Laney, willcooke: can we just make gtk+ not build the mir back-end on s390x?
[15:47] <Laney> "can" yes, "should" no
[15:47] <Laney> these upstart dependencies have to be sorted out anyway
[15:48] <dobey> yes, but support mir/unity8 stuff on s390x is an oxymoron
[15:48] <Laney> support upstart into the future becomes one too
[15:49] <dobey> i'm not talking about supporting upstart
[15:49] <Laney> adding technical debt into the gtk+3.0 package doesn't seem like fun either
[15:49] <Laney> doing what you want just kicks the can down the road
[15:49] <Laney> you are going to have to unwind the upstart stuff at some point
[15:50] <dobey> upstart is irrelevant to what i'm saying
[15:51] <Laney> it is the reason you are asking me to insert a hack into the gtk3 package
[15:51] <dobey> no
[15:51] <Laney> what is causing the problem then
[15:51] <dobey> the reason i'm asking is because mir/unity8 on certain architectures makes absolutely no sense
[15:52] <Laney> that's not how the archive works
[15:53] <Laney> what you're finding out now is that adding a pile of hacks to work around an upstart bug on s390x is a painful experience to undo
[15:54] <Laney> and I am to blame too, because I added the one to ubuntu-system-settings
[15:54] <dobey> no, what i'm finding out is that we care more about building on architectures that don't make sense, than being efficient
[15:56] <Laney> You're wrong, and you don't want to listen to what I'm saying.
[15:57] <Laney> I'll upload ubuntuone-credentials.
[15:58] <dobey> upload it to what?
[15:58] <dobey> no i am not wrong. and you don't want to listen to what i'm saying.
[15:59] <dobey> why would you upload ubuntuone-credentials?
[15:59] <dobey> we want to remove it from the archive, not add more architectures to it
[15:59] <dobey> it needs to die
[16:00] <Laney> Sounds good to me, feel free to make its dependencies not be depdencies
[16:01] <dobey> system-settings is getting rid of it per previous discussion
[16:05] <xnox> imho we actually do need gtk+3.0 on s390x with support for xvfb and remote-forwarded X11 server
[16:05] <dobey> xnox: yeah, but mir?
[16:05] <xnox> but we are not commiting to support it; or run either unity7 or 8 on it.
[16:05] <seb128> dobey, but mir is build/available on s390x
[16:06] <seb128> built
[16:06] <dobey> yeah, but it's a pointless build
[16:06] <xnox> ideally one wants similar gtk3+ to other arches, to lower any maintaince costs
[16:06] <seb128> that
[16:07] <seb128> and why not having it if it's not extra cost? it might be useful to some people some day
[16:07] <dobey> it is extra cost
[16:07] <seb128> which one?
[16:08] <seb128> having s390x builders to idle a bit less?
[16:08] <dobey> how many developers have s390x or ppc64 boxes sitting on there desk? where's the hardware to run our CI on them?
[16:09] <seb128> in the datacenter
[16:09] <seb128> as for other archs?
[16:09] <dobey> no
[16:09] <xnox> dobey, most of our mainframe is not utilised; and actually s390x works as a great canary as it finishes builds before anything else most of the time.
[16:09] <dobey> not launchpad builders, CI for developers
[16:09] <xnox> dobey, add a worker to your jenkinsaas environment?
[16:10] <seb128> dobey, you are speaking for the mir team there?
[16:10] <dobey> where are my jenkins nodes that are s390x and ppc64
[16:10] <xnox> dobey, ppc64 are in scalingstack & s390x are coming.
[16:10] <dobey> why do i have to care if my software keeps building on s390x, when it will NEVER be run on that architecture?
[16:10] <xnox> dobey, e.g. juju teams; hwe; server teams are all running slaves in their jenkins on both ppc64 and s390x
[16:11] <xnox> dobey, because we have reverse-dependcy chains to build (eventually) source packages that are useful in their command-line equivalent.
[16:11] <xnox> for example we had to build qt, to build cmake, to build a bunch of command-line utilities and server daemons that use cmake.
[16:11] <xnox> ditto with gtk+3.0, we need it because there are useful command-line tools that link with gtk+3.0
[16:11] <dobey> yeah, but choosing to add a new dependency to something that doesn't build on an archtecture where you normally build, doesn't mean the thing you depend on needs to change. it means you need to make it optional
[16:11] <xnox> ditto e.g. mir -> it's in the stack for u-a-l which can be used to launch s390x snaps from command line
[16:12] <dobey> so when is the mir team going to provide remote terminal support for mir so i can run it as a thin client? or forwarding of mir over ssh?
[16:12] <xnox> dobey, we've tried that, but the dependency cycles are weird and instead of redoing the chains of optional builds; it's cheaper and easier to just build everything and use the parts that are useful.
[16:13] <xnox> dobey, and acutally e.g. hwe; certification; java; toolchain teams have been asking for unity7 or unity8 support on s390x for java test-suite validation, etc.
[16:13] <xnox> such that e.g. if mir forwarding over ssh works; we may would actually want to have that supported on s390x for niche certification stuff.
[16:14] <xnox> so far i have been pushing back on that.
[16:14] <xnox> because we are clearly not in the position to support that with trivial amount of cost. but we should not be slashing our wrists over it as well by making parts of the archive not build at all, artificially
[16:39] <willcooke> desrt, hey! Would you be able take a look at these MPs and sanity check for GMenuModel?
[16:40] <willcooke> https://code.launchpad.net/~aacid/qtubuntu/aboutToShow/+merge/319080
[16:40] <willcooke> https://code.launchpad.net/~aacid/qmenumodel/aboutToShow/+merge/319078
[16:41] <desrt> willcooke: sure.
[16:42] <willcooke> desrt, no immediate hurry, merci
=== dandrader|afk is now known as dandrader
[17:57] <willcooke> davmor2, xnox - squeek squeek, the mouse is here!
[17:58] <willcooke> https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu-zesty/+merge/319962
[18:01] <Laney> BYEEEEEEEEEEEEEEEEEEEEEEEEEEEEE PALS
[18:02] <willcooke> have a nice weekend Laney
[18:02] <Laney> thx, will do!
[18:02]  * Laney is going to be So Mindful
=== dandrader is now known as dandrader|afk
[18:22] <davmor2> Enjoy Laney
[18:22] <davmor2> willcooke: \o/
[18:23] <seb128> have a nice evening desktopers, Laney, enjoy the long w.e!
[18:24] <willcooke> I'm off too, night all
=== dandrader|afk is now known as dandrader
[18:47] <Sweetshark> libreoffice 5.3.1~rc2 compiled and build successfully to private ppa, running autopkgtests in a local VM right now.
[18:49] <sarnold> Sweetshark: do you have good visibility into how many items the clusterfuzzer has found, how many cpu hours they've spent fuzzing, etc?
[18:49] <Sweetshark> (in a shell on desktop, not exactly an adt-testbed, but it should be good enough)
[18:51] <Sweetshark> sarnold: I should be able to find out items found, cpu hours spent would require me to do some digging (if that is even knowable outside GOOG)
[18:52] <sarnold> Sweetshark: ah, don't bother then; it's an idle curiosity, not worth spending time on it
[18:52] <sarnold> Sweetshark: thanks
[19:23] <Sweetshark> subsequentcheck and manual test succeeded for 5.3.1 build
=== ayan is now known as Guest18912