[04:55] <hikiko> hi
[06:49] <willcooke> o/
[06:53] <pitti> Good morning!
[07:06] <didrocks> hey guys
[07:11] <didrocks> pitti: hey! I have a very stupid question about the resolved email thread, you wrote:
[07:11] <didrocks> "That's the reason why the dnsmasq instance we spawn
[07:11] <didrocks>     with Network Manager doesn't have caching enabled"
[07:12] <didrocks> what is the use of dnsmasq without cache?
[07:12] <didrocks> for me, that was the only reason we had it
[07:16] <pitti> didrocks: yeah, that's my worry as well
[07:17] <pitti> didrocks: that's what I'm currently discussing with stgraber
[07:17] <pitti> I'm not convinced that cache poisoning actually works that way
[07:17]  * pitti is typing another reply
[07:17] <pitti> didrocks: and indeed I don't like this at all (neither does awe)
[07:18] <didrocks> pitti: ok, so if I get it right, there is no use of resolved or dnsmasq without cache, it's just a process in the middle forwarding requests?
[07:19] <didrocks> well, it does local DHCP I guess…
[07:19] <didrocks> in case you connect through ethernet another device
[07:19] <didrocks> but that's it
[07:20] <pitti> didrocks: there still is
[07:20] <pitti> didrocks: better failure handling with multiple DNS servers
[07:20] <sarnold> perhaps directing specific domain or reverses to specific recursors?
[07:20] <pitti> didrocks: and resolved does DNSSEC
[07:20] <pitti> but indeed, the main point is moot
[07:21] <didrocks> pitti: oh right, you mentioned the multiple DNS servers fallback
[07:21] <didrocks> pitti: got it, thanks :-)
[07:36] <willcooke> is it easy to flush the cache?  Just restarting the daemon?
[07:37] <pitti> needs root
[07:37] <willcooke> fair enough
[07:37] <pitti> ok, I sent two more replies
[07:58] <seb128> good morning desktopers
[07:58] <willcooke> hey seb128
[07:58] <seb128> hey willcooke
[08:01] <pitti> bonjour seb128
[08:01] <seb128> salut pitti, ça va ?
[08:02] <pitti> ça va bien, merci !
[08:02]  * seb128 is reading the dns resolver discussion, interesting one
[08:03] <Laney> why hello
[08:03] <seb128> hoi Laney!
[08:03] <pitti> seb128: indeed
[08:03] <pitti> hey Laney, good morning
[08:03] <Laney> what's up!
[08:04] <didrocks> Laney: because hey
[08:07] <Laney> I dropped my phone on the concrete floor at climbing last night and broke it :|
[08:07] <willcooke> :((
[08:07] <willcooke> Laney, I've replaced a couple of screens on my phone - it's fiddly but do-able.
[08:07] <Laney> it's not a smashed screen actually
[08:07] <willcooke> oh
[08:07] <willcooke> that's bad then
[08:08] <Laney> already had that replaced out of warranty on this one, so no insurance for me!
[08:08] <alexarnaud> Hello all!
[08:08] <Laney> it's some cable/connector inside it
[08:08] <Laney> it does actually work until it's moved
[08:09] <Laney> so can get the data off hopefully
[08:10] <didrocks> argh Laney :/
[08:10] <didrocks> hey alexarnaud
[08:10] <Laney> didrocks: I was trying to wait for the Oneplus 3!
[08:11] <didrocks> when is it going to be out?
[08:11] <alexarnaud> hey didrocks, how are you today? Are you still sick?
[08:12] <Laney> rumours say june 14
[08:12] <didrocks> alexarnaud: yeah, still…
[08:13] <didrocks> Laney: you can do it! wait wait wait :)
[08:13] <seb128> Laney, time to get an ubuntu phone! ;-)
[08:13] <Laney> /part
[08:13] <didrocks> a snapcraft part?
[08:14] <seb128> :-(
[08:14] <Laney> :P
[08:14]  * Laney looks up when he got this phone
[08:15] <Laney> 13 July 2014
[08:15] <Laney> this is poor
[08:18] <alexarnaud> seb128: it seems that Ubuntu Phone is good :) ! Unfortunately, it seems not accessible with a screenreader. I don't know if the work on Android and Firefox OS about this subject could event. I read that Mir use event manager of Android. Talkback aad Android accessibility stack change the way to interact with the phone ^^.
[08:19] <seb128> alexarnaud, yeah, it's improving but it still has feature gaps compared to main OSes
[08:26] <didrocks> oh btw, on the LTS, I have gnome-terminal with weird tabs layout since yesterday's upgrade, is that known?
[08:27] <Laney> what does weird tabs layout mean?
[08:27] <didrocks> let me do a screenshot
[08:27] <Laney> did you check what got upgraded? :)
[08:27]  * Laney suggests you do that first
[08:29] <seb128> blame willcooke!
[08:29]  * seb128 ducks
[08:29] <didrocks> Laney: I did and there was light-themes :p
[08:29]  * Laney is leading didrocks down the path
[08:30] <didrocks> http://people.canonical.com/~didrocks/tmp/terminal_tabs.png
[08:30] <willcooke> ruh row
[08:30] <didrocks> the tab colors changed and it's a little bit (IMHO) ;)
[08:30] <didrocks> ugly*
[08:30] <didrocks> :p
[08:30] <Laney> open the gate marked /usr/share/doc/light-themes/changelog.Debian.gz
[08:31] <didrocks> who is this guy?
[08:31] <didrocks> Will Cooke?
[08:31] <sarnold> .. what, no screenshot from yesterday too? :)
[08:31] <willcooke> didrocks, that's how it's supposed to look.
[08:31] <didrocks> new devs? :)
[08:31] <didrocks> new design ;)
[08:31] <willcooke> It's a feature, not a bug \o/
[08:31] <didrocks> willcooke: ok, it's weird to notice them now when I didn't before :)
[08:31] <didrocks> (but I guess that was the point of the change)
[08:32] <willcooke> didrocks, https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/762349
[08:32] <didrocks> 2 tabs are ok and great, it's when you have more (but I'm guilty of that)
[08:32] <didrocks> willcooke: yeah, I'm looking now
[08:32] <didrocks> at least, it's not my eyes which have derailed
[08:32] <didrocks> and I can notice changes!
[08:33] <didrocks> ok, this is when I should paste this: https://xkcd.com/1172/ :)
[08:33] <willcooke> :D
[08:34] <didrocks> at least, not a regression, but weird (and nice in some way) to have a visual change in a LTS for once!
[08:34] <didrocks> I just wasn't expecting it, hence the "something should have broke"
[08:34] <willcooke> :)  I agree, it's a tad on the ugly side, but it does the job.
[08:34] <didrocks> thx for answering about it guys! :)
[08:34] <didrocks> yep
[08:35] <willcooke> Laney, can you remind me what to add to the search providers in my browser so I can search LP bugs from the URL bar again?  The URL was something like bugs.launchpad.com/+bug/%s  but I can't get it to work
[08:37] <sarnold> http://launchpad.net/bugs/%s
[08:37] <Laney> I use pad.lv/%s
[08:37] <sarnold> https://wiki.canonical.com/UbuntuEngineering/Security/Tips
[08:37] <Laney> then you can use the other pad.lv patterns too
[08:37] <seb128> willcooke, what browser do you use?
[08:37] <willcooke> seb128 *cough* Chrome *cough*
[08:37] <willcooke> I HAVE A REASON TO USE IT!!
[08:37] <willcooke> thanks Laney sarnold
[08:40] <davmor2> willcooke: what was that it was hard to hear over the coughing it didn't sound like the default browser installed on the system though
[08:42] <seb128> willcooke, right click on the url bar -> edit search engine and you can add custom entries
[08:42] <willcooke> seb128, yeah all done, thx
[08:42] <seb128> it's less specific that pad.lv
[08:42] <seb128> and less to type :p
[08:43] <seb128> like I've "bts %s" which sends me to the bts page for the package
[08:43] <Laney> shortcut wars
[08:43] <willcooke> I do "lbp 123456"
[08:43] <seb128> or bzg for the gnome bugzilla
[08:43] <willcooke> *lpb
[08:43] <seb128> that's my "lp" ;-)
[08:43] <seb128> "lps" for the bugs list "lpc" for the component page :p
[08:44] <seb128> but yeah, seems like everyone has their own custom tricks
[08:50] <seb128> ok, after days of rain we have some sun, going to use the opportunity to get some pre-lunch exercice
[08:50] <willcooke> seb128, enjoy!  It's raining here still :(
[08:50]  * willcooke considers building an ark
[08:51]  * Laney whines "MIR please" at tedg
[08:52] <seb128> thanks!
[08:54] <Laney> pitti: is "rm pending.json" not enough to get britney to fix its knowledge of pending tests?
[08:54] <Laney> kcalcore -> ktnef is falsely in progress
[08:55] <pitti> Laney: ah, did you do that?
[08:56] <Laney> yesterday
[08:56] <pitti> Laney: I'm currently investigating what happened to the lost armhf requests
[08:56] <pitti> Laney: so either you did that while britney was running, or it lost them again
[08:56] <Laney> I checked britney wasn't running at the time
[08:56] <Laney> or it was running but not for yakkety
[08:56] <pitti> Laney: let me look at the runners; test requests are not supposed to get simply lost
[08:56] <Laney> it's been in progress for some days now
[08:57] <pitti> e. g. gvfs/armhf for systemd 230-2 is still "in progress", but https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety?format=plain&prefix=yakkety/armhf/g/gvfs has no result
[08:57] <Laney> first I re-requested them but that didn't clear it
[08:57] <pitti> but it's also not in the AMQP queues any more
[08:57] <pitti> so they just get eaten somehow, which Should Not Happen™
[08:58] <pitti> Laney: might still be a leftover swift glitch of course
[08:59] <pitti> Feb 12 04:13:16 cyclops-node23 worker[495]: 2016-02-12 04:13:16,425 INFO:worker Received request for package gvfs on yakkety/armhf; params: {u'triggers': [u'systemd/230-2']}
[08:59] <pitti> Feb 12 04:17:07 cyclops-node23 worker[495]: 2016-02-12 04:17:07,030 INFO:worker Putting results into swift autopkgtest-yakkety yakkety/armhf/g/gvfs/20160212_041707@
[08:59] <pitti> Feb 12 04:17:09 cyclops-node23 worker[495]: 2016-02-12 04:17:09,778 INFO:worker Acknowledging request gvfs
[08:59] <pitti> that looks fine
[09:00] <davmor2> willcooke: Go find Rhod Gilbert ask the audience how old they were when they realised they could take a kagool off ;)
[09:00] <pitti> Laney: err, wait -- that's a completely bogus timestamp
[09:00] <willcooke> davmor2, :D:D:D
[09:00] <Laney> pitti: errrm, quite
[09:00] <pitti> Laney: indeed, one of the runners has date == Fri Feb 12 11:21:48 UTC 2016
[09:01] <Laney> I guess something expects the timestamps to be monotonic
[09:01] <pitti> Laney: yes, in britney we remember the last timestamp and query for results newer than that
[09:01] <davmor2> willcooke: followed up with "In the bible it rained for 40 days and forty nights, that's still the best summer I ever remember"
[09:01] <pitti> Laney: ok, let me fix the date on this, then I'll mass re-run all the RUNNING ones
[09:01] <Laney> merci
[09:01] <pitti> Laney: btw, you don't need to wait for britney and rm pending any more
[09:02] <Laney> I did try re-running first
[09:02] <Laney> that was http://autopkgtest.ubuntu.com/data/packages/yakkety/amd64/k/ktnef/20160531_205915@.log
[09:02] <Laney> but it's still RUNNING on britney
[09:02] <Laney> no, lies, it was http://autopkgtest.ubuntu.com/data/packages/yakkety/amd64/k/ktnef/20160531_171644@.log - but still
[09:02] <pitti> Laney: hm, that sounds like something else then
[09:03] <Laney> I think there were still some swift problems at that time
[09:03] <pitti> ah, could be
[09:03] <Laney> it took debci ages to catch up with the results being put into swift
[09:03] <pitti> Laney: ah, that arm box has ntpd installed
[09:03] <pitti> so timesyncd disables itself
[09:03] <pitti> and apparently ntpd doesn't work so well
[09:03] <Laney> "oops"
[09:04] <pitti> kwality
[09:05] <pitti> ok, ntp purged, timesyncd started, date is correct
[09:05] <pitti> time for retry-autopkgtest-regressions -s yakkety --state RUNNING |grep armhf
[09:06] <pitti> (done)
[09:07]  * Laney runs ktnef locally
[09:07] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/k/ktnef/20160531_205915@/log.gz unhelpful
[09:07] <pitti> Laney: oh, I was looking at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux-raspi2/20160601_020110@/log.gz which is similar
[09:08] <pitti> Laney: thanks for that, investigating this on amd64 is much easier
[09:08] <Laney> it means 'uninstallable' right?
[09:08] <pitti> Laney: no, this means that apt-get source ktnef somehow failed
[09:10] <Laney> pitti: oh right, and apt's stdout/err isn't saved anywhere?
[09:10] <pitti> Laney: but I see why it might fail for linux-raspi2 (version mismatch wit NBS binaries), but not the same case for ktnef
[09:12] <pitti> Laney: it's actually suposed to print the apt stdout/err on failure
[09:12] <pitti> .. or not, hang on
[09:12] <pitti> yeah, I think it doesn't
[09:12] <pitti> Laney: does that reproduce locally?
[09:13] <Laney> not with schroot anyway
[09:13] <Laney> probably not minimal enough
[09:14] <pitti> Laney: does reproduce here
[09:14] <pitti> runner/adt-run ktnef --- schroot yakkety
[09:16] <pitti> Laney: right, bug in the heuristics for determining which source package to download
[09:16] <pitti> *throws hands into air*, /me really wants an apt-get source foo=version
[09:16] <pitti> this is excruciatingly difficult
[09:16] <pitti> err, apt-get source foo/yakkety-proposed
[09:17] <pitti> (=version works)
[09:21] <Laney> pitti: /me screams
[09:21] <Laney> just saw this code
[09:23] <pitti> Laney: it's pure joy, isn't it
[09:54] <Laney> pitti: https://paste.debian.net/713146
[09:54] <pitti> Laney: argh, that trap again
[09:56] <pitti> Laney: I'm a moron: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=7c1a251a4
[09:56] <Laney> pitti: haha
[09:56] <pitti> Laney: so we need to not specify it for precise, but everywhere else
[09:56] <Laney> we have autopkgtest for 12.04?
[09:56] <pitti> yes
[09:56] <pitti> kernel mostly
[09:57] <alexarnaud> TheMuso: Hello! I'm visual impaired and I would like to know if you have some type of experience about computer with EFI and Windows dual-boot. Is it possible from a new computer buy in the market with Windows to boot on a Ubuntu USB stick without sighted help that will disable fast boot or something like that ?
[09:57] <Laney> there's another showsrc in lib/adt_testbed.py
[09:57] <pitti> E: Command line option --only-source is not understood
[09:57] <pitti> yep, need to conditionalize that
[09:57] <pitti> runner/adt-run -d pmount --- schroot precise
[09:58] <pitti> ^
[09:58] <pitti> Laney: thanks, will clean this up too
[10:00] <Laney> pitti: you can call "apt-cache showsrc --only-source" and look at the exit code
[10:00] <Laney> you get 0 if it accepts the argument and 100 otherwise
[10:00] <pitti> $(grep -q 12.04 /etc/os-release || echo --only-source)
[10:00] <pitti> Laney: oh, and it helpfully exits with 0 if you specify a nonexisting source package
[10:00] <pitti> *#)$#(*$#
[10:07] <pitti> Laney: http://paste.ubuntu.com/16886653/ seems to work
[10:08] <pitti> this fixes ktnef and linux-raspi2
[10:09] <pitti> there's still something wrong with this logic for precise, though, but later on
[10:09] <pitti> --apt-pocket self-tests still succeed
[10:10] <pitti> precise> ah, it fails because it still behaves like in xenial without --only-source, it just doesn't have an option for thsi
[10:11] <pitti> apt-cache showsrc ^linux$
[10:11] <pitti> and that doesn't work either
[10:13] <Laney> I suppose you have to look for Package:
[10:14] <Laney> grep-dctrl would be easier for that
[10:15] <Laney> apt-cache showsrc ktnef | grep-dctrl -S -sPackage-List -n ktnef
[10:17] <pitti> Laney: I pushed http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=56ac53b for now and will re-retry stuff
[10:18] <Laney> ok, thanks!
[10:18] <pitti> to unblock promotions; but this indeed is in dire need for cleaning up
[10:18] <Laney> I wonder why this became a problem right now
[10:18] <Laney> ktnef last succeeded not long ago
[10:18] <pitti> maybe with the new KDE upload two weeks ago binaries got shuffled
[10:19] <Laney> looks the same on xenial too
[10:19] <Laney> ah well
[10:20] <pitti> libgmpada too
[10:21] <pitti> and http://autopkgtest.ubuntu.com/packages/k/kactivities/yakkety/amd64/
[10:21] <pitti> all retriggered
[10:40] <Laney> Mirv: I'll upload goldencheetah to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-035/+packages to test your theory, ok?
[10:42] <Laney> (done)
[11:02] <Mirv> Laney: thank you
[11:02] <Mirv> still building on arm64
[11:07] <Laney> Mirv: failed
[11:08] <Mirv> Laney: I see. do you know how to get a list of packages that don't have armhf build at all (like goldencheetah)? I could cross-check that to my list of packages depending on libqt5core5a to find other candidates that need some action
[11:08] <Mirv> goldencheetah was indeed on this second list, but not on my first list (armhf ftbfs)
[11:17] <Laney> Mirv: In [13]: yakketyarmhf = lp.load('https://api.launchpad.net/devel/ubuntu/yakkety/armhf/')
[11:17] <Laney> In [14]: ftbfs = yakketyarmhf.getBuildRecords(build_state='Failed to build')
[11:17] <Laney> In [15]: len(ftbfs)
[11:17] <Laney> Out[15]: 472
[11:18] <Laney> hmm
[11:18] <Laney> not sure that is right
[11:18] <Laney> I suppose you need to filter it for published records only
[11:19] <Mirv> ok that copy-paste should be enough to get me forward with lplib
[11:24] <Laney> Mirv: seems "current_ftbfs = [f for f in ftbfs if f.current_source_publication is not None]" filters it to the current ones
[11:24] <Laney> can there really only be 198?
[11:24] <Laney> I'm a bit suspicious
[11:25] <Mirv> Laney: so ftbfs would list also those without package like build dep missing, for example goldencheetah? my ftbfs (really failed to build) was 181
[11:26] <Laney> you want to add build_state='Dependency wait' too for those
[11:26] <Mirv> ok
[11:26] <Mirv> Laney: and what about if package is built only for selected architectures?
[11:27] <Laney> I wonder if this is only showing packages which have been uploaded to y
[11:28] <Laney> http://qa.ubuntuwire.org/ftbfs/
[11:28] <Laney> this agrees with my number
[11:31] <Mirv> ah right I was on xenial, I maybe lost a few when translating the list of binary packages to source package with apt-cache. I can see from my bash history that I did filter for armhf (F)
[11:33] <Mirv> hmm, no, since those are source packages, I used apt-cache for the libqt5core5a reverse deps. ok, going over again.
[11:35] <Laney> this is the only one I care about right now since it is blocking libical :)
[11:52] <andyrock> Morning all
[11:52] <seb128> hey andyrock, how are you?
[11:53] <andyrock> Hey seb128 not bad you?
[11:53] <Mirv> ok I reproduced the ftbfs list and also got three more candidate packages from the depwait list, and goldencheetah too. checking in 035 and updating the bug report. I think I could subscribe ubuntu-archive now too, even if I'd still find a package or two in my remaining re-re-checks.
[12:24] <desrt> good morning
[12:26] <willcooke> hi desrt
[12:27] <seb128> hey desrt
[12:34] <seb128> willcooke, omw for that call, having some wifi issues though
[12:35] <willcooke> seb128, ha!  Thought exactly that :)
[12:36] <seb128> willcooke, can you hear me when I talk?
[12:36] <willcooke> seb128, nope!
[12:37] <seb128> fail :-/
[12:55] <seb128> attente, sorry I saw the bug but still unsure what you are trying to solve
[12:57] <attente> seb128: if you build the galculator snap without that, the snap looks for resources in the parts directory of the build dir instead of inside the final snap itself
[12:57] <seb128> desrt, attente, sorry audio was not good in that hangout and I didn't really understand if we had more specific issues than the ones we are filing/tagging since Prague
[12:57] <seb128> attente, so basically https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1583250 ?
[12:58] <attente> seb128: yep, exactly that
[12:58] <attente> seb128: so that workaround is to modify the autotools snapcraft plugin locally and add it to the repo
[12:58] <attente> but there we hard code the destination of the mounted snap
[12:59] <attente> /snap/<name>/current
[12:59] <seb128> right
[12:59] <seb128> change the app to use gresources :p
[12:59] <attente> but they don't like this because it's hard-coded, and removes any future possibility of relocating the snap
[13:00] <seb128> what do they suggest doing?
[13:00] <seb128> what is flatpak doing? do they make the archive content being seen as /?
[13:01] <attente> i don't know what flatpak is doing, but our workaround right now with the hacked autotools plugin seems to be the only thing we have
[13:01] <seb128> yeah, Trevinho made a quilt plugin to patch the source before building
[13:02] <Trevinho> not that is the cleanest solution eh :)
[13:02] <seb128> hey Trevinho!
[13:02] <Trevinho> but... ti seems that there some discussion if we want that part of snapcraft or not
[13:02] <Trevinho> hey seb128
[13:02] <attente> that's about the same as just fixing all upstreams to be relocatable though
[13:02] <Trevinho> seb128, attente: relevant bug is https://bugs.launchpad.net/snapcraft/+bug/1551716 it would be nice your input too
[13:03] <seb128> Trevinho, well ideally you wouldn't need to patch a source to snap it
[13:03] <Trevinho> no, ideally not... But you know the world we live in
[13:03] <Trevinho> and forking just for a single patch is annoying to me
[13:04] <Trevinho> all the main pieces in core (nm, bluez) are still using patching in any case
[13:05] <seb128> yeah, that's fine for our stack
[13:05] <seb128> we create work for ourself so it's our choice
[13:05] <seb128> we shouldn't require that from app writers though
[13:05] <Trevinho> sure, upstream has not to do that
[13:06]  * desrt hugs the upstreams of the world
[13:06] <desrt> "we're all in this together, guys"
[13:07] <seb128> desrt, attente, do you me to write that email to the snappy list?
[13:07] <desrt> seb128: if you would like to, that would be great
[13:08] <seb128> k
[13:08] <desrt> i do have a slight aversion to getting involved in discussions that i know almost nothing about =)
[13:08] <Trevinho> seb128, attente: however one thing I was hacking on and that I think could be useful for this, is that IMHO when opened a snap should be do something like a bind mount on /this-snap or whatever that points to $STAN
[13:08] <Trevinho> $SNAP
[13:08] <Trevinho> in this way, we can just compile using /this-snap/ as prefix
[13:09] <desrt> *cough* filesystem *cough* namespaces
[13:09] <desrt> *cough* *cough*
[13:09] <Trevinho> well, naming can be better... But it's not the point
[13:10] <desrt> it's entirely the point
[13:10] <desrt> we could have some standard path that all snaps used without stepping on each others toes...
[13:10] <desrt> we could even give it a nice short easy-to-type name that looks friendly and familiar to everyone
[13:10] <desrt> maybe... oh... /usr, for example
[13:11]  * desrt twitches
[13:11] <Laney> :)
[13:11] <seb128> there might be a reason why they don't want to go that road
[13:12] <seb128> let's see what the discussion gives
[13:12] <seb128> at least filesystems namespaces can"t be used to restrict root apps
[13:12] <Laney> Mirv: can you point me to your list?
[13:12] <seb128> so it would work for desktop examples
[13:12] <seb128> but not for system services
[13:12]  * Laney knows a friendly archive admin
[13:12]  * Laney sniggers
[13:14] <desrt> seb128: filesystem namespaces can be used for root apps no problem
[13:14] <desrt> seb128: the basis of that discussion was that it may still be necessary to _also_ use apparmor for some things as well
[13:15] <desrt> (although i believe that the core kernel will improve to the point where this is not necessary... and if you use user namespaces, i'd say it's already there, modulo the horrifying bugs that appear on a semi-regular basis)
[13:15] <attente> Trevinho: isn't the same problem still going to happen? that's still going to be a hard-coded path in the final snap
[13:16] <Trevinho> attente: yeah, it's hardcoded, but it's always there
[13:16] <Trevinho> attente: while it won't be dependent on version or pkgname
[13:17] <desrt> since i can't really talk about the weather...
[13:17] <desrt> how many of you have stopped using firefox and switched entirely to chrome?
[13:18]  * desrt is starting to suspect that she may be the last holdout
[13:18] <Trevinho> desrt: although I've plenty of ram, chrome is too much a memory hog to me.. So no.
[13:18] <Trevinho> so.. firefox for life.
[13:19] <desrt> ....or until your next laptop upgrade :)
[13:19] <Trevinho> desrt: I did that.. And I've 32GB of ram, but still... I can't manage all my tabs in chrome :)
[13:19] <Laney> i use firefox too
[13:20]  * desrt very often gets into situations where firefox takes a very very long time to quit
[13:21] <desrt> clearing out history/awesomebar/etc/etc databases seems to help that for a bit, but it's not too long before it's back to where it was... and during that time, if i try to open another window (within 20 seconds, say, of last exit), i get "firefox is already running.  plz reboot."
[13:21] <desrt> any tips?
[13:21] <Mirv> Laney: bug #1586026 - ubuntu-archive not yet subscribed
[13:23] <Laney> Mirv: what does candidates: mean for yade?
[13:26] <Laney> desrt: seen the "firefox is still running" thing from time to time, but not slow quitting
[13:26] <Laney> no help from me then :(
[13:26] <desrt> the "firefox is still running" thing happens because it hasn't exited yet from the previous tim e
[13:26] <jbicha> desrt: I'm stil on firefox
[13:26] <desrt> ie: the windows are closed, but the process is still there, seemingly doing something in the background
[13:27] <desrt> jbicha: hey!
[13:27] <Laney> when i've seen it it's been a long time after quitting
[13:27] <seb128> grrr, got bitten again by docking my laptop changing connection which confuses IRC
[13:27] <desrt> jbicha: welcome back!
[13:27] <Laney> like the thing never managed to exit properly
[13:27] <seb128> if somebody talked to me since less than 10 min please repeat what you wrote
[13:28]  * Laney gets recruiter spam hiring for a cloud based tax and accounting platform
[13:28] <Laney> hmmmmmmmmmmmmmmmmmmmm maybe not
[13:28] <Mirv> Laney: that it was found in the cross-check list but check if it's failing a rebuild is not ready yet
[13:29] <Mirv> ie it did fail on armhf, but not yet sure if it would now fail on arm64. build still ongoing.
[13:29] <Laney> seb128: it breaks your existing network connections if you do that?
[13:30] <seb128> no, but I think it changes the routing
[13:30] <seb128> my dock is cable/eth connected
[13:30] <seb128> which becomes default over the wifi
[13:31] <Laney> not sure that should break established connections
[13:31] <Laney> did it always do that?
[13:31] <seb128> yes
[13:31] <Laney> annoying
[13:32] <seb128> indeed!
[13:34] <Laney> seb128: don't suppose you have a few minutes to process https://bugs.launchpad.net/ubuntu/+source/bino/+bug/1586026 do you?
[13:34] <Laney> if not then just goldencheetah would be appreciated
[13:35]  * Laney is attacking libical with maximum force
[13:35] <seb128> let me have a look
[13:35] <Laney> pretty sure the only thing left after that is indicator-datetime
[13:35]  * Laney stares at texas hard
[13:35] <seb128> why would they fail now if rebuilt?
[13:36] <seb128> teddddd
[13:36] <Laney> some gl change on arm64
[13:37] <seb128> shouldn't we fix gl/those then?
[13:37] <Laney> sure if you get the phone team that made this change to put it on their list
[13:38] <seb128> is goldencheetah blocking libical?
[13:38] <Laney> yep
[13:48] <seb128> Laney, done for goldencheetah, going to wait to hear more from Mirv before removing the others, looks like things that should be fixed to me
[13:50] <Laney> fine for me, fixing things is good, hope that happens ;-)
[13:50]  * Laney is bored of punching his phone
[14:55] <Sweet5hark> seb128: http://people.canonical.com/~bjoern/yakkety/5.1.3/ <- 5.1.3 yakkety for poppler transition and to avoid breaking against mdds
[14:56] <seb128> Sweet5hark, k, adding to my todo
[14:57] <Sweet5hark> seb128: I looked at bug 1586497 -- cant get any wiser from the logs there on what happened there really. I only see dpkg returning -1 in https://launchpadlibrarian.net/261979138/DpkgHistoryLog.txt but cant see why. I also note this happened with other packages before in the log ...
[14:57] <Sweet5hark> seb128: is that enough to mark it bot-stop-nagging?
[14:58] <seb128> Sweet5hark, right, maybe full disk or something, yeah just tag it
[15:03] <Sweet5hark> seb128: done (all SRU bugs now verification-done0.
[15:03] <seb128> Sweet5hark, thanks
[15:31] <seb128> Laney, ubuntu-app-launch was in main and demoted in xenial, I don't think it needs a MIR?
[15:32] <seb128> Sweet5hark, sponsored, ignore the rejected email, you included the orig in the libreoffice upload where it was already in yakkety, I hacked the .changes and reuploaded
[15:41] <Laney> seb128: you'd promote it?
[15:41] <Laney> I didn't find an mir bug
[15:42] <Laney> it looks like it went straight to main
[15:43] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+bug/1218952
[15:43] <seb128> it was renamed
[15:43] <seb128> so yeah, let me repromote it
[15:44] <Laney> neat
[15:45] <Sweet5hark> seb128: whoops, sorry. thanks for fixing.
[15:47] <seb128> yw!
[15:47] <seb128> Laney, done
[15:59] <seb128> happyaron, still around?
[16:10] <seb128> happyaron, your openconnect SRU is buggy :-/ you included changes that are not described in the changelog, like using "--enable-absolute-paths" and you reverted the updated build-depends requirement from nm 0.9 to 1.1 ... I fixed it and sponsored
[16:13] <seb128> happyaron, also you changed the sru bug number, unsure if that was wanted?
[19:40] <jbicha> mterry: hi, since you uploaded webkitgtk, do you want to look at
[19:40] <jbicha> https://code.launchpad.net/~jbicha/lightdm-webkit-greeter/lp1588037-obsolete-webkit-dependency/+merge/296250
[19:41] <mterry> heh
[19:41] <mterry> jbicha, sure
[19:46] <jbicha> hmm, libwebkitgtk-doc breaks & replaces libwebkitgtk-dev (<< 2.4.10) but we'll need that bumped to 2.4.11-1~
[19:50] <mterry> jbicha, guh right
[19:50] <mterry> whoops
[20:15] <jbicha> seb128: if you're still around, could you remove anjuta 3.20 from y-proposed
[20:16] <jbicha> anjuta will need a simple rebuild to drop the libwebkit2gtk-3.0 dependency...it doesn't even need webkitgtk to finish building first
[21:47]  * desrt boggles at gcc
[21:47] <desrt>         movl    $4, %edx
[21:47] <desrt>         movl    $.LC6, %esi
[21:47] <desrt>         movq    %r13, %rdi
[21:47] <desrt>         call    memcmp
[21:47] <desrt> this is your code on -O3.... wtf
[21:53] <desrt> clang says: cmpl    $1852400175, -4(%rbx,%r14)
[21:53] <desrt> good clang *pat pat*
[22:30] <TheMuso> alexarnaud: I think Windows does have an option to let you boot into the UEFI settings on next boot, but from there you will need sighted help, unless of course your UEFI vendor has implemented some kind of accessibility, but that is very very unlikely.
[22:30] <TheMuso> alexarnaud: There also may be a keyboard shortcut to press at boot that will bring up the boot selection, but working out which one is your USB is another matter, again likely requiring assistance.