[00:00] <Sebastien> omg, im still banned?
[00:01] <ikonia> yes
[00:01] <Sebastien> why
[00:01] <ikonia> as you told me not to bother
[00:01] <Sebastien> wow
[00:01] <ikonia> I did put a note in the logs to welcome you back if you came back
[00:01] <ikonia> I hoped you would, as I appreciate it's easy to get annoyed when you're frustrated
[00:01] <Sebastien> i come here to complain about someone rude to me, and i get banned...
[00:01] <ikonia> that wasn't what happened
[00:01] <ikonia> and I asked you to stay so I could explain it
[00:01] <ikonia> but I understand you where upset
[00:02] <Sebastien> one moment
[00:02] <ikonia> no problem
[00:11] <Sebastien> ok
[00:11] <Sebastien> so what's up
[00:11] <Sebastien> why am i still banned?
[00:11] <ikonia> no problem,
[00:11] <ikonia> so you where ban forwarded here (not banned as the intention is not to keep you out)
[00:11] <Sebastien> i was fucking pissed, i went for a 420 break, its better now
[00:11] <ikonia> tone down the language please
[00:12] <ikonia> it's not called for, or acceptable
[00:12] <ikonia> basically, 2 users came in here both claiming they where being pm abused
[00:12] <ikonia> I needed a minute to resolve it with you both
[00:12] <ikonia> you refused to stay in the channel and to be honest where a little dismissive that it needed looking into
[00:13] <ikonia> eg: I've reported it - ban him
[00:13] <ikonia> so I forwarded you back in here to actually resolve it and find out who was being abusive
[00:13] <ikonia> but you where angry and exploded,
[00:13] <ikonia> I tried to contact you privately but you said you where done with the project and to forget it,
[00:13] <ikonia> so I did just that until you rejoined
[00:13] <ikonia> (which I hoped you would a little clamer)
[00:14] <ikonia> that's all, nothing sinister
[00:14] <Sebastien> my intentions were just to tell you. you have no business whatsoever with what happens in pm. but being informed about rude people is sometimes fun, i know im rude too sometimes, and if triggered i will blow up f bombs and explosions like isi ain't got nothin' on me yo.
[00:14] <Sebastien> it happens
[00:14] <Sebastien> but i came here, and got banned from main
[00:14] <Sebastien> im really pissed about that
[00:14] <ikonia> Sebastien: it was useful to know there is a problem user, people should not be getting abused in pm from the ubuntu channel
[00:14] <ikonia> there is zero issue reporting it, so please don't think that
[00:15] <Sebastien> it was not abuse, don't say abuse, abuse would be sending someone 5000+ color codes super quick to make them crash.
[00:15] <Sebastien> this was pure rudeness
[00:15] <ikonia> the language was abusive
[00:15] <ikonia> thats why I said abusive
[00:16] <ikonia> either way, it's not something we want people to get from using the channel
[00:16] <ikonia> so reporting it is very much appreciated
[00:16] <Sebastien> he even came back after
[00:16] <Sebastien> Session Start: Fri Jan 01 14:36:47 2016
[00:16] <Sebastien> Session Ident: tkogitz
[00:16] <Sebastien> [14:40:40] <steamMAD> Asshole
[00:16] <Sebastien> Session Close: Fri Jan 01 14:40:48 2016
[00:16] <ikonia> I'm sure
[00:16] <Sebastien> like wth
[00:16] <ikonia> and if you'd stayed in the channel for a few minutes, we'd have discovered he was the problem and removed him
[00:17] <ikonia> however as you did pretty much a "hit and run" and refused to discuss it, it was hard for us to do anything about it
[00:17] <ikonia> (by us I mean me)
[00:17] <Sebastien> k
[00:18] <ikonia> if you give me a moment, you'll be welcome to use the channels again
[00:18] <ikonia> just try to keep calm, I certainly didn't deserve the insults I got thrown at me for trying to help you, but I DO appreciate you where upset
[00:18] <ikonia> just please don't get upset as easy,
[00:19] <ikonia> ok, the ban should be gone
[00:19] <ikonia> if you want to give it a try
[00:20] <Sebastien> ty
[00:20] <ikonia> super
[01:34] <Dylan____> How long is a ubuntu ban ?
[01:34] <Dylan____> Like from the #ubuntu channel
[01:35] <Dylan____> Cause i was abused by the channel over there
[01:35] <Dylan____> Dtsting
[01:35] <Dylan____> Stating that i was not getting things right and stuff
[01:35] <Dylan____> And im pretty annoyed how i wasnt answered by anyone ofer there
[01:38] <rww> @login
[01:38] <rww> @btlogin
[01:38] <rww> k1l_: around ^?
[01:40] <rww> might want to come back tomorrow when k1l is here and discuss it with him. since it was just set, i'm not comfortable removing it right now
[01:40] <rww> looks like he went to bed
[02:50] <Dylan____> Oh ok
[02:51] <Dylan____> Thanks anyways
[02:55] <phunyguy> Dylan____: if there is nothing else we can help you with, please part the channel and come back later.
[03:00] <Dylan____> Ok
[03:57] <Dylan____> Any news if i can get unbanned yet?
[03:57] <Dylan____> Cause i need serious help
[03:59] <bazhang> Dylan____, that was less than one hour
[04:02] <Dylan____> Hmm
[04:02] <Dylan____> Well i think im going to have to wait 24 hours till i get hell i guess
[04:03] <bazhang> try askubuntu.com
[04:03] <phunyguy> Dylan____: there is also a user support mailing list.
[04:03] <bazhang> I hope you meant help
[04:04] <phunyguy> Dylan____: with that said, #ubuntu-offtopic isn't a support channel either.
[04:05] <Dylan____> Listen i understand where your coming from
[04:05] <Dylan____> But the problem is that this is a problem i dont know how to solve and everytime it occurs i get so frustrated that i reinstall ubuntu all over again
[04:09] <bazhang> Dylan____, thats a shame, perhaps those other avenues of support are more suitable to your temeperament
[04:10] <bazhang> and temperament
[04:16] <Dylan____> So your saying im a downie then
[04:17] <bazhang> pardon?
[04:18] <bazhang> Dylan____, please use those other avenues, come back at a later time, its just now the new years weekend celebration so it wont be a come back every hour situation
[04:52] <avis> i am now banned from #ubuntu-offtopic and cleared up all issues here why i was silenced there and even came back to this channel to clarify i was not idling unreasonable here, because those here just as i had, were very turtle slow to respond to my support request.  i am the owner of ubuntu and would like to be unbanned from #ubuntu-offtopic.  i have not done anything in there that would warrant a ban.
[04:54] <rww> please elaborate on "i am the owner of ubuntu"
[04:56] <avis> if i go to the county courthouse in harris county united states of America here in the state of Texas and requested the papers for ownership i would be given full entitlement to it.  i can state previous owners, and the people that give it to me last.
[04:56] <rww> alrighty. please come back when you're not delusional and we'll discuss #ubuntu-offtopic
[04:57] <avis> may i ask who my claimant is ?
[04:57] <rww> what
[04:57] <avis> i take things to court, with my shapiros that are bottom line best shapiros best in the country of America when someone claims to own something that i do.
[04:58] <Dylan____> I think this guys a troll just saying
[04:58] <rww> Dylan____: As three ops have said now, your ban will not be removed at this time. Please /part the channel.
[04:58] <Dylan____> K soz
[04:59] <avis> so who is the claimant to my company and under what grounds am i being considered delusional ?
[04:59] <rww> avis: Alrighty, as for you. Come back when you're willing to behave in a sane and reasonable manner and not before.
[04:59] <rww> Have a nice rest of your day.
[04:59] <avis> rww, there is nothing i have said that reflects unsane manner
[04:59] <rww> I disagree.
[05:00] <avis> and any company owner would state legally that nothing was said unresonably here under grounds of ownership
[05:00] <avis> i'd like to hear your case
[05:00] <rww> I don't care to play into your nonsense.
[05:00] <rww> Anyone else want to tackle this one?
[05:03] <rww> No? Alrighty then. Your ban will not be removed at this time, avis. Please /part the channel.
[05:03] <Flannel> avis: This isn't the legal system.  We don't have to entertain your claim of ownership of Ubuntu.  Until you agree to stop discussing this matter in Ubuntu-related channels, you will remained banned, as the statements are considered unwelcome/offtopic/spam.
[05:05] <rww> @mark #ubuntu-ops avis apparently still "owns" Ubuntu. also, fun fact, i just discovered he has history under the nick k-rad too
[09:34] <k1l_> Dylan____: hi
[10:34] <ikonia> welcome back elky
[10:36] <ikonia> @clearban  65556
[10:36] <ikonia> @clearban  65338
[10:36] <ikonia> @cleanban  65556
[10:41] <ikonia> @clearban 65155
[10:41] <ikonia> @clearban  65156
[10:42] <ikonia> @clearban   66102
[10:42] <ikonia> @clearban  66435
[10:42] <ikonia> @clearban  68253
 why tell me to use the botnet?
