=== dobey_ is now known as dobey
[06:19] <FJKong> chrisccoulson: ping
[07:12] <pitti> Good morning
[07:16] <didrocks> hey pitti, how are you?
[07:17] <pitti> didrocks: very good, thanks! a bit tired still, but had a great basketball game last night
[07:17] <pitti> et toi ?
[07:19] <didrocks> pitti: très bien :-) however weather is rainy this week, so hard to find some spots to run :)
[07:24] <flocculant> didrocks: find one dry spot and run on it :p
[07:26] <didrocks> flocculant: haha, staying still :-)
[08:51] <flexiondotorg> pitti, didrocks, flocculant Morning!
[08:52] <didrocks> hey flexiondotorg!
[09:01] <willcooke> morning all
[09:04] <Laney> yo yo
[09:05] <pitti> Laney: hey hey
[09:07] <davmor2> Morning all
[09:09] <flexiondotorg> Good morning Laney, willcooke, davmor2
[09:09] <willcooke> howdy howdy howdy!
[09:10] <desrt> this is my favourite part
[09:10] <desrt> good morning willcooke, flexiondotorg, davmor2, pitti, Laney, didrocks and seb128 (since he's so obviously lurking)
[09:10] <seb128> good morning desktopers
[09:11] <desrt> !!
[09:11] <willcooke> ha! called it
[09:11] <seb128> hey desrt
[09:11] <pitti> heey desrt, guten Morgen! Wie gehts?
[09:11] <pitti> ça va seb128
[09:11] <seb128> pitti, oui, et toi ?
[09:11] <desrt> pitti: 'meh' :p
[09:11] <flexiondotorg> Morning desrt seb128
[09:12] <didrocks> hey desrt
[09:16] <FJKong> chrisccoulson: ping
[09:19] <seb128> FJKong, hey, you better include some context in that ping if you want a reply, chris than to be busy and might not reply without details
[09:19] <FJKong> seb128: ok ok
[09:21] <seb128> than->tend
[09:23] <pitti> seb128: je vais bien, merci ! bon basketball match hier soir
[09:23] <seb128> ah, mercredi le jour du basket ;-)
[09:59] <andyrock> good morning all :)
[10:00] <willcooke> hey andyrock
[10:01] <hikiko> hi
[10:01] <seb128> hey andyrock, how are you?
[10:02] <andyrock> seb128: rested and relaxed you? XD
[10:02] <seb128> I'm alright! a bit tired but it's ok ;-)
[10:05] <seb128> andyrock, what do you hack on this week?
[10:06] <andyrock> seb128: holidays but I've been  working on my thesis so yeah hacking on holidays too
[10:06] <seb128> andyrock, oh, you were off work a few days right? had some holidays/fun?
[10:06] <seb128> lol
[10:06] <seb128> right, I just remembered, sorry :-)
[10:42] <willcooke> oh, broken icon when updating cache from Software & Updates
[10:43] <seb128> where? what serie?
[10:43] <willcooke> Xenial, when "updating cache"
[10:43] <willcooke> just looking at the python code
[10:43] <seb128> in the unity launcher?
[10:43] <willcooke> sorry, gtk-software-properties
[10:43] <seb128> I've it matching the software&update icon
[10:44] <seb128> just having a second >
[10:44] <seb128> since it's another dialog from the same application
[10:45] <willcooke> http://imgur.com/a/SOfsm
[10:46] <seb128> 0_o
[10:47] <seb128> I don't see that issue on my xenial...
[10:48] <willcooke> heh
[10:48] <willcooke> probably a hangover from me messing around with themes
[10:49] <seb128> could be yeah
[10:53] <willcooke> seb128, trying to install the proposed version of g-s
[10:53] <willcooke> https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1
[10:53] <willcooke> but apt-cache policy says it's not there
[10:53] <willcooke> is this likely a mirror thing?
[10:53] <seb128> right
[10:53] <seb128> no, see the icons next to the builds
[10:53] <seb128> depwaiting
[10:53] <willcooke> ahh
[10:53] <willcooke> got it
[10:53] <willcooke> thanks
[10:53] <seb128> " Missing build dependencies: libsnapd-glib-dev "
[10:54] <seb128> SRU team needs to promote snapd-glib to main
[10:58] <seb128> pitti, ^ is that something you can help with?
[10:58] <pitti> err, I thought I accepted it into main already
[10:58] <seb128> hum
[10:58] <pitti> oh, maybe not binNEW
[10:59] <pitti> right! https://launchpad.net/ubuntu/xenial/+queue?queue_state=0
[10:59] <pitti> looking
[10:59] <seb128> oh, right
[10:59] <seb128> it's in binNEW
[10:59] <seb128> I technical can click that in but I'm not in the SRU team
[11:00] <pitti> accepted, and https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 is dep-wait, so it should auto-retry
[11:00] <willcooke> thanks pitti seb128
[11:00] <seb128> pitti, danke
[11:00] <pitti> de rien
[11:37] <willcooke> seb128, Jonas asked if we could take a look at this to fix a U8 keyboard layout issue
[11:37] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1644268
[11:37] <ubot5`> Ubuntu bug 1644268 in gnome-desktop (Ubuntu) "GnomeDesktop-WARNING **: Failed to load XKB rules file" [Undecided,Confirmed]
[11:37] <willcooke> Looks easy enough, what do you think>?
[11:39] <seb128> willcooke, sure, I'm adding it to my todo
[11:39] <willcooke> nice one, thanks seb128
[11:39] <seb128> yw!
[12:50]  * flexiondotorg lunches
=== hikiko is now known as hikiko|ln
[13:38] <pitti> Laney: hm, are you using juju-2.0 locally?
[13:38] <pitti> it still worked fine in zesty last week (I went through it with seb128), but it seems bootstrap stopped working
[13:39] <pitti> is that by any chance somethign you stubled over?
[13:44] <Laney> pitti: no, I don't use it at all locally actually
[13:56] <pitti> Laney: ack, thanks; there was some miniscule chance :)
[13:57] <Laney> pitti: I had some problem setting it up - forgot what now - and didn't try since :(
[13:57] <pitti> Attempting to connect to 10.0.4.32:22
[13:57] <pitti> mine is hanging forever at this step
[13:57] <Laney> I think I was trying with lxd
[13:57] <pitti> the lxd container is up, but there's no key installed in ~ubuntu/.ssh/authorized_keys
[13:57]  * Laney got IS to make a staging tenant and used that instead
[13:57] <Laney> (for appstream)
[13:57] <pitti> I'm not entirely sure how that's supposed to work, but I guess that's the problem
[13:57] <Laney> :)
[13:57] <pitti> heh
[13:58] <hikiko|ln> question:
[13:58] <hikiko|ln> I want to install distcc
[13:58] <hikiko|ln> but x, y and z have different gcc versions
[13:58] <hikiko|ln> is it safe to use the latest gcc or is better to downgrade the zesty gcc?
[13:59] <pitti> IMHO best to use chroots, and use the same chroot on every slave
[13:59] <hikiko|ln> chroots?
[13:59] <hikiko|ln> I want to use all the cpus that are available for compiling at home pitti
[13:59] <pitti> sure
[14:00] <hikiko|ln> does chroot do the same thing?
[14:00] <hikiko|ln> I didn't understand :)
[14:00] <pitti> no, I mean build in a chroot on every slave
[14:00] <pitti> and use the same x or y or z chroot everywhere
[14:00] <pitti> instead of installing gcc and the build deps on directly on the target
[14:00] <hikiko|ln> oh chroot for gcc
[14:00] <pitti> s/target/slave/
[14:01] <hikiko|ln> good idea :)
[14:01] <hikiko|ln> let's see if that's easy to do
[14:02] <hikiko|ln> or maybe I can just build the most recent gcc somewhere and export CC.. blah
=== hikiko|ln is now known as hikiko
[14:05] <seb128> hikiko, why do you need the new gcc?
[14:06] <Laney> -Wmisleading-indentation # awesome warning
[14:06] <hikiko> seb128, distcc requires that all the computers you use to compile something have the same cc version
[14:07] <seb128> you use several computers to build the same thing?
[14:07] <hikiko> so I was thinking that it's better to install the Z version than downgrade z, but I'll just build it, I probably don't need it system wide
[14:07] <hikiko> seb128, not yet
[14:07] <hikiko> but that's the plan
[14:08] <seb128> just curious but why do you need that?
[14:08] <hikiko> distcc claims that it can use all the available cpus on the network
[14:08] <seb128> Laney, did you catch some bug thanks to it?
[14:08] <hikiko> because chromium takes ages to compile
[14:08] <hikiko> :)
[14:08] <Laney> seb128: yeah
[14:08] <hikiko> and this laptop has 2 cpus only
[14:08] <Laney> I think it was that one that told me I forgot some {}
[14:08] <seb128> Laney, nice!
[14:08] <hikiko> but the new laptop has 8 cores and the desktop 4
[14:09] <hikiko> so I could use 16 :)
[14:09] <hikiko> -j16
[14:09] <hikiko> and make it 16 times faster
[14:09] <hikiko> 8 times*
[14:09] <pitti> well
[14:09] <pitti> you need to substract the network bandwidth and latency
[14:09] <hikiko> yeah
[14:09] <pitti> which is usually considerable
[14:09] <seb128> it's a balance
[14:09] <hikiko> but it's a lan
[14:09] <pitti> compiling C++ takes ages, and distcc might be worth it
[14:10] <hikiko> won't it be fast enough?
[14:10] <seb128> you can experiment
[14:10] <pitti> but compiling a single .c file is usually quite fast, and the network latency might just be worse than that
[14:10] <seb128> let us know how it works for you
[14:10] <pitti> right, doesn't hurt to try
[14:10] <pitti> but don't expect miracles :)
[14:10] <pitti> (particularly not over wifi)
[14:10] <hikiko> yeah I'm not gonna use wifi
[14:10] <seb128> I would probably just try with some ccache on the machine with the best cpu
[14:11] <seb128> but it might be an interesting experimental
[14:11] <hikiko> I've tried ccache but caching causes several other probs
[14:11] <seb128> experiment
[14:11] <hikiko> it's useful for maintainers
[14:11] <hikiko> but if you change your files frequently
[14:11] <hikiko> caching = nightmare
[14:11] <hikiko> then you have to make clean to get rid of errors
[14:11] <hikiko> and it's slower
[14:24] <Trevinho> Laney, hey... I would probably need some help/review with these packaging bits https://code.launchpad.net/~3v1n0/update-notifier/fix-pep8-style/+merge/311683
[14:25] <Trevinho> As autopkg tests and building was broken in zesty
[14:28] <seb128> Trevinho, hey! how are you? why are you working on update-notifier? ;-)
[14:28] <Trevinho> hikiko: anyway... Yeah, use schroot. If you configure it well, you basically have an environment you can do what you want without breaking anything.
[14:41] <didrocks> Trevinho: did you update the cloud wiki today? https://github.com/ubuntu/snappy-playpen/issues/269
[14:41] <didrocks> I don't even find back the url
[14:41] <didrocks> but I can confirm that since I merged your changes, they disappeared
[14:41] <Trevinho> didrocks: let me see :o
[14:42] <Trevinho> didrocks: no change to the wiki...
[14:43] <Trevinho> didrocks: it might be an issue of snapcraft not supporting remote on remote? :o
[14:43] <didrocks> Trevinho: well, this works for ubuntu-app-platform though
[14:43] <didrocks> Trevinho: but yeah, let me try to revert your changes
[14:43] <didrocks> and see if next pass works
[14:44] <Trevinho> didrocks: let's ask in #snappy to sergio, or maybe there's some logging of the server around
[14:45] <Trevinho> didrocks: ubuntu-app-platform has not an after statement isn't it?
[14:46] <didrocks> Trevinho: sergio didn't write the importer
[14:46] <didrocks> Trevinho: it's joe, and today is off for the us
[14:47] <didrocks> it seems to be an importer issue
[14:47] <didrocks> Trevinho: meanwhile, I reverted, and let's see if this appears soon (~1h at worst)
[14:47] <Trevinho> didrocks: it should be less... I think there's a cron every hour
[14:48] <Trevinho> didrocks: otherwise, I'd need to redefine these parts inside the helper... and I don't like much that, but... well if there's no other way
[14:49] <didrocks> Trevinho: I hope it's at the top of the clock!
[14:49] <didrocks> Trevinho: let's see first if the theory is correct
[14:49] <didrocks> nobody edited the wiki in days, so not the wiki itself
[14:49] <Trevinho> didrocks: yeah, not.... when I added my parts it was fine afterwards
[14:50] <Trevinho> but I guess it will be like: hey I depend on this part... ok, which part=?! I don't know it, and I've not parsed it yet
[14:50] <Trevinho> didrocks: ah.... wait, maybe it might be because it's listed later in the wiki? :-D
[14:50] <didrocks> Trevinho: could be
[14:50] <didrocks> Trevinho: but better to wait for people supporting the importer being here
[14:51] <Trevinho> didrocks: yeah, since you reverted... I'd have tried... but let's wait
[14:51] <didrocks> first, let's get back to a working status (especially if the US aren't around until Monday)
[14:51] <didrocks> well, people depend on it :)
[14:51] <didrocks> we need to get back to a working state ASAP
[14:56] <Trevinho> didrocks: sure, sure... In fact I should try with some test branches instead
[14:56] <didrocks> yeah
[15:42] <Laney> Trevinho: mmmmmmmmm don't understand the packaging changes
[17:36] <Trevinho> Laney: they might be wrong 😂
[17:38] <Laney> what are you trying to do?
[17:38] <Trevinho> Laney: make it build
[17:39] <Trevinho> Laney: it was failing without these
[17:39] <Trevinho> Laney: it wasn't triggering autogen
[17:40] <Laney> you had to fiddle with multiarch stuff?
[17:40] <Laney> seems suspicious
[17:40] <Trevinho> Laney: also there are multiple scripts depending on the fact it's in /usr/lib/..
[17:40] <Trevinho> Laney: I didn't want it to be in arch triplet
[17:44]  * Laney tries to build it
[17:45] <Trevinho> Laney: it's a zesty only issue eh
[17:47] <Laney> why did sbuild start being so slow :(
[17:48] <Laney> I: Built successfully
[17:48] <Laney> no changes from zesty
[17:50] <ximion> Laney: could LP: #1644498 be an artifact of the asgen switch?
[17:50] <ubot5`> Launchpad bug 1644498 in appstream (Ubuntu) "apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically" [Undecided,Confirmed] https://launchpad.net/bugs/1644498
[17:51] <Trevinho> Laney: with proposed?
[17:51] <Laney> Trevinho: of course
[17:51] <Trevinho> Laney: it failed in the ppa last night...
[17:52] <Trevinho> Laney: no changes at all, or my branch?
[17:52] <Laney> ximion: in what way?
[17:52] <Laney> Trevinho: no changes
[17:52] <ximion> Laney: maybe the data was broken temporarily and the mirror got busted data...
[17:55] <willcooke> dinner and quittin' time - night all
[17:57] <Laney> ximion: I see it too on xenial
[17:57] <Laney> it's saying everything in xenial-updates is invalid
[18:00] <ximion> the data looks fine though...
[18:00] <Laney> must be libas in xenial
[18:05] <ximion> Laney: oh, let me check something...
[18:05] <Laney> ximion: Trevinho: got to go, will check in later if possible (off tomorrow)
[18:06] <ximion> Laney: I found the bug
[18:06] <ximion> will prepare a patch
[18:06] <Laney> ximion: nice, will upload later, thanks!
[18:06] <Laney> (what is it?)
[18:08] <ximion> Laney: the data has 0.10 as minimum compatibility level, while the stuff in Xenial is too old
[18:08] <ximion> can easily be solved with one simple patch to the appstream package
[18:08] <Laney> oh right
[18:08] <Laney> not a problem is it?
[18:09] <ximion> (or switching asgen back to a lower compat-level, but solving this in appstream is better, since we already have support in asglib too)
[18:09] <ximion> not a big issue
[18:09] <Laney> cool
[18:17] <Laney> Trevinho: Just took your first commit, built, ran through autopkgtest -> passed
[18:17]  * Laney will upload that
[18:19] <seb128> was the build issue a side effect of you bumping the debhelper compat?
[18:20] <Laney> that's why it got multiarched
[18:20] <Laney> guessing there was a problem before otherwise he wouldn't have tried random things
[18:20] <Laney> probably
[18:20] <Laney> anyways, keep an eye on LP, sorry if it doesn't build /o\
[18:21] <Laney> probably want to retry the tests with --trigger update-notifier/3.177 added after this is published
[18:21]  * Laney is off
[18:21] <Laney> bye!
[18:22] <seb128> Laney, have a nice w.e!
[18:23]  * seb128 wonders why Trevinho is building update-notifier to start with
[18:23] <flexiondotorg> Night desktopers
[18:23] <Trevinho> Laney: this is what I get http://pastebin.ubuntu.com/23528583/
[18:23] <Trevinho> seb128: because it caused the autopkgtests for libindicator failed otherwise
[18:23] <Trevinho> to fail*
[18:26] <seb128> night flexiondotorg
[18:27] <Trevinho> Laney: let me see your package, it's just weird that it failed in the same way (the normal version, without my hacks) locally and in the bileto ppa
[19:31] <Trevinho> Laney: tomorrow if you can unblock this would be cool https://bileto.ubuntu.com/#/ticket/2208