[00:45] <amichair> JontheEchidna: another Reese's piece at lp:~amichai2/software-properties/fixes
[00:46] <JontheEchidna> I don't have commit rights to that repo :(
[00:46] <JontheEchidna> apachelogger: bleh, I suppose. I'll file a bug tomorrow
[00:49] <amichair> JontheEchidna: before we trouble apachelogger or Riddell to merge it, is there anything else needing peanut butter goodness in software-props-kde?
[00:49]  * apachelogger falls off chair due to highlight overload
[00:50] <apachelogger> I cannot merge
[00:50] <apachelogger> some ebay buyer bought my gpg, ssh keys and launchpad login :P
[00:50]  * amichair passes a Reese's piece to apachelogger to help stabalize his blood sugar levels
[00:50]  * apachelogger cant do no work anymore
[00:50] <vorian> cool, for how much apachelogger?
[00:50] <apachelogger> 2k
[00:50] <vorian> sweetness
[00:50] <apachelogger> never sold so little data for so much money ^^
[00:51] <JontheEchidna> ouch, sucks
[00:55] <konqi_aki> someone highlight my name please
[00:55] <nixternal> konqi_aki: hello
[00:57] <vorian> wow, he must be scared of nixternal
[00:57] <amichair> JontheEchidna: i don't see any other spk bugs to work on at the moment... is there anything I should do with this branch? or will someone pick it up via the lp magic links?
[00:58] <JontheEchidna> amichair: I can't think of anything, should be good to ping Riddell
[00:58] <Riddell> I'm about to sleep
[00:58] <Riddell> e-mail me and I can do it in the morning
[00:59] <Riddell> how about 23:00UTC tomorrow for meeting?
[00:59]  * apachelogger is good with everything
[01:00]  * apachelogger is also kinda drunk
[01:00] <amichair> I'm off to bed too...
[01:00] <apachelogger> JontheEchidna: I did not know nixternal was thtat scary :(
[01:00] <amichair> JontheEchidna: thanks again for helping me help u :-)
[01:00] <jjesse> nixternal is very scary
[01:00] <JontheEchidna> apachelogger: lol, you should see his picture on nixternal.com
[01:00] <jjesse> especially if you meet him in person
[01:01] <JontheEchidna> amichair: you're welcome. Thanks for the bugfixes
[01:01] <apachelogger> well
[01:01] <apachelogger> I shall never ever go to UDS!
[01:01] <vorian> heh, I saw nixternals brother on "the marraige ref"
[01:01]  * apachelogger doesnt wanna be scared of nixternal
[01:02] <jjesse> apachelogger: don't wory i don't think nixternal is allowed outside of the US
[01:02] <vorian> the dude looked just like nixternal with a mustache
[01:02] <apachelogger> oh, fortunately :D
[01:02]  * apachelogger still cant attend UDS :(
[01:02] <amichair> JontheEchidna: my pleasure :-)
[01:02] <apachelogger> got midterm exams that very week unfortunately
[01:02] <apachelogger> but some UDS I will attend
[01:02] <apachelogger> I promise :/
[01:03] <JontheEchidna> :(
[01:03] <JontheEchidna> I'll go if I can get sponsored. School gets out a week before UDS
[01:04] <vorian> I don't think i'll be getting a sponsorship this time :P
[01:04] <vorian> or ever again
[01:05]  * apachelogger cant got to akademy either since that is exaclty when major exams are -.-
[01:05] <JontheEchidna> anyways, bbl
[01:05] <apachelogger> vorian: you could join me in switiching to chakra or whatever it is called, then we both dont get sponsorship :)
[01:06] <vorian> whoooo hooo!
[01:06] <vorian> sounds like a plan
[01:06] <apachelogger> oh and we could get drunk at the same time and come up with some more sensible name
[01:06] <vorian> ha
[01:09] <vorian> ohhh, arch :x
[01:09]  * vorian had to google that one
[01:12] <vorian> see, that's why people are scared of nixternal 8-)
[01:13] <nixternal> huh?
[01:14] <konqi_aki> arch ftw!
[01:14] <vorian> topic change
[01:14] <nixternal> konqi_aki: you tell um!
[01:14] <nixternal> can't figure out that damn channel monitor at all
[01:15] <nixternal> and don't ban konqi_aki. that is me using Aki IRC client
[01:15] <vorian> what was that
[01:15] <vorian> ah
[01:15] <nixternal> I am writing documentation for Aki
[01:15] <nixternal> trying to figure out this channel buffer, but I can't
[01:15] <nixternal> guess I am to stupid to figure out simplicity
[01:15] <vorian> that's what started the whole "scared of nixternal" stuff
[01:19] <vorian> is there a reason you have to use '/quote stats p' in quassel?
[01:30]  * apachelogger is tres funny
[02:03] <jjesse> aki?
[02:04] <apachelogger> kubotu: google aki irc
[02:04] <kubotu> Results for aki irc: 1. Aki: http://www.akiirc.org/ | 2. AkiIRC Python Bindings | Aki: http://akiirc.org/node/3 | 3. Aki IRC Client | Get Aki IRC Client at SourceForge.net: http://sourceforge.net/projects/aki/
[02:12] <nixternal> fork me, git is a pain in the ass
[02:18] <nixternal> DarkwingDuck: lucky you, the meeting is tomorrow at 18:00 for us
[02:18] <jjesse> kubuntu meeting>
[02:18] <jjesse> ?
[02:43] <nixternal> jjesse: yes
[02:43]  * nixternal goes for pie and tv
[03:13] <jjesse> mmm i like pie
[03:15]  * apachelogger falls off chair again
[03:16] <apachelogger> oh my emperor!
[03:16] <apachelogger> 4:16 am
[03:16] <apachelogger> I  am a truely mad robotor
[03:17] <apachelogger> that reminds me on the song sad robot
[03:18] <apachelogger> http://www.youtube.com/watch?v=WBYkB_Rz7XM
[03:48] <DarkwingDuck> nixternal: I saw that. thank god it's not wed
[04:07] <DarkwingDuck> hmmm, strange
[04:08] <DarkwingDuck> Just because I want to know the details I'm going to see what apport says about this kernal crash
[04:09] <DarkwingDuck> why does this sound like a virus more then a crash?
[04:15] <DarkwingDuck> hmm, Okay, gonna reboot and see if my kernal records a crash
[04:21] <DarkwingDuck> woah... This is getting fun
[04:21] <DarkwingDuck> Okay, this just got really interesting
[04:31] <DarkwingDuck> Any kernal guys in here?
[04:42] <JontheEchidna> You'd probably have more luck for kernel dudes in #ubuntu-devel
[04:44] <DarkwingDuck> Nope. Not bothering patching it myself. Bug report off to kernal.org
[04:46] <DarkwingDuck> alright I'm crashing
[05:09] <JontheEchidna> apachelogger: zomg, an apt-pkg header that has documentation!!1!1
[05:09] <JontheEchidna> run for the hills!

