[12:24] <mterry> lpotter, did you ever get sorted with testing u8 on your device?
[12:50] <tedg> Saviq, Is there instructions on how to build qtmir in a silo? /me forgot again.
[12:50] <tedg> Messing up the twin, rebuild, etc.
[12:54] <Saviq> tedg, first, build with IGNORE_MISSING_TWINS
[12:55] <Saviq> tedg, then prep an MP of lp:~mir-team/qtmir/gles-sync with the version and silo number updated, like so: https://code.launchpad.net/~mir-team/qtmir/gles-sync/+merge/238123
[12:56] <Saviq> tedg, add that to the silo, build qtmir-gles alone
[12:57] <tedg> Hmm, okay. Seems the twins build is missing a version.
[12:58] <tedg> Saviq, It seems there's extra revisions that are in https://code.launchpad.net/~mir-team/qtmir/rtm-14.09 that aren't in trunk.
[12:58] <tedg> (releases)
[12:59] <tedg> Saviq, Should I merge rtm-14.09 into my branch and land onto there?
[13:03] <Saviq> tedg, right, we need to resolve that
[13:05] <tedg> Saviq, So, do you want me to do that? Or are you going to?
[13:07] <Saviq> tedg, we will, need to grok what exactly needs to happen
[13:09] <tedg> Saviq, Sure, do you want to use my silo? I've got rtm silo 2 to try and land a qtmir branch.
[13:10] <Saviq> tedg, I think I could use mine for unity8, just can't take care of this right now, will have some free time around 10
[13:11] <tedg> Saviq, K, works for me. Also can you add this to your U8 silo? https://code.launchpad.net/~ted/unity8/dash-oom-score/+merge/238888
[13:12] <Saviq> tedg, already done, it's WiP still, though
[13:12] <Saviq> tedg, that's safe to land without your qtmir branch anyway, right?
[13:13] <tedg> Saviq, Correct, let me change the status.
[13:13] <tedg> Saviq, It'll set the value and qtmir will change it today.
[13:21] <Saviq> mzanetti, bug #1383782 is a dupe... but guess what, can't find it :P
[14:13] <paulliu> kgunn: Do we have a similar page for unity8. https://unity.ubuntu.com/contact-us/
[14:14] <paulliu> kgunn: this page seems to majorly for unity7.
[14:30] <liuxg> pete-woods, ping
[14:30] <pete-woods> liuxg: hi
[14:30] <liuxg> pete-woods, are you available now?
[14:30] <pete-woods> liuxg: yes, sure
[14:31] <liuxg> pete-woods, OK. thanks. which room?
[14:31] <pete-woods> liuxg: dallas
[16:05] <dandrader> dednick, Saviq do we still want this as we should be targetting only trunk nowadays? https://code.launchpad.net/~nick-dedekind/unity8/edges-demo-indicator-improvements/+merge/238698
[16:06] <dednick> dandrader, Saviq: deleted
[16:13] <tsdgeos> larsu: can you write in https://code.launchpad.net/~larsu/unity8/stop-using-statusicon/+merge/234502 the required branch for it to work?
[16:14] <larsu> tsdgeos: sure
[16:14] <tsdgeos> larsu: description if possible
[16:15] <larsu> tsdgeos: of what? The branch has commit messges and an MR with some discussion
[16:18] <tsdgeos> larsu: i meant in the descirption of the MR :D
[16:18] <tsdgeos> i shall be more verbose
[16:18] <tsdgeos> larsu: i'll put it there
[16:18] <larsu> tsdgeos: oh, ok :)
[16:19] <tsdgeos> larsu: actually to be bureaucrazy proper you should put https://wiki.ubuntu.com/Process/Merges/Checklists/Unity8 into your description
[16:22] <larsu> tsdgeos: rather, I should stop MRing stuff to unity8 and let you guys deal with breakages from the toolkit :P
[16:22] <larsu> too much process over here
[16:22] <tsdgeos> larsu: i'm not the bureaucrazy guy
[16:22] <tsdgeos> tell Saviq ;)
[16:23] <tsdgeos> larsu: besides the toolkit should just not break
[16:23] <tsdgeos> we're supposed to have third party people using it ;)
[16:23] <larsu> tsdgeos: this was a change Saviq requested...
[16:23] <tsdgeos> sure sure
[16:23] <tsdgeos> that's fine
[16:23] <larsu> and we're still in the unstable phase, no?
[16:23] <tsdgeos> for a few days more, yep
[16:24] <larsu> ah, rght :)
[18:15] <mzanetti> Saviq: ok... issue: using urihandler focuses the app immediately
[18:15] <mzanetti> Saviq: but we need to switch it to the scope behind the other app, without switching
[18:16] <mzanetti> I'm afraid we can't get rid of DashCommunicator
[18:17] <mzanetti> tedg: or is there a way to dispatch something with urihandler without actually focusing the app? ^^
[18:52] <mzanetti> tsdgeos: I guess this is it then, at least for now https://code.launchpad.net/~mzanetti/unity8/setCurrentScope-index/+merge/239268
[18:54]  * tsdgeos reads
[19:17] <tsdgeos> Wellark: so were are we having that hud event? :D
[19:22] <tsdgeos> Cimi: ping
[19:31] <lpotter> mterry: no, still stuck with the equivs package missing
[19:37] <mterry> lpotter, it will be forever missing
[19:37] <lpotter> ok
[19:37] <mterry> lpotter, I recommend just building on device
[19:41] <lpotter> that's what I am trying to do, but ./build.sh -s needs equivs package :)
[19:43] <lpotter> that also misses lcov and gconvr seems to not be there as well
[19:44] <lpotter> gcovr
[20:06] <tsdgeos> dandrader: https://code.launchpad.net/~aacid/unity8/remove_unused_end/+merge/239294
[21:06] <Saviq> mterry, fun times 1384419
[21:06] <Saviq> bug #1384419
[21:06] <mterry> Saviq, that's...  by design?
[21:06] <Saviq> mterry, yeah, I know
[21:07] <mterry> Saviq, do we care about that bug?
[21:08] <seb128> greyback, http://paste.ubuntu.com/8632284/
[21:37] <greyback> seb128: hmm, it's blocked on trying to create a dbus connection :(
[21:46] <seb128> greyback, does that make any sense to you?
[21:53] <greyback> seb128: I've seen it a few times unfortunately. But I've no idea why unity8-dash fails to make a connection with the dbus server.
[21:53] <greyback> and I'm unable to reproduce it reliably
[21:56] <seb128> yeah, I can't either
[21:58] <greyback> seb128: I'd need someone with dbus skills to help out with it. Do you know who would be a good person to ask?
[21:59] <seb128> greyback, desrt?
[21:59] <greyback> when it happens, dbus-monitor is printing both session and system messages
[21:59] <greyback> seb128: noted, thanks]
[22:02] <seb128> greyback, desrt guess "code trying to access the same dbus connection from more that 1 thread"
[22:03] <seb128> greyback, but he seems tired and doesn't want to think more about it today
[22:03] <seb128> greyback, I can try to ping him again tomorrow