[13:16] <k1l> no knowledge and so all the bad linux and big companies are to blame
[13:17] <bazhang> yeah
[13:17] <bazhang> dylan____ wanted you earlier
[13:17] <bazhang> we said no to the unban
[14:00] <k1l> yes, saw that in the backlog and he idled in here. if one can get him to not make drama and actually read what people answer him, than he can be unbanned, imho
[18:20] <phunyguy> hi ilhami how can we help you?
[18:20] <ilhami> waiting to get unbanned. :)
[18:21] <phunyguy> ilhami: and, where are you banned, what was the reason?
[18:21] <ilhami> in #ubuntu
[18:21] <phunyguy> Let me check it out.
[18:22] <ilhami> the reason was that someone brought a personal matter to the channel and I pointed that out and then k1l got mad and banned me.
[18:22] <ilhami> and then he also banned me in #ubuntu-touch for no reason.
[18:22] <phunyguy> Seems to me you have quite the history...
[18:23] <ilhami> me and ikonia are getting along better now than earlier
[18:23] <ilhami> :D
[18:24] <phunyguy> Bear with me, still looking at some things.
[18:25] <phunyguy> 😞
[18:26] <phunyguy> ilhami: not looking good, friend... I think you may have burned this bridge.
[18:29] <ilhami> what is not looking good?
[18:29] <phunyguy> ilhami: the ban will not be removed at this time.
[18:30] <phunyguy> The type of behavior you insist on displaying in the channel is simply not welcome.,
[18:30] <phunyguy> and since the history of it goes back to 2013, I cannot justify a removal.
[18:32] <phunyguy> So, if there is nothing else we can help you with, please /part the channel now.  Thank you.
[18:33] <ilhami> phunyguy, so tell me what I did wrong by pointing out personal matters should be taken in this channel.. it says in the topic clearly.
[18:34] <ilhami> history is history. That's in the past.
[18:36] <phunyguy> Well for one, lecturing ops in the channel about acceptable behavior.
[18:37] <ilhami> but I told what was in the topic.. shouldn't the OPs be the first ones to stick to what it says in the topic?
[18:37] <ilhami> shouldn't they be the "good" examples?
[18:38] <phunyguy> 2016-01-01T22:30:43 <ilhami> OerHeks, I just told you the truth.. Live with it
[18:38] <phunyguy> 2016-01-01T22:32:05 <ilhami> slidinghorn, tbh I don't care who is an OP or not.. I am telling what is clearly stated in the topic. Personal matters should not be discussed in here..  "PM spam? Report in #ubuntu-ops and consider umode +R"
[18:39] <phunyguy> still trying to find the personal matters you are referring to.
[18:39] <ilhami> eeh it was someone mentioning something about he got a PM
[18:39] <phunyguy> It appears to me that you just want to be loud and berate other users.
[18:39] <ilhami> look up
[18:39] <ilhami> no
[18:39] <phunyguy> ...which is not welcome.
[18:39] <ilhami> He said he got a PM from a user in the channel... PMs are none of the official channels issue.
[18:41] <phunyguy> Ok, there are a few things in play here.  1.) You have a history.  That shortens the leash.  2.) It is not up to you to enforce topic items.  That is what the chanops are for.
[18:42] <ilhami> But if you set a topic you should follow it. Otherwise you should edit it.
[18:42] <phunyguy> Probably not a good idea to step on toes.  But this changes nothing.  The ban will stay, and the discussion about it is really over.
[18:42] <ilhami> can the police do whatever they want? they don't have to abide by the law?
[18:42] <ilhami> yes or no?
[18:44] <phunyguy> Wait, you are getting upset at k1l removing a PM spammer?  Is that all?  Yeah you don't need to question that.  An operator is doing his job in the channel.  It is not up to you to lecture him on it.
[18:45] <phunyguy> so like I said, that behavior is not allowed.  This is not up for discussion.  Please /part the channel now before it turns back into a ban.
[18:46] <ilhami> phunyguy, I am getting upset that it should be discussed in the public channel.
[18:47] <ilhami> and that I can be banned because of pointing this out.
[18:47] <phunyguy> ilhami: letme put it a different way.  Spamming users in PM is also against channel guidelines.  An operator banning that user is not "complaining about it in a public channel".  It is dealing with a problem user.
[18:49] <phunyguy> You really should find something more constructive to get upset about.
[18:49] <ilhami> The user should have either PMed the OP or joined this channel. Do we agree?
[18:49] <ilhami> It is disruptive that it was mentioned in the public channel.
[18:49] <phunyguy> who complained in the channel besides you?
[18:50] <phunyguy> I don't have history that far back.
[18:50] <ilhami> I complained about the user(not the OP) and then people were all over me.
[18:50] <phunyguy> Do you also agree that you bringing it up in a public channel is ALSO disruptive?
[18:51] <ilhami> I was only mentioning it as a principle. :)
[18:51] <phunyguy> disruptive.
[18:51] <ilhami> lol
[18:51] <ilhami> so are you unbanning me?
[18:51] <phunyguy> No, not at this time, sorry.
[18:51] <ilhami> Oh ok.. I will take this with ikonia.
[18:52] <phunyguy> Ok, please part the channel now.
[20:01] <JanC> someone is spamming everybody in #ubuntu in PM using changing nicknames but always from <IP_ADDRESS>
[20:01] <JanC> ah, I see they got K-lined already  :)
[20:03] <Dylan____> Hi
[21:21] <k1l> Dylan____: hi
[22:15] <Dylan____> Whats up
[22:17] <Dylan____> Can you unban me k1l?
[22:19] <k1l> Dylan____: do you understand now what lead to that ban?
[22:20] <k1l> because "2016-01-02:02:34:28<       Dylan____ > And im pretty annoyed how i wasnt answered by anyone ofer there"  is not what actually happend there.
[22:22] <Dylan____> Yes
[22:22] <Dylan____> I understand
[22:24] <k1l> there were several supporters trying to help you and it looked like you didnt even read the answers but were busy telling everyone how you are not a beginner and trying to tell them what they should do or not to do.
[22:24] <Dylan____> No because i didnt know what you were talking abou
[22:24] <Dylan____> And at the same time i couldnt reply cause i was busy
[22:25] <k1l> that is not really helping  if you ask for support then. to keep the channel not been busy with that sort of drama i set the ban to let things cool down.
[22:25] <Dylan____> Right
[22:25] <Dylan____> Well tell me how long does this last
[22:25] <Dylan____> ??
[22:25] <k1l> because there are a lot of users who need that channel for support and that drama is just unfair to them.
[22:26] <k1l> Dylan____: so if you can make sure you keep focused on the support and read the answers you receive so its not ending in drama again, i can unban you.
[22:28] <Dylan____> Ok
[22:28] <Dylan____> Im sorry about yestaday i was just really worked up
[22:31] <k1l> Dylan____: ok, i will remove the ban now. please make sure to focus on the support and help others to help you since they are all volunteers.
[22:32] <Dylan____> Ok will do thanks
[22:32] <k1l> ok, the ban is removed. please make sure you re-read the guidelines and help keep #ubuntu a good place to solve ubuntu issues. thanks
[22:39] <k1l> Dylan____: if that is all please exit that channel. you are free to come back to talk to the team if you have another issue
[22:39] <Dylan____> Ok
[22:39] <k1l> rww<EMAIL_ADDRESS>was used 1month ago. so you still can connect with tor to freenode
[22:40] <rww> only when freenode's dnsbl has a hiccup, which is very very rarely last i checked
[22:42] <rww> (and if it happens again, they'll likely be using a different exit node anyway, considering how many of them there are)
[22:43] <rww> (for anyone else curious, there are currently about 1000 tor exit nodes)
[22:44] <k1l> so i guess dnsbl was not running on the begin of december. since there were 3 trolls using tor.
[22:45] <rww> third one being<EMAIL_ADDRESS>?
[22:46] <rww> but yeah, looks like it went down indeed
[22:46] <k1l> yep
[22:46] <rww> oh well, it's freenode, i'm happy with two-nines reliability :3
[23:00] <elky> that's fortunate.
[23:08] <valorie> happy 2016, ops!
[23:08] <k1l> thanks, happy new year to you, too.
[23:09] <valorie> so far, so good


[00:00] <zradmin> just created a test user and was able to authenticate to maas through the webpage
[00:06] <davecheney> zradmin: via juju
[00:24] <zradmin> ah ok so create another api user and stand up a second juju environment?
[00:39] <arosales> zradmin, that is how I read davecheney suggestion
[00:40] <zradmin> yeah, I'm setting it up currently
[00:41] <arosales> zradmin, cool
[01:06]  * arosales grabs some dinner
[06:15] <AskUbuntu> Creating a charm | http://askubuntu.com/q/380207
[08:16] <ankrj> Hello everyone!
[08:18] <ankrj> What kind of an environment do I need t osetup in order to start writing charms?
[08:43] <jaywink> ankrj, you will find everything you need here: https://juju.ubuntu.com/docs/authors-charm-writing.html
[11:46] <makara> hi. Juju sounds like a good idea, but I'm skeptical
[11:47] <makara> suppose I want to deploy a Wordpress instance
[11:48] <makara> what type of instance would I get? I just want a microinstance - the smallest, least powerful option
[11:49] <makara> but I've been having trouble with Wordpress because it keeps the siteurl in it's DB, and then when I associate the instance with a static IP, the DNS changes, and Wordpress breaks
[11:50] <makara> since juju is the to cloud what apt is to a system, changing an IP address would be like messing with the directories APT installs to
[11:51] <makara> what are your experiences?
[12:13] <makara> how can I deploy an EC2 t1.micro instance instead of an m1.small instance?
[12:15] <makara> terminal hangs after: juju deploy --to 0 wordpress
[12:15] <makara> ctrl+c
[12:15] <makara> juju status
[12:15] <makara> hangs
[12:44] <mthaddon> makara: you can specify whatever instance size you want - that's independent of the charms you're deploying (e.g. wordpress or mysql)
[12:45] <mthaddon> makara: see https://juju.ubuntu.com/docs/charms-constraints.html
[12:47] <makara> mthaddon, ok thanks, but I have another problem now
[12:48] <makara> juju is hanging
[12:48] <makara> so I go "juju status" and it doesn't give me anything
[12:49] <mthaddon> it may be that the instance is too small to run juju and wordpress - but I'm not sure of the best way to troubleshoot unless you already know the IP and can login to the instance to diagnose
[12:59] <makara> mthaddon, juju is running on my own machine
[12:59] <makara> i'm deploying an m1.small instance
[12:59] <makara> it deploys it, but then juju hangs
[13:00] <mthaddon> well, you're using the juju client from your own machine, but juju itself is running on the m1.small instance
[13:00] <mthaddon> so I'd try to login to that instance directly and troubleshoot - I assume this is EC2 and you can use other tools to figure out the IP of the instance, etc.
[13:44] <makara> mthaddon, ok, well if I have to do that then first impressions aren't going very far
[13:44] <makara> its why I would want to use Juju in the first place
[13:45] <mthaddon> fair enough - I'm not a juju developer, just a user like yourself, so others may have better troubleshooting advice
[13:57] <marcoceppi> makara: what version of juju are you using (juju version) ?
[14:00] <makara> marcoceppi, 1.16.3-raring-amd64
[14:01] <marcoceppi> makara: awesome, you've got the latest. You shouldn't expereince problems deploying to amazon, sorry you're having a poor first time experience
[14:01] <marcoceppi> makara: so what happens when you run `juju status --debug --show-log` ? Could you paste that to http://pastebin.ubuntu.com
[14:01] <marcoceppi> makara: it may help us debug what's going on
[14:03] <makara> marcoceppi, there's a bit too much revealed in this log for my liking
[14:04] <marcoceppi> makara: you can mask IP addresses or PM me if you want it outside of the channel
[14:05] <makara> marcoceppi, its private key data, security keys, etc
[14:05] <makara> marcoceppi, i've taken that out: http://pastebin.ubuntu.com/6453412/
[14:23] <ashipika> hello juju world..
[14:24] <ashipika> manual provisioning.. bootstrapped one host, added another.. both ubunu 12.04.. tried deploying tomcat7.. but it is stuck in pending state
[14:25] <ashipika> and for the second machine i added it says instance-state:missing
[14:27] <ashipika> any ideas?
[14:27] <marcoceppi> makara: is i-d3b6399c actually running on your account right now?
[14:34] <marcoceppi> ashipika: can you ssh in to that machine? the instance-state:missing?
[14:34] <marcoceppi> ashipika: also, manual provisioning is still very much under development
[14:35] <ashipika> i can ssh manually, yes.. but not via juju
[14:35] <ashipika> Permission denied (publickey,password).
[14:36] <marcoceppi> ashipika: that's fine, manually ssh for now
[14:36] <ashipika> but how come the state is missing?
[14:37] <marcoceppi> ashipika: that's what I'm trying to help you figure out
[14:37] <marcoceppi> ashipika: again, manual provisioning is not a stable juju feature yet
[14:37] <ashipika> i understand that.. how can i help decypher this problem?
[14:38] <marcoceppi> ashipika: again, ssh in to the server and I can help you troubleshoot the problem :)
[14:38] <ashipika> i'm in :)
[14:38] <marcoceppi> ashipika: run `initctl list | grep juju` what do you get?
[14:39] <ashipika> jujud-machine-4 start/running process 2869
[14:40] <marcoceppi> ashipika: can you install pastebinit then run `cat /var/log/juju/machine*.log | pastebinit`
[14:41] <ashipika> http://paste.ubuntu.com/6453560/
[14:42] <marcoceppi> ashipika: that's the problem
[14:42] <marcoceppi> ashipika: where is the bootstrap node?
[14:42] <ashipika> on another machine.
[14:42] <marcoceppi> ashipika: is that other machine your local machine?
[14:42] <ashipika> no
[14:43] <ashipika> the bootstrap machine is at <IP_ADDRESS>, while this machine is <IP_ADDRESS>
[14:43] <marcoceppi> ashipika: the address it's getting for the bootstrap node is ubuntu.; this leads me to believe that the bootstrap node doesn't have proper hostname setup for it
[14:43] <marcoceppi>  dialing "wss://ubuntu.:37017/"
[14:43] <ashipika> oh! it's trying to contact mongodb at ubuntu.?
[14:44] <marcoceppi> ashipika: well, it's trying to contact the bootstrap API at ubuntu.
[14:44] <ashipika> ok
[14:44] <marcoceppi> which connects to mongo, so essentially yes
[14:44] <ashipika> so i need to fix hostname at the bootstrap host?
[14:44] <marcoceppi> ashipika: it's got a bad address resolution. make sure the bootstrap machine has proper hostname that's mappable in the system
[14:44] <marcoceppi> yeah
[14:45] <ashipika> why not ip? why hostname?
[14:45] <marcoceppi> ashipika: what did you set as the bootstrap node for the manual provisioner?
[14:45] <marcoceppi> again, improvements to this feature are being made
[14:45] <marcoceppi> this isn't the final product for manual provisioning
[14:45] <ashipika>  maas-server: 'http://<IP_ADDRESS>/MAAS/'
[14:45] <ashipika> in the .yaml file
[14:46] <ashipika> sorry.. wrong file..
[14:46] <ashipika> but i set the ip for the boostrap-host: <IP_ADDRESS>
[14:46] <marcoceppi> interesting
[14:46] <marcoceppi> ashipika: can you `cat /var/log/cloud-init/*.log | pastebinit`
[14:47] <ashipika> on the bootstrap server?
[14:47] <marcoceppi> ashipika: on the machine-4
[14:47] <ashipika> no cloud-init folder in the log folder..
[14:47] <marcoceppi> how about a cloud-init.log in /var/log?
[14:48] <ashipika> nope
[14:48] <marcoceppi> hum, cloud-init had to run somewhere on that machine
[14:49] <ashipika> i can't see any logs
[14:51] <marcoceppi> ashipika: apt-get install tree, `tree /var/log | pastebinit`
[14:52] <ashipika> http://paste.ubuntu.com/6453610/
[14:55] <makara> marcoceppi, no, I terminated it
[14:56] <marcoceppi> makara: okay, well run juju destroy-environment to clean up, then try bootstrapping again. This time use --debug and --show-log flags. If after a few moments you can't run juju status and get output, sanitize the log and paste it for me
[14:57] <marcoceppi> ashipika: interesting. No cloud-init log anywhere. Regardless, update the host of your bootstrap node, stop the juju-machine-4 upstart, delete /etc/init/juju-*, then try adding it again
[14:58] <ashipika> ok.. thank you very much
[14:59] <makara> marcoceppi, I'll post it tomorrow 6 UCT
[14:59] <marcoceppi> makara: I'm EST (UTC-5) so I won't get it for a few hours, but I'll look for it when I awake
[14:59] <makara> k
[15:49] <X-warrior> is anybody using elasticsearch/logstash with juju? I'm trying the elasticsearch charm but it is failling
[15:51] <marcoceppi> X-warrior: I know it's been deployed a few times, where is it failing?
[15:51] <X-warrior> on deploy, the hook start is failling ' HOOK WARNING: ElasticSearch may have failed to start.'
[15:54] <marcoceppi> thats not very helpful
[15:57] <X-warrior> I guess it is not juju faults, it is something related to ElasticSearch, let me dig into it
[15:57] <X-warrior> brb
[18:37] <x-warrior> What does this means? "ERROR no CA certificate in environment configuration" ?
[18:39] <x-warrior> I'm able to connect to one environment, but when I try to connect to otherone, I receive this error
[18:50] <marcoceppi> x-warrior: did you bootstrap from that machine or another machine?
[18:50] <x-warrior> marcoceppi, another machine
[18:51] <marcoceppi> x-warrior: yeah, that's why
[18:51] <marcoceppi> x-warrior: you need to copy the certs from that machine to this one
[18:51] <x-warrior> you mean .ssh certs?
[18:51] <x-warrior> because I'm able to ssh directly to the machine
[18:51] <x-warrior> without using juju
[18:57] <x-warrior> marcoceppi, have to go now, talk about this with u tomorrow, have a good one
[18:57] <x-warrior> ty
[20:15] <InformatiQ> i was searching for a directory server in the charm store, didn't find anything i know. anyone has an idea if there is one?
[20:16] <InformatiQ> i would tend to see that as an important part


