[01:44] <InHisName1> kids asleep, finally - now back
[09:21] <rmg51> Morning
[09:27] <JonathanD> Morning.
[09:37] <rmg51> 0/
[09:39] <JonathanD> Whats up?
[09:39] <JonathanD> Going to the store?
[09:40] <rmg51> shortly
[09:40] <rmg51> then to PACS
[09:41] <JonathanD> ooh pacs
[09:43] <rmg51> today jedijf is going to do his best to break Teddy's old laptop :P
[09:44] <rmg51> which shouldn't be to hard for him :-D
[09:45] <JonathanD> Maybe I should come see if someone can make my touchscreen work :/
[09:46] <rmg51> that someone would be jedijf
[09:46] <rmg51> he could just make it worse
[09:46] <rmg51> he is known for that
[09:46] <rmg51> but he does manager to fix things every once on a while
[09:49] <JonathanD> heh :p
[09:50] <rmg51> with him you always take your chances ;-)
[09:56] <rmg51> he's not as bad as it sounds
[09:57] <rmg51> a lot of it is a running joke
[09:57] <rmg51> but as he will tell you himself, he learns by breaking things
[09:57] <rmg51> time to go shopping
[10:00] <JonathanD> have fun.
[10:26] <jedijf> JonathanD: i have a few of my own to try
[10:27] <JonathanD> touchscreens?
[10:27] <jedijf> JonathanD: i did google some interesting stuff specifically for yours
[10:27] <JonathanD> I wasn't finding much of use on google yesterday.
[10:27] <JonathanD> jedijf: of course, I left it at work, too. so I probably can't do anything til monday.
[10:27] <jedijf> does it work with pen
[10:27] <JonathanD> unless I go get it.
[10:27] <JonathanD> jedijf: nope
[10:29] <jedijf> if i have a chance i find that link and you can try on monday, have to prepare for pacs, finish reapproval app
[10:29] <jedijf> too much to do
[10:30] <JonathanD> kk
[10:30] <JonathanD> take care :)
[10:30] <jedijf> its reported to work automagically with 9.04
[10:30] <JonathanD> it did work with 9.04
[10:30] <JonathanD> iirc
[10:31] <JonathanD> works presently with the windows dev thing, too.
[10:31] <InHisName1> quite the early conversations this morning
[10:31] <JonathanD> So I know it's functional.
[10:32] <JonathanD> hi InHisName1
[10:32] <JonathanD> This is when the REAL work gets done.
[10:32] <InHisName1> Hi, I got my HP touchPad a couple of weeks earlier than they promised.
[10:33] <JonathanD> sweet.
[10:33] <InHisName1> I have no wireless so it is not activated yet.
[10:33] <JonathanD> oh you were mentioning that
[10:33] <InHisName1> Hope I can do that at Giant at PACS today.
[10:33] <JonathanD> InHisName1: go to pacs!
[10:33] <JonathanD> yes
[10:33] <JonathanD> tehre
[10:33] <JonathanD> problem solved
[10:34] <JonathanD> And if you can't get it to work bring it to me and I'll activate it and give it back to you next year.
[10:34] <InHisName1> maybe.   Cept for using it at home, remember no wireless yet.
[10:34] <JonathanD> Does it function without wifi?
[10:34] <InHisName1> 'next year' ?

[10:34] <JonathanD> as in, I'll use it for a year, then give tit to you.
[10:34] <InHisName1> the apps should function once activated.
[10:34] <JonathanD> *it
[10:35] <InHisName1> as long as they don't need internet to function.
[10:35] <JonathanD> makes sense.
[10:35] <InHisName1> tit ?
[10:35] <JonathanD> *it
[10:37] <InHisName1> I've been browsing for wireless routers and found a pretty decent one that has refurb pricing on eBay that's MUCH better than best new prices.
[10:37] <JonathanD> Wait?
[10:38] <JonathanD> all you need is a router?
[10:38] <InHisName1> No - need wireless access point.
[10:38] <InHisName1> want a few cat5 1gig sockets.
[10:39] <InHisName1> someones awake bbl8tr
[10:42] <InHisName1> wow, whomever, just went back to bed.  No whooping noises or anything.   I have a bit more time.
[11:55] <beta0x64> goede morgen
[15:30] <musetux> Greetings All!
[15:30] <pleia2> hello musetux
[15:31] <musetux> jedijf: Nat Mechs was a cool joint. It was nice to meet you. and thanks for all the info!
[15:32] <JonathanD>  /249
[15:33] <pleia2> yeah, they did a nice job handling the crowd, and it wasn't too loud to carry a conversation
[15:48] <jedijf> musetux: it awesome to have you!
[17:49] <pleia2> jedijf: btw http://princessleia.com/journal/?p=5157
[23:48] <jedijf> pleia2: i saw earlier ty


[13:33] <BluesKaj> 'Morning folks
[22:12] <santa_> hi everyone
[22:13] <santa_> RikMills: what do you plan to do with apps 21.08.3 ? I got some FTBFS here because of symbols files
[22:14] <RikMills> fixed so far
[22:15] <santa_> ah, ok
[22:15] <santa_> I'm about to rebuild everything again
[22:15] <santa_> (from _staging)
[22:15] <RikMills> so far just updated them in jammy. perhaps some really need to be optional, but can see about the later
[22:17] <santa_> for kcoreaddons, I have here the package with the proper fix (i.e. the upstream patch, so for the next release it will fail to apply so we don't forget to re-enable the thing)
[22:17] <RikMills> ok
[22:18] <santa_> push to _staging [y/n]?
[22:18] <RikMills> please do
[22:19] <santa_> oh well
[22:20] <santa_> your fix of symbols apparently unblocked some builds in my server XD
[22:20] <RikMills> :)
[22:30] <santa_> RikMills: kcoreaddons fix pushed
[22:34] <RikMills> ack. I will do that later or in the morning


