[17:57] <cody-somerville> :)
[17:57] <cody-somerville> I gotta run. j1mc is going to host the meeting for me :)
[17:57] <cody-somerville> Have fun fellows
[17:59] <j1mc> hi all - who all is here?
[19:11] <TheSheep> cody-somerville: so I guess the meeting is cancelled?
[19:12] <techno_freak> oh?
[19:49] <jcastro> 10 minutes until "How to Run a Bug Jam"!
[19:55] <ccm> good luck with it, jcastro :)
[19:55] <greg-g> no luck needed ;)
[19:56] <ccm> right. just kind of an idiom :)
[19:57] <jcastro> heh
[19:58] <jcastro> greg-g: do you know how to control the bot?
[19:59] <greg-g> no clue
[19:59] <jcastro> heh, no worries
[20:00] <jcastro> ok, I guess we should start with introductions
[20:00] <jcastro> I'm jorge castro, I'm on the ubuntu community team.
[20:00] <greg-g> Hello everyone!  Welcome to the second session of "How to Run a Bug Jam"
[20:00] <greg-g> my name is Greg Grossmeier and the leader of the Michigan (US) LoCo Team
[20:01] <jcastro> so if you're here from the meeting please say hello!
[20:01] <jcastro> and what team you're representing. (or if you're just hanging out)
[20:01] <jacob> i might be ducking in and out (was in here yesterday) but I suppose i'm here. Hello from Ohio!
[20:02] <greg-g> Hello jacob
[20:02]  * chuckf representing MarylandTeam
[20:02] <greg-g> welcome
[20:02] <jcastro> I see Maryland already has all their stuff filed out on the wiki
[20:03] <nxvl> jcastro: #startmeeting
[20:03] <jcastro> nxvl: ah
[20:03] <chuckf> largly, yeah
[20:03] <jcastro> #startmeeting
[20:03] <jcastro> like that?
[20:03] <jcastro> ok whatever, let's get started!
[20:03] <jcastro> https://wiki.ubuntu.com/GlobalBugJam
[20:03] <nxvl> yes, mathiaz always use something like that
[20:03] <jcastro> this is the main page we're going to use for coordinating the jam
[20:04] <greg-g> and tips for how to run it: https://wiki.ubuntu.com/GlobalBugJam/Prep
[20:04] <jcastro> https://wiki.ubuntu.com/GlobalBugJam/Prep
[20:04] <jcastro> and this page is what we're going to discuss today
[20:04]  * nxvl represents Peru
[20:04] <jcastro> so if you remember one thing, it's that last URL. :)
[20:04] <jcastro> Ok, before we get into the nitty gritty
[20:04] <jcastro> the first thing that is most important for the Jam
[20:04] <jcastro> is that everyone has a good time.
[20:05]  * greg-g nods
[20:05] <jcastro> If 300 people show up
[20:05] <jcastro> and you only triage 1 bug, then that's totally fine
[20:05] <jcastro> the idea is to get Local teams together and having a good time
[20:05] <jcastro> so down the road when you want to do a social event, you'll know how to do a jam and can do one whenever you want
[20:06] <jcastro> we would like to see LoCos just running jams on their own and doing what their members want to do
[20:06] <jcastro> so hopefully we can make these fun so people want to do them
[20:06] <jcastro> so for example
[20:06] <jcastro> we just had a jam in michigan
[20:06] <jcastro> and due to weather only 3 people showed up
[20:06] <jcastro> but we still had a great time
[20:06]  * greg-g and me being in California
[20:06] <jcastro> so you should measure success by how good a time people had, and how you take notes to make things better next time, etc.
[20:07] <jcastro> don't use raw numbers or bug counts as your measurement of success
[20:07] <jcastro> those are just great side effects. :)
[20:07] <jcastro> Any questions so far?
[20:07] <chuckf> nope
[20:07] <jcastro> greg-g: want to go into venues?
[20:07] <jcastro> we can alternate on topics
[20:07] <greg-g> sure
[20:07] <siretart> FYI, we are having a BugJam right now in nueremberg, with 15 attendees (including myself) :)
[20:07] <greg-g> siretart: nice!
[20:08] <jcastro> siretart: oh well, that's awesome!
[20:08] <nxvl> jcastro: i have a doubt
[20:08] <greg-g> ?
[20:08] <nxvl> jcastro: the idea of the GBJ is to fix bugs or just to triage them, or both of them?
[20:08] <jcastro> nxvl: fix would be nice, but shoot for triage
[20:08]  * greg-g nods
[20:08] <jcastro> nxvl: people should know how to triage
[20:09] <nxvl> jcastro: so the goal is triaging, but if you fix them it's even nicer?
[20:09] <jcastro> and as your bug jams progress your team can go as advanced as they want
[20:09] <jcastro> yep, of course. :D
[20:09] <greg-g> So, Venues...
[20:09] <greg-g> You need some place that has power, internet, and places to sit for everyone that is going to show up (obviously)
[20:09] <greg-g> but, it also needs to be conducive to listening to one person talking for a little bit and asking questions
[20:10] <greg-g> some good places are offices of Open Source Friendly businesses or even Library conference rooms (where Michigan had ours)
[20:10] <greg-g> where is your bug jam going on siretart ?
[20:11] <jcastro> I bet in a pub. :)
[20:11] <greg-g> (feel free to answer later siretart ) another place we have done things for our team is at a person's house
[20:11] <greg-g> There we had the essentials plus nice seating and food and drinks
[20:12] <greg-g> so really, anywhere that is comfortable and conducive to group work.
[20:12] <greg-g> and, cheap :)
[20:13] <greg-g> any questions on venues? or other suggestions before we move on?
[20:13] <chuckf> colleges
[20:13] <jcastro> Colleges are always good
[20:13] <greg-g> good one
[20:13] <chuckf> the cis groups tend to have presentation/work rooms available on weekends
[20:13] <nxvl> we are thinking on running ours on a starbucks
[20:13] <jcastro> because you can link up with like a computer club or ACM or something and get more participation
[20:14] <greg-g> just make sure you have a way for everyone to get internet access where ever you are
[20:14] <chuckf> also check with local lugs see if they have inet friendly places
[20:14] <greg-g> yep.  and in general, communicating with the LUGs is a good idea
[20:14] <jcastro> It also doesn't hurt to ensure that there's enough power plugs for everyone, if not, just ask people to bring along power strips or whatever
[20:15] <chuckf> and a wireless ap for the group to work off of depending on the venue
[20:15] <greg-g> yep
[20:15] <greg-g> if there aren't any more venue questions, lets move on to Promotion
[20:16] <jcastro> ok
[20:16] <jcastro> so the biggest thing to help with promotion is to ensure that your loco is on the wiki page
[20:16] <jcastro> since we'll be blogging/twittering, and generally pointing people to that page
[20:16] <jcastro> also, your local team mailing list
[20:17] <jcastro> and your local lug mailing list is another place where you might want to send a mail
[20:17] <jcastro> lots of LoCo people are also local LUG people so with that overlap it's easy to get the word out
[20:17] <jcastro> other places to get the word out include local computer stores and shows
[20:18] <nxvl> i'm running some packagin jams here for the university lugs and telling them about the GBJ
[20:18] <jcastro> like, before they went out of business, our local CompUSA had a bulletin board where people could post stuff
[20:18] <greg-g> nxvl: good deal
[20:18] <jcastro> and in general, blogging about it on planet ubuntu, your blog, twitter, etc. etc. is a good way to promote it
[20:18] <nxvl> so i prepare people to fix bugs and know how to do them and also i invite them to stay tunned for it
[20:18] <jcastro> and if you've noticed we've put the word out on podcasts as well
[20:19] <jcastro> any other ideas for promotion?
[20:19] <jcastro> oh, your local area in the ubuntu forums if you have one
[20:19] <greg-g> along with the LUGs, be sure to contact the local ACM chapter at the university (if there is one)
[20:19] <jcastro> pointing people to the wiki page so they can get the date/time information, etc.
[20:19] <nxvl> jcastro: another way to promote event is to exchange publicity for content
[20:19] <nxvl> on the local magazines
[20:19] <jcastro> local university clubs are great, I used to ask CS professors to announce LoCo stuff
[20:19] <nxvl> or newspapers
[20:20] <jcastro> nxvl: ah, right, local media.
[20:20] <nxvl> you give them some content for them to make articles
[20:20] <nxvl> and ask them to mention the event
[20:20] <jcastro> It would be cool if you could get like a local newspaper, magazine, or radio/tv news or something to cover your event
[20:20] <jcastro> in return for highly technical articles. :D
[20:20] <greg-g> thats a great idea
[20:20] <jcastro> greg-g: we need to do that!
[20:20] <greg-g> noted
[20:21] <jcastro> anything else for Promotion before we get to the "Pre-Bug Jam Checklist of Awesome"?
[20:21] <nxvl> we have used it in some other events and it works fine
[20:21] <nxvl> :D
[20:22] <greg-g> Checklist of Awesome:
[20:22] <greg-g> First thing that is critical on the Checklist of Awesome is: ensuring everyone has a Launchpad Account
[20:22] <greg-g> without that, the participants can't make any bugs better themselves
[20:23] <greg-g> Checklist of Awesome number 2: 5-a-day preparedness
[20:23] <greg-g> does everyone know what 5-a-day is?
[20:23]  * chuckf does
[20:23] <nxvl> 5-a-day rocks!
[20:24] <greg-g> well, quickly, 5-a-day is a way to have the amount of work you are doing on bugs to be recorded.  but not only for you, but your loco team as well
[20:24] <greg-g> there are instructions at wiki.u.c/5-a-day
[20:24] <greg-g> Checklist of Awesome number 3: what package(s) does your group love?
[20:25] <chuckf> and there's not a problem of just cutting people loose to decide what they want to handle themselves right?
[20:25] <greg-g> to make things like this matter to the participants you don't want to triage bugs for a package no one uses.  Find popular packages that need some love, and get a list out for that package.  At the end of the day people will feel like they really helped
[20:25] <greg-g> oh right, you can break up into groups and have people interested in similar things work together
[20:26] <greg-g> 4 or so people per group is probably a good number, depending on how many people come
[20:26] <jcastro> chuckf: yeah, the idea is if people want to work on a specific project, then let them break out into groups or whatever
[20:26] <greg-g> Checklist of Awesome 4: irc channel for pasting links
[20:27] <jcastro> chuckf: some locos might want to target one thing for their entire group, or a specific upstream. Whatever works for you.
[20:27] <greg-g> make sure everyone knows where the loco's irc channel is and how to get on
[20:27] <chuckf> k
[20:27] <greg-g> Checklist of Awesome 5: have fun!
[20:27] <chuckf> and there will, i assume, be a gbj room set up on the weekend
[20:28] <greg-g> well, #ubuntu-bugs will have a bunch of experienced bug triagers
[20:28] <jcastro> it'll be in ubuntu-bugs
[20:28] <jcastro> so I think the best thing to do
[20:28] <greg-g> and then your loco team can be in your channel for more direct communication
[20:28] <jcastro> is have people idle in there that want to, but use your local channel for noisier conversation
[20:28] <greg-g> (or use gobby)
[20:29] <jcastro> but there should be at least one person in #ubuntu-bugs from your group to coordinate with everyone
[20:29] <greg-g> right
[20:29] <jcastro> in case you're loco is working on say a certain list of bugs
[20:29] <jcastro> we don't want another loco to come along and start working on the same list
[20:29] <jcastro> so we'll use #ubuntu-bugs for your loco to say "we're working on foo!" or whatever
[20:30] <greg-g> and, that Checklist of Awesome can be found on the GlobalBugJam/Prep wiki page (I'll add some more to it later).  So, go over that and send out instructions for the simple things before the day of the event
[20:30] <nxvl> greg-g: don't forget about gpg keys
[20:30] <jcastro> please note the tags for the 5-a-day application!
[20:30] <greg-g> like "No Launchpage account? No worries!" kinda thins
[20:30] <greg-g> nxvl: key signing?
[20:31] <nxvl> greg-g: not, just for people to have gpg keys
[20:31] <chuckf> they are not needed for bug triaging
[20:31] <chuckf> I thought
[20:31] <jcastro> yeah
[20:31] <greg-g> right
[20:31] <jcastro> they're not
[20:31] <nxvl> yes, but most of them will want to fix some bugs
[20:31] <greg-g> not needed, but if people ask about them you can do a 1 on 1 with them to set it up
[20:32] <chuckf> though our team is having a tutorial/signing over the next month
[20:32] <nxvl> since there are some really bitsize ones
[20:32] <nxvl> and it will be great for people to fix them
[20:32] <nxvl> :D
[20:32] <jcastro> yeah that's fine
[20:32] <jcastro> just don't start off a jam with "and now we're going to do a massive keysigning"
[20:32] <greg-g> nxvl: if you have some experienced packagers on hand to help out with that, yeah
[20:32] <greg-g> right, takes a lot of time
[20:32] <jcastro> don't want to scare people off too early!
[20:32] <nxvl> greg-g: i am :D
[20:33] <greg-g> nxvl: good deal
[20:33] <chuckf> our keysigning will be the prior week so it'll be out of the way:)
[20:33] <jcastro> good idea
[20:33] <chuckf> we should be done by the start of this
[20:33] <chuckf> :)
[20:33] <jcastro> heh
[20:33] <greg-g> chuckf: that is a good way to do it.  at some other event like a basic get-together
[20:34] <chuckf> ours is going to be a the nsa crypto museum
[20:34] <chuckf> :)
[20:34] <greg-g> nice
[20:35] <greg-g> here is the rundown:
[20:35] <greg-g> Checklist of Awesome: 1) Launchpad 2) 5-a-day 3) Popular Packages 4) IRC channel information  5) FUN!
[20:35] <greg-g> next item on the agenda?
[20:35] <nxvl> 6) Friends!
[20:35] <jcastro> Running it!
[20:35] <jcastro> OK, so something we've had success with
[20:35] <jcastro> was a presenter go over a few examples
[20:35] <jcastro> so new people get an idea of what to do
[20:36] <nxvl> greg-g: don't forget about the most important part of a community!
[20:36] <jcastro> if you have experienced triagers already there, you can break them off into groups with other peopole
[20:36] <greg-g> nxvl: beer?
[20:36] <nxvl> greg-g: no, friends!
[20:36] <jcastro> so new people have an experienced person in their group to help them
[20:36] <jcastro> or you can have one smart person up front answering questions
[20:36]  * greg-g smiles at nxvl
[20:36] <jcastro> what we did is started working on our own list of bugs
[20:37] <jcastro> and if someone had a question they would yell out the number, and then the person connected to the projector would load it up
[20:37] <jcastro> and we would look through it, and decide what to do
[20:37] <chuckf> are there any 'demo' bugs in the system that we can use?
[20:37] <jcastro> if not, then one person would ask in #ubuntu-bugs
[20:37] <jcastro> chuckf: there will be a premade list of bugs, but I should ask about some demo bugs
[20:37] <jcastro> that's a good idea
[20:37] <greg-g> noted
[20:38] <jcastro> the lists of bugs will be made available before the jam
[20:38] <jcastro> so basically your loco picks one of the parts of the list
[20:38] <jcastro> and starts working on it
[20:38] <chuckf> maybe have a 'gbj-marylandteam' bug
[20:39] <nxvl> jcastro: also if there are no experienced triagers or packagers, it's cool to have meetings with tome people on the community and start working with them and teaching
[20:39] <jcastro> chuckf: wolfger runs our jams, and he's experienced, so usually he just finds a bug in real time and triages it on the spot
[20:39] <nxvl> s/no/just one/g
[20:39] <jcastro> nxvl: yep, if everyone is brand new I expect most of the time you will just be teaching
[20:39] <jcastro> which is why we don't put an emphasis on the amount of bugs you triage
[20:39]  * greg-g nods
[20:40] <chuckf> and it's difficult to quota volunteers:)
[20:40] <jcastro> at the very minimum, if you get lost, frustrated, or it's turning into a disaster, you can always concentrate on just teaching people little things.
[20:40] <jcastro> yeah
[20:40] <jcastro> I suspect we'll get a few reports that start off with "We started triaging and then decided to go to the pub instead."
[20:41] <jcastro> So whatever works for you. :D
[20:41] <greg-g> :)
[20:41] <greg-g> So, what to do after the GBJ is over?  Good question
[20:41] <nxvl> jcastro: heh
[20:42] <nxvl> greg-g: key signing and beers
[20:42] <nxvl> :D
[20:42] <greg-g> 1) Put our pictures online (flickr or something) with tags that will help people find them (global-bug-jam-2008 or similar)
[20:42] <chuckf> take the spouses/friends out to dinner for abandoning them all day:)
[20:42] <greg-g> both good suggestions :)
[20:42] <greg-g> 2) beer
[20:42] <greg-g> 3) spouse/friend dinner
[20:42] <greg-g> 4) get feedback from the participants
[20:43] <greg-g> like how it went, what to do differently next time, etc
[20:43] <greg-g> not formal questionaire or anything, just take notes
[20:43] <greg-g> 5) plan some future bug jams!
[20:43] <greg-g> 6) Blog it, blog it, blog it
[20:44] <jcastro> yeah, do like a quick feedback thing at the end, where people can say what sucked, what rocked, etc.
[20:44] <jcastro> and then put those notes on your loco wiki
[20:44] <greg-g> yeah, just generally take some notes on how well it was executed
[20:44] <greg-g> right
[20:44] <jcastro> so you can say "don't go to this place again!" or "this place was real friendly!"
[20:44] <jcastro> things like that
[20:44] <greg-g> including information on the venue you used (good/bad/ugly)
[20:45] <jcastro> also, if you could put the feedback in your loco monthly report, that would be great. Also your local list.
[20:45] <jcastro> we'd like to get as much feedback as to how the event went across the world
[20:45] <jcastro> even if it's bad!
[20:45] <greg-g> yeah, if it didn't work, it is good to know why
[20:46] <greg-g> are there any other questions at this time?
[20:46] <xander21c> The idea is to make it fun instead to be too academic type
[20:46] <greg-g> correct!
[20:46] <jcastro> cool cool!
[20:46] <jcastro> this is going to rock.
[20:47] <greg-g> heck yeah, I'm excited for August 8-10th
[20:47] <jcastro> any other questions?
[20:47] <xander21c> nxvl and I are looking for a fun place with wifi :) in Lima
[20:47] <nxvl> yes
[20:47] <jcastro> if you think of some later, track me down on irc or you can mail me at jorge at ubuntu.com
[20:48] <nxvl> xander21c: i find a nice Starbuck that we can use
[20:48] <chuckf> what time zone are we starting from:)
[20:48] <xander21c> nxvl: nice :)
[20:48] <greg-g> chuckf: whenever it is August 8th for you
[20:48] <nxvl> chuckf: just any, that's why it's so many days
[20:48] <nxvl> xander21c: just use 9th and you will hace no change to fail
[20:48] <nxvl> :D
[20:49] <nxvl> s/ xander21c / chuckf /g
[20:49] <xander21c> also can make and advocacy showing Ubuntu + compiz
[20:49]  * chuckf was making a joke after the FF release day compaints
[20:49] <chuckf> complaints
[20:49] <greg-g> chuckf: :)
[20:50] <jcastro> chuckf: we're kind of flexible on start/end times
[20:50] <jcastro> whatever works for you
[20:50] <jcastro> greg-g: will you be back for ours?
[20:50] <greg-g> :( no
[20:50] <jcastro> dang
[20:50] <greg-g> I'll be online though as much as I can
[20:50] <snap-l> greg-g: bummer
[20:51]  * nxvl too
[20:51] <nxvl> let's make GBJ as cool as we can!
[20:51] <greg-g> any other questions/ideas from anyone?
[20:51] <nxvl> it need to rock!
[20:52] <greg-g> it WILL rock! ;)
[20:52] <jcastro> with people like you nxvl how can we fail!
[20:54]  * nxvl HUGS jcastro and greg-g
[20:54]  * greg-g hugs nxvl back
[20:55] <greg-g> and with that: thanks everyone for coming and go have great Bug Jams!
[20:56] <chuckf> thanks for the chat!@
[20:56] <greg-g> thank you
[20:57] <greg-g> ... for running a bug jam :)
[20:57] <chuckf> krispy kreme for breakfast and pizza for lunch, what more incentive do I need???
[20:58] <jcastro> have a good one guys!
[20:58]  * jcastro hugs everyone
[20:58] <chuckf> oh, helping make the software I use better is just a side benefit:)
[20:58] <greg-g> my best to everyone!
[21:00] <nxvl> jcastro: be carefull of everyone huging you!
[21:00] <nxvl> jcastro: as in the flash hug
[21:00] <nxvl> :P
[21:00] <jcastro> heh
[21:01] <juliux> ,v _stink_
[21:27]  * xander21c see u later guys