[05:10] <JontheEchidna> ^and dantii ran :P
[05:11] <JontheEchidna> (he implemented the aptcc PackageKit backend with apt-pkg, he's probably scared too)
[05:12] <JontheEchidna> sleepy times now
[05:19] <nixternal> ok, I have my metal jamming, now I need work to do
[05:20] <nixternal> only 23:19
[07:07] <Sput> apachelogger: just use your compose key with <3 and you get a nice ♥
[08:44] <agateau> Riddell: ping
[09:41] <amichair> Riddell: could you please merge the bugfix in the latest revision at lp:~amichai2/software-properties/fixes ?
[10:03] <bodksi> hi all, I have a feature request for PyQt4... (that the API file that is generated during the build be included in the package) now that PyDev (Python plugin for Eclipse) has introduced support for it. Anyone know the best place to make this feature request?
[10:04] <bodksi> (or that it is somehow available without downloading sources and building PyQt4 from scratch :) )
[10:10] <freinhard> bodksi: i'd suggest to file a bug on launchpad against pyqt4
[10:11] <bodksi> OK thanks, I thought it might serve to annoy if i filed it as a bug... but if thats the best way to request features then I'll do that :)
[10:24] <Mamarok> hm, any idea why I have no sound in youTube on lucid? all flash and codecs installed, this came up in the last few days
[10:24] <Tm_T> Mamarok: pa?
[10:25] <Mamarok> Tm_T: well, I don't use it, default is the sound card
[10:25] <Mamarok> and it worked before
[10:26] <Tm_T> Mamarok: doublecheck you don't have it running
[10:26] <jussi01> PA is evil and sneaky like that
[10:28] <Mamarok> why oh why can't we just get rid of that crap?
[10:30] <jussi01> Mamarok: was it the issue?
[10:31] <jussi01> Motorola droid
[10:31] <jussi01> crap
[10:31] <jussi01> wrong window :)
[10:31] <Mamarok> jussi01: I have no sound in browsers anymore, regardless if it is Konqueror, Firefox or Chromium
[10:31] <Riddell> agateau: you pinged?
[10:31] <agateau> Riddell: I did
[10:32] <Mamarok> why isn't there a nice button allowing to just kill PA when needed?
[10:32] <agateau> Riddell: just wanted to know what was the status with the latest patches I sent your way
[10:35] <Riddell> agateau: I have "agateau amarok, ksni, kdebase-workspace dbusmenu patches" written at the top of my todo today
[10:35] <agateau> Riddell: sounds good :)
[10:35] <Riddell> along with a note to coordinate it with ted
[10:35] <agateau> Riddell: perfect then
[10:35] <agateau> Riddell: thanks
[11:30] <ulysses> hy
[11:43] <larsivi> eh, Apport KDE crashed on me, segfault in Python - Apport refused to let me report it because there was no stacktrace
[12:16] <Trouble_> Hey guys, is 4.4.2 in ninjas ready for testing on Karmic?
[12:19] <Riddell> Trouble_: yes please
[12:20] <Trouble_> Riddell: Cool, I'll install it now, but gotta pop out, but I'll have a play and update the wiki later
[12:21] <Trouble_> or at least update the wiki if it installs correctly  :)
[13:16] <larsivi> which process is responsible for the plasma runner widget?
[13:16] <Riddell> krunner
[13:17] <freinhard> there is no more sun jre in lucid?
[13:17] <larsivi> it seems to stop working after the first use (or alternatively a little while)
[13:19] <freinhard> krunner's calculator got really slow lately...
[13:20] <larsivi> nothing I do seems to bring up the krunner at all
[13:22] <larsivi> maybe it is related to virtuoso-t crashing? although I don't know if it crashed this time since apport crashed ...
[13:28] <nigelb> what are the qt development packages?
[13:28] <nigelb> I started to fix what sounded like a small bug
[13:28] <nigelb> now, I end up having to get deep into it :(
[13:29] <Riddell> how do you mean development packages?
[13:29] <nigelb> upstream asked if I had them
[13:29] <nigelb> I hit this error during compilation http://pastebin.com/UUdDbnLU
[13:30] <Riddell> libqt4-dev is it
[13:30] <nigelb> um, lemme try with that one
[13:30] <nigelb> I'm so lost in kde
[13:38] <apachelogger> Sput: yeah but using KDE emoticons would be way more consitent in a KDE env
[13:39] <apachelogger> also it looks way better with colors ^^
[13:39] <apachelogger> good morning everyone :)
[13:39] <apachelogger> btw ;)
[13:40] <Riddell> happy Monday apachelogger
[13:41] <shadeslayer> Mamarok: ping
[13:41] <apachelogger> Riddell: thanks, to you too :)
[13:43] <shadeslayer> nigelb: btw you can install kde-devel,its a meta package for dev libs which help in compiling most kde apps
[13:43] <nigelb> shadeslayer, I'm just fixing a *particular* bug
[13:43] <maco> i didnt knw about that
[13:43] <shadeslayer> maco: :D
[13:44] <shadeslayer> nigelb: um.. ok :)
[13:45]  * nigelb wonders how I got dragged into kde anyway
[13:45] <maco> o/
[13:46]  * maco thinks that's her fault
[13:46] <nigelb> nah, someone came in on bugs channel asking how to link kde bug tracker
[13:46] <nigelb> and now here I am :D
[13:46] <shadeslayer> nigelb: hehe.. theres a super natural force that attracts all users to KDE :)
[13:47] <nigelb> shadeslayer, that was a supernatural force attracting to all things easy.  I was bored :D
[13:47] <nigelb> the only bug assigned to be is ftbs, and I was tired of hunting around
[13:47] <nigelb> s/be/me
[13:48] <shadeslayer> nigelb: which one?
[13:48] <nigelb> maco, though you advertising it at every momment may have something to do with it :D
[13:48] <shadeslayer> i have some spare time....
[13:48] <nigelb> shadeslayer, vlc
[13:48] <Riddell> "digiKam 1.2.0 released" where's lure when you need him?
[13:48] <shadeslayer> nigelb: :)
[13:49] <shadeslayer> nigelb: so whats the exact error? and please link the bug report as well :)
[13:49] <nigelb> shadeslayer, the last time, I didn't have enough space
[13:49] <nigelb> I just fixed *that* part
[13:50] <shadeslayer> ah..
[13:51]  * apachelogger runs doxygen
[14:35] <Mamarok> shadeslayer: pong
[14:35] <Mamarok> sorry,m was afk
[14:35] <Mamarok> I*
[14:36] <Mamarok> shadeslayer: could you remind me your PPA, please?
[14:38] <shadeslayer> Mamarok: lp.net/~rohangarg
[14:38] <shadeslayer> Mamarok: its in the playground.. ill move it to kde extra as well so you can use that too
[14:38] <Mamarok> thanks
[14:39] <Mamarok> shadeslayer: just FYI, lp.net doesn't resolve to launchpad.net...
[14:39] <shadeslayer> i was attending a TEDx confrence so i couldnt be here around the last few days :)
[14:39] <shadeslayer> Mamarok: i know :)
[14:39] <shadeslayer> Mamarok: i thought that youll just replace it yourself :P
[14:39] <Mamarok> shadeslayer: lazy you :)
[14:39] <Mamarok> you were at a TEDx conference physically?
[14:39] <shadeslayer> Mamarok: yes
[14:40] <Mamarok> lucky you!
[14:40] <shadeslayer> Mamarok: i know.. there were only a few seats left :P
[14:40] <Mamarok> so either you are full of money or full of luck
[14:40] <shadeslayer> Mamarok: the latter :D
[14:41] <shadeslayer> Mamarok: some last minute cancelations and we were in :)
[14:41] <Mamarok> nice!
[14:42] <shadeslayer> Mamarok: packages copied
[14:42] <Mamarok> right, on another note: how can I get my sound back fro flash in lucid? It stopped working the other day
[14:42] <Mamarok> for*
[14:43] <shadeslayer> Mamarok: hmm.. well is this with just one browser or all of them>
[14:43] <Mamarok> all of them, else I wouldn't have asked
[14:44] <shadeslayer> Mamarok: oh btw the father of the Intel Atom was there too,he gave me his card when i mentioned the magic words 'Ubuntu' , 'Kubuntu' and 'Packager' :p
[14:44] <Mamarok> shadeslayer: the question was not specifically for you, so don't worry too much, I bet some PA stuff broke it
[14:44] <shadeslayer> Mamarok: im refering to Pankaj Kedia :)
[14:44] <shadeslayer> Mamarok: oh np
[14:44] <Mamarok> hey!
[14:45] <Mamarok> shadeslayer: you should have mentioned KDE specifically :)
[14:45] <shadeslayer> Mamarok: hehe
[14:45] <shadeslayer> Mamarok: well he said that theyre working on moblin and i said that i wanted to join intel and that ill probably contact him when i have enough experience
[14:46] <Mamarok> not moblin, MeeGo
[14:46] <Mamarok> moblin is the past
[14:46] <shadeslayer> Mamarok: yeah thats the one
[14:48] <shadeslayer> Mamarok: http://simplest-image-hosting.net/i0-img00122-20100327-1859-jpg.jpg
[14:49] <shadeslayer> a bit blurry,but im the one in the middle
[14:50] <Mamarok> pics in the dark rarely turn out very sharp
[14:50] <shadeslayer> :D
[14:50] <shadeslayer> But as you can see theres a TEDx board behind us.. the confrence was in a auditorium just behind the board
[14:51] <apachelogger> Mamarok: lol :D
[14:51] <Mamarok> apachelogger: lol?
[14:52] <apachelogger> Mamarok: pics in the dark rarely turn out very sharp
[14:52] <shadeslayer_> Mamarok: oh and btw you need to set the volume as high in the flash settings
[14:52] <apachelogger> got a nice sound to it
[14:52] <apachelogger> most awesome actually
[14:52] <apachelogger> or maybe I am still drunk *shrug*
[14:52] <shadeslayer_> Mamarok: if that doesnt do it .. idk :P
[14:52] <Mamarok> shadeslayer_: I tried that, doesn't change
[14:58] <shadeslayer_> ^^ my knowledge of flash ends there
[14:58] <shadeslayer_> Mamarok: one more thing can be done,try removing the .adobe folder in ~
[14:59] <Mamarok> hm, I have a suspicion: I tried to check if Nickelback were as bad as everybody told they were, maybe they broke the flash sound...
[14:59] <Mamarok> ;)
[14:59] <shadeslayer_> Mamarok: hahaha....
[15:00] <shadeslayer_> Mamarok: oh btw do the kraft packages work?
[15:00] <shadeslayer_> i didnt have the time to check
[15:01]  * Mamarok checks now
[15:01] <shadeslayer_> Mamarok: thanks :)
[15:06] <Mamarok> shadeslayer: it opens up correctly, them I get this: http://pastebin.com/b2eTc530
[15:06] <Mamarok> not sure this is package related, though
[15:07] <Mamarok> and dragotin is rearely online
[15:07] <shadeslayer> Mamarok: um..i think this is related to ibus
[15:07] <shadeslayer> Mamarok: QFileSystemWatcher: failed to add paths: /home/myriam/.config/ibus/bus
[15:08] <shadeslayer> Mamarok: do you have ibus installed?
[15:08] <Mamarok> no, apparently not, it should be made a dependency for the package, then
[15:09] <shadeslayer> hmm... ok ill look into this.. :)
[15:10] <Mamarok> shadeslayer: not ibus related
[15:11] <shadeslayer> Mamarok: hmm
[15:11] <Mamarok> http://pastebin.com/ZGkfCtjX
[15:13] <Mamarok> shadeslayer: looks more like a database problem
[15:13] <shadeslayer> Mamarok: yeah... Qsql.. ive not heard of such a package
[15:14] <Mamarok> shadeslayer: I choose the default SQlite, but it looks for MySQL
[15:14] <shadeslayer> Mamarok: ah try libqt4-sql
[15:15] <Mamarok> that is already installed, but the package name is libqt4-sql-sqlite
[15:16] <shadeslayer> Mamarok: well i guess we will have to talk to upstream about this...
[15:16] <shadeslayer> or if somebody else can help...
[15:16] <Mamarok> shadeslayer: do you have dragotin's mail address? I don't know if he often uses IRC
[15:16] <shadeslayer> Mamarok: nope..
[15:16] <Mamarok><EMAIL_ADDRESS>[15:20] <shadeslayer> Mamarok: ive sent him a mail... lets see
[15:26] <Mamarok> shadeslayer: thanks a lot :)
[15:26] <shadeslayer> Mamarok: oh no problem.. lets hope he replies and we can get it working
[15:27] <Mamarok> oh, he sure will :)
[15:27] <Mamarok> he is interested himself in getting this done
[15:27] <Riddell> agateau: does org.ayatana.dbusmenu.xml need to be installed?
[15:27] <agateau> Riddell: don't think so
[15:46] <shtylman> I am UTC retarded... how many hours until the meeting?
[15:47] <Riddell> 7 and 10 minutes
[15:48] <shtylman> Riddell: thanks :)
[15:48] <shtylman> Riddell: also... can bug: #389658 be closed as won't fix?
[15:48] <Riddell> bug 389658
[15:48] <shtylman> the paper cuts aspect of it I mean
[15:49] <Riddell> shtylman: we should add back the icon we had in kde4libs so people can chose it if they want to
[15:49] <shtylman> Riddell: I agree... do we not have that now?
[15:49] <Riddell> shtylman: it seems to have disappeared at some point
[15:49] <shtylman> heh
[15:49] <Riddell> want to add it back?
[15:50] <shtylman> Riddell: sure... for lucid?
[15:50] <Riddell> yes
[15:50] <shtylman> k
[15:50] <Riddell> into bzr
[15:50] <shtylman> indeed
[15:50] <shtylman> maybe add the new logo once we decide?
[15:50] <shtylman> since that will happen today I assume?
[15:52] <rgreening> Riddell: looks like everything is uploaded to PPA/BZR. I'll start reviewing BZR to ensure it all looks good for upload to archives.
[15:55] <Riddell> shtylman: hmm, good point
[15:55] <Riddell> rgreening: I'm worried that I can't install packages in karmic
[15:56] <Riddell> is it using polkit instead of policykit?
[15:56] <rgreening> Riddell: ?
[15:56] <rgreening> Im on lucid, so I can test backports atm
[15:56] <apachelogger> Riddell, shtylman: I would put the icon into kubuntu-default-settings really
[15:56] <apachelogger> otherwise maintenance is a PITA
[15:57] <Riddell> agreed
[16:07] <rgreening> lex: ping
[16:22] <Riddell> koffice 2.1.2 tars are up
[16:24] <rgreening> Riddell: Im started on cleaning up the bzrs to make sure they match (like removing obsolete patches from both bzr and the PPA package)
[16:26] <shtylman> ubuntu slideshow is looking spiffy
[16:26]  * shtylman feels that the kubuntu one needs to be prettier now :)
[16:30] <rgreening> shtylman: do we have a slideshow now?
[16:30]  * rgreening would be impressed :P
[16:33] <shtylman> rgreening: yea... we have a slideshow
[16:33] <shtylman> didn't we have one for karmic? I don't recall such things anymore :)
[16:42] <rgreening> not that I recall
[16:42] <rgreening> could be wrong tho
[16:47] <jussi01> hrm, is anyone else having this: when quassel is maximised and the updates notifier pops up, then you click "not now" and quassel disappears to system tray? (on lucid)
[17:01] <Riddell> rgreening: maybe we should upload qt now
[17:01] <Riddell> lex79: that ok? ^^
[17:01] <rgreening> Riddell: sounds like a plan. give it time to build before we upload kde 4.4.2
[17:02] <Riddell> rgreening: can you make the .diff.gz .dsc and .changes for me to sign and upload?
[17:02] <maco> Sput: quassel client question... is there a limit to how much scrollback itll store locally in memory beyond which point it requests from the server? i'm wondering because after a day or two of running quassel can be using quite a lot of memory. kinda guessing it starts out with X lines scrollback locally then over time as scrollback grows, doesnt trim the old stuff and say "well if i need it later, i'll ask the server"
[17:03] <rgreening> Riddell: sure.. give me a few minutes to grab and generate
[17:03] <Riddell> "few minutes" you'll be lucky :)
[17:03] <rgreening> ya. but you get my meaning.. ill di it and fwd as soon as possible :P
[17:06] <maco> Sput: at least, it doesnt seem to be requesting from the server anything that happened since it was opened, even if that was a long while ago
[17:08] <maco> Sput: http://imagebin.ca/view/NQnZ9Wjt.html  <-- "top" from a few days ago (i started looking at choqok to figure out what it's doing too)
[17:23]  * nixternal is working on koffice-2.1.2 and koffice-l10n-2.1.2
[17:23] <DarkwingDuck> morning nixternal
[17:23] <nixternal> almost noon isn't it :)
[17:23] <nixternal> mornin' to you as well
[17:23] <DarkwingDuck> lol
[17:24] <DarkwingDuck> race is on. lol
[17:24] <nixternal> what race?
[17:24] <DarkwingDuck> nascar
[17:24] <nixternal> oh, got rained out yesterday?
[17:24] <nixternal> martinsville right?
[17:24] <DarkwingDuck> martinsville got rained out yesterday
[17:24] <DarkwingDuck> sunny rt now
[17:25] <nixternal> yeah, I watched the interviews and it looked cold...didn't see the track but you could hear the dryers on it
[17:25] <DarkwingDuck> gotta fix my wiki
[17:25] <nixternal> I am excited, we will be in the 70s this week...that means i will be out riding the hell out of my bikes
[17:25] <DarkwingDuck> :D
[17:26] <nixternal> riding a bike when it is freezing or below freezing is not fun
[17:26] <DarkwingDuck> nope. not at all
[17:26] <DarkwingDuck> oh, nixternal... thanks
[17:26] <nixternal> for?
[17:26] <nixternal> your welcome btw :p
[17:27] <nixternal> i see you can now commit to the repos
[17:27] <DarkwingDuck> Matthew added me to the core-doc team
[17:27] <nixternal> hehe
[17:27] <DarkwingDuck> yuppers
[17:27] <nixternal> just one thing....DON'T COMMIT!
[17:27] <DarkwingDuck> rofl. just in time eh? yeah i know
[17:27] <nixternal> hehe
[17:28] <nixternal> during a freeze, if it really needs to be committed, it is probably safer to let me commit, as they won't yell at me as loud
[17:28] <DarkwingDuck> :)
[17:28] <DarkwingDuck> we are done for this cycle right? everything in translations
[17:30] <DarkwingDuck> bbiaf
[17:30] <nixternal> the people are back out working on the transformer that sits behind our house...if they blow the power, i will personally go out there and handle them
[17:30] <nixternal> yeah, it is all about the translations now
[17:30] <DarkwingDuck> lol
[17:30] <DarkwingDuck> okay... brb
[17:31] <rgreening> Riddell: I see some lintian errs from qt build. can you look at http://paste.ubuntu.com/406065/
[17:32] <Riddell> rgreening: nothing to worry about there that I can see
[17:32] <rgreening> Riddell: ok
[17:32] <Riddell> changing those would just get us out of sync with debian for no gain
[17:33] <rgreening> np. want me to upload the dsc to ktown?
[17:33] <rgreening> Riddell: ^
[17:34] <Riddell> rgreening: ktown not the best place if you have somewhere else
[17:34] <Riddell> but anywhere is good
[17:34] <lex79> rgreening: why you signed qt package with your name? lol
[17:35] <shadeslayer> nixternal: can i file a bug for inserting a new package in kubuntu?
[17:35] <shadeslayer> or is it too late?
[17:35] <nixternal> to late
[17:35] <rgreening> lex79: updating for Riddell to upload (as per Riddell) and as per I reviewed it (being coord for the release). You still get cred :P
[17:35] <shadeslayer> nixternal: meh.. ok ill file one anyways,maybe itll get included in backports
[17:36] <shadeslayer> nixternal: ive basically built a new version of a kraft in my PPA... upgraded it from 0.2 to 0.4b2
[17:36] <lex79> rgreening: you should use debuild -S -sa -kyour_email to generate dsc
[17:36] <shadeslayer> apparently it runs fine here,but mamarok had a problem with the package
[17:37] <debfx> Riddell: have you had a chance to test the brightness osd patch?
[17:38] <Riddell> debfx: oh sorry that's still on my todo
[17:38] <dpm> nixternal, thanks for the heads up on kubuntu-docs. The only missing part was me accepting the "Needs Review" templates. It was a bit of a hectic weekend, so I only came to it this morning, but they are all ok now. I've got one question, though. There is a template in https://translations.edge.launchpad.net/ubuntu/lucid/+source/kubuntu-docs/+imports?field.filter_status=NEEDS_REVIEW&field.filter_extension=pot which conflicts with another one (docs/about
[17:38] <dpm> /po/about.pot) I think the docs/about... is already the correct one, and I shuld get rid of that template in the queue. Is that correct?
[17:38] <rgreening> lex79: Yeah, prob could have done that for qt, as there were no changes
[17:38] <Riddell> shadeslayer: you can request a feature freeze exception
[17:38] <rgreening> my bad
[17:39] <shadeslayer> Riddell: well just so that you know that the original version in the repo uses KDE 3 libs i think
[17:40] <shadeslayer> and its my understanding that were trying to remove as many KDE 3 apps as possible right
[17:40] <rgreening> Riddell: the files are on ktown under qt4-x11. feel free to delete when done with them
[17:41] <rgreening> Riddell: we need to get some secure space for hosting.. any thoughts?
[17:41] <Riddell> rgreening: why secure?  people.ubuntu.com would work
[17:41] <Riddell> glatzor: hi
[17:41] <rgreening> Riddell: cool. how do I get that?
[17:42] <Riddell> rgreening: I don't know but I believe it's available to anyone with membership
[17:42] <jussi01> https://wiki.ubuntu.com/PeopleUbuntuCom
[17:45] <nixternal> damn koffice-l10n package will not build, FTBFS because of docbook entities
[17:45] <nixternal> rgreening: ssh<EMAIL_ADDRESS>[17:45] <nixternal> use your ssh password that is on lp
[17:45] <Riddell> nixternal: which one?
[17:46] <Riddell> I mean what version
[17:46] <nixternal> Riddell: 2.1.2
[17:46] <Riddell> nixternal: are you doing koffice too?
[17:46] <rgreening> nixternal: cool. ty
[17:46] <nixternal> Riddell: yes
[17:46] <nixternal> rgreening: then it will be http://people.ubuntu.com/~lp_id
[17:47] <nixternal> rgreening: actually, I don't think you can ssh to it, just sftp to it maybe
[17:47] <Riddell> nixternal: ping cyrille in #koffice
[17:47] <nixternal> trying something really quick then I will do so
[17:48] <nixternal> and that didn't work
[17:49] <Riddell> rgreening: did you upload the wrong thing?  qt4-x11_4.6.2-0ubuntu3~ppa2.diff.gz has "ppa" in it
[17:50] <rgreening> Riddell: ah. prob. let me look again
[17:51] <rgreening> Riddell: yeah, cp/paste wrong .. uploaded now.
[17:54] <nixternal> dpm: thanks! got all of the email this morning about all of the templates being in :)
[17:55] <dpm> cool (well, apart from the spam bit ;) )
[17:55] <nixternal> dpm: ahh dang, so a .desktop.in pot file is conflicting with a docbook one
[17:55] <nixternal> ok, I will have to rename the desktop one and reupload
[17:56] <dpm> nixternal, hmm, I think we can sort this out without a reupload, I'll just try to rename the template in LP differently. Let me just try, give me a sec
[17:59] <nixternal> dpm: groovy
[17:59] <nixternal> otherwise I can do a quick upload
[18:01]  * hunger grumbles that the udevadm divert was left in place after the latest update of lucid. Broke the boot.
[18:06] <Riddell> rgreening: uploaded qt
[18:06] <rgreening> Cool.
[18:07] <rgreening> Riddell: I have people.ubuntu.com/~roderick-greening setup, so I can use that moving forward for uploads. Thanks.
[18:08] <dpm> nixternal, ok, should be ok now -> https://translations.edge.launchpad.net/ubuntu/lucid/+source/kubuntu-docs/+translations I've named it kubuntu-docs-about-desktop. If the name is ok for you, then we're all set, if not, just tell me which template name you'd prefer and I'll change it straight away
[18:08] <nixternal> dpm: rock on!
[18:08] <nixternal> thanks
[18:09] <nixternal> that name is good, I will know what it is (I hope)
[18:09] <dpm> \o/
[18:09] <nixternal> i am glad you cleaned out the old templates...i didnt' know about that and when i went to do translations a couple of releases ago, i was importing old templates and was confused as all hell :)
[18:10] <nixternal> now I will work up a script that will take the LP tarball when I go for it, and do everything for me
[18:10] <dpm> cool
[18:10] <nixternal> that way there I can have my monkeys, errr minions, errr jjesse and DarkwingDuck do translation imports too :)
[18:10] <dpm> hahaha
[18:12] <dpm> the ubuntu-docs sources have got scripts for that as well. You might already know them, but in case you don't, perhaps you can use some of them for kubuntu-docs. In any case, if you've got any questions and I can be of any help, just give me a shout
[18:12] <nixternal> yeah, i used it in the past, but it needs to be reworked to work for kubuntu a bit better
[18:12] <nixternal> to use it, i have to install gnome-doc-tools, which doesn't sound right for kubuntu-docs :)
[18:17] <dpm> :)
[18:25] <DarkwingDuck> still not getting a splash screen on startup
[18:25] <DarkwingDuck> nixternal: ping
[18:26] <nixternal> one minute
[18:26] <nixternal> DarkwingDuck: go for it
[18:27] <DarkwingDuck> nixternal: after tonights meeting we need to take some steps to ensure we don't duplicate this bug on the kubuntu side. bug: 551058
[18:27] <DarkwingDuck> bug:551058
[18:28] <DarkwingDuck> https://bugs.launchpad.net/bugs/551058
[18:28] <genii> DarkwingDuck: Here either, plymouth seems broken for me. I do see maybe 1/4 second flash of it *just* before NVidia logo but very oversize
[18:28] <DarkwingDuck> genii: Only time I get it is when I scan drives
[18:28] <DarkwingDuck> However, shutdown it works fine
[18:29] <jjesse> nixternal: if i knew/understand the whole translation import process i would be more then willing to use them
[18:29] <nixternal> DarkwingDuck: that is why i removed anything witht he kubuntu logo out of the docs
[18:29] <DarkwingDuck> nixternal: I thought you had but, wasn't 100% sure
[18:29] <DarkwingDuck> so I thought I'd mention it
[18:29] <jjesse> DarkwingDuck nixternal maybe we should do a planning meaning for whatever Kubuntu M is and we can do it via my conference bridge so we can actually talk
[18:30] <DarkwingDuck> Am willing to call... nixternal and I both are on VZW
[18:30] <jjesse> i'm on VZW as well, nixternal has my cell # if i recall correctly
[18:30] <jjesse> plus on the droid it is super simple to setup a conference call
[18:31] <DarkwingDuck> jjesse: you have the Motorola Droid?
[18:31] <jjesse> DarkwingDuck:  yup
[18:31] <DarkwingDuck> Its a wonderful phone eh?
[18:31] <jjesse> love it
[18:31] <DarkwingDuck> LOVE the phone
[18:31] <DarkwingDuck> I upgraded from the Tour to it... I still have a Storm laying around my place
[18:32] <DarkwingDuck> jjesse: Your on CST right?
[18:32] <nixternal> jjesse: that works
[18:32] <DarkwingDuck> jjesse nixternal just let me know what time you want to do this call.
[18:33] <nixternal> i will never let google have my data! they are evil! I am going with an iPhone :p
[18:33] <nixternal> no time soon, or at least today....i am up to my neck in upstream shit right now
[18:33] <DarkwingDuck> eeeewww AT&T???
[18:33] <DarkwingDuck> Well, meeting is at 2300UTC
[18:33] <DarkwingDuck> that is what... 1800 CST for us?
[18:36] <jjesse> 1700 EDT
[18:36] <jjesse> 1900 EDT
[18:36] <jjesse>  :)
[18:37] <DarkwingDuck> So yeah, thats 1800 CST :P
[18:45] <freinhard> changing the timezone in digital clock doesn't work. kde or kubuntu issue?
[18:47] <DarkwingDuck> It worked for me...
[18:49] <freinhard> the apply button is greyed, ok isn't. the dialog says i will be asked to authenticate, i wasn't.
[18:56] <shadeslayer> Riddell: ping
[18:56] <shadeslayer> Riddell: how do i go about filing a feature freeze exception
[18:57] <lex79> shadeslayer: open a bug in launchpad
[18:58] <shadeslayer> lex79: ok and?
[18:58] <neversfelde> Riddell: https://code.edge.launchpad.net/~kubuntu-members/amarok/ubuntu
[18:58] <shadeslayer> lex79: oh and one more thing,can you test out kraft from https://launchpad.net/~rohangarg/+archive/kde-extra
[18:58] <neversfelde> sorry, I should have posted here, that I am working on amarok
[18:59] <shadeslayer> lex79: it apparently runs fine on my machine but not on Mamarok
[18:59] <shadeslayer> s/Mamarok/Mamarok's Machine
[19:05] <lex79> shadeslayer: is it a beta 2 version? I don't think we want beta2 applications in archive, too late
[19:05] <shadeslayer> lex79: yeah its a beta 2 version
[19:06] <shadeslayer> lex79: hmm.. can they go in backports?
[19:07] <lex79> nope for now
[19:08] <lex79> maybe when final version will be released
[19:09] <shadeslayer> lex79: hmm... btw do they run fine on your machine? ( the packages i mean )
[19:12] <lex79> shadeslayer: it works, yes
[19:13] <shadeslayer> lex79: ah thanks for the feedback.... weird that it didnt work on Mamaroks machine
[19:16] <nixternal> koffice will have to wait...they need to repackage l10n and koffice tarballs thanks to me :D
[19:21] <DarkwingDuck> hehehe
[19:33] <DarkwingDuck> genii: did you file a bug for the plymouth boot splash problem?
[19:33] <nixternal> what is the problem?
[19:34] <DarkwingDuck> genii and I dont have a splash image on boot. We do for shutdown
[19:35] <DarkwingDuck> Figured you were busy so I would pester you with a bug :P
[19:35] <nixternal> did you have the ubuntu one on boot previously?
[19:35] <DarkwingDuck> Yes
[19:35] <nixternal> try this:
[19:35] <nixternal> sudo update-initramfs -u
[19:36] <nixternal> for some reason, it seems it didn't update for you all, which I don't understand why it didn't
[19:36] <genii> nixternal: Already updated my initramfs when I dupgraded kernel to -18 ( for nvidia dkms)
[19:36] <nixternal> what shows now when you boot up? the ubuntu one
[19:37] <DarkwingDuck> dunno... hang on and I'll let ya know
[19:37] <genii> nixternal: For me, I get blinking cursor only then a flash of whichever one is currently on (In this case the kubuntu amd64 deb you had) then my NVidia logo comes on, then kde splash, etc
[19:41] <DarkwingDuck> nixternal: Nope. Black screen with a blinking white curser line in the upper left still
[19:42] <DarkwingDuck> However, when I shutdown it shows up quite pretty like
[19:42] <DarkwingDuck> taunting me... :P
[19:43] <genii> I also on shutdown see whichever logo is set. But the size during both boot and shutdown is extremely huge (to the point of pixellation)
[19:43] <genii> DarkwingDuck: You have nvidia card?
[19:43] <DarkwingDuck> and I don't get anything... INTEL video drivers
[19:44] <genii> Hm
[19:44] <DarkwingDuck> This is strange...
[19:46] <DarkwingDuck> I'm removing the ubuntu theme packages and reinstalling the kubuntu ones and see if that tricks something
[19:49] <genii> DarkwingDuck: This may be something related to bug 506717
[19:50] <DarkwingDuck> possibly... But, then it would also apply to intel drivers
[19:50] <maco> freinhard: the digital clock's timezone setting thing is fine for me. you sure you dont mean the system settings one? cuz that one's broken just like you described on my machine
[19:51] <freinhard> maco: well i can add different timezones to the digital clock and since i get to the configuration of the systemwide timezone i didn't make a difference there.
[19:52] <freinhard> *since i get there from the same menue...
[19:52] <maco> freinhard: huh?
[19:53] <jussi01> Can someone with Quassel test this for me?
[19:53] <jussi01> when quassel is maximised and the updates notifier pops up, then you click "not now" and quassel disappears to system tray? (on lucid)
[19:53] <maco> freinhard: right clicking the clock applet and going to its settings, i just get checkboxes to pick what goes in the dropdown, then choose one from the dropdown. there's no "apply" button at all. just ok/cancel
[19:53] <freinhard> maco: you get to the configuration of the systemwide timezone trough the digital clock menue
[19:53] <maco> freinhard: you do?  how?
[19:54] <freinhard> digital clock->right click->adjust date and time
[19:54] <maco> reahhhhh
[19:54] <freinhard> then switch to timezone
[19:54] <genii> DarkwingDuck: Postings 23-27, 63   indicate nvidia is not the only affected
[19:54] <maco> i went to the clock's "digital clock settings" in the right click menu
[19:55] <maco> ok yeah that thing you're seeing is the same thing as what's in systemsettings
[19:55] <maco> it's just another way to reach it
[19:55] <maco> yes, i see the kcm module for timezones being broken
[19:55] <freinhard> that's another story. the widget is stupid enough to show timezones twice.
[19:55] <DarkwingDuck> genii: Yeah, I see that... I might try purging plymouth, reinstall and reboot to see what happens.
[19:55] <maco> freinhard: huh??
[19:55] <maco> its not being stupid actually...
[19:55] <maco> you can set the clock itself to show a different timezone than your system time
[19:55] <freinhard> maco: it is, let me explain it
[19:56] <maco> i have 3 clock applets. one shows local, one shows GMT, one shows berlin
[19:56] <DarkwingDuck> genii: Because, the problem occured only after the new theme
[19:56] <maco> so the one youre clicking is for system time. the one in the digital clock settings is for *that specific applet*
[19:57] <freinhard> maco: here's what you do: add some timezones including your own in the digital clock timezones settings. then use your mousewheel on the clock to switch the displayed time to another timezone. then move your mouse a gain over the clock and see that the tooltip shows your local timezone twice
[19:57] <freinhard> i call that stupid ;)
[19:58] <maco> wait you mean put "local" AND the actual name for your local timezone *both* into the applet's settings?
[19:58] <freinhard> yes
[19:58] <freinhard> erm no
[19:59] <freinhard> give me a minute
[19:59] <DarkwingDuck> genii: I'm giving this a shot... BRB
[19:59] <maco> i had no idea you could mousewheel over the applet
[20:01]  * genii makes more coffee
[20:02] <freinhard> maco: http://imagebin.ca/view/3qMiRm.html
[20:02] <freinhard> first and last timezone: sydney
[20:02] <freinhard> doesn't make any sense at all
[20:09] <DarkwingDuck> *grumbles* nada
[20:10] <DarkwingDuck> nixternal: I didn't change that?
[20:12] <genii> DarkwingDuck: I'm going to try changing my framebuffer. Back in a bit
[20:12] <DarkwingDuck> kk
[20:13] <Riddell> neversfelde: what's that about amarok?
[20:15] <neversfelde> Riddell: amarok crashes, when it's info applet is enabled. The patch fixes that and markey suggested to use it on the amarok packager list a while ago
[20:18] <maco> freeflying: huh. mine looks nothing like that
[20:18] <markey> neversfelde: yes, using that patch would be good
[20:18] <markey> it's safe, and really fixes this issue for good
[20:19] <neversfelde> yes, it fixes it for lucid. I'll test it for karmic later.
[20:20] <nixternal> DarkwingDuck: it wasn't in the desktop.xml file
[20:20] <nixternal> so since it was just a package name, i went ahead changed, it, updated the pot file, and created a new package
[20:21] <maco> freeflying: er not you
[20:21] <maco> oh hrmph. freinhard left. well my clock doesnt look funny like his:  http://imagebin.ca/view/xTVIZ7w3.html
[20:32] <genii> DarkwingDuck, nixternal: No dice on the framebuffer change, as far as getting the plymouth logo. I took a pic of what it does look like for the brief moment it is seen during boot/shutdown http://i40.tinypic.com/20gck7o.jpg
[20:37] <nixternal> genii: I have no idea why it isn't working for you and DarkwingDuck...the only difference between it and the ubuntu theme is I changed 2 rgb values (TopBackgroundColor and BottomBackgroundColor) and changed the ubuntu_logo.png to a kubuntu_logo.png which is the same exact format
[20:38] <nixternal> genii: so you do at least get an image at boot or not at all?
[20:38] <nixternal> or was that pic snapped at shutdown? because you said "during boot/shutdown"
[20:39] <genii> nixternal: I get it just at the last moment of booting just before my NVidia logo pops up, and then lust briefly again for another 1/4-1/2 second during shutdown... at the size which you see both times. That particular pic was at shutdown but at both times it appears the same
[20:40] <nixternal> anyone else see a pixbuf error prior to KDM starting? I keep seeing this pixbuf error on a black screen before the kdm image loads, however I can see the mouse cursor at that time
[20:40] <nixternal> i think any issues you are seeing are either related to plymouth or nvidia drivers....the theme isn't the issue, i am fairly positive on that
[20:41] <JontheEchidna> Nope, works fine here with Intel
[20:41] <nixternal> w00t, koffice-l10n built \o/
[20:41] <nixternal> JontheEchidna: yeah, same here
[20:41] <genii> nixternal: Yes, I think I'll do some more poking around
[20:41] <Riddell> nixternal: new tar?
[20:41] <nixternal> that's why I think it is the nvidia stuff, because they both are plagued by the nvidia logo on startup :D
[20:41] <JontheEchidna> :D
[20:41] <nixternal> Riddell: yup :) for l10n and koffice
[20:42] <nixternal> building koffice now, first build, where I can do a proper list-missing, then fix that up, then do a pbuilder-build so I can test, and then clean everything up, build one more time, test and commit
[20:43] <nixternal> i try not to upload broken stuff...i think the only thing i upload broken is kubuntu-docs after importing translations...though this time around I have a test bed of other kubuntu installs with various languages (fr, de, zh_CN)
[20:47] <keffie_jayx> hello all, I have just updated my netbook to lucid and I notice lack of window borders when windows are maximized, Is this a feature or a bug?
[20:48] <keffie_jayx> this is netbook-plasma
[20:48] <rgreening> Riddell: there's a new digikam 1.2.0 out. Will we be able to update or is it too late? Prob too late... but I guess we can put in updates
[20:49] <nixternal> keffie_jayx: feature
[20:49] <nixternal> maximizing the amount of screen realestate as possible
[20:49] <keffie_jayx> nixternal:  thanks. I was thinking something had gone wrong with the window border
[20:50] <nixternal> if it is maximized, why the need for a window border right? :)
[20:50] <nixternal> once you unmaximize it, then you get the window border
[20:51] <keffie_jayx> nixternal: right. cool thing then. I am currently trying stuff after an update, a reporting some bugs
[20:51] <keffie_jayx> thanks again
[21:05] <DarkwingDuck> nixternal: that's strange... It works perfect for shutdown but not startup... Its almost as if something turned off a graphic bootloader or something.
[21:07] <nixternal> yeah, probably called nvidia
[21:08] <DarkwingDuck> I'm running an intel vid on my thinkpad though
[21:09] <nixternal> oh?
[21:09] <nixternal> well, I still blame nvidia
[21:10] <DarkwingDuck> where is plymouth installed at?
[21:10] <nixternal> /lib/plymouth
[21:10] <nixternal> /lib/plymouth
[21:10] <nixternal> interesting, usually doing / first doesn't work, but it did for me
[21:15] <DarkwingDuck> is there a plymouth theme switcher?
[21:15] <lex79> Can we put oxygen color scheme in Lucid instead of keeping our colors? bug 551117
[21:17] <nixternal> DarkwingDuck: sudo update-alternatives --config default.plymouth
[21:18] <DarkwingDuck> okay, brb, lemme try that... there are two choices for kubutnu-logo
[21:19] <DarkwingDuck> an auto and a manual
[21:19] <DarkwingDuck> BRB
[21:20] <nixternal> Riddell: is it safe to upload koffice-l10n prior to koffice?
[21:20] <nixternal> I will wait, as I need a few more hours more than likely, and I don't know if I can dedicate a few more hours straight, would be cutting it close as I am planning on going out this evening
[21:24] <rgreening> Riddell: Uploaded newly fixed kdelib5 to PPA. After it builds, I'll then retry kdebase-workspace, which depends on the changes in kdelibs5.
[21:24] <rgreening> Ill check back later on it.
[21:30] <DarkwingDuck> nixternal: okay, it's not plymouth.
[21:30] <DarkwingDuck> For soem reason It's not loading any bootsplash
[21:30] <DarkwingDuck> the defualt ubuntu one doesn't work anymore
[21:31] <DarkwingDuck> Or rather, it's not your plymouth theme
[21:44] <genii> DarkwingDuck: I got mine working finally
[22:00] <neversfelde> Meeting in 2 hours?
[22:00] <ryanakca> neversfelde: Aye
[22:00] <neversfelde> that's late :)
[22:03] <DarkwingDuck> genii: how?
[22:04] <ryanakca> nixternal: update-alternatives vs. plymouth-set-default-theme ?
[22:15] <ScottK> nixternal: The plymouth theme works fine here (also Intel).
[22:18] <nixternal> ryanakca: where is plymouth-set-default-theme? it was removed iirc for update-alternatives
[22:19] <dantti> JontheEchidna: :D It can now save PPD options :D take a look when you can
[22:19] <JontheEchidna> neat!
[22:21] <dantti> JontheEchidna: in regard of changing settings it only misses selecting a different driver (I think I'll do that tomorrow)
[22:21] <nixternal> 16:15:02 [@     root] yahoo - Message from unknown handle manishmotwani:
[22:21] <nixternal> 16:15:02 [@     root] You work for Canonical, right?
[22:21] <JontheEchidna> lol
[22:21] <nixternal> LOL, gotta love bitlbee
[22:22] <JontheEchidna> nixternal: did you see the guy on your blog commenting about the atrocity of an unfinished font not having a K?
[22:22] <JontheEchidna> I lol'd
[22:23] <nixternal> yeah
[22:23] <nixternal> ubnt isn't even finished yet
[22:23] <JontheEchidna> dantti: Know anything about that weird character next to "and" in the sidebar?
[22:23] <JontheEchidna> http://simplest-image-hosting.net/i0-plasma-desktopga1544-jpg.jpg
[22:24] <dantti> JontheEchidna: hmm that was supposed to be a '\n'
[22:24] <JontheEchidna> dantti: I think that the sidebar code handles that automagically
[22:24] <dantti> as it's too wide
[22:24] <dantti> no
[22:25] <dantti> it get's pretty wide
[22:25] <JontheEchidna> Oh, it's new in KDE 4.4
[22:25] <dantti> unless there is some hidden option I didn't find..
[22:25] <dantti> or 4.4 :P
[22:25] <JontheEchidna> :)
[22:25] <JontheEchidna> Though, doesn't policies imply allowed users?
[22:25] <dantti> maybe that's why you see that char...
[22:26] <dantti> JontheEchidna: what do you mean?
[22:26] <JontheEchidna> I thought policies were where you could define who can do what
[22:26] <JontheEchidna> which is the same as allowed users
[22:26] <JontheEchidna> am I confusing the two?
[22:27] <dantti> well policies at localhost:631, defines just the users that can/can't print
[22:27] <dantti> a no
[22:28] <dantti> the policies are something like printer behavior
[22:28] <dantti> like what to do when it can't print...
[22:28] <JontheEchidna> ooh, ok
[22:28] <dantti> on error retry job
[22:28] <dantti> maybe we can find a less confusing naming
[22:28] <JontheEchidna> Just a bit confused, because the PolKit config modules is called "System Policies" in trunk
[22:28] <dantti> yup :)
[22:34] <dantti> k, got to go now... cya
[22:34] <JontheEchidna> cya
[22:45] <nixternal> damn, no changes to the packaging except for ripping out a patch for koffice
[22:45] <nixternal> i love it when it just works
[23:07] <rgreening> when is the meeting? now or 1 hr?
[23:07] <DarkwingDuck> 1hr
[23:08] <apachelogger> \o/ windows xp sp2 :D
[23:09] <rgreening> kk
[23:09] <apachelogger> ScottK: I was thinking... maybe we could deploy KDE updates in form of service packs?
[23:09] <rgreening> ty. UTC drives me nuts with DST
[23:09] <DarkwingDuck> LOL
[23:09] <rgreening> We should book in GMT no DST
[23:09] <rgreening> :)
[23:09] <DarkwingDuck> rgreening: Yeah, Know. LOL
[23:10] <DarkwingDuck> apachelogger: Service packs? That lazy? :P
[23:11] <Tm_T> monday patches
[23:11] <apachelogger> well, we cant push it via the repos
[23:11] <apachelogger> so maybe service packs would be a good approach
[23:12] <ScottK> apachelogger: We mostly need to get upstream to sign up for a policy of bug fix only in third digit updates.
[23:12] <ScottK> I think we can get it pushed through then.
[23:12] <apachelogger> well, until that :)
[23:13]  * apachelogger is getting the midnight hunger
[23:16] <crimsun> crzy-rse mtg times
[23:17] <huats> Does anyone can point me to a simple package that uses CMake ? I'd like to see a bit how it works
[23:17] <nixternal> huats: python or c++?
[23:18] <huats> c++ nixternal
[23:18] <nixternal> umm
[23:18] <nixternal> simple...lets see
[23:18] <ScottK> Any KDE package.
[23:18] <ScottK> Although those aren't typically "simple".
[23:19] <nixternal> huats: partitionmanager is fairly simple
[23:19] <huats> nixternal, actually I give a lesson tomorrow on debian packaging and I know some of my students will ask me about packaging a C++ application that uses CMake :)
[23:19] <huats> nixternal, ok I'll check that one then !
[23:19] <huats> thanks
[23:20] <nixternal> np
[23:21] <apachelogger> omg
[23:21] <apachelogger> I was attacked by spiders
[23:21] <apachelogger> but I managed to escape
[23:22]  * DarkwingDuck raises an eyebrow
[23:22] <apachelogger> and now I am in posession of
[23:22] <apachelogger> pop corn!
[23:22] <DarkwingDuck> apachelogger: Do you sleep?
[23:22]  * apachelogger invites Nightrose to sit next to him at the meeting, so that he may share
[23:22] <apachelogger> DarkwingDuck: barely
[23:22] <DarkwingDuck> Insomniatic visions are not good :P
[23:22] <Nightrose> oh dear
[23:22] <Nightrose> meeting
[23:23]  * apachelogger thinks Nightrose is not prepared ^^
[23:23] <Nightrose> :D
[23:23] <apachelogger> oh
[23:24] <apachelogger> I have an agenda item
[23:24]  * Tm_T huggles Nightrose and apachelogger
[23:24]  * apachelogger rehuggles Tm_T
[23:24] <Nightrose> :)
[23:24]  * Nightrose listens to http://buytaert.net/milow-born-in-the-eighties
[23:24] <Nightrose> beautiful song
[23:24] <Tm_T> Nightrose: oh and that one rant in identi.ca, made me wonder why bother to post that poorly articulated stuff...
[23:25] <Nightrose> Tm_T: not just you...
[23:25] <apachelogger> DarkwingDuck: what does ICO mean?
[23:25] <Nightrose> the guy's a bit strange
[23:25] <Nightrose> well a bit...
[23:25] <Tm_T> glad I'm not
[23:25] <Tm_T> ...a bit
[23:26]  * apachelogger almost wanted to identica rant about how smb is broken in kde 4.4.0 :P
[23:28] <neversfelde> where is the meeting agenda?
[23:29] <JontheEchidna> \o/ http://simplest-image-hosting.net/i0-plasma-desktopik1544-jpg.jpg
[23:30] <JontheEchidna> when I am too lazy to make a gui for things, I crap it out with kDebug() :P
[23:30] <apachelogger> kubotu: google kubuntu wiki meetings
[23:30] <kubotu> Results for kubuntu wiki meetings: 1. Desktop Team 20090623 meeting minutes<EMAIL_ADDRESS>| 2. Print Page - Lucid Release Schedule, Plans, KDE 4.4: http://www.kubuntuforums.net/forums/index.php?action=printpage;topic=3108103.0 | 3. Re: Kubuntu meeting in ~2 hours (#ubuntu-meeting) - msg#02316 ...: http://osdir.com/ml/ubuntu-users/2010-01/msg02316.html
[23:30] <apachelogger> hm
[23:30] <apachelogger> neversfelde: https://wiki.kubuntu.org/Kubuntu/Meetings
[23:30] <neversfelde> apachelogger: thanks
[23:31] <apachelogger> JontheEchidna: hehe, cool
[23:31] <apachelogger> JontheEchidna: also kdebug++
[23:32] <JontheEchidna> apachelogger: the "actually make this apt implementation install stuff" is going to be the harder part, as long as I want to have PolicyKit integration so apps using it can be run as a normal user
[23:33] <apachelogger> JontheEchidna: how so?
[23:34] <JontheEchidna> gotta pass things between processes, iirc.
[23:34] <JontheEchidna> also, I'll have to look at another api. Though if I conquered apt-pkg I guess it won't be too hard
[23:35] <JontheEchidna> using apt-pkg means using crazy pointer-fu
[23:36] <apachelogger> pointers!!!
[23:36] <Tm_T> pointy fingers!
[23:37] <JontheEchidna> pkgCache::VerIterator ver = (*m_depCache)[*m_packageIter].CandidateVerIter(*m_depCache);
[23:37] <JontheEchidna> \o/
[23:37] <DarkwingDuck> apachelogger: ICO is a naval term sorry... it means "In Care Of"
[23:37] <apachelogger> ah :)
[23:38]  * apachelogger notes that shtylman doesnt have a wiki page and will have to get grilled a lot for that :P
[23:38] <apachelogger> JontheEchidna: at least there aint is no ** ;)
[23:38] <DarkwingDuck> nixternal: Velvet purple always works for weddings...
[23:38] <JontheEchidna> apachelogger: After that bit of pointer madness, we then get the file list from that version iterator, make a pkgRecords::Parser out of that, then do a lookupon the parser for the version maintainer
[23:38] <neversfelde> apachelogger: mhh https://wiki.kubuntu.org/RomanShtylman
[23:38] <shtylman> apachelogger: https://wiki.ubuntu.com/RomanShtylman
[23:38] <neversfelde> just read it
[23:38] <apachelogger> JontheEchidna: the first dereferenceis not necessary btw
[23:38] <apachelogger> s/./->
[23:39] <huats> nixternal, where is defined the install target in the partitionmanager package ?
[23:39] <JontheEchidna> apachelogger: so m_packageIter->CandidateIterVer?
[23:39] <huats> I have a simple helloworld here that fails to build because of that :(
[23:39] <apachelogger> shtylman: your lp thingy ... erm page ... should link there I suppsoe :)
[23:40] <apachelogger> JontheEchidna: m_depCache[*m_packageIter]->CandidateVerIter(*m_depCache);
[23:40] <apachelogger> possibley put the stuff before the -> into bracets
[23:41] <apachelogger> or maybe I am already to drunk to parse pointers ^^
[23:41] <JontheEchidna> lol
[23:41] <ScottK> apachelogger: Isn't that supposed to help?
[23:41] <apachelogger> not past ballmer peak ^^
[23:43] <ScottK> Ah, true.
[23:45] <lex79> JontheEchidna: any thoughts on this? bug 551117
[23:46] <JontheEchidna> lex79: I remember that we had a custom setting in there in the past, but since the whole dir structure got moved around I've not been able to find it. But I do know it's still lingering around somewhere
[23:46] <apachelogger> probably in kdeglobals
[23:46] <apachelogger> we did not have a proper colors profile for that
[23:46] <apachelogger> which I wanted to fix at some point ^^
[23:47] <apachelogger> JontheEchidna, lex79: my two cents: I never liked our brighter version, I am scared it will give me eye cancer or something
[23:47] <apachelogger> way too bright IMHO
[23:47] <JontheEchidna> lol
[23:47] <apachelogger> oxygen is just right
[23:47] <JontheEchidna> especially on LCD's that have less contrast capabilites
[23:48] <JontheEchidna> o,r I should say, lower-quality contrast capabilities
[23:48] <JontheEchidna> too bight
[23:48] <JontheEchidna> bla
[23:48] <nixternal> huats: you pass -DCMAKE_INSTALL_PREFIX= to tell it where to install
[23:48] <lex79> apachelogger: ok, who wants fix that? :D
[23:48]  * apachelogger points at lex79 :P
[23:48] <apachelogger> omg
[23:48] <nixternal> more than likely there is a dh --with-kde in debian/rules, and that tells it '-DCMAKE_INSTALL_PREFIX=`kde4-config --prefix`'
[23:48]  * lex79 points to JontheEchidna :P
[23:49] <huats> nixternal, ok
[23:49] <apachelogger> austria radio only features crap -.-
[23:49] <nixternal> umm, i might be leaving dangit
[23:49] <huats> this was something I have removed to strip down to the essential :)
[23:50] <JontheEchidna> apachelogger: this is the closest I found in kdeglobals:
[23:50] <JontheEchidna> [Colors:Window]
[23:50] <JontheEchidna> BackgroundNormal=233,232,232
[23:50] <apachelogger> that is it
[23:50] <JontheEchidna> the whole colorscheme?
[23:50] <apachelogger> we only changed the main color
[23:50] <JontheEchidna> ah
[23:50] <JontheEchidna> the blues looked a bit different, I thought
[23:50] <apachelogger> that is probably why we did not create a whole scheme
[23:50]  * apachelogger beings to remember :D
[23:50] <lex79> you should remove that to fix
[23:51] <JontheEchidna> I'll put it on the agenda for this meeting, since it's an artwork meeting anyways
[23:51] <lex79> sounds good
[23:53] <rgreening> I cant change my password on my system. I get "system error" and an exit code of 10. THe man page does not show exit codes beyond 5!!?!?!
[23:53] <rgreening> grrrr
[23:56] <DarkwingDuck> apachelogger: kubuntu-ppa/experimental?
[23:56] <apachelogger> kubotu: google kubuntu wiki kubuntu ppas experimental
[23:56] <kubotu> Results for kubuntu wiki kubuntu ppas experimental: 1. News | Kubuntu: http://www.kubuntu.org/news | 2. KDE 4.2 Beta 2 | Kubuntu: http://www.kubuntu.org/news/kde-4.2-beta-2 | 3. Kubuntu - Konversation: http://konversation.kde.org/wiki/Kubuntu
[23:56] <apachelogger> -.-
[23:57] <apachelogger> google is quite the horrible search engine
[23:57] <DarkwingDuck> :D
[23:57] <DarkwingDuck> But, that's where I would do right? I can find it
[23:57] <apachelogger> https://wiki.kubuntu.org/Kubuntu/KubuntuPPAs#Kubuntu Experimental
[23:57] <DarkwingDuck> #ubuntu-meeting right?
[23:57] <apachelogger> looks like it
[23:58] <DarkwingDuck> Thanks apachelogger
[23:58] <DarkwingDuck> for the experimental ppa link
[23:58] <Riddell> ** meeting in a couple of minutes in #ubuntu-meeting
[23:58]  * apachelogger is wondering if we have quorum at all
[23:58] <apachelogger> kubotu: topic learn
[23:58] <kubotu> alright
[23:59] <apachelogger> kubotu: topic set Kubuntu Meeting in #ubuntu-meeting