[12:16] <ryanakca> thanks
[12:17] <gnomefreak> i use it that way so it stays with the same scheme ;)
[12:17] <gnomefreak> yw
[12:17] <Riddell> ryanakca: known problem
[12:17] <Riddell> tonio uploaded a fix
[12:17] <ryanakca> Riddell: kk, thanks
[12:56] <nixternal> anyone with KDE SVN+SSH: is your initial connection, where it checks the SVN and then asks for your password, slow? I notice constant HD activity when I do svn up and it takes a minute until it asks for a password for my SSH key
[05:09] <manchicken> Riddell: What now?
[05:09] <manchicken> ^_^
[05:10] <manchicken> (I suppose it's 0400 where you are, so I suppose you won't be on.  Silly me.)
[05:30] <ryanakca> is KNetworkManager supposed to be wireless network only? or should it detect eth0?
[05:30] <ash211__> from what I've read, it's supposed to do wireless & wired
[05:31] <ryanakca> ash211: hmm... odd... it's showing "No network devices found."
[05:31] <ash211> yes, see http://en.opensuse.org/Projects/KNetworkManager
[05:31] <ryanakca> hmmm... file a bug?
[05:32] <ash211> I'd guess so
[05:32] <ash211> I'm not really familiar with it...
[05:34] <ryanakca> nor I... I just noticed it in my kicker's tray...
[05:35] <ryanakca> hmm...  I'll ask about it again in the morning... g'night
[05:38] <nixternal> ryanakca: it does both
[05:38] <ryanakca> nixternal: so, file a bug?
[05:39] <nixternal> no, you have to make sure your /etc/network/interfaces is set to auto for everything
[05:39] <nixternal> auto lo
[05:39] <nixternal> iface lo inet loopback
[05:39] <nixternal> auto eth0
[05:39] <nixternal> iface eth0 inet dhcp
[05:39] <nixternal> and so on
[05:40] <ryanakca> yep
[05:40] <ryanakca> s/dhcp/static
[05:40] <nixternal> no static
[05:41] <nixternal> knetworkmanager works with dhcp only ;(
[05:41] <ryanakca> http://www.pastebin.ca/323245
[05:41] <ryanakca> :(
[05:41] <ryanakca> kk
[05:41] <nixternal> oh ya, that is why knetwork manager doesn't see it
[05:41] <nixternal> but if you disable wireless with knetwork manager, it will use your eth0 automatically then
[05:43] <ryanakca> ok, edited to http://www.pastebin.ca/323248 , /etc/init.d/networking restart, restarted KNetworkManager, same thing...
[05:43] <ryanakca> hmm...
[05:44] <nixternal> get rid of all of that address stuff
[05:45] <ryanakca> nevermind, yep
[05:45] <ryanakca> restarting them...
[05:45] <nixternal> heh, seems one of my neighbors has setup a new wifi network
[05:46] <nixternal> and they have to be super close
[05:46] <ryanakca> nixternal: updated to http://www.pastebin.ca/323251 ... same thing... hmm...
[05:46] <ryanakca> lol
[05:46] <nixternal> http://www.pastebin.ca/323254
[05:47] <ryanakca> My cousin built some gadget to amplify the wifi networks in the area so he could use them... dunno if it actually worked or not...
[05:47] <nixternal> that is all i have in mine, and iirc anything else in there made it not work
[05:47] <nixternal> probably made a yaggi or a cantennae
[05:48] <nixternal> you can't amplify a wifi signal because it will take it out of the band, creating a more powerful antennae is what you do so there is no db loss
[05:48] <nixternal> for every inch away from a typical wifi router you usually loose 1db
[05:50] <ryanakca> ah
[05:50] <manchicken> I'm out of stuff to hack :(
[05:51] <manchicken> I'm gonna look at the adept spec again.
[05:51] <nixternal> heh
[05:51] <ryanakca> hmm... same thing... oh well... I don't need it :)
[05:51] <nixternal> lol
[05:51] <nixternal> don't know why it isn't working for you
[05:51] <ryanakca> nor do I :)
[05:51] <nixternal> i think it is popcorn and movie time
[05:51] <nixternal> manchicken: wanna cuddle?
[05:51] <ryanakca> hmm...
[05:51] <ryanakca> see yah
[05:52] <nixternal> later ryanakca :)
[05:52] <ryanakca> bedtime here :)
[05:52] <nixternal> close here
[05:52] <ryanakca> hmm... I can mute and put the volume down... and I can play/pause... but not put it up... *adds that to his todo for the morning*
[05:55] <manchicken> nixternal: My kitty beat you to it.  Maybe later.
[05:57] <manchicken> I have two.
[05:57] <Jucato> wow
[05:57] <manchicken> But if one of them keeps pissing all over everything I'll shortly have only one.
[05:57] <Jucato> lol
[05:58] <manchicken> NOTHING is more infuriating than laying down in a bed just to find a wet spot.
[05:58] <Jucato> hah
[05:58] <Jucato> if I had a cat, I'd train it not to do that... :(
[05:58] <manchicken> I've tried.
[05:58] <manchicken> BELIEVE ME, I've tried.
[05:58] <Jucato> and not to leave it's poop inside the house... make it go to the neighbor...
[08:08] <praetor> Hobbsee: hullo :-)
[08:08] <Hobbsee> heya praetor :)
[08:09] <praetor> i'm all settled in and ready to code once more
[08:11] <Hobbsee> praetor: woot :D
[08:11] <Hobbsee> praetor: however, i'm going out, sorry :(
[08:12] <praetor> nw, i see adept development is moving along nicely
[08:12] <Jucato> Hobbsee: remember that article I was talking about? the one from desktoplinux.com?
[08:13] <Hobbsee> Jucato: yeah
[08:13] <Hobbsee> Jucato: i'm out - i'll read the backscroll though
[08:13] <Jucato> Hobbsee: it was on digg (thank goodness not /.)... I was quite surprised... lots of positive comments, no negative...
[08:14] <Hobbsee> Jucato: wow.  it's on crack, and inaccurate though
[08:15] <Jucato> yeah. that's why I was surprised...
[08:15] <Jucato> hm...
[10:41] <mhb> ryanakca: it doesn't show ANY wireless network on my laptop & my girlfriend's
[02:28] <Hobbsee> praetor_: so we should find you some more to code?
[02:29] <praetor_> Hobbsee: i've been looking through the adept stuff a bit
[02:29] <praetor_> i'll find something to keep myself busy
[02:29] <Hobbsee> praetor_: :0
[02:29] <Hobbsee> * :)
[02:30] <Jucato> heh looks like Adapt is getting all the love it needs (and deserves??) :)
[02:30] <Hobbsee> hehe, nice :)
[02:31] <abattoir> adept? or is there some new tool?
[02:31] <Jucato> abattoir: changes have been made to Adept the past days... courtesy of manchicken
[02:31] <abattoir> oh, nice
[02:31] <Jucato> the new Manage Repositories is still in the works though :(
[02:34] <praetor_> Jucato: I got it from backports, but it didn't work
[02:35] <Jucato> praetor_: the one in -backports is Flash 9 Beta 2
[02:35] <praetor_> so what I did was just go and d/l it from adobe, then copy the .so file into the appropriate plugins direc
[02:35] <\sh> moins
[02:37] <praetor_> Jucato: ah you are right, the one in backports is beta.
[02:37] <praetor_> still, if you need it, just d/l the .tar.gz archive and move the .so file
[02:38] <Jucato> yeah... but I'm old fashioned... I prefer to use the repos... so that I have someone to blame if things go wrong :P
[02:38] <Lure> \sh: congrats
[02:38] <\sh> lure: thx :)
[02:39] <\sh> guys, I'm just getting totally crazy...
[02:39] <Hobbsee> oh?
[02:39] <Hobbsee> congrats, \sh :)
[02:39] <\sh> Hobbsee: my gf is pregnant
[02:39] <Hobbsee> yes, but why crazy?
[02:39] <Lure> \sh: wait for 9 months for "totally crazy" ;-)
[02:40] <\sh> Lure: the news just hit me suddenly...she was just telling it as it was something normal...you know...
[02:40] <Hobbsee> heh
[02:42] <Jucato> kubuntu sticker?!?!
[02:43] <praetor_> where do you get these kubuntu stickers anyway?
[02:44] <Hobbsee> praetor: linux conf - any of them
[02:44] <Lure> Jucato: I got ubuntu stickers, as I ordered one ubuntu cd with my kubuntu pack ;-)
[02:44] <praetor> no possibility of getting some mailed or something?
[02:45] <Hobbsee> dunno
[02:45] <Jucato> Lure: yeah.. when I heard that there were Ubuntu stickers, I was sooo tempted to order Ubuntu CD's :D
[02:45] <Hobbsee> Lure: :)
[02:45] <Hobbsee> Lure: i pinched the last one off the table - i saw some more in the bags..
[02:45] <praetor> 2 mates that did cs with me went to linux conf
[02:45] <praetor> they said they had a great time and got to have a beer with the guy who wrote iptables
[02:45] <Lure> Hobbsee: I got some ubuntu stickers on uds-mtv though - to make friends happy ;-)
[02:46] <Hobbsee> :D
[02:46] <Jucato> stickers stickers stickers!! :(
[02:47] <Hobbsee> hehe
[02:57] <ryanakca> should I file a bug on it taking about 35 minutes for one page to print with cups threw samba up to my XP machine?
[02:59] <Lure> ryanakca: sounds like a bug
[02:59] <ryanakca> Lure: kk
[03:10] <sredna> Hello
[03:11] <sredna> Is it possible to install qt4 demos in kubuntu?
[03:11] <ryanakca> hey sredna
[03:11] <sredna> I have qt4demo, but there is no way to activate the actual demo programs
[03:13] <ryanakca> Lure: sounds like an ongoing problems since april '06... bug 39484 ... even though mine did print a test page... hmm...
[03:13] <Ubugtu> Malone bug 39484 in samba "cups smb printing backend no longer works" [High,Confirmed]  https://launchpad.net/bugs/39484
[03:26] <serzholino> hi! will be updates from dapper to feisty supported?
[03:26] <serzholino> or only via update to edgy first?
[03:28] <praetor> afaik, you can't skip upgrades, so dapper->feisty will not work
[03:30] <serzholino> ok
[03:30] <serzholino> is it known bug tat konqueror crashes randomly on right mouse click on file in edgy?
[06:17] <MidMark> hi, guys with Edgy how can I say to kppp to override the default gateway to the one returned by the ppp connections? I have always the <IP_ADDRESS> that was the old default
[07:24] <mhb> good evening
[07:26] <manchicken> Yay timezones!
[07:27] <manchicken> Hello all you happy people.
[07:30] <gnomefreak> jdong: you busy?
[11:13] <manchicken> Is there a limit to how many bazaar branches you can store on launchpad?
[11:14] <ryanakca> manchicken: dunno... I just store mine in +junk...
[11:14] <manchicken> There's a #launchpad?
[11:14] <manchicken> Neat.
[11:15] <ryanakca> yeah
[11:15] <ryanakca> and a #bzr too :D
[11:16] <manchicken> Yeah.
[11:16] <manchicken> I like svn more though.
[11:16] <manchicken> Maybe once they make it faster, and there's some emacs support, it'll be better.
[11:16] <manchicken> Either way, version control is version control.
[11:17] <ryanakca> instead of always having to commit on a remote server...
[11:17] <manchicken> Yeah, that's nice.
[11:17] <manchicken> I know lots of people who still use CVS.
[11:17] <ryanakca> ah
[11:17] <manchicken> I never really minded CVS.
[11:19] <manchicken> svn and .bzr is that they keep too many files around though.
[11:20] <ryanakca> too many programs I want to write when I can't even figure out how to do a simple task that Riddell gave me...
[11:20] <manchicken> What did he give you?
[11:20] <ryanakca> something about adding UPS to kde-hal-device-manager...
[11:21] <manchicken> Is that using .desktop stuff?
[11:22] <ryanakca> from what I see in the code, it's all automaticly recognised threw hal or something of the sort... so I don't know how I could add it... python
[11:23] <ryanakca> of course, I probably have it all wrong... I'll work on it next week... I have 6 days off after exams... which I should probably be studying for... meh
[11:23] <manchicken> Ah.  I'm not a big Python guy.
[11:24] <manchicken> I wouldn't mind doing more in that area, but I really would prefer to be doing C++
[11:28] <manchicken> No such thing.
[11:29] <manchicken> Every language has its complexities ^_^
[11:29] <ryanakca> lol
[11:29] <ryanakca> well... a higher level language?
[11:29] <manchicken> Thing that gets me is the whole indentation thing.
[11:29] <manchicken> Kinda seems silly to me.
[11:30] <ryanakca> sure, I could go to esolang.org and learn glass or bf or another crazy low level/esoteric language... and get more confused that with C++...  but... nah
[11:30] <ryanakca> lol... indentation... makes it easier to read? which means easier to maintain?
[11:30] <manchicken> Naw.
[11:31] <manchicken> Makes it hard to maintain when you've got some people who like tabs and some people who like spaces though ;)
[11:31] <manchicken> Either way, they're all just languages.
[11:31] <manchicken> And we've got a lot of python code out there.
[11:31] <manchicken> We need someone who can work it well ^_^
[11:32] <gnomefreak> anyone here know why apports not included in kde?
[11:32] <gnomefreak> !info apport
[11:32] <ubotu> apport: automatically generate crash reports for debugging. In component main, is optional. Version 0.28 (edgy), package size 22 kB, installed size 156 kB
[11:32] <gnomefreak> i got someone that lost 30gigs over night
[11:33] <manchicken> You mean drkonqui?
[11:33] <ryanakca> hmm.. no clue
[11:33] <manchicken> (drkonqi?)
[11:33] <gnomefreak> was wondering if ff crashed many times over. where does kde store crash reports or is it backtrace on own
[11:33] <ryanakca> gnomefreak: ouch... how?
[11:33] <gnomefreak> ryanakca: working on it
[11:33] <gnomefreak> not sure
[11:34] <ryanakca> manchicken: http://esolangs.org/wiki/Black   ... now that's what I define as a... confusing language?
[11:35] <ryanakca> manchicken: still waiting for them to answer :)
[11:35] <manchicken> ryanakca: Look up APL
[11:35] <ryanakca> assembly?
[11:35] <manchicken> No.
[11:35] <ryanakca> or no...
[11:35] <manchicken> the A Programming Language
[11:35] <manchicken> An old Bell Labs feller.
[11:36] <manchicken> Very old.
[11:37] <ryanakca> heh, doesn't even use the english alphabet...
[11:37] <manchicken> Nope.  Greek alphabet.
[11:37] <ryanakca> heh
[11:39] <manchicken> Most of those languages you're seeing on esolangs are experimental things that people do to learn.
[11:39] <manchicken> I made my own programming language once.
[11:39] <manchicken> It was an interpreted language executed by a Perl script.
[11:39] <manchicken> That was fun.
[11:39] <ryanakca> Appeared in: 1964... hehe... that's... 43 years old...
[11:39] <manchicken> But it was slow.
[11:39] <ryanakca> lol
[11:40] <ryanakca> [17:38]  <mpt> ryanakca, probably after a few billion the database will get a bit flaky
[11:40] <ryanakca> [17:39]  <LarstiQ> ryanakca: not that I know of
[11:40] <ryanakca> there's your answer :)
[11:40] <manchicken> cool
[11:40] <ryanakca> put your junk repos in +junk though... :)
[11:40] <gnomefreak> any devels feel like helping with this weird ass issue?
[11:40] <gnomefreak> lol
[11:40] <ryanakca> anywais, bbl, supper
[11:40] <manchicken> What about a launchpad space limitation?
[11:40] <manchicken> gnomefreak: What issue?
[11:41] <gnomefreak> the loss of 30gigs over night
[11:41] <manchicken> Wow.
[11:41] <gnomefreak> no kidding
[11:41] <manchicken> Loss of data or loss of space?
[11:42] <gnomefreak> he says hes missing 30gig i think its just not showing data seems to be there
[11:42] <manchicken> In kubuntu?
[11:42] <gnomefreak> im waiting for an answer on how big drive is
[11:42] <gnomefreak> yeah
[11:42] <manchicken> #kubuntu even
[11:43] <manchicken> Who's having the issue?
[11:44] <gnomefreak> thehound
[11:45] <manchicken> YES!!!