[09:49] -queuebot:#ubuntu-ci-eng- paelzer, https://bileto.ubuntu.com/#/ticket/4717 Generating diffs
[09:50] -queuebot:#ubuntu-ci-eng- paelzer, https://bileto.ubuntu.com/#/ticket/4717 Successfully built
[15:05] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Successfully built (jammy/systemd). Uploading build (jammy/netplan.io)
[15:25] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Diff missing (jammy/netplan.io). Successfully built (jammy/systemd)
[15:26] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Generating diffs
[15:27] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Successfully built
[16:25] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Proposed pocket (jammy/glib2.0). Successfully built (jammy/netplan.io, jammy/systemd)


[00:02] <lilstevie> ptl, is sound working in general?
[00:14] <ptl> lilstevie: no. The only sound I ever heard in nexus7 ubuntu was the sound or the changing volume
[00:14] <ptl> and even then the volume always starts muted and I have to raise it up
[00:14] <ptl> then, it doesn't work
[00:14] <ptl> tried with the bare minimun... gst123, a console program that uses regular gstreamer
[00:15] <ptl> first time: reboot
[00:15] <ptl> second time: says it's playing. Does not produce any sound!
[00:15] <lilstevie> ptl, you did read the thing that says sound only works after suspend/resume yes?
[00:31] <vanhoof> ogra-cb_: ah you're awake, just sent you some bits to check out
[00:31] <vanhoof> ogra-cb_: thats much easier btw versus what I sent over abootimg wise
[01:17] <ptl> lilstevie: good call. I think I read that, but I forgot.
[07:47] <dholbach> good morning
[10:32] <ogra_> look, images ! http://cdimage.ubuntu.com/daily-preinstalled/20121121/
[10:32] <ogra_> (not the slightest idea if anything works with them though)
[10:40] <dholbach> ogra_, when are the images moving over to raring? ;-)
[10:40] <ogra_> these are raring ones ;)
[10:41] <dholbach> oh wow
[10:41] <ogra_> they are unlikely to work yet, just downloading one to test
[10:41] <dholbach> is this stock raring? or are there modifications which still need to get into the archive?
[10:41] <ogra_> the nexus7 settings package
[10:42] <dholbach> that's all? awesome
[10:42] <dholbach> go go go!
[10:42] <ogra_> but first of all i need to get oem-config to work
[10:42] <ogra_> (it might already, cant say until i have tested one :) )
[10:43] <ogra_> download will still take 45min or so
[10:43] <dholbach> cool - let me know how it goes :)
[10:43] <ogra_> will do
[10:43] <ogra_> i will actually blog once they are usable :)
[10:44] <ogra_> though i guess the nux patch is still missing
[10:44] <ogra_> until thats there the desktop will be a mess
[10:44] <ogra_> (but the installer part up to teh desktop should work at least)
[10:44] <day> ogra_: is the ubuntu-arm branch officially supported?
[10:45] <ogra_> ubuntu-arm branch ?
[10:45] <ogra_> rmhf is an official arch if you mean that
[10:45] <ogra_> *armhf
[10:46] <ogra_> the nexus image is built from universe using a universe kernel ....
[10:46] <day> ogra_: i guess i mixed things up quite a bit :P
[10:46] <ogra_> so there is no official canonical commitment to security of the kernel etc ... i.e. its "community supported"
[10:46] <day> ogra_: ty
[10:47] <ogra_> we have officially supported arches like the panda, highbank (calxeda) and armadaxp (marvell)
[10:47] <ogra_> btw panda ...
[10:48] <ogra_> ppisati, what are your kernel plans for raring wrt panda ?
[10:48] <ogra_> to support the GLES stuff we will still need the ton of patches
[10:49] <ogra_> (unless that changed since quantal)
[10:50] <ogra_> victorp, fyi http://cdimage.ubuntu.com/daily-preinstalled/current/ (untested and likely not working yet)
[10:50] <victorp> ogra_, \o/
[10:51] <ogra_> victorp, no blogging yet ! :)
[10:51] <victorp> does it mean that at least I can ask vanhoof to point his super installer to it ? :)
[10:51] <ogra_> (not before we at least know the installer part works)
[10:51]  * victorp puts down wp
[10:51] <ogra_> :)
[10:52] <ogra_> nothing in these images has been tested yet, its all new code so give me a bit to make sure it works
[10:52] <victorp> ogra_, I know that you are getting the USB creator to work with this, but what does that actually mean for the user?
[10:52] <ogra_> additionally the rootfs img is still to big
[10:52] <victorp> ogra_, at least something is being spitted out! thanks
[10:53] <ogra_> for the user it means that usb-creator pops up offering him an install as soon as he attaches a nexus7 in flash mode to a raring ubuntu PC
[10:53] <ogra_> fotr pre-raring i guess chris should just go on maintaining the zenity installer
[10:54] <ogra_> i doubt the changes to usb-creator will be easily backportable ( xnox may correct me :here ) )
[10:54] <xnox> ogra_: in a ppa, why not =)
[10:55] <ogra_> heh, k
[10:55] <ppisati> ogra_: my hope was to fold the omap4 branch into master
[10:56] <ppisati> ogra_: and import only: dvfs + patches to make pvr-omap work
[10:56] <ogra_> ppisati, please talk to robclark if the GLES bits can workj with that
[10:56] <ogra_> yeah
[10:56] <ppisati> ogra_: i'll do
[10:56] <dholbach> ogra_, the nux fix might be https://code.launchpad.net/~unity-team/nux/nux.depth-texture-detection-support/+merge/134729 (which hopefully lands soon)
[10:56] <ogra_> its just important that these bits work as long as we go on to provide desktop images for pandas
[10:56] <ppisati> robclark: ^
[10:57] <ogra_> (i wouldnt mind dropping them though, but we need one reference platform and nexus is not fully supported)
[10:57] <ppisati> robclark: we where wondering what it takes to make pvr-omap4 work with vanila upstream
[10:57] <ppisati> robclark: do you have a bare minimum amount of patches that we need to take into account?
[10:58] <ogra_> dholbach, yeah, thats the one
[11:04] <lilstevie> dholbach, ogra_, will that land in quantal or raring?
[11:05] <dholbach> lilstevie, I don't know - the folks in #ubuntu-unity should know though
[11:06] <ogra_> well, definitely in raring
[11:06] <ogra_> no idea if any backport SRUs are planned
[11:06] <ogra_> (you could ask on the merge request)
[11:07] <lilstevie> ogra_, ok, not a major thing, I think TheMuso and I decided we were going to build tf201 images with gnome anyway for the time being, it can wait until raring for unity I guess :p
[11:08] <lilstevie> oh btw ogra_ have you tried using the brcmfmac firmware for the bcm4330 rather than the android one?
[11:08] <ogra_> yes, i didnt try very hard though and couldnt get it to work
[11:11] <lilstevie> hm ok
[12:11] <ogra-cb_> yay, it boots and seems to unpack the tarball
[12:11]  * ogra-cb_ waits in awe
[12:16] <ogra-cb_> *twiddle thumbs*
[12:17] <dholbach> ogra-cb_, http://www.youtube.com/watch?v=0Wi8Fv0AJA4
[12:18] <ogra-cb_> haha
[12:19] <ogra-cb_> hmm, k, seems the unpacking finished ... no X yet though
[12:20] <ogra-cb_> doesnt seem to come up :(
[12:24] <ogra-cb_> sniff
[12:24] <Orik> :c
[12:24] <ogra-cb_> and rebooting gets me into an endless reboot loop
[12:40] <ogra-cb_> hmm, k looks like thats the old plymouth issue
[12:40] <ogra-cb_> whee !
[12:40] <ogra-cb_> oem-config
[12:40] <lilstevie> ogra-cb_, I find it odd that you have an issue with plymouth
[12:41] <ogra-cb_> well, the bootloader sets console=none
[12:41] <ogra-cb_> plymouth picks that up
[12:41] <lilstevie> ah, I override that
[12:41] <ogra-cb_> i cant
[12:42] <ogra-cb_> it comes hardcoded from the bootloader
[12:42] <ogra-cb_> we set a second console= arg, but plymouth only picks up the first
[12:42] <lilstevie> you could hardcode the command line in the boot.img :p
[12:43] <ogra-cb_> thats exactly what i do
[12:43] <lilstevie> then the bootloader set cmdline should vanish 0.o
[12:43] <ogra-cb_> the bootloader still prefixes it with its own stuff
[12:43] <lilstevie> the hell
[12:45] <ogra-cb_> k, so there is no touchscreen support at all, X comes up in portrait but beyond that it looks ok
[12:46] <ogra-cb_> i'm nearly through oem-config ... using a kbd/mouse
[12:46] <ogra-cb_> oh
[12:46] <ogra-cb_> suddenly the touchscreen works
[12:46] <ogra-cb_> completely inverted though
[12:52] <ogra-cb_> yay
[12:52]  * ogra-cb_ sees a desktop ... garbled unity elements indeed
[12:55] <ogra-cb_> sigh
[12:56] <ogra-cb_> corrupt filesystem
[12:58] <ogra-cb_> ok, so most of this will be fixed by the settings package
[12:58]  * ogra-cb_ re-flashes again
[13:05] <diwic> Hi, I'm having a side project (fluidsynth) where it would be interesting to see if NEON optimisations would speed things up. Assuming those tests are successful, how do we enable those optimisations by default?
[13:05] <diwic> I mean, we can't just compile with fpu=neon for the standard armhf build, can we?
[13:05]  * lilstevie needs to stop procrastinating and finish his project for the tf201
[13:05] <lilstevie> diwic, not all armv7 hardware includes NEON
[13:06] <diwic> lilstevie, exactly, so what is the standard/recommended way of doing this?
[13:06] <diwic> so NEON is used automatically where available, and fallback code otherwise
[13:08] <ogra-cb_> diwic, there should be a way to do a runtime check
[13:08] <ogra-cb_> so you can switch code paths at runtime if your code supports it
[13:09] <ogra-cb_> alternatively you can build the binary twice and create a -neon binary (or package)
[13:09] <diwic> ogra-cb_, hmm, that sounds interesting
[13:09] <ogra-cb_> by default all armhf packages should not be neonized
[13:10] <ogra-cb_> since there are still many a7 SoCs that dont support neon
[13:10] <lilstevie> which is sad
[13:11] <diwic> ogra-cb_, I was hoping there was a wiki page or something about how to best deal with this
[13:12] <ogra-cb_> there might be a linaro page for it, not sure
[13:13] <ogra-cb_> iirc the runtime selection had to do with using /proc/self/auxv
[13:17] <diwic> hmm, the code for pulseaudio reads /proc/cpuinfo
[13:21] <ogra-cb_> that might work as well
[13:21] <ogra-cb_> just grepping fpr neon i guess
[13:22] <diwic> but long story short, this is just something every new project has to invent the wheel again
[13:23] <ogra-cb_> yeah, a bit annoying
[13:23] <ogra-cb_> thats why i think there is some better linaro solution
[13:33] <ogra-cb_> xnox, we shoould really look at the startyup time of ubiquty-dm ... not sure if it is so slow in non oem-config mode, but running oem-config i nearly sit a minute at a localhos login prompt before X even starts
[13:34] <xnox> ogra-cb_: *sigh*
[13:34] <ogra-cb_> it might be less odd if there is a splash
[13:34] <xnox> ogra-cb_: do these comments mean you have an image with oem-config for me play around with?
[13:35] <ogra-cb_> xnox, a broken one but yeah
[13:35] <xnox> ogra-cb_: define broken =)
[13:35] <xnox> a little, a lot, not enough?
[13:35] <ogra-cb_> the tarball installer accidentially unmounts /root after unpacking
[13:35] <ogra-cb_> which leaves you with a black screen
[13:36] <ogra-cb_> rebooting at the point where you are sure it is done gets you into a normal boot though
[13:36] <ogra-cb_> xnox, http://cdimage.ubuntu.com/daily-preinstalled/current/
[13:36] <ogra-cb_> grab both files
[13:37] <xnox> ack
[13:37] <ogra-cb_> edit the bootimg with abootimg to point to tty0 instead of tty1
[13:37] <ogra-cb_> gunzip the img.gz
[13:37] <ogra-cb_> fastboot erase boot
[13:37] <ogra-cb_> fastboot erase userdata
[13:37] <ogra-cb_> fastboot flash boot /path/to/*.bootimg
[13:38] <ogra-cb_> fastboot -S 630M flash userdata /path/to/*.img
[13:38] <ogra-cb_> thats how i flash here
[13:38] <ogra-cb_> and after that: fastboot reboot
[13:38] <ogra-cb_> oh, all of that needs sudo atm
[13:39] <Tassadar> what does the "-S" param mean? Oo
[13:39] <ogra-cb_> transfer in chunks
[13:40] <ogra-cb_> xnox, note that the touchscreen is completely broken, you need kbd and mouse
[13:41] <ogra-cb_> well, not broken but inverted
[13:42] <ogra-cb_> fix for the tarball stuff is uploaded already
[13:42] <ogra-cb_> next image wont have the issue anymore
[13:42] <ogra-cb_> for the rest we need the default-settings package now
[13:47] <xnox> ack.
[14:00] <ogra-cb_> new image build running
[14:58] <ppisati> do you know if there's a place where i can find a maverick armel image?
[15:00] <ogra-cb_> oof
[15:00] <ppisati> oof?
[15:00] <ppisati> woof?
[15:02] <ogra-cb_> ppisati, theoretically on http://old-releases.ubuntu.com/releases/
[15:02] <ppisati> nope
[15:02] <ogra-cb_> but that doesnt have any arm stuff it seems
[15:02] <ppisati> doesn't arm maverick stuff
[15:02] <ogra-cb_> so probably a cjwatson or infinity question
[15:03] <ppisati> is there a script to recreate an image?
[15:03] <ppisati> since the archives are still there
[15:03] <ogra-cb_> well, there should also be images somewhere
[15:03] <ogra-cb_> i'm pretty sure they havent been thrown away
[15:04] <achiang> brendand: um, daniel *is* working on fixing the button1 bug
[15:05] <ppisati> infinity: ^
[15:05] <brendand> achiang, ok - but In Progress -> Confirmed is not a correct transition then
[15:05] <ogra-cb_> achiang, well, he did set it from in progress to confirmed
[15:06] <brendand> achiang, In Progress -> Confirmed says something like 'I was working on it, but I give up and can't figure it out'
[15:06] <achiang> might be better to ask than to accuse
[15:12] <brendand> it wasn't intended to sound accusatory, probably would have been better phrased as a question
[15:14] <ppisati> ogra-cb_: ah! i found an obscrure mirror that still had it :)
[15:14] <ogra-cb_> heh
[15:14] <ogra-cb_> well, i know GrueMaster had a complete mirror carrying all arm images ever built
[15:14] <ppisati> from Bangkok
[15:14] <ogra-cb_> but he's gone
[15:18] <vanhoof> ogra-cb_: lol
[15:18] <vanhoof> ogra-cb_: /me curses
[15:18] <achiang> brendand: ok, fair enough. it might be nice to follow up with daniel and explain that you were just asking him a question.
[15:20] <ogra-cb_> vanhoof, heh
[15:21] <brendand> achiang, ok followed up on the bug (hopefully politely :) )
[15:21] <ogra-cb_> vanhoof, achiang .... in case you missed the backlog http://cdimage.ubuntu.com/daily-preinstalled/current/
[15:21] <achiang> brendand: thanks. :)
[15:21] <ogra-cb_> not working yet, fixes are uploaded and a new build is running
[15:22] <achiang> woo hoo!
[15:22] <brendand> achiang, and apologies again. in my experience it's very common to see people misusing bug states - but i agree that there's no need to be blunt in response
[15:22] <ogra-cb_> you can manually work around the issues though, xnox is just guineapiggin :)
[15:22] <achiang> brendand: sure, no worries. i just didn't want to demotivate the guy who is fixing one of our hardest bugs. ;)
[15:24] <achiang> ogra-cb_: so with that, i believe the nux bug is our only remaining issue
[15:25] <vanhoof> ogra-cb_: nice!
[15:25] <ogra-cb_> achiang, well, i need to get to the settings, currently you pretty well notice that they are missing
[15:25] <ogra-cb_> and it is still to big until we did the seed change
[15:26] <ogra-cb_> so it wont work for everyone (fastboot -S works fine for me here)
[15:27] <ogra-cb_> i would also like to look into rersizext2fs instead of having to produce a bunch of differently sized images
[15:28] <achiang> brendand: now it's my turn to apologize to you. guess daniel *did* move on to other things :-/
[15:28] <vanhoof> ogra-cb_: +1 there
[15:32] <xnox> ogra-cb_: is that image one size fits all?
[15:33] <xnox> ogra-cb_: or which size is it currently for?
[15:34] <ogra_> xnox, nope, currently its the smalles common denominator ...
[15:34] <ogra_> 6G
[15:34] <xnox> ack
[15:34] <ogra_> we have two options, one is to provide three images ... and the other is to grow the rootfs on the fly
[15:34] <ogra_> i fear the latter will not work properly though
[15:35] <ogra_> by experience i had with the fastboot ext4 version
[15:37] <Tassadar> what about providing just update.zip for recovery?
[15:38] <ogra_> feel free to work on something like that
[15:39] <ogra_> for raring the plan is to just to replicate what we did in quantal and improve that ... there are no plans to develop new image types from scratch in the ubuntu infrastructure atm
[15:40] <Tassadar> it should be simple, just erase everything and extract boot.img and rootfs.tar.gz
[15:40] <ogra_> well, the files are there now :)
[15:40] <ogra_> feel free to play with them
[15:41] <Tassadar> I think I'll do that
[15:41] <ogra_> (though probably wait for the next build, so that you at least get through into the installer)
[15:41] <ogra_> that one *should* get you into oem-config
[15:41] <Tassadar> I have to make something so that my multi-boot thing can edit the update-initramfs files
[15:41] <ogra_> ugh
[15:42] <ogra_> that sounds very ugly
[15:42] <Tassadar> yeah)
[15:42] <Tassadar> but well, I don't really feel like distributing modified ubuntu image
[15:42] <ogra_> do you know that there is initiative for getting grub running under arm ?
[15:42] <ogra_> in linaro
[15:42] <Tassadar> whau
[15:42] <ogra_> that will just get ou multiboot for free
[15:42] <ogra_> *you
[15:43] <Tassadar> that sounds...complicated to do Oo
[15:43] <ogra_> as complicated as on x86 :)
[15:43] <Tassadar> well, on hard drive you can mess with partitions
[15:44] <ogra_> well, you dont need to mess with them
[15:44] <Tassadar> I need to separate OS-es somehow
[15:45] <ogra_> no, you just need to be able to switch between boot images
[15:45] <ogra_> the only issue that leaves is that boith OSes want to upgrade the kernel in the same place if it comes to that
[15:46] <ogra_> and thats something thats not easily fixable ... but you will hit that issue in all variants of dial booting
[15:46] <Tassadar> hmm, still seeems a bit complicated to do
[15:46] <ogra_> which is why i suggest since day one to put the ubuntu bootimg into recovery and be done
[15:46] <Tassadar> switch between boot images == flash new ones?
[15:46] <ogra_> no
[15:46] <ogra_> just switch
[15:46] <Tassadar> so...they, like, wanna change the bootloader?
[15:47] <ogra_> they update mmcblk0p2 if a new kernel shows up (or in case of ubuntu even if a package that ships initramfs bits gets ionstalled)
[15:51] <RaYmAn> ogra_: kexec or similar? :P Sadly, that's the most promising option atm..You can't replace bootloader, even if you had a working u-boot.
[15:51] <Tassadar> hmm
[15:52] <Tassadar> I still dont really get how they switch between kernels
[15:52] <ogra_> RaYmAn, either kexec or just use what the bootloader offers already (keep android in boot and flash ubuntu to recovery)
[15:52] <Tassadar> like, where is the grub stored?
[15:52] <RaYmAn> ther'es no..grub
[15:52] <ogra_> the grub would be your bootimg
[15:53] <RaYmAn> ogra_: yeah..but then you lose recovery :) though, not much of an issue with fastboot available
[15:53] <ogra_> the bootloader would chainload it
[15:53] <ogra_> RaYmAn, right
[15:53] <ogra_> it is the price you have to pay for dual boot
[15:53] <RaYmAn> indeed. It's such a pity they locked down bootloader changes.
[15:54] <ogra_> ask the linaro guys about details for grub on arm :)
[15:54] <Tassadar> anyway, it's not like I'll stop now, when it's already working, I am just working on the UI and installation process
[15:54]  * ogra_ only heard of it third hand, i havent seen it or anything
[15:55] <Tassadar> it's a pitty I can't get kexec working, though :/
[15:55] <ogra_> well, then you would still have the issue that an android kernel update would overwrite it
[15:57] <Tassadar> custom kernels have "AnyKernel" installer, which changes only kernel (and leaves ramdisk as-is), and if you mean OTAs, well, then the user will have to go to recovery and select "inject boot.img"
[15:58] <RaYmAn> Tassadar: look at kexec-hardboot
[15:58] <RaYmAn> that'll definitely work. (I have it working on my TF201)
[15:58] <RaYmAn> It puts some requirements on the 'target' kernel, but it's minor.
[15:58] <Tassadar> yes, I did, and I got stuck on "how the hell should I reboot tegra3 via watchdog"
[15:59] <RaYmAn> you don't need to use watchdog to do it
[15:59] <ogra_> watchdog is disabled in ubuntu kernels iirc
[15:59] <ogra_> caused suspend issues
[15:59] <xnox> I am simply getting Google white logo =/
[15:59] <xnox> with the unlocked padlock
[15:59] <vagabon> hi all, I'm trying to install ubunutu on a N7. I used the ubuntu installer and it installed fine. But now I'm wondering if wifi is supposed to work ?
[15:59] <ogra_> xnox, hmm, that doesnt sound like you flashed bootimg properly
[15:59] <Tassadar> vagabon: yes, it is
[16:00] <Tassadar> works for me
[16:00] <Tassadar> well..using one of the ooold images)
[16:00] <vagabon> Tassadar: hmm how am I supposed to enter the key ?
[16:00] <ogra_> vagabon, with the keyboard
[16:00] <ogra_> that pops up on your screen
[16:00] <vagabon> hmm it doesn't for me
[16:01] <Tassadar> try reboot
[16:01] <vagabon> ok
[16:01] <ogra_> it should as soon as the focus goes into the text input field
[16:01] <Tassadar> it glitches sometimes
[16:01] <RaYmAn> Tassadar: volatile u32* reg = (u32*)(0x7000E400); reg |= 0x10; - that should reboot instantly (even from within android or linux)
[16:01] <Tassadar> okay, I'll look to that again once I finish this, thanks
[16:02] <ogra_> RaYmAn, instantly as in ... it will take care for syncing your open files etc and flush the memory to disk and properly unmount it ? or instantly like pulling out AC and battery at the same time ?
[16:03] <RaYmAn> ogra_: instantly as in, instantly.. The idea is that you execute it in the kexec shutdown sequency, so only once it's already almost turned off
[16:03] <Tassadar> pulling the battery I guess)
[16:03] <RaYmAn> it's the same effect as if the watchdog timed out
[16:03] <ogra_> ah
[16:03] <RaYmAn> it resets the main clock controller iirc
[16:03] <Tassadar> Oo
[16:04] <RaYmAn> Tassadar: my kexechardboot for n7 is here: https://github.com/EnJens/kernel_tf201_stock/tree/android-tegra-nv-3.1-kexec
[16:04] <Tassadar> heh
[16:04] <RaYmAn> err
[16:04] <RaYmAn> not n7
[16:04] <RaYmAn> tf201
[16:05] <Tassadar> I was just writing "could you send me a link..." :D
[16:05] <Tassadar> because all I could find was hardboot for ...atrix I think
[16:05] <vagabon> otherwise can I add a static config file in the rootfs somewhere so I can init the wifi connection ?
[16:05] <ogra_> vagabon, you can use /etc7network/interfaces
[16:06] <ogra_> vagabon, http://wiki.debian.org/WiFi/HowToUse#WPA-PSK_and_WPA2-PSK
[16:07] <ogra_> the question is how you will access the rootfs :)
[16:08] <vagabon> unpack it on my host, hack it, repack, reflash... I gues
[16:08] <vagabon> ubuntu installer seems to download the images from somewhere
[16:09] <ogra_> well, wifi works for all of us
[16:09] <ogra_> there are plenty of nexus7 with ubuntu out in the wild and we havent had a single bug report yet
[16:09] <vagabon> ok I'm reflashing the images and give it a new test
[16:09] <ogra_> repacking is quite a task
[16:10] <vagabon> ogra_: does Network manager handle the wireless connection?
[16:10] <ogra_> yes
[16:10] <Tassadar> hmm, is it possible to just add some files into that tgz file, or do I have to unpack it and then pack again?
[16:10] <ogra_> you might be able to add
[16:10] <ogra_> not sure
[16:10] <Tassadar> hmm I hope I will
[16:11] <Tassadar> it's like 2 files only
[16:11] <ogra_> as long as you use the same optiuons that were used for tarring it up it should all be fine
[16:12] <vagabon> ogra_: cool this time the virtual kb pop up :)
[16:12] <ogra_> ah, thats how it sould be :)
[16:13] <vagabon> ogra_: does a sshd is running on the tablet ?
[16:13] <vagabon> ogra_: is a sshd  running on the tablet ?
[16:13] <ogra_> nope
[16:13] <ogra_> sudo apt-get install openssh-server
[16:13] <vagabon> why not install it by default ?
[16:13] <ogra_> we used to have it preinstalled, but during UDS there were some 100s of devices around, all using our image with the same user and password
[16:14] <ogra_> so that wouldnt have been clever
[16:14] <ogra_> and after all its just an apt-get away :)
[16:14] <vagabon> using a virtual kb is a PITA :)
[16:14] <ogra_> well, i used the nexus7 for three weeks as my main machine while developing the image
[16:14] <ogra_> you get used to it after a while
[16:15] <Tassadar> by the way, I didn't find default root password mentioned anywhere on the nexus 7 wiki
[16:15] <ogra_> its annoying in the beginning, i agree :)
[16:15] <vagabon> you're more skilled than I am :)
[16:15] <Tassadar> and, not even the "ubuntu" password, for that matter)
[16:15] <ogra_> Tassadar, thats because there is none ... its ubuntu
[16:15] <vagabon> entering a WPA key is just a nightmare for me
[16:15] <ogra_> the ubuntu password is ubuntu and i'm sure it at least was once mentioned on the wiki
[16:17] <vagabon> just out of curiosity, is the virtual kbd part of unity ?
[16:20] <xnox> vagabon: package onboard
[16:20] <xnox> it's part of ubuntu a11y packages =)
[16:21] <Tassadar> RaYmAn: when calling the kexec userspace tool, what parameters do I have to load? I mean it allows to specify ramdisk and command line, what if I specify none of these?
[16:21] <Tassadar> will it you ramdisk and cmd line from current kernel?
[16:22] <RaYmAn> not afaik
[16:22] <RaYmAn> I assume you use the patched kexec tool, right?
[16:23] <Tassadar> yeah
[16:23] <vagabon> xnox: which one ?
[16:23] <vagabon> a11y ?
[16:23] <xnox> vagabon: $ apt-get install onboard
[16:23] <vagabon> ok thanks
[16:24] <vagabon> xnox: actually I'm wondering how the kbd is started automagically...
[16:24] <ogra_> it detects input field focus
[16:24] <ogra_> as soon as an input fiel is focused, it will pop up
[16:24] <ogra_> i think it asks the window manager
[16:25] <xnox> vagabon: it has been around for a while as our on-screen keyboard as accessibility feature for those who cannot use a regular keyboard.
[16:25] <vagabon> xnox: ok, but I'm just starting to discover ubuntu.
[16:25] <vagabon> xnox: does that mean that the package should work with any DEs ?
[16:26] <xnox> yes.
[16:26] <ogra_> yes
[16:26] <vagabon> cool
[16:26] <vagabon> I'will try to use it here (xfce4)
[16:26] <xnox> vagabon: the same way cursor | flashes when you need to input text =))))))
[16:33] <xnox> I am not having joy with the daily: either I am dropped into initramfs shell or it doesn't boot.
[16:36] <ogra-cb_> xnox, did you see it unpacking the tarball ?
[16:37] <xnox> nope
[16:37] <ogra-cb_> hmm, that sounds very wrong
[16:37] <ogra-cb_> it definitely did that here
[16:37] <ogra-cb_> did you do the fastboot erase steps before flashing ?
[16:39] <ogra-cb_> it should clear the screen and then start verifying the tarball structure ... after that it will unpack and tell you that it takes a few min
[16:39] <xnox> yeap
[16:39] <Neko> rsalveti, nudge? have any idea on why I might get some XPutImage BadMatch running glmark2?
[16:39] <xnox> i am getting mounting /dev/mmcblk0p9 on /root failed: Invalid argument
[16:39] <ogra-cb_> the next step was broken for me ... but up to there everything worked as expected
[16:39] <xnox> but the tarball unpack was not shown....
[16:39] <ogra-cb_> right, thats the broken step
[16:40] <vagabon> xnox: the kbd doesn't pop up when the application search input field is selected
[16:40] <ogra-cb_> xnox,  the quantal image worked for you, right ?
[16:40] <xnox> ogra-cb_: yeah.
[16:40] <ogra-cb_> vagabon, yep, known bug
[16:40] <xnox> vagabon: is onboard running in the background?
[16:40] <xnox> ah, known bug. ok.
[16:41] <vagabon> ok
[16:41] <Tassadar> by the way, what will you use to determine the /data partition in tarball-installer?
[16:41] <ogra-cb_> you can go to the onboard settings and switch on "show a floating button"
[16:41] <vagabon> then where can I find a terminal launcher ?
[16:41] <ogra-cb_> then you can force it on if you need it
[16:41] <ogra-cb_> even if the input field detection doesnt work
[16:41] <ogra-cb_> vagabon, press ctrl+alt+t
[16:42] <vagabon> cool
[16:42] <ogra-cb_> xnox, so i guess you should wait for the next build
[16:42] <xnox> =/
[16:42] <xnox> ack
[16:42] <vanhoof> ogra-cb_: should it fail?
[16:42] <ogra-cb_> theoretically that shoudl fix the mount issues ... but i'm not really sure whats going on there if you dont see it unpack
[16:43] <vanhoof> ogra-cb_: sounds similar to what we saw using -S before if not
[16:43] <ogra-cb_> vanhoof, oh, hmm
[16:43] <vanhoof> ogra-cb_: I believe some folks saw that on 16gb n7's
[16:43] <ogra-cb_> xnox, you could trz without the -S option
[16:43] <Tassadar> xnox: which nexus 7 do you have? I mean wifi/3g 8/16/32gb?
[16:43] <vanhoof> and we yanked -S out of the installer
[16:43] <ogra-cb_> vanhoof, i know
[16:44] <ogra-cb_> but the current image is 750M
[16:44] <vanhoof> ah
[16:44] <xnox> i have 16G and without -S it doesn't flash.
[16:44] <ogra-cb_> wont work without -S until the ubuntu seeds have been split
[16:44] <ogra-cb_> yeah, it exhausts the ram
[16:44] <vanhoof> ogra-cb_: im trying on a 8gb now
[16:44] <xnox> blimey, the vol up/down in the bootloader have shutdown option.
[16:44] <ogra-cb_> my 8G here worked fine with -S
[16:44] <xnox> \0/
[16:45]  * xnox was stuck in restart loop for a second here.
[16:45] <ogra-cb_> heh
[16:45] <ogra-cb_> getting it started up is sometimes a pain
[16:45] <ogra-cb_> after such a loop
[16:45] <RaYmAn> ogra-cb_: cat ubuntu.img|adb shell dd of=/dev/block/mmcblk0p10 while in recovery? ;)
[16:45] <RaYmAn> poor mans fastboot, heh.
[16:45] <ogra-cb_> no adb :P
[16:46] <RaYmAn> darn
[16:46] <ogra-cb_> we discussed that in advance :) neither update.zip nor any adb way are an option for the official images
[16:46] <Tassadar> and it's event funnier when you accidentally press volUp when holding power-up)
[16:46] <RaYmAn> fastboot boot an image that sets up mmcblk0p10 as UMS?
[16:46] <ogra-cb_> well, fix -S woudl eb the best option
[16:46] <ogra-cb_> *be
[16:47] <RaYmAn> I suppose
[16:47] <ogra-cb_> or alternatively just dont use oversized images as we do atm :)
[16:47] <ogra-cb_> i was actually pondering to use bzip2 for the tarball
[16:48] <ogra-cb_> but that will break rsync/zsync abilities
[16:48] <RaYmAn> wouldn't a fastboot boot'ed image work for offline resizing after write? I'm not sure how much actual data is in the .img
[16:49] <ogra-cb_> 3-4G
[16:49] <ogra-cb_> iirc
[16:49] <RaYmAn> ah, nevermind then
[16:49] <ogra-cb_> ah, i lied
[16:50] <ogra-cb_> 2-3G actually
[16:50] <ogra-cb_> the pint with resizing is that when i tried any of the ext2fs tools in the past it resulted in an unbootable corrupt fs
[16:51] <ogra-cb_> fastboot does anything to the ext4
[16:51] <ogra-cb_> else a simple resizext2fs would do
[16:52] <RaYmAn> have you tried doing it iwth an ext3 image?
[16:54] <ogra-cb_> i havent even tried it with ext4 yet :)
[16:54] <ogra-cb_> i'll get to that next
[16:54] <ogra-cb_> i know that a mkfs.ext4 definitely produces something the kernel cant boot
[16:54] <RaYmAn> the nvidia bootloaders support for ext4 has been...spotty at best
[16:55] <ogra-cb_> its the kernel
[16:55] <ogra-cb_> the bootloader is long gone at that point
[16:55] <ogra-cb_> i'm usually operating from an initrd shell when trying such stuff
[16:55] <RaYmAn> hm
[16:55] <RaYmAn> so what you're saying is that if you do mkfs.ext4 on a device, it refuses to mount it after reboot?
[16:56] <ogra-cb_> it mounts redonly and there is no way to get it properly out of that state
[16:57] <RaYmAn> peculiar
[16:57] <ogra-cb_> you can force it into RW but it will always be recognized as having errors on boot
[16:58] <vanhoof> ogra-cb_: what size are you specifying for -S, /me finally finished download
[16:59] <ogra-cb_> i took 630M iirc
[17:02] <ogra-cb_> http://paste.ubuntu.com/1375201/
[17:03] <vanhoof> cool, yeah didnt have scrollback just wanted to confirm
[17:03] <vanhoof> rebooting now :)
[17:04] <ogra-cb_> it will fail with a black screen after untarring, a reboot makes it work though
[17:04] <ogra-cb_> at least that worked for me
[17:04] <vanhoof> cool, determining structure now
[17:04] <ogra-cb_> yeah, thats definitely further than xnox got
[17:05] <ogra-cb_> i actually wonder if we can drop the structure check now
[17:05] <ogra-cb_> it takes a lot of time and we dont have any subdirs in the official tarballs ... so there is nothing to strip
[17:09]  * vanhoof waits
[17:17] <vanhoof> ogra-cb_: flashed, then dumped me to busybox after a few mount errors
[17:17] <ogra-cb_> great, a reboot should get you onto oem-config
[17:17] <vanhoof> ogra-cb_: rebooted, not it looks like its attempting to boot but rebooting itself when it looks like plymouth would kick in
[17:18] <ogra-cb_> oh, k
[17:18] <ogra-cb_> well, i changed the cmdline to point to tty0 instead of tty1
[17:18] <ogra-cb_> that helped here
[17:19] <ogra-cb_> (for console= that is)
[17:19] <vanhoof> in the boot.img thats on the daily page?
[17:19]  * vanhoof checks
[17:19] <ogra-cb_> the next image will have that and an umount fix
[17:19] <vanhoof> ah lemme try that, im still tty1 here
[17:19] <ogra-cb_> i used the bootimg modified, added a break=bottom, chrooted into the rootfs and updated the initrd from there
[17:24] <Haffe> Hi, I am looking to buy an arm system to turn into a PVR. Can I get a usb DVB-T2stick to work in ubuntu under ARM?
[17:26] <vanhoof> ogra-cb_: I should read sooner ;)
[17:26] <vanhoof> ogra-cb_: just updated boot.img, flashed that and reflashed userdata ;)
[17:27] <vanhoof> ogra-cb_: now I wish I was in CPH and got that screen from ya w/ all this fun as of late :)
[17:27] <ogra-cb_> heh
[17:40] <vanhoof> ogra-cb_: much further!
[17:41] <vanhoof> ogra-cb_: in oem-config now, although with a heavily distorted background
[17:41] <ogra-cb_> yeah, thats not arm specific i think
[17:41] <ogra-cb_> i saw an x86 bug about that yesterday or so
[17:42] <Tassadar> chmm
[17:42] <vanhoof> ogra-cb_: and portrait by default which comes with its own fun but the update to tty0 got me running, though no actual splash
[17:43] <Tassadar> RaYmAn: I applied the kexec-harboot patches, tried to do "kexec --load-harboot /tmp/zImage --mem-min=0x50000000 && kexec -e"
[17:43] <Tassadar> but it just reboots
[17:44] <RaYmAn> I assume the flashed image on boot partition has the patches?
[17:44] <RaYmAn> and that the target kernel /tmp/zImage at least has the decompressor patches?
[17:45] <Tassadar> wait, I used fastboot boot
[17:45]  * Tassadar slaps Tassadar
[17:45] <RaYmAn> it needs to be on flash, because the whole point of hardboot is that it does a full reset, then kernel detects a kexec kernel in memory and jumps to that :P
[17:46] <Tassadar> doesnt it use the kernel from recovery?
[17:50] <Tassadar> hm, now it's stuck on the google logo, let's see what ramconsole says
[17:50] <Tassadar> [  121.854978] Starting new kernel
[17:50] <Tassadar> [  121.855128] Bye!
[17:51] <Tassadar> well, that's disappointing)
[17:59] <RaYmAn> Tassadar: the value for min-memory can be quite important..I think i used 0xa0000000 or similar
[18:00] <Tassadar> honestly, I have no idea what does it mean, so..)
[18:00] <ogra-cb_> http://cdimage.ubuntu.com/daily-preinstalled/20121121.1/
[18:00] <ogra-cb_> next round
[18:01] <ogra-cb_> vanhoof, ^^^
[18:01] <vanhoof> ogra-cb_: heh
[18:01]  * vanhoof grabs
[18:01] <ogra-cb_> that should get you completely through to oem-config
[18:02] <vanhoof> ogra-cb_: cool, i'll give it a spin
[18:03] <ogra-cb_> and indeed the rootfs is now zsyncable
[18:04] <ogra-cb_> that should speed up downloading a lot
[18:04] <RaYmAn> Tassadar: stuck on logo is progress though :P
[18:05] <Tassadar> it definitely is, but I also have no debug info :/
[18:06] <Tassadar> ..and I really wonder what is it doing, it does not even open the ramconsole
[18:07] <mahmoh> robher: ping, what's ripal's nick?
[18:15] <Tassadar> RaYmAn: does normal kexec work on TF201? I mean, on nexus7, it does not even restart the device
[18:23] <Tassadar> woot
[18:24] <Tassadar> its bootin
[18:24]  * Tassadar waits for adb
[18:24] <Tassadar> ..but it is the same kernel
[20:52] <vanhoof> ogra-cb_: looks good
[20:52] <vanhoof> ogra-cb_: flashed booted right up to oem-config
[21:25]  * achiang makes an upload of unity-6.12.0 to staging ppa
[21:25] <achiang> hope it doesn't FTBFS
[21:27] <infinity> achiang: After the issues you had with diffs to tarballs, I'm thinking that's not actually very 6.12 at all. :P
[21:27] <achiang> infinity: it's ... "something"
[21:28] <achiang> probably closer to 7.0 than anything else
[21:28] <achiang> oh, but... i heard it might FTBFS on armhf
[21:28] <achiang> le sigh
[21:58]  * achiang cries. FTBFS due to bamf API change
[23:09] <lilstevie> tassadar_, you should keep an eye on mem-min, that is the minimum memory that it uses to put the zImage and initrd in. I know with the tf201 0x50000000 is outside of real memory so wouldn't work
[23:23] <tassadar_> lilstevie: can I somehow find out the memory layout of nexus7? Like, at least what is the "end" address?
[23:28] <tassadar_> aah, cat /proc/iomem i believe :ú
[23:28] <lilstevie> tassadar_, iomem, but also one of the very first things dmesg will should you is a basic mem map :p
[23:30] <tassadar_> and the kexec should load the kernel and initrd somewhere to system ram, preferably outside kernel, yes?
[23:32] <lilstevie> well of course, what good would it be loading into the kernel :p
[23:33] <tassadar_> hmm, I think I also have to change the hardboot page address, now it is in framebuffer
[23:35] <lilstevie> hah yes you probably will
[23:36] <lilstevie> I know in the first revision RaYmAn accidentally put it in the framebuffer
[23:36] <tassadar_> yes, well, the second put it precisely into nexus 7's frambuffer :D
[23:42] <lilstevie> heh


[09:14] <smeag0l> good morning
[16:45] <stgraber> highvoltage: I'm writing the skeleton of the announcement.
[16:48] <stgraber> highvoltage: http://www.edubuntu.org/news/12.04.2-release
[16:50] <highvoltage> stgraber: I guess I would just remove the insert some stuff here part
[16:51] <stgraber> highvoltage: ok, so simply not quote anything in this one?
[16:51] <highvoltage> (well, I just did it)
[16:51] <highvoltage> stgraber: unless you have some quotes gathered? I don't have anything atm
[16:52] <stgraber> highvoltage: nope, was wondering if you had any. As you don't, it's fine to just drop the paragraph altogether
[16:52] <stgraber> highvoltage: alright. I'll prepare the mirror and the e-mail announcement. Looks like we're getting close to release as we need to get 12.04.2 out before alpha2 can be released (and we want both done by EOD UK time if possible)
[16:53] <highvoltage> stgraber: who besides kubuntu is doing alpha2? ubuntu core?
[16:54] <stgraber> highvoltage: ubuntu cloud
[16:54] <stgraber> (just the cloud images, not server)
[19:07] <Tstoner98133> Hi!  I am installing edubuntu-12.04.1-dvd-amd64 on a Toshiba Satellite C655-S5212 64 bit.  the dvd installs and I come up to a graphic background screen wiht a big satellite (coincidence?) and a login prompt.  Apparently I need credentials at this point?  which I can't find reference to.  or something wrong?   Help?
[19:20] <Tstoner98133> I can now see that I did not go through the full installation process.  I selected the language as the first step, and then the next screen I see is the GUI login.  I am sure there are directions regarding this problem but I dont know where to look.  Any help :-)
[19:26] <highvoltage> Tstoner98133: hmm, while installing it will ask you for a username and password
[19:26] <highvoltage> Tstoner98133: if the setup didn't complete, it might be a good idea to restart the installation, otherwise who knows what else didn't finish up :)
[19:29] <Tstoner98133_> i tried it twice with the same result.  boot from the CD.  select language.  whir whir.  GUI login screen.  Seeing the installation guide there are a number of setup screens which should appear but don't
[19:30] <stgraber> sounds like you're either having an extremely weird installation bug (can you try installing in english?) or your DVD/iso image is somehow corrupted
[19:35] <Tstoner98133> I did select english as the install.  I saw something referring to a hardware problem causing the install to go to a shell prompt, but I assumed that would be a CLI not a GUI prompt
[19:35] <stgraber> ok, so english is usually pretty well tested, so it's not a generic installer problem at least :)
[19:36] <stgraber> so I'd recommend re-downloading the image (you may as well take 12.04.2 then, it'll be released in a couple of hours) and try burning on a new media
[19:36] <stgraber> you can find the 12.04.2 images at: http://cdimage.ubuntu.com/edubuntu/releases/12.04.2/release/
[19:39] <highvoltage> Tstoner98133: weird, that's something we've never seen before. and you wrote it to DVD, not a CD? might be good to do a test of the disc to make sure it downloaded and burned correctly
[19:42] <Tstoner98133> thats a good plan, I will try that


[06:17] <ScottK> Looks like nodejs can be synced.  That would fix installability of node-resolve.
[06:17] <ScottK> Oops, wrong channel.
[06:23] <smartboyhw> Release Team: When will 12.04.3 builds start appearing in http://iso.qa.ubuntu.com/qatracker ?
[08:16] <stgraber> slangasek: heya. I'm about to jump on a plane and disappear for 9 hours or so. I created the 12.04.3 milestone on the ISO tracker and checked that nusakan is properly configured for it (first auto-publish + self-rebuild milestone for precise)
[08:16] <stgraber> slangasek: everything looks good, so once you're ready and have cron turned off, go to http://iso.qa.ubuntu.com/admin/config/services/qatracker/milestones/301/edit and tick "Automatically publish builds listed in the series manifest", then save the milestone
[08:17] <stgraber> slangasek: from that point on, any build being pushed to the tracker for precise which is listed on http://iso.qa.ubuntu.com/admin/config/services/qatracker/series/1/manifest will automatically show up as part of 12.04.3
[08:19] <stgraber> slangasek: I'm currently planning on setting up the paperwork (release notes + announcement) tomorrow (wednesday) morning. If you think we should have those earlier, ping me and I'll try to get them done when I arrive home
[09:21] <infinity> slangasek: -proposed kernels all pushed to -updates, and the matching d-i has been released too.
[15:21] <bdmurray> Could somebody approve libgksu2-0 in the raring -proposed queue for me?
[16:06] <slangasek> bdmurray: accepted
[16:29] <slangasek> infinity: ping
[17:33] <infinity> slangasek: pong. :P
[17:36] <slangasek> infinity: pacman
[17:37] <infinity> slangasek: Ms PacMan was way better.
[17:48] <slangasek> plars: finally got everything in order, first candidate images should be rolling off the line within the hour
[17:48] <slangasek> infinity: oh, I didn't copy pciutils over before I started; I don't think that's worth stopping for now fwiw
[17:55] <infinity> slangasek: Yeah, no pciutils should be fine.  PCI DBs are a purely cosmetic thing anyway.
[17:55] <infinity> (Though it makes the ISO less pleasant as a debugging tool, but that's a bit of a *shrug*)
[17:57] <infinity> rtg: *poke*
[17:57] <rtg> infinity, ?
[17:57] <rtg> pciutils ?
[17:57] <infinity> rtg: I noticed that intel-microcode SRU of yours claims (at least, according to upstream) to be a scurity fix.  Can you coordinate with mdeslaur or someone to make that happen as a security release instead of an SRU?
[17:57] <infinity> rtg: And I'll reject the SRUs.
[17:58] <infinity> mdeslaur: ^
[17:58] <rtg> infinity, there was no CVE allocated, plus its a multiverse package. is it really worth it ?
[17:58] <infinity> rtg: I'd rather not push security fixes only to -updates, personally.  Even for weird multiverse thingees.
[17:59] <slangasek> plars: alternate images already available now
[17:59] <infinity> jdstrand, mdeslaur: Opinions?
[18:00] <mdeslaur> do we have any idea what the "important security fix" is in that?
[18:01] <plars> slangasek: awesome, thanks for the heads up
[18:01] <plars> psivaa: ^
[18:01] <rtg> infinity, mdeslaur: there is no changelog on the ucode download page
[18:04] <infinity> mdeslaur: You missed "very".  A "very important security fix".  Whatever that means. :P
[18:04] <plars> slangasek: according to http://iso.qa.ubuntu.com/qatracker/milestones/301/builds/51817/testcases - the alternate images are oversized
[18:04] <slangasek> plars: nominally; we've agreed to raise the limit rather than try to get them back down to CD size, as that's a lost battle
[18:04] <mdeslaur> infinity: oh! that's changes _everything_ :)
[18:04] <mdeslaur> sarnold: could you please handle rtg 's packages ^
[18:05] <sarnold> mdeslaur: yes
[18:07] <infinity> rtg: ^-- That would have been rejected anyway, due to the version clash.
[18:08] <infinity> sarnold: Bug's https://bugs.launchpad.net/intel/+bug/1212497
[18:08] <ubot2`> Launchpad bug 1212497 in intel "[Feature] update microcode to 20130807 version" [High,New]
[18:08] <sarnold> rtg: can you provide me with the debdiffs? that's my easiest way forward :)
[18:08] <sarnold> thanks infinity
[18:08] <infinity> sarnold: debdiffs of binary blobs don't end well.
[18:09] <sarnold> infinity: ah. makes sense.
[18:10] <rtg> sarnold, infinity: so I'm a little confused here. what do you want done with those uploades  (aside from fixing the quantal version) ?
[18:11] <infinity> rtg: Just hand them to sarnold and let him sort it through the kernel PPA and release them.
[18:11] <sarnold> rtg: I'd like to rebuild the packages in the security ppa and unembargo them through the usual process
[18:12] <infinity> Err... The security PPA.
[18:12] <infinity> I can't brain this morning.  Need sugar.
[18:12] <rtg> sarnold, ok, lemme get them prepped.
[18:12] <sarnold> rtg: thanks
[18:12] <infinity> sarnold, rtg: Thanks.
[18:14] <infinity> slangasek: Bleh, yeah, the whole world is still a tiny bit oversized.  Did we reach a conclusion on carefactor there?
[18:14] <slangasek> infinity: pretty sure the consensus was to accept defeat on this front
[18:15]  * infinity nods.
[18:15] <infinity> slangasek: We could drop unity from the images instead.
[18:16] <infinity> Anyone who needs more than glibc, gcc, and perl is probably using their computer wrong anyway.
[18:16] <slangasek> we could drop acid instead; both are about as helpful for getting us to a point release
[18:17] <infinity> slangasek: I suppose if we were going to accept defeat, we could have added some langpacks back, but oh well.  There's always .4
[18:42] <rtg> sarnold, http://kernel.ubuntu.com/~rtg/intel-microcode for p/q/r
[18:46] <sarnold> rtg: thanks
[18:46] <rtg> sarlemme know if I've borked the versions
[18:46] <rtg> sarnold, ^^ (damn tab completion)
[18:54] <bdmurray> infinity: how was the linux update in raring released?
[18:54] <bdmurray> infinity: I mean with what tool?
[18:55] <infinity> bdmurray: With sru-release, hacked up to remove the bug twiddling because of races.  We need to sort that. :/
[18:56] <infinity> bdmurray: With copies being much (MUCH) faster now, the bug twiddling collides with launchpad's auto-closures and sru-release backtraces itself into oblivion, so I've had to do that.
[18:56] <infinity> bdmurray: (I assume the complaint is that I didn't unsub all the teams, as the tool would have done)
[18:56] <bdmurray> infinity: okay, well the phased-update-percentage was set (I have a fix for that) but you want to use change-override to set it to 100% in -updates
[18:57] <infinity> bdmurray: Oh.  This is about PUP?  Check.  Is that meant to be set by tools or by LP?
[18:57] <infinity> I may be a bit out of date on my u-a-t branch.
[18:57] <infinity> Ahh, no.  No changes to sru-release.
[18:57] <bdmurray> infinity: I meant I'm working on the fix right now, mp forthcoming
[18:58] <infinity> bdmurray: Is the intent to have sru-release do it, or LP do it?  Having it happen in the copy seems saner and less racy.
[18:58] <bdmurray> sru-release sets it initially to 10% but should for security updates
[18:59] <infinity> s/should/shouldn't/
[18:59] <bdmurray> er should not
[18:59] <bdmurray> right
[18:59] <infinity> bdmurray: Will that be wrong in both pockets?
[18:59]  * infinity looks.
[18:59] <bdmurray> no
[19:00] <bdmurray> https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/no-phase-security/+merge/181129
[19:00] <infinity> Ahh, no.  It's 100 in security, so at least people are getting their updates.  Just from a poor, overloaded server.
[19:00]  * infinity overrides the world.
[19:02] <infinity> bdmurray: I assume dep resolution works fine if something at 100% depends on something at 10%?
[19:02] <infinity> (Not that I'm creating that situation, just curious)
[19:03] <bdmurray> infinity: that's my understanding
[19:03] <infinity> Alright, linux, linux-ppc, linux-lowlatency, and matching signed/meta stuff all bumped to 100%
[19:04] <bdmurray> thanks
[19:04] <infinity> We do need to have a bit of a think about the bug twiddling races.  Very annoying to have to noop that part of the tool right now.
[19:05] <infinity> Exponential backoff, I suppose.
[20:12] <plars> stgraber, slangasek: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1214563
[20:12] <ubot2`> Launchpad bug 1214563 in ltsp (Ubuntu) "ltsp-client-builder: Unable to locate package linux-image-generic-lts-quantal" [Undecided,New]
[20:13] <slangasek> plars: well then!
[20:13] <slangasek> how about I fix that
[20:15] <plars> slangasek: sounds good :)
[20:16] <plars> slangasek: on the plus side, all the other tests I had been doing on alternate looked good so far
[20:17] <slangasek> cool
[20:18] <slangasek> so interestingly, wherever the lts-quantal bit lives, it's not in the ltsp source itself
[20:18] <slangasek> stgraber: ^^ home yet?  Do you know what we've missed wrt ltsp and enablement stacks?
[20:40] <stgraber> slangasek: just arrived in Canada but not quite home yet (on my phone). IIRC there's a patch in debian/patches for lts kernels in the precise LTSP source. Extending this to cover the new backport stack should be enough.
[20:40] <stgraber> slangasek: if you don't have the time to look at it, I should be able to do it in 2-3 hours
[20:41] <slangasek> stgraber: oh... I saw there was no branch for precise-updates and assumed that meant there was no package either, wah :(
[20:41] <slangasek> stgraber: ok, I've got it then
[21:27] <slangasek> infinity, stgraber: ^^ please review/accept ltsp
[21:29] <bdmurray> slangasek: could you merge https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/no-phase-security/+merge/181129?
[21:34] <slangasek> bdmurray: done
[21:36] <infinity> 2> /dev/null > /dev/null
[21:36] <infinity> Curious construct.
[21:37] <infinity> slangasek: That patch looks a bit fragile and strangely non-deterministic, but I guess you didn't make it any worse than it already was.
[21:40] <slangasek> infinity: thanks; I'll respin {k,x,}ubuntu alternates + kubuntu dvd + ubuntu-server once that publishes
[21:41] <slangasek> oh, except we've already disabled -proposed
[21:41] <slangasek> infinity: how would you like to play this?  test rebuild with -proposed, or slam it straight into -updates?
[21:42] <infinity> slangasek: Let me give it a better review (like, a second set of eyes grepping the whole source package), but if it's as obviously correct as it looks, slamming it straight into updates seems fine.
[21:43] <infinity> slangasek: Yeah, that looks Obviously Correct(tm) to me on a review of the full source.  I say we just let it build and release it.
[21:43] <slangasek> okie
[22:02] <infinity> slangasek: iz copied.
[22:13] <slangasek> infinity: ta
[22:18] <infinity> slangasek: And now published to ftpmaster.
[22:18] <slangasek> infinity: and wait-for-package trigger set
[22:44] <slangasek> plars: 12.04.3 ubuntu/alternate respin imminent
[22:47] <plars> slangasek: ok
[23:19] <plars> hmm, server too
[23:19] <plars> ok