[01:41] <pangolin> hello mazda01 how can i help you?
[02:00] <mazda01> how do I use whois in xchat? or is this the wrong place to ask?
[02:01] <CarlFK> wrong place
[02:01] <mazda01> ok, sorry. goodbye
[02:01] <CarlFK> no prob
[04:21] <stu-2> hi  my ubuntu crashed the other day    now i get a message that my profile has not loaded properly   what does it all mean?
[09:18] <bazhang> whoops sorry
[09:19] <ikonia> it's fine, the guy does this all the time
[09:19] <pozic> ikonia: are you out of your freaking mind?
[09:19] <ikonia> pozic: every time you are in #ubuntu you cause a problem with your ranting
[09:19] <pozic> ikonia: let me guess: you are affiliated with Canonical?
[09:19] <ikonia> pozic: if the distro does not meet your needs, change distros
[09:19] <ikonia> pozic: if the distro does meet your needs and you want help, then ask and we can try to help
[09:19] <pozic> ikonia: uhm, just because Ubuntu sucks, doesn't mean I cannot say that it does.
[09:19] <ikonia> pozic: sure it does
[09:20] <pozic> ikonia: I did ask for help.
[09:20] <pozic> ikonia: the help quality just sucked.
[09:20] <ikonia> pozic: it's a support channel, you adding "ubuntu sucks" isn't helpful to anyone
[09:20] <pozic> ikonia: because I still have the problem.
[09:20] <ikonia> pozic: then don't use the channel, everytime you are in #ubuntu you cause a problem,
[09:20] <pozic> ikonia: I think you are just an ASSHOLE, and nothing else if you have this attitude.\
[09:20] <pozic> Ubuntu has multiple bugs open.
[09:20] <pozic> Are you saying it is the fault of those users?
[09:20] <ikonia> it has many bugs and problems
[09:20] <pozic> No, the software sucks. Period.
[09:20] <ikonia> then don't use it
[09:21] <pozic> You shouldn't ban me for pointing out flaws.
[09:21] <ikonia> I didn't
[09:21] <pozic> Well, _someone_ did.
[09:21] <ikonia> however you are adding no value with your comments.
[09:21] <pozic> ikonia: yes, I am adding value.
[09:21] <ikonia> you where warned enough times on this occasion and you've had warnings in the past
[09:21] <pozic> ikonia: because I am saying that it doesn't work.
[09:21] <ikonia> so I'm tried of giving you warnings
[09:21] <pozic> ikonia: so, that is feedback.
[09:21] <ikonia> no it's not
[09:22] <pozic> ikonia: at this moment, Canonical QA personal should FIX the issue.
[09:22] <ikonia> feedback would be logging the bugs, updating them, pushing them through
[09:22] <ikonia> sat in #ubuntu saying "ubuntu sucks" isn't
[09:22] <pozic> ikonia: I am sure that someone could reproduce the problem with the information I gave them.
[09:22] <ikonia> I'm sure they could
[09:22] <ikonia> but why would they want to
[09:23] <pozic> ikonia: exactly.
[09:23] <pozic> They do not want to provide bug free software.
[09:23] <ikonia> log a bug
[09:23] <ikonia> put as much detail in the bug as possible
[09:23] <ikonia> push the bug through
[09:23] <pozic> Because that would destroy their business model.
[09:23] <ikonia> ok - whatever, this conversation is done
[09:23] <pozic> That's why Linux will never succeed.
[09:23] <ikonia> pozic: until you can contribute to the channel, you're not going to be allowed into the channel
[09:23] <pozic> There is not reason to make it good.
[09:23] <ikonia> good bye
[09:23] <pozic> ikonia: I contributed tons of times.
[09:24] <pozic> ikonia: also, you are just a sucker.
[09:24] <pozic> ikonia: you likely don't even have a degree in CS.
[09:24] <pozic> ikonia: you sound like a stupid system administrator in any way.
[09:24] <pozic> ikonia: just a piece of garbage that can only ban people when they have a different opinion.
[09:25] <pozic> You are nothing different than Hitler.
[09:25] <pozic> Also, which moron decided to ban me?
[09:25] <bazhang> this is going nowhere
[09:26] <bazhang> once you reference Nazi's, it's over
[09:26] <pozic> I just cannot have any respect for a bunch of idiots.
[09:26] <pozic> Why should I?
[09:26] <Tm_T> pozic: as you keep that attitude, I have to ask you to leave until you can behave
[09:26] <bazhang> pozic, you won't be unbanned at this time. please exit the channel.
[09:26] <pozic> I have no problems with anyone that I didn't communicate with.
[09:26] <pozic> I have a problem with ikonia.\
[09:27] <pozic> He/she clearly lacks the intelligence to communicate with me.
[09:27] <Tm_T> pozic: I ask you again, please leave when you have that attitude
[09:27] <bazhang> thats quite enough of the insults
[09:27] <pozic> It is not an insult.
[09:27] <pozic> It is a fact.
[09:27] <bazhang> bye
[09:27] <pozic> Not everyone is created equal.
[09:27] <bazhang> heh
[09:27]  * Tm_T fails with scripts sometimes
[09:28] <bazhang> chanserv.py?
[09:28] <Tm_T> no, my own aliases for irssi
[09:28] <bazhang> heh ok
[09:28] <Tm_T> I forgot to add the nick before hitting enter
[09:28] <ikonia> and he'll start in +1 in 30 seconds
[09:29] <bazhang> and more insults now
[09:29] <ikonia> and he's gone
[09:29] <Tm_T> I was on it ):
[09:29] <ikonia> sorry, didn't know if you where in +1
[09:30] <Tm_T> np, you just keep pointing out how old and slow I am (:
[09:30]  * Tm_T huggles the young an fast ikonia
[13:20] <Pici> !ping
[14:58] <Flannel> Shouldn't there be an additional call for IRCC nominations instead of a vote?  How can we elect four people to five seats?
[14:59] <Pici> Good question.  I must not have been as awake as I thought when I read it earlier.
[15:02] <jussi> I have no idea to the answer. I suggest you ask the CC.
[16:25] <mneptok> ubottu: i nom-nom-nominate you!
[16:28]  * genii-around votes for the bot
[16:58] <pangolin> least we know the bot will attend the meetings
[17:14] <genii-around> pangolin: Good point
[17:23] <pangolin> !guidelines > iToast
[17:44] <jussi> I think meetings should be abolished. stupid waste of time. :)
[17:46] <genii-around> I'm not crazy about meetings either actually.
[17:46] <pangolin> as of wednesday you no longer have to attend
[17:46] <pangolin> let it be written, let it be done.
[17:47] <genii-around> Heh
[17:50] <genii-around> If there are 4 candidates and 4 positions, doesn't everyone just get acclaimed?
[17:51] <jussi> genii-around: read the email again, and then the link in it :) :) :)
[17:51] <Corey> I'm not a Ubuntu member, else I'd throw my hat into the proverbial ring.
[17:52] <jussi> its basically a yes/no vote
[17:52]  * genii-around re-examines email
[17:53] <pangolin> thing is doesn't the ircc require 5 members?
[17:53]  * jussi points that question to the CC
[17:55] <ikonia> I didn't think elky's term was expiring yet
[17:55] <pangolin> the CC said they were going to start a fresh IRCC
[17:57] <pleia2> having a strong council that the CC is confident is more important than a specific number
[17:57] <pleia2> s/confident is/confident in
[17:57] <pangolin> +1
[17:59] <pangolin> answers like that is why you are on the CC
[17:59] <pleia2> :)
[18:02]  * genii-around sets an alarm to remind him to vote in about 6 hours
[18:15] <pangolin> since the voting is secret and all that. I am voting yes for all four nominees.
[18:16] <pangolin> good luck and looking forward to working with you folks :)
[19:30] <ikonia> jita = known troll
[20:33] <dax> pleia2: Well, I imagine certain numbers wouldn't work. Four people being an even number would be interesting voting-wise, for example (two vs. two?).
[20:34] <dax> Although I guess you could just require 3/4 to pass things. Not too different from how things work now.
[20:35] <pleia2> dax: there is really no perfect solution to this, and if there is a decision that is so contentious that we'd need such a tiebreaker I'd rather it was discussed more widely with the community so council members could agree somehow rather than simple council majority deciding
[20:37] <pleia2> (or discussed with the CC, whatever is more appropriate for the sitation)
[20:38] <genii-around> But as I understand... there are 3 positions which are at the end of their term... one position which the member is stepping down.. which makes 4 positions. And there are 4 candidates...
[20:38]  * genii-around goes to make more coffee
[20:38] <dax> genii-around: elky's position is being voted upon also.
[20:38] <mneptok> pleia2: i strongly disagree with that approach, and can muster the votes to ensure that ..... snow!!! LOOK AT THE PRETTY SNOWFLAKES!!!!!
[20:38] <dax> genii-around: The CC feels it's best to re-elect a full council, basically.
[20:39] <pleia2> genii-around: as the email about this said, every council member is being removed
[20:39]  * mneptok scampers off
[20:39] <pleia2> we're voting on the 4 proposed to staff the council
[20:39] <genii-around> Ah, this starts to make more sense then
[20:40] <dax> pleia2: I'd suggest throwing a CC member on there and making it 5, but then they'd have yet another hat to juggle.
[20:40] <JoshuaP> I'd like to staff the council if there is a position open. :)
[20:40] <pangolin> heh
[20:40] <dax> pleia2: One hopes that the efforts towards fixing Ubuntu's derth of leaders will actually work. That you can't find five people out of a core ops team of almost 100 kinda points at it again.
[20:40] <pangolin> you need to be an ubuntu member JoshuaP
[20:40] <pleia2> dax: the CC will be closely working with the IRCC moving forward (not formally replacing the 5th because we do want that space available should a suitable replacement be found)
[20:40] <pangolin> JoshuaP: How can we help?
[20:40] <dax> true. 100 is too high, then :\
[20:41] <JoshuaP> pangolin, how do I become an Ubuntu member?
[20:41] <pangolin> !membership > JoshuaP
[20:41] <pleia2> dholbach, myself and Gwaihir have already committed to helping, don't want to overwhelm CC members either by just making one of us do it :)
[20:43] <dax> pleia2: (What's Gwaihir's realname? This must be the first time I've known someone by that and not IRC handle)
[20:43] <pleia2> Milo Casagrande :)
[20:43] <dax> ah, right
[20:44] <pleia2> I didn't actually know his IRC nick either before he joined the CC
[20:44] <pleia2> but I've met him
[20:44] <pangolin> JoshuaP: if there is nothing else please don't idle in this channel.
[20:44] <JoshuaP> I'm reading the article Dx
[20:45] <JoshuaP> I'm a bot slow at it as my eyes are strained from staring at a command line for 19 hours
[20:45] <pangolin> JoshuaP: ok well, there is a no idling policy in this channel. unless you have immediate business with the ops team please /part.
[20:46] <JoshuaP> Fair
[20:46] <pangolin> thank...
[21:16] <Pici> !cookie | ikonia
[21:16] <ikonia> ha ha ha
[21:16] <ikonia> for what ?
[21:16] <Pici> ikonia: for today, you've been dealing with a bunch of problem users in #u
[21:17] <ikonia> ha ha ha, not too bad
[21:17] <ikonia> the main issues seem to be solved, well, manday is anyway
[22:31]  * genii-around gets a 30-minute warning alarm
[23:05] <genii-around> What the hell. https://launchpad.net/~ubuntu-irc-members/+polls said an hour ago opening in 1 hour. Now the hour is gone it says one more hour. ( actually 55 minutes now)
[23:05] <ikonia> you're keen
[23:06] <genii-around> ikonia: I stayed an hour at work for it. Now it looks like another one.
[23:06] <ikonia> aren't you a good operator
[23:06] <ikonia> commited
[23:07] <genii-around> Hm
[23:07] <ikonia> staying late
[23:10] <genii-around> ikonia: I don't usually use a computer from home after being around them at work all day, etc.
[23:10] <ikonia> understandable, still good effort
[23:10]  * genii-around makes more coffee and settles in for the second hour