[07:10] <kjackal> Good morning Juju world!
[07:46] <BlackDex> Hello there
[07:46] <BlackDex> I have an environment where i have juju in HA using 3 nodes
[07:47] <BlackDex> unfortunally i need to remove 2 of those nodes now because of maintenance
[07:47] <BlackDex> how can i remove those nodes manually and afterwards just create new ones?
[07:48] <BlackDex> can i juse do juju remove-machine on the controller model?
[07:53] <kjackal_> Hi BlackDex, based on this: https://jujucharms.com/docs/2.1/controllers-ha
[07:54] <kjackal_> BlackDex: "The only way to decrease is to create a backup of your environment and then restore the backup to a new environment, which starts with a single controller. You can then increase to the desired number."
[07:54] <kjackal_> BlackDex: never done that
[09:14] <BlackDex> kjackal: Well, one controller is still a controller right
[09:14] <BlackDex> ill first create a backup, and remove the 2 machines
[09:28] <BlackDex> hmm shutting down the 2 nodes prevents me from using `juju` at all
[09:28] <BlackDex> thats not really ha then :)
[12:56] <lazyPower> o/ kjackal /buffer 2
[12:56] <kjackal> hello lazyPower
[12:57] <kjackal> what's this code language "/buffer 2"
[12:57] <kjackal> ?
[12:57] <kjackal> lazyPower: ^
[12:58] <lazyPower> lol sorry
[12:58] <lazyPower> early morning, weechat buffer switching
[13:25] <freyes> hello o/ , where can I find the snapcraft recipe used to build the 'charm' snap?
[14:46] <Zic> hi here
[14:48] <Zic> My CDK cluster running fully@AWS cannot manipulate PV as EBS, I saw on GitHub that it's maybe tied to "CLOUD_PROVIDER" var, do you have any documentation about it?
[14:50] <lazyPower> Zic: we haven't released cloud integration points yet. We're still in a bare-metal first representation of k8s. Work has been started to enable that in a juju native way, but its still WIP
[14:51] <Zic> thanks for the info :)
[14:51] <Zic> lazyPower: do you have any recommendation for PersistentVolume @ AWS so? just a manually created EBS ?
[14:51] <Zic> (or EFS)
[14:52] <lazyPower> Zic: i've been using EFS with great success
[14:52] <lazyPower> but its been only via testing, and i use the NFS volume type
[14:52] <lazyPower> so ymmv - i haven't done battle-hardened testing here, just exploratory work
[14:54] <Zic> lazyPower: is "cloud integration" just control the fact that CDK cluster can auto-create EBS on-demand, or also the fact that K8s can mount EBS volume?
[14:54] <Zic> because I just tried to create the EBS manually and mount it
[14:54] <Zic> -> found invalid field AWSElasticBlockStore for v1.PersistentVolumeSpec
[14:54] <lazyPower> Zic: no, this would be for cloud level integrations. Giving your nodes IAM profiles to request things from the cloud on your behalf
[14:55] <lazyPower> ebs volumes, ELB load balancers, et-al
[14:55] <Zic> ok so I can normally mount manually-created EBS, I need to find why it did not work :(
[14:57] <Zic> I don't need my cluster to auto-create EBS on-demand, I just need the ability to mount them as PersistentVolume :D
[15:07] <Zic> lazyPower: so just to be sure, you confirm that I normally can use this https://kubernetes.io/docs/concepts/storage/volumes/#awselasticblockstore, but I need to create EBS volume manually (as it's precised in the link) before?
[15:08] <Zic> or mounting EBS is also part of cloud-integration and I need to stick with EFS
[15:08] <Zic> (EFS is cool, but not for large micro-access)
[15:19] <Zic> an other solution will be to add "--cloud-provider=aws" to /etc/default/kube-apiserver and kube-controller-manager on master side, and to /etc/default/kubelet node-side
[15:19] <Zic> but Juju will erase this extra-parameter
[17:06] <lazyPower> Zic: you can also place that in the templates in /var/lib/juju/agents/unit-kubernetes-master-#/charm/templates.  But note that once you modify those templates you're making a snowflake.
[17:07] <lazyPower> Zic: but if you strawman out what you're looking for, and propose it, we can certainly review the contribution and help get it landed.
[19:18] <kwmonroe> petevg: cory_fu:  curious about the matrix... http://paste.ubuntu.com/24262725/ is my status output for gce and aws.  you see the core count for those matrix models?  it's as if they deployed with no machine constraints.  contrast that with the non-matrix models in the same job.
[19:18] <kwmonroe> petevg: cory_fu:  i verified that a sample gce matrix unit did in fact have 1 cpu and 2gb ram.  that's not in accordance with any of the constraints set in my bundle.
[19:18] <petevg> kwmonroe: matrix can spin up additional machines, remember.
[19:19] <petevg> kwmonroe: but there might still be stuff missing when translating constraints in python-libjuju.
[19:20] <kwmonroe> ok petevg, so this isn't expected for the matrix first-pass (vs chaos), right?  as in, i should expect my bundle constraints to be honored by matrix?
[19:20] <petevg> That section of the websocket api is kind of broken. (The websocket api doesn't like parsing the plan that it generates.)
[19:20] <petevg> kwmonroe: yes. On the first pass, matrix should honor your constraints.
[19:21] <kwmonroe> thx petevg.. issue-a-coming :)
[19:24] <petevg> kwmonroe: sounds like tons o' fun.
[20:00] <ken_> Very confused.  Set up an Openstack cloud, put all my MAAS nodes in a zone, and tried to go HA -- ran into issues deploying nodes, so decided to back out.  Now I can't "juju add-unit" anything: "cannot run instance: No available machine matches constraints: zone=default".  Re-added all MAAS nodes to default; same issue.  Any ideas before I nuke it all?
[20:02] <ken_> Ah.  Just noticed a couple hundred of these, too: ERROR juju.state database.go:231 using unknown collection "remoteApplications"
[20:11] <ken_> OK.  Rebooting the Juju node still throws some errors, but it *did* result in nodes being deployed.
[22:01] <cholcombe> i don't think you can do this yet but can you tell juju to exclude a set of directories when deploying from a local directory?
[22:08] <hatch> cholcombe not as of yet
[22:08] <cholcombe> hatch: yeah i thought so.  that would be really useful
[22:09] <hatch> yes very :)
[22:09] <hatch> I can't find the bug right now....
[22:09] <hatch> there is/was one
[22:09] <cholcombe> oh cool
[22:09] <cholcombe> someone else had the same thought :)
[22:10] <hatch> cholcombe it might be worth filing another since I'm not able to find it
[22:13] <cholcombe> hatch: ok


