[04:57] <hikiko> Hi
[05:45] <pitti> Good morning
[07:10] <seb128> good morning desktopers
[07:12] <pitti> bonjour seb128 !
[07:12] <seb128> pitti, salut, ça va ?
[07:13] <pitti> seb128: ça va bien, merci ! c'était un bon week-end
[07:13] <seb128> ici aussi !
[07:13] <pitti> J'ai fait beaucoup de jardinage, et j'ai fait enfin notre <tax declaration>
[07:15] <seb128> one sounds good, the other one borring :p
[07:15] <seb128> vous avez du beau temps ?
[07:15] <seb128> ici c'était bien samedi mais il pleut depuis hier après-midi
[07:15] <pitti> c'était bien le week-end entier ici
[07:16] <pitti> mais maintenant il fait gris aussi
[07:18] <didrocks> salut seb128, pitti
[07:18] <pitti> bonjour didrocks, comment vas-tu ?
[07:19] <didrocks> pitti: aussi bien que possible, mais enfin en France!
[07:19] <didrocks> et toi ?
[07:19] <pitti> didrocks: ah, tu as renté après une conférence ?
[07:20] <didrocks> pitti: oui, j'étais au sprint snappy à vancouver il y a 2 semaines
[07:20] <didrocks> pitti: et la semaine dernière, à Austin pour FTF/NXP
[07:20] <pitti> uuh, beaucoup de voyager
[07:22] <didrocks> pitti: oui…
[08:03] <willcooke> morning all
[08:04] <Laney> hello!
[08:04] <pitti> hey Laney!
[08:04] <seb128> hey willcooke Laney
[08:05] <seb128> happy monday!
[08:05] <didrocks> hey willcooke, Laney
[08:07] <Sweet5hark> moin guys!
[08:08] <willcooke> Public holiday in Canada today
[08:10] <seb128> oh, what are they celebrating?
[08:10] <seb128> hey Sweet5hark!
[08:10] <didrocks> morning Sweet5hark
[08:10] <willcooke> seb128, Victoria Day
[08:11] <willcooke> I think Victoria is like the head moose of Canada
[08:11] <seb128> old queen day, I see :p
[08:12] <Laney> she was our queen too
[08:12] <Laney> therefore
[08:12] <Laney> /quit
[08:12] <willcooke> :D
[08:13]  * duflu must be slow if that's a brexit reference
[08:13] <Laney> More a reference to having a day off
[08:13] <seb128> trying to slack!
[08:13] <seb128> tsss
[08:14]  * seb128 hands some tea to Laney, it's ok, you can get work done ;-)
[08:15] <davmor2> seb128: I wouldn't bother with slack to be honest irc is fine ;)
[08:15] <seb128> heh
[08:16] <Laney> ahhh a comedy morning
[08:16] <willcooke> Speaking of which , cool story.... I stuck a sewing needle right through the end of my finger on Saturday.
[08:16] <willcooke> right through
[08:17] <davmor2> hahahahahahahahaahahahahahahahahahahahahahahahahahahhahahaaha ouch I bet that hurt hahahahahahahahahahahahahahahahahahahahahahahahaha etc
[08:17] <willcooke> exactly the reaction I predicited :D ^
[08:18] <willcooke> I was trying to unclog the windscreen washer jets on my car
[08:18] <willcooke> because it never gets used they gunked up with moss of something
[08:18] <davmor2> willcooke: use a pin it has a blunt end you can push on :P
[08:19] <willcooke> where were you on Saturday?!?!
[08:19] <willcooke> I was using a 10p peice to act as a blunt end, and of course it slipped
[08:19] <willcooke> *piece
[08:19] <willcooke> * peeice
[08:20] <seb128> utch
[08:20] <davmor2> willcooke: I was at our caravan in shrewsbury chillaxing
[08:21] <Laney> haha
[08:21] <Laney> if it's weekend story time
[08:21] <Laney> I almost caused a big fire at the allotment
[08:21] <willcooke> yay!!!
[08:22] <Laney> got a picture... one sec
[08:23] <Laney> https://orangesquash.org.uk/~laney/fire.jpg
[08:23] <Laney> you can see the flames
[08:23] <Laney> that's a big pile of extremely dry stuff
[08:23] <willcooke> that is a very big pile
[08:23] <seb128> don't play with fire new to dry stuff
[08:23] <seb128> next to*
[08:24] <Laney> hahaha
[08:24] <Laney> I had burnt it elsewhere
[08:24] <Laney> then put the ashes on a compose heap
[08:24] <Laney> compost
[08:24] <Laney> turns out they were still quite hot!
[08:24] <seb128> lol
[08:25] <pitti> ouch
[08:25] <Laney> had to put like 300L of water on it before it stopped smoking completely
[08:26] <Laney> still a bit warm when we went yesterday
[08:26] <pitti> we did this in the municipality during my civil service back then, but we left the ashes (from cut tree branches) for two days and instead sticked potatoes (wrapped in tin foil) into it :)
[08:26] <Laney> which is good for composting if it doesn't ignite again ;-)
[08:27] <Laney> nice
[08:27] <Laney> eventually all that woody stuff has to go
[08:27] <Laney> fire wouldn't have been all bad...
[08:28] <davmor2> Laney: why did you try to kill the allotments with fire why why???? what did it ever do to you except give you lovely vegetables
[08:28] <seb128> how can wood get that dry when it's supposed to rain every day in your country :p
[08:28] <seb128> speaking of which seems it's going to rain every day here this week :-/
[08:28] <seb128> go summer :-(
[08:29] <Laney> haha
[08:29] <Laney> brown twiggy stuff dries out quickly
[08:29] <Laney> it's nice here atm
[08:31] <Laney> so, work......
[08:31] <Laney> pitti: should I ignore these 9999999999 emails? :)
[08:32] <pitti> Laney: yes, please
[08:32] <Laney> looks like all the clouds broke
[08:32] <pitti> Laney: most of it was fallout from util-linux (fixed now, needed to run with --all-proposed to not remove initramfs-tools etc.), and the remaining trickle is about virtualbox FTBFSing and a bug in autopkgtest
[08:33] <pitti> i. e. if there are NBS binaries in -proposed it currently treats this as a tmpfail
[08:33] <pitti> it should be a real failure
[08:33] <pitti> working on it right now
[08:33] <Laney> cool
[08:34] <Laney> I got paged overnight on friday because the appstream machine got to <10% free disk /o\
[08:34] <Laney> luckily it didn't wake me up
[08:34] <Laney> (don't put me on call for anything real ever)
[08:34] <pitti> Laney: oh, do you have some kind of SMS alerting service there?
[08:34] <Laney> yeah I hooked it up to pagerduty via nagios
[08:35] <Laney> would be more clever if it could do some trend analysis
[08:35] <Laney> "this is going to run out of space in the next 3 days" or so
[08:36] <pitti> "this is going into space" would be way cooler
[08:36] <Laney> appstream.iss
[08:36] <pitti> with ubuntu-app-launch
[08:38]  * Laney stole another 500G in the meantime
[09:24] <seb128> happyaron, hey, what's the status of the nm-applet sru? did you see that mathieu fixed the 3g icon thing?
[09:27] <happyaron> seb128: upstream proposed a fix, but not tested yet
[09:27] <happyaron> will get my usb dogle tomorrow
[09:28] <seb128> happyaron, to what? the 3g icon? cyphermox did, he upload to y as well on friday
[09:28] <happyaron> yep that's it
[09:28] <happyaron> but not read it's cyphermox
[09:29] <seb128> k
[09:30] <seb128> what is taking so long for that update? do you need help?
[09:30] <seb128> I'm going to have a look to backport some specific patches and do a SRU with that I think
[09:30] <seb128> so we don't make oem wait for too long
[09:30] <seb128> we can do another one then when we manage to get 1.2.2 working
[09:31] <happyaron> not much trouble but I thought to wait for the dongle to arrive
[09:32] <happyaron> I can work on the backports and give something to you tomorrow, will this work for you?
[09:32] <seb128> please don't, cyphermox tested it and upstream commited
[09:32] <seb128> it's a one liner
[09:32] <happyaron> ok
[09:32] <seb128> yes
[09:32] <seb128> or I can do the backport SRU if you want
[09:33] <seb128> which we can replace by your update when you get it done?
[09:33] <seb128> as you prefer
[09:33] <happyaron> I think just wait till tomorrow, just a schedule problem
[09:33] <seb128> k
[09:34] <happyaron> ty
[09:34] <seb128> thanks
[09:46] <willcooke> why are so many people worried about that missing symlink thing in g-s.  Meh.
[09:46]  * willcooke approves the fix for X
[09:48] <seb128> seeing warnings on start makes you feel like things are buggy
[09:49] <seb128> I think it's all that is
[09:49] <willcooke> yeah
[09:49] <willcooke> I'm surprised that many people are running it from a shell prompt
[09:50] <seb128> our users are technical it seems ;-)
[09:50] <Laney> not technical enough to tell which messages are harmless
[09:51] <seb128> yeah :-/
[09:53] <willcooke> Who wants to track the "mouse not working" (presumably something to do with fwupdate) https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1578317
[09:53] <willcooke> ?
[09:53] <willcooke> Laney or attente I think, but whooooooo? Laney thoughts?^
[09:54] <willcooke> I'm keeping an eye on it, but I wonder if we should make a call on it soon.  I dont think it's affecting that many people right now or we'd here more about it, but it's a bit sucky
[09:57] <Laney> what is a call?
[09:57] <Laney> I thought/hoped that the other two were working on client side stuff again now
[10:01] <willcooke> Sorry, should have explained my thinking, I was considering stopping fwupdate starting on login while this mouse issue gets fixed.  Yes - mouse would stop if you run g-s , but at least you could do something until then
[10:01] <willcooke> @ who - I wasnt sure if fwupdate counts as client or backend
[10:01] <meetingology> willcooke: Error: "who" is not a valid command.
[10:13] <Laney> I think you would have to disable firmware updating completely
[10:22] <seb128> but are we sure it's fwupdate triggering the issue?
[10:23] <seb128> your comment suggests that the option there makes no difference
[10:23] <Laney> I wouldn't jump the gun
[10:23] <Laney> the next step is investigating isn't it
[10:27] <seb128> that would be the first step :p
[10:27] <seb128> but yeah
[10:27] <seb128> would help if we knew somebody having the issue...
[10:56] <pitti> Laney: I pushed the autopkgtest fix for handling this virtualbox corner case, so the worker failure email stream should stop now..
[10:57] <Laney> nice, thanks!
[10:57] <pitti> go apt
[10:57] <pitti> it would be nice if there were different error codes for "this source package does not exist" and transient network errors on download..
[11:00] <seb128> willcooke, is your indicator-power showing an invalid icon when you connect your iphone to your ubuntu computer?
[11:00] <willcooke> seb128, testing.....
[11:00] <willcooke> seb128, via cable?
[11:01] <seb128> yes
[11:01] <willcooke> yes
[11:02] <willcooke> also, the fact that it knows about the battery on the phone is very nice!
[11:02] <willcooke> erm
[11:02] <willcooke> but
[11:02] <willcooke> hmm, this needs more testing, but, it looks like it's just kicked me off wired ethernet
[11:03] <willcooke> could just be that it sees the phone as an ethernet
[11:03] <seb128> weird
[11:03] <seb128> is n-m listing it?
[11:03] <willcooke> no, but's its doing the little "trying to get an ip address" animation
[11:04] <seb128> willcooke, so you get the incorrect icon? seems like it's an obvious bug, I wonder why we didn't get more feedback about that before :-/
[11:04] <seb128> either ubuntu users don't own idevice
[11:04] <seb128> or they never plug them to their ubuntu?
[11:04] <willcooke> historically it never worked, so people might have just given up
[11:05] <willcooke> seb128, is the fix the same as the BT speakers?  You want me to try and make a deb diff patch?
[11:05] <seb128> willcooke, no, that's different
[11:05] <seb128> I'm trying to get charles_'s input
[11:05] <seb128> but maybe it's mpt's one we need
[11:05] <seb128> bug #1470080
[11:06] <Trevinho> hey seb128 did you see my u-s-d branches? One looks big, but it's just backporting stuff
[11:06] <seb128> willcooke, it seems that the issue is that upower doesn't tell us the device state (charging/discharging/...) and upower display a image-not-found in that case
[11:06] <seb128> hey Trevinho!
[11:07] <Trevinho> hey seb128, had a nice WE?
[11:07] <seb128> willcooke, that seems like a poor default/fallback though, I think either we should charging icon or not list the device
[11:07] <seb128> Trevinho, yes, quite relaxing! you?
[11:08] <Trevinho> seb128: yeah, quite good.
[11:08] <seb128> Trevinho, I saw you had some branches for the screensaver/proxy thing, I've on my todo to look at u-s-d today, we should have a look to do a landing
[11:08] <seb128> Trevinho, how is the bamf landing/SRU going btw?
[11:08] <willcooke> seb128, yeah, looks like any useful info about battery is missing:  http://imgur.com/wqKwcbn
[11:09] <seb128> willcooke, I would think we should just ignore/not list the device at all
[11:09] <mpt> seb128, agreed
[11:09] <willcooke> seb128, +1
[11:09] <Trevinho> seb128: I'm waiting the upstart missing dependency to land in yakkety, but sru branches are almost ready
[11:09] <seb128> willcooke, mpt, thanks
[11:10] <seb128> Trevinho, why is upstart blocking bamf?
[11:10] <seb128> that doesn't make any sense to me
[11:10] <Trevinho> seb128: it's a build dep
[11:10] <Trevinho> seb128: but only for mainframes... I actually would publish it
[11:11] <seb128> $ apt-cache showsrc bamf | grep upstart
[11:11] <seb128> $
[11:11] <mpt> seb128, why was it ever showing up in the menu? Is it that we know the charge level, but not whether it’s charging right now?
[11:11] <seb128> mpt, correct
[11:11] <Trevinho> seb128: I mean, the silo is waiting... And the dep is in unity
[11:11] <Trevinho> seb128: you remember https://requests.ci-train.ubuntu.com/#/ticket/1419
[11:11] <seb128>   phone
[11:11] <seb128>     rechargeable:        yes
[11:11] <seb128>     percentage:          11%
[11:11] <Trevinho> Laney: would you hit the publish thing for that, or want to wait ^^^^
[11:11] <Trevinho> ?
[11:11] <seb128> mpt, ^ that's all we know
[11:11] <mpt> huh, I never considered that case
[11:12] <seb128> Trevinho, right, my point is "why does bamf needs to land with unity/be blocked on it"
[11:12] <seb128> Trevinho, seems like we have an important fix that should be fast tracked
[11:12] <seb128> Trevinho, is it should be decoupled from other things and land
[11:12] <Trevinho> seb128: I thought it would have been a quick landing, instead it got blocked by that.. This I found there was no reason for making a new silo
[11:13] <seb128> right
[11:13] <seb128> that reasoning is clearly failing though...
[11:13] <mpt> seb128, and, we don’t have a generic icon for phones?
[11:13] <seb128> Trevinho, if we learnt one thing is that there is never easy unity landings ;-)
[11:14] <Trevinho> well... true... but not recently
[11:14] <Trevinho> anyway, I would think that we can just unblock things
[11:15] <seb128> how?
[11:15] <seb128> upstart needs to be fixed to land unity...
[11:15] <seb128> xnox, hey, are you looking at fixing upstart build in y?
[11:15] <Trevinho> can't we just publish? since it's only blocked for one arch
[11:15] <seb128> mpt, we don't have a phone case ... the code is http://paste.ubuntu.com/16630843/
[11:15] <seb128> Trevinho, well, it's not going to migrate out of proposed so it doesn't help you much
[11:16] <Laney> delete upstart from proposed
[11:16] <seb128> or that
[11:16] <Laney> think x_nox is away this week
[11:17] <seb128> mpt, we could add a "phone" case and display a phone icon, or a normal battery ...
[11:18] <mpt> seb128, ok, so I think we have two bugs … (1) If we know the charge but not whether it’s charging/discharging, it’s still useful to show that inside the menu, but the device shouldn’t have ever made it to the title. (2) The fallback icon should be an “unknown device” icon, not a “-missing” icon.
[11:19] <Trevinho> Laney: do you think that is possible? As I'd love to push the whole thing, but if it's not working, I've to decuple bamf...
[11:19] <Trevinho> and it's annoying anwyay
[11:20] <seb128> mpt, do we have a "unknown device" icon?
[11:21] <Laney> Trevinho: I don't have the power to fix upstart
[11:22] <mpt> seb128, you know far more about where to find icons on the system than I ever will
[11:22] <Trevinho> Laney: that means, that there's no other way than making me split the silo, right?
[11:24] <Laney> no, see what you just got pinged about in #ubuntu-devel
[11:24] <seb128> mpt, we don't have an icon for that that I can see ...
[11:24] <seb128> mpt, I guess we can start by fixing (1) and making devices without a charging/discharging info non primary ... want to comment about that on the bug?
[11:25] <mpt> seb128, sure
[11:25] <seb128> thanks!
[11:43] <andyrock> hey all
[11:56] <willcooke> seb128, phone has just finished charging and now the icons are back to normal
[11:56] <willcooke> and I have a little phone icon in the list
[11:58] <willcooke> seb128, http://imgur.com/lel38wq
[12:20] <Sweet5hark> 1/ backup? check 2/ after-release cleanup? check 3/ setting up yakkety pbuilder/jenkins-foo? ongoing
[12:28] <seb128> andyrock, hey!
[12:28] <seb128> willcooke, yeah, we get the "charged" info not the charging/discharging one
[12:29] <seb128> willcooke, thanks for testing
[12:30] <mpt> seb128, done
[12:30] <seb128> mpt, thanks
[12:30] <seb128> hey Sweet5hark!
[12:30] <Sweet5hark> seb128: yes?
[12:31] <seb128> Sweet5hark, btw seems doko updated libreoffice to y so you don't have to do it ... nice from it to step up to maintain libreoffice this cycle
[12:33] <Sweet5hark> seb128: https://launchpad.net/ubuntu/+source/libreoffice/1:5.1.3-0ubuntu3 <- it failed to build due to mdds being to new on yakkety, so I got an email from doko to take care of it.
[12:33] <Sweet5hark> (which is fine, just needed finishing the backup/cleanup dance before going there ...
[12:33] <seb128> Sweet5hark, he uploads, he can take care of it imgo
[12:33] <seb128> imho
[12:53] <pitti> not IMHO
[12:53] <pitti> doko cleaning up after other people does not mean to completely take over other people's work :)
[12:53] <seb128> well nobody asking him to "clean up"
[12:56]  * ricotz notes there are library transitions which he isn't ignoring
[12:57] <pitti> yeah, he's the poor guy doing most of the lib transition/FTBFS/NBS in Ubuntu
[12:57] <seb128> the issue with him is that he does random uploads for things actively maintained by others without talking to the maintainer first
[12:57] <seb128> and often ignoring the vcs on the way
[12:57] <seb128> so yeah, he creates more work for him and for others
[12:57]  * ricotz is feeling ignored when he mentioned the mdds issue
[12:58] <pitti> agreed on this specific LibO upload; but not in general
[12:58] <seb128> he tends to do
[12:58] <seb128> +that
[12:58] <seb128> but yeah, he also do lot of useful work
[12:58] <pitti> if you upload hundreds of packages because other people don't care about them, you don't figure out the pckaging quirks of every single one
[12:58] <seb128> well, you know that some packages are maintained
[12:59] <seb128> like I wouldn't do a cowboy fix to systemd without talking to your first
[12:59] <pitti> right
[12:59] <ricotz> imho there is still the rules of thumb that the version in the current dev-release should higher then in previous maintained ones
[12:59] <seb128> ricotz, don't, it's usually that people are just too busy to comment/reply to everything
[13:00] <ricotz> I remember Sweet5hark answering
[13:00] <seb128> ricotz, you can't upload older versions :p
[13:00] <seb128> and we are supposed to upload to devel before SRU
[13:00] <seb128> though sometime it makes sense to not block SRU work while newest serie is being prepared
[13:01] <ricotz> seb128, yes which is regularly not happing for libreoffice
[13:01] <ricotz> *happening
[13:01] <seb128> right, because libreoffice is big
[13:01] <ricotz> it is *really* not hard to do so
[13:01] <seb128> and it takes time to start on a new serie
[13:01] <seb128> it's not hard
[13:01] <ricotz> it doesnt in this case
[13:01] <seb128> it's time consuming
[13:02] <seb128> and priorities might be on other things
[13:02] <ricotz> if you prepare an upload of xenial you can easily do a yakkety one in parallel
[13:02] <pitti> the rule makes sense because pretty well all of our tens of thousands of packages are simple to upload to devel first, and we have no other means to control that we don't drop fixes
[13:02] <pitti> look at the disaster in ubuntu touch that we had a while back
[13:02] <seb128> right
[13:02] <pitti> LibO is a special snowflake here
[13:03] <ricotz> which is should not be imo
[13:03] <seb128> it's not like having 5.1.3 was making any difference to anyone
[13:03] <pitti> so if we have *some* other way to pressure Sweet5hark to upload LibO before alpha-1 and can track this somewhere, and convey this special policy to the SRU team, it might work
[13:04] <willcooke> late lunch today, got some errands to run, bbl
[13:04] <pitti> but yeah, such rare exceptions to processes and workflows (which also need to get encoded into tools like sru-review) are a nuisance
[13:04] <seb128> willcooke, enjoy!
[13:04] <ricotz> even if 5.2 beta 1 is tagged this week will it land in yakkety too by friday?
[13:04] <seb128> pitti, well, imho we don't want an exception
[13:04] <pitti> seb128: hm, I thought you did
[13:05] <seb128> pitti, no, just depending on the circumstance sometime I think it makes sense to not enforce
[13:05] <pitti> ... which is called an exception :)
[13:05] <seb128> pitti, same as atm important unity fixes are blocked to be SRUed because upstart in yakkety ftbfs on s390x
[13:05] <seb128> which block the landing in y
[13:05] <seb128> which blocks the SRU
[13:06] <seb128> unity landing*
[13:06] <pitti> that sounds curious
[13:06] <seb128> why?
[13:07] <pitti> so xenial-proposed unity has a strict dependency on an upstart fix to xenial which doesn't land in y?
[13:07] <seb128> ricotz, I doubt 5.2 is going to land this week, at the same time I don't think it's important
[13:07] <pitti> seb128: btw, at least I require "fix in devel-proposed", not "fix in devel"
[13:07] <seb128> pitti, no, Trevinho wants to respect the SRU rules to land in yakkety before SRUing
[13:07] <pitti> so in this case I wouldn't have blocked such an update
[13:07] <pitti> and I did accept the upstart SRU
[13:08] <seb128> pitti, well, except that CI train has its own britney and refuses to land unity while it ftbfs in s390x
[13:08] <seb128> on
[13:08] <ricotz> seb128, what I meant is having 5.2 this is main argument of Sweet5hark to not care about updates of 5.1 in yakkety
[13:08] <Sweet5hark> woa, epic drama on the channel ;) -- FWIW, my reluctance to forward-port e.g. LibreOffice 5.1 to yakkety is that it is wasted effort for the most part. Take this mdds thing: a/ we wont release yakkety final with LO 5.1, so fixing 5.1 against newer mddses is helping anyone in production b/ massaging e.g. LibreOffice 5.1 to bring its own mdds on yakkety isnt too much work, true. Then again, doing such things makes the yakkety and xenial 
[13:08] <pitti> seb128: ah ok, so that's the missing info to my "curious"
[13:09] <seb128> pitti, right, so we can't get it to y-proposed
[13:09] <seb128> pitti, which was my earlier ping on -devel about deleting that version of upstart
[13:09] <seb128> which I think I'm going to do
[13:09] <seb128> L_aney said x_nox was out this week
[13:09] <pitti> seb128: you mean remove it on s390x?
[13:09] <seb128> no
[13:09] <pitti> (which seems fine)
[13:09] <seb128> delete the version in proposed
[13:09] <pitti> ah
[13:09] <pitti> sure, go ahead
[13:09] <seb128> thanks
[13:10] <pitti> it breaks its tests anyway
[13:10] <pitti> seb128: ok, seems I should resume my work to move away from upstart in the graphical session :)
[13:10] <seb128> :-)
[13:11] <seb128> ricotz, well, uploads to yakkety requires out to have yakkety envs/installs/vms to do work, which takes some work. I for one didn't start yet and I think the lts is higher priority still and I'm happy to delay y-work
[13:12] <seb128> ricotz, so different people have different priorities
[13:12] <seb128> ricotz, seems you enjoy the most recent series/updates work which is fine, but don't blame others which focus on other parts of Ubuntu
[13:12] <ricotz> Sweet5hark, will try to get an updated forward-port to the ppa later
[13:15] <pitti> seb128: btw, can you please try "pkexec whoami"? does that actually work for you?
[13:15] <pitti> seb128: (the command doesn't matter, I'd like to know whether pkexec works)
[13:15] <seb128> $ pkexec whoami
[13:15] <seb128> root
[13:15] <seb128> yes
[13:15] <pitti> seb128: thanks; I was a bit scared
[13:15] <seb128> it asked me for credential and took it
[13:15] <seb128> I'm on xenial though
[13:15] <pitti> so I guess I just wrecked my machine
[13:15] <pitti> seb128: yes, me too
[13:16] <ricotz> seb128, I am working on the libreoffice packaging and backports, so I am familiar with the process and it is really not that difficult to do, so I am opinion stands that dev-pocket must have corresponding highest version in the archive and library transitions must be followed for the sake of buildable isos
[13:16] <seb128> ricotz, yeah, I agree on principle, in practice days have a limited number of hours and we have many things to work on
[13:18] <ricotz> alright, I don't want to go more into detail here
[13:51] <willcooke> back
[13:52] <seb128> wb willcooke
[13:52] <willcooke> dropped a load of stuff off at the charity shop and dry cleaning at the dry cleaners.  Great success!
[13:53] <seb128> hope you didn't mix those!
[13:54] <seb128> having the old stuff back from the dry cleaner ;-)
[13:54] <willcooke> :D
[14:41] <Sweet5hark> thunderbolt and lightning, very very frightning!
[14:42]  * Sweet5hark bets the guy driving the crane on the construction side next door curses the day he said he wanted an "exciting job" ....
[14:43] <chrisccoulson> Sweet5hark, that sounds awesome
[14:45] <Sweet5hark> chrisccoulson: I mean: I prolly _is_ a Faraday cage. But still.
[16:07] <seb128> Trevinho, https://code.launchpad.net/~robert-ancell/unity-settings-daemon/no-gnome-shell/+merge/289104 seems to merge fine here?
[16:20] <ximion> Laney: looking at the version number on appstream.ubuntu.com, you might want to update the dep11-generator and apply your patches on the latest Git master
[16:20] <ximion> there weren't many changes, and all that changed was bugfixes, so that would be useful :)
[16:22] <ximion> support for immutable suites will follow in a future release of asgen, I think the hardlink-solution is actually pretty good - will take some time to implement, though
[16:23] <Laney> yeah ok
[16:23] <ximion> a slightly better solution would be to use a fast relational database as data store, but I don't want to make people using asgen also install a full Postgres or MySQL database
[16:23] <ximion> (keeping it simple is likely better here)
[16:26] <seb128> Trevinho, https://requests.ci-train.ubuntu.com/#/ticket/1419 isn't red anymore
[16:26] <Trevinho> seb128: it wasn't merging when approving the other roberts' branches
[16:27] <seb128> Trevinho, oh, that's different from not merging
[16:28] <seb128> seems like https://code.launchpad.net/~robert-ancell/unity-settings-daemon/no-print-notification/+merge/289103 includes the same change
[16:30] <seb128> Trevinho, thanks for pointing that out!
[16:31] <Trevinho> seb128: well, yeah... it doesn't merge with other branches... Sorry I have not been clear in the reivew :)
[16:31] <seb128> Trevinho, no worry, I commented on the other one now
[17:09] <Laney> night!
[17:09] <willcooke> cya Laney
[17:12] <seb128> night Laney!
[18:45] <willcooke> night all