[00:00] <jcastro> ok everyone, let's get started
[00:01] <jcastro> please announce yourself and from which LoCo you hail from
[00:01] <jcastro> I'm Jorge Castro and I'm from ubuntu-michigan
[00:01] <nhandler> I'm Nathan Handler and I'm with ubuntu-chicago
[00:01] <jcastro> For the next hour I will be running a session on how to run an effective "bug jam" for your Local Team
[00:02] <jcastro> LoCo teams from around the world will be participating in the Ubuntu Global Bug Jam: https://wiki.ubuntu.com/GlobalBugJam
[00:02] <jacob> jacob from ohio..!
[00:02] <jcastro> so the primary goal of these sessions are to provide help, tips, and tricks in how to make that more efficient and fun for everyone
[00:03] <jcastro> though a LoCo can have bug jams as much as they want
[00:03] <jcastro> For example in Berlin they have a bug jam every 2 weeks!
[00:03] <jcastro> Looks like we have good representation from the midwest
[00:03] <jcastro> anyone else?
[00:04] <jcastro> ok, let's continue. :)
[00:05] <jacob> heh, small group.
[00:05] <jcastro> So, the primary piece of documentation that is important for a bug jam is this page: https://wiki.ubuntu.com/RunningBugJam
[00:05] <jcastro> if you're doing a real life bug jam, ie. meeting someplace
[00:05] <jcastro> then the venue is probably the most important part
[00:06] <jacob> jcastro: bug jams have been done online? wasn't aware of that
[00:06] <jcastro> because that takes planning and choosing a location that fits for the loco
[00:06] <jcastro> yes, in fact, one of the most successful groups during the last GBJ was club-ubuntu
[00:06] <jcastro> which is a group of people without a physical loco
[00:06] <jacob> mm, interesting.
[00:06] <jcastro> of course, we encourage people to get together physically
[00:07] <jcastro> in fact, the goal of the bug jam isn't so much fixing bugs, as it is an opportunity for the loco to get together and have a good time
[00:07] <jcastro> so you shouldn't have a goal of something like "We should try to do X bugs as a loco"
[00:07] <jcastro> the goal should be that everyone has a good time
[00:07] <jcastro> and learned something about ubuntu
[00:08] <jcastro> so your venue should probably be centrally located
[00:08] <jcastro> or on a place that's easy for people from around the area to congregate at
[00:08] <jcastro> power and internet are of course important.
[00:08] <nhandler> And a projector can come in handy too
[00:08] <jcastro> yep
[00:09] <jcastro> one thing we found useful
[00:09] <jcastro> was to tell people to get their launchpad accounts ready beforehand.
[00:09] <jacob> Panera has been friendly with the power and wireless, though they have a 30min cap on wifi as of a few months ago (d'oh)
[00:09] <jcastro> new people will show up and need accounts, but it helps if you can get people to at least do those before they show up
[00:10] <jcastro> the projector is useful because we used it to keep a list o bugs we were working on
[00:10] <jcastro> and when someone got "stuck", someone would put the bug on the projector
[00:10] <jcastro> and then the group would go over the bug, discuss possible actions, and then recommend what to do
[00:10] <jcastro> this is useful because it allows new people to see how bug workflow works
[00:10] <jcastro> and it allows you to work together
[00:11] <jcastro> because it's easy to get rusty if you're not doing your 5-a-day. :)
[00:11] <jcastro> Promoting the jam is also key
[00:11] <jcastro> on the wiki page we provide a PDF that you can print
[00:11] <jcastro> (someone even translated it to spanish!)
[00:11] <jcastro> of course we encourage people to blog/dent/post on the forums, etc.
[00:12] <jcastro> You'll want to take pictures of the jam so you can share those with other Local Teams
[00:12] <jcastro> https://wiki.ubuntu.com/GlobalBugJam
[00:13] <jcastro> if you look on that page you'll see a list of bugs that we've classified from easy to hard.
[00:13] <nhandler> jcastro: You mentioned 5-a-day a few minutes ago. I would just like to mention that Daneil Holbach is currently working on improving 5-a-day, and plans to release a new version prior to the Global Bug Jam.
[00:13] <jcastro> right
[00:13] <jcastro> it'll be easy to just join a team
[00:13] <jcastro> instead of having an applet and all that
[00:13] <jacob> cool, i think that was a bit of a barrier when introducing some to 5-a-d
[00:13] <jcastro> For your new volunteers, something like "New bugs without a package assigned to them" would be useful
[00:14] <jcastro> yeah, that's why it's going away
[00:14] <jcastro> you'll just join your loco group in lp, and a 5-a-day group
[00:14] <jcastro> and then that's it
[00:14] <jcastro> Bugs marked for expiration are also good for beginners
[00:14] <jcastro> one can probably check those bugs for days asking the reporter if they still experience the bug.
[00:15] <jcastro> For more advanced and intermediate people we have lists as well
[00:15] <nhandler> needs-packaging bugs are also pretty easy to triage.
[00:15] <jcastro> yep
[00:15] <jcastro> You can pair people off, or small groups, or individual, whatever works for your team
[00:15] <jcastro> I tend to like pairing off experienced people with new people
[00:16] <jcastro> the experienced person won't get as many bugs done, but in the long run teaching their knowledge pays off
[00:16] <jcastro> plus since it's face-to-face, you can get alot of tutoring done, and then let the new person improve on their own after the GBJ
[00:17] <jcastro> teaching someone to fish vs. giving them a fish kind of thing
[00:17] <jcastro> any questions so far?
[00:17] <nhandler> Nope
[00:17] <jcastro> We also have a video of how to run a bug jam: http://www.youtube.com/watch?v=mBY7wfX2jpA
[00:17] <jacob> would it be a good idea to try to get a bug jam of sorts going on during a release party?
[00:17] <jcastro> also, all the videos in the developer channel
[00:17] <jacob> those have been ohio's most successful events in terms of attendance
[00:17] <jcastro> you could have those running on the projector too while people are doing stuff
[00:17] <jcastro> yes
[00:18] <nhandler> jacob: I believe that is what the French Loco did too
[00:18] <jacob> while the idea of a bug jam on the mailing lists has been met with a bit of silence
[00:18] <jcastro> in fact, we want LoCos to spontaneously run jams
[00:18] <jcastro> we also encourage locos to run jams at events
[00:19] <jcastro> so while we didn't have internet at the ohio linuxfest we still had a tutorial session on bug best practices, etc.
[00:19] <jacob> (if only there was internet access at OLF, that would be a great place for one)
[00:19] <jcastro> yeah
[00:19] <jcastro> We didn't try this at my loco last year but we plan to try
[00:19] <jcastro> https://wiki.ubuntu.com/GlobalBugJam/Bingo
[00:19]  * nhandler found the greasemonkey script annoying
[00:20] <jcastro> you can also think of local prizes or ways of rewarding people who are doing well
[00:20] <jcastro> again, don't worry about the actual numbers, worry about having a smooth run event where people are having a good time
[00:20] <jcastro> some loco's have jams at pubs, or they might go to a pub after, or whatever
[00:20] <jcastro> so it's very much a social thing
[00:21] <jcastro> a new volunteered shouldn't feel bummed out if they only get through one bug for example
[00:21] <jcastro> every little contribution is appreciated
[00:21] <jacob> i think our (ohio's) main barrier is getting people to *go* to the actual events - plenty show up on irc ;)
[00:21] <jcastro> well
[00:21] <jcastro> for non-GBJ days you can always do what club ubuntu does
[00:22] <jcastro> pick a date on the calendar and just do it in irc.
[00:22] <jcastro> sometimes a LoCo might want to pick one thing and work on those bugs
[00:22] <jcastro> for example "hey, we all like pidgin, let's focus on that."
[00:22] <jcastro> or something
[00:22] <jacob> jcastro: we've been doing that with a bit of success on Friday's, "5-a-day Friday"
[00:22] <jcastro> ah, excellent.
[00:22] <jcastro> I didn't know that, you should blog that. :D
[00:23] <jacob> it's quieted down recently, but i think i'll poke some people to get it running :P
[00:23] <nhandler> jacob: You might also consider turning it into a community-wide Bug Day
[00:23] <jacob> yeah, that's an idea. something for #ubuntu-bugs perhaps?
[00:24] <jcastro> whichever way works for your LoCo is encouraged.
[00:24] <jcastro> yeah, there are existing bug days
[00:24] <jcastro> called hug days
[00:24] <jacob> right
[00:24] <jcastro> it might be a good idea to just get your loco started in that
[00:24] <jcastro> and just set some small but attainable goals
[00:24] <jcastro> like "this cycle we'll do 2 hug days and the GBJ"
[00:24]  * jacob searches for the next hugday
[00:25] <nhandler> February 19 jacob
[00:25] <jacob> nhandler: thanks, that's close
[00:25] <jcastro> in our LoCo we really only do the release party and the GBJ as our two main events per cycle
[00:25] <nhandler> jacob: https://wiki.ubuntu.com/UbuntuBugDay/20090219
[00:25] <jcastro> and inbetween people try to do their 5-a-day
[00:26] <jcastro> any other questions or ideas?
[00:27] <nhandler> What wiki pages would you recommend showing to new contributors at/prior to the GBJ?
[00:27] <jcastro> ah
[00:27] <jcastro> good question
[00:27] <jacob> just remembered this: https://wiki.ubuntu.com/OhioTeam/5-A-Day-Friday if you're interested in that
[00:27] <jcastro> https://wiki.ubuntu.com/Bugs
[00:28] <jcastro> so we've revamped these pages to be easier to read
[00:28] <jcastro> and not so daunting
[00:28] <jacob> jcastro: indeed, those are much more pretty than I remember
[00:28] <jcastro> triaging is probably the best thing to get people started on
[00:29] <jcastro> It wouldn't hurt at the beginning of the jam for someone to go over a simple bug
[00:29] <jcastro> and the documentation
[00:29] <jcastro> though it's broken right now, remember staging.launchpad.net is a test instance of lp with test data
[00:30] <jcastro> so you can  make example bugs in there to help teach people
[00:30] <jcastro> without adding noise to the normal bug tracker
[00:30] <nhandler> Will staging.launchpad.net be up again by the GBJ?
[00:30] <jcastro> that is useful because people can click around and get a hang of it
[00:30] <jacob> ah, another thing - ustream.tv, works out well for demonstrating bugs if you have the right video hardware for streaming
[00:30] <jcastro> yeah it's been messed up today
[00:31] <jcastro> normally it's up and around though
[00:31] <jcastro> hmmm, any other tips?
[00:33] <nhandler> We have the Greasemonkey scripts that are very helpfuli
[00:33] <nhandler> s/helpfuli/helpful/
[00:33] <jcastro> ah, good pointer
[00:34] <jcastro> https://code.edge.launchpad.net/launchpad-gm-scripts
[00:34] <jcastro> though I would let the intermediate/advanced users use those
[00:34] <jcastro> I have found that explaining GM in the first place can get complicated for people
[00:35] <nhandler> I find the karma script very useful. It shows a user's LP name next to their real name. It also shows their karma and certain teams that they are on. This is useful for spotting comments from more experienced users.
[00:36] <jacob> nhandler: +1, i've added other teams to that script (our loco for example, makes it easy to spot team activity)
[00:37] <jcastro> that's a good idea
[00:38] <jcastro> I am trying to think of other wacky ideas
[00:38] <jcastro> but this is pretty straightforward and both your LoCos have been around for a while
[00:38] <jacob> bug jeopardy? "i'll have 'Bugs without a Package' for $500"
[00:39] <jcastro> haha
[00:39] <nhandler> What would you advise LoCo's that don't really have any experienced bug triagers do to participate in the GBJ?
[00:39] <jcastro> nhandler: I always learn by following along
[00:39] <nhandler> jcastro: Following along where? In #ubuntu-bugs?
[00:39] <jcastro> one thing I find useful is finding a person who is an experienced triager and follow their work
[00:39] <jcastro> yep, either in irc or on launchpad
[00:39] <jcastro> for example (give me a sec)
[00:41] <jcastro> ok so Pedro is a good example of an experienced bug person
[00:41] <jcastro> https://bugs.edge.launchpad.net/~pvillavi
[00:41] <jcastro> that's the list of bugs he's touched
[00:41] <jcastro> you can have new people open a bunch of those in their browser
[00:41] <jcastro> and see how he does his work
[00:41] <nhandler> Most of the people at the top of the 5-a-day list (http://daniel.holba.ch/5-a-day-stats/) are pretty experienced too
[00:42] <jcastro> yep
[00:42] <jcastro> and also, ubuntu-bugs will be hopping with people
[00:42] <jcastro> and of course they will be available to answer questions, etc.
[00:42] <jcastro> one thing I find useful for the irc channel
[00:42] <jcastro> is to have one person representing the group
[00:42] <jcastro> and ask the questions on irc
[00:42] <jcastro> and then announce the answer or whatever in the room
[00:42] <nhandler> jcastro: Didn't bdmurray create a tag for LP that was used for new triagers to request help?
[00:43] <jcastro> that way you don't have people sitting next to each other all asking the same questions.
[00:43] <jcastro> hmm, I don't recall that
[00:43] <jcastro> but that is a good idea
[00:43] <jcastro> I will ask him and then add the info to the bug page
[00:43] <nhandler> Thanks a lot jcastro
[00:43] <jcastro> wow, that seems like a really great idea now that I think about it
[00:44] <jcastro> but at the minimum, if someone is totally lost, having them follow along with someone else or just watching a bug will help them
[00:45] <jcastro> bug work can be complicated and frustrating, so don't force it, go at their pace.
[00:46] <jcastro> any other ideas or questions?
[00:49] <jcastro> well, as always, people can ask questions on the loco lists
[00:49] <jcastro> or get ahold of me via<EMAIL_ADDRESS>[00:49] <jcastro> so go forth and conquer bugs!
[00:49] <jcastro> if you use KDE, you can go forth and konquer bugs!
[00:49] <nhandler> Thanks a lot for giving this great session jcastro !
[00:49] <nhandler> :)
[00:49] <jcastro> thank you for coming!
[00:50] <jacob> great session jcastro :)
[00:50] <jcastro> happy unix epoch everyone!
[00:50]  * jacob parties \o/
[00:50] <Rafik> thx jcastro :)
[00:52] <jcastro> wow, a fourth person!
[00:53] <nhandler> jcastro: I think you had a few people silently watching the session.
[00:54] <mattt> i found out about this channel too late, doh!  :)
[01:02] <nhandler> IRC Logs for jcastro's session are available here: http://paste.ubuntu.com/117893/
[01:03] <mattt> handy, tnx
[01:05] <nhandler> You're welcome matt
[03:20] <andresmujica> hmm...