[00:00] <menn0> wallyworld: thanks
[00:02] <wallyworld> menn0: actually, i don't have credentials for jujubot, i'll ask the qa guys
[00:05] <menn0> wallyworld: I would have thought you could do it with your own account?
[00:09] <wallyworld> menn0: that's don
[00:09] <wallyworld> e
[00:10] <wallyworld> menn0: yeah, i could, i didn't realise i could :-)
[00:14] <menn0> wallyworld: cheers :)
[00:14] <wallyworld> np
[00:19] <wallyworld> menn0: fyi, i'm working on the status 2.0 spec based on notes from the sprint; still very much wip https://docs.google.com/a/canonical.com/document/d/19ljAmIe3wVC-jpDRFl8KfvJKQzx0HIC0yuPu3cCMh7Q
[00:23] <menn0> wallyworld: having a quick look
[00:28] <menn0> wallyworld: looking good so far
[00:28] <menn0> wallyworld: I made a few tiny typo corrections
[00:29] <wallyworld> menn0: oh ty, didn't mean to burden you just yet with corrections :-)
[00:29] <menn0> wallyworld: I couldn't help myself :)
[00:29] <wallyworld> :-)
[01:11] <sinzui> wallyworld, Do you have minute to review http://reviews.vapour.ws/r/1497/
[01:12] <wallyworld> sure
[01:12] <wallyworld> sinzui: you always give me the difficult ones
[01:13] <sinzui> wallyworld, its an opportunity for you to say STOP, I have another issue that needs fixing
[01:14] <wallyworld> sinzui: i left off the :-)
[01:14] <sinzui> :)
[01:25] <sinzui> wallyworld, http://reports.vapour.ws/releases/2570 shows that 1.23.2  Passed every test, even against adverse dirty substrates and flakey vivid
[01:26] <wallyworld> yay
[01:26] <sinzui> This is could be the highest score ever gotten
[01:26] <wallyworld> now all we need is for 1.24 to do the same
[01:28] <wallyworld> let's hope it's reproducable then
[01:41] <axw> wallyworld: reviewed your branch
[01:41] <wallyworld> ty
[01:47] <wallyworld> axw: with the client facade, william didn't want to bump that beyond 0. the only other alternative is to introduce a whole new facade and stick the method on that. I started going down that path but couldn't decide on a suitable facade so took the path of least resistence (the branch was already big enough and i was trying to get it done in time before branching). given we already have AddMachinesV2, any proper refactoring work would
[01:47] <wallyworld>  have to sort out that stuff also, which is getting beyond the scope of removing a storage feature flag
[01:48] <axw> wallyworld: why does he not want to bump the version?
[01:50] <wallyworld> gets messy - we would need to fire up api servers for both 0 and the new version, and we want to ultimately move stuff off client anyway
[01:50] <wallyworld> we support uniter v 0, 1, 2, but that's a much smaller facade
[01:50] <wallyworld> i was trying to avoid depending on a charm repo change with the patching but i guess that's unavoidable :-(
[01:51] <wallyworld> and even with the uniter stuff, the tests are incomplete as it's hard to write common tests to cover all facade versions
[01:52] <wallyworld> s/hard/tedious due to code cut and paste
[01:55] <axw> wallyworld: can we at least hide this ugliness in api/client? so if the caller of AddMachines specifies storage, it calls AddMachinesV3 instead of V2
[02:25] <axw> wallyworld: not sure ify ou saw this before
 wallyworld: can we at least hide this ugliness in api/client? so if the caller of AddMachines specifies storage, it calls AddMachinesV3 instead of V2
