[01:52] <wallyworld> babbageclunk: can haz small review at some stage when you are free? no rush https://github.com/juju/juju/pull/8739
[01:53] <babbageclunk> wallyworld: yup, looking now
[02:04] <babbageclunk> wallyworld: approved
[02:05] <wallyworld> yyay ty
[03:27] <_thumper_> proxies suck
[03:27] <_thumper_> just sayin
[07:06] <manadart> jam externalreality: In the HO.
[10:43] <manadart> Anyone able to take a look at https://github.com/juju/juju/pull/8736 ? It is small.
[10:46] <stickupkid> manadart: looks good to me.
[10:47] <manadart> stickupkid: Ta.
[11:51] <srihas> hi guys, the space "aci" which is passed as 'juju deploy neutron-openvswitch --bind "data=aci" ' should have DHCP enabled?
[12:17] <srihas> how can I remove a subordinate service that has "hook failed: install" status in juju 2.3
[12:17] <srihas> ??
[12:45] <manadart> Another PR for review: https://github.com/juju/juju/pull/8740/files - mostly mechanical.
[13:26] <stickupkid> manadart: i added a quick comment to the PR...
[13:28] <srihas> thank god, --no-retry saved me
[13:40] <manadart> stickupkid: Ta.
[21:15] <thumper> bugger...
[21:15] <thumper> simon's gometalinter patch causes all the CI unit tests to fail
[21:19] <veebers> thumper: ah, because gometalinter is not installed :-\
[21:20] <thumper> veebers: yeah, I emailed the crew asking if it should be added to the makefile or just the jenkins jobs
[21:20] <veebers> thumper: we can either update the jobs to install it as part of the process, or add it to the make file
[21:20] <veebers> hah
[21:20] <rick_h_> No, the linter was put in make check with what's already being run
[21:20] <thumper> rick_h_: where?
[21:20] <rick_h_> I know simon checked on that and already updated the makefile for make check to add the linting
[21:20]  * rick_h_ is looking
[21:20] <thumper> rick_h_: clearly it isn't working
[21:20] <veebers> rick_h_: installing the linter, not running it
[21:21] <rick_h_> ah, installing it...good question.
[21:21] <veebers> running the linter is there (that's what's causing the error). It needs to be installed
[21:21] <rick_h_> I guess I assumed it would be part of updating deps but ... guess not
[21:27] <thumper> how are users expected to install gometalinter?
[21:27] <thumper> it would have been good to get an email to the crew about the addition if it was going to cause problems
[21:27] <thumper> or even the juju email list
[21:31] <veebers> hindsight is 20/20 :-)


[06:58] <prabhu> how to upgrade from 10.10 to 11.04
[07:09] <joschi> prabhu: follow the instructions on http://www.ubuntu.com/testing/natty/alpha1
[07:10] <joschi> prabhu: but don't expect everything to be working
[07:13] <prabhu> oki
[07:13] <prabhu> okay


[01:34] <rkota> cjwatson, thanks. Do you know of a way to "move" a bug  from one proprietary project to the other ?
[01:35] <wgrant> rkota: You should just be able to expand the row on the bug page and change the project name.
[01:35] <wgrant> Same as any other bug.
[01:35] <wgrant> Or indeed click the edit icon next to the project name.
[01:35] <rkota> wgrant, ah, leme try
[01:36] <rkota> wgrant, nice! Thanks Much!
[06:28] <Enrico_Menotti> Hello. I'm new to Ubuntu and Launchpad, but I have some experience with Debian. I'm trying to find info about ppa's. From add-apt-repository manual, when the <repository> is specified as ppa:<user>/<ppa-name> it is expanded to its full deb line. What is the rule for the expansion? I mean, how may I get the deb line by just knowing <user> and <ppa-name>? I'm googling for this, but so far didn't find a clear
[06:28] <Enrico_Menotti>  explanation.
[07:19] <wgrant> Enrico_Menotti: You can see the PPA's repository URL by expanding the "Technical details about this PPA" section on its launchpad.net page, but the pattern is http://ppa.launchpad.net/USER/PPA/ubuntu
[15:41] <Enrico_Menotti> wgrant Thanks!


[00:00] <Pricey> Have I gotten my times mixed up?
[00:00] <Pricey> bluekuja: apologies, got mixed up.
[00:00] <bluekuja> np
[00:00] <bluekuja> see ya
[00:00] <bluekuja> leaving
[00:00] <bluekuja> have a good night
[02:34] <Flannel> Anyone know anything about Severity's bot?  Severity-Logging
[02:40] <elky> Flannel, it looks spanking new as of today
[02:40] <elky> its nick isn't registered and it only has one entry in whowas
[02:51] <Flannel> Looks like 3.5 finally made it to updates.
[02:52] <Flannel> I've seen some bad info on how to make it default though.  Some mozillateam guy basically removed the entire FirefoxNewVersion wikipage, and inserted stuff that only covers Jaunty/3.5
[02:52] <Flannel> just overwriting the symlink is wrong, correct?  Need to dpkg-divert first?
[02:53] <Flannel> That is, to make /usr/bin/firefox point to 3.5
[02:58] <Flannel> thanks Pici
[02:58] <Pici> np
[02:59] <elky_work> Flannel, might be worth conferring with the developers
[03:00] <Flannel> dpkg-divert makes it so you don't step on the toes of the package manager, it renames the file as far as dpkg is concerned, so you can recreate it manually.
[03:00] <Flannel> This was in the old FNV wiki (which I really don't think should've been removed entirely, since the new one is way too special case)
[03:01] <Flannel> But yeah.  Was just hoping someone else could confirm
[03:06] <elky> Flannel, has the *matix stuff not taught you anything? we need dev sayso before what we say counts for anything as far as the dodgy-advice-givers are concerned
[03:06] <Pici> Why not ask in #ubuntu-mozillateam ?
[03:06] <Flannel> well, unfortunately the mozilla channel is apparently (second/third hand) the ones saying to just link it
[03:06] <Flannel> Pici: because their advice is raising red flags in my head
[03:07] <Flannel> Some of it at least
[03:07] <Pici> Who?
[03:07] <Flannel> I don't know, we could check logs.  Give me a sec
[03:09] <elky> which means you go to a Core Dev
[03:13] <Flannel> Hmm
[03:16] <Flannel> Alright, seems my LoCo member just extrapolated incorrectly (not surprising).  Official stance is "change the link" which doesn't mean simply ln, but would also include the divert I believe
[03:19] <Flannel> actually, seems preferred way is: "set firefox-3.5 %s in gnome -> preferences -> preferred applications", which should work for "most use cases"
[03:24] <bazhang> floodbotk1 does not seem to check ident
[03:27] <elky> Flannel, that doesn't solve the wiki issue though
[03:27] <Flannel> elky: Indeed.
[03:27] <Flannel> In my opinion, wiki should be reverted to prior edits, and then this stuff added in.
[03:28] <elky> Flannel, poke asac if it wasnt him who did the edit
[03:28] <Flannel> since that other stuff needs to exist for older versions of Ubuntu, and also in X months when firefox 84.0 comes out and someone wants to upgrade
[03:29] <Flannel> Andrew Sayers... probably asac, although his nick isn't on LP
[03:30] <Flannel> Hmm, maybe not.  Not in mozilla team.
[03:30] <elky> no, asac is alexander sack or something of the like
[03:31] <elky> https://launchpad.net/~asac like so
[04:23] <bazhang> severity-logging , according to severity1, is simply his work irc account; he has a bot sevbot , but will ask before any further actions related to Ubuntu channels
[04:32] <elky> bazhang, i assume you suggested that a nick change would be nice
[04:32] <bazhang> elky, for namelezz or severity-logging?
[04:34] <elky> severity-logging
[04:34] <bazhang> no; he explained what it was. If you wish I can ask him
[04:36] <elky> explain that it gives the wrong impression and severity-work or severity-backup would be far less encouraging to people who'd take it as a 'he gets bots, so i should too' invitation
[04:37] <bazhang> am doing so now elky just waiting his reply
[04:38] <elky> Flannel, what the HELL just went down in -ot? :-/
[04:41] <elky> Flannel, would 'she came in and asked some slightly trolly questions, then got basically ripped apart on the basis of gender' be an appropriate surmise from a glance?
[04:45] <Flannel> elky: What?
[04:46] <elky> Flannel, -ot. they harrassed shadowgirl out of there by nicking to girl nicks and being absolutely ridiculous, then cheered when she left saying 'only room for one girl here'
[04:46] <Flannel> Oh, thats stupid.
[04:46] <elky> *I* feel uncomfortable there when that crap goes down, and i have the banhammer
[04:46] <Flannel> I wasn't paying attention to -ot for about 10 minutes if not more
[04:47] <Flannel> Mmm, yeah, looks like I picked the wrong time to look away
[04:47] <elky> murphy needs to be spanked big time
[04:47] <elky> him and his damned laws
[04:48] <Flannel> I really wouldn't be against short-term bans for those involved
[04:49] <elky> yes, but i dont want the wrath of the snuxtroll right now
[04:50] <elky> i'll do it anyway
[04:50] <Flannel> He's not even active, also, what would he have to say on the matter?
[04:51] <elky> long story, but he got sick of me getting pissed off at misogynist comments that pipe up reguarly
[04:51] <elky> so was it just derek and pokethesmot?
[04:51] <Flannel> h00k became SweetNSassyLinux, but yes, those three
[04:52] <elky> what about atomic
[04:52] <Flannel> Nope
[04:52] <Flannel> He's been playing a game for half an hour now.
[04:53] <elky> i saw irack from atomicfail, but trying to quickly read the whole lot i didn't see much else
[04:53] <Flannel> irack? let melastlog
[04:53] <elky> it's about the only thing i do see from him at glance
[04:54] <Flannel> Yeah, he was responding to her mentioning apple making a bra
[04:54] <Flannel> some TV skit
[04:54] <elky> fair nuff considering
[04:55] <Flannel> wording of removes could've used some work, the harassing wasn't done out of the channel, but close enough.
[04:56] <elky> it's obvious to those who saw
[04:58] <elky> keep an eye on aprilhare, he's going to start baiting us with bacon
[04:58] <elky> and icecream and cake
[04:59] <Flannel> Thats an interesting beating...
[04:59] <elky> Flannel, 48hours sufficient do you think or should we make it a whole week?
[04:59] <Flannel> 48 hours should suffice.
[05:05] <bazhang> elky, he is at home, and that is his office account, so he has suggested we remove it now and he will re-name and re-enter when he gets to the office at some point in the near future. Is that satisfactory?
[05:05] <elky> bazhang, we can wait until tomrrow for him to change
[05:05] <bazhang> elky, he wont be at work until Friday
[05:06] <elky> gah, i need to werks, and now derek is PMing me
[05:06] <elky> bazhang, see, now if it was registered he'd be able to ghost it
[05:06] <bazhang> he has no objection to removing now, and re-naming, re-entering then
[05:06] <elky> bazhang, it's not urgent.
[05:07] <bazhang> elky, so leave as is and let him reset on Friday?
[05:07] <elky> yep
[05:07] <bazhang> okay thanks
[05:09] <h00k> Hey elky, I'd like to talk to you about my kick/ban in #ubuntu-offtopic
[05:09] <h00k> I'm not quite sure of the way to go about it.
[05:09] <bazhang> he will rename on Friday -work , or similar
[05:10] <Flannel> bazhang: Thank him for the cooperation/etc
 the ban is 48hrs for all three of you (pokethesmot and h00k too)
 you can report to -ops with apologies at that time