[03:59] <Guest63458> hello i need help.. what is the name of a package who have jee5 in ubuntu?
[03:59] <Guest63458> sun-java-6?
[03:59] <Guest63458> or sun-java-5?


[18:43] <Fallen> youngbin: re UbuCon Asia on events.c.c, I think that makes a lot of sense. I've created an UbuCon category specifically. Do you just want an entry pointing to your setup, or would you want to use the full conference management capabilities?
[18:53] <Fallen> ahoneybun: where did you update the link?
[18:54] <ahoneybun[m]> A few weeks ago once arraybolt3 told me about it.
[18:55] <ahoneybun[m]> It looks like the link is completely gone now and not even with my own link.
[18:58] <aaronprisk[m]> ahoneybun: I notified the lead from our IS team who is working on Ubuntu Planet about the NSFW link and he temporarily disabled the link while he is working on the backend. Once they finish the maintenance, the aggregator will display it correctly again.
[18:59] <ahoneybun[m]> Ah no worries, I'd rather it be dead then NSFW!
[19:11] <Fallen> Thanks for the update aaronprisk , glad this is being handled!


[21:27] <brousch> Did apple just open source all of the MacOS and iOS kernels? https://opensource.apple.com/
[22:36] <brousch> Hm, mayeb that's just pieces of it