[03:10] <wallyworld> axw: here's a patch to the charm repo to allow juju to patch the NewCharmStore from any package https://github.com/juju/charm/pull/123
[03:11] <axw> wallyworld: ?! why?
[03:11] <axw> where is this needed?
[03:12] <wallyworld> axw: to allow core tests to run - stuff in the apiserver/service package calls into methods in apiserver/client and the apiserver/client code calls NewCharmRepo and this needs to be patched. the apiserver/client package patches NewCharmRepo but you objected to tha being exposed to apiserver/service package
[03:13] <axw> wallyworld: I object to patching across packages in general, not that one case
[03:14]  * axw looks at code in question
[03:14] <wallyworld> so it's easier to just patch at the source of the charm repo creation instead of indirectly
[03:16] <wallyworld> axw: sadly we already patch charmrepo.CacheDir
[03:16] <wallyworld> so i'm at least lining up with what's done already
[03:17] <axw> yeah, I want to stop the sadness :)  I'm looking if there's a better alternative..
[03:17] <wallyworld> and the client code patches across packages anyway to patch charmrepo.NewCharmRepo
[03:17] <wallyworld> longer term, agreed. but this is simply to remove a feature flag to get 1.24 out
[03:18] <wallyworld> it's not introducing new badness
[03:18] <axw> wallyworld: service doesn't call into client, client calls into service
[03:18] <wallyworld> service calls s.APIState.Client().AddCharmWithAuthorization(curl, nil)
[03:18] <axw> client previously *internally* patched that function, which isn't great but at least doesn't spread the hack around
[03:18] <wallyworld> to set up a test
[03:18]  * axw looks again
[03:19] <axw> I see
[03:19] <wallyworld> yes it did, but any code can also patch cahrmrepo.CahedDir
[03:20] <wallyworld> this is a consequence of starting to move service apis off the client facade
[03:20] <wallyworld> and onto their own Service facade
[03:20] <wallyworld> there's a whole bunch of other service apis with todos to move
[03:21] <wallyworld> sadly, it we designed our code using inversion of control, this wouldn't be an issue, but we didn't :-(
[03:24] <axw> wallyworld: this can be fixed by changing apiserver/service to operate on interfaces rather than *state.State. getting out of scope, so please ditch the juju/charm change and use the original patch change and add a TODO(wallyworld)
[03:25] <axw> if we're adding hacks, let's at least confine them to juju/juju
[03:27] <anastasiamac> axw: wallyworld: on a different note, here is the start of dynamic add - http://reviews.vapour.ws/r/1498/
[03:49] <axw> anastasiamac: reviewing now
[03:49] <anastasiamac> axw: tyvm :D
[03:55] <axw> anastasiamac: done
[04:15] <wallyworld> axw: so, just to confirm you happy to retain the x-package patching as per what i submitted so that we don't have to modify charm.v5? that was my original thought and rationale also
[04:22] <wallyworld> axw: FFS, disconnected again, may have missed your reply
[04:48] <axw> wallyworld: sorry, was afk. yes.
[04:49] <axw> wallyworld: provided it gets replaced later with an interface and the cross-package patching removed
[04:51] <wallyworld> axw: yeah, there's a bit of work to do there. won't happen for 1.24 is suspect, best we can do is 1.25. i've updated the PR on RB
[04:51] <axw> looking
[05:28] <wallyworld> axw: i guess i should add a MachineManager facade and stuck the new AddMachine API on that. i was previously trying to avoid missing the 1.24 branching but given that's already happened, might be best not to introduce another lagacy API to have to support
[05:29] <axw> wallyworld: that would be ideal
[05:30] <wallyworld> yeah, agreed. sigh. branch already soo bg
[05:31] <axw> wallyworld: I already gave a shipit, you don't have to do it immediately
[05:31] <wallyworld> axw: ok, i'll land but then do an immediate followup
[05:31] <axw> cool
[05:39] <axw> wallyworld: is that a straight backport? do I need to review again?
[05:43] <mup> Bug #1449367 was opened: remove storage feature flag <juju-core:Triaged by wallyworld> <juju-core 1.24:In Progress by wallyworld> <https://launchpad.net/bugs/1449367>
[05:49] <mup> Bug #1449367 changed: remove storage feature flag <juju-core:Triaged by wallyworld> <juju-core 1.24:In Progress by wallyworld> <https://launchpad.net/bugs/1449367>
[05:55] <mup> Bug #1449367 was opened: remove storage feature flag <juju-core:Triaged by wallyworld> <juju-core 1.24:In Progress by wallyworld> <https://launchpad.net/bugs/1449367>
[07:07] <mup> Bug #1449390 was opened: storage: charms must wait for storage to be attached before running "install" hook <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1449390>
[09:02] <TheMue> voidspace: sorry for not being in hangout, have to help daughter
[09:03] <voidspace> TheMue: no problem
[09:03] <voidspace> TheMue: it's just you and me anyway :-)
[09:03] <voidspace> TheMue: I'm working on forward porting the addressable container feature flag to master
[09:03] <voidspace> TheMue: nearly done
[09:03] <voidspace> TheMue: hard work - just about none of the patch applied cleanly
[09:03] <voidspace> TheMue: only two more files to do though
[09:03] <voidspace> TheMue: that's my report :-)
[09:13] <mup> Bug #1449436 was opened: Environment variables are not propagated to jujud on vivid <juju-core:New> <juju-core 1.23:New> <juju-core 1.24:Triaged by axwalk> <https://launchpad.net/bugs/1449436>
[09:14] <TheMue> voidspace: so, "first aid" done, daughter has troubles with her car on the highway and asked what to do. and the other daughter is ill at home. :(
[09:15] <TheMue> voidspace: I'm currently writing a little conference report about last week, the continue with the process changes with Katherine, and will then take a look in the list Dimiter sent
[09:22] <voidspace> TheMue: ok
[09:25] <mup> Bug #1449436 changed: Environment variables are not propagated to jujud on vivid <juju-core:New> <juju-core 1.23:New> <juju-core 1.24:Triaged by axwalk> <https://launchpad.net/bugs/1449436>
[09:31] <mup> Bug #1449436 was opened: Environment variables are not propagated to jujud on vivid <juju-core:New> <juju-core 1.23:New> <juju-core 1.24:Triaged by axwalk> <https://launchpad.net/bugs/1449436>
[10:19] <axw> jam: gotta go, fix up for review here FYI -- http://reviews.vapour.ws/r/1500/
[10:19] <jam> axw: have a good night
[10:19] <jam> axw: I believe this should also go into 1.23, right?
[10:19] <jam> Since that is what we're actually releasing on V
[10:21] <Mmike> lads, when I bootstrap my env and then do 'juju ensure-availability', juju will fire up additional three units, set up replicaset for mongodb and all of that. Now when unit 0 dies (the initial bootstrap unit) I can't connect to my env any more. I need to manually change my environment.jenv file and remove references to machine 0 from there. Then juju works ok again. Now I want to remove machine 0 from juju, as it no longer exists, but juju won't let me
[10:21] <Mmike>  do so, saying: "ERROR no machines were destroyed: machine 0 is required by the environment".
[10:21] <Mmike> Is this by design, or am I doing something wrong?
[10:21] <Mmike> Using juju 1.22 currently, but observed same behaviour on 1.23
[10:22] <natefinch> hooooly shit.  just went to write a fake object to fulfill the CloudConfig interface, and umm.. it has over 60 functions :/
[10:29] <davecheney> that's no interface .... mother of god!
[10:29] <davecheney> Mmike: machine 0 is special, it cannot be removed
[10:30] <natefinch> luckily the function I need to mock it for only uses like 6 of those functions, so I can replace the interface with a more narrow one, but still, jeezus.
[10:31] <natefinch> davecheney, Mmike: you definitely should be able to kill machine 0 and have your environment still work fine.
[10:31] <natefinch> (when in HA)
[10:32] <natefinch> I don't know about actually tell juju to remove the phantom machine from its DB, but your environment should definitely still work.
[10:33] <jam> natefinch: seems a bit oversized. Though you can do ttype
[10:33] <jam> type MyFake struct { CloudConfig }
[10:33] <jam> and then only override the ones you actually want to
[10:33] <jam> (you'll get nil pointer dereference failures for anything that gets used that you didn't define)
[10:33] <jam> Mmike: so I'd like to walk through it a bit with you.
[10:33] <jam> After "juju ensure-availability" do you end up with 3 or 4 total machines?
[10:33] <jam> (I would expect 3)
[10:33] <jam> second, after those machines are up and running, you should be able to run "juju status", and connect to that env
[10:33] <jam> and then it will notice that there are more machines
[10:33] <jam> and record them as alternatives in your environments.jen
[10:33] <jam> It won't actually record new machines until they are up and running and connected (AIUI)
[10:33] <jam> but you shouldn't have to edit your JENV normally
[10:33] <jam> just you have to connect to the environment once the extra machines are running.
[10:33] <jam> Mmike: third, after machine-0 has died, you probably need to run "juju ensure-availability" again, where it should now notice that you have a dead machine, and try to take it out of official API server status
[10:33] <jam> (this is a bit of a wart, and we're looking at splitting up ensure-ha into more precise commands)
[10:33] <jam> and then you can "juju destroy-machine machine-0" (sp?)
[10:33] <jam> once it has lost its voting status
[10:34] <Mmike> jam: i see
[10:34] <Mmike> jam: let me try that
[10:35] <natefinch> jam: good idea embedding the interface in the struct
[10:50] <perrito666> morning all
[10:55] <Mmike> jam: where can I find the password jujud is using to connect to mongod?
[11:03] <jam> Mmike: you have to look on machine-0 for it, it should be in /var/lib/juju/agents/machine-0/agent.conf I think
[11:03] <jam> Mmike: sorry, looks like "/var/lib/juju/agents/machine-0.conf"
[11:05] <Mmike> jam: ack, thnx
[11:05] <perrito666> nope /var/lib/juju/agents/machine-0/agent.conf
[11:05] <perrito666> jam: unlest it changed
[11:05] <jam> perrito666: that's what I originally thought, but our backups test disagree
[11:06] <jam> perrito666: ./state/backups/files_test.go:114:              filepath.Join(s.root, "/var/lib/juju/agents/machine-0.conf"),
[11:06] <Mmike> jam: actually on 1.22 it's in  /var/lib/juju/agents/machine-0/agent.conf
[11:06] <Mmike> just verified
[11:06] <perrito666> jam: ill remember to ping eric on that one
[11:07] <jam> perrito666: k. That sounds suspiciously like its a bad test.
[11:08] <jam> perrito666: but "cmds/juju-restore" does use /var/lib/juju/agents/machine-0/agent.conf
[11:08] <perrito666> jam: it is
[11:08] <perrito666> jam: looking at the code that it is testing it does not really matter since that seems the result of faking a glob result
[11:08] <perrito666> but is missleading
[11:09] <jam> perrito666: yeah, I'm not saying the test doesn't pass, but we shouldn't have incorrect paths in a backup test :)
[11:09] <perrito666> I have opened and restored that files enought times to know it is named agent.conf :p
[11:09]  * perrito666 makes a note for a less urgent time
[11:10] <jam> perrito666: :)
[11:10] <jam> yeah, I would guess you did
[11:17] <dimitern> voidspace, ping
[11:34] <jam> Mmike: did you get things to work?
[11:34] <Mmike> jam: nope, not yet, my openstack deploy is a bit slow as I'm testing some other stuff too, so it takes time...
[11:34] <jam> Mmike: np
[11:35] <jam> just curious
[11:35] <Mmike> jam: yup, have a case about that, so I need to know how it works
[11:35] <Mmike> and for convenience too :)
[11:37] <dimitern> fwereade, http://reviews.vapour.ws/r/1501/
[11:38] <jam> dimitern: is it actually allowed to start with - or _
[11:38] <jam> ?
[11:38] <dimitern> jam, it is in fact
[11:39] <dimitern> jam, rvba just confirmed that
[11:40] <jam> dimitern: is there any reason not to be slightly more restrictive than them?
[11:40] <jam> I think avoiding opening "-" is probably a good thing
[11:40] <dimitern> jam, apart from another critical blocker from OIL
[11:40] <dimitern> can't think of one :)
[11:41] <dimitern> in case they now decide to have names like "-my_NET"
[11:41] <fwereade> dimitern, jam: so the core of the problem is that we use provider ids as network names
[11:42] <fwereade> dimitern, jam, which means we need to come up with a regexp that matches every possible valid provider network id
[11:42] <dimitern> fwereade, jam, yeah, that's the crux of it; but it's much harder to fix it properly
[11:42] <fwereade> dimitern, jam, but is still somehow useful
[11:42] <dimitern> fwereade, jam, also, fwiw this only applies to maas anyway now
[11:44] <fwereade> dimitern, jam: with that patch, can we still transform name<->tag safely?
[11:44] <fwereade> dimitern, jam: and can we depend on correctly munging globallKeys?
[11:44] <dimitern> fwereade, jam, yes - there are tests for that in fact, which didn't stop passing, and we don't allow /
[11:44] <jam> or # right?
[11:44] <dimitern> yeah
[12:04] <Mmike> jam: so, here is what I did: juju bootstrap; juju ensure-availability. Then I did 'juju status' until I had all three machines with "state-server-member-status: has-vote". Then I deployed some service (percona-cluster, with 3 units).
[12:05] <Mmike> Waited for that service to settle down, verified all is ok.
[12:05] <Mmike> After that I killed the machine 0 (as this is openstack, I did nova delete $instance_id). Did juju status after that, waited for like 2-3 minutes, and then juju status returned status with machine0 being down.
[12:05] <Mmike> Also, some percona-cluster units where shown as 'agent-state: down'.
[12:05] <jam> Mmike: 2-3 minutes sounds odd to me
[12:06] <jam> Mmike: one option is to use "juju status --verbose" (-v) which should have it report what its trying to do
[12:06] <jam> is it still 2-3 min per status?
[12:06] <jam> or is status fast now?
[12:07] <Mmike> Then I did juju ensure-availability, juju instantiated another machine. Waited for that one to have 'state-server-member-status: has-vote'. Then did: "juju destroy-machine 0", but juju complained about 'machine 0 being needed for the env'
[12:07] <Mmike> no, it is fast now
[12:07] <Mmike> just the first run after I killed machine 0 was slow.
[12:08] <Mmike> ok, now all of my percona-cluster units are up, and marked ok (no more 'agent-state: down').
[12:08] <Mmike> But I still can't remove machine 0.
[12:09] <jam> Mmike: can you pastebin the "juju status" output ?
[12:09] <Mmike> sure
[12:10] <Mmike> jam: http://pastebin.ubuntu.com/10924694/
[12:10] <Mmike> jam: I can paste whole termlog from the first bootstrap, if needed
[12:11] <jam> Mmike: so i *believe* that now that machine-0 has been removed from voting, you can do another "juju ensure-availability" and it will be removed as a state server entirely, and then you can "juju destroy-machine machine-0"
[12:12]  * Mmike tries
[12:12] <jam> I think each transition needs another ensure-availability call. starts with has-vote, then goes to no-vote, then goes to no-longer-a-state-server
[12:13] <Mmike> jam: ack, confirmed.
[12:13] <Mmike> jam: excellent! :)
[12:13] <Mmike> jam: thank you very much
[12:13] <Mmike> just one more, though
[12:13] <Mmike> so let's say I had 3 state machines. One of them died. Then another died. Now mongodb on remaining unit is in readonly state.
[12:14] <Mmike> I don't have juju backup.
[12:14] <Mmike> I'm thinking, then, connecting to the remaining machine, and 'reseting' mongodb - forcing it to become primary again.
[12:14] <Mmike> Will that work? That is, will I be able to use juju afterwards?
[12:14] <Mmike> (Havent tried, just curious)
[12:15] <jam> Mmike: so if you manually poke the replicaset document in mongo
[12:15] <jam> you should be able to do anything you want :)
[12:15] <jam> just don't do it wrong.
[12:15] <jam> obviously with db surgery you can make anything work. I'm not 100% sure how much Juju would let you get away with, because it will likely try to write the replicaset document to match its own state
[12:16] <Mmike> well, obviously the 'right thing to do' is to have backups.
[12:17] <Mmike> But, there being only two kinds of people in the world... sooner or later I'll have to deal with 'we WILL be doing backups' kind of people :)
[12:17] <Mmike> jam: thnx for the inputs, will try breaking my env later again to verify if poking with mongo will bring it back to life
[12:18] <jam> Mmike: have you verified that Juju becomes completely unhappy with 2 machines down?
[12:18] <jam> It is *possible* that "juju ensure-availability" would rewrite things to try and get back into 3-man mode.
[12:18] <jam> but I can entirely believe that we didn't get there.
[12:18] <jam> And IIRC, we don't support "juju ensure-availability -n1" to get back out of HA mode
[12:19] <Mmike> jam: nop, tbh. But I know from previous mongodb experience that if two nodes go down the last remaining node is in read-only, as it has no quorum.
[12:19] <jam> Mmike: but being able to get a DB backup at that point seems *really useful*
[13:05]  * perrito666 uses deployer for the first time ever
[14:02] <katco> natefinch: standup
[14:03] <aznashwan> natefinch: ping
[14:04] <natefinch> aznashwan: sup?
[14:13] <aznashwan> natefinch: sorros
[14:13] <aznashwan> natefinch: got distracted
[14:14] <aznashwan> natefinch: could give me an idiot's guide to using that perl script for syscalls on windows?
[14:15] <aznashwan> natefinch: (if you could exemplify on your npipe package what the result should be; that would be awesome)
[14:50]  * perrito666 drops a bucket of debug messages onto deployer
[14:55] <natefinch> aznashwan: all I really did was look at the files in the syscall stdlib and copy what they did there.  The zsyscall_* files give the command line to use, and show the input file, which contains the patterns that generate the syscalls in comments at the top of the file.
[14:55] <natefinch> aznashwan: I meant to write a blog post about how to do it back when I wrote npipe, but never got around to it. I should brush up on it and do so, it would be pretty useful, I think.
[14:59] <voidspace> dimitern: just FYI, I merged the tests as well
[14:59] <voidspace> dimitern: that was easier
[14:59] <voidspace> dimitern: I have a bunch of failing tests to fix now
[15:00] <voidspace> dimitern: not all obvious, but I'll work through them
[15:01] <dimitern> voidspace, sweet!
[15:05] <voidspace> dimitern: hey, we have a test "TestNewCloudInitConfigNoFeatureFlag"
[15:05] <voidspace> dimitern: testing maas config generation
[15:05] <voidspace> https://github.com/juju/juju/compare/master...voidspace:addressable-featureflag
[15:05] <mattyw> jam, are you around this week?
[15:05] <voidspace> (the first s.SetFeatureFlags() in that branch is spurious I assume - and I've removed it locally)
[15:06] <voidspace> dimitern: the intent of the test seems to be to test we get the same config with feature flag on and off
[15:06] <voidspace> dimitern: but we don't
[15:06] <voidspace> dimitern: we get the juju-br0 stuff when the flag is off
[15:06] <jam> mattyw: I'm around
[15:06] <voidspace> dimitern: so the test seems flawed (and is failing for this reason)
[15:06] <jam> though its EOD for me now
[15:07] <mgz_> dimitern: I failed to find you in person, but can I have a review please? :)
[15:07] <mgz_> dimitern: https://github.com/go-goose/goose/pull/8/files
[15:08] <mup> Bug #1449613 was opened: service/windows is missing unit tests. <juju-core:New> <juju-core 1.23:New> <juju-core 1.24:New> <https://launchpad.net/bugs/1449613>
[15:20] <mgz_> katco: can I wave bug 1447841 at you?
[15:20] <mup> Bug #1447841: eu-central-1 AWS region V4 signing required and not supported <ec2-provider> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1447841>
[15:24] <katco> mgz_: sure tal
[15:25] <katco> mgz_: should be an easy fix
[15:27] <natefinch> perrito666: review please? http://reviews.vapour.ws/r/1504/
[15:32] <mup> Bug #1449617 was opened: service.Service implementations are missing functional tests. <juju-core:New> <juju-core 1.23:New> <juju-core 1.24:New> <https://launchpad.net/bugs/1449617>
[15:33] <perrito666> natefinch: reviewed, just one issue
[15:35] <dimitern> vo
[15:35] <katco> mgz_: very small review for that bug: http://reviews.vapour.ws/r/1505/
[15:35] <dimitern> voidspace, hey
[15:36] <mgz_> pants, we have in fact not yet switched to gopkg.in goose yet
[15:37] <dimitern> voidspace, why is that happening can be gnarlly - check basically jujuconnsuite's setupsuite and setuptest - there might be something overriding the set FF
[15:38] <mgz_> katco: change lgtm - no tests need updating? also, s3 auth works with the same auth object as ec2 okay?
[15:38] <mgz_> I'm confident our testing will fail fast if anything is wrong
[15:39] <katco> mgz_: yeah s3 defaults to v4, we deprecated v2 signing for s3
[15:39] <katco> mgz_: i haven't run tests, let me do that rq for just the ec2 provider package
[15:40] <katco> mgz_: those tests pass. i'll try and land and see what happens
[15:43] <alexisb> ericsnow, as always thank you!
[15:44] <mup> Bug #1449633 was opened: Cannot terminate/remove broken state server after ensure-availability <cts> <juju-core:New> <https://launchpad.net/bugs/1449633>
[15:46] <mgz_> should we be sorting external import alphanum-wise? what can I use to do that?
[15:47] <mgz_> hm, seems not, I have github.com and gopkg.in both ways round
[15:49] <natefinch> mgz_: go fmt will alphabetize
[15:50] <natefinch> mgz_: it sorts each section independently (where a section is delimited by blank lines)
[15:55] <natefinch> perrito666: thanks
[15:55] <perrito666> np
[15:56] <mup> Bug #1449633 changed: Cannot terminate/remove broken state server after ensure-availability <cts> <juju-core:New> <https://launchpad.net/bugs/1449633>
[15:58] <mgz_> natefinch: yeah, I was wondering about sorting the blocks after that - which we seem not to do
[16:01] <natefinch> mgz_: go fmt definitely sorts all the blocks... try it out here:  http://play.golang.org/p/lb4Nc0Nz2B  the blocks are intentionally out of order to start
[16:02] <mup> Bug #1449633 was opened: Cannot terminate/remove broken state server after ensure-availability <cts> <juju-core:New> <https://launchpad.net/bugs/1449633>
[16:02] <katco> perrito666: hey do you need any help with 1441826?
[16:03] <perrito666> katco: I think I just nailed it :)
[16:04] <katco> perrito666: course you did... bc you're AWESOME ;p
[16:04] <natefinch> perrito666: nice
[16:04] <perrito666> I am writing the patch now to see if it works, but apparently its a shim missing in the multiwatcher status
[16:16] <mgz_> ocr: can I request another review on http://reviews.vapour.ws/r/1473/
[16:17] <mgz_> I needed to bump goose version (and location) to add a test)
[16:21] <perrito666> mm, that is a nasty thing to read on reviewboard
[16:22] <mgz_> perrito666: blame Ian
[16:22] <perrito666> ok
[16:22] <perrito666> git blame ian
[16:22] <mgz_> it was a nice clean change till I had to update all the imports
[16:23]  * perrito666 impatiently awaits for his stream to update
[16:23]  * perrito666 reads in github and gets a pill for the headache
[16:24] <mgz_> perrito666: looking at each commit in turn may be more informative
[16:25] <perrito666> mgz_: do you arrange your tests in lexicographic order?
[16:29] <mgz_> perrito666: I arrange them in random walk order
[16:31] <perrito666> mgz_: brb, will review upon return,  I promise
[16:32] <mgz_> perrito666: no problem
[16:32] <mgz_> I'm off for now at least
[16:34] <aznashwan> natefinch: sorry; got carried away again...
[16:34] <natefinch> aznashwan: did you see my prior responses?
[16:35] <aznashwan> natefinch: figured it out; it's quite handy
[16:35] <aznashwan> natefinch: yes I did
[16:35] <natefinch> aznashwan: ahh cool. Yeah. it's nice.
[16:35] <aznashwan> natefinch: I used the go one in the syscall package
[16:35] <aznashwan> natefinch: they should really raise awareness for it
[16:36] <natefinch> aznashwan: yeah, I remembered they added a go version finally... after I had to struggle with installing perl on windows ;)
[16:36] <aznashwan> natefinch: oh; it's yours?
[16:36] <aznashwan> natefinch: Windows salutes you :D
[16:37] <natefinch> aznashwan: no no... I was sorely tempted to port it, but never found the time.  Not sure who did, but not me :)
[16:39] <aznashwan> natefinch: works great; but there was a lot a lot of guesswork involved in figuring out how to use it for procs' that weren't in kernel32
[19:10] <katco> perrito666: how is the bug coming?
[19:11] <perrito666> katco: fixed It looks, fixing the tests now
[19:11] <katco> perrito666: awesome :)
[19:14] <perrito666> mmpf I am pretty sure network manager indicator has less functions than before :( I dont seem to be able to priorize my connections
[19:59] <perrito666> talk about useful test failure errors
[19:59] <perrito666> Error: entity mismatch; got len 1; want 1
[20:05] <natefinch> perrito666: heh wow
[20:09] <katco> natefinch: hey is https://bugs.launchpad.net/juju-core/+bug/1446871 landed yet?
[20:09] <mup> Bug #1446871: Unit hooks fail on windows if PATH is uppercase <ci> <hooks> <windows> <juju-core:In Progress by natefinch> <juju-core 1.24:In Progress by natefinch> <https://launchpad.net/bugs/1446871>
[20:11] <natefinch> katco: I hadn't thought it was targetted at 1.24-alpha1, so I just have a PR up against master, which is blocked... but I could easily put it on 1.24 instead
[20:11] <natefinch> katco: so, no :)
[20:12] <katco> Nate looks like it's just targeted against 1.24
[20:12] <katco> natefinch: mgz was working on https://bugs.launchpad.net/juju-core/1.24/+bug/1441826 but it's past his EoD... we're blocked until that is complete
[20:12] <mup> Bug #1441826: deployer and quickstart are broken in 1.24-alpha1 <api> <blocker> <ci> <deployer> <quickstart> <regression> <juju-ci-tools:Triaged> <juju-core:Triaged by hduran-8> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1441826>
[20:13] <katco> natefinch: looks like you might have had some insight there, so if you are blocked, it would be a good thing to look into
[20:13] <natefinch> katco: I can certainly look at that one, though I thought perrito666 had that one handled
[20:14] <katco> natefinch: i thought he was looking at https://bugs.launchpad.net/juju-core/+bug/1441826?
[20:14] <mup> Bug #1441826: deployer and quickstart are broken in 1.24-alpha1 <api> <blocker> <ci> <deployer> <quickstart> <regression> <juju-ci-tools:Triaged> <juju-core:Triaged by hduran-8> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1441826>
[20:14] <katco> gah... stupid copy/paste mistake
[20:14] <perrito666> katco: you have a problem with your pastebin?
[20:14] <katco> haha
[20:14] <perrito666> you sound just like the error I pasted a moment ago
[20:14] <katco> natefinch: i meant https://bugs.launchpad.net/juju-core/+bug/1440940
[20:14] <mup> Bug #1440940: xml/marshal.go:10:2: cannot find package "encoding" <blocker> <ci> <regression> <test-failure> <juju-core:In Progress by gz> <juju-core 1.24:Triaged> <juju-release-tools:In Progress by gz> <https://launchpad.net/bugs/1440940>
[20:14] <natefinch> oh yeah that one
[20:14] <katco> natefinch: perrito666 is definitely working the other one
[20:15] <katco> natefinch: but mgz thought he had a fix, but apparently not
[20:15] <natefinch> katco: I'll look through what has been posted there since I last looked at the bug.
[20:15] <katco> natefinch: cool ty
[20:15] <katco> wwitzel3: are you blocked on 1326091?
[20:20] <natefinch> sinzui: you around?
[20:20] <sinzui> I am
[20:20] <natefinch> in the above bug about encoding, one of your recent messages contains a typo that makes it hard for me to understand: "The release tarfile but contain the encoding src or pkg, or we avoid using github.com/juju/govmomi/vim25/xml."
[20:21] <sinzui> natefinch, *must*
[20:21] <natefinch> sinzui: ahh, ok, I couldn't figure out what it was supposed to be
[20:22] <sinzui> natefinch, mgz advised that including the encoding package in the source tree would ensure gccgo found the package. He reported it was fixed but is not. The packages don't build and I don't see the package, so I don't know what mgz changed to lead him to believe the issue was fixed
[20:22] <sinzui> damn, too many uses of the word packages
[20:23] <sinzui> We cannot make debs, and I don't see "encoding" in src/
[20:25] <natefinch> sinzui: it seems odd to me that we package up the standard library in our tarfile. shouldn't the standard library just be installed on the target machine, and we just tar-up what's outside the stdlib?  I presume ubuntu doesn't build other languages by including the stdlib in the tar we give the builders.
[20:26] <natefinch> (and I'm using a very broad version of "installed" .... I don't actually care how it arrives on disk)
[20:27] <sinzui> natefinch, it seem odd to me we would fork xml and use it without checking it worked on all arcs
[20:27] <sinzui> regardless, *we* are obligated to deliver a tarball that Ubuntu and Lp can build ppc64el debs. so need to provide a version of encoding that work with that xml package
[20:29] <natefinch> sinzui: I guess my question would be...  why isn't the entire go std library on the builder?  Is it because there's no golang package we can apt-get install for PPC64el that we don't do it that way?
[20:30] <sinzui> natefinch, Ubuntu/debian uses shared lib and they are already built and distributed for Juju to link too
[20:30] <sinzui> natefinch, juju is *not* 100% static for ppc. it uses golib5
[20:30] <natefinch> sinzui: I don't know what that is, unfortunately.
[20:31] <sinzui> natefinch, a lib that doesn't have encoding in it, at least, not by that name
[20:32] <natefinch> sinzui: where do we get golib from?  google isn't being very helpful for me there
[20:32] <sinzui> well I can see there is an encoding, but it doesn't match what the xml package wants :(
[20:32] <sinzui> natefinch, I think you are taking the wrong path here
[20:33] <sinzui> natefinch, We will not release any 1.24 version in the next month if we are trying to bet debian/ubuntu to change packages. mgz's solution is to include just what is needed to satisfy debian packaging rules
[20:34] <natefinch> sinzui: we're getting an error that should be impossible.  The most likely reason is because we're doing things in weird ways to satisfy people's ideas of the way things should be built.  I'm just trying to figure out how this builder differs from what happens when I run gccgo.
[20:34] <natefinch> sinzui: if I can't look at golib, I can't figure out why its encoding is different
[20:34] <natefinch> sinzui: or how to fix it
[20:35] <natefinch> (it/us/whatever)
[20:36] <sinzui> natefinch, https://launchpad.net/ubuntu/+source/gccgo-go
[20:37] <sinzui> natefinch, I think trusty used http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gccgo-go/trusty-proposed/files
[20:38] <sinzui> natefinch, but you are entering into packaging and linking in debian/gccgo which is not like golang
[20:40] <natefinch> sinzui: so, I do see the encoding directory and encoding.go under src/pkg: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gccgo-go/trusty-proposed/files/head:/src/pkg/encoding/
[20:41] <sinzui> natefinch, yes, we established that a few weeks ago
[20:43] <sinzui> natefinch, the recent change here is that go build to make packages was working, now it doesn't So the hack to create a goroot on the test machines wont work in the clean-room env used by builders
[20:50] <natefinch> sinzui: I'm more than willing to help, and I'm sorry if I get frustrated.  There's a lot of the packaging part, especially for gccgo, that I still don't know well, so trying to figure out why something is going wrong is difficult without preloading a lot of knowledge.
[20:50] <katco> natefinch: sinzui: it seems extraordinarily hazardous to me that we would patch the go stdlib to include an entire package
[20:50] <katco> natefinch: sinzui: seems like we could get unexpected behavior quite easily, doesn't it?
[20:51] <natefinch> katco: we forked the xml package.  I would not say we were patching the std lib at all.   we copied the xml package to github.com/juju/xml and reference it as a normal 3rd party package
[20:51] <natefinch> katco: the problem seems to be that we're using any package that itself depends on the encoding package.
[20:51] <katco> natefinch: that doesn't have a dependency graph that spiders out into other parts of the go stdlib?
[20:52] <natefinch> katco: it should be exactly the same as if we just imported the xml package
[20:52] <sinzui> natefinch, I found 3 changes between the the time we could make packages and when we couldn't mgz made two of them https://bugs.launchpad.net/juju-core/+bug/1440940/comments/15
[20:52] <mup> Bug #1440940: xml/marshal.go:10:2: cannot find package "encoding" <blocker> <ci> <regression> <test-failure> <juju-core:In Progress by gz> <juju-core 1.24:Triaged> <juju-release-tools:In Progress by gz> <https://launchpad.net/bugs/1440940>
[20:53] <katco> natefinch: well, what i'm getting at is we're using version X of the xml package with version Y of the rest of the go stdlib
[20:53] <katco> natefinch: and i'm wondering if that might introduce unintended consequences
[20:54] <natefinch> katco: it shouldn't matter, because the only code using our XML package is code we specifically wrote to use it.  It should either compile on all platforms or not.
[20:54] <katco> natefinch: compilation =/= proof of correctness
[20:54] <natefinch> katco: but if the problem is a compilation error....
[20:54] <katco> natefinch: this particular problem; i'm questioning the larger strategy
[20:55] <sinzui> natefinch, the xml package *did* compile a week ago. When only tests were broken I assumed it was test-double nonsense from gccgo
[20:55] <natefinch> katco: it's really conceptually no different than forking any other package and using it instead of the original.  the stdlib isn't special, it's just normal go code.
[20:56] <katco> natefinch: correct, but the version of the xml package we've imported was written to depend on perhaps a different version of the go stdlib
[20:56] <katco> natefinch: what i'm getting at is: we're mucking with dependencies in a very non sustainable way
[20:57] <natefinch> katco: there's no version of the stdlib that doesn't have the encoding package, though
[20:57] <natefinch> katco: also, the stdlib is guaranteed backwards compatible to go1.0 and they're very strict about it
[20:58] <natefinch> I think looking at sinzui's list of commits that might have broken it is a good way to tackle the problem.  IN theory, something should stand out.
[20:58] <katco> natefinch: from a signature perspective... not implementation
[20:58] <katco> natefinch: this line of questioning is probably irrelevant at this point, i'll drop it
[20:59] <natefinch> sinzui: is it possible to re-run the last test that worked?  To rule out environmental / process changes?
[20:59] <katco> natefinch: but wow will this get messy fast
[21:00] <natefinch> sinzui, katco: unfortunately, I'm at EOD.  I may be able to get online significantly later (9pm-ish eastern), but may not, depending on the state of my kids.
[21:00] <katco> natefinch: hope everyone feels better, and hope the appt. went well today
[21:00] <natefinch> I think it's worth going through the code changes to look for things that stand out ,and also doing a double check to make sure that the last run that worked still works.
[21:00] <natefinch> katco: thanks
[21:01] <sinzui> natefinch, not in CI since the job is publishing. But in this case, this is the actual packaging rules. anyone can take the  release tarball, make a source package from the packaging branch, and then build it (on ppc
[21:01] <sinzui> )
[21:02] <sinzui> natefinch, note that building happens in fakeroot, so changes cannot just happen
[21:02] <natefinch> *nod*
[21:02] <natefinch> ok, gotta run, sorry.  Will try to be back on later.  I'll take a look at the changelists and possibly the tarballs themselves to see if I can figure out what's going on.
[21:04] <natefinch> oh, one hack to fix it might just be to do an unnecessary import "encoding"  from somewhere under github.com/juju/juju so we force that it gets included in the tarball
[21:23] <wwitzel3> katco: no, it isn't blocked
[21:24] <katco> wwitzel3: k ty
[21:36] <menn0> wallyworld: ping?
[22:48] <mup> Bug #1449277 changed: juju environment create fails on aws: invalid config <juju-core:Invalid by waigani> <juju-core 1.24:Invalid by waigani> <https://launchpad.net/bugs/1449277>
[22:57] <perrito666> so http://reviews.vapour.ws/r/1508/ and http://reviews.vapour.ws/r/1509/ Fix lp1441826 in 1.24 and master respectively, who would be so kind? wallyworld ?
[22:57] <perrito666> katco: ?
[22:57] <perrito666> ill go get some dinner and then come back
[23:23] <ericsnow> could I get a review on http://reviews.vapour.ws/r/1510/?
[23:23] <ericsnow> it's the fix we talked about on the call (build constraints for vsphere provider)
[23:28] <ericsnow> it should be super easy to review
[23:29] <perrito666> famous last words
[23:41] <wallyworld> ericsnow: looks like there's additional unrelated changes in that diff
[23:42] <ericsnow> wallyworld: ah, that's just RB doing its thing (I'll fix)
[23:43] <ericsnow> fixed
[23:44] <wallyworld> looking again
[23:44] <wallyworld> ericsnow: what does the newly added init_gccgo do?
[23:45] <ericsnow> wallyworld: makes it so I don't have to touch provider/all/all.go :)
[23:46] <ericsnow> wallyworld: (allows import of "github.com/juju/juju/provider/vsphere")
[23:46] <ericsnow> wallyworld: I'll add a note to that effect
[23:56] <ericsnow> wallyworld: good to go? (I'm going AFK in a minute)
[23:57] <wallyworld> ericsnow: bah, i got disconnected again, i asked a quesion - what does the newly added init_gccgo do?
[23:58] <ericsnow> wallyworld: yep, and I responded :)  I've added a comment explaining (allows imports of the package to continue to work)
[23:58] <wallyworld> sorry, didn't see
[23:58] <ericsnow> np :)
[23:59] <wallyworld> ericsnow: lgtm, ty
[23:59] <ericsnow> wallyworld: thanks


[14:50] <mup> Bug #2041854 opened: maas config-vault  migrate failed due to region not restarting <systemtests> <MAAS:Triaged> <https://launchpad.net/bugs/2041854>
[14:56] <mup> Bug #2041854 changed: maas config-vault  migrate failed due to region not restarting <systemtests> <MAAS:Triaged> <https://launchpad.net/bugs/2041854>
[15:02] <mup> Bug #2041854 opened: maas config-vault  migrate failed due to region not restarting <systemtests> <MAAS:Triaged> <https://launchpad.net/bugs/2041854>
[15:05] <mup> Bug #2041854 changed: maas config-vault  migrate failed due to region not restarting <systemtests> <MAAS:Triaged> <https://launchpad.net/bugs/2041854>
[15:08] <mup> Bug #2041854 opened: maas config-vault  migrate failed due to region not restarting <systemtests> <MAAS:Triaged> <https://launchpad.net/bugs/2041854>