[01:49] <InHisName> and maybe a few NewJerseyites
[10:19] <JonathanD> Good morning.
[10:35] <InHisName> Good morning JonathanD and I thought I got up earlier than usual.
[10:35] <JonathanD> It's nice out :D
[10:35] <JonathanD> long run today, I think.
[10:36] <JonathanD> before it gets un nice.
[10:40] <rmg51> morning JonathanD InHisName
[10:41] <JonathanD> Howdy rmg51
[10:41] <rmg51> o/
[10:41] <InHisName> So far only the two of us /// three
[10:42] <InHisName> plus one (stuffed)
[10:47] <rmg51> you have to wait till later for Teddy
[10:48] <InHisName> Don't like dual lappys so early in morning ?
[10:51] <Bikie> Just call me a stuffed bicycle
[10:52] <JonathanD> Hello stuffed bicycle
[10:59] <Bikie> Hi JonathanD
[11:08] <JonathanD> off to run
[12:24] <rmg51> off to work
[13:22] <andrew> morning
[13:58] <teddy-dbear> morning andrew
[14:14] <InHisName> off to typing at chat - oops already there!
[14:15] <Bikie> High stuffed bear from a lowly stuffed bicycle
[14:19] <teddy-dbear> o/
[14:21] <Bikie> teddy-dbear: o/
[14:21] <teddy-dbear> \o
[14:21] <teddy-dbear> o/
[14:22] <teddy-dbear> \o/
[14:22] <teddy-dbear> :-D
[14:22] <InHisName> O:-)
[14:34] <Bikie> ~  __0   _-\<,_ (*)/ (*)
[14:34] <Bikie> bad insert - inhisname type for me
[14:35] <InHisName> ~  __0
[14:35] <InHisName>  _-\<,_
[14:35] <InHisName> (*)/ (*)
[14:35] <teddy-dbear> ??????????????????
[14:35] <PennBot> It has been said that ? is a question mark, silly, teddy-dbear
[14:36] <InHisName> Silly bear ?? are for people
[14:36] <InHisName> and trix are for kids
[14:36] <teddy-dbear> that I am PennBot`
[15:00] <SamuraiAlba> May the bacon be with you all
[15:00] <SamuraiAlba> Client called.  Demands I be there in 15 minutes, 60 miles away, due to "hard drive failing" Windows Recovery Virus on his Pawn Shop PC that holds all the photos and dox for pawn transactions
[15:01] <SamuraiAlba> Friend of mine lives 5 blocks away and gives mee 40% of ALL business cash I send him
[15:01] <Bikie> Hey baconerizer!
[15:01] <SamuraiAlba> I told him, "EMERGENCY" rates.  $100 normal, 100 emergency.  PER HOUR
[15:01] <SamuraiAlba> He just arrived
[15:01] <SamuraiAlba> He's 5 blocks from Client
[15:01] <SamuraiAlba> Client aggreed to $200/hr
[15:01] <SamuraiAlba> AND...
[15:02] <SamuraiAlba> Friend is removing HD from PC and fixing it on a secure lappy
[15:02] <SamuraiAlba> Avg scan/fix there is 3.5/4hrs
[15:02] <SamuraiAlba> :)
[15:02] <Bikie> Whotta deal, IF you can succeed
[15:02] <SamuraiAlba> I fixxed that virus before
[15:02] <SamuraiAlba> takes 10 minutes...
[15:03] <SamuraiAlba> mostly copying files back from %temmpdir%/smtemp
[15:03] <Bikie> Oh, so you know the cause, then its easy.
[15:03] <SamuraiAlba> and unhiding his files in the program start menu
[15:03] <SamuraiAlba> friend is doing full, "If I find a rootkit the price doubles" scan, just to be safe
[15:03] <SamuraiAlba> I told him not to double...
[15:04] <SamuraiAlba> Client was crying and begging...
[15:04] <SamuraiAlba> I feel bad...
[15:04] <SamuraiAlba> ok.. bad feeling was just gas :)
[15:06] <SamuraiAlba> He's also being sued for $150k... Daughter caught a SECOND time downloading movies
[15:06] <SamuraiAlba> after I blocked em on the router... I blocked BT and a crap load of sites, and pirate bay
[15:06] <SamuraiAlba> she knew how to reset the router to factory, it seems
[15:14] <SamuraiAlba> 113 infections on PC, so far...
[15:14] <SamuraiAlba> told my subby to LITERALLY cut the ethernet cable, and block the PC MAC on the router
[15:15] <SamuraiAlba> no need for internet on that PC
[15:15] <SamuraiAlba> any file backups can be done via USB...
[15:15] <Bikie> wow - and probably more
[15:15] <SamuraiAlba> he said...
[15:15] <Bikie> No need for internet, what an improvement on that problem.
[15:15] <SamuraiAlba> "Why is there C:/Program files (x86)/Limewire"?
[15:16] <SamuraiAlba> and "wtf is microtorrent on here?!?"
[15:16] <Bikie> Pirate bay etc.
[15:16] <SamuraiAlba> *why the...
[15:16] <SamuraiAlba> ooog!
[15:16] <Bikie> Seems the blocks were remove quite a while ago.
[15:17] <SamuraiAlba> CLIENTS DAUGHTER was using PC all week at the shop, since he is now taking the cable modem with him when he leaves for work LOL
[15:17] <SamuraiAlba> I'm going down there on Saturday
[15:17] <Bikie> This guy need a 'button" to click and it tests router for factory default.  Gives error if there.
[15:17] <SamuraiAlba> I'm instituting FULL lockdowns on ALL his WORK and HOME and PORTABLE devices.
[15:18] <SamuraiAlba> and guess who will be the system admin?
[15:18] <Bikie> Then another button to install your preset 'default' to put things back.
[15:18] <SamuraiAlba> _ME_
[15:18] <SamuraiAlba> This client doesnt deserve admin access on his own tech.
[15:18] <SamuraiAlba> And I'm charging $600 for the day
[15:19] <SamuraiAlba> for when I go down
[15:19] <SamuraiAlba> I'm gonna secure that crap so tight, air wont get in or out of the pc case, figuratively speaking
[15:20] <Bikie> Until some hacker says 'watch me break air!!'
[15:20] <SamuraiAlba> lol
[15:20] <SamuraiAlba> This client is gettng an earfull, as we speak
[15:20] <andrew> Oh look, a wall of bacon.
[15:20] <SamuraiAlba> bacon?!?!
[15:20] <SamuraiAlba> where!?
[15:21] <SamuraiAlba> Luckily, my service contract WITH this client gives ME, and not HIM, the right to terminate the contract at any time :)
[15:21] <SamuraiAlba> Hiya, Andrew
[15:21] <andrew> the service contract gives you ME?
[15:21] <andrew> I feel sorry for you.
[15:21] <SamuraiAlba> umm
[15:21] <andrew> Along with anyone else forced to use Windows ME
[15:21] <SamuraiAlba> It states I may terminate the contract at any time, and he has to wait to the end of the contract if he wants it to end, and I dont
[15:22] <SamuraiAlba> ahhh
[15:22] <SamuraiAlba> just got the joke LOL
[15:22] <SamuraiAlba> This client makes my no no spot BLEED
[15:22] <SamuraiAlba> argh
[15:22] <SamuraiAlba> He keeps giving out his admin password and this crap ALWAYS happens
[15:22] <SamuraiAlba> I make about $140 a week off of him
[15:23] <SamuraiAlba> I told him he should make his daughter pay, but she is a colelge student and just lost her job
[15:23] <SamuraiAlba> what an idjit
[15:23] <SamuraiAlba> I need to head down there...
[15:23] <SamuraiAlba> Nao
[15:23] <SamuraiAlba> ttyl
[15:23] <Bikie> bye good porkin
[17:48] <ChinnoDog> Ubiquity is crashing in vbox. I can't win
[18:22] <ChinnoDog> I fixed it 0_0
[18:33] <ChinnoDog> hrm. It crashed later on.
[18:33]  * ChinnoDog shrugs


[11:13] <Rhonda> klebers: Any news, have you heard anything?
[17:13] <klebers> Rhonda, hi! We have the fix backported to the affected kernels and they are queued to be included in our next SRU cycle.


[00:02] <eruditehermit> cnd, hey, is gesture support working?
[00:40] <cnd> I can't seem to get xorg-server to build properly
[00:40] <cnd> I'm using parallel=16
[00:40] <cnd> I think that may have something to do with it
[00:40] <cnd> but that has always worked in the past
[00:40] <cnd> I'm trying without any parallel
[00:41] <RAOF> cnd: What's failing?
[00:41] <cnd> that's the thing, I don't know
[00:41] <cnd> it's very non-obvious
[00:41] <RAOF> Aah, the joys of no multiplexing.
[00:41] <RAOF> Got it pushed to git?  I can build locally.
[00:42] <cnd> RAOF, this is what I get at the end: http://paste.ubuntu.com/906483/
[00:42] <cnd> I'll push to git
[00:42] <RAOF> We can also turn on the integration tests while where at it.
[00:42] <cnd> pushed
[00:45] <RAOF> Yeah, the actual error will be waaaaay back.
[00:45] <RAOF> Oh!  That's why this system's so slow.  I seem to be using 4G of swap.
[00:45] <RAOF> Ah, Chromium and Evolution, you are marvellous, but perhaps not 6G worth of marvellous.
[00:46] <cnd> Chromium I can understand, but Evolution? marvelous?
[00:47] <cnd> RAOF, ahh
[00:47] <cnd> it's your gtest patch
[00:47] <RAOF> Well, perhaps not marvellous.
[00:47] <RAOF> But “less sucky than the alternatives”
[00:48] <RAOF> cnd: Oh, that breaks something?
[00:48] <RAOF> cnd: Or the tests are failing?
[00:48] <cnd> yeah, all over :0
[00:48] <cnd> they won't compile
[00:48] <cnd> probably due to the libxorg-gtest changes
[00:48] <RAOF> That'd be right.
[00:48] <cnd> RAOF, http://paste.ubuntu.com/906488/
[00:49] <RAOF> Allow me to fix that for you
[00:49] <cnd> RAOF, unfortunately, we need the server pushed with one of the other fixes asap
[00:49] <cnd> do you think you can get this fixed and uploaded today?
[00:49] <RAOF> Well, it won't fail on the buildds.
[00:49] <RAOF> Because it won't build those tests.
[00:50] <cnd> ahhh
[00:50] <cnd> RAOF, would you rather upload now, and you can fix it in due course?
[00:50] <cnd> or fix it now and upload in a few hours
[00:50] <RAOF> If you've got urgent fixes, upload now.
[00:50] <cnd> ok
[00:50] <RAOF> I'll fix it in due course.
[00:51] <RAOF> It's not like the build time checks are urgent.
[00:51] <RAOF> Also, they'll cause the X server to hit dep-wait until the relevent packages get promoted.
[00:51] <cnd> yeah
[00:51]  * cnd fires of a nocheck build
[00:51] <cnd> off*
[01:30] <Sarvatt> ooo, ITPs for utouch in debian, awesome!
[01:41] <cnd> yep :)
[01:41] <cnd> Sarvatt, now that utouch doesn't require a multi-thousand line patch in xserver, we figure it might actually make it into other distros :)
[01:41] <cnd> it's a crazy thought
[01:42] <Sarvatt> cnd: yeah its freaking awesome that the X side doesnt need crazy stuff now, except now xfixes!!
[01:42] <cnd> heh
[01:42]  * cnd points at RAOF
[01:42] <cnd> it's not me this time!
[01:42]  * Sarvatt points at RAOF too
[01:43] <cnd> I got my crap out before the LTS release at least :)
[01:43] <Sarvatt> its still much less of a change than is needed in all the gnome crap though :)
[01:43] <cnd> maverick is almost dead
[01:43] <RAOF> cnd: Yeah, it's high priority to get that done.
[01:43] <Sarvatt> and the whole compiz supported by pkg-xorg in debian and desktop team in ubuntu thing
[01:52] <Sarvatt> it would be awesome to see unity in debian optionally at least, but yeah its not the gnome 2 everyone wants to keep going, not like theres gonna be anyone caring outside of ubuntu, and its complicated enough that its more than one person could do most likely
[01:53] <Sarvatt> utouch-evemu will be freaking useful at least regardless :)
[02:01] <Sarvatt> unity in debian is strange, gnome 3 is forced on everyone so its "accepted" but theres a lot more work needed for unity that noone wants to deal with
[02:03] <Sarvatt> but i see complaints that its not even in debian
[02:04] <Sarvatt> it took me over a year to accept and embrace the changes in unity
[02:05] <Sarvatt> aka its less shit than what i would put up with in gnome 3
[02:07] <Sarvatt> guess thats too real to say in a channel bound by the CoC, I'm sorry :)
[02:12] <RAOF> :)
[02:12] <RAOF> I think it's getting less difficult to package Unity over time.
[02:13] <Sarvatt> yeah i feel the same way, compiz is the big problem still imo
[02:13] <Sarvatt> "someone" needs to maintain it in debian before it just gets removed, pkg-xorg is maintaining it now but none of us are in that path
[02:16] <Sarvatt> the people maintaining it in ubuntu which is the only place its released for atm are in pkg-gnome
[02:16] <Sarvatt> debian is still on 0.8.x compiz
[02:17] <Sarvatt> aka lucid compiz
[02:17] <RAOF> Oooh, urgh.
[02:23] <Sarvatt> RAOF: btw, s precise still boned for ivb for you?
[02:23] <Sarvatt> i need to check that out if so
[02:23] <RAOF> Yes, it is.
[02:23]  * Sarvatt is still on 11.10
[02:24] <Sarvatt> RAOF: displayport monitors by any chance?
[02:24] <RAOF> I'm not restarting for a while because it's doing a backup, but the current status is that I know 3.3-rc7 works, and our 3.2 kernel doesn't.
[02:24] <RAOF> Yes, I am indeed using a DP monitor.
[02:24] <RAOF> Because screw that VGA nonsense.
[02:24] <Sarvatt> ok so crap I cant check, go figure
[02:24] <Sarvatt> i've heard many woes about 3.2 and dp though
[02:25] <Sarvatt> all the OEM crap is using 11.10 so i've had to care about that more, i'm glad someone can care about 12.04 :P
[02:26] <Sarvatt> the intel guys say 3.2 is fail for dp though, i'll see if i can come up with anything for that
[02:28] <Sarvatt> tuesday is the latest kernel changes can go in for the 12.04 livecd kernel, go figure its tight timing
[02:33] <RAOF> You reckon that DP is the issue?  That should significantly reduce my bisection requirements.
[02:34] <Sarvatt> 100% positive
[02:34] <Sarvatt> i'm monitor shopping now
[02:35] <Sarvatt> your monitor have hdmi/dvi ports to be sure?
[02:35] <RAOF> It does, yes.
[02:35] <Sarvatt> do you have cords to check? :P
[02:36] <RAOF> I presume that a (passive) DP→DVI connector would work?
[07:57] <tjaalton> Sarvatt: hmm, having these in git would make things easier ;)
[07:58] <tjaalton> for me anyway, but a debdiff isn't too bad..
[10:01] <tjaalton> meh, forgot to add DM-Upload-Allowed to libwacom..
[10:14] <tjaalton> oh well, replied to my AM, so hopefully that won't be an issue for too long
[19:47] <FernandoMiguel> hi


[01:55] <Unit193> Cheri703: Talked to someone for a short time sat that lives somewhere around here using Ubuntu.
[01:55] <Cheri703> \o/
[01:56] <Cheri703> we need to plan another ubuntu hour :)
[15:05] <thafreak> Anyone know anything about cpu temperatures?
[15:05] <thafreak> I have a 6 core amd phenom constantly peaking above 60c
[15:06] <thafreak> and the mb alarm keeps going off...
[15:06] <thafreak> is that so hot it will damage the machine, or is it ok
[15:06] <thafreak> I just have the stock cooler on there...been thinking I should grab beefier cooler
[15:19] <andygraybeal_> i can't help you much but  my shit hangs around 30-37
[15:21] <andygraybeal_> imma go get some brunch
[15:22] <thafreak> yikes...
[15:23] <thafreak> don't want it to melt....
[15:23] <thafreak> guess i need a beastly cooler
[15:23] <thafreak> Also, FYI, I probably said this before, but aria2==badass
[15:23] <thafreak> it's like wget on roids
[15:24] <thafreak> can download the same file from a bunch of http/ftp urls at the same time...kind of like a torrent
[15:24] <thafreak> and it supports checksumming the final download to make sure it's ok
[15:24] <thafreak> oh, and it can also act as a torrent client too
[15:29] <canthus13> nice.
[16:31] <thafreak> finally ordered my pelican case, and some protective hard drive cases
[16:31] <paultag> dude
[16:31] <paultag> that's awesome
[16:31] <paultag> canthus13: the game
[16:31] <thafreak> opted to go with bare hard drives plugged into an external sata->usb thing
[16:31] <paultag> thafreak: I want one to build a portable debian hackstation
[16:32] <thafreak> ha
[16:32] <paultag> raspi + externals + wifi router
[16:32] <thafreak> i got it for backups
[16:32] <paultag> host a full mirror on there
[16:32] <paultag> buildd nodes, small cluser perhaps
[16:32] <thafreak> pelican cases aren't too pricey
[16:32] <paultag> interesting.
[16:32] <thafreak> i got a decent size one for $40
[16:32] <paultag> hackable?
[16:33] <thafreak> dunno...airtight, watertight
[16:33] <thafreak> un-crushable
[16:33] <thafreak> the one I got is full of foam cubes that you can arrange to fit whatever
[16:34] <thafreak> i'm hoping to fit hard almost 6 bare hard drives...
[16:34] <paultag> I would love to make one a hack-in-a-box
[16:34] <thafreak> I wonder what the failure rate of bare hard drives is compared to tapes
[16:35] <thafreak> paultag: don't see why you couldn't...if you have sufficient power
[16:35] <paultag> are there "glands" I can put wires through and keep it watertight?
[16:36] <thafreak> probably could rig a li-ion laptop battery up to power everything for a while
[16:36] <thafreak> nah
[16:36] <thafreak> it's all solid
[16:36] <thafreak> why would you put wires through?
[16:36] <paultag> power strip
[16:36] <thafreak> put a decen battery inside, and you're self contained
[16:36] <paultag> mmm
[16:36] <thafreak> rasppi's are only 5w
[16:36] <paultag> true
[16:37] <thafreak> could power a bunch for hours off of an old laptop battery
[16:37] <thafreak> rig multiple batteries for extra win
[16:38] <thafreak> or i'm sure there are specialty battery stores
[16:38] <thafreak> actually, I know there are
[16:38] <paultag> not a bad idea
[16:38] <thafreak> OR, even just build a battery pack out of lantern batteries
[16:39] <thafreak> those are 6v...but I'm sure there are some instructables
[16:39] <paultag> yah, but that gets pricy
[16:39] <thafreak> lantern batteries are maybe $9
[16:40] <thafreak> unless you mean the capacitors and resistors, etc you'd need to step the voltage down
[16:40] <paultag> also a wireless AP
[16:45] <thafreak> boom
[16:45] <thafreak> http://www.adafruit.com/blog/2012/08/17/new-product-usb-battery-pack-for-raspberry-pi-3300mah-5v-1a-and-500ma-piday-raspberrypi-raspberry_pi/
[16:45] <paultag> … swag
[16:45] <thafreak> they powered a headless pi, with a wifi dongle for like 6 hours with that
[16:45] <thafreak> it's $60 though
[16:49] <thafreak> actually, it seems any of the portable phone re-charging things would work too
[16:49] <thafreak> http://www.amazon.com/PowerGen-External-Blackberry-Sensation-Thunderbolt/dp/B005VBNYDS/
[16:52] <thafreak> http://www.rpiforum.net/forum/tutorials/article/17-how-to-portably-power-your-raspberry-pi-with-a-battery/
[16:53] <thafreak> there...get busy wiring paultag
[16:53] <paultag> :)
[16:53] <paultag> thafreak: I need to find a way to do some crazy stuff first.
[16:53] <paultag> e.g. set up a new A record for ftp.us.d.o and make that force use of the raspi mirror when behind the LAN (or use mirror://)
[16:54] <paultag> and find a way to give it internet along with the hackinabox
[16:54] <paultag> (which involves not doing DHCP when DHCP is running upstream)


[00:03] -kubuntu-ci:#kubuntu-devel- Project merger_kolf build #166: FAILURE in 59 sec: http://kci.pangea.pub/job/merger_kolf/166/
[00:06] <clivejo> wxl: in the script gbp-ppa, it now seems to check the git branch you are in
[00:06] <clivejo> however, there are occasions I want to run it in kubuntu_unstable and it wont let me
[00:06] <clivejo> would you take a look?
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #760: UNSTABLE in 7 min 34 sec: http://kci.pangea.pub/job/mgmt_merger/760/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #744: UNSTABLE in 7 min 35 sec: http://kci.pangea.pub/job/mgmt_progenitor/744/
[00:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #11: STILL FAILING in 8 min 37 sec: http://kci.pangea.pub/job/yakkety_unstable_kreport/11/
[00:18] <acheronuk> clivejo: think this is the commit? https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=35eb222d6b607f15d0f127e989eddb3bb7a4ce6c
[00:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kapptemplate build #265: FAILURE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kapptemplate/265/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_polkit-kde-agent-1 build #332: FAILURE in 22 min: http://kci.pangea.pub/job/xenial_unstable_polkit-kde-agent-1/332/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdf build #111: FAILURE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kdf/111/
[00:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_prison build #28: FAILURE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_prison/28/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-thumbnailers build #57: FAILURE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-thumbnailers/57/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktimer build #221: FAILURE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktimer/221/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjsembed build #52: FAILURE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kjsembed/52/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwrited build #316: FAILURE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kwrited/316/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kontactinterface build #264: FAILURE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kontactinterface/264/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kanagram build #273: FAILURE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kanagram/273/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #12: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/12/
[00:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #8: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kdb/8/
[00:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #14: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/14/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #14: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdb/14/
[00:44] <wxl> clivejo: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/git-buildpackage-ppa#n118 :/
[00:46] <clivejo> is there an option I could pass to ignore that?
[00:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-php build #41: FAILURE in 8 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kdev-php/41/
[00:46] <wxl> judging by the note alone, i'm guessing not
[00:46] <wxl> let me try to understand exactly what's going on here
[00:47] <wxl> ahh
[00:47] <wxl> yes you can
[00:48] <wxl> set kubuntu-check-valid-branch off https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/conf/defaultrc#n65
[00:49] <clivejo> wxl: I mean in this block - https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/git-buildpackage-ppa#n35
[00:49] <wxl> clivejo: no. no argument. you can only tweak the config file.
[00:49] <clivejo> could you add an option/argument to ignore the branch
[00:50] <clivejo> and just do what I ask it to do
[00:50] <wxl> sure
[00:50] <wxl> it'd be just a matter of adding another argument and then having that config check alternately check the arg
[00:51] <clivejo> does it affect any logic later on?
[00:51] <wxl> i can drum something up and push it to my branch
[00:51] <wxl> given that the config has an option to allow for that i doubt it
[00:52] <wxl> and if i'm reading this correct it seems that the end result here is merely putting the source package in an upload area
[00:52] <wxl> so even if it does break something (which again i seriously doubt) it should have no dramatic effect
[00:53] <clivejo> ok
[00:53] <wxl> want me to drum something up for you?
[00:53] <clivejo> please, if you can
[00:54] <clivejo> Im having to create branches locally for it to run
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #42: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/42/
[00:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #41: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/zesty_unstable_kopete/41/
[01:11] <wxl> there you go clivejo https://git.launchpad.net/~wxl/+git/kubuntu-automation/commit/?id=295a97269c97f1069476181e0c506d1735d12baf
[01:11] <wxl> bah that extra "to" will make tsimonq2 livid. we should keep it.
[01:12] <clivejo> do we need --checkbranch?
[01:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #23: FIXED in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/23/
[01:12] <clivejo> that should be default behaviour, unless someone decides to override
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #189: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/189/
[01:13] <wxl> this follows the behavior of the lintian switch
[01:13] <wxl> which, if nothing's done, will get the default config
[01:14] <clivejo> oh
[01:14] <wxl> run-lintian is set to on as default
[01:14] <wxl> just as kubuntu-check-valid-branch is set to on
[01:14] <clivejo> I'm no good with python programming
[01:14] <clivejo> so don't even try!
[01:14] <wxl> well even if you were you'd have to figure out what he's doing :)
[01:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #176: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/176/
[01:15] <wxl> to answer you more clearly:
[01:15] <clivejo> my memory is rubbish
[01:15] <wxl> if you do nothing, it will automatically check the branch
[01:15] <clivejo> which makes reading and understanding code very difficult
[01:16] <wxl> if you change your conf file so that it doesn't, then it will automatically NOT check the branch
[01:16] <wxl> regardless of what you do in your conf file, explicitly using --nocheckbranch or --checkbranch will always trump everything
[01:16] <wxl> which is how unixy stuff is supposed to work, so that's Good™ :)
[01:16] <clivejo> I see
[01:17] <clivejo> wxl: have you zesty installed?
[01:17] <wxl> um no
[01:19]  * wxl added a comment to the defaultrc
[01:20] <DarinMiller> Hey all o/
[01:20] <wxl> hey DarinMiller
[01:20] <wxl> long time no see
[01:20] <clivejo> Hi DarinMiller
[01:21] <DarinMiller> clivejo: I have zesting installed if something needs tessted.
[01:21] <DarinMiller> that would be zesty....
[01:21] <clivejo> DarinMiller: do you know of the Konversation crash bug?
[01:21] <clivejo> LP: 1635911
[01:21] <DarinMiller> yes
[01:21] <clivejo> could you check it is still crashing
[01:22] <DarinMiller> rebooting to check brb....
[01:22] <clivejo> then install version 1.6.2 from my PPA here - https://launchpad.net/~clivejo/+archive/ubuntu/zesty/
[01:22] <clivejo> oh hes gone
[01:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kfind build #9: FIXED in 28 min: http://kci.pangea.pub/job/xenial_unstable_kfind/9/
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #140: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kopete/140/
[01:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #142: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/142/
[01:26] <DarinMiller> clivejo: do I need to enable staging applications or any other ppa?
[01:26] <clivejo> then install version 1.6.2 from my PPA here - https://launchpad.net/~clivejo/+archive/ubuntu/zesty/
[01:27] <clivejo> sudo add-apt-repository ppa:clivejo/zesty
[01:27] <clivejo> sudo apt-get update
[01:27] <clivejo> sudo apt-get install konversation
[01:28] <DarinMiller> brb...
[01:30] <DarinMiller> Fixed and now i am able to add other channels.
[01:31] <clivejo> no crashing?
[01:31] <DarinMiller> nope
[01:31] <DarinMiller> working perfectly
[01:31] <wxl> now go fix ubiquity, clivejo
[01:31] <wxl> XD
[01:32] <DarinMiller> Used to have to select the server to avoid the crash.  Now selecting the top level and clicking edit no longer crashes either.
[01:34] <clivejo> DarinMiller: great, thanks for double checking that
[01:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #237: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/237/
[01:37] <DarinMiller> np
[01:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #38: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/38/
[01:40] <clivejo> wxl: :P
[01:40] <clivejo> SRU konversation
[01:40] <clivejo> https://wiki.ubuntu.com/StableReleaseUpdates
[01:41] <wxl> yes dear
[01:41] <clivejo> good boy!
[01:42] <clivejo> not sure if you can convert the current bug to an SRU or need to open a new one
[01:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #21: STILL UNSTABLE in 1 hr 37 min: http://kci.pangea.pub/job/xenial_unstable_krita/21/
[01:46] <wxl> hm
[01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #43: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/43/
[01:46] <wxl> does this count as a "new upstream microrelease?"
[01:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kiriki build #44: FAILURE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kiriki/44/
[01:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_user-manager build #50: FAILURE in 20 min: http://kci.pangea.pub/job/zesty_unstable_user-manager/50/
[01:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #322: FAILURE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kstars/322/
[01:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-filetransfer-handler build #42: FAILURE in 21 min: http://kci.pangea.pub/job/zesty_unstable_ktp-filetransfer-handler/42/
[01:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kaccessible build #145: FAILURE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kaccessible/145/
 Konversation 1.6.2 is a hotfix release that fixes an unfortunate severe crash condition that crept into 1.6.1."
 bug fix release
[01:50] <wxl> k
[01:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-gdrive build #16: FAILURE in 4 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_kio-gdrive/16/
 https://launchpad.net/ubuntu/+source/konversation/1.6.2-0ubuntu1
[01:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #12: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/12/
[01:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-php build #42: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kdev-php/42/
[01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #14: FAILURE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kreport/14/
[01:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #34: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_peruse/34/
[01:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #163: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/163/
[01:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #33: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/33/
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #12: FAILURE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kreport/12/
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-php build #42: FAILURE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kdev-php/42/
[02:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #15: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_peruse/15/
[02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kapptemplate build #266: FIXED in 29 min: http://kci.pangea.pub/job/xenial_unstable_kapptemplate/266/
[02:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #46: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/zesty_unstable_cantor/46/
[02:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwrited build #317: FIXED in 29 min: http://kci.pangea.pub/job/xenial_unstable_kwrited/317/
[02:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_prison build #29: FIXED in 29 min: http://kci.pangea.pub/job/yakkety_unstable_prison/29/
[02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_polkit-kde-agent-1 build #333: FIXED in 29 min: http://kci.pangea.pub/job/xenial_unstable_polkit-kde-agent-1/333/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjsembed build #53: FIXED in 29 min: http://kci.pangea.pub/job/zesty_unstable_kjsembed/53/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-thumbnailers build #58: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-thumbnailers/58/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kontactinterface build #265: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_kontactinterface/265/
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #248: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_cantor/248/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdf build #112: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdf/112/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktimer build #222: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_ktimer/222/
[02:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #38: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/38/
[02:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #222: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/222/
[02:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #51: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/51/
[02:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kanagram build #274: FIXED in 32 min: http://kci.pangea.pub/job/xenial_unstable_kanagram/274/
[02:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #15: STILL FAILING in 8 min 31 sec: http://kci.pangea.pub/job/xenial_unstable_kreport/15/
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #13: STILL FAILING in 8 min 35 sec: http://kci.pangea.pub/job/zesty_unstable_kreport/13/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konversation build #16: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_konversation/16/
[02:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #57: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/57/
[02:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #50: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/zesty_unstable_kstars/50/
[02:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #29: FIXED in 31 min: http://kci.pangea.pub/job/zesty_unstable_kfind/29/
[02:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #74: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_marble/74/
[02:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #189: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/189/
[02:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-php build #43: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdev-php/43/
[02:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konversation build #16: FAILURE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_konversation/16/
[02:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konversation build #16: FAILURE in 15 min: http://kci.pangea.pub/job/zesty_unstable_konversation/16/
[02:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-php build #41: FAILURE in 6 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-php/41/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #204: STILL FAILING in 5 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/204/
[02:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kaccessible build #146: FIXED in 24 min: http://kci.pangea.pub/job/xenial_unstable_kaccessible/146/
[02:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konversation build #17: STILL FAILING in 5 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_konversation/17/
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #42: STILL UNSTABLE in 2 hr 23 min: http://kci.pangea.pub/job/zesty_unstable_krita/42/
[02:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_user-manager build #51: FIXED in 25 min: http://kci.pangea.pub/job/zesty_unstable_user-manager/51/
[02:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-gdrive build #17: FIXED in 24 min: http://kci.pangea.pub/job/zesty_unstable_kio-gdrive/17/
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #30: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_peruse/30/
[02:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #116: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/116/
[02:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-filetransfer-handler build #43: FIXED in 25 min: http://kci.pangea.pub/job/zesty_unstable_ktp-filetransfer-handler/43/
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #58: STILL UNSTABLE in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_marble/58/
[02:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konversation build #17: STILL FAILING in 9 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_konversation/17/
[02:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kiriki build #45: FIXED in 25 min: http://kci.pangea.pub/job/zesty_unstable_kiriki/45/
[02:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-php build #42: STILL FAILING in 4 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-php/42/
[02:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #205: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/205/
[02:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konversation build #17: STILL FAILING in 8 min 51 sec: http://kci.pangea.pub/job/zesty_unstable_konversation/17/
[02:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #42: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/42/
[02:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #250: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/250/
[02:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #323: NOW UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kstars/323/
[02:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #19: STILL UNSTABLE in 2 hr 26 min: http://kci.pangea.pub/job/yakkety_unstable_krita/19/
[02:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #237: STILL FAILING in 50 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/237/
[02:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #283: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/283/
[03:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #351: STILL FAILING in 3 min 36 sec: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/351/
[03:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #352: STILL FAILING in 4 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/352/
[03:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #238: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/238/
 @wxl, I WILL BURN YOU WITH FIRE. :)
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #150: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/150/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #65: FAILURE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/65/
 Should I use the commit message "SOMEBODY didn't pass 4th grade literacy" or "SOMEBODY doesn't know how to check for typos"? :)
[03:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #62: FAILURE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/62/
[04:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #66: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/66/
[04:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #42: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/42/
[04:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #63: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/63/
[04:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #99: STILL FAILING in 27 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/99/
[04:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #94: STILL FAILING in 43 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/94/
[04:40] <lmnet> acheronuk: unfortunately, I can't downgrade from backports-landing. I need plasma 5.8 because I have some problems with multimonitor configuration with plasma <5.8.
 It's already landed into Backports
 So you'll be fine. :)
[04:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #100: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/100/
[05:02] <valorie> clivejo: sorry, was out for awhile
[05:03] <valorie> now installed: 1.6.2-0ubuntu1 -- all good! thank you for fixing
[05:04] <valorie> should I also test kdeconnect from your PPA?
[05:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #95: STILL FAILING in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/95/
[05:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #57: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/57/
[05:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #70: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/70/
[05:50] <[Relic]> yay! turning off the allow programs to override compositing fixed that annoyance
[06:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #71: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/71/
[06:28] <wxl> aw shoot
[06:28] <wxl> what's the stupid password for the notes?
[06:33] <wxl> ah kde identiy
[06:33] <wxl> sheesh
[06:33] <wxl> thank god for grep
[06:41] <valorie> we need to move those notes
[06:41] <wxl> that'd be good
[06:41] <valorie> notes.kde.org is moving
[06:41] <valorie> I mean dying
[06:41] <wxl> oh noes
[06:41] <valorie> we have phab now
[06:42] <valorie> which actually I need to write an email about
[06:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #100: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/100/
[06:47] <wxl> man i love stockhausen
[06:50] <valorie> the music?
[06:51] <wxl> yep
[06:51] <valorie> you never fail to surprise me
[06:51] <wxl> hehehe
[06:52] <wxl> don't be too surprised. stockhausen was a major influence of aphex twin who i was listening to earlier.
[06:52] <wxl> i have a grand love for the avant-garde of all forms
[06:54] <wxl> i had a radio show on the local college station. citing the local newspaper with a nod to the sex pistols, i called it "nevermind the register guard, here's the avant-garde"
[07:05] <valorie> lol
[07:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #101: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/101/
[08:34] <acheronuk> lmnet: I said downgrade the qt packages, not the whole ppas.
[08:34] <acheronuk> i.e. to these packages https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-011-deletedppa/+build/10491543
[08:35] <acheronuk> whatever ones of those you have installed
[08:35] <wxl> arrrrrrrrrrrrrrrrrgh
[08:35] <wxl> Rejected:
[08:35] <wxl> Unable to find distroseries: yakkety-amd64
[08:35] <acheronuk> wxl??
[08:35] <wxl> whaaaat?
[08:36] <wxl> oh
[08:36] <wxl> wait, i think i see why
[08:36] <wxl> weiiird
[08:37] <acheronuk> lmnet: if you have trouble downgrading, try to catch me late afternoon or evening time on there (UK time) and I'll help you do it
[08:37] <acheronuk> *on here
[08:38] <acheronuk> wxl: sbuild target and distro series mixed up?
[08:38] <wxl> yeah
[08:40] <wxl> thank god for -j4 tho
[08:42] <wxl> i guess instead of using -d i should use -c
[08:53] <wxl> for building to stick into a ppa with sbuild, is it ok to specify --source or does one need to debuild -S first?
[08:54] <wxl> looks like --source is it
[09:05] <wxl> tee hee
[09:07] <wxl> adding all arguments except the nth one(s) to the end of a bash script → first convert to array (args=("$@")) and then just throw in ${args[@]:n} at the end
[09:34] <wxl> ok i think (think) i finally managed to get something uploaded to my ppa if anyone wants to try testing the potential sru candidate of konversation in yakkety
[09:34] <wxl> i warn you i went totally on my own on this one
[09:34] <wxl> so might want to put it in a vm
[09:34] <wxl> i'm way past bed time so night night
[09:34] <wxl> https://launchpad.net/~wxl/+archive/ubuntu/kubuntu
[12:11] <BluesKaj> Hi folks
[13:34] <clivejo> yofel: can this LP 1635911 be converted into a SRU, or do we have to create a brand new one just for the SRU to yakkety?
[13:43] <yofel> clivejo: that already has a sru task?
[13:44] <clivejo> does it?
[13:47] <clivejo> it falls under section 2.3 New upstream microreleases ?
[13:55] <yofel> clivejo: yes, but konversation will probably need a review it if has no auto-tests and there's more than one crash fix
[13:57] <clivejo> also, there are two plugin's for kdevelop, were the source has been renamed, how do I get those added to our package list so kubuntu-devel can upload?
[13:57] <clivejo> !info kdev-python yakkety
[13:58] <clivejo> upstream are calling it kdevelop-python now
[13:58] <clivejo> same with -php
[13:58] <yofel> you have someone with >= MOTU upload it, wait for it to pass source and binary NEW, then add it to the seed and refresh the packageset
[13:58] <clivejo> so stuck waiting for release team to approve it?
[13:58] <clivejo> another krita
[14:00] <clivejo> ah *beep* that for a game of billiards
[14:00] <yofel> well, krita got accepted into debian experimental, so that might help
[14:01] <clivejo> has it always been like this?
[14:04] <yofel> well, it has been like this the last couple months. Before that we had 3 core devs, +2 motus, and from the former 1 was an archive admin, and one on the release team. Back then things were easier
[14:05] <clivejo> :(
[14:06] <clivejo> is there an alternative path?
[14:08] <clivejo> maybe provide an addons PPA?
[14:09] <clivejo> or extras or whatever the bike shedding team decide to call it!
[14:09] <clivejo> PPA extreme
[14:11] <yofel> the moment we add a PPA by default we go from 'flavor' to 'derived distribution'. We had that discussion months ago already
[14:21] <clivejo> not much flavour going on at the moment
[14:22] <yofel> hm, I love looking through old wtf articles, and considering that I had to reverse-engineer the CI, I now want to call it Codethulhu http://thedailywtf.com/articles/The_Call_of_Codethulhu
[14:22] <yofel> how about  a job description of the "regular jenkins maintenance, paid in rubies" sort?
[14:25] <clivejo> LOL
[14:32] <clivejo> see they use Java too
[14:32] <clivejo> it should all be re-written in Java
[14:34] <clivejo> KCI.addProject("krita")
[14:34] <clivejo> and it would do everything for us
[14:34] <yofel> hm, that should already be a thing, just a tad less readable
[15:54] <wxl> clivejo: not sure you read the scrollback but https://launchpad.net/~wxl/+archive/ubuntu/kubuntu
[15:55] <wxl> clivejo: i couldn't get sbuild to drum up something reasonable so i ended up using pdebuild and that seemed to do the trick.
[15:57] <wxl> tsimonq2: your homework— figure out how to use sbuild to build source packages (not binaries) for upload to a ppa. when i used --source it build BOTH, which lp won't accept.
[16:06] <wxl> someone please change topic to read "Zesty Zapus Alpha 2 testing starts 24 Jan"
[16:07] <wxl> i've emailed release team to say we're not doing it
[16:07] <wxl> frankly, i don't think anyone's going to and that includes lubuntu
 @wxl, RTFM https://wiki.debian.org/sbuild#source_only_upload
 Why not Lubuntu?
[16:08] <wxl> well
[16:08] <wxl> (A) no one else is doing it
[16:08] <wxl> (B) the timing is terrible for me (and others)
 Yeah, not good timing...
 wxl: Fine manual, ain't it? :)
[16:09] <wxl> the problem is with early milestones SOMEONE needs to head up the whole thing
[16:09] <wxl> i can't
[16:09] <wxl> and xubuntu is out
[16:10] <wxl> that leaves mate. and timing's bad for flexiondotorg
[16:10] <wxl> so i left a message to ubuntu-release to see if someone wants to pick up the torch
[16:10] <wxl> budgie? XD
[16:11] <wxl> tsimonq2: tl;dr you CAN'T do it with sbuild.
 I totally think we can make it work if we push it back a week
[16:11]  * wxl shrugs
 Right?
[16:11] <wxl> not worth it for alpha 1
 wxl: Sí
[16:13] <wxl> tsimonq2: problem using dpkg-buildpackage is that (unless i'm wrong) requires you to be on the distribution you're building for. that's why i went with pdebuild
 So I'm gonna torture myself and use Dvorak
[16:13] <wxl> you're off school right?
[16:13] <blaze> kgpg kf5 depends on akonadi libs :\
 (Photo, 720x1280) https://irc-attachments.kde.org/0ptMpfSJ/file_1506.jpg
[16:14] <wxl> ew
[16:14] <blaze> which means no kgpg 'til apps 16.12
 wxl: debuild -s
 Wrong
[16:15] <wxl> tsimonq2: yes debuild -S but that's not in a chroot, so same problem again
 wxl: nope, bored in class
[16:15] <wxl>  oh wow
[16:15] <wxl> bummer
 Why is that a problem?
[16:16] <wxl> well when you get a chance later check out ppa:wxl/kubuntu, specifically the konversation for yakkety. test it out for me?
[16:18] <wxl> thx clivejo
[16:18] <wxl> off to work
 I have work, wxl
 Who uses Dvorak?
[16:24] <blaze> clivejo: remove landing
[16:28] <DarinMiller> wxl: your PPA w/ Konversation update worked great.
 I swear, you better not say ZZ!
[16:29] <davmor2> :wq
[16:29] <clivejo> ZZ
 Aaaaaaaaah
 use apt-get to install QT on ZZ
[16:30] <clivejo> LOL
[16:30] <clivejo> you'll cause him damage!
 too late
 OMG you're killing me!
[16:31] <clivejo> I just imagine him sitting with an eye twitching
 Dvorak is hard...
 Of course! Torture!
 (Photo, 720x1280) https://irc-attachments.kde.org/ShY0ov4i/file_1506.jpg
[16:32] <clivejo> @acheronuk: are you shopping?
[16:32] <blaze> who said ZZ? http://i.imgur.com/eALZvxT.jpg
 Lol
 @clivejo, No, but I have people here ATM
 Screw it, I'll switch to Dvorak later... :P
 (Photo, 720x1280) https://irc-attachments.kde.org/mUKhFUUU/file_1508.jpg
[16:54] <clivejo> what is Boost Mobile?
[16:58] <marco-parillo> clivejo: Probably off-topic, which I try to avoid at work, but Boost Mobile is an MVNO. Generally the "real" wireless operators in the USA try to lock in customers with long-term contracts. The "virtual" ones are more flexible (and IMHO) less expensive also.
[16:58] <clivejo> oh right
[17:01] <clivejo> DarinMiller: did you ever get that KDE bouncer?
[17:03] <DarinMiller> hey clivejo,
[17:03] <DarinMiller> Yes  they approved my applicaiton but I did not know what to do once approved.
[17:04] <clivejo> go to https://bnc.kde.org:7778/
[17:04] <clivejo> use your KDE username and password to log in
[17:06] <DarinMiller> OK, logged in and reviewing the email options now...
[17:06] <clivejo> click on Your Settings on the menu right hand side
[17:09] <DarinMiller> What option do you recommend I enable?
[17:09] <clivejo> Fill out your IRC Information
[17:10] <clivejo> then  under networks click add new
[17:11] <DarinMiller> umm, I think I am viewing a different settings page: https://phabricator.kde.org/settings/user/darinmiller/
[17:11] <clivejo> thats your KDE account
[17:12] <clivejo> go to https://bnc.kde.org
[17:12] <DarinMiller> sry, I missed your previous post... makes much more sense now...
[17:13] <clivejo> log in using your KDE username and password
[17:13] <DarinMiller> logged in and scanning the module section....
[17:13] <clivejo> at the top it should say logged in as : darinmiller
[17:14] <clivejo> so click on Your settings
[17:15] <clivejo> there should be a Networks section
[17:15] <DarinMiller> add freenode to the IRC network?
[17:15] <clivejo> yes
[17:16] <clivejo> add the channels you want to be buffered for you
[17:16] <clivejo> ie #kubuntu-devel
[17:19] <DarinMiller> enable any of the channel options?
[17:19] <clivejo> in the modules select nickserve and enter your nickserve password
[17:21] <DarinMiller> Rookie question: what is my Ident: ?
[17:22] <clivejo> usually just your nick
[17:23] <DarinMiller> My nickname is: DarinMiller, so am confused by  the Ident field.  Leave blank?
[17:23] <clivejo> just put it the same
[17:23] <DarinMiller> ok
[17:23] <DarinMiller> Add Network?
[17:24] <clivejo> yup
[17:28] <DarinMiller> OK, I think it's setup.  My IRC nick is blank in the Networks table even though it's setup in the config....
[17:28] <DarinMiller> How to test?
[17:28] <clivejo> you need to copy it in there too
[17:30] <clivejo> added the IRC server or servers you usually connect to
[17:32] <clivejo> once you have configured the network and channels and nickserve when you click on Active, it should connect to it
[17:32] <clivejo> I would change your nick here first
[17:33] <clivejo> so that it can connect using it
 workded for me https://community.kde.org/Sysadmin/BNC#Configure_Identify
 *worked
[18:10] <DarinMiller> wow, that BNC rabit hole is deep.
 *rabbit
 *runs from mob*
[18:14] <hippybear> If a package is already built for Ubuntu how do I get that into Kubuntu repos?
[18:15]  * DarinMiller brain goes to high efficiently mode when typing.  You will often notice many missing characters and words.  The letters and words were sent to the fingers, but they do not always obey...
 Ubuntu and Kubuntu share repositories with the exception of a few PPAs we have
[18:16] <hippybear> http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/pool/main/y/youtube-dlg/
[18:17] <hippybear> this one is not in the repos
[18:17] <hippybear> or at least not available to install via apt install youtube-dlg
[18:20] <DarinMiller> hippybear:  I think the package you want is: sudo apt install youtube-dl
[18:21] <hippybear> DarinMiller: I already have youtube-dl installed this is a GUI in python to control that youtube-dl
[18:21] <wxl> http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/pool/main/y/youtube-dlg/youtube-dlg_0.3.8-1~webupd8~wily0.dsc
[18:21] <hippybear> https://github.com/MrS0m30n3/youtube-dl-gui
[18:21] <acheronuk> !info youtube-dl
[18:21] <wxl> this is all python
[18:21] <wxl> not specific to kubuntu at all
[18:22] <acheronuk> oh. GUI. nm
[18:22] <hippybear> Ok, how do I create a package to be distributed in the repos
[18:22] <wxl> hippybear: usually the first step is to get it in debian
[18:22] <hippybear> if a package is already in the Ubuntu repos and not available to Kubuntu users
 Get it in Debian Sid
[18:22] <wxl> you might want to ask #ubuntu-devel
 JINX :)
[18:22] <hippybear> wth
[18:23] <hippybear> Why?
[18:23] <wxl> DarinMiller: thanks, btw, for checking that konversation in yakkety
[18:23] <wxl> hippybear: because that's how ubuntu development works
[18:23] <wxl> hippybear: it's very rare to find a package in ubuntu that's not in debian
[18:23] <hippybear> But I am on Kubuntu
[18:23] <wxl> hippybear: which is a derivative of debian
[18:23] <acheronuk> hippybear: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[18:23] <hippybear> and when you ask anything in Ubuntu it is always met with the snarky Ubuntu != Kubuntu
[18:23] <wxl> hippybear: so say you want it for ubuntu.
[18:23] <hippybear> Its already in the Ubuntu repos
[18:24] <wxl> where?
[18:24] <hippybear> so.... gonna look like a moron
[18:24] <hippybear> Ohhh thats debian
[18:24] <acheronuk> the command line program is in the ubuntu repos
[18:24] <wxl> yes, which is not the same
[18:24] <hippybear> It has been successfully packaged for ubuntu at http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/pool/main/y/youtube-dlg/
[18:24] <wxl> yes, but that's not how development in ubuntu works
[18:24] <hippybear> According to this bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753350
[18:25] <acheronuk> the GUI (which I didn't know existed) is not in the ubuntu repos
[18:25] <hippybear> Ahh so it has been packaged but not put in  the repos?
[18:25] <wxl> it's only packaged for ubuntu
[18:25] <wxl> not for debian
[18:25] <hippybear> ok, so now join Ubuntu-devel and ask how to get it in the repos?
[18:26] <wxl> you need to find someone to sponsor it into debian
[18:26] <wxl> that bug is not fixed, which is to say, it's not finished in debian
[18:26] <wxl> there are debian developers in #ubuntu-devel. they should be able to help
[18:26] <hippybear> Or go to debian and ask how to get it in sid so I can go to ubuntu-dev and ask how to get that in Ubuntu then come here and ask how to get it ready for KDE?
[18:26] <wxl> it does not need us at all
[18:26] <wxl> if it's ready for ubuntu it's ready for kubuntu/kde
[18:26] <hippybear> right on
[18:27] <hippybear> so what does Kubuntu-devel do?
[18:27] <hippybear> Just point to other rooms ?
[18:27] <wxl> work on releasing kubuntu
[18:27] <wxl> and packaging *KDE-SPECIFIC* packages
[18:27] <acheronuk> we make the kde/kubuntu packages for ubuntu
[18:27] <wxl> konversation is such an example.
[18:27] <hippybear> How can I make this gui a KDE specific package?
[18:27] <wxl> irssi is not.
[18:28] <wxl> hippybear: you can write a qt front end for it. and even then, it's not kde specific.
[18:28] <hippybear> kirssi mght be?
[18:28] <wxl> there's no irssi (irssi is command line, and thus not specific to any desktop environment or graphical libraries)
[18:28] <hippybear> How do I make it KDE specific so I dont feel rejected coming in here asking how to make it for the distro I have used for the past 10 years?
[18:28] <wxl> s/irssi/kirssi/
[18:29] <wxl> you don't
[18:29] <wxl> it's not kde specific
[18:29] <wxl> because it's not developed by kde
[18:29] <wxl> if you go to kde.org you can see all the things that are developed by the kde team
[18:29] <hippybear> How do I make an app KDE specific so I dont feel rejected coming in here asking how to make it for the distro I have used for the past 10 years?
[18:29] <hippybear> any app
[18:29] <hippybear> like fresh repo, new code
[18:29] <wxl> there are many things that they DO NOT develop that are in kubuntu
[18:29] <wxl> hippybear: join the kde team
[18:29] <hippybear> Ok example me?
[18:29] <wxl> hippybear: bash.
[18:29] <hippybear> I would love to!
[18:30] <hippybear> bash is KDE specific?
[18:30] <wxl> no, it's not
[18:30] <wxl> but it's in your kubuntu
[18:30] <hippybear> lol
[18:30] <acheronuk> Firefox, Libreoffice
[18:30] <hippybear> so any app with K in the front such as Konversation / Kopete are KDE specific?
[18:30] <wxl> no
[18:30] <hippybear> I assume yes
[18:30] <hippybear> wth??
[18:30] <acheronuk> no
[18:30] <hippybear> :(
[18:31] <hippybear> so I can install Kopete in Ubuntu?
[18:31] <hippybear> or debian?
[18:31] <wxl> sure, as long as you install all the required libraries
[18:31] <wxl> OH!
[18:31]  * acheronuk goes to find a beer
[18:31] <wxl> kvm is not kde specific
[18:31] <hippybear> well isnt that any system?
[18:31]  * wxl wins
[18:31] <wxl> well, any linux system
[18:32] <wxl> wmmv with unix, but feel free
[18:32] <wxl> regardless of what people tell you, kubuntu *IS* ubuntu
[18:32] <hippybear> I would like to join a development team and do some stuff but I feel like im getting the run around
[18:32] <wxl> it's just ubuntu with some packages missing and some other packages added
[18:32] <hippybear> so I will just idle and pretend to be cool
[18:32] <wxl> suit yourself
[18:35] <wxl> https://www.youtube.com/watch?v=8vgDpI8kU98
[18:36] <hippybear> I think Ubuntu-devel is shunning me
[18:37] <hippybear> jk
[18:37] <hippybear> still too early maybe
[18:37] <wxl> patience is a virtue. watch that video while you wait.
[18:37] <hippybear> already listening to this https://www.youtube.com/watch?v=vE76N4JqM-Y
[18:38] <wxl> yeah mine's got more to keep your attention visually :)
[18:38] <hippybear> lol
[18:38]  * hippybear is a blind guy
[18:38] <wxl> rilly?
[18:39] <hippybear> so this will get me setup to develop in KDE? http://packaging.ubuntu.com/html/index.html
[18:39] <wxl> look, if you want to help with kubuntu, the first step is packaging for sure. so yeah, that'll be a good start :)
[18:39] <hippybear> not totally, but I am considered blind by all medical arenas
[18:39] <hippybear> alright
[18:39] <wxl> hippybear: do you need to use any accessibility features because of that?
[18:39] <hippybear> I want to learn the process
[18:40] <hippybear> be able to contribute to apps I already love and use
[18:40] <hippybear> a ton
[18:40] <wxl> i'd follow the packaging guide and get hello in a ppa. once you've done that you'll ahve enough familiarity with the tools that we can move you forward from there
[18:40] <wxl> and you can ALWAYS help with testing
[18:40] <hippybear> all kinds of system tweaks, cool monitors, fancy magnifier lens going all the time\it looks goofy but meh
[18:41] <wxl> neat!
[18:41] <wxl> there's an accessibility team in ubuntu
[18:41] <hippybear> i want to take on zim also
[18:41] <hippybear> its kinda abandoned
[18:41] <wxl> not sure if you need help but if you use that stuff it makes a BIG difference!!!!
[18:41] <wxl> had someone come into #lubuntu the other day looking for help with voice recognition and i was just clueless. i'd feel the same way with your needs.
[18:42] <wxl> anywho re: testing i just threw together a fix for konversation in yakkety if you want to test it out.
[18:42] <hippybear> Yeah its hard to get setup initially but after using buntu for +15 yrs I pretty much know what to change and where
[18:42] <hippybear> sheeet link me bro
[18:43] <wxl> https://launchpad.net/~wxl/+archive/ubuntu/kubuntu
[18:43] <hippybear> I did have Konversation crash twice yesterday and it wouldnt stop spamming me to send a report and leave closed or relaunch
[18:43] <wxl> ^^ that should fix it!
[18:43] <hippybear> sweet!
[18:43] <wxl> it's a fix for https://launchpad.net/bugs/1635911
[18:44] <wxl> hippybear: i will say if you're interested in development, getting started with the things you use regularly is the BEST way to do things
[18:45] <hippybear> for sure
[18:45] <hippybear> ok now to test this fix
[18:48] <hippybear> E: Failed to fetch http://ppa.launchpad.net/wxl/kubuntu/ubuntu/dists/xenial/main/binary-amd64/Packages  404  Not Found
[18:49] <wxl> hippybear: oh yeah. don't have it in xenial :(
[18:49] <hippybear> Oh carp
[18:49] <wxl> only yakkety
[18:49] <wxl> you can drum a vm if you want to test it out tho
[18:49] <hippybear> didnt even notice the version lol
[18:49] <wxl> ^^ look at the bug note from ubottu
[18:49] <hippybear> ok so.... how do you update it to xenial? Whats that process?
[18:50] <hippybear> ubottu?
[18:51] <hippybear> I can make it ready for xenial?
[18:51] <hippybear> and thereby earn the process?
[18:51] <hippybear> learn
[19:18] <clivejo> is the konverstaion bug in xenial too?
[19:21] <clivejo> DarinMiller: did you get your bouncer setup?
[19:34] <DarinMiller> clivejo: I installed irssi, configured the server and chatnet
[19:34] <clivejo> are you connected via the bouncer now?
[19:35] <DarinMiller> irssi succesfully connects to  bnc.kde.org, but same credentials and setup in konversation do not seem to work.
[19:35] <clivejo> should work :/
[19:36] <clivejo> are you using the correct username and password?
[19:36] <DarinMiller> konversation welcome met to ZNC but then says: [12:35] <*status> Your message to [nickserv] got lost, you are not connected to IRC!
[19:37] <clivejo> did you see the instructions Rik posted, https://community.kde.org/Sysadmin/BNC#Configure_Identify
[19:37] <DarinMiller> followed by [12:36] <*status> Disconnected from IRC (Can't resolve server hostname). Reconnecting...
[19:37] <DarinMiller> yes.  that's when I installed irssi and tested that connection.  No errors with irssi.
[19:38] <clivejo> did you reuse any old settings in konversation
[19:40] <DarinMiller> I setup, deleted and resetup the Konv. server 3 times as per the webpage referenced by Rik.
[19:40] <DarinMiller> but obviously something is amiss...
[19:44] <clivejo> did you use the nickserv module in the BNC settings?
[19:47] <DarinMiller> Under default idently, -I tried both nickserv and server settings.  Do I need to clear out all of my default nicks?
[19:48] <DarinMiller> No channels are set as specified by the instructions.
[19:52] <clivejo> you can add the channels later once logged on
[19:53] <clivejo> just join them as usual and they get added
[19:56] <clivejo> you have no cloak now
[19:58] <DarinMiller> hmmm... let me kill the BNC server and see if that allows the cloal.
[19:58] <DarinMiller> BNC server says: [12:56] [Welcome] - Welcome to ZNC
[19:59] <DarinMiller> so I assume it likes my credentials.
[19:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #16: STILL FAILING in 6 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_kreport/16/
[19:59] <DarinMiller> but then I get a *status channel that repeatably says: [12:57] <*status> Disconnected from IRC (Can't resolve server hostname). Reconnecting...
[20:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #13: STILL FAILING in 7 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_kreport/13/
[20:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #14: STILL FAILING in 9 min 12 sec: http://kci.pangea.pub/job/zesty_unstable_kreport/14/
[20:02] <DarinMiller> looks like my cloak is dead.  Not sure how I killed it.
[20:03] <DarinMiller> also i don;t understand this section: https://community.kde.org/Sysadmin/BNC#Configure_Identify
[20:03] <DarinMiller> Configure Identity^
[20:04] <BluesKaj> +da perhaps since your're using a bouncer the setting there overides nickserv registry
[20:04] <BluesKaj> DarinMiller,^
[20:05] <wxl> who else wnats to test konversation in yakkety/
[20:05] <acheronuk> a cloaked login via the BNC with SASL works here. check the config again?
[20:05] <DarinMiller> BluesKaj: probably.  but I killed the bouncer server from Konversation (for the umpteeth time today) so it should not have any affect at the moment.
[20:05] <BluesKaj> just a guess, i haven't used znc for a while
[20:05]  * acheronuk uses hexchat :/
[20:05] <DarinMiller> acheronuk: what is SASL, that's the part I don't understand
[20:06] <BluesKaj> acheronuk, I'm using Konversation on Yakkety as we speak
[20:06] <wxl> BluesKaj: you mean me :)
[20:06]  * DarinMiller thinking of going back to stone tablet and chisel.  Not as komplicated....
[20:06] <wxl> BluesKaj: you have the crashy problem?
[20:06] <BluesKaj> SASL requires a user acct/username and password
[20:06] <wxl> and a certificate, no?
[20:07] <acheronuk> wxl: if it does, the BNC handles that
[20:07] <BluesKaj> wxl, yeah sometimes when I quit
[20:07] <wxl> BluesKaj: see if this fixes https://launchpad.net/~wxl/+archive/ubuntu/kubuntu/+packages
[20:08] <wxl> as upstream describes it, it should "Fixed a bug causing various operations on server list data to crash, e.g. pressing "Edit" on a server sub-item in the Server List dialog.
[20:09] <wxl> valorie: since you're the OP on the bug that fixes, you might want to check too
[20:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #14: STILL FAILING in 6 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_kreport/14/
[20:11] <valorie> wxl: I will comment once I test a bit more
[20:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #137: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/137/
[20:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #80: NOW UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/80/
[20:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #17: STILL FAILING in 8 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_kreport/17/
[20:12]  * DarinMiller 2 pass email account, ssh keys, gpg keys, kde account, lp account, irc account, bouncer account, sasl account (did I miss any????).  wtf??? why so fricken complicated.... just to fix packages
[20:13] <clivejo> LOL
[20:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #15: STILL FAILING in 6 min 36 sec: http://kci.pangea.pub/job/zesty_unstable_kreport/15/
[20:14] <BluesKaj> wxl, my vesion is fine now , it didn't crash when it quit so I'm leaving it as is.
[20:14] <BluesKaj> version
[20:16] <wxl> BluesKaj: fwiw i'm looking for testers to verify this will for an SRU. you can pop it into a vm if you like.
[20:17] <BluesKaj> wxl, sorry i don't do vms ..never had much luck with them
[20:18] <BluesKaj> I'm dual booting yakkety and zesty atm
[20:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #41: NOW UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/41/
[20:21] <DarinMiller> as per my irssi command line connection, my account connects without issue so I think my credentials are fine but I am totally stumped as to why I kannot konfigure konversation.  The website directions are simple.
[20:33] <BluesKaj> DarinMiller, check this out https://userbase.kde.org/Konversation/Configuring_SASL_authentication
[20:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #16: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kreport/16/
[20:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #18: NOW UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kreport/18/
[20:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #15: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/15/
[21:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #16: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/16/
[21:03] <pedahzur> Trying to install kdesudo from Kubuntu Backports on 16.04.  It says it can't install kde-runtime.  When I try to install kde-runtime, I get this: https://gist.github.com/jkugler/33fa356d0e4d57f23b470163783bd96f I've noticed this with other packages I've tried to install as well, such as konqueror. Is kdesudo no longer in KDE? What does one use instead?
[21:09] <valorie> how about kdesu ?
[21:13] <BluesKaj> pedahzur, what method are you using to install ?
[21:14] <pedahzur> BluesKaj: apt-get install
[21:14] <BluesKaj> rgen use sudo
[21:14] <BluesKaj> then
[21:15] <BluesKaj> kdesudo is on;u used to call up gui files in the cli
[21:15] <pedahzur> BluesKaj: Well, yes, 'sudo apt-get install'
[21:16] <pedahzur> Yes, and apparently, in this case (usb-creator-kde) sudo worked even in the GUI.  But it seems odd that ther are so many broken packages.  Is it because of Kubuntu Backports + native packages?
[21:17] <BluesKaj> did you update and upgrade before adding the backports ppa ?
[21:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konversation build #18: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_konversation/18/
[21:17] <pedahzur> 99% sure. It's been a while since I added the back ports.
[21:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konversation build #18: FIXED in 14 min: http://kci.pangea.pub/job/xenial_unstable_konversation/18/
[21:23] <valorie> it is fine in Zesty: kdesudo is already the newest version (<IP_ADDRESS>+repack-2ubuntu4)
[21:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konversation build #18: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_konversation/18/
[21:25] <acheronuk> no prob here with kdesudo and it deps in Xenial + backports
[21:26] <clivejo> oh dear
[21:26] <clivejo> my iCloud will be closed in 48 hours
[21:26] <clivejo> what a shame
[21:29] <acheronuk> pedahzur: ok here, so you have something peculiar blocking it http://paste.ubuntu.com/23675045/
[21:30] <pedahzur> acheronuk: Hmm...That's weird.  I wonder what I did...
[21:32] <acheronuk> clivejo: wow. that's a coincidence. had the same the other day on an iCloud account I never knew I had
[21:35] <valorie> my Mac was in the 90s
[21:35] <valorie> pretty sure I have no iCloud
[21:39]  * wxl enjoys his new standing desk at work
[21:41] <pedahzur> acheronuk: I forget how to get the breakdown that you posted in that pastebin.
[21:42] <valorie> those look like the result of apt-cache policy packagename
[21:48] <acheronuk> pedahzur: what does 'apt-get install kdelibs5-plugins' output?
[21:50] <acheronuk> ???
 apt-get
[21:51]  * acheronuk shrugs and doesn't give a ####
[21:56] <pedahzur> acheronuk: https://gist.github.com/jkugler/9bfed349deccc63b90ab23fff739e4e4
 +1 to acheronuk
[21:57] <pedahzur> acheronuk: policy output for kdelibs5-plugins https://gist.github.com/jkugler/32397f1a2db8daf6ffa092d26e143505
[21:57] <wxl> who else wants to check konversation in yakkety?
[21:57] <wxl> i mean YY
 OMG STFU
[21:58] <wxl> !language | tsimonq2
 Shut The Frank Up, Shut The Freak Up
 *shrug*
[21:59] <wxl> too ambiguous to be sure
 :[
[22:00] <wxl> ahoneybun: tsimonq2: go test konversation in yakkety from my ppa!
[22:00] <wxl> vm
 On mobile
[22:00]  * valorie has no yakkety anymore -- the zesty version from clive's ppa is working great
 Will do wxl
[22:01] <wxl> aw fooey valorie
[22:01] <valorie> and my xenial laptop is still SOL
 !language
 <ubottu> tsimonq2: Please avoid any language that may be considered offensive, including acronyms and obfuscation of such - also see https://wiki.ubuntu.com/IRC/Guidelines || The main channels are English only, for other languages, see https://wiki.ubuntu.com/IRC/ChannelList
[22:01] <valorie> like the sun!
 Bah, if I can't get away with it, you can't either :P
[22:02]  * valorie accepts the reproof
[22:05] <clivejo> !info xdgurl
[22:05] <clivejo> !info xdgurl zesty
[22:05] <clivejo> LOL
[22:07] <valorie> clivejo: maybe
[22:07] <valorie> dg-utils/zesty,zesty,now 1.1.1-1ubuntu2 all [installed]
[22:07] <valorie>   desktop integration utilities from freedesktop.org
[22:07] <valorie> pfff, bad paste
[22:07] <valorie> xdg-utils
[22:08] <acheronuk> pedahzur: that is ok, but I wanted to know what happens when you try to install kdelibs5-plugins
[22:09] <acheronuk> pedahzur: the packages it says won't be installed. what does it say if you use 'apt-get install' to try to install them?
[22:10] <pedahzur> acheronuk: For kdoctools: kdoctools : Depends: libkio5 (= 4:4.14.22-0ubuntu2~ubuntu16.04~ppa61) but it is not going to be installed
[22:11] <pedahzur> libkio5 : Depends: libstreamanalyzer0v5 (>= 0.7.8) but it is not going to be installed
 s/apt-get/apt/g
[22:11] <pedahzur> libstreamanalyzer0v5 : Depends: libclucene-core1v5 (>= <IP_ADDRESS>) but it is not going to be installed
[22:12] <pedahzur> acheronuk: And to install liblucene-core1v5, it wants to remove a whole bunch of other liblucene stuff, as well as libreoffice-* (or just about "*") :)
[22:14] <wxl> ahoneybun: did i give you a link to my ppa
[22:14] <wxl> ?
[22:15] <acheronuk> pedahzur: hard to say for sure, but with thsoe packages not wanting to be installed it sounds like you have some problem with your installed packages that is not really KDE or backports related. or if it is, via a very very obscure path
[22:19] <pedahzur> acheronuk: Hmm...I have the libreoffice PPA in my list, and it points (or pointed) to trusty.  So I seem to be running 5.2.1, but the latest in Xenial is 5.1.4.  I'll wipe LibreOffice, and install the version from Xenial (or at least from a PPA for Xenial).
[22:20] <acheronuk> pedahzur: well, having ppas from a different ubuntu release is never going to help. they may contain incompatible dependencies or even packages
[22:21] <pedahzur> acheronuk: The odd thing was that it was disabled (commented out). I wonder if I already had a later release when I did 14.04 -> 16.04, so it didn't downgrade it to the 16.04 libreoffice version, thus kept some wonky packages around.
[22:24] <acheronuk> well, the ubuntu ugrage scripts tend to just disable ppas on upgrade, but don't touch what has been installed from them
[22:24] <acheronuk> *upgrade
[22:24] <clivejo> whats going on with kdev-php and kdevelop-php?
[22:24] <acheronuk> going on?
[22:25] <clivejo> yup
 In what regard?
[22:26] <clivejo> why are they both there
[22:27] <clivejo> http://kci.pangea.pub/search/?q=-php
[22:27] <clivejo> http://kci.pangea.pub/job/merger_kdevelop-php/
[22:27] <clivejo> is disabled
[22:28] <pedahzur> acheronuk: Yeah, that makes sense. It disabled the PPA, saw that the libreoffice (installed in 14.04) was a later version than the version it had, so left that alone too...which caused a bunch of conflicts later on. :)
[22:29] <acheronuk> clivejo: they changed the git repo name, so the old job was just disable instead of removed?
[22:30] <pedahzur> acheronuk: Oh looky! kdesudo installed just fine! Thanks for the debugging. I thought this was a dev issue, but it wasn't, but you helped me anyway. I greatly appreciate it!  And I added tools to my debugging toolkit.
[22:30] <clivejo> acheronuk: no idea and too tired to look at it
[22:30] <acheronuk> clivejo: I remember you asking me to change the LP repo names, but at that point I didn't have KCI access to change jobs AFAIK, so that side was you?
[22:31] <acheronuk> clivejo: no problem
[22:31] <clivejo> https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdevelop-php https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdev-php
[22:31] <clivejo> but we have two :/
[22:31] <acheronuk> clivejo: must be thinking of something else then!
[22:32] <valorie> clivejo: one old and one new?
[22:32] <clivejo> I dunno, my head hurts
[22:32] <acheronuk> I guess it was mirrored to the new name, but again old one not removed
[22:34] <acheronuk> pedahzur: glad that is sorted :)
[23:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-php build #44: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdev-php/44/
[23:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-php build #43: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kdev-php/43/
[23:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-php build #43: FIXED in 14 min: http://kci.pangea.pub/job/xenial_unstable_kdev-php/43/
[23:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:36] -kubuntu-ci:#kubuntu-devel- Project merger_kolf build #167: FIXED in 14 sec: http://kci.pangea.pub/job/merger_kolf/167/
[23:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #27: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kexi/27/
[23:56] <wxl> clivejo: fyi in case you haven't noticed, i've only got one test so far. still working on the sru bug itself, but jesus work has been nuts
[23:56] <clivejo> no problem, my head it not working tonight anyway


[00:42] <darizzle> is steven beattie in here
[00:42] <darizzle> i was just wondering
[00:42] <darizzle> or anyone interested
[00:42] <darizzle> the testing day page is out of date
[17:02] <cr3> moustafa: hey dude, how are things?
[17:02] <moustafa> cr3: Hey!  Didn't see you come in!
[17:03] <moustafa> cr3: Doing fine so far, looking at the code, seeing what tests I can add
[17:03] <cr3> moustafa: excellent, I'll try to find time to push the log component and merge your tests from Friday
[17:03] <moustafa> Cool
[17:04] <moustafa> cr3: How's the conference so far?  Or it hasn't started yet?
[17:04] <cr3> moustafa: it's been running for three hours so far
[17:07] <moustafa> cr3: Did Mark give you some parting gifts?
[17:08] <cr3> moustafa: not yet, I've managed to avoid him successfully by wearing a ronald reagan mask
[17:09] <moustafa> cr3: I take it he fears old cowboy presidents?
[17:18] <fader_> moustafa: Who doesn't?
[17:19] <moustafa> fader_: The brits?
[17:19] <fader_> moustafa: They should ;)
[17:20] <moustafa> fader_: I dunno.  I mean, they have killer rabbits over there.  With big, sharp, pointy teeth!
[17:23] <moustafa> This should be bookmarked and used daily: http://www.instantrimshot.com/
[17:24] <fader_> moustafa: Also sadtrombone.com
[17:25] <moustafa> fader_: This deserves a "roflcopter"
[18:14] <cr3> moustafa: hey dude, your branch has been merged and I've pushed checkbox.log into the message branch.
[18:15] <cr3> moustafa: you might not be able to bzr pull, since you have an updated branch. instead, you might either have to bzr merge and commit, or branch all over again
[18:17] <moustafa> cr3: I'll take the merge and commit for 500 Alec
[18:24] <moustafa> cr3: branch merged and committed, using a full sentence too!
[18:26] <cr3> moustafa: "Merged from [branch].", where [branch] is usually "trunk" or "message" in this case is fine
[18:27] <cr3> moustafa: you should have plenty of work for the week with checkbox.message and checkbox.log
[18:27] <cr3> moustafa: there is one missing module under checkbox.log that I need to work on is an abstraction layer for reading multiple log files at once
[18:28] <cr3> moustafa: then, I will finally be able to return to working on services (previously known as plugins), such as a graph service to manage dependencies


[16:38] <peppe84> Hi doc-team
[16:41] <peppe84> Building today the serverguide I don't understand why the html file are present in root directory instead /build/serverguide/LN/. nothing serious, just move the files in the right position. I have try whit revision 81 (the last). thanks in advance.
[16:48] <Darkwing> jbicha, mdke, FYI, We are having issues with the docs on the Kubuntu side... we will have to do more with an SRU. just FYI
[17:03] <peppe84> Sorry again: I have found a dead link here: http://<IP_ADDRESS>/a11y-contrast.html is a know issue?


[15:39] <designbybeck> greetings all. has anyone used Celestia, the space program?
[15:39] <designbybeck> I'm wondering why the Moon and other textures don't show up
[15:39] <designbybeck> this has happened in all versions I've used
[16:08]  * highvoltage installs it out of curiousity after not having run it for years