[04:08] <infinity> pitti: And still more disappearing tests...
[04:08] <infinity> pitti: apport (triggered by binutils) went from RUNNING to no longer on the list.
[04:09] <infinity> pitti: And I see no evidence that it ever passed.
[05:25] <Logan_> is it necessary to keep a delta if the only change is libpng12-dev to libpng-dev? it doesn't look like there will be a transition any time soon...
[05:37] <infinity> Logan_: The only provide of libpng-dev is libpng12-dev currently.
[05:37] <Logan_> right
[05:37] <infinity> s/provide/provider/
[05:37] <infinity> Logan_: That didn't used to be true, hence some of the deltas.
[05:38] <Logan_> ah, okay
[05:38] <infinity> Logan_: So, yeah, if that's all the delta we have, go ahead and drop it.
[05:38] <Logan_> sweet, will do
[06:01] <infinity> First autosync in progress.  Should take about an hour to sync, and possibly a day or three for the buildds to forgive me.
[09:19] <work_alkisg> ibus wasn't running by default up until 12.04, is there any reason why it's running now, even for locales that don't need it?
[09:19] <work_alkisg> It's causing severe typing issues (e.g. https://bugs.freedesktop.org/show_bug.cgi?id=42244) and it's eating up RAM without any benefit at all.
[09:19] <alkisg> (it's not about multimedia keys, we can't even change the keyboard layout now)
[13:37] <prepangolin> Hi guys
[13:37] <prepangolin> How to compile compiz?
[16:18] <dupingping_> hello developers.
[16:45] <ScottK> stgraber: I'd like it so edubuntu-server-host used the native ipaddress module instead of ipaddr from python3-ipaddr.  I'm happy to do the changes if you'll be able to test them.  Do you have a requirement to backport prior to saucy?  I'm trying to delete the binary in Debian, so it'll go soon in uptopic.
[17:25] <Unit193> pitti: src:systemd, "- debian/rules: Don't install init.d scripts, only the upstart jobs." you use the no-op '--upstart-only' switch for dh_installinit.  At least one less change needed.
[17:34] <stgraber> ScottK: nope, we require a pretty recent LXC anyway, so we don't care about pre-saucy
[17:37] <pitti> Unit193: oh, how is it a no-op?
[17:38] <Unit193> Changelog of debhelper has '- dh_installinit: Add no-op --upstart-only option for compatibility.' and manpage has the same info.
[17:38] <Unit193> "Deprecated option, ignored for compatibility."
[17:44] <pitti> Unit193: ah, ok; thanks for pointing out!
[17:47] <Unit193> pitti: Any time!
[17:47] <pitti> Unit193: in fact, we'll get rid of a lot of our delta in the next merge
[17:47] <pitti> http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=shortlog
[17:47] <pitti> we've been busy today :)
[17:47] <Unit193> That'll be nice.
[17:48] <pitti> and I'll create am ubuntu branch on top of the debian git, so that we finally have an official Vcs
[17:48] <pitti> we went through our delta today, and we pushed the useful bits to Debian, and can drop a lot of other bits
[19:02] <ScottK> stgraber: Thanks.
[19:03] <infinity> 164 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[19:03] <infinity> Looks like the autosync is working. :P
[19:06] <pitti> hehe
[19:23] <Logan_> infinity: lol, I have 260 to upgrade
[19:24] <xnox> Unit193: "--upstart-only" still installs init.d script & the upstart job.
[19:24] <infinity> Logan_: I did some last night too. ;)
[19:24] <Logan_> ah :P
[19:25]  * infinity starts slogging through the NEW queue.
[19:25] <Unit193> xnox: Right.
[19:25] <xnox> Unit193: that option has meant to not install init.d script symlink to an "upstart-job" executable, however that has been obsoleted.
[19:26] <infinity> xnox: Yeah, he knows, he was pointing out to pitti that he could drop the option, since it was a no-op.
[19:26] <Unit193> Yes, that's how I read it.
[19:26] <xnox> infinity: ah, ok. correct.
[19:26] <Mirv> I need to kill 100% CPU eating dnsmasq once after reboot now, hmm (on utopic)
[19:58] <otto> I need help submitting mariadb-5.5 5.5.37 to trusty universe.
[19:59] <otto> I've read the ubuntu wiki pages ForDebianDevelopers and found out about sponsorship requests and sync requests. I however didn't quite figure out what situation applies to me now.
[20:00] <Unit193> otto: I'd think you're looking for a SRU, considering it fixes CVEs.
[20:00] <otto> It is a security update, fixes http://www.ubuntu.com/usn/usn-2170-1/, should I ask security team to pull in mariadb-5.5 5.5.37 from Debian sid?
[20:01] <xnox> otto: security sponsorship is slightly different, there is security documentation on the wiki as well.
[20:01] <otto> yes, I've read https://wiki.ubuntu.com/SecurityTeam/ForDebianDevelopers too, but I still don't quite get what applies to me now
[20:02] <xnox> otto: 5.5.37-1 is already in trusty (well in proposed (~= unstable), not release pocket (~= testing))
[20:02] <otto> this seems to apply (from the wiki): "In stable releases of Ubuntu where the Ubuntu package has the same version as in Debian, the Ubuntu Security team will perform a sync from Debian (called a 'security fake sync'). These are typically performed weekly by a member of the Ubuntu Security for packages that are not officially supported. "
[20:02] <xnox> otto: 5.5.36-1 is in trusty release in universe.
[20:03] <otto> xnox: no, .37 is only proposed for utopic: https://launchpad.net/ubuntu/+source/mariadb-5.5
[20:03] <xnox> otto: i don't see mariadb in stable, thus you have no DSA issued right?
[20:04] <otto> xnox: status overview https://packages.debian.org/search?keywords=mariadb
[20:04] <infinity>  mariadb-5.5 | 5.5.36-1 | trusty/universe          | source
[20:04] <infinity>  mariadb-5.5 | 5.5.36-1 | utopic/universe          | source
[20:04] <infinity>  mariadb-5.5 | 5.5.37-1 | utopic-proposed/universe | source
[20:05] <infinity> So, yeah.  You can't get 5.5.37-1 into trusty, as we don't copy backwards.
[20:05] <infinity> But you should get with the security team and see about pushing a 5.5.37-0ubuntu1 to trusty.
[20:05] <xnox> otto: yeah, and there is no DSA to fakesync either. So just follow https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation open a bug report against maraiadb-5.5 package in ubuntu, nominate for trusty
[20:06] <xnox> otto: and prepare a suitable diff & changelog entry + subscribe ubuntu-security, they should get back to you about it.
[20:06] <xnox> otto: opening bug report which is "public security" with "ubuntu-security" is a first step to push this update to trusty.
[20:20] <otto> xnox: does this look proper? https://bugs.launchpad.net/ubuntu/+source/mariadb-5.5/+bug/1313187
[20:21] <otto> should I file for a MRE at this point? where does it come in?
[20:21] <xnox> otto: looks good.
[20:21] <xnox> otto: MRE? no, that's unrelated.
[20:21] <xnox> otto: i've made a comment on that bug report for the security team.
[20:22] <infinity> Maria should probably enjoy the same MRE status that MySQL does, but that would also need a commitment from someomne to update and test it.
[20:22] <xnox> In file included from /usr/include/ruby-2.1.0/ruby.h:33:0,
[20:22] <xnox>                  from qmfengine.cpp:845:
[20:22] <xnox> /usr/include/ruby-2.1.0/ruby/ruby.h:24:25: fatal error: ruby/config.h: No such file or directory
[20:22] <xnox>  #include "ruby/config.h"
[20:22]  * xnox ponders if our ruby is good or not.....
[20:23] <infinity> xnox: Is that package passing an explicit -Iruby2.0 maybe?
[20:24] <xnox> infinity: it does pass explicit -I and they are all 2.1 based.
[20:24] <xnox> infinity: maybe not finding config.h, because multiarch.
[20:24] <otto> infinity: I will anyway update the package for Debian, I could easily maintain it for Ubuntu too. I now already build and test all version on both Debian and Ubuntu
[20:25] <infinity> (utopic-amd64)root@cthulhu:/usr/include# find . -name config.h
[20:25] <infinity> ./x86_64-linux-gnu/ruby-2.1.0/ruby/config.h
[20:25] <infinity> ./x86_64-linux-gnu/ruby-2.0.0/ruby/config.h
[20:25] <infinity> xnox: So, this situation isn't new.  2.0 was set up the same way.
[20:25] <psusi> infinity, hey there... I forwarded a query from someone last month about util-linux... I figured you were a little busy with finalizing trusty but now that it's out... how is that coming?
[20:25] <otto> I am just a bit confused on what the proper process it to push new versions into Ubuntu stable releases
[20:25] <xnox> infinity: quite. yeah. I'm porting qpid-cpp from ruby1.8-dev -> ruby-dev. Cause we somehow removed ruby1.8 without fixing all packages that like explicitely build-depend on ruby1.8-dev.
[20:26] <xnox> infinity: i'm just gonna go la-la-la or possibly propose an SRU for qpid-cpp to be build against ruby2.0
[20:26] <otto> The current wiki pages describe scenarios where somebody patches and existing package, but not really how a Debian release is supposed to be synced/backported into Ubuntu
[20:26] <xnox> actually was qpid-cpp released or not...
[20:27] <infinity> otto: It won't be synced.  And it usually shouldn't be the Debian release being backported either, as we don't want unrelated packaging changes.
[20:27] <xnox> otto: we don't sync/backport into stable/released releases.
[20:27] <infinity> otto: Your best bet is to poke mdeslaur and have him walk you through what the security team would like to see for things like this.
[20:30] <otto> infinity: it's not feasible to cherry-pick security fixes, thus I was thinking if I should now draft a MRE request?
[20:31] <psusi> otto, how is it not feasible to cherry-pick a security fix?
[20:32] <otto> upstream releases on the 5.5 branch maintenance micro releases which contain security and other fixes. When I update the Debian package, e.g. 5.5.36 -> 5.5.37 I just import the whole upstream .37 release
[20:33] <infinity> otto: Like I said, I suspect no one will disagree that maria should enjoy the same MRE status as MySQL does.
[20:33] <psusi> should have no problem cherry picking the security fix, but yea, it does sound like a good candidate for MRE
[20:34] <psusi> infinity, did you miss my question there? ;)
[20:34] <otto> I was just wondering is this the right timing to send a MRE request to technical-board?
[20:34] <infinity> otto: So, we'll probably want you to attend the meeting where it's discussed, or be prepared for a lively mailing list discussion, but please do.
[20:35] <otto> ok
[20:35] <infinity> otto: Like I said, I think that if someone (you?) is willing to commit to doing the updates and testing them, we'll all be happy to grant it based on the fact that MySQL already has an MRE, and the codebases are nearly identical.
[20:35] <infinity> psusi: I might have.
[20:36] <infinity> psusi: So, yeah, working on util-linux this coming week is bubbling up to "very important".  LaMont and I have had a few chats about it, and I'll let you know where things go.
[20:36] <psusi> infinity, wondering how you're doing on util-linux... it has been a month now since I forwarded a query about it to you... some other debian devs were starting to say debian-qa maybe needs to step in to get it updated
[20:37] <infinity> People sure are happy to talk about hijacking a package when it doesn't meet their version number fetish, yes.
[20:37] <psusi> ok.. I'm thinking if you can't get to it in the coming week we really will need to fall back to my version
[20:37] <infinity> It's being worked on.
[20:38] <psusi> it's several years out of date and it's been "update in progress" for a few months now ;)
[20:38] <infinity> Yeah, I know.
[20:39] <infinity> It's just demoralising to have people jump down your throat with every NMU, as if it's a reflection on your worth as a human being. :P
[20:39] <infinity> psusi: Anyhow, I want to get it into jessie in a sane state, and into utopic ASAP, so I'll get cracking this week and keep you posted on progress.
[20:40] <psusi> ok, sounds good
[20:41] <infinity> This NEW processing would go faster if I didn't feel the need to fix every FTBFS I notice along the way.
[20:43] <infinity> pitti: Do you not need a transitional package for systemd-services?  Or are you doing a C/P/R forced removal trick and updating deps?
[20:43] <pitti> infinity: the latter
[20:44] <pitti> infinity: if nothing else, libpam-systemd's changed deps will force the transition already
[20:44] <pitti> as it's not a top-level package
[20:44] <pitti> infinity: I tested this a fair number of times and it worked well
[20:44] <infinity> pitti: Oh, there's the C/P/R at the end of the changelog.  I didn't read far enough.
[20:45] <infinity> pitti: I'm assuming you can get that into Debian too, since it's harmless cruft to carry there.
[20:45] <pitti> infinity: yeah, will try tomorrow
[20:45] <pitti> infinity: we just uploaded 204-9 to Debian which has a lot of our changes, and some others are obsolete
[20:46] <pitti> infinity: I'm currently doing another merge (which should cut down our delta by 2/3 or more :) )
[20:46] <infinity> pitti: \o/
[20:47] <infinity> pitti: While you're in there, care to write cgroups support for FreeBSD and port systemd?  Thanks.
[20:47]  * infinity isn't bitter, though.
[20:47] <pitti> infinity: and what shall I do in the afternoon?
[20:48] <infinity> pitti: The HURD port, of course.
[21:21] <xnox> infinity: well, before util-linux is updated i should double check that d-i is compatible with it first.
[21:22] <xnox> infinity: my fetish is however is more towards reviewing apw's initramfs tools merge ;-)
[21:23] <xnox> pitti: what about pulling in 204 stable patch series? is that still planned to happen or should i start the repo to get those included?
[21:23] <pitti> xnox: ah, we can do that
[21:23] <pitti> it's also fairly easy now
[21:23] <xnox> pitti: into debian&ubuntu or just ubuntu?
[21:24] <pitti> xnox: please don't start on a branch right now; I'm in the middle of a rebase-of-doom against 204-9, this time with a proper public ubuntu branch in the debian git
[21:24] <pitti> xnox: probably both (but tomorrow, getting late)
[21:24] <xnox> pitti: cool! will wait after that.
[21:24] <pitti> gbp-pq is awesome
[21:25] <xnox> pitti: also "re: should the shim stay" -> i thought that stgraber was mentioning that cgmanager for 208 logind compat level is getthing there. Thus we'd want to keep shim for now, on linux.
[21:25] <xnox> pitti: cjwatson has convinced me that "git-dpm" is far superior than gbp-pq.
[21:25] <pitti> xnox: yes, I know -- I thought the plan was to teach shim about the systmed d-bus calls to create cgroups
[21:26] <xnox> pitti: cool, i was seeing some agenda items for the debian-systemd sprint that looked a bit inconclusive.
[21:27]  * xnox goes back to untagling transitions
[21:41] <xnox> Laney: stole a trivial merge of muffin from you, to unblock cogl20 transition.
[21:48] <pitti> xnox: yay :) http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=shortlog;h=refs/heads/ubuntu
[21:48] <pitti> (still WIP)
[21:48] <xnox> pitti: =))))) keep going.
[21:49] <xnox> pitti: maybe i should start trying out systemd ;-)
[22:15] <psusi> what was the timeframe on the systemd transition again?  we going for it in unicorn?
[22:25] <xnox> psusi: when it's ready.
[22:26] <psusi> so trying for unicorn, but maybe not?
[22:26] <xnox> psusi: it should be available for testing soon in unicorn. no estimates when it will be the default.
[22:27] <psusi> is it going to be in the initramfs?
[22:27] <pitti> I see no reason why it sohuld be
[22:27] <pitti> it's making stuff unnecessarily slow and complicated
[22:28] <psusi> hrm... maybe we can finally get around to fixing the issues with degraded or stacked mdadm/lvm/crypt
[22:28] <psusi> oops, I misread that
[22:28] <pitti> we still have the workaround for bug 1185394
[22:29] <pitti> but I think I've seen some Debian bugs / LVM improvements which fixes that more properly than having to settle udev in initramfs with LVM
[22:29] <xnox> psusi: stacked/degraded mdadm/lvm/crypt is not solved in systemd yet either on debian. work with debian folks to sort it out. that would be appreciated.
[22:30] <psusi> well that's why I asked if it was planned to go in the initramfs or not
[22:30] <psusi> if so, it should be possible to use it to sort those issues out that the current scripts have
[22:31] <pitti> it would only make things worse
[22:31] <psusi> say... how about plymouth?  is that going to fit into the systemd picture?
[22:31] <pitti> because then you'd have to restart systemd as well, to use the one from the root fs after initramfs is finished
[22:31] <pitti> yes, the integration needs to be re-done
[22:31] <pitti> ATM, if you boot with systemd it doesn't use plymouth at all
[22:31] <psusi> yea... we had planned on making upstart be able to do that for that reason.. I thoguht systemd was already capable of that?
[22:32] <psusi> what is upstream systemd's solution to that problem?  do they just ignore the issue?
[22:32] <pitti> re-exec itself with keeping state? maybe
[22:32] <infinity> dracut supports initrd with and without systemd.  systemd devs recomment it's in your initrd, sane people recommend against, take your pick.
[22:33] <psusi> that problem being multiplexing boot services interacting with the console
[22:33] <infinity> I'd prefer not, personally, but making initramfs-tools support both modes so people don't make me switch to dracut might also be a decent plan.
[22:34] <infinity> And, IIRC, systemd's "reexec" left something to be desired, I remember a longstanding bug about Fedora systems booted with systemd-in-initrd having open files from boot to shutdown and unclean umounts at shutdown every time.
[22:34] <infinity> But maybe they finally fixed that.
[22:35]  * pitti waves good night
[22:35] <psusi> how do they deal with boot service console interaction?
[22:35] <psusi> if they don't use plymouth?
[22:35] <infinity> They use plymouth, AFAIK...
[22:36] <psusi> ohh, cool
[22:36] <psusi> figured they wouldn't be using something that came from ubuntu ;)
[22:37] <infinity> It didn't come from Ubuntu.
[22:37] <psusi> huh?  yea it did... Scott James Remnant wrote it?
[22:37] <psusi> didn't he?
[22:37] <infinity> Really not.
[22:37] <infinity> Plymouth came from Fedora.
[22:37] <infinity> They had it a year or two before us.
[22:37] <psusi> I could have *sworn* SJR wrote it
[22:38] <infinity> Perhaps you're thinking of usplash, written by mjg59 and others, and replaced by plymouth.
[22:40] <xnox> infinity: can you hint boost-defaults and kdepim together?
[22:40] <xnox> infinity: or am i missing something else for the two to migrate?
[22:40] <infinity> xnox: Is the autohinter not doing that itself?
[22:40] <xnox> infinity: nope.
[22:41]  * infinity tries an easy hint, then.
[22:41] <infinity> Odds are they're caught in another transition.
[22:42] <xnox> infinity: last time Laney did "easy kdepim/4:4.11.2-0ubuntu2 boost-defaults/<IP_ADDRESS>ubuntu1" for me
[22:43] <xnox> infinity: http://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/472
[22:43] <infinity> xnox: Yes, I know how to do it. :P
[22:43] <infinity> xnox: (It's already committed)
[22:44] <xnox> infinity: thanks. just a reference that for some reason autohinter doesn't find it.
[22:44] <infinity> xnox: It could be because it's also caught up with openjpeg?
[22:45] <xnox> infinity: and librtmp1 as well..... i'm sorting out rtmp1 at the moment. didn't look at openjpeg yet.
[22:45] <infinity> And rtmpdump...
[22:45] <xnox> infinity: should have migrated boost-defaults & kdepim pre-freeze.
[22:45] <infinity> So, yeah.  You might be jumping the gun on thinking a hint is necessary. :P
[22:46] <infinity> xnox: It'll shake out.  What's the rush?
[22:46] <infinity> xnox: Did you not read my email about relaxing while the buildds catch up? :)
[22:46] <xnox> infinity: people who use utopic, without proposed, will get boost1.54 - not 1.55 by default.
[22:46] <infinity> xnox: So?
[22:47] <xnox> infinity: i don't know how to relax after a dormant week? =)
[22:47] <infinity> xnox: People who upload to utopic will build against 1.55
[22:47] <infinity> xnox: People running utopic will get things as they transition, which is fine.
[23:08] <xnox> infinity: success ;-) final: boost-defaults,kdepim
[23:10] <mdeslaur> xnox: "* No change rebuild against $2."
[23:10] <mdeslaur> xnox: that was cheap :)
[23:10] <xnox> mdeslaur: darn.
[23:11] <xnox> mdeslaur: which uploads?
[23:11] <mdeslaur> gst-plugins-bad1.0 and a few others
[23:11] <infinity> xnox: You don't read your .changes before you upload?
[23:11] <infinity> Or, like, debdiff to make sure your automation isn't crack?
[23:11] <mdeslaur> well, maybe just the gst-* two
[23:12] <mdeslaur> xnox: I suggest bribing at least $5 next time :)
[23:12] <xnox> mdeslaur: =))))
[23:12] <xnox> mdeslaur: yeah just those two. i did fix up the rest.
[23:13] <xnox> infinity: i do read them, but obviously over-skimmed.
[23:13] <xnox> mdeslaur: oh, any opinion on fake-syncing mariadb .37 security release?
[23:13] <xnox> mdeslaur: (similarish to mysql security update)
[23:14] <infinity> Uhh, fakesyncing?  What?
[23:14] <infinity> No.
[23:14] <infinity> There's a proper way to do this, and that's not it.
[23:15] <xnox> infinity: using the term from security-team docs -> called a 'security fake sync'
[23:15] <infinity> xnox: That's not the right thing in this case.
[23:15] <infinity> xnox: Because we don't want to keep pulling in Debian packaging changes through a 5 year LTS.
[23:16] <infinity> xnox: The right way is the same way that MySQL is done, update the tarball and changelog, and not much else.
[23:16] <mdeslaur> yes, what infinity said
[23:16] <xnox> infinity: oh, right. i'm thinking one-time only, not long term. Once mariadb is actually part of stable release in debian, and after that only take if debian security does DSA.
[23:17] <xnox> infinity: mdeslaur: or are you actually proposing to support universe mariadb for 5 years...
[23:17] <infinity> xnox: otto wasn't looking for one-time only.
[23:17] <infinity> xnox: If he wants it updated for today's CVEs, he wasn't the same for the next set. :P
[23:17] <xnox> s/wasn't/wants/
[23:17] <xnox> ack.
[23:18] <infinity> xnox: So, no, *we* (Canonical, and their security team) won't be supporting maria, but if otto wants to, that's how.
[23:18] <xnox> yeah, smells more like MRE indeed then.
[23:18] <mdeslaur> xnox: it needs to get done just like everything else gets done...in this case, he needs to get a couple of updates sponsored by the security team, and then can apply for a MRE
[23:18] <mdeslaur> so he needs to file a bug, propose some updated packages that only touch the tarball, etc.
[23:19] <mdeslaur> if that goes well for a couple of releases, he can get an MRE and then do non-security updates too
[23:35] <xnox> =( gccxml


 But around here, more hard work than fun
[08:47] <seb128> :/
[08:48] <willcooke> didrocks, Trying to log in to a gnome session in an 18.04 vm, but I dont have the little cog to change session, what did I do wrong?
[08:50] <didrocks> willcooke: you only have one session installed, correct, or did you install gnome-session?
[08:50] <didrocks> have*
[08:51] <willcooke> didrocks, I installed gnome-session
[08:51] <willcooke> Want to make a point on a bugzilla bug :)
[08:51] <didrocks> willcooke: rebooted in between, I guess?
[08:51] <seb128> willcooke, did you restart gdm after installing gnome-session?
[08:51] <willcooke> ohhhhhhhh
[08:52] <willcooke> man I suk
[08:52] <seb128> no, gdm sucks :p
[08:52] <didrocks> yeah, gdm doesn't pick up new session files dynamically
[08:52] <seb128> you shouldn't have to restart
[08:52] <seb128> but yeah, there we are...
[08:52] <willcooke> on the plus side, it didnt occur to me to reboot because, on the whole, these things just work
[08:53] <willcooke> silver cloud etc
[08:53] <willcooke> there we go, gnome session
[08:53] <willcooke> and gnome font
[08:53] <willcooke> aaaaand a big failure in my plan, because my VM doesnt have a wifi nic
[08:53] <willcooke> ok, going to log out and try it on this one
[08:56] <didrocks> speaking of which…
[08:56] <didrocks> we'll need to investigate to force gdm on X, while having the Wayland session proposed
[08:56] <didrocks> as when you disable wayland on gdm, it blacklists the wayland user sessions
[08:56] <didrocks> we'll probably need a patch for this
[08:56] <seb128> we could keep gdm on wayland?
[08:57] <seb128> we don't go away from wayland for reasons that impact the greeter
[08:57] <didrocks> are we sure it's that safe/consistent?
[08:57] <didrocks> yeah, that's true enough
[08:57] <didrocks> we could keep it likt his
[08:57] <didrocks> forget about it thus ;)
[08:57] <seb128> not sure no, I did't think about it much
[08:58] <seb128> but you are right, it puts a stack different from our default/most supported one in the boot path
[08:58] <seb128> at the same time I don't think wayland/gdm creates us issues so it wouldn't be crazy to keep it
[08:58] <didrocks> yeah, we'll need to think about it, the best answer is maybe "let's no do anything"
[08:58] <didrocks> we juste need to be cogniscent about this
[08:58] <seb128> right
[08:58] <seb128> do you want to add a trello card for that?
[08:58] <didrocks> not*
[08:59] <didrocks> yeah, just for bookkeeping
[09:00] <didrocks> seb128: https://trello.com/c/zKYtpgyZ/194-take-a-decision-if-we-keep-gdm-running-under-wayland
[09:00] <seb128> didrocks, thanks
[09:03] <Laney> heyyyyyyyyyyy
[09:03] <seb128> good morning Laney, happy fosdem week!
[09:03] <seb128> how are you?
[09:03] <didrocks> good morning Laney!
[09:04] <Laney> hey seb128 didrocks
[09:05] <Laney> happy fosdem week to you too!
[09:05] <xnox> morning =)
[09:05] <Laney> i'm alright thanks, you?
[09:05] <Laney> hey xnox
[09:05] <Laney> wb(?)
[09:05] <Laney> how's it going?
[09:05] <duflu> Hello Laney, xnox, world
[09:07] <xnox> Laney, https://twitter.com/tdlk/status/957902966996029441 =) look what I found in Tokyo about #FOSDEM
[09:08] <Laney> !!!
[09:09] <Laney> it is actually the same delerium
[09:09] <Laney> funny
[09:09] <Laney> hey duflu, you good?
[09:09] <Laney> have a nice .au day?
[09:10] <duflu> Laney, yeah it was OK :)
[09:11] <seb128> Laney, I'm good thanks :)
[09:11] <seb128> a bit tired but that is normal state nowadays
[09:11] <Laney> give it 10 years
[09:12] <didrocks> xnox: nice, in which area?
[09:12] <xnox> didrocks, Ginza I believe, not far from Kabukiza
[09:16] <didrocks> interesting, I wouldn't have said Ginza would be the place where you find this kind of pub :)
[09:23] <xnox> didrocks, for me it was the first time in Japan, so everything was confusing and exciting =)
[09:26] <didrocks> heh ;)
[09:32] <willcooke> right, really am logging in to the other session now, brb
[10:07] <andyrock> good morning
[10:07] <willcooke> hi andyrock
[10:13] <didrocks> ok, my best bet now at gdm not starting is due to:
[10:14] <didrocks> auth could not identify password for [gdm]
[10:14] <didrocks> I do have though: /etc/pam.d/gdm-autologin
[10:14] <didrocks> with authoptionalpam_gdm.so
[10:14] <didrocks> and:
[10:15] <didrocks> $ ls -l /lib/x86_64-linux-gnu/security/pam_gdm.so
[10:15] <didrocks> -rw-r--r-- 1 root root 6120 oct.  11 18:57 /lib/x86_64-linux-gnu/security/pam_gdm.so
[10:16] <seb128> did anything got upgraded in that stack?
[10:17] <didrocks> didn't find anything pam-related: http://paste.ubuntu.com/26482861/
[10:21] <didrocks> so, I did in addition to this dist-upgrade purge a lot of packages on Friday: http://paste.ubuntu.com/26482869/
[10:21] <didrocks> I see on this long-lived install that it did purge a gdm package
[10:21] <didrocks> maybe there was a conffile in common between gdm3 and gdm and it did purge that one?
[10:24]  * didrocks tries to purge and reinstall gdm3
[10:24] <didrocks> bbiab
[10:25] <GunnarHj> Good morning, Laney! After having talked with Debian, we came up with this as regards the libpinyin upload stuck in -proposed:
[10:25] <GunnarHj> https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1735362/comments/22
[10:25] <GunnarHj> Can you please help to get it in?
[10:26] <didrocks> ok, it works
[10:26] <didrocks> so, my theory is that purging very old packages, like gdm, had a conffiles in common with gdm3, and so removed it
[10:27] <didrocks> nothing impact real artful users, hopefully ;)
[10:33] <Laney> hi GunnarHj
[10:33] <Laney> ok, we can probably skip those tests
[10:34] <GunnarHj> Laney: Great!
[10:35] <GunnarHj> Laney: Of course, it means that libzhuyin needs to be removed fast, because once libpinyin is in, I suppose it's no longer possible to rebuild libzhuyin.
[10:36] <Laney> done
[10:36] <GunnarHj> Laney: Thanks! :)
[10:36] <Laney> If someone tries to upload libzhuyin source they'll get some kind of error or other
[10:36] <Laney> so yeah, do follow up on it being removed
[10:36] <GunnarHj> Will do.
[10:39] <Laney> brb
[11:07] <oSoMoN> can someone with powerz re-run the failed autopkgtest for glm? http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#glm
[11:13] <didrocks> oSoMoN: done
[11:15] <oSoMoN> thanks didrocks !
[11:15] <didrocks> yw ;)
[11:36] <GunnarHj> sil2100: Hi Łukasz, you should set "Language pack base" at this page:
[11:36] <GunnarHj> https://translations.launchpad.net/ubuntu/bionic/+language-packs
[11:36] <GunnarHj> so LP starts exporting delta tarballs.
[11:43] <sil2100> GunnarHj: oh, I didn't know I can do it, I poked Colin and William on Friday but maybe they missed the ping
[11:44] <sil2100> GunnarHj: is it ok now?
[11:44] <sil2100> (yeah, looks like I had the power to do that in the end)
[11:45] <GunnarHj> sil2100: Yes, looks good to me.
[11:47] <jbicha> didrocks: Debian Stretch and Ubuntu GNOME for a few releases had gdm use Wayland by default where available but the default session was stil the GNOME on Xorg
[11:48] <jbicha> good morning
[11:49] <didrocks> ack
[11:51] <GunnarHj> sil2100: That page is where you later (soon before the release) can check "Request a full language pack export". No need to ping anyone about that either. (I.e. as long as it works - that's not always the case.)
[11:51] <sil2100> bbl!
[11:51]  * sil2100 drives home
[11:52] <didrocks> see you sil2100 :)
[12:00] <didrocks> Trevinho: hey! do you mind setting milestone if you can on my G-S MR?
[12:01] <didrocks> and label feature as well?
[12:12] <GunnarHj> Hi didrocks! Can you please help with bug #1745777? It's a bit more urgent than usually is the case with package cleaning, since one of the build dependencies for libzhuyin is no longer present in bionic.
[12:17] <didrocks> GunnarHj: hey, I'm unsure to understand the "there is a need to remove them in bionic before they have been removed from sid"?
[12:17] <didrocks> if I remove them manually, next sync from debian may bring them back
[12:17] <didrocks> (as long as they are not removed from sid)
[12:17] <GunnarHj> didrocks: We have synced from experimental.
[12:18] <GunnarHj> didrocks: Isn't is possible to block them from reappearing?
[12:18] <didrocks> GunnarHj: it's name blacklisting, but what does this give? Can't we just wait for them to be removed from sid and then autosync will remove them?
[12:19] <GunnarHj> didrocks: It depends on how fast things move forward on the Debian side. Once the whole archive is rebuilt, libzhuyin will fail.
[12:20] <didrocks> GunnarHj: and I think that's fine, if we see that it's still here near release, we can remove it
[12:20] <didrocks> I just don't think there is a need and remove them before Debian does
[12:20] <jbicha> autosync is separate from autoremove. I have a whole list of packages removed from Debian unstable I'm waiting to see removed from bionic
[12:21] <GunnarHj> didrocks: Ok, I have no problem with that. You know the implications better than me.
[12:21] <didrocks> jbicha: yeah, autoremove is run manually from time to time AFAIK
[12:21] <didrocks> GunnarHj: let's plan on that. However, please reping me if we are near release and it's still in the repo
[12:22] <Laney> It's because the binaries have been taken over by libpinyin now
[12:22] <Laney> in bionic
[12:22] <jbicha> didrocks: since we're talking AA stuff, could you review gnome-tweaks (renamed from -tweak-tool) in bionic NEW
[12:22] <didrocks> jbicha: too much time devoted to AA this week… but adding it to my list :p
[12:22] <GunnarHj> didrocks: I'll try to remember that...
[12:22] <jbicha> I expect one more rename: gnome-themes-standard → gnome-themes-extra whenever upstream releases a tarball
[12:23] <jbicha> didrocks: that's fine. It's not urgent and maybe someone else will get to it first :)
[12:23] <didrocks> jbicha: we'll see who gets to it first :)
[12:23] <jbicha> (although waiting for someone else to do it doesn't work out as often as one would hope … )
[12:30] <jbicha> I'm doing this now since it makes sense: LP: #1726395
[12:31] <didrocks> sure
[12:31] <Trevinho> didrocks: ok, I'm out this week (and in France, close to you), but I can do it after the slopes :-)
[12:31] <GunnarHj> Hi doko, can you please revisit bug #1738582. It ought to be ready to approve by now, and with that let us proceed with adding the packages to the live seed.
[12:31] <didrocks> Trevinho: oh sure! Profites bien :)
[12:31] <Trevinho> Oui!
[12:32] <Trevinho> C'est fabtafique
[12:32] <Trevinho> Fantastique
[12:32] <Trevinho> (manger a part :-D)
[12:32] <didrocks> pffff ;)
[12:33] <jbicha> btw, the patch for #737362 was applied upstream briefly and then reverted. Design issues and worries about users breaking their systems by turning it off
[12:33] <jbicha> GNOME #737362
[12:46] <seb128> typical GNOME argument :/
[12:53] <jbicha> speaking of GNOME … https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=77ff1d9
[12:54] <jbicha> ggsettings set org.gnome.desktop.peripherals.touchpad 'fingers'
[12:59] <jbicha> oh Tweaks already has a setting for it in Keyboard & Mouse > Touchpad > Click Method
[14:09] <seb128> jbicha, I'm not sure to understand the impact of that touchpad change
[14:10] <seb128> jbicha, if that doesn't impact edge scrolling then seems fine to me
[14:11] <jbicha> I am working on redesigning that option in Tweaks to make it a bit more clear, the first screenshot is the current UI, the next 2 are my proposal
[14:11] <jbicha> https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/117
[14:11] <jbicha> the click-method options aren't supposed to affect scrolling AIUI
[14:20] <didrocks> I did test it on Bastien's request FTWI before he enabled by default. No difference on my one-touch touchpad
[14:21] <seb128> didrocks, do you understand what the difference is supposed to be?
[14:23] <didrocks> seb128: from what he told, it's mostly a MacOs feature for multi-touch touchpads, it's a no-op in other cases
[14:23] <didrocks> he referenced https://bugzilla.gnome.org/show_bug.cgi?id=757255 at the time
[14:24] <seb128> didrocks, right, I read that, I still not understand what it changes really
[14:24] <seb128> I guess it doesn't matter much
[14:24] <seb128> we will see if we get users having issues
[14:24] <didrocks> seb128: I think it's something Mac users understand apparently ;)
[14:25] <didrocks> I think it's the "right click on multiple fingers"
[14:25] <seb128> k
[14:25] <didrocks> but I might be wrong
[14:25] <didrocks> seb128: https://support.apple.com/en-us/HT207700
[14:26] <jbicha> it's going to surprise people with newer laptops that don't have separate touchpad "mouse" buttons
[14:26] <didrocks> first case
[14:27] <kenvandine> jbicha, thx for the gedit ack :)
[14:29] <jbicha> kenvandine: I'm doing a gedit tarball release soon because someone needs to and there were fixes piling up in git master
[14:29] <jbicha> I don't intend to be the gedit maintainer though, so we'll see how that works :|
[14:29] <kenvandine> jbicha, great
[14:29] <kenvandine> jbicha, you touch it... you own it :)
[14:29] <jbicha> I hope not!
[14:30] <kenvandine> i'd kind of like to do some work on gedit actually
[14:30] <kenvandine> but i seem to have no free time :/
[14:32] <seb128> jbicha, when you say it's controversial, was there more discussions on the topic or just some maintainers pushing back because they consider flatpak the GNOME supported solution?
[14:32] <seb128> hey kenvandine, how are you?
[14:34] <jbicha> seb128: for instance mcatanzaro thinks GNOME already has one classic build system (meson ideally) and one new build system (flatpak)
[14:34] <jbicha> so he isn't interested in adding snap metadata for packages he maintains
[14:34] <seb128> jbicha, right, so the later one
[14:34] <jbicha> yes
[14:34] <seb128> k, I was checking if there were more discussions I didn't notice
[14:34] <seb128> that I knew about
[14:34] <seb128> thx
[14:34] <jbicha> Ken has been the one proposing these patches so he can give you more details if needed :)
[14:34] <kenvandine> hey seb128
[14:36] <kenvandine> seb128, mcatanzaro suggested i email the desktop-devel list to get a discussion going on snap support
[14:36] <seb128> kenvandine, I would refrain from doing that
[14:36] <jbicha> I think mcatanzaro might have proposed having a project-wide position against adding the snap metadata but mcatanzaro didn't really follow up on that
[14:36] <kenvandine> seb128, however, i've avoided that for now... since i pretty much know how it'll go
[14:36] <seb128> I can't see any useful outcome
[14:36] <kenvandine> right
[14:36] <kenvandine> so i'm ignoring the patches i've sent him and hoping to get the rest in ;)
[14:37] <kenvandine> maybe eventually i can say to him "your projects are the only ones without snap packaging"
[14:37] <jbicha> I think it would help if we clone jamesh so that Builder would natively support building Snaps ;)
[14:38] <kenvandine> jbicha, he has a branch that works :)
[14:38] <kenvandine> but needs refactoring to get it upstream
[14:38] <seb128> jbicha, I think he would argue against accepting the snap support in builder :p
[14:38] <jbicha> csoriano for instance has said that he likes the flatpak option as an easy way for contributors to build and test nautilus from git master
[14:40] <jbicha> upstream Builder (hergertme) seems receptive to patches to support all sorts of build systems
[14:40] <kenvandine> yeah, he didn't reject it
[14:41] <seb128> right, I'm just saying that the guy who doesn't want the snapcraft.yaml files added upstream and would want to the project to nack them would probably also argue that snap has no point being into builder
[16:23] <GunnarHj> didrocks: Do you have time to help out with bug #1738582?
[16:27] <didrocks> GunnarHj: not today
[16:27] <didrocks> could before EOW
[16:27]  * didrocks has a lot of MIR to deal with recently…
[16:28] <didrocks> GunnarHj: it seems doko started the review
[16:28] <didrocks> GunnarHj: maybe ask him? Don't want to step over
[16:28] <GunnarHj> didrocks: Yes. I pinged doko too, but he seems not to be around. (What's EOW?)
[16:28] <didrocks> GunnarHj: end of week
[16:29] <GunnarHj> didrocks: Thanks. :)
[16:29] <didrocks> GunnarHj: well, try again later and keep me posted :)
[16:30] <GunnarHj> didrocks: Will do.
[16:58] <oSoMoN> chrisccoulson, chromium-browser 64.0.3282.119 is ready for publication in https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+packages (already in bionic-proposed)
[17:58] <willcooke> night all, going to go to the office tomorrow morning
[17:59] <GunnarHj> jbicha: Thanks for pushing that gnome-user-docs patch. Do you think I should apply for commit rights? If I understand it correctly, such rights apply to the whole git.gnome.org, not only specific packages.
[18:00] <jbicha> GunnarHj: have you contributed to other modules besides gnome-user-docs?
[18:00] <GunnarHj> jbicha: Yes, but just a few small things.
[18:01] <jbicha> I don't know what the threshold for commit number is
[18:02] <jbicha> I think they want you to have someone vouch for you so maybe ask in #docs on irc.gnome.org what you need to do to apply for git commit rights
[18:03] <GunnarHj> jbicha: Maybe. Or, considering that they are planning to move the thing to another place, maybe I'd better wait til then.
[18:03] <jbicha> https://wiki.gnome.org/AccountsTeam/NewAccounts
[18:04] <jbicha> I believe the account is the same. commit rights gets you commit access at git.gnome.org and gitlab.gnome.org
[18:04] <GunnarHj> jbicha: Right, I have seen that page.
[18:11] <jbicha> I don't work on docs these days, I just happened to see your patch when I filed a wishlist bug there
[18:12] <GunnarHj> jbicha: Yeah, I know. So I was lucky. :)
[18:15] <jbicha> it'll probably be a little different with gitlab, but with bugzilla, a lot of maintainers mark patches as accepted_commit_now which means "go ahead and push"
[18:16] <jbicha> GNOME gives project-wide commits rights fairly easily so if you can't push, it's good to mention that on the bug
[18:18] <GunnarHj> jbicha: Yes, if I understand it correctly, gitlab will allow for merge proposals like in bazaar. But yes, mentioning the absence of push right on the bugs is probably a good idea.
[21:17] <willcooke> night all
[21:17] <willcooke> again
[21:57] <jamesh> kenvandine: with a bit of hacking, I got one of your GNOME snaps to display translated
[21:58] <jamesh> it wasn't particularly pretty
[21:58] <kenvandine> woot
[21:58] <kenvandine> jamesh, so what's the issue?
[21:58] <jamesh> kenvandine: the core snap only provides compiled locale data for C.utf-8
[21:59] <jamesh> so setlocale(LC_ALL, "") fails.  Then gettext uses the libc locale to pick which translations to use
[21:59] <jamesh> which still thinks it is the C locale
[22:00] <jamesh> I got things to work by compiling a locale for French, putting it somewhere the snap could read, and setting LOCPATH
[22:01] <kenvandine> that's ugly
[22:01] <jamesh> we could try staging locales-all somewhere (app or gnome platform snap), and make sure they're found that way
[22:02] <jamesh> however, locales-all is 3.4 MB compressed, 130 MB uncompressed
[22:04] <oSoMoN> kenvandine, can the LO i386 autopkgtest failure be ignored to allow it to migrate? http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#libreoffice
[22:05] <oSoMoN> we've done that for the last few uploads
[22:05] <oSoMoN> the autopkgtests are failing on i386 because of that infamous java crash
[22:06] <oSoMoN> https://bugs.documentfoundation.org/show_bug.cgi?id=108619
[22:11] <kenvandine> oSoMoN, we should
[22:11] <kenvandine> we need to poke someone about that
[22:13] <oSoMoN> kenvandine, who do we need to poke?
[22:14] <kenvandine> jbicha, do you know?
[22:15] <Laney> #ubuntu-release
[22:15] <Laney> I'd do it but I'm not really here
[22:15] <Laney> also I'd ask what the status of the fix is :-)
[22:17] <oSoMoN> ok, I'll do that tomorrow as it's getting late and I have to get some rest
[22:18] <oSoMoN> have a good night all
[22:19] <kenvandine> Laney, you aren't here!


[02:24] <MangHuoEr> 大家早啊
[02:31] <iMadper``> MangHuoEr: 早.
[13:59] <gQuigs> Was wondering if there is any feedback between ibus-sunpinyin vs ibus-libpinyin for Ubuntu/Gnome to default too?   re:https://lists.ubuntu.com/archives/ubuntu-desktop/2017-October/005269.html
[13:59] <ubrl> ⇪ f:  Remove Python2 for 18.04?
[14:00] <gQuigs> which do people actually use and prefer?


[14:21] <teward> repost from yesterday since nobody helped yesterday - can someone force-approve the Xenial nomination for LP bug #1716968 ?  It only affects Xenial so far, but doesn't affect the development release. https://launchpad.net/bugs/1716968
[22:46] <hggdh> teward: approved