[13:54] <foo> If I want to copy files from local drive to portable drive, and if I want to remove on source as copying, I think I want rsync -av --remote-source-files source/ destination/ - correct?
[14:02] <sdeziel> foo: sounds right. When in doubt with rsync, you can always add `-vni` for verbose, dry-run and itemize-changes
[14:02] <foo> ! Thanks
[14:03] <foo> ubottu: I wasn't thanking you, I was thanking sdeziel and his real humanness
[14:05] <sdeziel> foo: you are welcome :)
[15:18] <foo> sdeziel: I think I actually want: --delete-after          receiver deletes after transfer, not before ... if I want to delete files after they're transferred on source (eg. trying to free up space on my source drive and move things to destination)
[15:21] <sdeziel> foo: I think --delete-after is meant to cleanup the destination to remove files that were not in the source to begin with. Maybe you just want to `mv` the stuff from your source to your destination?
[15:44] <esv> it is always good to test with a small sample of files that you don't care losing
[15:58] <foo> sdeziel: yes, I'll look into move, thank you
[16:02] <foo> sdeziel: oh, if you're referring to the mv command, my concern with that is if something happens during transfer a file getting corrupted midway which is why I like rsync. I can sync things and then clean up as needed. Maybe I underestimate mv and it's smarter than that
[20:44] <Phibs> Anyone know why when trying to build mwy own ice-dkms pkg, make in the source tree works but a dkms mkdeb created deb fails at the final step?
[20:44] <Phibs> https://salty.link/screenshots/user1/1685047488yBBWvbEjf2.png