[11:13] <JonathanD> Morning.
[11:14] <Jackson> Moin
[12:36] <KyleYankan> Monin
[13:21] <rmg51> Morning
[17:01] <pvl1> does anyone run a non official rom on android
[18:05] <cyberanger> yeah, I do
[18:05] <cyberanger> pvl1: ^
[20:36] <pvl1> cyberanger what you run
[20:37] <cyberanger> cm9
[20:37] <cyberanger> on a lg c800
[20:39] <pvl1> im trying to compile cm 11 for devel
[20:40] <pvl1> I had to move a 43g partition to the left, too makeit a150 gb partition, bc I ran out of space
[20:40] <pvl1> twice
[20:40] <pvl1> I'm not even home to see if it worked
[20:40] <pvl1> I hope kali live doesn't go to sleep


[14:59]  * slangasek waves
[15:00] <rbalint> o/
[15:00] <philroche> \o
[15:01] <slangasek> #startmeeting
[15:01] <meetingology> Meeting started Thu Aug 30 15:01:31 2018 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:01] <meetingology> Available commands: action commands idea info link nick
[15:01] <juliank> o\
[15:02] <slangasek> [TOPIC] Lightning round
[15:02] <slangasek> $ echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke juliank fginther)
[15:02] <slangasek> Odd_Bloke slangasek xnox sil2100 fginther bdmurray philroche rbalint doko cyphermox tdaitx infinity juliank rcj mwhudson
[15:02] <Odd_Bloke> * Mostly working on a variety of partner facing issues, or meeting with partners
[15:02] <Odd_Bloke> * Assisted in upgrade of cloud images Jenkins server
[15:02] <Odd_Bloke> (done)
[15:02] <Odd_Bloke> slangasek:
[15:04] <slangasek>  * "+1 maintenance"; -proposed backlog down about 30% since last week, outstanding autopkgtest regressions down by about half
[15:04] <slangasek>  * finding novel ways to break the Canonical porter chroots, filed RTs (as yet unresolved)
[15:04] <slangasek>  * working to get nvidia packages for clouds into their final form
[15:04] <slangasek>  * Next week:
[15:04] <slangasek>    * out Monday (bank holiday)
[15:04] <slangasek> xnox:
[15:04] <slangasek> (done)
[15:04] <xnox> * helping debug cloud archive charm deployment failures -> promoting ubuntu-cloud-keyring
[15:04] <xnox> * systemd crypttab support for sector-size merged upstream, in proposed
[15:04] <xnox> * cryptsetup crypttab support sector-size is in review in debian, to be uploaded into ubuntu soon
[15:04] <xnox> * kexec-tools FFe fix for s390x uploaded
[15:04] <xnox> * binutils march s390x parsing SRU in unapproved
[15:04] <xnox> * tested packet.net cloud kernel upgrades
[15:04] <xnox> * debugging adt tests systemd/linux/s390x pain
[15:04] <xnox> * interview home work feedback
[15:04] <xnox> * short week, monday was off.
[15:04] <xnox> (done)
[15:05] <slangasek> no sil2100
[15:05] <slangasek> fginther:
[15:06] <fginther> * Out last week
[15:06] <fginther> * Draft of an image build and publication spec
[15:06] <fginther> * Progress on cloud-init changes to support redirecting logins from specific users
[15:06] <fginther> * Some maintianence work
[15:06] <fginther> done
[15:06] <fginther> bdmurray:
[15:06] <blackboxsw> +1 fginther review comments posted
[15:06] <bdmurray> I too was out last week.
[15:06] <bdmurray> vacation catch up
[15:06] <bdmurray> updated cosmic seeds snap section with a reference to DistUpgradeQuirks.py
[15:06] <bdmurray> investigation into unattended-upgrades bug LP: #1787460
[15:06] <bdmurray> meeting regarding package to team mapping
[15:06] <bdmurray> fixed u-r-u's Prompt= for cosmic
[15:06] <bdmurray> research into release-upgrade metrics / numbers
[15:06] <bdmurray> investigation into updates needing to be installed before release upgrades
[15:07] <bdmurray> fixing of ubuntu-release-upgrader LP: #1787668
[15:07] <bdmurray> uploaded and verified SRU of the above for 18.04
[15:07] <bdmurray> improved the fix for snap channel switching bug LP: #1748581
[15:07] <bdmurray> discussion with / code review for sil2100's fix for LP: #1783328
[15:07] <bdmurray> added an u-r-u quirk which checks for i386 and blocks the upgrade
[15:07] <bdmurray> ✔ done
[15:07] <bdmurray> philroche:
[15:07] <philroche> * Cloud image build system vanguard
[15:07] <philroche> * Cloud image customisations
[15:07] <philroche> (done)
[15:07] <cshep> hiii
[15:07] <philroche> rbalint:
[15:07] <rbalint> (short week)
[15:07] <rbalint> * fixed LP: #1788716
[15:07] <cyphermox> cshep: hey
[15:07] <rbalint> * prepared new rax-nova-agent for Xenial
[15:07] <rbalint> * verifed LP: #1775226
[15:07] <rbalint> * fixed ruby-concurrent autopkgtest on armhf
[15:07] <rbalint> * fixed unattended-upgrades regression with python-apt with frontend lock support
[15:07] <rbalint> * prepared new unattended-upgrades SRU to bionic
[15:07] <rbalint> * new wireshark upstream release upload to Debian
[15:07] <rbalint> (done)
[15:08] <doko> - was off last week (sick leave, two days off)
[15:08] <doko> - worked on MIRs, to get component-mismatches down
[15:08] <doko> - promotions / demotions of binary packages
[15:08] <doko> - looking into pythonX.Y autopkg test failures
[15:08] <doko> - preparing next batch of GCC updates, tracking down two new ICEs
[15:08] <doko> - chat with mwhudson about -proposed status, sorted by team
[15:08] <doko> (done)
[15:09] <cyphermox> - MIR: intel-processor-trace
[15:09] <cyphermox> - release shim/shim-signed 15+1533136590.3beb971-0ubuntu1
[15:09] <cyphermox> - prepare shim + gnu-efi SRU everywhere
[15:09] <cyphermox> - systemd:
[15:09] <cyphermox>   - work on optional-addresses implementation
[15:09] <cyphermox>   - revived + submit for review interface ActivationMode=
[15:09] <cyphermox> - netplan:
[15:09] <cyphermox>   - PR review
[15:09] <cyphermox>   - discuss development process with new contributors on #netplan
[15:09] <cyphermox> (I'm off Friday and Monday)
[15:09] <cyphermox> (done)
[15:09] <slangasek> bdmurray: speaking of package team mappings, kernel team said yes to ocl-icd and khronos-opencl-headers, correct?  I notice they're still unsubscribed
[15:09] <slangasek> (which I can notice as a glance, now that he unsubscribed list is so short!)
[15:09] <gaughen> y
[15:10] <bdmurray> slangasek: I did subscribe them
[15:10] <gaughen> slangasek, is there still a boost on there?
[15:10] <slangasek> yes
[15:10] <slangasek> is something not regenerating?
[15:10] <bdmurray> what are you looking at?
[15:10] <gaughen> http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html
[15:10] <bdmurray> gaughen: you aren't slangasek
[15:11] <gaughen> duh, but that's what I'm looking at
[15:11] <bdmurray> https://launchpad.net/ubuntu/+source/ocl-icd
[15:11] <bdmurray> kernel-packages is subscribed
[15:13] <gaughen> tdaitx is out
[15:14] <rcj> juliank:
[15:14] <juliank> * short week / long weekend (was out fri+mon)
[15:14] <juliank> * fixed fpc-related upgrade issues (bug 1786486)
[15:14] <juliank> * verified grub SRU (bug 1785859)
[15:14] <juliank> * rebuilt grub2-signed against that SRU (forgot to upload that with the SRU upload)
[15:14] <juliank> * found a bug in apt that causes it to stop pipelining in future connections once a server responds with Connection: close (archive.u.c does that every 101 requests, thus only 101 packages are pipelined). PoC fix
[15:14] <juliank> * further investigation in aptdaemon locking
[15:14] <juliank> * some minor bug triaging
[15:14] <juliank> (done)
[15:14] <rcj> rcj:
[15:14] <rcj> * attended cloud-init summit last week
[15:14] <rcj> * prepared for new hire on-boarding
[15:14] <rcj> * assisted with build system upgrade side-effects
[15:14] <rcj> * partner image development
[15:14] <rcj> (👋 done)
[15:17] <bdmurray> no mwhudson
[15:18] <slangasek> any questions on status?
[15:21] <slangasek> [TOPIC] Bugs
[15:21] <slangasek> bdmurray:
[15:21] <bdmurray> bug 1745664 is supposedly a regression
[15:22] <slangasek> NIS?
[15:24] <bdmurray> Is it the same as bug 1774417
[15:25] <slangasek> possibly
[15:26] <slangasek> I'm doubtful that we should prioritize this
[15:26] <slangasek> NIS is broadly obsolete and insecure and we don't exercise it
[15:28] <bdmurray> slangasek: okay
[15:29] <bdmurray> then bug 1785723
[15:29] <slangasek> xnox, rbalint: ^^ ?
[15:30] <xnox> hm
[15:30] <gaughen> I have a bug too to chat about
[15:30] <gaughen> when you're ready
[15:30] <xnox> journalctl --flush
[15:31] <xnox> should help to clear things, so comparing after a flush would be useful.
[15:31]  * xnox can check if it is leaking on e.g. my machine...
[15:32] <rbalint> i'm not sure if this is an actual leak but i'd be +1 on taking it and at lease provide workarounds
[15:32] <slangasek> ok, pulling into the backlog
[15:32] <gaughen> slangasek, https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863
[15:32] <gaughen> slangasek, I know this caused strong views, but it is still sitting out there
[15:32] <slangasek> gaughen: that required a reupload and was in the unapproved queue awaiting re-review, last I checked
[15:33] <slangasek> gaughen: I had accepted and then it FTBFS because it was one of these annoying packages with a testsuite that embeds SSL certificates with expiration dates
[15:33] <gaughen> k, so ddstreet the nodejs bug above is waiting on you to rebase, correct?
[15:33] <slangasek> so any SRU team member can re-review
[15:33] <slangasek> no, it's not waiting on him
[15:34] <gaughen> oh okay
[15:34] <ddstreet> gaughen i rebased and reuploaded it 8/14
[15:34] <ddstreet> it's been waiting on slangasek since then
[15:34] <gaughen> I'm slow, and not reading all of slangasek's words
[15:34] <gaughen> bdmurray, would you do a re-review please?
[15:35] <slangasek> it's been waiting on the SRU team, not on me personally :)
[15:35] <gaughen> look slangasek it's hard to read ALL your words
[15:35] <bdmurray> gaughen: okay
[15:35] <gaughen> thank you!
[15:36] <slangasek> any other bugs?
[15:36] <bdmurray> Odd_Bloke: is bug 1727751 important to you?
[15:38] <slangasek> win 37
[15:38] <slangasek> aaaaaa
[15:41] <Odd_Bloke> bdmurray: Not especially.
[15:41] <bdmurray> Odd_Bloke: okay
[15:42] <bdmurray> that's it from me then
[15:43] <xnox> slangasek, rbalint - i think it is leaky, restart of journald results in 35M -> 1M ram usage for me, as per $ systemctl status systemd-journald
[15:43] <slangasek> xnox: cool; it's in the systemd trello backlog for you to prioritize :)
[15:43] <slangasek> [TOPIC] AOB
[15:43] <slangasek> anything else?
[15:44] <slangasek> #endmeeting
[15:44] <meetingology> Meeting ended Thu Aug 30 15:44:38 2018 UTC.
[15:44] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-08-30-15.01.moin.txt
[15:44] <slangasek> thanks, all!


[06:51] <Mirv> mitya57: woohoo, we might get your qtchooser fallback merged upstream :)
[06:59] <mitya57> Yeah, I will update the patch today to fix the issues
[08:39] <lordievader> Good morning.
[09:05] <Riddell> "sebas (sebasje) renewed their own membership in the Kubuntu Members (kubuntu-members) team until 2016-02-17" yay sebas still loves us!
[09:06] <sebas> Of course I do!
[09:13] <Riddell> https://www.youtube.com/watch?v=9fc9lIruikE&list=UUQaC9B-8uudlaxwhqHX4dRw  "Kubuntu 15.04 (Alpha 2) A Masterpeice In The Making"
[09:13] <Riddell> whee
[09:15] <sitter> now go fix the issues revealed
[09:21] <sitter> Riddell: vivid ready except for symbol nonesense because of qt5.3 and false positives that ought to be resolved in git. same for utopic minus the symbol nonesense >.<
[09:21] <sitter> needs testery
[09:21] <sitter> Riddell: also do note for the archive upload that plasma-workspace must also be uploaded as it needed adjustments for the new kglobalaccel
[09:22] <sitter> /// anyone on plasma5 who wants to the test frameworks 5.7 upgrade? \\\\\
[09:23] <sitter> actually
[09:23] <sitter> anyone on plasma5 who wants to the test frameworks 5.7 upgrade?
[09:24] <sitter> fun story: konversation has no gui to make fancy format
[09:24] <yofel> ask me again around 7PM UTC
[09:24] <sitter> anyone on plasma5 who wants to the test frameworks 5.7 upgrade?
[09:25] <sitter> yofel: hehe, by then someone will have rolled a dice and published depending on the outcome
[09:26] <sitter> and there's a lot of dice rolls that can be made between now and 1900 xD
[09:26] <yofel> true
[09:26] <yofel> well, you could also just let the users do the testing :P
[09:26] <sitter> Errors were encountered while processing:
[09:26] <sitter>  /var/cache/apt/archives/libkf5globalaccel-data_5.7.0-0ubuntu1~ubuntu14.10~ppa2_all.deb
[09:26] <sitter> QQ
[09:26] <sitter> oh
[09:26] <sitter> I know
[09:29] <kfunk> sitter: Riddell: where would I request packaging of kdev-qmljs for Ubuntu/Debian?
[09:29] <sitter> yofel: actually I could let KCI do the testing
[09:29] <kfunk> I still didn't fully grasp how we usually deal with the upstream distro (Debian here)
[09:29] <sitter> alas, what with being a bit on the perfectionist side it'd probably take longer to bootstrap all the upgrade origins :S
[09:30] <sitter> kfunk: for debian would file a bug somewhere I think, somewhere being their BTS that is really a mailing list...
[09:31] <sitter> kubotu: newpackage kdev-qmljs
[09:31] <kubotu> incorrect usage, ask for help using 'kubotu: help newpackage'
[09:31] <yofel> file a RFP bug with reportbug against 'wnpp'
[09:31] <sitter> kubotu: help newpackage
[09:31] <kubotu> newpackage <packagename> <version> [description]; Adds needs-packaging bug for entirely new package.
[09:31] <kubotu>                 newversion <packagename> <version> [description]; Adds update bug for existing package.
[09:31] <kubotu>                 buildstatus <packagename> [release] [ppa]; Buildstatus for package.
[09:31]  * sitter shakes fist
[09:31]  * kfunk winces
[09:31] <sitter> kubotu: newpackage kdev-qmljs 1.7.0 http://download.kde.org/stable/kdevelop/kdev-qmljs/1.7.0/src/ ... kfunk says it is imortant or something
[09:31] <kubotu> https://bugs.launchpad.net/bugs/1420190
[09:32] <sitter> problem solved \o/
[09:32] <kfunk> thanks
[09:32] <sitter> kfunk: you're working on kdevelop?
[09:33] <kfunk> sitter: sinces ages, yes
[09:33] <kfunk> since, even
[09:33]  * sitter did not know that
[09:33] <kfunk> tststs
[09:33] <kfunk> read planetkde.org?
[09:33] <sitter> also, bad answer, mitya57 had things to complain about :P
[09:33]  * kfunk hides
[09:33] <kfunk> yofel: so, say that again? what do I have to do? :)
[09:34] <kfunk> ah, google helped
[09:34] <sitter> kfunk: kdev-python vs. kdev-python-randomnumber-py3 is very messy as they install the same files. also apparently the py2 version actually has a code copy of python itself in the tarball
[09:34] <sitter> all of which makes packagers whine
[09:34] <yofel> kfunk: https://www.debian.org/devel/wnpp/#l1
[09:34] <kfunk> sitter: did you try sending a mail to<EMAIL_ADDRESS>[09:34] <yofel> oh well
[09:34] <kfunk> I think that'd be easiest
[09:35] <sitter> kfunk: enotime :P
[09:35] <kfunk> just nag downstream about this, no need to secretly patch things or such :)
[09:37] <kfunk> could be so easy if the world just had one distro :|
[09:38]  * kfunk fires up 'reportbug'
[09:38] <kfunk> Please enter the name of your SMTP host. Usually it's called something like "mail.example.org" or "smtp.example.org". If you need to use a different port than
[09:38] <kfunk> default, use the <host>:<port> alternative format. Just press ENTER if you don't have one or don't know, and so a Debian SMTP host will be used.
[09:38]  * kfunk is already annoyed by the tool
[09:39] <sitter> kfunk: just send a manual mail
[09:39] <sitter> bug tracking in debian is atrocious, and that tool only makes it worse
[09:39] <kfunk> literally took my 10 seconds to find that out
[09:39] <kfunk> me*
[09:39] <sitter> xD
[09:39] <yofel> this is debian... they also do things like telling people that doing a release upgrade in a running X session is unsupported...
[09:40] <yofel> (although with kde that's actually sensible -.-)
[09:43] <sitter> mh, I think it's not specifically applying to kde software, it just happens to be that gui software is usually using a lot more pieces with generally complicated nonesense such as runtime plugins which in turn makes live upgrades undesirable
[09:44] <sitter> I do very much believe that this is ultimately why windows upgrades usually involve a reboot
[09:45] <sitter> if you pull a library from under the application and put in a slightly different one, chances are one or another application will not take kindly to that
[09:45] <yofel> well, we strongly recommend one too. What we would need is a big red reboot button whenever kdelibs or ksmserver(?) is updated
[09:45] <sitter> ^ at laest for kdelibs that's there :P
[09:45] <sitter> kdelibs triggers reboot notitifcations
[09:45] <yofel> I stopped counting how many times kickoff->shutdown did nothing in vivid
[09:46] <sitter> yofel: you really should take this to #plasma when it happens, that youtube video Riddell posted earlier had a similar thing happening and when I asked notmart he didn't have an immediate guess as to why that would happen
[09:47] <yofel> will do, happens rather often here :P
[09:47] <sitter> it most definitely shouldn't though. not for something as cruical as being able to actually reboot the computer
[09:47] <kfunk> sitter: for Windows it's more easy: you can't overwrite files if they're open -> you can't do shit while $things are running.
[09:47] <sitter> kfunk: ah that is true, hadn't thought of that
[09:48] <yofel> well, there's 2 issues. clicking on shutdown not brining up the shutdown dialog (which is what I juts meant), and the shutdown dialog only quitting plasmashell and nothing more which I have right now (*that* doesn't happen in ci though)
[09:48] <sitter> it makes sense in a way, of course OTOH that does prevent live patching when appropriate and necessary
[09:48] <sitter> yofel: I haven't tested this in a while but the latter case could totally be a random application halting the shutdown
[09:49] <sitter> last I checked what happened was that plasmashell would shut down, then some random app would tell ksmserver to wait because it needs to save something (kate) and then ksmserver never would be able to shut down
[09:49] <yofel> hm, true... I'll try to make a ps dump later
[09:49] <sitter> also the respective window blockign wouldn't be raised xD
[09:49] <sitter> twas a right mess
[09:50] <yofel> well, the only 2 things I usually have still running are quasselclient and yakuake, so I use latter do shutdown over dbus
[09:50] <yofel> *to
[09:51] <sitter> kf5 utopic looks good now
[09:51] <sitter> Riddell: talk to me honey
[09:51]  * Riddell blogs http://wire.kubuntu.org/
[09:51] <Riddell> sitter: yo, what do you need?
[09:51] <sitter> Riddell: more utopic testing
[09:52] <sitter> Riddell: and probably an upload to vivid in case you want to review first, which would be handy
[09:53] <yofel> can someone also please upload calligra from bzr? I added a breaks/replaces
[09:53] <Riddell> what's up with khtml? "E: libkf5khtml5: symbols-file-contains-current-version-with-debian-revision on symbol"
[09:53] <sitter> Riddell: qt5.3 crap
[09:53] <Riddell> kpackage missing manpages?
[09:53] <sitter> I'd just ignore it for now
[09:53] <sitter> Riddell: no, false positives
[09:53] <sitter> because no one can be bothered to fix this properly...............
[09:54] <Riddell> sitter: but if there's new symbols then surely they need added to the .symbols files?
[09:55] <Riddell> new manpages to the .install files
[09:55] <sitter> ................
[09:55] <Riddell> or the not-installed files
[09:55] <sitter> [10:21] <sitter> Riddell: vivid ready except for symbol nonesense because of qt5.3 and false positives that ought to be resolved in git. same for utopic minus the symbol nonesense >.<
[09:55] <sitter> [10:21] <sitter> needs testery
[09:55] <sitter> [10:21] <sitter> Riddell: also do note for the archive upload that plasma-workspace must also be uploaded as it needed adjustments for the new kglobalaccel
[09:55] <sitter> Riddell: the symbols update makes pointless work
[09:55] <Riddell> mm ok
[09:56] <sitter> the real solution to it is have Mirv land qt5.4
[09:56] <Riddell> right
[09:59] <seaLne> ovidiu-florin: we should be announcing the official akademy accomodaion in the next week or 2
[10:01] <seaLne> ovidiu-florin: we are also working on adding more info to the akademy website
[10:04] <Mirv> hopefully really soon now.. (qt 5.4)
[10:05] <sitter> Mirv: <3
[10:05] <Mirv> the emulator packages need some love still, but functionally on the phone example it's now officially good enough
[10:05]  * kfunk wonders if he'll ever get a confirmation of Debian that his bug has been registered
[10:06] <sitter> kfunk: you should get a mail 'Info received ...'
[10:10] <valorie> ovidiu-florin will be an Akademy virgin
[10:12] <sebas> Akademy - deflowering nerds
[10:13] <sitter> Oo
[10:18] <Riddell> sitter: kf5 working good on vivid
[10:18]  * Riddell trys a utopic chroot
[10:20] <kfunk> sebas: lol
[10:22] <kfunk> sebas: btw, I'd be interested in snorkeling instead of scuba diving at A Coruna :)
[10:22] <kfunk> I know, I'm a pussy
[10:22] <Riddell> but where's the canoeing?
[10:22] <sebas> kfunk: not a pussy, I didn't specifically ask for anyone wanting to snorkel, but often it can be combined
[10:22] <sebas> i.e. take the same boat, one group goes under, others stay at the surface
[10:23] <kfunk> yeah, that'd be great
[10:23] <sebas> I read that there are some diving spots which are also fun to snorkel
[10:23] <kfunk> I'm still not sure I can come there earlier. I'm already quite short on vacation days
[10:23] <sebas> kfunk: I can keep you in mind for that, as soon as I find others who want to dive, I'll check with one of the diving centers there about possibilities, and we can try to fit snorkeling in then
[10:24] <sebas> aye, nothing's set in stone, anyway
[10:24] <kfunk> yeah, just ping me again when you're taking a decision
[10:24] <kfunk> awesome
[10:24] <sebas> also, I haven't heard back from anybody yet
[10:24] <sebas> so just an "I'd be interested, we'll see if we can make it work" is fine
[10:25] <valorie> Riddell: you have to set up the canoeing
[10:26] <sitter> <- wants to get drunk on a yacht
[10:27] <sebas> who doesn't? :)
[10:28] <Riddell> sitter: hmm my chroot says https://paste.kde.org/p6yf4mkca
[10:28] <Riddell> on a dist-upgrade
[10:28] <sitter> dist-upgrade from what?
[10:29] <sitter> also turn on resolver debug
[10:31] <kfunk> "Message with no Package: tag cannot be processed!" -- me vs. debian BTS: 0:1
[10:31] <kfunk> granted. I should have RTFM.
[10:32] <sitter> yeah, with an intuitive BTS you only get bugs from actual people :O
[10:47] <valorie> doodly-doo, I <3 you
[10:48] <soee> 2good morning
[10:48] <Riddell> does it need a doodle? do we have much choice in what we choose?
[10:49] <valorie> morning or afternoon
[10:49] <valorie> very simple doodle
[10:49] <Riddell> ah I see
[10:49] <valorie> too many choices make people indecisive
[10:49] <valorie> we should plan a dinner too
[10:50] <kfunk> might be a *bit* too early for all this unfortunately :)
[10:50] <valorie> last year was fun!
[10:50] <valorie> kfunk: I know, I just want to get the ball rolling before people buy tickets
[10:50] <kfunk> fair enough.
[10:51] <kfunk> dinner would be best during "official" akademy, though
[10:51] <valorie> plus this way we have first dibs
[10:51] <ovidiu-florin> valorie: well put
[10:51] <ovidiu-florin> seaLne: thank you for the notice
[10:52] <ovidiu-florin> seaLne: do you have some kind of email notification?
[10:52]  * valorie heads to bed
[10:53] <Riddell> thanks valorie
[10:54] <seaLne> normally when we open registration we subscribe people to a list but that would probably be later on. its https://mail.kde.org/mailman/listinfo/akademy-attendees
[10:55] <seaLne> ovidiu-florin: if you subscribe with the email that is set in identity.kde.org that will save you getting subscribed twice if you use different email addressess
[10:55] <valorie> yw Riddell - gotta earn my Councillor pay
[10:55] <valorie> :-)
[10:56] <seaLne> valorie: is there a timezone issue with the doodle?
[10:58] <seaLne> yeah looks like you set it in USA tz which it then changes based on geoip at a guess
[11:59] <BluesKaj> Hiyas all
[12:00] <Riddell> sitter: kf57 seems to be installing and running good in my utopic chroot once I add the right ppa dependencies
[12:02] <sitter> lol, ok
[12:03] <sitter> does anyone else want to test kf5.7 upgrade on utopic?
[12:10] <BluesKaj> no thanks sitter, vivid is already too annoying for my taste
[12:17] <soee> Riddell: moving 14.12.2 to vivid ?
[12:18] <soee> BluesKaj: but he wants to test it on Utopic, you are scaed it might break your 14.10  ? :)
[12:19] <sitter> Riddell: objections to copy 5.7 utopic?
[12:20] <Riddell> sitter: none
[12:20] <Riddell> soee: dunno sgclark was working on that
[12:21] <BluesKaj> hi soee,. exactly
[12:22] <sitter> W, [#27701]  WARN -- t-4: Caught exception wrong status line: "\x1F\x8B\b\x00\x00\x00\x00\x00\x00\x03\xABV*\xC9/I\xCC\x89/\xCE\xACJU\xB2R0\xD0QP*.I,*\x81\xB2S\xF3J\x8A2S\x8B\x81\xBC\xE8\xD8Z\x00\x16\xCE\x91\xC9,\x00\x00\x00HTTP/1.1 200 Ok"
[12:22] <soee> Riddell: i tested it already liek 2 days ago i think
[12:22] <sitter> W, [#27701]  WARN -- t-3: Caught exception undefined method `closed?' for nil:NilClass
[12:22] <soee> Riddell: smmoth upgrade, without any roblems
[12:22]  * sitter not sure his launchpad module is as threadsafe as it should be
[12:23] <sitter> Riddell: btw, releaseme l10n is now threaded, landing caching still needs some architecture musing on how to best implement the cache transparently
[12:23] <sitter> of course threading alone gives a heafty speedup already
[12:29] <sitter> Riddell: 5.7 for utopic publishing
[13:01] <santa_> sitter: just a quick question, what is the oldest kubuntu version which will have kde frameworks? utopic?
[13:03] <sitter> santa_: yes
[13:05] <santa_> ok, thanks. I will send a patch
[13:31] <sitter> kubotu: newversion about-distro 2.0.1 http://people.ubuntu.com/~apachelogger/tmp/feburary/
[13:31] <kubotu> https://bugs.launchpad.net/bugs/1420289
[13:31] <sitter> kubotu: newversion debconf-kde 1.0.1 http://people.ubuntu.com/~apachelogger/tmp/feburary/
[13:31] <kubotu> https://bugs.launchpad.net/bugs/1420291
[13:32] <Riddell> ooh new stuff
[13:32] <sitter> ^ updates translations
[13:33] <sitter> also I was shocked
[13:33] <sitter> tarme on about-distro took like 10 seconds without caching
[13:33]  * sitter had to diff with old tar as he couldn't believe it would be that fast :O
[13:45] <sgclark> morning
[13:48] <Riddell> hi sgclark!
[13:48] <BluesKaj> 'Morning sgclark
[13:50] <sgclark> Riddell: yeah kde-applications for vivid is good to go, I have not actually done a proper archive upload. help!
[13:53] <Riddell> sgclark: kubuntu-archive-upload is the magic script
[13:54] <Riddell> sgclark: but as ever with these scripts you'll need to know what they are doing and check it is doing it
[13:54] <sitter> the magic script that will screw up :suspicouslook:
[13:55] <sgclark> lol
[13:55] <sitter> it's a script with 268 lines, what could possibly go wrong
[13:56] <Riddell> it should be checking out the packaging from git, downloading the tar, checking they are not out of date with the PPA, committing the release changelog to debian/changelog and making the source files ready to upload
[13:56] <sitter> oh ah
[13:56] <sitter> blimey
[13:56] <yofel> FWIW, Riddell or sitter should do the upload. Only a subset of the applications is actually in the packageset
[13:56] <sitter> Riddell: I know why your uploads of frameworks always were missing things
[13:56] <sitter> the upload script is based on the text files listing the packages
[13:57] <sitter> the ones you always forget to update from what I have seen :P
[13:57] <sitter> ^ the text files I find insulting tbh
[13:59] <sitter> http://paste.ubuntu.com/10158846/
[13:59] <sitter> :S
[13:59] <sgclark> yofel: I know ktux is no good and cantor for the moment... what else do you  mean?
[14:00] <sgclark> Riddell: what yofel states ^ ?
[14:00] <sitter> sgclark: he means you can't upload some of them because you have no permissions outside the kubuntu packageset
[14:00] <sitter> well you can, launchpad will just go 'nono'
[14:00] <sitter> yofel: the question of course is... shouldn't the packages be moved to the packageset?
[14:01] <Riddell> right, would be worth getting a list of those packages and poking whoever can add them
[14:01] <sgclark> oh well then you two should do it then...
[14:01] <sitter> sgclark: no, you should, then you check your mails for rejected things and then we can go annoy someone to add them to the packageset ;)
[14:01] <Riddell> right
[14:02] <sgclark> alrighty
[14:02] <sitter> if kubuntu devs can't upload all packages we maintain it defeats the purpose of being kubuntu dev
[14:02] <Riddell> Tm_T: what did you make of the ubuntu phone?
[14:02] <sitter> so that ought to be fixed
[14:03] <sitter> http://paste.ubuntu.com/10158907/ who can spot the problem?
[14:04] <Tm_T> Riddell: it's proper ubuntu so I wonder what stuff in the repos suopor mir
[14:04] <sgclark> kdeapplications is now kde-applications I think
[14:04] <Tm_T> that's prolly the biggest culptit
[14:06] <sgclark> kf5 does not have a # check
[14:07] <sitter> it's all wrong xD
[14:07] <soee> sitter: wtat is teh language used there ?
[14:07] <sitter> http://paste.ubuntu.com/10158947/ more sensible version
[14:07] <sitter> soee: garbage
[14:07] <sitter> eh
[14:07] <sitter> python
[14:08] <sitter> #freudianslip
[14:08] <sgclark> lol
[14:09] <soee> doesn't look to complicated :)
[14:10] <Riddell> Tm_T: will it take over the world?
[14:14] <yofel> sitter: they should, but maybe you can figure out a good script to get one binary package of each kf5 and application source and add that to the supported seed?
[14:14] <sitter> http://paste.ubuntu.com/10159013/ same thing expressed in rubee
[14:15] <sitter> yofel: it's all getting redone as part of ci tooling if I get my way
[14:16] <sitter> but yeah, the biggest problem with tooling right now is that it has no shared classes (has no classes really) so you can't go in the upload script 'give-me-all-frameworks' and some class would figure out how to do that and how to make sure the list is actually complete
[14:17] <sitter> I mean, making sure the list is complete for the most part would probably entail an ls on depot.kde.org and then building a repo-upstreamsrc-debsrc-deb map
[14:17] <sgclark> archive upload has no support for kde-applications
[14:18] <sitter> which in turn isn't possible because there is no thing that one could ask 'whats-all-our-debsrcs' and then there's no thing 'what-debs-does-this-debsrc-create' etc. etc.
[14:18] <sitter> sgclark: -r kdeapplications
[14:18] <sitter> (from looking at the code)
[14:18] <sgclark> hmm perhaps I need to update my branch
[14:27] <Tm_T> Riddell: I do believe there's a concept that has a place in the market
[14:28] <Riddell> Tm_T: in terms of UI or freedom or what?
[14:29] <Tm_T> well the fact that if need be you can just use apt-get like on any ubuntu
[14:29] <Tm_T> and the fact that the normal use doesn't mean installing dozen of apps that has access to your data
[14:35] <sgclark> Riddell: where does pull-ppa-source come from, I don't seem to have it and I can't find where it would be
[14:36] <Riddell> sgclark: looks like it's in kubuntu-dev-tools
[14:36] <sitter> sgclark: kubuntu-dev-tools
[14:36] <sgclark> thanks
[14:37] <Riddell> which of course should be tidied up and moved into kubuntu-automation
[14:38] <jmux> Do you think it would be a lot of afford to get KF5 and Plasma 5 running on 14.04? Our next major update might be available end of this year and I'm trying to convince myself and the others to switch...
[14:38]  * jmux is currently on a workshop to plan LiMux development for this year
[14:39] <jmux> And - of caouse - colab would still have to run with KDE 4 - not sure how that would interact (akonadi KDE4 and all)...
[14:39] <sitter> there is no kdepim5 anyway, so that should be fine
[14:41] <jmux> How much stuff of the KF5 packages is tied to technologies - like systemd - not available in 14.04?
[14:41] <Riddell> jmux: it doesn't use systemd
[14:41] <sitter> backporting all the stuff might be a bit tricky... off the top of my head you'd need all the frameworks and all of plasma which comes in at some 120 or so source packages, plus 15 for qt, if you care about bluetooth you'd additionally need bluez+pulseaudio, other than that I think from a dependency point of view the gap between 14.10 and 14.04 isn't that big
[14:42] <Riddell> right it's a big job but I don't think a difficult one
[14:42] <sitter> libinput and libepoxy definitely need backporting but I don't think anything in 14.04 uses those, so that's as straight forward as it gets
[14:42] <Riddell> if someone wants to put in the time then sure
[14:43] <jmux> Well - we're more talking about 15.04 base. I don't think the 14.04 based work will start in the next 3 months. And I nhave to think about a KF5 LibreOffice backend.
[14:44] <Riddell> jmux: I did start to look at qt5 libreoffice when in munich and we have a list of the icons and it just needs someone to finish off the script to put the icons in the right place (Quintasan may even have looked at that)
[14:45] <jmux> Hmm - so from your POV there is nothing like "I wouldn't do this, because it would need any changes to a core 14.04 technology" (like gcc compiler)
[14:45] <Riddell> jmux: porting the libreoffice widgets is obviously a bigger task and I suspect I'm scared off that for now
[14:46] <jmux> Riddell: Yeah - I know, but that would still use the KDE4 backend just with KF5 icons.
[14:46] <sitter> jmux: qt is pretty much the most core thing that needs exchanging
[14:46] <jmux> We currently don't have any qt5 based apps, so qt5 would just install parallel to qt4
[14:48] <jmux> So I guess qt5 should - just compile. There is already qt5 5.2.1 in 14.04, so I guess it would be more or less a recompile of current packages.
[14:49] <Riddell> yes I would guess so too
[14:49] <jmux> I've already done a Xorg backport for etch some years agos using automatic scrips and general patches - probably that would be possible for KF5 too.
[14:49] <Riddell> jmux: many kde applications still use qt4 and kdelibs4 so continuing to use libreoffice with new icons is perfectly in line with most kde applications
[14:49] <jmux> That' was something like 60 source packages in these days
[14:50] <jmux> I guess we'll wait for 15.04 and get some testers on it, so they can decide, if it is stable enought
[14:51] <sitter> sounds sensible
[14:53] <sgclark> I am clearly still missing something. http://paste.ubuntu.com/10159427/
[14:54] <sitter> the toolign is all so very terrible :@
[14:54] <sitter> sgclark: what happens if you run that command manually?
[14:55] <sitter> although
[14:55] <sitter> Package not found in the PPA is pretty much as clear as it gets ^^
[14:55] <sgclark> same
[14:55] <sgclark> it is there tho
[14:56] <sitter> #toolingfail
[14:57] <sitter> sources = ppa.getPublishedSources(distro_series=lpseries, status="Pending", source_name=args.package, exact_match=True)
[14:57] <sitter> wut
[14:57] <santa_> I have a somewhat decent tooling to bump the build depends in siduction by the way
[14:58] <sitter> shadeslayer: y u break tools
[15:01] <sitter> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-dev-tools/trunk/revision/202
[15:01] <sitter> sgclark: should be fixed now
[15:01] <sitter> shadeslayer: ^ please fix that properly if you want pending included
[15:01] <sgclark> sitter: great thanks
[15:06] <sgclark> should fatal: '4:14.12.2-0ubuntu1' is not a valid tag name. be something I am concerned about?
[15:06] <sitter> shadeslayer, Riddell: in case I haven't done so by 22 UTC and you happen to be online, please unpause CI http://kci.pangea.pub/job/mgmt_pause_integration/
[15:06]  * sitter will try to remember though xD
[15:06] <sitter> don't want to hammer the builders in the middle of the day
[15:06] <sitter> on that note
[15:07] <sitter> Riddell: have you done the archive upload?
[15:07] <Riddell> nope
[15:07] <sgclark> anyone ^?
[15:07] <sitter> Riddell: are you goint to?
[15:07] <Riddell> wasn't aware I was expected to, should I?
[15:08] <sitter> Riddell: would be lovely
[15:08]  * sitter would only get even more outraged by the shit scripts
[15:08] <sitter> sgclark: broken
[15:08] <sitter> Riddell: how does kubuntu-archive-upload work for you?
[15:08] <sitter> sgclark can't push because it is tagging with tag names that get rejected by git.debian
[15:09] <sitter> (which is interesting in of itself really)
[15:10] <sgclark> wait, next line is already tagged
[15:10] <Riddell> sitter: what do you want me to upload?
[15:10] <sitter> Riddell: frameworks
[15:10] <sitter> sgclark: lol
[15:11] <sitter> it's madness
[15:11] <sitter> all of this
[15:11] <sitter> madness
[15:13] <sgclark> so when this thing is done I will have a pile of .changes to upload to somewhere or ?
[15:13] <Riddell> yep
[15:13]  * yofel wonders why kubuntu-archive-upload still pushes as part of the main loop :S
[15:14] <yofel> sitter: do you have a plan when you want to rewrite all that?
[15:14] <yofel> and is that planned to be ruby?
[15:15] <yofel> and what's with all the quadrupled code in there /o\
[15:16] <Riddell> oh please don't rewrite in ruby
[15:17] <yofel> we should rewrite in python3
[15:17] <Riddell> hmm, someone updated lots of these frameworks in git and didn't update them in the ppa
[15:17] <Riddell> so it's going to prompt me to confirm every one
[15:17] <yofel> -.-
[15:18] <yofel> I think we also have a #workflowfail somewhere
[15:21] <sgclark> Riddell: I did 3 merges last, it was late, I thought I did ppa builds but possibly I forgot...
[15:23] <Riddell> sgclark: what what? I'm just talking about sitter's frameworks packages
[15:24] <sgclark> oh sorry
[15:25] <sgclark> I did fix kpackage, I know I did an upload on that though
[15:28] <sitter> yofel: #toolingfail
[15:29] <sitter> if there is a change in git something should upload to ppa
[15:29] <sitter> sgclark: btw you made your changes in the wrong branch :P
[15:29] <sitter> yofel: also most of it is rewritten in ruby already as part of kci, the concepts underlying all of it anyway
[15:30] <sgclark> sitter: that does not surprise me, where should I have made it?
[15:30] <sitter> on that note, if having the code be ruby prevents people from creating things like this I think I'd be a much less depressed person http://paste.ubuntu.com/10158907/
[15:30] <sitter> sgclark: vivid_archive
[15:30] <sitter> also see my mail about merge orders from a month or two ago
[15:30] <yofel> yeah... but I think you can do that in ruby too :S
[15:31] <sitter> vivid_archive automerges into unstable, unstable into unstable_$series as well as stable, stable into stable_$series
[15:31] <sgclark> alright, yeah I am behind on email, I will look for it. apologies
[15:31] <yofel> if I have some time I might at least try to rewrite parts of what we have (hopefully without breaking anything)
[15:31] <sitter> yofel: yes, since shadeslayer and I are the only ones who actually write ruby that helps a lot
[15:31] <sitter> mh
[15:31] <sitter> actually
[15:31] <sitter> the biggest problem with our current stuff is that there is 0 test coverage :P
[15:32] <yofel> right
[15:33] <sgclark> dumb question, where is this archive upload script putting these .changes files?
[15:34] <Riddell> sgclark: you can specify it in -t foo  or it'll put them in /tmp/<random>
[15:34] <Riddell> I think
[15:34] <Riddell> inside the upload/ directory
[15:34] <Riddell> and anything it gets confused by inside the manual/ directory
[15:34] <sgclark> as much as I crash /tmp is bad... ok thanks
[15:34] <Riddell> I always use -t ~/src/foo
[15:36] <yofel> sitter: please check that I didn't misunderstand that http://bazaar.launchpad.net/~kubuntu-packagers/+junk/kubuntu-automation/revision/509
[15:41] <sitter> yofel: does kdesc actually have to be specified explicitly now?
[15:41] <sitter> other than looks fine
[15:42] <yofel> yes, because it defaults to kdeapplications. With the old logic you already had to do that though because there's a defualt for releasetype
[15:43] <yofel> oh great, we have hardcoded ppa's in there /o\
[15:45] <sitter> yeah
[15:45] <sitter> it's a lovely script
[15:45] <yofel> and shortcut git urls for debian //o\\
[15:45] <sitter> much spaghetti
[15:47] <yofel> I need a break, bbl ^^
[15:56] <yofel> I just fixed the tagging, whoever is against the tags being "ubuntu/<version>" please complain
[15:56] <yofel> now really bbl
[15:57] <yofel> (that's e.g. ubuntu/4%14.12.2-0ubuntu1)
[16:04] <shadeslayer> sitter: oh funsies
[16:04] <shadeslayer> sorry about that
[16:11] <Riddell> sitter: kf5 5.7.0 uploading
[16:16] <Riddell> sgclark: how's your uploading going?
[16:18] <sgclark> Riddell: archive script still running
[16:27] <sitter> yofel: the pre-receive hook serverside might be against it
[16:27] <sitter> didn't it reject anything but a debian prefix or something like that?
[16:27] <sitter> there definitely was some weirdness
[16:33] <shadeslayer> sitter: what to do with QCA in Debian btw?
[16:34] <shadeslayer> It keeps failing with the shit symbols
[16:46] <sitter> remove symbols file
[16:46] <sitter> as part of your build
[16:46] <sitter> or implement the kubuntu_unstable_$series logic to have a divergent branch
 Mmh, we had a kwin 5:66 in squeeze..
 What version number should I use then for kwin?
 6:5.x.x-x ?
[17:42] <yofel> yay, one more epoch version
[17:43] <soee_> ;-)
[17:55] <sgclark> err dput ... where? for archive
[17:56] <sgclark> Riddell: ^
[18:01] <sgclark> nm
[18:56] <ovidiu-florin> What's BoF ?
[19:04] <sgclark> bird of feather meetings, typically mini hackfests / planning meetings
[19:06] <Quintasan> Riddell: Yeah, I'm working on the script right now
[19:06] <Quintasan> I also have to handle the MR for ktron
[19:06] <Quintasan> Urgh'\
[19:11] <Quintasan> Riddell: Could you reply to https://git.reviewboard.kde.org/r/121589/ ? IMO it makes no sense for another MR for the same thing
[19:11] <Quintasan> Unless I'm missing something
[19:13] <sgclark> Riddell: pretty much 80% were rejected for me....
[19:19] <Quintasan> Riddell: Actually, I'd consider having the files renamed as well
[19:32] <Quintasan> Well, nevermind, I'd have to go to do a renaming in the code as well.
[19:37] <Riddell> Quintasan: what do I reply to it?
[19:38] <Quintasan> I'm wondering now.
[19:38] <Quintasan> Riddell: I'd say that the names you proposed should be enough as the initial transition worked this way
[19:40] <Quintasan> Riddell: The whole thing requires major refactoring just to get rid of the names but I have no time to tackle it this week
[20:01] <kfunk> I'm *so* waiting for Plasma 5.2.1 -- that kded5 i-eat-your-cpu bug is driving me crazy :|
[20:01] <R33D3M33R> kfunk: +1
[20:02] <R33D3M33R> the current situation is pretty bad for laptop owners
[20:03] <kfunk> yay, I always notice when my fan is starting to annoy me ;)
[20:05] <soee_> kfunk: we all waiting for it :D
[20:05] <soee_> there is also fix for kwrited
[20:10] <R33D3M33R> anyone knows why was the metapackage kdegames removed from vivid?
[20:29] <yofel> R33D3M33R: yes, not sure why though
[20:30] <yofel> "  * Remove kde-sc meta packages, they are no longer valid"
[20:30] <yofel> Riddell: that's not completely true...
[20:30] <yofel> it's not like all the applications are removed from the archive
[20:31] <R33D3M33R> interesting
[20:33] <yofel> Riddell: the only thing that's no longer valid are the meta packages that contained the old plasma workspace
[20:36] <santa_> yep, they can/should be reworked (I did for my siduction stuff)
[20:40] <Riddell> yofel: yeah they can be recreated if you like but with all the changes in upstream releases my feeling is that kubuntu has its own meta packages and if debian wants to have some others that's up to them
[20:41] <santa_> well, that's also true, I reworked it because those are our metapackages too
[20:42] <santa_> unrelated question: are you backporting phonon 4.8.3 to utopic?
[20:45] <sgclark> Riddell: did you see my epic rejection list? it is causing the few that did not get rejected to fail.
[21:06] <ovidiu-florin> sgclark: thank you
[21:07] <ovidiu-florin> I asked what's BOF because my name is Bogdan Ovidiu-Florin so... BOF :D
[21:07] <sgclark> ah hehe
[21:08] <ovidiu-florin> In romania we usually put our Last name at the beginning
[21:08] <ovidiu-florin> even though we call the First name "first name" (literal translation
[21:08] <ovidiu-florin> )
[21:29] <yofel> # Enforces some rules in the repository.
[21:29] <yofel> #
[21:29] <yofel> # Packaging tags:
[21:29] <yofel> #
[21:29] <yofel> # * tag is under debian/ namespace;
[21:29] <yofel> that, is a problem :S
[21:31] <yofel> except that... "#error("only tags in the debian/ namespace are allowed");" is clearly commented out...
[21:32] <yofel> hm, there's a version check too though :/
[22:07] <Riddell> sgclark: yep, I don't know who controls the keys to that but cjwatson would be a good try to forward it to
[23:17] <soee> sgclark: some 14.12.2 packages  are uploaded to archive? i see some update
[23:31] <sgclark> soee: sorry, despite being kubuntu developer 80% of the packages were rejected saying I did not have upload rights.
[23:31] <soee> :-)
[23:32] <soee> strange that there are so big restrictions when it comes to uploads
[23:33] <yofel> comes from having to manage a lot of developers :/
[23:34] <yofel> sgclark: you can upload what's in the packageset for kubuntu ("edit-acl -P kubunt -S vivid query" from lp:ubuntu-archive-tools tells you the package list)
[23:34] <soee> hmm, there should be few people that could coordinate this and give proper rights to trusted devs
[23:35] <yofel> said packageset is generated from the packages in our seed (i.e. what's on the release image + the supported seed)
[23:35] <sgclark> yofel: that is not very many haha
[23:35] <yofel> soee: that's called being an ubuntu-core-dev...
[23:37] <sgclark> yofel: and as you said they should have done it.. oh well, seems that a kubuntu developer should be able to upload kde stuff... I sent an email to this cjwatson, we'll what happens
[23:40] <yofel> yeah sure, but the problem is how you define "kde stuff". As I said, it's stuff on our images and dependencies (e.g. you can change x264, if you ever want to) so random new kde applications that we don't explicitely ship and where we don't say that we support them are not something we can change
[23:40] <valorie> hopefully I fixed the doodle poll
[23:46] <sgclark> well I do not define kde-applications as ubuntu-core, alas I digress, I tried, I failed, moving on.
[23:57] <yofel> right, it's not a fault on your side, someone will just have to fix our packageset
[23:58]  * yofel is off to bed, gn8
[23:58] <sgclark> night!