[05:10] <bazhang> very apolgetic and co-operative
[05:10] <bazhang> ugh spell fail
[05:10] <elky> h00k, this is what i've told derek.
[05:10] <bazhang> Flannel, done so thanks
[05:10] <bazhang> have to head out for a bit, so just wanted to clear that up.
[05:11] <h00k> I didn't mean it to be offensive, it wasn't meant to chase her out of the channel.  I apologize.
[05:12] <elky> h00k, come back in 48 hours and repeat the apology. until then, the ban stands.
[05:16] <elky> pokethesmot has now been advised the same.
[05:17] <elky> h00k, this isn't a channel to idle in. if you have nothing further to say then we ask that you part it until the 48hrs is up so we can keep tally of who actually needs talking to.
[05:17] <h00k> elky: as I said, I'll apologize now and I'll be back in 48 hours to do the same, had she responded on the defense or showed that she was taking it offensively, I would have immediately stopped and apologized
[05:17] <h00k> elky: I'm sorry, I was typing.
[05:18] <Flannel> h00k: Sounds good.  We appreciate it
[05:18] <elky> h00k, it's not all about her.
[05:18] <Flannel> h00k: See you back in 48 to discuss it further.
[05:19] <elky> he really should take his own part message as advice
[05:19] <Flannel> Eh, He'll be better after he cools off.
[05:19] <Flannel> Right now, he just wanted to have his apology recognized.  Discussion can come later.
[05:19] <elky> well if he had have thought, he'd not have been in the firing line to begin with.
[05:20] <elky> Flannel, that's wonderful, but i'm really not in the mood for validating those particular guys right now.
[05:21] <Flannel> elky: I don't see how its validating.  Full discussion can come once things have cooled down
[05:22] <Flannel> Of the three, he'd be the good apple among the bad ones, I don't really have any reason to think he did it out of malice, and when she left, his comment did seem to indicate he was surprised.
[05:23] <Flannel> I'm not saying he was thinking at the time, but of the three, he's the one most likely to think in the future
[05:24] <Flannel> and I don't think stonewalling him here so he gets more frustrated accomplishes anything
[05:25] <elky> Flannel, i realise that he's the lesser contributor to the incident. i don't however see why he should be pampered with praise.   This is his first entry in the BT, I don't see any reason to treat him like scum.
[05:29] <elky_work> That was not treating him less than human.
[05:31] <elky_work> I acknowledged his apology by saying he could repeat it in 48 hours. He was not ignored and he was not mistreated.
[05:43] <elky_work> Space, if you take the rude word out of your ident, you wont get forwarded here.
[05:44] <elky_work> bah
[06:34] <shadowwolf> how can i get unbanned?
[06:34] <Flannel> shadowwolf: This is the channel to discuss bans and their removals
[06:35] <shadowwolf> ok.... well how can i get unbanned?
[06:37] <Flannel> shadowwolf: Do you know why you were banned?
[06:37] <shadowwolf> well not me personally, but my server... yes
[06:37] <Flannel> And why was that?
[06:38] <shadowwolf> because someone who used my server threatened to kill
[06:39] <Flannel> That was the final action, yes.  But this was also after a long period of people on your server causing trouble
[06:39] <shadowwolf> ohh...... well it wasnt me
[06:40] <Flannel> Actually, you were a part of it; or at least your nick.
[06:40] <shadowwolf> that wasnt me, however
[06:40] <ikonia> nick+ident+ip = you
[06:40] <Flannel> Regardless, What steps have you taken to fix the problems?
[06:40] <nalioth> shadowwolf: if it wasn't you personally, it was you by allowing your computer / network to be abused
[06:41] <shadowwolf> i dont know how i can?
[06:41] <Flannel> shadowwolf: Not allowing people who misbehave to use it would be an easy way.
[06:41] <elky> wait, so it wasn't you, but you know all the details?
[06:41] <shadowwolf> correct
[06:41] <indus> hi
[06:42] <ikonia> indus: hi there, please hang on a moment
[06:42] <indus> folks, ff 3.5 is in jaunty  but ubottu shows its still being built
[06:42] <elky> so how do you know all the details?
[06:42] <indus> ikonia: hi
[06:42] <ikonia> indus: thank you, noted
[06:43] <elky> indus, thanks, was that all?
[06:43] <indus> yes thank you
[06:44] <shadowwolf1> im
[06:44] <indus> ikonia said hang on a moment
[06:44] <indus> so i shall
[06:44] <shadowwolf1> im sorry i missed thar
[06:44] <Flannel> indus: If that's it, you don't need to hang on :)
[06:44] <ikonia> indus: no - it's fine
[06:44] <indus> heh ok. but i have one question
[06:44] <shadowwolf1> i missed what you guys were telling me
[06:45] <indus> the menu entry for ff still beta and shiretoko ,any ideas why?
[06:45] <shadowwolf1> my server was messing up
[06:45] <ikonia> indus: this isn't a support channel
[06:45] <ikonia> indus: I'm sure you can discuss it in #ubuntu or #ubuntu-mozzila-team
[06:45] <Flannel> I believe it's #ubuntu-mozillateam
[06:45] <indus> hmm ok thanks
[06:46] <ikonia> thank you Flannel
[06:46] <shadowwolf1> buut anyway... iI know the details because i read all of the conversations when they were done
[06:47] <ikonia> you know how to log conversations for other users, but not how to limit other users access ?
[06:48] <shadowwolf1> no, i kust scrolled down the conversatlons... they left it up
[06:48] <ikonia> indus: if there is nothing else you need you are requested to leave the channel
[06:48] <elky> you actually let them use your nickname?
[06:49] <shadowwolf1> well yes because i didnt realize it could cause harm
[06:49] <indus> ikonia: ok i cant stay ?
[06:49]  * mneptok stares blankly
[06:49] <shadowwolf1> mow that i know... they will no konger use my nick
[06:49] <ikonia> indus: it's requested not please
[06:49] <indus> ikonia: rude, but i guess its your channel
[06:49] <ikonia> !idle | indus
[06:50] <ikonia> indus: it's not rude
[06:50] <indus> sorry bye folks, but does sound rude :)
[06:50] <elky> more rude than watching someone elses discussion? i think not.
[06:51] <shadowwolf1> but anyway... is there any way i can get unbanned
[06:52] <mneptok> shadowwolf1: you're using an IRC client on a Nintendo DS
[06:52] <mneptok> is that correct?
[06:52] <shadowwolf1> yes
[06:52] <shadowwolf1> is that a problem?
[06:52] <mneptok> 23:37 < shadowwolf> well not me personally, but my server... yes
[06:53] <mneptok> a Nintendo DS is a "server?"
[06:53] <shadowwolf1> no... there are multiple ds in this household
[06:53] <mneptok> and you allow all the people to use your ident and nick on their handhelds?
[06:53] <shadowwolf1> so multiple can go on IRC at one time... but they use the same s
[06:53] <shadowwolf1> erver
[06:54] <shadowwolf1> occassionally yes
[06:54] <ikonia> the quicker you just say this was you the easier this will be
[06:54] <shadowwolf1> i didnt see any harm in it
[06:54] <ikonia> so someone used, your nick, and your ident, and then left the DS around, that you then read the conversation on
[06:54] <mneptok> shadowwolf1: i may be young, but i wasn't born yesterday
[06:54] <ikonia> just to be clear
[06:55] <shadowwolf1> not quite it was more along the lines of them showing me their conversation
[06:55] <ikonia> ooh it changes now
[06:55] <ikonia> Flannel: apologies, I'll but out
[06:55] <ikonia> butt
[06:55] <Flannel> ikonia: no, you were doing fine
[06:55] <Flannel> it's not my ban
[06:56] <Flannel> I'm half caught up in other stuff anyway
[06:56] <shadowwolf1> how did it change?
[06:56] <ikonia> shadowwolf1: you read the conversation - he left it on the screen, now he's showing you the conversation
[06:57] <ikonia> shadowwolf1: until however is responsible for your internet connection can take precautions to stop this happening again it seems sensible to leave the ban
[06:57] <ikonia> whoever sorry
[06:59] <shadowwolf1> but i can ensure that future users, including me, will obide by your rules
[07:00] <ikonia> how ?
[07:00] <elky> how?
[07:00] <ikonia> I'm out
[07:00] <Flannel> bye ikonia
[07:00] <ikonia> bye
[07:01] <shadowwolf1> because all users on a ds automatically log onyo #dsorganize, i can see who has loggedvp on and off
[07:01] <shadowwolf1> w/ this i can ytake control of users
[07:01] <Flannel> shadowwolf1: and how does that make them follow the rules?
[07:02] <shadowwolf1> i know who will and wont follow the rules
[07:02] <shadowwolf1> some friends messed with IRC for fun but othersvp like me use it as a learning experience
[07:02] <elky> i find it hard to trust your judgement
[07:03] <shadowwolf1> what if i dont allow anyone to use this nick again
[07:04] <shadowwolf1> can u ban all other nicks?
[07:04] <shadowwolf> this nick
[07:06] <shadowwolf> well...... is it possible?
[07:06] <mneptok> no.
[07:06] <mneptok> your IP address is a source of abuse.
[07:06] <shadowwolf> ohhhhh....
[07:06] <mneptok> it should, IMO, be banned. regardless of nick.
[07:07] <shadowwolf> well then what would be the problem w/ lifting the ban... i this server gets banned again theres no lifting of it
[07:08] <shadowwolf> i can promise i wont allow any abuse from this server from here on
[07:09] <shadowwolf> if abuse does happen again... then you could just ban it again, without ever lifting it again
[07:09] <elky> why would we risk another death threat?
[07:11] <shadowwolf> well if it makes a difference the death threat came from and was directed towards a nick of the same server
[07:11] <Flannel> it really doesn't
[07:11] <shadowwolf> and besides... i woukd let it happen again
[07:11] <shadowwolf> wouldnt
[07:11] <Flannel> shadowwolf: Are you saying you're going to escort everyone on the server at all times?
[07:12] <shadowwolf> escort?
[07:13] <shadowwolf> oohhhhhhhhh.... of course
[07:14] <shadowwolf> im not letting another one of those incidents happen again
[07:14] <Flannel> I really don't see how you'd manage that though,
[07:15] <shadowwolf> how not? i can see when peopke go on and off
[07:16] <mneptok> do you sleep?
[07:16] <shadowwolf> yes.... but when im asleep eveertone is asleep
[07:17] <shadowwolf> plus.... i have control of ALL Aof the ds's in this house
[07:20] <bazhang> bizarro
[07:21] <nalioth> quite.
[08:28] <jussi01> ikonia: ping
[08:31] <Flannel> linuxguy really seems to enjoy falling on his sword
[08:43] <elky> likewise grant-a
[10:47] <ikonia> I wonder if it's possible to get an ubuntu domained image bin
[10:48] <elky> find a pastebin service that also does pics and submit it for code review to the sysadmins
[10:51] <ikonia> I'll have a look, nice to put a tidy / professional spin on the services
[10:51] <elky> well, a comprehensive spin which is more important
[10:52] <elky> all under one url would be alot easier than having to revise info in multiple places
[10:52] <ikonia> very true
[12:20] <jussi01> ikonia: pm
[13:32] <jussi01> Pici: #ubuntu a bit crazy today...
[13:32] <Pici> jussi01: Agreed
[14:06] <bazhang> nameless_au said thanks
[14:22] <bazhang> glad I cleared out most of my bans yesterday
[14:29] <bazhang> wth
[14:37] <elky> Pici, around?
[14:37] <Pici> elky: Indeedy
[14:37] <elky> Pici, can you remove the baiting paddy from -ot please
[14:38] <elky> i'm sick to death of his accusations of bullying smothered with baiting. me removing him now would be fuel.
[14:38] <Pici> elky: I understand
[14:40] <elky> wow, the change in behaviour is impressive
[14:40] <elky> we ought to kick him more.
[14:41] <Pici> If only that worked for more people...
[14:41] <bazhang> he has been pretty bad of late
[14:42] <bazhang> nameless still baiting
[14:43] <elky> yep
[14:44] <elky> i take it he's been piped guidelines
[14:45] <elky> the ice is thinning, thinning...
[14:46] <Myrtti> woheee
[14:46] <Myrtti> ubuntu ultimate user!
[14:47] <elky> who?
[14:47] <bazhang> same guy yesterday; was told it was offtopic, then said 'my friend is using Ubuntu; I want to ask some questions for him'
[14:47] <bazhang> pratamesh
[16:29] <RichiH> fyi, 17:24:46 -!- [-D35P14D4D0-]<EMAIL_ADDRESS>has quit [K-lined]
[16:29] <bazhang> thanks RichiH
[16:29] <RichiH> that was most likely the runner of the bots in #ubuntu-es half an hour ago
[16:29] <RichiH> i klined him along with all the other clone hosts
[16:30] <bazhang> much appreciated
[16:38] <bazhang> what is with all the jgi today...
[17:00] <Myrtti> no`u<EMAIL_ADDRESS>seems to have some issues
[17:01] <bazhang> ah hetor`
[17:02] <bazhang> trolling about packagers/repos maintainers should be fired
[17:02] <Pici> Jordan_U: Is there anything that we can help you with today?
[18:01] <Flannel> !away > marceloleaes
[18:11] <Flannel> Hmmm
[18:11] <Flannel> that didn't forward
[18:12] <Flannel> Hmm
[18:12] <Flannel> No such channel?
[18:12] <Pici> To what channel?
[18:12] <Flannel> ##fix-your-connection, right?
[18:12] <Flannel> +b *!*@h116-000-230-016.ms01.itscom.jp!##fix-your-connection
[18:12] <Pici> ##fix_your_connection iirc
[18:12] <Flannel> BT has it with hyphens, let me try
[18:13] <Flannel> there we go
[18:13] <Flannel> Odd that the BT has it with hyphens (I can never remember,so I always just go check)
[18:29] <nalioth> why doesn't 'mv' have recursion?  i've got loads of crufty *.url and *.URL files i want to delete
[18:34] <Pici> nalioth: find /some/path -iname "*.url" -delete
[18:34] <nalioth> thanks
[18:35] <nalioth> dunno why half the man pages show -R can be used with mv
[18:35] <Pici> Mine don't :/
[18:36] <nalioth> ask Uncle Google
[18:48] <nalioth> thanks, Pici
[18:49] <nalioth> http://searchmonkey.sourceforge.net/index.php/Main_Page   is not yet ready for prime time
[21:16] <shadowwolf> can i get unbanned
[21:17] <Seeker`> @bansearch shadowwolf
[21:17] <shadowwolf> what?
[21:17] <gnomefreak> Seeker`: banned him ;)
[21:17] <gnomefreak> j/k
[21:18] <Seeker`> @login
[21:18] <Seeker`> @btlogin
[21:18] <gnomefreak> bot is slow
[21:18] <gnomefreak> Seeker`: you already are loged in
[21:18] <Seeker`> can say that again
[21:18] <Seeker`> shadowwolf: give me a minute
[21:18] <shadowwolf> k
[21:18] <gnomefreak> !whoami
[21:18] <gnomefreak> @whoami
[21:19]  * gnomefreak logs in automagicly
[21:21] <Seeker`> ah yes, would you also be ilovellama?
[21:21] <shadowwolf> nott exactly
[21:21] <Seeker`> not exactly?
[21:21] <shadowwolf> that was another person using this server
[21:22] <shadowwolf> im using a nintendo ds
[21:23] <Flannel> shadowwolf: We had this conversation last night.  What has changed since then?
[21:23] <shadowwolf> nothing... but i had to leave
[21:23] <shadowwolf> so im continuing it
[21:23] <Flannel> Operators aren't like parents, you can't just go ask another one hoping for a different answer.
[21:23] <shadowwolf> i never got an answer though
[21:24] <shadowwolf> you kept trying to call me a liar
[21:24]  * gnomefreak is a parent
[21:24] <Flannel> shadowwolf: Yeah, you did.  You haven't done anything to make us think people using your server won't cause trouble, so we don't see any reason to risk it.
[21:25] <shadowwolf> im not allowing anyone troublesome on IRC via my server
[21:26] <Flannel> So, everyone who was using it before won't be using it again, and we won't be having any more issues from you or anyone else using your server?
[21:26] <shadowwolf> like the person using the nick "ilovellama"... theyre not allowed on irc anymore
[21:26] <Seeker`> "not allowed"?
[21:27] <shadowwolf> yes... they are people who live in my household
[21:27] <Flannel> shadowwolf: And the person who was using your nick? what about the handful of others?
[21:27] <shadowwolf> i control what they can and cant do
[21:27] <Flannel> Through what methods?
[21:28] <shadowwolf> because the only way they can access IRC is via NintendoDS... i take their DS's away when unsupervised
[21:29] <Flannel> and when they are being supervised?
[21:29] <shadowwolf> i watch what they do... even if they're only playing games.... its their punishmment
[21:29] <Seeker`> who are these other people?
[21:30] <shadowwolf> my lil siblings
[21:31] <Seeker`> you are allowed to take away their DS?
[21:31] <shadowwolf> yup
[21:32] <Seeker`> so how do you spend any time chatting if you are so busy supervising all of these lil siblings?
[21:32] <shadowwolf> tthey dont mind... as long as they get a little time on it every day, theyre happy
[21:32] <shadowwolf> i stand behind them when they're on their DS
[21:33] <shadowwolf> so all i hav to do is look over there shoulder every minute or so just to peek at what theyre doing
[21:34] <shadowwolf> sometimes i can just hear their games... like mario kart sound
[21:34] <shadowwolf> i know what they're doing that was as well
[21:34] <shadowwolf> way
[21:35] <shadowwolf> im sorry ill be back in a little, i must eat dinner brb
[21:35] <Flannel> I'm mostly satisfied, but I can't watch him in -ot to make sure he doesn't cause trouble for a few more hours
[21:36] <Flannel> So, I'm bowing out of making any decision at the moment, etc.  Someone else can feel free to. yadda yadda
[21:36] <Seeker`> I cant do any serious watching atm
[21:37] <gnomefreak> unban him tomorrow and ill keep eye open but way to deep into fixing my set up
[22:04] <shadowwolf> im back
[22:04] <shadowwolf> sorry, where were we Seeker'?
[22:07] <shadowwolf> Seeker`?
[22:10] <shadowwolf> can someone please answer me?
[22:14] <shadowwolf> so how can i get unbanned?
[22:15] <Seeker`> shadowwolf: you can be unbanned tomorrow
[22:16] <shadowwolf> ? how does thatvwork?
[22:16] <shadowwolf> that work
[22:16] <Seeker`> shadowwolf: because that is what we have decided
[22:17] <shadowwolf> ? no.... im asking how do you unban someone?
[22:17] <Seeker`> type in a command
[22:18] <shadowwolf> ohhhh.... how come you can type commands but i can't
[22:18] <Seeker`> because I am an op
[22:18] <shadowwolf> is there any way for me to become an oP?
[22:21] <Seeker`> people are asked to be ops when they have been observed to contribute to the community over a length of time
[22:21] <Seeker`> typically, if you ask to be an op, you wont get it
[22:22] <shadowwolf> ohhhh... that figures
[22:22] <shadowwolf> lol
[22:22] <shadowwolf> well..... i guess that just means i have to be good huh?
[22:22] <Seeker`> yup
[22:22] <Myrtti> shadowwolf: anything else?
[22:23] <shadowwolf> ummmm.... you said id be unbanned tomorrow, correct?
[22:24] <Seeker`> yes
[22:25] <shadowwolf> ok, is there a time as well, or at any time tomorrow?
[22:28] <Myrtti> sometime in the following 24-30 hours is a good guess.
[22:29] <shadowwolf> ok.... thank you
[22:38] <Bejeezus> Hi, would anyone be able to tell me why I'm banned from #ubuntu-offtopic?
[22:42] <Seeker`> @bansearch Bejeezus
[22:43] <Bejeezus> Ah
[22:43] <Bejeezus> So it's simply because I have jesus in my name?
[22:43] <Seeker`> becuase of your ident
[22:43] <Seeker`> yup
[22:45] <Seeker`> Bejeezus: change your ident and you can join -offtopic
[22:58] <ikonia> Seeker`: I thought jesus was an ok ident,
[22:59] <gnomefreak> its a latin name (at least in mexico)
[23:01] <ikonia> yup
[23:04] <Seeker`> ikonia: not my ban
[23:04] <ikonia> ohj
[23:04] <ikonia> oh


[02:31] <fmarier> I think that the status on this answer should not be "answered": https://answers.launchpad.net/canonical-identity-provider/+question/154500
[02:32] <fmarier> or at the very least someone should translate that last update :)
[02:33] <lifeless> fmarier: #canonical-isd
[02:34] <lifeless> fmarier: deals with that product
[02:34] <fmarier> lifeless: alright, thanks
[02:34] <StevenK> lifeless: But the last three messages are from *our* PQM bot?
[02:34] <lifeless> sorry
[02:34] <wgrant> There may be a few yet to come.
[02:35] <lifeless> StevenK: see the whiteboard
[02:36] <StevenK> lifeless: Ah, but why is PQM commenting?
[02:37] <wgrant> It got an email from spm.
[02:37] <wgrant> And replied because it is broken.
[02:37] <wgrant> No idea how the email got to it, though...
[02:37] <spm> what the...
[02:38] <spm> oh ffs. I bet I know why.
[02:38] <wgrant> Oh.
[02:38] <wgrant> It's in isd-hackers?
[02:38] <wgrant> That's unfortunate.
[02:38] <spm> I assigned it to them, betcha that sends an email to their pqm.
[02:38] <StevenK> spm: But it's LP's PQM
[02:38] <lifeless> hahhahhahahahahahahahaha
[02:39] <lifeless> StevenK: its not all that isolated
[02:39] <StevenK> Ah, right
[02:39] <wgrant> launchpad-pqm is in isd-hackers.
[02:39] <StevenK> Pity
[02:39] <wgrant> Possibly because of shipit/sso.
[02:40] <spm> fmarier: in any event, no. is not answered. have reset that.
[02:41] <fmarier> spm: thanks
[02:46] <spm> fmarier: actually - try again on the creation? we do have some juju to fix that. see if I got it right. ??
[02:46] <wgrant> I wonder how long PQM is going to keep talking to itself.
[02:48] <spm> forever
[02:48] <StevenK> Sounds likely
[03:32] <fmarier> spm: looks like it worked
[03:32] <fmarier> i'm logged in as<EMAIL_ADDRESS>[03:37] <spm> excellent
[06:36] <chx> hello. we made a payment several hours ago and yet our project (examiner) shows expire in 10 hours.
[06:37] <lifeless> hi chx
[06:37] <chx> lifeless: hi!
[06:37] <lifeless> the uk dudes process that sort of thing I believe
[06:38] <chx> ah
[06:38] <lifeless> so in ~ 2 hours should be able to check
[06:38] <lifeless> IMBW and will enquire
[06:38] <chx> i also sent a few mails to our intenral folks
[06:38] <chx> they might have botched this up (forgot to apply voucher?)
[06:45] <lifeless> could be
[06:46] <lifeless> I suggest touching base with mrevell in ~1h14m
[06:58] <chx> ah it's fixed , it was our end. Sorry!
[06:58] <chx> thanks for launchpad. it's great to work with.
[12:20] <artfwo> is launchpad having some ppa problems today? i've uploaded a couple of package and they're still in "needs building" status without an estimate of the build start time
[12:21] <StevenK> artfwo: I think the majority of the PPA buildders are still out performing release duty.
[12:21] <StevenK> artfwo: Remember, that Natty thing that just happened? :-)
[12:22]  * henninge backspaces ;-)
[12:22] <artfwo> right using natty since alpha1 and kinda missed the release :)
[12:22] <henninge> adeuring: Hi! ready to switch? I am off to lunch.
[12:22] <adeuring> henninge: sure
[12:22] <StevenK> artfwo: They should return fairly soon, hopefully.
[12:23] <artfwo> oh my, https://launchpad.net/ubuntu/+builds already shows the oneiric builds underway
[12:23] <henninge> adeuring: oh, you already did ... ;-)
[12:23] <adeuring> eah ;)
[12:23] <henninge> cool
[13:03] <soren> When can we expect a full set of PPA builders again?
[13:04] <soren> Can we perhaps do it gradually? Maybe give half of them back so that queue would at least stop growing?
 more ppa builders are in bound (installing as of a few min ago)
[13:14] <lamont> repeating myself in the right channel, and all that
[13:15] <wgrant> lamont: !! Thanks!
[13:35] <lamont> you have more builders noew
[13:35] <lamont> wgrant: in your copious spare time, I want architecture to show up in the builders() api
[13:41] <wgrant> lamont: Oh, it doesn't already? I guess we need to expose Processor.
[13:41] <lamont> it is not.
[13:42] <lamont>         if opts.arch:
[13:42] <lamont>             # this is where we check the architecture, and continue if it is not us.
[13:42] <lamont>             pass    ## There's no way of getting by $arch just yet, you need the name,
[13:42] <lamont> that's my current scriptage for --arch=
[13:42] <lamont> in my script
[13:42] <lamont> and it makes me cry sometimes
[14:03] <mfraz74> what is the correct way for a browser to state what version of ubuntu it is running?
[14:59] <davidgiluk> is there any chance of a fix for the persistent oops on https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue    OOPS-1950CF324
[15:00] <davidgiluk> it's been broken for a few weeks, and now edge has the same timeout; I believe this is a known issue with that type of search (although I can't remember the issue number)
[15:03] <deryck> hi davidgiluk.  let me look at bugs we have and see if I can get a sense of what's involved.
[15:03] <deryck> adeuring, hey, I'll take IRC now.
[15:03] <adeuring> deryck: thanks!
[15:03] <davidgiluk> deryck: Thanks; it's a bit of a pain that one, we use it for the Linaro porting jam as a known-set-of-issues
[15:34] <deryck> davidgiluk, I think this is that same as bug 757426.
[15:36] <davidgiluk> deryck: Yeh that looks like it - I remember a bug with a few pages of SQL :-)
[15:36] <deryck> davidgiluk, let me talk to lifeless when he comes online.  if the fix is involved, perhaps we could raise the timeout on that one view.
[15:37] <davidgiluk> deryck: Is there a similar view but perhaps less detailed - something that just lists the bugs with that tag but without perhaps say the importance or criticality or anything smart like that ?
[15:37] <deryck> davidgiluk, no, unfortunately not.
[15:38] <davidgiluk> ah ok, I was looking for some form of workaround
[15:38] <deryck> davidgiluk, have you tried the API?  I would guess it times out too, but it's worth trying.
[15:39] <davidgiluk> maybe, haven't done any API stuff to be honest
[15:40] <deryck> davidgiluk, boo-yah!  Try:  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue&orderby=-id
[15:40] <davidgiluk> deryck: Thank you!
[15:40] <deryck> np
[15:40] <davidgiluk> deryck: IOU one cookie!
[15:40] <deryck> heh
[16:08] <dpm> deryck, henninge, I've just registered a blueprint for a session at UDS to present the upstream imports feature and discuss the plans for enabling it for source packages in Ubuntu. I know you are not attending UDS in person, but I'll subscribe you guys, and it'd be awesome if you could participate remotely. Also, who else is on your squad? I'll subscribe them too to make sure at least one of you guys can make it if possible
[16:08] <dpm> Anyway, it's https://blueprints.launchpad.net/ubuntu/+spec/community-o-launchpad-translations-upstream-imports-presentation-and-plans/
[16:09] <deryck> dpm, great, thanks. abentley and abel are on the squad too
[16:09] <deryck> dpm, and flacoste and jml will be there in person.  one of them might like to attend.
[16:09] <dpm> cool, thanks deryck
[16:09] <jml> dpm: feel free to invite me & make my attendance necessary.
[16:09] <dpm> jml, awesome, thanks
[16:11] <dpm> danilos, same for you if you decide to get the car and come for a couple of days to UDS ;) ^^
[16:11] <henninge> dpm: the session will have to be held by noon Thursday. I'll be away on Friday and travelling dome of Thursday afternoon.
[16:11] <dpm> henninge, ok, I'll make sure it's scheduled properly then, thanks!
[16:15] <dpm> henninge, actually, would you mind registering yourself at https://launchpad.net/sprints/uds-o for the days you'll be available, even if only remotely? This way the session auto-scheduler will do the job and it's less error prone (so we don't have to schedule sessions manually)
[16:15] <danilos> dpm, thanks, I'm still pondering if I should drop by :)
[16:16] <dpm> danilos, come on, I'll buy you a beer or two!
[16:16] <henninge> dpm: sure
[16:16] <henninge> dpm, danilos: I was wondering the same thing ...
[16:16] <danilos> dpm, heh, I am very strongly in favour of coming, just not absolutely sure yet :)
[16:16] <dpm> thanks henninge (you'd get a drink too! ;)
[16:17] <danilos> henninge, heh, that'd be cool
[16:17] <dpm> absolutely
[16:18] <henninge> danilos: wow, it's only 5 hours by car for you ...
[16:19] <henninge> dpm: I guess you'd have to ask my manager to send me ;)
[16:28] <danilos> henninge, 5 hours? I usually do it in 3 :)
[16:28] <danilos> henninge, it's all highway, 350km, 5h is definitely too much even for others :)
[16:29] <henninge> danilos: well, google maps said 4:40 ...
[16:29] <henninge> danilos: do you know where the docs for opening translations are? jtv had found them but I failed to record it.
[16:29] <danilos> henninge, viamichelin.com is much better for that :)
[16:29] <danilos> henninge, not sure, sorry
[16:30] <henninge> danilos: np
[16:31] <henninge> danilos: viamichelin says 3:57 ;)
[16:32] <danilos> henninge, yeah, it's closer :)
[16:32] <henninge> danilos: found it!
[16:32] <danilos> henninge, cool, where was it? (I tried looking at dev.l.n)
[16:33] <henninge> danilos: no, it's on the internal wiki
[16:33] <henninge> https://wiki.canonical.com/Launchpad/Translations/UbuntuOpenings
[16:33] <danilos> henninge, ah
[16:34] <henninge> danilos: would I use dogfood for step 3?
[16:36] <danilos> henninge, why not staging?
[16:37] <danilos> anyway, gotta run, ttyl
[16:37] <henninge> danilos: bye
[17:55] <deryck> abentley, hey.  coming up on your shift if you're ready.
[17:55] <abentley> deryck: yep, I'll be there.
[17:55] <deryck> abentley, cool.
[18:01] <abentley> deryck: I think we can kill the "Launchpad Down" from the topic, right?
[18:01] <deryck> abentley, yeah, I think so.
[19:15] <cody-somerville> OOPS-1950CQ433
[19:30] <debfx> abentley: can you recreate the lp:~vcs-imports/pkg-kde-tools/debian branch?
[19:42] <abentley> debfx: I could, but I think it would make more sense if you request it.  That way, the new one will be owned by you or whatever team of yours is appropriate.
[19:48] <debfx> abentley: ok will do, thanks for your help
[19:48] <abentley> debfx: No problem.
[20:01] <joey> abentley: hello!
[20:01] <joey> I found a bug
[20:01] <abentley> joey: hello!
[20:01] <joey> abentley: https://blueprints.launchpad.net/sprints/uds-o?searchtext=%25
[20:02] <joey> abentley: There's a blueprint scheduled for UDS on the 11th that appears to have a % sign in it according to the summit folks. I was trying to find it and found that oops
[20:03] <abentley> joey: Since it produces an oops, if you file a bug, we'll mark it critical.
[20:05] <joey> abentley: https://bugs.launchpad.net/launchpad/+bug/777357


[14:16] <BluesKaj> Hi all
 Should we look at replacing VLC for this? https://haruna.kde.org/
 Studio have switched. (re @ahoneybun: Should we look at replacing VLC for this? https://haruna.kde.org/)
 To that one?
 Yes
 The close youtube-dl integration makes me hesitate. That needs more frequent updating to keep working than a Ubuntu release cycle is good at
 Anyway, it is something to seriously consider before feature freeze
 Do we want to make a vote? I think your vote is a bit more important though if Studio is using it then maintaining shouldn't be too bad?
[23:35] <Eickmeyer> youtube-dl hasn't had a release in over a year and isn't as much of a moving target as you realize: https://github.com/ytdl-org/youtube-dl/
[23:53] <arraybolt3> I thought youtube-dl was dead and yt-dlp was the right one to use now?


[04:38] <MTeck> What would you think about the ability to have you're own little dashboard so you can log in and see things such as open bugs assigned to you, add a short note, view open bugs in a speific project, etc?
[04:53] <micahg> MTeck: this is the slow time for this channel
[04:56] <MTeck> micahg: I was hoping not to clog the channel - just want opinions
[04:58] <micahg> what would the short note be for?
[04:58] <MTeck> a reminder or something
[04:59] <micahg> maybe e-mail the bugcontrol list
[04:59] <MTeck> I figured it wouldn't take too much sql or storage space for it
[04:59] <MTeck> ok
[04:59] <MTeck> I'm talking to one of the LP devs - I just want more ideas on what people will think
[10:14] <Ryan52> I have access to private bug reports (I'm in the bug control group), however I don't get notification via email of new private bugs on packages I'm subscribed. is there any way I can make this happen?
[10:14] <Ryan52> I understand that email is insecure, but maybe it could send a gpg encrypted message?
[10:14] <Ryan52> or it could just send a mail with "oh look, there's a new bug here: http://..."
[10:16] <lifeless> you're not subscribed appropriately, I suspect
[10:16] <lifeless> but #launchpad may have a better answer
[10:16] <Ryan52> "appropriately"?
[10:16] <Ryan52> okay, I'll go to launchpad, I just expected people here would know.
[11:14] <dutchie> is it useful to go through bugs with patches attached and apply them in bzr branches?
[13:12] <AnAnt> Hello, could someone help with LP 414795 ?
[13:12] <ubot4> Launchpad bug 414795 in pulseaudio "PC beep no longer works in Karmic alpha4" [Undecided,Confirmed] https://launchpad.net/bugs/414795


[00:01] <sinzui> huwshimi: mumble?
[00:02] <huwshimi> sinzui: Sure
[00:04] <lifeless> sinzui: added; please give another once-over. Thanks!
[00:33] <lifeless> hmm
[00:33] <lifeless> how does the lp wiki get wikinames these days?
[00:33] <lifeless> SSO or LP ?
[00:33]  * sinzui wants to know that answer
[00:33] <sinzui> we can close about 8 bugs id LP is not involved
[00:33] <lifeless> hloeung: hi
[00:34] <hloeung> lifeless: Hi
[00:34] <lifeless> we're wondering how dev.launchpad.net gets its wikinames for users logging in via openid
[00:34] <lifeless> is it via the SSO service
[00:34] <lifeless> or via LP
[00:34] <wgrant> lifeless: Wikinames? Doesn't it just use usernames?
[00:35] <wgrant> It's not like the old days of the Ubuntu wiki.
[00:35] <lifeless> well, consult - https://dev.launchpad.net/UserPreferences
[00:35] <wgrant> Hm?
[00:35] <lifeless> if someone does a timestamp
[00:35] <lifeless> it uses their wikiname
[00:36] <lifeless> but there is no ui to set it
[00:36] <wgrant> Hmm, true.
[00:36] <lifeless> so presumbably its coming from openid or *something*
[00:36] <NCommander> wgrant: so I'm trying to poke dominator to handle my arch_any_all skew test case, and I'm really concerned about performance. To determine if a skew has happened, we need to query each SPH for a given binary package, and check to see what has published where. That's not going to be DB friendly ...
[00:36] <wgrant> But it gets it through SSO, which doesn't expose wikinames.
[00:36] <wgrant> Maybe it just uses displayname.
[00:36] <lifeless> we're about to delete wikinames from lp
[00:36] <lifeless> if that table is replicated to sso
[00:36] <wgrant> It's not.
[00:36] <lifeless> I can imagine Bad Things Happening
[00:36] <wgrant> \d lp_<TAB>
[00:37] <lifeless> NCommander: indeed. That would be fail.
[00:37] <NCommander> Right
[00:37] <wgrant> NCommander: What is the algorithm you are using?
[00:37] <wgrant> We do far worse queries in the dominator now.
[00:37] <NCommander> wgrant: I haven't written one yet
[00:38] <NCommander> wgrant: well, for each BPPH, I need the SPH to grab the binary packages it generates, and then checks the dependencies to see if they would still be satisifiable if a package was marked SUPERSEDED
[00:39] <wgrant> NCommander: I don't think you can sensibly parse dependencies.
[00:39] <wgrant> NCommander: that is going to be terribly slow.
[00:39] <lifeless> if they are modelled in the db we can do it
[00:39] <lifeless> recursive query
[00:40] <cody-somerville> wgrant, why does it have to be slow?
[00:40] <lifeless> cody-somerville: death by a thousand cuts
[00:40] <NCommander> Ideally, I want LP to make sure the archive is in an installable state
[00:40] <lifeless> NCommander: you might like to look at the conflictchecker schema
[00:40] <cody-somerville> NCommander, There are tools that exist that do just that.
[00:40] <NCommander> cody-somerville: your not catching the point
[00:40] <lifeless> NCommander: it handles in-db dependency queries to answer some very similar questions
[00:41] <NCommander> The archive should NEVER be uninstallable as it disrupts image building on ports architectures
[00:41] <lifeless> FWIW I agree
[00:41] <NCommander> lifeless: right, but conflictchecker isn't run once an hour like the publisher :-)
[00:41] <wgrant> NCommander: The publisher is run every 5 minutes.
[00:41]  * NCommander coughs
[00:41] <lifeless> NCommander: no, but it can handle a single package change in typically 50-100ms
[00:41] <wgrant> The primary archive publisher is a special case.
[00:42] <NCommander> lifeless: the dominator does the entire archive at once. Not on a per package basis. Given we have 17-20k binary packages, that's going to add up
[00:42] <NCommander> fast
[00:42] <wgrant> NCommander: Not quite.
[00:42] <lifeless> NCommander: you don't need to recheck things that aren't changing.
[00:42] <wgrant> NCommander: I think they will still transition from Published->Superseded as normal.
[00:42] <lifeless> NCommander: you need to check the implication of things that *are* changing.
[00:43] <wgrant> NCommander: But Superseded will be included in indices, until removal is scheduled.
[00:43] <wgrant> NCommander: judgeSuperseded will implement this logic.
[00:43] <NCommander> wgrant: as it stands, shouldn't it be PUBLISHED if it should be in the index?
[00:43] <wgrant> NCommander: It examines Superseded but uncondemned publications. It needs to implement this extension.
[00:43] <wgrant> NCommander: Yes, but we are not talking about as it stands :)
[00:45] <NCommander> At the risk of making a lot of pain for myself, but it might be saner to have a new PUBLISHED_SUPERSEDED status
[00:45] <wgrant> Why?
[00:45] <NCommander> instead of making SUPERSEDED now be inconsistant w.r.t. to something publishing status
[00:45] <wgrant> All tools can now handle multiple versions in the indices.
[00:45] <wgrant> Since Debian does it.
[00:45] <NCommander> yes, but if I look at all SUPERSEDED packages, I no longer have an idea what may or may not be held in archive.
[00:46] <NCommander> er, in the indices
[00:46] <NCommander> Ideally, PUBLISHED_SUPERSEDED should also include a reason on why it hasn't left the incidies
[00:46] <wgrant> The idea is that everything on disk will be in the indices.
[00:46] <lifeless> stuff in superseded is on disk, right ?
[00:47] <NCommander> So then SUPERSEDED should simply always be in the indicies.
[00:47] <NCommander> until it reaches its execution time.
[00:47] <wgrant> lifeless: Partly.
[00:47] <wgrant> lifeless: status = SUPERSEDED AND dateremoved IS NOT NULL is on disk.
[00:47] <wgrant> GRAR
[00:47] <wgrant> s/NOT //
[00:48] <NCommander> wgrant: won't that become DELETED on the next publisher run?
[00:48] <wgrant> NCommander: No.
[00:48] <wgrant> Superseded/Deleted/Obsolete are all final states.
[00:48] <wgrant> Superseded == package was superseded
[00:48] <wgrant> Deleted == package was explicitly deleted
[00:48] <wgrant> Obsolete == series went obsolete.
[00:49] <NCommander> Ah
[00:49] <NCommander> So as I read domination, the only thing that tells LP is something is SUPERSEDED is if it pops multiple versions of a given package
[00:49] <NCommander> That check needs to be made smarter
[00:49] <lifeless> huh, no
[00:49] <wgrant> Why?
[00:51] <NCommander> bah
[00:51] <NCommander> sorry
[00:51] <NCommander> my brain seized
[00:53] <NCommander> so if I'm following you, the 'correct' solution is to have everything that is SUPERSEDED end up in the indicies until its execution time, and then modify deathrow to be smarter about what packages it brings death to.
[00:53] <NCommander> am I in the right ballpark?
[00:54]  * wallyworld grumpy. no coffee yet so far today. must rectify
[00:54] <wgrant> NCommander: Until its *condemnation* time.
[00:54] <wgrant> Removing it at the time of execution would leave stuff 404ing a lot.
[00:55] <wgrant> We have no maintenance people around right now, do we?
[00:55] <wgrant> lifeless: ^^?
[00:55] <NCommander> Well, then the most straightforard thing to start off with is implementing that SUPERSEDED packages stay in indicies and fixing whatever breaks from that, then make deathrow smarter
[00:55] <lifeless> wgrant: in this tz atm ? I think not.
[00:56] <wgrant> lifeless: :(
[00:56] <lifeless> maybe brad or someone.
[00:56] <wgrant> lifeless: There are unlanded cowboys :(
[00:56] <lifeless> they can be reapplied in a pinch
[00:56] <lifeless> which sucks butwhatare yougoingtodo
[00:56] <wgrant> Or we just exclude germanium this time.
[00:56] <lifeless> right
[00:58]  * NCommander makes a new LP branch for changing how SUPERSEDED is handled
[01:00] <wgrant> NCommander: We probably want to talk to Julian before you start on anything like this.
[01:00] <NCommander> wgrant: fair enough. What time zone is he in?
[01:00] <wgrant> NCommander: He's UK
[01:01] <wgrant> So BST.
[01:02] <wgrant> Yay, I can self-review without lifeless killing me now.
[01:02] <NCommander> right, so I will see him in ~8 hours
[01:02] <wgrant> NCommander: I hope not.
[01:04] <NCommander> wgrant: ?, that would be at the start of his day
[01:05] <lifeless> wgrant: I would never kill you :)
[01:05] <wgrant> NCommander: Yes, but the middle of your night.
[01:06] <wgrant> Hmm.
[01:06] <wgrant> Is my connection dodgy, or is LP sending empty responses?
[01:07] <NCommander> wgrant: well, that's hat caffiene is for, but hopefully he will be up when I get up (and that your timezone overlaps somewhere in there)
[01:07] <wgrant> Overlap between the three of us is just about impossible.
[01:08] <wgrant> Maybe late my evening.
[01:40] <wgrant> Hm.
[01:41] <wgrant> ShipIt is inactive, but the bugs are still open?
[01:43] <wgrant> sinzui: Can we delete mailing-list-experts?
[01:43] <wgrant> sinzui: It's not a celebrity any more, and its only related artifact is the deleted mailing-list-beta-testers
[02:33] <wallyworld> wgrant: you have some changes to lazr-js for the picker entry rendering? i need to hack in the same area - i want to extract out the picker entry rendering to a method that can be overridden. if you are done i can merge in your branch before i start hacking
[02:35] <wallyworld> or i can take just your lazr-js changes for the affiliation rendering work and go with that
[02:41] <wgrant> wallyworld: Heh, no, the lazr-js changes are terrible hacks that need to be rewritten. And they're tiny. So you do your stuff, and I'll rework on top of that when you're done.
[02:41] <wallyworld> ok. thanks
[02:59] <LPCIBot> Project windmill-devel build #159: STILL FAILING in 1 hr 6 min: https://lpci.wedontsleep.org/job/windmill-devel/159/
[02:59] <timrc> StevenK, hey... where are you guys pulling python-testtools from?  I'm not seeing 0.9.11-r189 on pypi (at least sudo easy_install "testtools>0.9.10" is not finding it) and I don't see it getting built in Ubuntu, either
[03:00] <lifeless> its not released yet I don't think
[03:01] <lifeless> __version__ = (0, 9, 11, 'dev', 0)
[03:01] <lifeless> timrc: thats a snapshot
[03:01] <lifeless> timrc: its in the lp download cache
[03:18] <timrc> lifeless, ah... rocketfuel-get is my friend
[03:22] <jtv> hi folks
[03:22] <wgrant> Morning jtv.
[03:30] <lifeless> u
[03:30] <lifeless> hi jtv
[03:31] <jtv> hi
[03:31] <jtv> what does the "u" stand for?
[03:31] <lifeless> jtv: bigjools suggested we have a call w.r.t. the persona discussion - I'd be delighted to do that sometime today if you want.
[03:31] <lifeless> jtv: 'u' - up in gmail.
[03:31] <jtv> ewin?
[03:31] <lifeless> yup
[03:31] <jtv> :)
[03:32] <jtv> Julian also suggested that we chat about another problem, but since I haven't had my coffee yet I can't even speak coherently about it
[03:32] <lifeless> well there is no rush
[03:32] <lifeless> I'm still in my workday for at least another 1.5 hours, and probably significantly more
[03:34] <jtv> Knowing you, you'll probably throw in another 17 of overtime.
[03:34] <lifeless> yeah
[03:34] <lifeless> I just won't feel guilty about wandering off during those hours :)
[03:34] <jtv> Good!
[03:35] <jtv> Well, I've made a note of the time and will definitely get that coffee first.
[04:13] <wgrant> lifeless: Good plan to try GPGHandler first.
[04:32] <jtv> lifeless: the coffee is kicking in.  Yes, I'd be delighted to have a chat about the persona thing if you still have time!
[04:32] <lifeless> sure thing
[04:35] <jtv> lifeless: mumble?
[04:36] <wgrant> lifeless hates freedom.
[04:36] <lifeless> jtv: do you have canonical voip?
[04:36] <lifeless> jtv: failing that skype ?
[04:36] <lifeless> mumble to here is frankly terrible
[04:36] <jtv> I don't have the voip thing, no… let me start skype.
[05:23] <StevenK> wgrant: O hai. Where does one get testr?
[05:25] <spiv> StevenK: from lp:testrepository, or packaged in https://launchpad.net/~testing-cabal/+archive/archive
[05:25] <wgrant> StevenK: apt:testrepository
[05:26] <wgrant> Fail, gnome-terminal doesn't link that.
[05:26] <wgrant> apt://testrepository
[05:26] <wgrant> Still fail.
[05:26] <wgrant> Anyway, it's in the primary archive.
[05:35] <StevenK> spiv, wgrant: Ta
[06:09] <StevenK> Is anyone available to review?
[06:10] <wgrant> StevenK: What's up?
[06:11] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/notify-announce-list/+merge/63067
[06:11] <wgrant> You've probably had enough of my reviews lately, though.
[06:11] <StevenK> Haha
[06:11] <wgrant> Aha.
[06:11] <StevenK> This is a hopefully 1: short, 2: safe
[06:12] <wgrant> Yeah.
[06:12] <wgrant> It's not the branch I thought it was.
[06:12] <StevenK> No, Julian subverted me.
[06:14] <wgrant> StevenK: You've not cleaned up archiveuploader. Your point is invalid.
[06:14] <wgrant> You can wipe announcelist out of archiveuploader entirely, AFAICT.
[06:15] <StevenK> wgrant: I had not done so because I wasn't sure how much test fallout there would be.
[06:15] <wgrant> Test fallout is better than tech debt in the most tech debty part of the tech debt that is our codebase.
[06:15] <StevenK> wgrant: Let me wave the axe around more.
[06:15] <wgrant> Thankyou sir.
[06:17]  * StevenK tries to remember where else he saw it
[06:18] <wgrant> lib/lp/archiveuploader/uploadpolicy.py should be all that's left.
[06:18] <wgrant> Except maybe tests.
[06:18] <wgrant> But there probably aren't tests.
[06:18] <wgrant> Because this is archiveuploader.
[06:19] <wgrant> Ah, no, uploadpolicy.txt tests it vaguely.
[06:19] <StevenK> I've just cleaned that up by removing the *ugly* property
[06:19] <wgrant> Yup.
[06:19] <StevenK> However, I can recall something that took announce_list as an argument
[06:19] <wgrant> acceptFromQueue?
[06:19] <wgrant> notify?
[06:19] <StevenK> lib/lp/soyuz/browser/queue.py perhaps
[06:19]  * StevenK looks
[06:19] <wgrant> A whole lot of other stuff which was sick and wrong?
[06:20] <StevenK> Let me see if the test you mentioned is broken first
[06:21] <StevenK> I changed the file already, so finding it is a simple matter of grep
[06:21] <LPCIBot> Project windmill-devel build #160: STILL FAILING in 1 hr 9 min: https://lpci.wedontsleep.org/job/windmill-devel/160/
[06:25] <StevenK> wgrant: It was soyuz/scripts/queue.py
[06:25] <wgrant> :(
[06:25] <StevenK> I've cleaned it up too
[06:33] <wgrant> StevenK: Done.
[06:38] <StevenK> wgrant: Is http://pastebin.ubuntu.com/615643/ better?
[06:39] <wgrant> Worse.
[06:40] <wgrant> That linewrap makes me sad.
[06:40] <wgrant> There's a reason I did it the other way :)
[06:40] <StevenK> Sure, but distroseries.changeslist is longer :-)
[06:41] <wgrant> If you must have the BACKPORTS line wrap, put it on a separate line and indent it.
[06:42] <wgrant> Complex conditions want to be readable :(
[06:42] <StevenK> wgrant: http://pastebin.ubuntu.com/615644/
[06:43] <wgrant> StevenK: At that point you might as well just move the whole thing on to a new line.
[06:43] <wgrant> No parentheses, and it's clearer.
[06:44] <wgrant> But that is better :)
[06:44] <StevenK> wgrant: http://pastebin.ubuntu.com/615645/
[06:44] <wgrant> StevenK: Looks great, thanks.
[06:45] <StevenK> Excellent. I've also eradicated announce list from queue.py and its tests, so I'll toss it at ec2.
[06:45] <wgrant> Perfect.
[06:46] <StevenK> wgrant: Also, not arguing about my changes? What, are you sick? :-P
[06:47] <wgrant> This is a largely unoffensive cleanup :)
[06:47] <StevenK> Tis not large enough for my liking
[06:47] <StevenK> wgrant: Oh, was that your first code review?
[06:47] <StevenK> (As opposed to code*)
[06:48] <wgrant> Well, apart from the one yesterday where lifeless graduated me so he didn't have to find a mentor, yes.
[06:48] <StevenK> Haha
[06:53]  * StevenK ponders a bug vs --no-qa
[06:54] <wgrant> no-qa
[06:56] <wgrant> lifeless: I see the notification on the blog... no issues with deploying the inTeam fix?
[07:29] <lifeless> wgrant: no issues
[07:31] <LPCIBot> Project windmill-db-devel build #354: STILL FAILING in 1 hr 5 min: https://lpci.wedontsleep.org/job/windmill-db-devel/354/
[07:33] <wgrant> lifeless: Thanks.
[07:54] <wgrant> Yay
[07:54] <wgrant> I think person search works OK when karma is added.
[07:54] <wgrant> wallyworld: Do you have a newer query than the one you gave to lifeless yesterday>
[08:27] <wgrant> Hmm.
[08:27] <wgrant> Except team search.
[08:27] <wgrant> This sort of completely breaks that.
[08:27] <wgrant> Fail.
[08:29] <StevenK> wgrant: Is that wallyworld's branch, or something else?
[08:30] <wallyworld> wgrant: i've included one in the mp: https://code.launchpad.net/~wallyworld/launchpad/person-picker-results-order/+merge/63057
[08:30] <wgrant> StevenK: I have added karma to his query.
[08:30] <wgrant> And it works pretty well.
[08:30] <wgrant> IRC nicks and email addresses are awkward, though :(
[08:31] <wgrant> Since all we have is non-discriminatory prefix match.
[08:31] <wgrant> They tend to dominate.
[08:31] <wgrant> Karma mostly sorts that out.
[08:31] <wgrant> But something longer-term would be nice.
[08:46] <jtv> I've had quite enough of this bouncing.  Let's see if it gets better if I take wifi out of the loop.
[08:52] <jtv> stub: I'm hoping to get a db review & patch number out of you for https://code.launchpad.net/~jtv/launchpad/db-bug-790161/+merge/63002
[08:53] <lifeless> wgrant: aggregate karma across the team ?
[08:54] <wgrant> lifeless: That would work for ranking people and teams separately.
[08:54] <wgrant> lifeless: But ranking them sensibly in a single listing borders on impossible.
[08:55] <lifeless> average the karma across the team
[08:56] <wgrant> That might actually work.
[09:02] <adeuring> good morning
[09:06] <mrevell> Hello
[09:07] <adeuring> hi mrevell
[09:35] <stub> jtv: k
[09:35] <jtv> ขอบ
[09:39] <lifeless> stub: evening
[09:43] <stub> jtv: Why is copy_policy free form test rather than something like an enum?
[09:43] <stub> lifeless: yo
[09:44] <jtv> stub: otp
[09:44] <stub> (yeah you know me)
[09:52] <danilos> anyone knows if there's an easy way to fetch multiple persons (given by their self_links) using API without doing multiple round-trips to the server?
[09:53] <wgrant> You can't.
[09:53] <danilos> or, how would one best export a tuple over the API for use in JS (I want to get a tuple (BugSubscription, Person, Person [subscribed_by]) from an API call so I don't have to do multiple round-trips, but I'd also feel that such API wouldn't really be the best publicly facing thing one might have; or maybe it would be)
[09:54] <danilos> wgrant: "yay"
[09:58] <danilos> I am guessing I'll have to define a separate interface holding this information, because I want a collection of such tuples; or, is there a way to force "shallow" (1-level) snapshotting of particular attributes on an already exported interface?
[09:58] <lifeless> danilos: you're probably best off defining a custom view which can return the json youneed
[09:59] <lifeless> our API is hugely focused on types and URL mapping, sadly
[09:59] <danilos> lifeless, is that the practice we encourage? I kind of dislike that approach
[09:59] <lifeless> danilos: to date folk generally throw their hands up and say 'man this is too hard'
[10:00] <danilos> lifeless, right, it's probably the simplest thing but the bug page is doing a bunch of that stuff and I'd rather do away with it (well, I'd still be able to get rid of 3-4 portlets, and introduce 1 new view, so it'd be an improvement, but I was hoping for 0)
[10:00] <lifeless> danilos: I recall a page somewhere that exists just to give json to browser js scripts
[10:01] <danilos> lifeless, yeah, there's a few of those on the bug page, and some of them render the actual HTML that's loaded through AJAX (yuck)
[10:01] <lifeless> danilos: the main API can do that too
[10:01] <lifeless> danilos: I agree that its yuck. It makes the service proposal I have have some fugly bits
[10:02] <lifeless> danilos: but all that said, I think if you have something pretty use case specific, putting it in the public API would be a little ugly
[10:02] <danilos> lifeless, right; still, useful to know that this is the approach I should take
[10:03] <danilos> lifeless, agreed, but if I need this (i.e. "get all subscriptions with subscriber Person fetched at the same time"), I am pretty sure public users might need it too
[10:03] <danilos> lifeless, but, then again it'd be opening a whole new can of worms, and I'd rather not go there
[10:04] <lifeless> right
[10:04] <lifeless> there is a broad issue with the API and performance
[10:04] <danilos> yup
[10:04] <lifeless> launchpadlib cannot use point solutions
[10:04] <lifeless> it needs some (perhaps easy) infrastructure and a defined pattern for the solutions to fit into
[10:05] <danilos> ok, thanks; I'll go with a view-provided JSON and load that on-demand, and I'll let you worry about coming up with nice infrastructure for this :P
[10:05] <lifeless> There is a document about doing a V2 API by leonardr/benji/gary on the wiki
[10:05] <lifeless> cool
[10:28] <wallyworld> stub: hi. i was hoping you could give me a db patch number for the person.displayname index creation script. it's included in mp https://code.launchpad.net/~wallyworld/launchpad/person-picker-results-order/+merge/63057
[10:28] <stub> wallyworld: I landed a patch to add the person.displayname index already
[10:29] <stub> patch-2208-60-1.sql
[10:30] <jtv> stub: back.  And that was opp, not otp.
[10:30] <wallyworld> stub: ok thanks. i thought you'd create the index but i needed to do the ptach still as part of my mp. i'll remove it.
[10:31] <jtv> stub: the boss specified a plain text field for the policy name because it's a bit easier to follow than an enum field.
[10:31] <stub> wallyworld: no probs. I tend to create the patches that I apply live, since the live version is usually very similar to what needs to land and I want to minimize chances of administrative screwups
[10:31] <bigjools> the policies are named rather than enummed :)
[10:31] <stub> bigjools: enums are names stored as integers
[10:31] <wgrant> But the names are crap :(
[10:31] <bigjools> SIGH
[10:32] <bigjools> nice constructive criticism there wgrant
[10:32] <wgrant> 'insecure' doesn't make sense outside the uploader.
[10:32] <wgrant> That is my only objection :)
[10:32] <stub> bigjools: Is there a fixed set of names, or are they freeform input of some sort?
[10:32] <wgrant> Well, it doesn't really make sense *in* the uploader either, but that's what we have.
[10:32]  * bigjools lets jtv continue
[10:33] <jtv> stub: fixed set, for matching policy classes.
[10:35] <stub> So what is the advantage of a text field over an enum for that? We know the advantages of enum over text field which is why we normally use them.
[10:36] <jtv> Mostly that it takes us from a mapping between policies and names to a mapping between policies, names, and numbers.
[10:37] <jtv> Not lethal, but inconvenient.
[10:37] <bigjools> I am not wedded to names, switch it if you want
[10:37] <stub> The enum infrastructure means it is a mapping between policies and enums, not between policies, names and numbers.
[10:38]  * stub would love to use pg builtin enums, but not suitable for agile development until PG 9.1
[10:38] <jtv> Well the enum provides a mapping between names and numbers; we'd add the mapping between names and policies ourselves.
[10:39] <stub> I don't follow. You reference enums as names, not as numbers using some external mapping repeating what the enum infrastructure gives you for free.
[10:40] <jtv> Apart from getting ints in the database, of course.
[10:40] <stub> job.copy_policy = CopyPolicy.ZAPIT
[10:40] <stub> Right. And you don't see then in the Python code.
[10:41] <jtv> Well, apart from the one place of course.
[10:41] <jtv> Not trying to argue, really; just describing the inconvenience.
[10:43] <stub> There is small inconvenience creating the enum definition, but advantages to using it (smaller tables, no toast, faster lookups, smaller indexes, typo catching, faster python code). So unless there is a good reason, we should switch that column to an integer and use the standard pattern.
[10:43] <jtv> Toast may be a bit of an exaggeration for this case.  :)
[10:44] <jtv> But sure, I can switch it.
[10:44] <stub> I think the toast table gets created when the main table gets created
[10:45] <jtv> Oh well
[10:45] <stub> I can list more rationalizations for enums too if you like :)
[10:45] <jtv> No that's alright, thank you :)
[10:56] <jtv> stub: updated the patch.
[11:06] <stub> jtv: Ta. Does allowing NULL still make sense ('not set' vs. explicit enum value)?
[11:06] <stub> I expect so as not all jobs will use the field (?)
[11:07] <jtv> stub: that may depend a bit on where the class hierarchy goes, but I guess it would make sense for now to forbid it.
[11:08] <stub> if it makes sense, make it not null. Or leave it as nullable if we are not sure yet.
[11:08] <jtv> I'll make it "not null."  If we ever decide that's wrong, we can relax it.  Easier than going the other way.
[11:10] <stub> jtv: Unless we are mid cycle :)
[11:10]  * stub isn't helping
[11:11] <jtv> We'll just wake up an admin in the middle of the night to drop the constraint.
[11:18] <stub> lifeless: did you see https://code.launchpad.net/~stub/launchpad/bug-758587-tests/+merge/63012 ?
[11:19] <bigjools> make it default to the current "insecure" policy please jtv
[11:19] <stub> jtv: Did you find that cpu indicator yet?
[11:19] <jtv> bigjools: it seems to make more sense to do that in the code, not in the db.
[11:20] <bigjools> jtv: either is fine
[11:20] <jtv> At the DB level I think neglecting to provide a value should produce either a null or an error, even if we do require a value for PlainPackageCopyJob.
[11:21] <jtv> stub: no, I don't have it yet
[12:04] <LPCIBot> Project devel build #771: FAILURE in 4 hr 52 min: https://lpci.wedontsleep.org/job/devel/771/
[12:19] <jtv> rvba: reviewed your branch
[12:21] <rvba> jtv: thanks a lot!
[12:21] <jtv> np
[12:22] <rvba> I'll reply to your comments once I've finished my chicken :).
[13:23] <bac> hello mrevell
[13:42] <wgrant> Hm.
[13:42] <wgrant> That is a /lot/ of failurse.
[13:49] <jelmer> wgrant: it's so bad, it's even affecting your spelling :P
[13:50] <wgrant> That's more the freezingness :(
[13:50] <jelmer> wgrant: of your machine or of your fingers ?
[13:50] <jelmer> hi matsubara
[13:50] <wgrant> The latter.
[13:50] <matsubara> hi jelmer
[13:52] <jelmer> matsubara: I made some more progress on updating bzr - current work is at lp:~jelmer/launchpad/newer-bzr
[13:53] <matsubara> jelmer, cool. should I merge your branch into mine and run tests to see if the errors are fixed?
[13:53] <matsubara> oh, you merged my branch :-)
[13:54] <jelmer> matsubara: it's too early for that, I'm still chasing some errors in bzr-git
[13:54] <matsubara> jelmer, ok, thanks for letting me know.
[14:01] <mrevell> Hey bac#
[14:13] <deryck> Hi, adeuring, abentley, and henninge.  You guys have the standup yet?
[14:13] <abentley> deryck: no, waiting for you.
[14:13] <henninge> deryck: we are chatting but waiting for youi
[14:13] <henninge> yui?
[14:13] <deryck> ok, cool.  thanks.  coming....
[14:13] <henninge> yiu?
[14:14] <henninge> :-D
[14:14] <deryck> if mumble will ever connect
[14:16] <cjohnston> henninge: mornin
[14:17] <abentley> deryck: do you want to Skype instead?
[14:17] <deryck> maybe so.  let me try one more restart.
[14:18] <henninge> cjohnston: Hi!
[14:18] <henninge> cjohnston: otp now
[14:18] <cjohnston> ok
[14:18] <cjohnston> mine still need to be worked on?
[14:18] <henninge> cjohnston: the test run failed because of other errors. I just sent a mail to launchpad-dev.
[14:19] <henninge> cjohnston: the branch should be fine now, I expect
[14:19] <henninge> but don't know for sure
[14:21] <gmb> Is anyone else seeing "AssertionError: Name "id-only" is not registered as a view or navigation step for "Person" on "mainsite"." OOPSes on launchpad.dev instances? It happens on pretty much every page.
[14:21] <cjohnston> henninge: ok.. If you get an answer, let me know please :-)
[14:34] <gary_poster> matsubara or Ursinha, will either of you have some time for some exporatory testing tomorrow?  And then we'll actually need some more probably Thursday of next week too
[14:35] <matsubara> gary_poster, yep
[14:35] <gary_poster> *exploratory :-)
[14:35] <matsubara> gary_poster, can you give me more details?
[14:40] <gary_poster> cool, thanks matsubara, I'll send you details the start of my day tomorrow.
[14:40] <gary_poster> Overview: the better bug notification feature had two bugs that meant rewriting large chunks of UI.  We have one in db-devel now, and one will be ready for a no-downtime deploy after next Wed.'s downtime deploy.
[14:40] <gary_poster> Tomorrow, we need to make sure that the intermediate changes we have are OK for a few days in production; then next Thursday we need to make sure that the final changes are OK.  Since they change a lot of code, and touch on a lot of the issues that were raised in the feature review, I thought exploratory testing would be a good idea.
[14:40] <gary_poster> Moreover, particularly for the intermediate changes, I know that we had hoped to get the final changes in before the db-deploy, so we were not as careful as we usually are, so another pair of eyes would be appreciated.
[14:40] <gary_poster> (done)
[14:41] <matsubara> gary_poster, sure thing. I'll wait for the details tomorrow and let you know once I have done the testing
[14:41] <gary_poster> thanks matsubara!
[14:41] <benji> I don't know one way or the other.  Let me take a look real quick.
[14:42] <gary_poster> benji, you and your channels :-P
[14:42] <benji> so many channels, so few windows
[14:42] <gary_poster> :-)
[14:51] <jcsackett> StevenK: you still around?
[14:51] <StevenK> jcsackett: Barely
[14:52] <jcsackett> StevenK: fair. i posted a screenshot on the MP you requested one on. but if it's too late for you to take a look at it i can throw it to someone else.
[14:52] <StevenK> jcsackett: Link me the MP again?
[14:52] <jcsackett> https://code.launchpad.net/~jcsackett/launchpad/oh-oh-pick-me-pick-me/+merge/63047
[14:53] <jcsackett> screenshot is in my reply to your comment, StevenK.
[14:54] <StevenK> jcsackett: Okay, I shall Approve. Do you feel it needs a UI review now or when it starts being used?
[14:54] <jcsackett> StevenK: i intended to get UI when it gets bolted in. until then it's too much of a pain for a UI reviewer to play with.
[14:55] <StevenK> jcsackett: Sounds fine. r=me
[14:55] <jcsackett> thanks, StevenK.
[15:34] <deryck> henninge, shall we chat now?
[15:34] <henninge> ser
[15:34] <henninge> deryck: yes, just getting ready
[15:36] <deryck> mumble is acting up again
[15:49] <timrc> If a ppa is made public after its been made private do discard the buildd_secret as well?
[15:49] <timrc> do we ^
[15:51] <wgrant> timrc: You can't change the privacy of a PPA after it has been used.
[15:52] <wgrant> Oh, I guess you're working on the API export?
[15:52] <timrc> wgrant, right, but before it's been used you can... and so in that case, do we discard the  buildd_secret
[15:52] <timrc> wgrant, right...
[15:52] <wgrant> timrc: Yes, you need to discard it.
[15:52] <timrc> wgrant, cool, thx
[15:53] <wgrant> The DB doesn't enforce it, but the secret would become public.
[16:04] <LPCIBot> Project windmill-devel build #161: STILL FAILING in 1 hr 8 min: https://lpci.wedontsleep.org/job/windmill-devel/161/
[16:24] <adeuring> abentley: fancy a small review (100 lines)? https://code.launchpad.net/~adeuring/launchpad/bug-750274/+merge/63129
[16:24] <abentley> adeuring: sure.
[16:32] <abentley> adeuring: r=me
[16:32] <adeuring> abentley: thanks!
[16:41] <gmb> sinzui: I'm looking at https://bugs.launchpad.net/launchpad/+bug/61531 at the moment and I could do with knowing whether it's something that the disclosure work is going to deal with.
[16:41] <_mup_> Bug #61531: Forbidden error when trying to mark a bug as private <403> <lp-bugs> <oops> <privacy> <ui> <Launchpad itself:In Progress by gmb> < https://launchpad.net/bugs/61531 >
[16:44] <sinzui> gmb: it is not a priority since we are focused on non-subscription mechanisms to provide access
[16:45] <gmb> sinzui: How far away is that work from being viable? I.e. is it worth me fixing the bug anyway just to make an OOPS go away or should I mark it low (or Invalid or whatever).
[16:45] <sinzui> gmb: Is this a case where ajax works and html does not?
[16:46] <gmb> sinzui: No, the problem is that either of them breaks. It's just that the HTML version breaks more obviously.
[16:46] <gmb> Because you can mark the bug private but then you can't see it. With AJAX it's not immediately apparent there's a problem until you refresh the page.
[16:46] <sinzui> Since the work is not scheduled, never. We will introduce pillar permissions in 2 months in conjunction with allowing owners to see who is subscribed to what...
[16:47] <gmb> Okay.
[16:47] <sinzui> but there are no requests from stakeholders to change how subscription to individual bugs and branches works.
[16:47] <gmb> Ah, right.
[16:47] <gmb> In that case, I'll go fix it.
[16:47] <gmb> sinzui: Thanks for clearing that up for me.
[16:48] <LPCIBot> Project windmill-devel build #162: STILL FAILING in 44 min: https://lpci.wedontsleep.org/job/windmill-devel/162/
[16:50] <sinzui> gmb: I think this bug is really about Lp's privacy entitlement rules. We simply do not permit bugs to be private without also being security issues unless an admin has toggled the projects private bug rules.
[16:51] <gmb> Hmm. I'm not sure that I understand what you mean. Are you saying that we shouldn't allow private bugs unless $SOME_RULE_FLAG is set to True?
[16:52] <sinzui> gmb: lp bugs conflates privacy and security. They are not equal since the issues are seen by different users. At this time, I think no user can toggle a bug private unless the project is configured to have private bugs. The any user can see and change security though
[16:53] <cody-somerville> sinzui, I don't think thats accurate.
[16:53] <sinzui> It will be
[16:53] <gmb> sinzui: This is the work that you're going to be landing in 2 months, right?
[16:53] <sinzui> We are separating security from privacy. We have always known Lp did not do a proper implementation
[16:54] <gmb> s/landing/releasing
[16:54] <sinzui> gmb yes
[16:54] <gmb> Right.
[16:54] <gmb> sinzui: In that case, I'll still fix the bug since the fix is cheap and it kills an OOPS.
[16:55] <sinzui> gmb When I change the bug supervisor, we will not suffer the subscription insanity. Though I can assign a team I am not a member of to the security contact, thus not have access to security bugs, I can change the role, and get access back
[16:55] <sinzui> gmb yep
[16:55] <gmb> Here's to not suffering insanity.
[16:56] <cody-somerville> lol
[16:56] <cody-somerville> I read that as sufficient instead of suffering
[17:32] <LPCIBot> Project windmill-devel build #163: STILL FAILING in 44 min: https://lpci.wedontsleep.org/job/windmill-devel/163/
[18:42] <jkakar> lifeless: FYI, I remember talking to smagoun at SomeHands last year and he mentioned he'd worked on/built a big system made out of many services connected by message queues.  You might want to ping him to get his input about your ideas for Launchpad.
[18:59] <lifeless> jkakar: thanks
[19:00] <jkakar> np
[19:32] <sinzui> lifeless: This is an example oops I have seen when we attempt to store that exceeds MAX_EMAIL_SIZE:
[19:32] <sinzui> InvalidEmailMessage: Msg <...> size 13947097 exceeds limit 10485760
[19:33] <sinzui> see lib/services/messages/model/message.py
[19:33] <lifeless> yes
[19:33] <lifeless> thats a large incoming mail ?
[19:34] <lifeless> we shouldn't record that as an OOPS, its out of our control. Hmm, but the mail path should match that.
[19:34] <lifeless> I see your point.
[19:34] <lifeless> even with that set we'd still have trouble.
[19:34] <sinzui> In a round about way mailman > holds > lp store it for review
[19:34] <lifeless> sinzui: do mailman list messages go through this code path ?
[19:35] <lifeless> s/that set/incoming mail size limited in postfix/
[19:35] <sinzui> lifeless: only the hold path. and mailman now knows not to send the entire message
[19:35] <sinzui> it also knows to only forward the text part as well
[19:36] <lifeless> ok
[19:36] <sinzui> So Lp does not oops no
[19:36] <sinzui> now
[19:36] <lifeless> so for lists.launchpad.net we allow bigger
[19:36] <sinzui> we *could*
[19:36] <lifeless> but the postfix setup anything for @launchpad.net should limit to 10485760
[19:36] <lifeless> because our code path enforces that anyway
[19:36] <sinzui> I believe it is currently configured to be lower
[19:37] <lifeless> 50MB
[19:37] <lifeless> which is, I believe, somewhat larger :)
[19:48] <lifeless> sinzui: I had a question for you
[19:48] <lifeless> sinzui: why do we blacklist -owner as a team/person name.
[19:49] <lifeless> sinzui: is it because we wouldn't be able to give the object a mailing list ?
[19:49] <lifeless> sinzui: and if so, I'm confused because having the owner of list foo as a list itself sounds darn cool
[19:50] <sinzui> lifeless: I honestly do not know.
[19:50]  * sinzui looks at nameblacklist
[19:52] <sinzui> lifeless: mailman does routing based on naming convention. http://www.gnu.org/software/mailman/mailman-install.txt
[19:53] <lifeless> sinzui: yeah, I realise we'd need to smack mailman upside the head a little
[19:54] <sinzui> lifeless: mailman3 aka a restful lib might be easy to smack
[19:54] <lifeless> yeah
[19:55] <lifeless> so lets leave it for now, I wanted to confirm I understood it properly - thanks
[20:02] <LPCIBot> Project windmill-db-devel build #355: STILL FAILING in 1 hr 5 min: https://lpci.wedontsleep.org/job/windmill-db-devel/355/
[20:03] <LPCIBot> Yippie, build fixed!
[20:03] <LPCIBot> Project devel build #772: FIXED in 4 hr 56 min: https://lpci.wedontsleep.org/job/devel/772/
[20:30] <benji> abentley: do you have a minute for a simple review? https://code.launchpad.net/~benji/launchpad/bug-719637/+merge/63159
[20:30] <abentley> benji: sure.
[20:30] <benji> cool
[20:33] <abentley> benji, do you know about the lp.testing.temp_dir context manager?
[20:33] <benji> abentley: I do now. ;)
[20:35] <abentley> benji: why are you deleting the directory in setUp?
[20:36] <benji> abentley: that was some copy-pasta; I just realized that the entire setup and teardown methods are unneeded; I've pushed a change to remove them
[20:36] <abentley> benji: excellent.
[20:39] <abentley> benji: in 9-14, are you actually considering throwing an exception or reporting an OOPS?
[20:39] <abentley> benji: nm, I must be seeing things.
[20:39] <abentley> benji: r=me.
[20:40] <benji> cool, thanks!
[20:45] <jcsackett> sinzui: i just threw up the MP for the branch that links the new YUI personpicker into the web ui. i requested you as reviewer, if you don't mind, since it needs UI as well as code.
[20:51] <benji> gary_poster: I used (a slightly modified version of) the lp2kanban script to update a card for me and it wanted to change the card with title "This will be closed automatically by doing this feature [I should not get bugmail when I am subscribed via an invalid bugtask]" to the real title for bug 380205...
[20:51] <_mup_> Bug #380205: Invalid bugtasks should not cause emails for structural subscriptions <email> <lp-bugs> <story-better-bug-notification> <Launchpad itself:Fix Committed by yellow> < https://launchpad.net/bugs/380205 >
[20:52] <benji> so if you want to run the script against the board, know that that'll happen
[20:52] <gary_poster> benji, good to know
[20:53] <gary_poster> benji, I wonder if script should only be willing to change title if the current card's title is a certain string, or maybe less than N chars or something
[20:53] <gary_poster> (unless you explicitly request it somehow?)
[20:54] <gary_poster> If we tweak a title we miht have a reason for it
[20:54] <gary_poster> might
[20:54] <benji> well, if we went that route it would be better to some how mark the card as robot-managed
[20:55] <gary_poster> maybe title would have short prefix?
[20:55] <benji> for example, if I enter a card, putting in the bug ID, the script fills in the details, then I edit the bug title, I'll want the new title updated on the card
[20:55] <gary_poster> understood
[20:55] <gary_poster> or suffic
[20:55] <gary_poster> suffix
[20:56] <benji> that's possible, I have a slight preference for the rule being "if it has a bug number (external ID), then it is externally managed"
[20:56] <gary_poster> that's pure but not as flexible as I think I want.  I s'pose we could try it out and see how much it chafes me
[20:56] <benji> we could then add an opt-out rule instead of an opt-in rule
[20:57] <benji> tag the card with "keep your grubby robot hands off me"
[20:58] <gary_poster> that would be fine-ish, but if instead it is an opt-in, and a card that is synced initially will get the opt-in mark by default, then we might get the best of both worlds: by default, things are synced, but it's clear what to delete if you want to stop the syncing
[20:58] <benji> I like that better.
[20:59] <benji> gary_poster: I'll add a card for that functionality.
[20:59] <gary_poster> cool benji
[21:10] <LPCIBot> Project windmill-devel build #164: STILL FAILING in 1 hr 8 min: https://lpci.wedontsleep.org/job/windmill-devel/164/
[21:15] <jcsackett> sinzui: can we remove the card for bug 669933 given its resolution?
[21:15] <_mup_> Bug #669933: person picker could accept extra criteria to find a user <disclosure> <lp-registry> <person-picker> <Launchpad itself:Won't Fix> < https://launchpad.net/bugs/669933 >
[21:16] <sinzui> jcsackett: yes, we can delete it
[21:16] <jcsackett> cool, done.
[21:51] <LPCIBot> Project windmill-db-devel build #356: STILL FAILING in 41 min: https://lpci.wedontsleep.org/job/windmill-db-devel/356/
[22:04] <LPCIBot> Project db-devel build #605: FAILURE in 2 hr 55 min: https://lpci.wedontsleep.org/job/db-devel/605/
[22:37] <LPCIBot> Project windmill-devel build #165: STILL FAILING in 45 min: https://lpci.wedontsleep.org/job/windmill-devel/165/
[23:04] <lifeless> poolie: when you're around, I would like to talk about bzr formats and lp
[23:49] <sinzui> wgrant: wallyworld: jcsackett. I will be 15 minutes late to the stand up.  Sorry.
[23:50] <wallyworld> np


[03:38] <davecheney> hey, can anyone help with charm-tools ?
[03:47] <webbrandon> bangorang!!!!!!!!!!!!!
[03:48] <davecheney> +1, insightful
[03:50] <webbrandon> :)
[03:50] <webbrandon> I thought I remember 13.04 being pushed as the default server launch
[03:51] <webbrandon> I dont want 12.04
[03:51] <sarnold> webbrandon: 13.04 has been retired: https://wiki.ubuntu.com/Releases
[03:51] <webbrandon> how about 13.10
[03:51] <webbrandon> :)
[03:52] <webbrandon> kidding
[03:54] <webbrandon> can't find anything in the code for aws to handle this image-stream configuration setting that sits in the template.  I just wanted to launch a current version.
[04:14] <webbrandon> sarnold: this is useful :  juju metadata validate-images -s saucy -r us-east-1
[04:41] <dpb1`> Hi -- I'm trying to bootstrap azure, I keep getting 'The affinity group name is empty or was not specified', my storage-account-name is in West US, my location is West US.  Is there something I'm missing.  I get the same error on Trunk and 1.17 (trusty)
[04:45] <dpb1`> 1.16 too... must be something I'm doing.
[05:01] <dpb1`> ya, switching to the east us sorted it.  /me ignores for now
[09:04] <tomixxx3> hi, can i launsch an "instance" in openstack without the dashbaord? because the dashboard does not work properly, i.e. the page "instances & volumes" ends up in an "interal server error" when clicking on it.
[09:22] <gnuoy> I'm using the openstack charms to deploy Havana. I'm setting the mtu on the quantum-gateway via dhcp to 1546 but something seems to be reverting it. Can you think of anything that might account for that ?
[09:54] <jamespage> gnuoy, odd
[09:54] <jamespage> I can't see anything in the charm that touches the MTU
[09:54] <jamespage> https://code.launchpad.net/~openstack-charmers/charms/precise/quantum-gateway/trunk
[09:55] <gnuoy> jamespage, and none of the neutron services are likely to fiddle with it themselves ?
[09:55] <Lord_Set> So quick question. With Ubuntu 14.04 is Openstack deployment with Juju going to get any better?
[09:55] <Lord_Set> Or any cool new features being added?
[09:56] <jamespage> Lord_Set, mailing incremental improvements; ML2 plugin will be the default for neutron
[09:56] <Lord_Set> Awesome
[09:57] <Lord_Set> What about Cisco Nexus/Neutron integration via Juju? Well the Openstack/Neutron side of it
[09:57] <jamespage> Lord_Set, some guys from Cisco have been working on that - they did an announce a few weeks ago
[09:57] <jamespage> the changes still need to land in the official charms but that is planned
[09:57] <Lord_Set> Yay great news. I missed that somehow.
[09:58] <jamespage> mailing == mainly
[09:58] <jamespage> gnuoy, I don't think so
[09:58] <Lord_Set> I love my Nexus stuff
[09:58] <gnuoy> jamespage, ok, thanks for your time. I'm going to redeploy the node in question and see what happens
[09:59] <jamespage> gnuoy, ok
[09:59] <Lord_Set> The Nexus API makes VM deployment a lot less of a headache but takes some time to setup and configure properly
[10:02] <Lord_Set> MAAS and Juju and soon going to dominate Mirantis. Trying to use Mirantis made me want to cry after a bit. Its deployment model is so rigid and to change or customize anything about deployment via Mirantis just plain hurts.
[10:14] <jamespage> Lord_Set, http://blogs.cisco.com/datacenter/availability-of-the-nexus-1000v-cloud-networking-platform-for-openstack-unveiled-at-cisco-live/
[10:26] <Lord_Set> Thanks James
[10:28] <Lord_Set> That is beyond awesome and I cannot wait! Cisco is doing some amazing things with Openstack and virtual machine networking.
[13:11] <nessita> hello everyone, I was hoping someone could help me debug why a LXC container where I ran juju bootstrap (as per https://juju.ubuntu.com/docs/config-LXC.html) now can not connect to the internet
[14:00] <gnuoy> jamespage, after redeploying the quantum-gateway I see eth0 has the desired mtu setting. Looking at the other interfaces br0 also has it but the rest don't http://pastebin.ubuntu.com/6970990/ is that ok ?
[14:03] <jamespage> gnuoy, yup
[14:03] <gnuoy> jamespage, excellent, thanks
[20:49] <cjohnston> A few of us just today started seeing "ERROR empty image-stream in environment configuration" when trying to deploy.. has something changed to cause this to happen?
[20:52] <rick_h__> cjohnston: heh, just hitting up people on this in #juju-dev
[20:52] <rick_h__> cjohnston: this on ec2?
[20:52] <rick_h__> natefinch: ^ makes me wonder if something is down on the simple streams side perhaps? or something like that?
[20:52] <cjohnston> rick_h__: canonistack
[20:52] <rick_h__> cjohnston: ok
[20:53] <cjohnston> rick_h__: https://bugs.launchpad.net/juju-core/+bug/1217397  ?
[20:53] <_mup_> Bug #1217397: image-stream configuration option for openstack provider <config> <openstack-provider> <juju-core:Fix Released by wallyworld> <https://launchpad.net/bugs/1217397>
[20:53] <rick_h__> cjohnston: yea, it seemed to be azure only but something today is causing issues with it on other providers
[20:54] <cjohnston> :-(
[20:54] <rick_h__> cjohnston: what juju version?
[20:54] <rick_h__> I've got another person testing on precise, I'm on trusty 1.17.2
[20:54] <cjohnston> the newest upload in t
[20:54] <cjohnston> 1.17.2-0ubuntu4
[20:54] <plars> I have 1.17.2-0ubuntu4 and I'm seeing it too
[20:54] <rick_h__> ok, well at least that bit is common
[20:54] <rick_h__> natefinch: this is looking like a bigger issue?
[20:55] <rick_h__> sinzui: ^
[20:55] <plars> I've been able to bootstrap and deploy just fine earlier today though (with no upgrade in between)
[20:55] <rick_h__> plars: yea, why I'm wondering if it's something associated with finding images not juju itself
[20:58] <natefinch> rick_h__: that error message is definitely a juju error message, it's trying to validate your configuration.... but for some reason it's barfing on the image-stream value, even though it's supposed to be fine for it to be unset
[21:15] <rick_h__> plars: on trusty?
[21:15] <plars> rick_h__: yes
[21:16] <rick_h__> natefinch: my teammate got it to run using 1.17.1 on precise
[21:18] <natefinch> rick_h__: hmmm...   Seems there's something funky going on with 1.17.2
[21:18] <rick_h__> natefinch: thanks. Did you want me to file a bug or are you ok from here then?
[21:22] <natefinch> rick_h__: bugs are always good.  Help prevent things from falling through the cracks
[21:26] <rick_h__> natefinch: filed https://bugs.launchpad.net/juju-core/+bug/1283246
[21:26] <_mup_> Bug #1283246: cannot deploy on 1.17.2 on trusty: error on image-stream <juju-core:New> <https://launchpad.net/bugs/1283246>
[21:26] <rick_h__> plars: cjohnston please add any notes and track &
[21:26] <cjohnston> thanks rick_h__
[21:30] <natefinch> rick_h__: thanks.  I'll make sure it gets looked at, ASAP.
[21:31] <cjohnston> natefinch: could we maybe get a slightly older version thrown in a ppa somewhere?
[21:34] <natefinch> cjohnston: 1.16 should be what's in ppa:juju/stable
[21:34] <rick_h__> natefinch: don't think it's built for trusty
[21:34] <rick_h__> or I lied
[21:34] <rick_h__> and it is
[21:34] <rick_h__> https://launchpad.net/~juju/+archive/stable?field.series_filter=trusty
[21:34] <cjohnston> ack
[21:35] <cjohnston> 1.16 complains about alot of config fields :-/
[21:36] <natefinch> unfortunately, forwards compatibility is not something we've spent any time on
[22:16] <lazyPower> has there been a recent change to the charmstore api?
[22:18] <rick_h__> lazyPower: how so?
[22:18] <rick_h__> and by store you mean juju store or charmworld?
[22:19] <lazyPower> rick_h__: i mean charmworld - my apologies. I keep forgetting there are 2 api's
[22:19] <rick_h__> lazyPower: what change are you getting. There was a release this week, but trying to recall what api changes might have existed
[22:20] <lazyPower> i have amulet tests that were working an hour ago - now i'm getting a non-helpful stacktrace bubbling up from charmworldlib. I'm trying to decompose to code to find the endpoint its calling - that way i can rule out a temporary hiccup in charmworldlib and validate its the code
[22:21] <rick_h__> lazyPower: gotcha, yea nothing changed today in charmworld. I'd have to see more details to help trace. Let me make sure charmworld is reporting healthy
[22:21] <rick_h__> bah, elasticsearch bit it
[22:24] <lazyPower> cool so i'm not going crazy then
[22:24] <mbruzek_> I am also encountering an error with juju lazyPower, and rick_h__
[22:24] <mbruzek_> rick_h__, I have a traceback that looks like this http://pastebin.ubuntu.com/6973456/
[22:25] <mbruzek_> I can grab logs if you need them.
[22:25] <lazyPower> mbruzek_: its because the search provider tanked
[22:26] <rick_h__> lazyPower: mbruzek_ if it's charmworld I'm working with webops on it atm
[22:26] <lazyPower> thats the one :) Thanks rick_h__
[22:47] <webbrandon> Could I launch a t1.micro bootstrap to manage m1 type instances
[22:47] <lazyPower> webbrandon: thats not recommended at all. since hte controller node runs zookeeper and what not
[22:48] <lazyPower> you'll run out of memory on the bootstrap node when multiple nodes converge
[22:48] <sinzui> juju doesn't use zookeeper
[22:48] <lazyPower> wait, what?
[22:48] <sinzui> juju has used mongodb for 8 months
[22:48] <lazyPower> i'm just full of misinformation today
[22:49] <webbrandon> lazyPower: you sending me down the wrong path huh???
[22:49] <lazyPower> webbrandon: well, its still not recommended...
[22:49] <webbrandon> lol
[22:49] <lazyPower> regardless of my fud
[22:50] <lazyPower> sinzui: ty for correcting me. I'm thinking of chef-server not juju
[22:50] <lazyPower> my internal wiring is getting crossed looking at this charm
[22:50] <sinzui> webbrandon, juju's boostrap node has been run on 512m, but I think 1G is the minimum. Each deployment may require its own sizes just because the services need more storage or ram
[22:51] <sinzui> webbrandon, I often bootstrap with --constraints "mem=1G" the each deploy has --constrains "mem=2G"
[22:51] <webbrandon> sinzui: thank you
[22:52] <webbrandon> sinzui: I am thinking of launching t1 because its free to manage a bitcoin pooling service
[22:53] <webbrandon> unfortunatly i have to run m class instance just to install the software
[22:54] <sinzui> webbrandon, alas juju doesn't let you specify an aws/hp instance-type (yet). The constraints only guide the selection of an instance type. I think the the HP rules have issues in fact. 2G on aws gets me a more memory that 2G on Hp
[22:55] <webbrandon> I understand how to launch the right instance type.
[23:41] <rick_h__> lazyPower: should be coming back
[23:42] <lazyPower> rick_h__: awesome. I'll run a test and see if its cleared up
[23:42] <lazyPower> thank you for driving this rick_h__
[23:42] <rick_h__> lazyPower: heh, last one around on a friday when it goes boom :)
[23:42] <rick_h__> lucky me!
[23:43] <lazyPower> We'll be meeting up in vegas soon enough. I'll buy the first beer :)
[23:44] <mbruzek_> thanks rick_h__
[23:44] <mbruzek_> now you can't say it is a thank-less job.
[23:45] <rick_h__> mbruzek_: hah, good call