[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2146: SUCCESS in 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2146/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2146: SUCCESS in 1 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2146/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2146: SUCCESS in 4 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2146/
[09:52] <BluesKaj> Hi folks
[11:17] -kubuntu-ci:#kubuntu-devel- Starting build #4 for job iso_bionic_unstable_amd64 (previous build: SUCCESS)
[11:21] -kubuntu-ci:#kubuntu-devel- Project iso_bionic_unstable_amd64 build #4: FAILURE in 3 min 31 sec: https://kci.pangea.pub/job/iso_bionic_unstable_amd64/4/
[11:33] -kubuntu-ci:#kubuntu-devel- Starting build #5 for job iso_bionic_unstable_amd64 (previous build: FAILURE -- last SUCCESS #3 2 mo 11 days ago)
[11:36] -kubuntu-ci:#kubuntu-devel- Project iso_bionic_unstable_amd64 build #5: STILL FAILING in 3 min 32 sec: https://kci.pangea.pub/job/iso_bionic_unstable_amd64/5/
[11:44] -kubuntu-ci:#kubuntu-devel- Starting build #6 for job iso_bionic_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #3 2 mo 11 days ago)
[12:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gcompris build #111: STILL FAILING in 19 min: https://kci.pangea.pub/job/bionic_unstable_gcompris/111/
[12:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:03] -kubuntu-ci:#kubuntu-devel- Project iso_bionic_unstable_amd64 build #6: FIXED in 18 min: https://kci.pangea.pub/job/iso_bionic_unstable_amd64/6/
[12:45] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-workspace build #1547: FAILURE in 6 sec: https://kci.pangea.pub/job/merger_plasma-workspace/1547/
[12:48] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-workspace build #255: STILL FAILING in 3 min 51 sec: https://kci.pangea.pub/job/artful_stable_plasma-workspace/255/
[12:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #434: STILL FAILING in 3 min 51 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/434/
[12:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #282: STILL FAILING in 3 min 51 sec: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/282/
[12:49] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-workspace build #188: STILL FAILING in 4 min 18 sec: https://kci.pangea.pub/job/xenial_stable_plasma-workspace/188/
[14:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:05] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-workspace build #1548: FIXED in 13 sec: https://kci.pangea.pub/job/merger_plasma-workspace/1548/
[14:09] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-workspace build #283: STILL FAILING in 2 min 44 sec: https://kci.pangea.pub/job/artful_unstable_plasma-workspace/283/
[14:09] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-workspace build #189: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/xenial_stable_plasma-workspace/189/
[14:09] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-workspace build #256: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_stable_plasma-workspace/256/
[14:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #435: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-workspace/435/
[14:13] <blaze> boo, kio gdrive stopped working all of a sudden
[14:13] <blaze> can anyone reproduce?
[14:15] <blaze> google apis are not reliable at all
 @blaze, gdrive:// working fine here in dolphin with 18.04....
 maybe turn it off and on again?
 Update: gdrive is acting a little quirky.  Delete action does not auto refresh the list and certain actions causes duplciate branches.
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2147: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2147/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2147: SUCCESS in 1 min 17 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2147/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2147: SUCCESS in 4 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2147/
[16:01] <santa_> good afternoon everyone
[16:02] <santa_> acheronuk: if you have a few minutes I could explain the changes I made in kmailtransport + upload it to bionic if you are ok with tthat
[16:04] <santa_> s/tthat/that/
[16:04] <acheronuk> santa_: go for it
[16:06] <santa_> ok, in the first place, let me say that I did several commits and the first ones wasn't on my most inspired day so sorry for the mess
[16:06] <santa_> so...
[16:07] -kubuntu-ci:#kubuntu-devel- Project merger_kmailtransport build #921: FAILURE in 5.8 sec: https://kci.pangea.pub/job/merger_kmailtransport/921/
[16:07] <santa_> to see the actual changes you may want to type "git diff ubuntu/17.12.3-0ubuntu3"
[16:08] <santa_> note that I have just pushed a couple of commits right now, so make sure you pull them now
[16:08] <acheronuk> doing...
[16:10] <acheronuk> ok. seems sensible
[16:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #356: STILL FAILING in 3 min 39 sec: https://kci.pangea.pub/job/xenial_unstable_kmailtransport/356/
[16:11] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kmailtransport build #175: STILL FAILING in 3 min 39 sec: https://kci.pangea.pub/job/xenial_stable_kmailtransport/175/
[16:12] <acheronuk> DarinMiller: did you try the settings package from the ppa, or just manually set the backgrounds?
[16:14] <santa_> so a couple of comments about the changes
[16:14] <acheronuk> santa_: kmailtransport has been a 'mess' for much longer than you touching it. scarlet has quite some issue with it on Neon
[16:14] <acheronuk> s/has/had
[16:14] <santa_> about the kio-smtp deletion I just blindtrusted you the other day when you say it's gone
[16:14] <santa_> in second place there's something still wrong
[16:15] <santa_> or probably wrong
[16:15] <acheronuk> I thought it had, but somehow not
[16:15] <santa_> usr/lib/*/qt5/plugins/mailtransport/mailtransport_smtpplugin.so installed by libkf5mailtransport5abi2
[16:16] <santa_> that, as far as I know is a violation of a debian must policy, but aparently scarlett had some issue providing it in its own package
[16:17] <santa_> so we could upload this improved version and discuss with her a possible new package providing mailtransport_smtpplugin.so
[16:17] <santa_> even after our lts release
[16:21] <acheronuk> santa_: scarlet seems to be doing more with debian than Neon at the moment, and as they have it in the same place, maybe she can get it changed in all places
[16:21] <santa_> that's the idea
[16:21] <acheronuk> okay. sounds a plan
[16:22] <santa_> I mean, if we are going to have a separate package, better if we have the same name everywhere
[16:23] <acheronuk> yep
[16:24] <acheronuk> tsimonq2: you about?
 @acheronuk, On phone for the next five hours but otherwise yeah
 later or tommorow then
 not urgent
 @acheronuk, What's up?
 never did get ksmtp 17.12.3 uploaded. but on 2nd thoughts, maybe should leave it until this kmailtransport upload is done. that is nore important to get in 1st
 @acheronuk, I neglected to use the PPA.  Will try ppa shortly....
[17:21] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kio-gdrive build #146: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/artful_stable_kio-gdrive/146/
 @DarinMiller new kio-gdrive 1.2.2 on the way. fixes don't really sound like those issues, but I don't use it, so can't really say 100%
[17:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio-gdrive build #152: STILL FAILING in 4 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kio-gdrive/152/
[19:10] <yofel> o/
 Yo
[19:30] -kubuntu-ci:#kubuntu-devel- Project merger_kmailtransport build #922: STILL FAILING in 5.7 sec: https://kci.pangea.pub/job/merger_kmailtransport/922/
[19:32] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kmailtransport build #110: FAILURE in 1 min 17 sec: https://kci.pangea.pub/job/bionic_stable_kmailtransport/110/
[19:34] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kmailtransport build #176: STILL FAILING in 3 min 36 sec: https://kci.pangea.pub/job/xenial_stable_kmailtransport/176/
[19:34] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmailtransport build #156: STILL FAILING in 3 min 41 sec: https://kci.pangea.pub/job/artful_stable_kmailtransport/156/
[19:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:36] -kubuntu-ci:#kubuntu-devel- Project merger_kmailtransport build #923: FIXED in 13 sec: https://kci.pangea.pub/job/merger_kmailtransport/923/
[19:37] <sick_rimmit> Hi, sorry i'm a little late
[19:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #357: STILL FAILING in 3 min 36 sec: https://kci.pangea.pub/job/xenial_unstable_kmailtransport/357/
[19:40] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kmailtransport build #177: STILL FAILING in 3 min 43 sec: https://kci.pangea.pub/job/xenial_stable_kmailtransport/177/
[19:40] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmailtransport build #157: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/artful_stable_kmailtransport/157/
[19:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmailtransport build #211: STILL FAILING in 3 min 43 sec: https://kci.pangea.pub/job/artful_unstable_kmailtransport/211/
[19:41] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kmailtransport build #111: STILL FAILING in 4 min 46 sec: https://kci.pangea.pub/job/bionic_stable_kmailtransport/111/
[19:43] <valorie> sick_rimmit: {{{{{{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}
[19:43] <valorie> so good to see you again!
[19:44] <sick_rimmit> Hi valorie
[19:44] <valorie> how are you?
[19:44] <sick_rimmit> I'm good
[19:44] <sick_rimmit> It's been a very eventful year
[19:44] <valorie> it was quite a winter
[19:44] <sick_rimmit> WoW for you guys, most certainly
[19:44] <sick_rimmit> Couldn't believe the weather you've been getting
[19:44] <valorie> yes, a lot packed in and it's just the third month
[19:45] <valorie> well, milder over on my side of the continent
[19:45] <valorie> well and truly spring here now
[19:45] <sick_rimmit> We had a couple of days of snow, one of which was a blizzard
[19:45] <sick_rimmit> most unusual
[19:46] <sick_rimmit> I've been trying to keep in the loop with the high level stuff, via Telegram
[19:46] <valorie> cool
[19:46] <sick_rimmit> and Email
[19:46] <valorie> lots to keep up on
[19:47] <valorie> beta 2 next week!
[19:47] <sick_rimmit> Some great early reviews on YouTube
[19:47] <sick_rimmit> 18.04 is looking very promising
[19:47] <valorie> yes, I've got beta 1 on my travel laptop and it's great so far
[19:48] <sick_rimmit> What's been happening in the community
[19:48] <sick_rimmit> I saw a post from a person on the web, who announced themselves as the Product Manager for Kubuntu
[19:48] <sick_rimmit> Did we find someone ?
[19:48] <sick_rimmit> I'll be so pleased
[19:48] <valorie> besides the devel going nuts and uploading spectactular packages
[19:49] <valorie> yes, Nate Graham @nggraham  is going great guns at the job
[19:49] <sick_rimmit> Oh that's excellent
[19:49] <valorie> working all over Kubuntu and KDE in QA, usability, etc.
[19:50] <valorie> I asked him -- you are already doing the job, why not take the title?
[19:50] <valorie> lol
[19:50] <valorie> so he did
[19:50] <sick_rimmit> Well done
[19:50] <sick_rimmit> :-D
[19:50] <sick_rimmit> {{{hug}}}
 Hello!
[19:50] <sick_rimmit> Hi Nate.
[19:50] <valorie> thank YOU for crystalizing our need into that proposal
 Hi, nice to meet you
[19:51] <sick_rimmit> I've been seeing some of your interactions, well done, doing an awesome job
[19:51] <valorie> hey nate, meet Rick who proposed your job title
 hehe
[19:51] <sick_rimmit> Very nice to meet you
 thank you very much, I've been having a blast
[19:52] <sick_rimmit> I'm afraid, I'm going to have to leave doing Kafe.
 the CTO of my company, who is ordinarily a Windows guy, put Kubuntu 17.10 on his machine recently and was very impressed. I was so happy
[19:53] <sick_rimmit> It's clear already that 18.04 is shaping up really strongly
[19:53] <sick_rimmit> I think it is important to sweat the small stuff, at this stage.
 yup
[19:54] <sick_rimmit> We really must try hard to stamp any niggles our
[19:54] <sick_rimmit> s/our/out/
[19:54] <sick_rimmit> We've been getting some great reviews and videos on YouTube
[19:54] <valorie> sick_rimmit: don't sweat it
[19:55] <valorie> if it can resume at some time, that would be great
[19:55] <sick_rimmit> Thanks @valorie
[19:55] <valorie> I miss having your energy in the team
[19:55] <valorie> so when you can slide back in that would be great
[19:55] <valorie> if
[19:55] <sick_rimmit> Well, I'm on my way back into the fold
[19:56] <sick_rimmit> I've still lots of family stuff todo, Brother, Sister both need my support
[19:56] <sick_rimmit> and of course my own girls
[19:56] <valorie> losing a parent is very hard
[19:57] <sick_rimmit> But, you've all been great, supportive and understanding
[19:58] <sick_rimmit> More importantly we've got an LTS to ship, and lots to do
[19:58] <sick_rimmit> So what's to do ?
[19:59]  * sick_rimmit Kicks off Firefox, for a look at Phab
[19:59] <valorie> the meeting is when?
[19:59] <valorie> I thought it was later, but no reason we can't start now
[20:00] <valorie> hmmm, looks like ahoneybun didn't add the meeting to calendar
[20:00] <valorie> tsk tsk
[20:01] <valorie> i'm supposed to be in another meeting right now but I don't see JP on irc, so....
 HiI Rick. Good to see you. :)
 I am here and not here :/
[20:02] <valorie> @acheronuk, where are you on minimal install?
 Same here. Easter lunch with the family.
[20:02] <valorie> does a mini-install work yet?
 it works
[20:02] <valorie> @tsimonq2 Easter is tomorrow!
 @valorie, I know :)
 just the package list needs refining a bit
[20:02] <valorie> do you feel like you are done with it?
[20:03] <valorie> oh, ok
[20:03] <valorie> task not ready for the "done" pile then
[20:03] <sick_rimmit> acheronuk: Hiya, good to see you too
 Heyo Rick
[20:04] <sick_rimmit> tsimonq2: Hello young man, nice to see you, hoe you getting along ?
 @valorie, not sure it will require too much discussing. it is mostly a dev job now of getting rid of left over cruft that PIM etc leaves behind when the main apps are removed
 @sick_rimmit, Pretty good!
[20:07] <valorie> @acheronuk cool, I'm just sort of randomly clicking on stuff I know anything about
[20:07] <valorie> looks like most of the uploads on our wishlist are done
 @valorie, that is exactly my tactic every time I look at the board. 🤣
 Last chance to get uploads in is tomorrow
[20:08] <valorie> https://phabricator.kde.org/T7332
[20:08] <valorie> so I guess today is the last chance for anything left there that anybody realy realy really wants
[20:09] <sick_rimmit> Ah, so I was playing with MyCroft PLasmoid today
 Yep.
[20:09] <sick_rimmit> I didn't get it working yet.
[20:09] <valorie> is the Morse issue resolved, or just *dead*
 Monday is only beta freeze. In theory a new source could go in after
[20:09] <valorie> https://phabricator.kde.org/T5125
 I'm pretty sure that project is dead :(
 Cutelyst is on my radar. … Peruse needs some fixing up and an upload to Debian. … Some new Qt packages need to be uploaded (we have #ubuntu-qt for coordination of that now, btw, Rick). … Am I missing anything we want in for 18.04?
[20:10] <valorie> I see no sign of telepathy reviving soon, so I'm going to mark that one as dead
[20:10] <valorie> ah, I thought peruse was done
[20:11] <valorie> ok
 I'd love to see an official package for Lollypop, FWIW
 @acheronuk, It's Final Freeze. I've already asked, and been told "no" for new sources. :P
 clive was keen on that new tp stuff. I never really cared, as it seemed to want to stay dead
 it's the best GTK music player in existence IMHO, and so good that I use it in Plasma
 @tsimonq2, Unless it's super urgent or the KC makes a statement on it.
 @valorie, Peruse had some concerns that I need to address. Upstream doesn't do library handling right, and I messed up the version number...
[20:12] <valorie> ok
 I'll be going for Debian Maintainer at LFNW so I should be able to upstream a lot of this work.
 @tsimonq2, Final freeze is April 19th on the schedule
 @acheronuk, Hmmmmmm
 Oh
 I suck XD
[20:13] <valorie> @nggraham have you filed a bug for that lollypop thing on LP?
 So, we'll be able to do a Qt transition after all...
[20:13] <valorie> I don't see us doing it though, because it's gtk
 But I'll still call it a deadline for new sources unless a flavor identifies it as a release goal.
[20:14] <valorie> falkon got in, correct?
 https://wiki.ubuntu.com/BetaFreeze
[20:14] <valorie> I didn't have a chance to check on the travel laptop
 @valorie, Yepper
 "Once the BetaRelease is shipped, we roll back to FeatureFreeze and UserInterfaceFreeze status. "
 @acheronuk, Yeah I got mixed up. :P
[20:15] <valorie> \o/
 We shoudl still aim to get things in PDQ though
 But yeah, besides Qt, if anyone sees a new upstream bugfix release of things, yell loudly and we can get it in.
 @acheronuk, Right.
 for that, please test Krita 4.0.0 in ppa:kubuntu-ppa/staging-misc
 @tsimonq2, Before Final Freeze, that is...
[20:16] <sick_rimmit> \o/ Yay I'm really pleased about Falkon
[20:16] <sick_rimmit> Ah ha, I am a pretty competent Krita user. I'll pull that in and test it
[20:17] <valorie> I use it exclusively now and love it
[20:17] <valorie> So Peruse, Cutelyst, kio-stash, systemdgenie, Plasma Mycroft and kube remain unpackaged or not uploaded.
[20:17] <valorie> from the list on that task
[20:17] <sick_rimmit> I really really think Plasma Mycroft should be focused on
[20:18] <valorie> what are the issues with it?
 One other thing is that I did a Mass Bug Filing in Ubuntu the other day. No new package sources should be introduced that depend on Qt 4, and the goal is to get that completely removed by the 19.04 release. … So if you see a package here that isn't triaged that you want to get ported, make sure to talk to upstream! https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal
[20:18] <sick_rimmit> That is such an exclusive item, and we could mke much PR of that
 @sick_rimmit, Got a link to the source package.
 s/./?/
[20:18] <valorie> !info plasma-mycroft
[20:18] <sick_rimmit> Sure.. stand tsimonq2
[20:19] <valorie> sick_rimmit: I'm reasonably sure neon has a package
[20:20] <sick_rimmit> https://github.com/MycroftAI/mycroft-core.git
 I love Neon, I really do, but some of their stuff is "package it and don't touch it"...
[20:20] <sick_rimmit> on 17.10 the Core won't build for me, the problem is with Python virtualenv
[20:20] <sick_rimmit> missing zlib.so.1
[20:20] <valorie> right, but plasma-mycroft
 @sick_rimmit, Hum
[20:20] <sick_rimmit> Hangon not finished
[20:20] <valorie> the other stuff isn't KDE software
[20:20] <valorie> this is
[20:20] <sick_rimmit> I'll grab the next link
 If y'all can find Neon's packaging, that'd be cool.
 doing krita ffe bug.....
[20:27] <valorie> my friend showed up for our meeting so I'll be busy elsewhere for awhile
 Does anyone find it important to get Qt Creator 4.6.0 or Gcompris-qt 0.90 in Bionic?
 @tsimonq2 https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1760347
 @tsimonq2 please amend, if you feel appropriate
[20:29] <valorie> acheronuk: thank you! I know paperwork is not your most loved thing
[20:29] <valorie> anybody know if this https://phabricator.kde.org/T8177 got done?
[20:29] <sick_rimmit> tsimonq2: https://cgit.kde.org/plasma-mycroft.git/
 @acheronuk, Ack. I'll poke around next week.
[20:30] <sick_rimmit> This is not the one I was using today, but I can't find that. However, AIX states on his GitHub that this is now the latest and greatest
[20:31] <valorie> well, for plasma stuff, cgit is the latest and greatest
[20:31] <valorie> not github
[20:31] <valorie> which is only a mirror, and sometimes out-of-date
 @sick_rimmit, I'll package it tonight and give you something to play with tomorrow, then we can decide from there if it's ready?
 @valorie, nope. I can't test PLASMA_USE_QT_SCALING=1 thing, and it seems to me to be problematic
[20:32] <valorie> ah, ok
 what's the problem with it?
[20:33] <valorie> perhaps when you have a sec you can comment on it
 @nggraham, https://bugs.launchpad.net/bugs/1760319
 I don't know, and can't test though
 interesting, didn't see that in my own testing
 taking a look
 but maybe this is too buggy to turn on yet, especially for an LTS
 @nggraham, my instinct said that, even before seeing that bug. So if you want it in, you are going to have to prove that feeling wrong
 sounds like your instinct is right; let's not do it
 I'll do more upstream work first to see if we can kick it into shape
[20:37] <valorie> I edited the task  : Wait until 18.10; re-test
 ok :)
[20:39] <sick_rimmit> tsimonq2: That sounds excellent
[20:41] <valorie> @nggraham, any more progress on https://phabricator.kde.org/T7566 ?
[20:41] <valorie> backends for Discover
[20:41] <valorie> sounds very promising
 I wouldn't support changing the default backend, but I think we could turn on the Flatpak backend, at least. It's pretty stable.
[20:43] <valorie> I would love to see snaps/flatpacks/whats the other thing all offered
 what I think would be really awesome is to ship with the Kubuntu backports PPA added, but disabled, so people could go into Discover and turn it on with one click
[20:44] <valorie> how much testing was done though?
[20:44] <valorie> this is an LTS....
 on the flatpak backend?
[20:44] <valorie> yes
 a lot. I use it in 5.12 myself and report every bug I see, and there aren't many
[20:45] <valorie> or with the PPA added but disabled
[20:45] <valorie> the problem I see with the latter idea is that how does one do ppa-purge via discover?
[20:45] <valorie> and that is very occasionally necessary
 @valorie, actually now that I think about it, we can't do this because the UI for showing debian-based repos is still terrible in Discover
[20:46] <valorie> ok
 and yeah, DIscover can't do ppa-purge
[20:46] <valorie> so:  : Wait until 18.10; re-test
 @nggraham, not allowed
 not allowed?
 @acheronuk, Gray area
 I can ask the TB
[20:50] <valorie> so not much input on https://phabricator.kde.org/T7979
[20:50] <valorie> and might be a bit too late for this one
 Kylin and MATE *technically* do similar things.
 well it's moot anyway because even if it was allowed and disirable, Discover isn't ready yet
[20:50] <valorie> Use kicker by default for Application Launcher
 @valorie, yes please
[20:50] <valorie> we have lots to do for the Chronic Carrot
 Kicker is much better and more usable than Kickoff
 [09:02] <acheronuk> hi. is there an issue with flavours shipping a ppa sources list in /etc/apt/sources/ even if disabled by default? I vaguely recall this was a red line 'thou shall not cross', but could be wrong? … [09:02] <acheronuk> *sources.d/ … [09:10] <slangasek> acheronuk: why would you ship it if it's disabled by default?  But yes, it is a red line
 @acheronuk, I have an agenda item at the next TB meeting anyway, I'll ask.
 I would rather people have to deliberately add the source anyway. added by default, but diabled, suggests a level of support'ness (if that's a word) that it doesn't merit
[20:55] <valorie> we do often announce it, and how to add it
[20:55] <valorie> and I quite often link to that announcement in #kubuntu
[20:55] <valorie> or on the k-user list
[20:55] <valorie> so I'm with acheronuk on this one
 Ok
[20:56] <valorie> we usually or always mention ppa-purge just in case
[20:56] <sick_rimmit> Rebooting - brb
[20:57] <valorie> so, are we doing https://phabricator.kde.org/T7979 or not? too late to do it?
[20:57] <valorie> I can never remember the names
[20:57] <valorie> but I always change
 Kicker is the nice one :)
[20:58] <valorie> rofl
 Kickoff is the huge space-wasting one that doesn't switch tabs until 250msec of hover time, and makes you click on app categories to look at apps, and click again to go back
 You know what I've been keeping an eye on lately? … I encourage y'all to grab an ISO of Ubuntu MATE or Ubuntu Budgie, and check out their welcome center...
[20:59] <valorie> I don't like their color schemes but it is pretty nice
[20:59] <valorie> I helped with their beta1 tests
[20:59] <valorie> when ours were fudged
 I like kickoff, and the stealth branding it gives us :P
 heh
 we already get extra always-visible branding via the menu icon now though!
 plus it's a bit win10 (ish)
[21:01] <valorie> sec
 personally I would rather go with the familiar kickoff for the LTS, and again make a experimental switch for 18.10
[21:04] <valorie> hmmm, wonder where ahoneybun is?
 if we stay with kickoff, let's patch it to make the tabs instantly switch on hover instead of making you feel like your machine is crawling through molassas. I'm submitting a patch upstream now that we can cherry-pick if it's accepted (and I expect it to, as it seems popular among the plasma developers)
[21:05] <valorie> ok, so put on hold until 18.10?
 250ms ?????
 yup
 check out /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml on your machine
 try reducing that to like 15 and see how much it lowers your blood pressure :)
 can't actually say it has ever bothered me!
 you must be a tolerant soul
[21:07] <sick_rimmit> Just played with Kickoff - +1 for nggraham. It's really subtle and I never noticed, but now he points it out, I agree
 Timer { …         id: clickTimer
[21:07] <mamarley> I usually just click on those buttons.
 an admirable trait, outside of UI criticism! 🤣
[21:07] <sick_rimmit> mamarley: Funny me too
[21:08] <valorie> i usually just use krunner
[21:08] <sick_rimmit> which is probably because of the delay
[21:08] <valorie> rare that I use either
 the menu has a limited form of KRunner inside it, actually
 its search *is* a KRunner search
[21:08] <valorie> cool
[21:09] <sick_rimmit> valorie: I wish I could get into the habit of using that, it would save me so much time
 but we can make it even better: https://bugs.kde.org/show_bug.cgi?id=38276
[21:09] <valorie> alt+space and type
 oops, that's not the right bug...
[21:09] <valorie> for everything!
[21:09] <valorie> even simple addition, subtraction
[21:09] <valorie> esp useful for systemsettings
 This one: https://bugs.kde.org/show_bug.cgi?id=382760
 that's on my to-do list, and then it just becomes "meta key and type"
[21:11] <sick_rimmit> OK, friends I got to go.. catch up tomorrow
[21:11] <valorie> but meta key+type doesn't work for subtraction
[21:11] <valorie> lol
[21:11] <valorie> sick_rimmit: {{{{{{{{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}
[21:11] <valorie> so good to see ya
 @sick_rimmit great to see you
[21:12] <valorie> have a wonderful easter
 bye bye!
[21:14] <valorie> so are we deciding on https://phabricator.kde.org/T7979 ?
[21:14] <valorie> or waiting
[21:16] <valorie> because the right-click for alternatives is not the most discoverable thing
[21:16] <valorie> so I imagine 90% of our users will stick with the default
[21:16] <valorie> if not more
 I don't see anything wrong with that :P
[21:17] <valorie> I don't feel strongly either way
[21:17] <valorie> but I always change it
[21:18] <valorie> to menu
 Well, I have both as I use a bottom and top panel. So have kickoff on the top one, and kicker on the bottom.
 I always change it too, but Kicker has problems of its own. I'm actually writing a new menu right now that's based on Eike Hein's SimpleMenu that I hope will be better than all of them
[21:18] <valorie> why on earth do they call it kickoff and kicker, and then in their own menu call it menu and launcher/
 Simplemenu gound be sooooooooooo good
 SimpleMenu is amazing
 but a bit *too* simple
[21:19] <valorie> ok, so lets wait until 18.10
 mine uses it as a base, but adds missing features. I call it SuperMenu :)
 Let me put it this way. I will change it, but ONLY if I am seriously outvoted! lol
 Lets at least get beat feedback
[21:21] <valorie> yes
[21:21] <valorie> so: https://phabricator.kde.org/T7911
[21:21] <valorie> Kubuntu should install PowerTOP and TLP and turn them on during installation
[21:22] <valorie> quite a few yes votes, yofel had a sobering message about testing
[21:22] <valorie> and I have to agree, I didn't see this in a PPA or so for testing
[21:22] <valorie> and so didn't test
 it's not in a PPA, it's abailable in the default repos
[21:23] <valorie> ah
[21:24] <valorie> well, a call for testing should have gone out
[21:24] <valorie> I didn't really notice this until now, sorry
 I just run laptops off the adapter 99% of the time, but the few time I have treid stuff like that before I got really ****y performance to get a few % more battery life
 but has been some years since I tried
[21:25] <valorie> I'm not willing to vote for it without more testing
 I use it on mine and it makes a difference in battery life. Gets me about an extra hour and a half, up to 8.5 hours
[21:25] <valorie> for the LTS
[21:25] <valorie> that's cool
[21:26] <valorie> let's put up a wiki page or even let people login to phab and give their feedback there
 if we are too push that on people by default, then we need a good case for it being of benefit to that majority, and no detriment to others
[21:26] <valorie> but this needs more than just a couple of testers
[21:27] <valorie> precisely
 yep
 ok. maybe back in a bit. maybe not. "good stuff" so far
[21:30] <valorie> ok, I'll be around
[21:33] <valorie> any progress recently on Replace Middle Click Paste on Desktop with Application Launcher ?
[21:33] <valorie> https://phabricator.kde.org/T7978
[21:34] <valorie> sounds like a stalemate
 bye guys, I'm off too for a while
[21:34] <valorie> @nggraham, LOL at your PM
[21:34] <valorie> ciao!
[21:38] <valorie> !info TLP
[21:38] <valorie> !info powertop
[21:43] <yofel> from what I saw, TLP had fairly sane defaults, so I could be convinced to seed that.
[21:43] <yofel> Powertop OTOH, while being a really useful CLI power usage reporting tool, isn't that useful for a general user. And turning on auto-tuning unconditionally is something I don't feel good about, as it changes kernel settings
[21:45] <valorie> ugh
[21:45] <valorie> thanks for speaking up about it yofel
[21:46] <valorie> did you see https://www.omgubuntu.co.uk/2018/02/better-battery-life-on-fedora-linux ?
[21:47] <valorie> Enabling auto-suspend for USB Bluetooth seems like a no-brainer, although bluetooth often seems buggy
[21:48] <valorie> dunno what Enabling auto-suspend for Intel HDA codecs would do or not do
[21:48] <valorie> same with
[21:48] <valorie> Enabling SATA link PM by default
[21:48] <valorie> Enabling i915 Panel Self Refresh by default.
[21:49] <valorie> I remember trying powertop in the past and didn't see any effects at all, good or bad
[21:49] <valorie> but i''ll try it again on the travel lappy
[21:50] <valorie> this laptop is always plugged in
[21:50] <valorie> it's nvidia and battery life is bleah
[22:00] <valorie> ok, if we're all gone for now, so am I
[22:00] <valorie> :-)
[23:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-runtime build #263: STILL FAILING in 2 min 49 sec: https://kci.pangea.pub/job/artful_unstable_kdepim-runtime/263/
[23:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #398: STILL FAILING in 3 min 49 sec: https://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/398/
[23:42] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kdepim-runtime build #135: STILL FAILING in 3 min 50 sec: https://kci.pangea.pub/job/xenial_stable_kdepim-runtime/135/
[23:42] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdepim-runtime build #144: STILL FAILING in 3 min 51 sec: https://kci.pangea.pub/job/artful_stable_kdepim-runtime/144/
[23:44] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdepim-runtime build #89: FAILURE in 5 min 54 sec: https://kci.pangea.pub/job/bionic_stable_kdepim-runtime/89/


[01:03] <seiflotfy> hey gus
[01:03] <seiflotfy> guys
[01:03] <seiflotfy> :)
[01:04] <seiflotfy> I have been thinking of a way to maybe enhance launchpad experience
[01:04] <seiflotfy> Using Zeitgeist as a backend in Launchpad will allow users to have a personal timeline of their activities regarding themselves or specific project. This will allow easier trackeing of when things were done commited and view a chronicle of the project in terms of all (blueprints/bugs/etc..) mashed together.
[01:04] <seiflotfy> Basically what we can provide is a timeline per project/team/individual
[01:07] <seiflotfy> I think I can get it done
[01:07] <seiflotfy> imagine a persoal journal for each developer
[01:08] <seiflotfy> poolie, ?
[01:09] <seiflotfy> sorry
[01:10] <seiflotfy> back
[01:10] <seiflotfy> poolie, did i miss something or is it still silent in here
[01:12] <poolie> sorry, phone
[01:12] <poolie> i think it would be a superb idea
[01:12] <poolie> the big question istm is how, technically, we will get activity data from lp into zeitgeist
[01:13] <seiflotfy> well it has to be hooked into launchpad
[01:13] <seiflotfy> :)
[01:13] <seiflotfy> basically if anything happens on launchpad it has to be forwarded to the zeitgeist running on the server
[01:16] <seiflotfy> so its basically hooking up into launchpad and listneing ot activities
[01:17] <poolie> right, that's the key thing
[01:18] <poolie> actually, i should really have sent you to #launchpad-dev, not here :)
[01:18] <poolie> do you mind?
[01:19] <seiflotfy> nope
[01:19] <seiflotfy> not at all
[01:26] <_habnabit> So I'm getting an odd error when checking out a bzr branch, but only on windows.
[01:27] <_habnabit> bzr 2.2.1, I get an error about 'checkout/limbo/new-3' already existing every time.
[01:27] <_habnabit> Across three different machines.
[01:27] <_habnabit> Pulling over ssh from a UNIX machine, if that matters.
[01:27] <_habnabit> I can pastebin the exact error.
[06:59] <poolie> _habnabit: hm, please search for an existing bug, or file a new one?
[06:59] <_habnabit> poolie, whoops, I forgot to mention I resolved it.
[06:59] <poolie> oh, what was it?
[06:59] <_habnabit> Windows was choking on the filename '. '
[07:00] <_habnabit> svn did it too, back when we used svn. That's how I recognized the problem!
[07:23] <vila> hi all
[07:25] <peitschie> evenin vila :)
[07:25] <vila> peitschie: ;)
[07:29] <poolie> hi vila; now i have to run
[07:29] <poolie> vila, are you on the udd list? you should be
[07:30] <vila> poolie: hello, bye, any news about pqm ?
[07:30] <poolie> what about it?
[07:30] <vila> I think so
[07:30] <vila> I just upgraded and had to reboot, will look at my mail backlog now, any topic in particular ?
[07:30] <poolie> you'll see it :) i just sent a bit mail
[07:30] <poolie> is something wrong with pqm?
[07:31] <vila> the upgrade to testtools-0.9.6 went wrong leading to no subunit
[07:31] <vila> i.e. no more landing
[07:32] <vila> jam was trying to follow yesterday when I EODed, I was just wondering if you heard about it
[07:33] <poolie> i hadn't even heard that
[07:33] <poolie> tell the list? chase a losa
[07:33] <poolie> i haven't tried to land anything today
[07:33] <poolie> more's the pity
[07:34] <vila> oh, it's under losa's control, re-building the needed bits was taking a long time and mthaddon also EODed before it was done, so I don't know where it's at but I will ;)
[07:34] <poolie> k, please send a mail letting us know one way or the other
[07:34] <vila> k
[07:36] <vila> poolie: so, yes, I'm subscribed to udd, got your 'udd at uds-n' yesterday
[07:36] <vila> poolie: and I'm a big fan of the UDD stakeholders meeting minutes for a while ;)
[08:41] <GaryvdM> Morning all.
[08:41] <GaryvdM> Bla - I missed poolie.
[08:46]  * jelmer waves to Gary
[08:53] <GaryvdM> Hi jelmer
[10:37] <vila> GaryvdM: hey !
[10:42]  * jelmer hugs GaryvdM
[10:42] <GaryvdM> :-)
[10:42]  * GaryvdM is not sure why
[10:45] <jelmer> GaryvdM: I noticed your last MP when I was reading my email.
[10:45] <GaryvdM> Ah :-)
[10:47] <vila> +1
[10:48] <vila> GaryvdM: I saw your loggerhead poc the day *after* you mentioned it and was never able to congratulate. Now is the time: very well done ;)
[10:50] <GaryvdM> vila: thanks
[14:02] <vila> maxb: ping
[14:02] <vila> maxb: we are upgrading testtools/subunit on pqm for bzr
[14:02] <vila> maxb: we used the packages from the stable bzr PPA
[14:03] <vila> maxb: it turned out that we also needed  python-central-debhelper-sequence-addon provided by the https://launchpad.net/~bzr/+archive/builddeps PPA
[14:03] <vila> maxb:  so far, so good, except that subunit-stats is nowhere to be found now, does this ring a bell ?
[14:15] <soren> Is there a way I can trick two branches into having a common ancestry?
[14:15] <soren> Use case:
[14:15] <soren> I have a project which has a number of series, each with their own branch.
[14:16] <soren> I want to put my packaging code (which should apply cleanly to any of these branches) in a separate branch which has nothing but the packaging (contained in a debian/ directory).
[14:17] <soren> Just creating a new repo doesn't work, because it'll complain about lack of common ancestry.
[14:18] <maxb> vila: Hello
[14:18] <soren> I thought I was being clever, and tried "bzr branch -r 0 <one of the upstream branches> packaging" hoping that would give me a branch with a common ancestor (namely some sort of fictional 0th commit)
[14:18] <maxb> vila: You should only need python-central-debhelper-sequence-addon to build the package, and only on hardy.
[14:19] <maxb> Is the bzr PQM machine still lagging behind? I thought most of the datacentre wa on lucid now
[14:19] <vila> maxb: seems like it was required to install subunit :-<
[14:19] <maxb> wtf?!
[14:19] <vila> +1
[14:19]  * maxb fires up a quick cowbuilder chroot
[14:20] <vila> maxb: we need python-2.4 there to ensure compatibility, it's gone in lucid AFAIK
[14:21] <maxb> vila: meh. ok
[14:22] <maxb> vila: I'm still confused, I just ran 'apt-get install python-testtools subunit' in a hardy chroot, WITHOUT bzr/builddeps, and it installed fine
[14:23] <maxb> Or, it is because the l o s a s want to rebuild the packages in their own archive?
[14:23] <vila> maxb: exactly
[14:23] <maxb> Ah, well that's entirely different then.
[14:23] <maxb> I wish they could be a little more trusting. It's not like PPAs aren't a secured build environment already
[14:24] <vila> +1 :-}
[14:24] <vila> well, I can understand them too :-/
[14:26] <vila> maxb: well, when I said exactly I may not have been correct, I don't really know if they copy the packages or if they rebuild them
[14:28] <vila> maxb: python-central-debhelper-sequence-addon is from you right ? Can you refresh my memory ? It's a workaround about python-central or ?
[14:29] <maxb> It's a backport of a single file that was added to python-central after hardy
[14:29] <vila> ok
[14:29] <maxb> in fact
[14:30] <maxb> python-central-debhelper-sequence-addon (0.6.8~bazaar1~hardy1) hardy; urgency=low
[14:30] <maxb>   * This package takes the python-central debhelper sequence file from
[14:30] <maxb>     python-central 0.6.8 and repackages it for installation on hardy, whose
[14:30] <maxb>     python-central ships no debhelper sequence file.
[14:30] <maxb>  -- Max Bowsher<EMAIL_ADDRESS> Wed, 01 Sep 2010 02:05:46 +0100
[14:31] <vila> hence the value of commit messages :)
[14:31] <vila> or changelogs
[14:33] <maxb> I mainly did it that way because it seemed nicer than rebuilding a core infrastructural package like python-central just to provide an additional file
[14:34] <vila> maxb: which sounds perfectly reasonable
[14:35] <vila> maxb: what I don't understand is why (and where) we lost subunit-stats
[14:35] <maxb> What is subunit-stats? A binary package that is supposed to be there but is not?
[14:35] <vila> maxb: when upgrading subunit
[14:35] <vila> it's a script provided by subunit
[14:35] <maxb> uh, it exists in *my* package
[14:36]  * vila cries
[14:37] <maxb> vila: Do you have (read-only) shell access to the PQM machine?
[14:37] <vila> maxb: can I ping you back once my losa is back (he said biab less than an hour ago)
[14:37] <GaryvdM> soren : You can do bzr merge -r 0.. ../packing_branch
[14:37] <vila> maxb: mwhahahahahahaha
[14:37] <vila> maxb: does this answer the question ? >-/
[14:37] <soren> GaryvdM: Yeah, but that's terrible.
[14:37] <maxb> Not entirely :-)
[14:37] <GaryvdM> soren: Or use bzr join
[14:38] <soren> GaryvdM: I have to tell everyone else to do that, not all tools support it (bzr-builder, for one doesn't).
[14:38] <GaryvdM> soren: Why?
[14:38] <vila> maxb: my access to pqm is: send submissions, see new revisions on bzr branches when all goes well, see no email when something fail because my ISP, most of the times, consider pqm email as spam
[14:38] <GaryvdM> Ok - Sorry, I'm not familiar with bzr-builder.
[14:39] <vila> maxb: oh, and http://pqm.bazaar-vcs.org/ of course
[14:39] <maxb> Hrm. If there's one thing I think Canonical does poorly, it's this iron curtain between developers and admins
[14:40] <soren> GaryvdM: Mostly it's because I shouldn't have to.
[14:40] <fullermd> Well, somebody has to keep vila in his place...
[14:40] <maxb> Sometimes it just has to be, like where LP is storing proprietary data, but on the bzr PQM machine !?
[14:40] <vila> well, as long as things works well, they are doing a great job, pqm is the only exception this far
[14:40] <soren> GaryvdM: Most people want to do this because they want to avoid conflicts between identical files.
[14:41] <vila> maxb: if I was an admin I would be quite worried to let devs play around with production servers too :)
[14:41] <soren> GaryvdM: I understand why that happens, and I'm fine with that. I just want to be able to merge two trees that have no files in common.
[14:41] <vila> maxb: may be the problem here is that we shouldn't use a production server for pqm....
[14:41] <maxb> vila: I love working in a small (division of a) company. I'm a dev, but I have root@ the production servers for my app
[14:41] <soren> GaryvdM: ..and I'm actually lucky enough that I get to start one of these from scratch, so I thought I could create the common ancestry this way.
[14:42] <vila> maxb: who is the official root then ?
[14:42] <fullermd> Yeah.  It's nice being the dev AND the admin.  I'd go nuts trying to work any other way...
[14:43] <vila> maxb: as in: who is blamed when things go horribly wrong ?
[14:43] <vila> fullermd: I am slowly going nuts on this problem :(
[14:43] <vila> I see fingers all around...
[14:43] <fullermd> Sounds like a waste of time.  Why not go nuts quickly?  Then you have more time to enjoy it.
[14:44] <maxb> vila: Whoever broke it :-)
[14:44] <vila> maxb: Ha ! Easy, if you already know *who* :D
[14:44] <vila> fullermd: hehe, thanks, feeling better already :D
[14:45] <fullermd> That's easy to find out.  Just take everyone with root, and lock them in a room with a couple bricks.  Whoever makes it out under their own power is innocent.
[14:46] <vila> fullermd: yeah, all in the same room, quite tricky in a distributed company :-P
[14:47] <fullermd> That just means they need bigger bricks   :p
[14:48] <soren> Does bzr's data model simply not support this or is it just not possible with the current UI?
[14:52] <vila> soren: #ubuntu-devel should get you better answers, they do that routinely AIUI
[14:53] <vila> soren: you *can* merge your packaging branch into all your series branches and from there merge the changes in the packaging branches
[14:54] <vila> but you can't keep them separate and still ask them to have a common ancestry
[14:55] <maxb> soren: Why do you need a common ancestry at all?
[14:55] <soren> vila: it's just silly that if I had known from the start that I wanted to do this, I could have created an emtpy revision as my r1, and branch from that.
[14:56] <soren> maxb: In short: To be able to merge them without having to specify a base revision.
[14:56] <soren> maxb: I explained the use case 40 minutes ago in this channel.
[14:56] <maxb> Why do you need to do that? (bzr-builder now supports nest-part for embedding a debian directory)
[14:57] <soren> maxb: For a couple of reasons, it's more convenient to have the debian/ directory in the bzr repo (and not just the contents of it).
[14:57] <maxb> Agreed. nest-part was created to allow that layout
[14:58] <soren> maxb: Er?
[14:58]  * soren looks at code
[14:58] <maxb> nest-part allows you to instruct bzr-builder to take the debian directory from your branch and place it into the upstream branch, without it ending up at debian/debian/
[14:59] <soren> maxb: Oh, cool.
[14:59] <soren> maxb: That solves the recipe problem, at least.
[14:59] <soren> maxb: It's just annoying that I have to tell people to do special things to merge this stuff.
[15:00] <soren> maxb: Especially since a lot of these people are git fanatics, and they get all excited and annoying when these quirks come up.
[15:00]  * maxb attempts to think how this would work in git
[15:00]  * maxb fails
[15:00] <soren> I don't know. I don't really care. :)
[15:02] <Tak> blargh, I don't know what it is about git that fanaticizes people
[15:03] <soren> But it's so fast!!!!1!!!!eleven!!!
[15:03] <mthaddon> vila: howdy - so what do we need to discuss?
[15:04] <vila> mthaddon: hehe, where did subunit-stats go ?
[15:05] <mthaddon> vila: how can I help answer that?
[15:05] <vila> mthaddon: it's part of subunit and that;s what you installed right ? maxb built it and found subunit-stats in his hardy chroot
[15:05] <mthaddon> maxb: in which file?
[15:05] <maxb> mthaddon: In the 'subunit' binary package
[15:06] <maxb> Could you check 'dpkg -L subunit' ?
[15:06] <mthaddon> maxb: we have python-subunit installed, not subunit
[15:06] <maxb> Ah. You should also have subunit installed, to provide the command line entry points
[15:06] <mthaddon> hookay...
[15:07]  * mthaddon suggests there really should be a bzr-pqm-dependencies package, but feels like he's suggested that before
[15:07] <mthaddon> and presumably we'll need the version of subunit from the same PPA?
[15:09] <vila> mthaddon: that's where it's get interesting since the stable bzr PPA provides subunit not python-subunit, so where did you get the later ?
[15:11] <mthaddon> hmm, interesting - in any case, have subunit ready to install now, one sec
[15:13] <vila> mthaddon: +1 on bzr-pqm-dependencies package, but isn't it already covered by the PPAs ?
[15:13] <mthaddon> vila: er, how?
[15:13] <vila> they provides all the needed packages no ?
[15:14] <mthaddon> vila: a dependencies package defines all the specific packages and versions - we don't install directly from PPAs
[15:14] <mthaddon> vila: subunit has now been installed
[15:15] <vila> mthaddon: how did you use the PPA there ?
[15:16] <mthaddon> vila: I'm not sure I understand the question
[15:16] <vila> :)
[15:16] <vila> You asked me for PPAs but then you say you don't install from them, then what bit do you use ?
[15:16] <vila> mthaddon: submission set
[15:16] <vila> sent
[15:17] <mthaddon> vila: we backport from the PPA, we don't install directly from them, so having packages in a PPA is only part of the puzzle
[15:18] <vila> what means backport here ?
[15:18] <vila> You install and repackage ?
[15:18] <mthaddon> vila: having a dependencies package means you can define exactly which packages need to be installed and what versions, and we know as long as we satisfy that everything will work rather than having to ask about each individual package
[15:19] <mthaddon> we download the source package from the PPA, verify it, build it and upload it to the admin repos
[15:19] <vila> ha right, stupid, you can get the source from the ppa
[15:20] <vila> so if we had this package we can just update it and ask you to update
[15:21] <mthaddon> yep
[15:21] <vila> shudder
[15:21] <vila> it's kind of chicken -and-egg problem, *I* don't know precisely what is used *today* on pqm
[15:22] <vila> but probably enough to give it a try
[15:22] <vila> except I have no idea how to write such a package :D
[15:23] <vila> echo Depends: bzr, subunit, python-testtools > sudo make-me-a-package
[15:25] <mthaddon> the way to determine if it's correct would be to create a clean install, install the dependencies package, run the test suite, and see what it needs
[15:25] <mthaddon> should be fairly easy to do
[15:26] <mthaddon> and we have a ton of dependencies packages that we maintain for other projects, so if you need an example that's easy enough to provide
[15:26] <vila> mthaddon: deal, you've got my email ?
[15:29] <vila> mthaddon: I'm sure I won't be able to build a perfect pqm clone but I should be able to mimick the real one close enough (minus email handling, chroot, web report and so on ;)
[15:29] <mthaddon> vila: you don't need to do a pqm clone at all - just a chroot to run the test suite
[15:30] <mthaddon> vila: or a vm or whatever
[15:33] <vila> mthaddon: my crystal ball knows less than you (and I trust you) so it's reporting grey areas, so I will *assume* that running the test suite will be enough but I already have an hardy VM and by *default* python-2.5 is used not python-2.4, such details are so easily missed...
[15:33] <mthaddon> vila: see https://edge.launchpad.net/~launchpad/+archive/ppa - launchpad-dependencies for an example
[15:33] <vila> perfect
[15:34] <mthaddon> vila: you'd need to run the same command we run for PQM - "LANG=en_GB.utf8 make check PYTHON=python2.4"
[15:35] <vila> en_GB.utf8 ! Of course !
[15:52] <mgz> ooh, vila has won in the battle against pqm?
[15:52] <mgz> should I merge up my branches?
[15:53] <vila> mgz: no, and first you should mthaddon :D
[15:54] <vila> mgz: I have a test submission running, please don't fill up the queue (yet) :F
[15:54] <mgz> +thank? +eat? +marry?
[15:54] <vila> :D
[15:54] <vila> marry
[15:54] <vila> err no, thank
[15:54] <vila> stupid random mouse events doing copy paste now ? What next ?
[15:55] <mgz> a giant lwn thread!
[15:55] <fullermd> Iguana invasion?
[16:14] <GaryvdM> Hi jam
[16:15] <jam> morning GaryvdM
[16:15] <GaryvdM> I want to talk to you about bug 153787
[16:17] <jam> k
[16:17] <GaryvdM> I think it would be better to for me to work on a iterative gui annotate.
[16:18] <GaryvdM> So I guess I'm going to need to add api to the Annotator classes.
[16:19] <GaryvdM> And plumbing api to the tree objects
[16:19] <jam> I think that is the route I would go
[16:20] <jam> note that it turns a lot of the guts of Annotator on its head
[16:20] <jam> so its a non-trivial change
[16:20] <jam> I would actually expect in the short-term for annotation to get quite a bit slower, though the tradeoff is that you'll get initial results faster
[16:20] <jam> command-line annotate would get slower, though
[16:21] <GaryvdM> Oh - ok. I've read some of the code, but not enough to understand why.
[16:21] <GaryvdM> I hope that is not the case.
[16:21] <jam> annotation currently is based around start at the original, and build up to the current
[16:21] <jam> and it knows when you can release what texts, etc
[16:21] <jam> based on whether anything needs that in the future
[16:21] <jam> (simple refcounting, really)
[16:22] <GaryvdM> Ok - usefull to know
[16:22] <jam> lots of other differences...
[16:22] <jam> for example, if you annotate in reverse, can you then save an intermediate step?
[16:22] <jam> or will reverse annotating break caching?
[16:23] <jam> will the api depend on incremental updates, what happens if you have a cache and can answer the whole thing right away?
[16:23] <jam> (just make sure that sending more information than a single step is reasonable, and it should be fine)
[16:23] <GaryvdM> Ok
[16:23] <jam> annotating forward, you 'save' each step along the way before you're ready to do the next step
[16:23] <jam> annotating in reverse, I think you would only tend to save "this is what I know about so far"
[16:23] <jam> has some benefits
[16:24] <jam> potentially, you could change the diff matching code to know to not care about certain regions because they "already match"
[16:24] <jam> but that would be a pretty major change, too
[16:24] <GaryvdM> Ok.
[16:25] <GaryvdM> Thanks - Lots of usefull info to think about.
[16:26] <jam> I think the first thing is to just design an api that can talk about it the way you want
[16:26] <jam> and then to validate an actual step-by-step produce this
[16:26] <jam> without worrying about too much caching, etc
[16:26] <jam> and then see what you get
[16:26] <GaryvdM> Ok
[16:26] <jam> also, we may need a new "get_record_stream" verb
[16:26] <jam> we currently have "topological"
[16:26] <jam> but this will want "reverse_topological"
[16:27] <jam> which is *close* to "groupcompress" order, and maybe a good enough approximation, as long as your code could handle things not 100% in order
[16:27] <GaryvdM> jam: Where would that need to be implemented? VersionFile implementations?
[16:28] <GaryvdM> reverse_topological ^
[16:28] <jam> GaryvdM: something like that, yes.
[16:29] <jam> As mentioned, punt for now, though
[16:29] <jam> especially since "groupcompress" order is close enough
[16:30] <GaryvdM> jam: did you start on caching code?
[16:31] <jam> GaryvdM: I was working on refactoring PackCollection to make it easier to define an arbitrary cache
[16:31] <jam> but that hasn't fully panned out
[16:32] <GaryvdM> Ok
[16:32] <GaryvdM> jam: Thanks for all the info. Let me now try digest all of it :-)
[16:32] <GaryvdM> And the code.
[16:35] <jam> vila: your code has landed! Does that mean pqm is working again/
[16:35] <jam> ?
[16:35] <hrw> hi
[16:35] <vila> jam: yeah ! Yes. Hi :)
[16:36] <GaryvdM> jam: Thanks for the merge review.
[16:36] <vila> jam: I just followed up on ML, you're too fast :D
[16:36] <hrw> http://hrw.pastebin.com/erWV8eRM is what I got with bzr-fastexport - any ideas what is wrong?
[16:38] <GaryvdM> hrw: My initial *guess* is that you maybe have a old version of python-fastimport.
[16:39] <hrw> GaryvdM: python-fastimport 0.9.0~bzr293-1, bzr-fastimport 0.9.0+bzr279-1
[16:39] <hrw> GaryvdM: natty packages
[16:39] <GaryvdM> Ok
[16:40] <hrw> bzr 2.3.0-beta2
[16:42] <hrw> GaryvdM: I do not know - maybe they should match
[16:42] <hrw> hi zyga
[16:43] <zyga> hrw, hi
[16:43] <zyga> hrw, ask :)
[16:43] <GaryvdM> hrw: The bzr rev numbers? I dough it.
[16:43] <hrw> zyga: if you want... http://hrw.pastebin.com/erWV8eRM is what I got with bzr-fastexport - any ideas what is wrong?
[16:43] <GaryvdM> *doubt
[16:44] <zyga> hrw, from the top of my head, either bzr or git/python wrapper version mismatch
[16:46] <hrw> GaryvdM: I think I found. need to check a bit more first
[16:47] <hrw> rev279 moved lot of code to python-fastimport from bzr-fastimport
[16:47] <GaryvdM> hrw: I think you may have manually installed a version to /usr/lib/python2.6/dist-packages/bzrlib/plugins/
[16:49]  * zyga has ath9k issues again :
[16:49] <GaryvdM> The file that the error occurs in no longer exists (bzr_exporter.py)
[16:49] <hrw> GaryvdM: http://hrw.pastebin.com/scwJcFU1
[16:50] <GaryvdM> Sorry - That's is where apt-get put it
[16:52] <hrw> I am not too familiar with python-support/central and how they handle
[16:52] <GaryvdM> Yes - Sorry - I was way off
[16:55] <zyga>  hrw python-support does some things but essentially puts the source in /usr/share/pyshared and byte-compiled version in some other place, per installed and compatible interpreter
[16:57] <hrw> fixed
[16:57] <GaryvdM> hrw: It seems like it is fixed in rev 282 of bzr-fastimport.
[16:58] <GaryvdM> hrw: how?
[16:59] <hrw> GaryvdM: r282 fixed problem indeed but one more left
[16:59] <hrw> ah. second is fixed in r384
[16:59] <hrw> 284
[16:59] <hrw> GaryvdM: from fastimport import helpers as helpers2
[17:00] <hrw> and then s/helpers.binary_stream/helpers2.binary_stream
[17:00] <hrw> and same with helpers.single_plural
[17:06] <hrw> ok, tomorrow will check bzr fast-import
[17:06] <hrw> fixes from r282/284 allowed me to do "git bzr clone" - "git bzr push" fails in other way
[17:09] <hrw> have a nice rest of day
[17:18] <GaryvdM> Bla - bzr-pipeline,  locations.conf with appendpath policies, and bzr-pqm don't play nicely.
[17:24] <GaryvdM> Hmm - Not sure why, but my bzr-pqm sends duplicate mails.
[17:27] <vila> GaryvdM: yeah, just notice that, you were so missing pqm that you had to double submit ? :D
[17:32] <fullermd> Oh no, vila's talking to nobody again.  Get the straitjacket...
[17:32] <vila> damn, missed the bear
[17:33] <vila> nooooo, not a typo for beer
[17:44] <mgz> rawr.
[19:53] <jam> GaryvdM: I did a basic review of your loggraphviz branch. Please ignore  the first email, it was sent before I finished the writeup.
[19:53] <GaryvdM> jam: ok - Thanks
[19:54] <jam> also, you don't have to take things I've said as "gospel".
[19:54] <jam> Its meant to be some feedback on how you have things structured, but I'd like it to be more of a conversation.
[20:53] <poolie> hi jam
[20:54] <jam> hi poolie
[20:55] <jam> didn't expect to see you on Sat
[20:56] <jam> wait, still Fri for you, right?
[20:56] <poolie> yes, it is
[20:56] <poolie> pretty sure
[20:58] <poolie> how are things with you?
[20:59] <jam> poolie: pretty good. Still a bit unhappy with the lp-serve stuff
[20:59] <jam> I can't reproduce production locally to make sure I get everything working right
[20:59] <jam> but tom works on it at 3am my time
[20:59] <jam> so it is 1 incremental change every 24 hrs
[20:59] <poolie> yuk
[20:59] <jam> but, at least it is something
[20:59] <poolie> why can't we assign someone in your tz?
[21:00] <poolie> actually shall we take this to lp-dev?
[21:00] <jam> sure
[21:00] <jam> -dev or -ops
[21:19] <poolie> vila: still up?
[22:19] <GaryvdM> Hi poolie
[22:31] <peitschie> mornin all
[22:31] <GaryvdM> Hi peitschie
[22:31] <peitschie> hi GaryvdM :)
[22:51] <poolie> hi GaryvdM, peitschie
[22:59] <peitschie> hi poolie :)
[23:29] <szim90> Hi. I've been deciding between version control systems (I'm a solo developer that has gotten sick of saving things as rev1,rev2, etc). I've been reading up on the options, and I've narrowed it down to git and bzr. I wanted to ask, are the advantages mentioned on "Why Switch to Bazaar" still valid if I'm comparing a stand alone bzr install to a stand alone git install (speed and efficiency, etc)? Also, does bazaar have anything like svn's missing
[23:31] <dash> szim90: anything like svn's what?
[23:31] <maxb> For a solo developer, the choice between git and bzr will mainly rest on which philsophy and UI you prefer
[23:33] <szim90> dash: svn's obliterate feature (it's something they say they have been working on for ever - it enable you to undo a commit completely, so if you accidentally included proprietary information, or (in my case), a 120mb binary, you can remove it without taking down the entire database and filtering manually).
[23:34] <exarkun> If you're like most normal human beings, you'll probably prefer bzr's UI though, at least while you're climbing the learning curve.
[23:34] <exarkun> (but gosh git is fast)
[23:34] <szim90> maxb: I suppose I can test the UIs, but how would you describe the differences in philosophy.
[23:35] <maxb> Well, one interesting point is that Bazaar tracks the identity of files - so if you rename/move one, it stores that directly.
[23:35] <dash> szim90: right, bzr doesn't have that either
[23:35] <maxb> Whereas git tracks content, and guesses file moves based on seeing blocks of content move from one file to another
[23:35] <dash> szim90: like exarkun, i think git's user interface is more than a little confusing. :)
[23:36] <maxb> Me three.
[23:37] <szim90> Well, since it's more for personal use, less confusing is definitely good! Regarding files, though, I remember reading that git trees are stored as data in .git and as data themselves (so when you clone, you then have to check out your own database to regen files). Does bzr work like this, or is it more like svn where files act like real files?
[23:38] <maxb> szim90: Erm, I'm afraid I understand git and svn and bzr really quite well, but I really don't understand your question.
[23:40] <szim90> Fair enough, I really could have worded that better. What I meant was, I was told that if I wanted to copy a git tree (like a local directory with project data), the copy action wouldn't copy files, just the database. So I would have to checkout files after making a copy.
[23:43] <maxb> That depends on what you mean by 'copy'
[23:44] <maxb> Obviously if you copy a git or bzr tree with OS tools, you end up with the same files in the destination as the source.
[23:45] <maxb> It's possible what was meant was that if you push a git or bzr tree over the git or bzr wire protocols, that does not create a working tree on the server
[23:47] <szim90> yes. That's what I wanted to check. My concern is that if I transfer a bzr tree to another server over ssh (something I read bzr was capable of doing), and the other system did not have bzr, then I would be stuck without a working tree on the server unless I transfered the files manually.
[23:48] <maxb> well, yes?
[23:48] <dash> szim90: sure. for that you want to use tar or rsync or something
[23:49] <dash> there's an 'rspush' bzr plugin that will do that.
[23:50] <mwhudson> or bzr upload, for a different kind of use case
[23:51] <dash> that one i haven't seen
[23:52] <szim90> Perfect! Thanks. I just need to make sure the work is accessible in the event I end up on a work station that isn't mine. I believe that answers all my questions. Thanks you for all of your help; I'll try bzr out when I get back to my system.


[02:57] <JotaMG> hi!!
[02:57] <JotaMG> anyone??
[02:57] <phillw> JotaMG: ??
[02:57] <JotaMG> I have a simple question...
[02:58] <phillw> !ask
[02:58] <JotaMG> I'm new to Lubuntu... lxde can restore the previous session, like Kde, for instance
[02:59] <JotaMG> I mean, for instance, the terminal window, the file manager window, just like they are when logout
[03:00] <JotaMG> can I have them restored when I login next time??
[03:00] <phillw> for terminal, that should be saved in the history.
[03:00] <phillw> are you referring to http://forums.opensuse.org/english/other-forums/development/programming-scripting/477708-manually-saving-restoring-kde-sessions.html
[03:00] <phillw> ?
[03:01] <JotaMG> no no mannualy... I mean automatically when logout
[03:01] <JotaMG> and restore next time when login
[03:02] <JotaMG> I google a little and LXDE session is supposed to do that by on my Lubuntu install that does not happen
[12:46] <david> hello
[12:47] <david> can anyone help me uninstall lubuntu 12.10 so i can access my windows xp install
[17:56] <Micky1> Salve a tutti
[17:57] <wxl> uhhh
[17:57] <wxl> !it
[17:57] <Micky1> ho un problema con Lubuntu 12.04 x64
[17:57] <wxl> sorry we're english only here, Micky1
[17:57] <Micky1> sorry I think that this was only for italian language
[17:58] <Micky1> I'll try to explain my problem in english
[17:58] <wxl> no you can try #ubuntu-it if we can't help
[17:58] <Micky1> when I log in to Lubuntu the screen become black
[17:59] <wxl> can you get to a tty? try ctrl-alt-f1 (and ctrl-alt-f7 to get back)
[17:59] <Micky1> I'm able to access in ssh
[18:00] <Micky1> it's the same ?
[18:00] <wxl> not necessarily
[18:00] <wxl> though it does imply your system is working, just not the display
[18:01] <wxl> what graphics card do you have? you can use lspci -v to see and also find out what kernel module is being used with it
[18:01] <Micky1> the PC is not accessible because the screen is like in energy saving
[18:02] <Micky1> it's a server machine
[18:02] <Micky1> I think it's an Intel Graphic VGA board
[18:02] <wxl> i need to know exactly which is why i suggested lspci -v
[18:04] <Micky1> http://pastebin.com/dKEq8x69
[18:04] <Micky1> this is the output of your command
[18:05]  * Unit193 wonders why a server would have Lubuntu.
[18:05] <Unit193> ATI ES1000.
[18:05] <wxl> yep
[18:05] <wxl> using radeon
[18:06] <Micky1> because I use it to virtualize with Virtualbox and Lubuntu consume less resource than Ubuntu
[18:07] <wxl> having trouble fiding info on this but looking
[18:07] <Micky1> sorry for my network problems
[18:08] <Micky1> do you think that could be a video card problem ?
[18:08] <Unit193> wxl: Right, so it should be using xserver-xorg-video-ati and not xserver-xorg-video-radeon right?  Know what'd happen if you'd purge the second?
[18:08] <wxl> absolutely certain of it
[18:09] <wxl> Unit193: well, that's what i'd suspect, but you never know. seen a lot of ati issues lately
[18:09] <Micky1> no
[18:09] <Micky1> I googled before come here and I runned this command: cat .xsession-errors
[18:10] <Micky1> this is the result:
[18:11] <Micky1> http://pastebin.com/ExZPk54p
[18:13] <phillw> Micky1: try ssh -X into the server (this will allow an 'X' session to run)
[18:14] <Micky1> you mean from the server machine ?
[18:14] <phillw> ssh -X onto the server
[18:15] <Micky1> (@phillw)
[18:15] <Micky1> I can't because the screen result in energy saving
[18:16] <phillw> it does not matter about the screen on the remote server, or even if it has a screen.
[18:16] <Micky1> and I'm not able to see nothing
[18:17] <phillw> when you are ssh'd in.
[18:17] <phillw> do you see a output for, say, ls ?
[18:18] <Micky1> Now I attached a screen to it
[18:18] <Micky1> the problem is that if I reboot the machine the screen will power on
[18:18] <Micky1> when I make the login the screen goes in energy saving mode
[18:18] <phillw> on the machine you are ssh'ing up FROM?
[18:19] <Micky1> but until the login I'm able to see everything
[18:19] <Micky1> mouse, login GUI
[18:22] <phillw> I'm just putting ssh onto a lubuntu desktop machine, bear with me.
[18:23] <Micky1> anyone has suggestion ?
[18:25] <phillw> I don't, I ssh -X into my remote server several times a day.
[18:26] <Unit193> Micky1: This issue with Ubuntu as well?
[19:19] <PH5> hey, what software can i use to put Ubuntu on a USB drive?
[19:24] <genii-around> PH5: usb-creator-gtk
[19:24] <genii-around> "Startup Disk Creator"
[19:25] <PH5> can i get it from the terminal?
[19:30] <genii-around> Yes
[19:30] <genii-around> PH5: eg: sudo apt-get update && sudo apt-get install usb-creator-gtk
[19:32] <PH5> thanks i will try it now
[19:45] <PH5> it didn't work, it said " Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?"
[19:46] <holstein> PH5: run sudo apt-get update and report errors
[19:48] <PH5> Some index files failed to download, they have been ignored, or old ones used instead.
[19:48] <holstein> PH5: i would work out your package errors
[19:49] <PH5> genii-around: any other software?
[19:49] <holstein> PH5: sure
[19:49] <holstein> PH5: but the issue is with your packages
[19:50] <PH5> ok
[19:50] <holstein> you can tyr sudo apt-get install unetbootin
[19:50] <PH5> no
[19:50] <holstein> but, you will likely have the same errors, since you have broken something with maybe a PPA, or a bad source
[19:50] <holstein> PH5: no?
[19:50] <holstein> no what?
[19:50] <holstein> you wont try unetbootin?
[19:51] <holstein> either way, you'll want to troubleshoot your package issues
[19:51] <PH5> no i haven't try it yet
[19:52] <PH5> oh i see
[19:55] <PH5> i am sure firefox will give me a different result
[19:56] <holstein> PH5: ?
[19:56] <holstein> PH5: you mean, installing firefox?
[19:56] <holstein> PH5: unetbootin is a tool for creating USB drives.. but that is not the issue you are having
[19:56] <holstein> you have a broken package system.. you can run "sudo apt-get update" and we can troubleshoot them
[19:57] <PH5> no i say i will try getting it from firefox
[19:57] <holstein> PH5: doesnt matter where you get it from.. your system is broken
[20:02] <PH5> brb
[20:04] <genii-around> They seem to have a comprehension problem.
[20:04]  * genii-around slides phunyguy a coffee
[20:05] <holstein> eh.. it might be a windows user.. not used to package management...
[20:05] <phunyguy> sorry, messin with some stuff
[20:06] <phunyguy> and thanks
[20:06] <phunyguy> :P
[20:08] <genii-around> phunyguy: Anytime. I actually didn't realize how many of the same channels we're in until I saw you rejoin all of them...
[21:16] <Micky> Hi al
[21:16] <Micky> about my problem of screen after the login
[21:17] <Micky> now I'm able to connect to it with CTRL + ALT + F1
[21:17] <Micky> how can I solve my problem from prompt ?
[21:17] <holstein> Micky: i have no idea what you are talking about.. but i would just make a new user and test
[21:18] <holstein> OR, you can remove parts of your /home directory related to your config
[21:18] <holstein> if your login is normal as the other user, its safe to assume the issue is in the /home directory of your other user
[21:18] <holstein> you can then, remove or rename things til you get it
[21:19] <Micky> Oh sorry, my problem is that I can't use my PC because after the login (with a GUI) the screen seems to go in power saving mode
[21:19] <holstein> Micky: i would try as another user
[21:19] <Micky> ok I will try
[21:19] <holstein> if the issue is the same as the other user, i would make a custom xorg.conf and set the vesa driver
[21:21] <Micky> yes with another user it is able to log in
[21:22] <holstein> Micky: so, i would just move the ~/.config to start with.. log in as the offending user and test
[21:22] <holstein> then, you can put back what you need.. til it breaks again... or just start over
[21:23] <Micky> can I only rename ~/.config in i.e. ~/.config.old ?
[21:24] <holstein> Micky: that should work fine
[21:24] <holstein> Micky: i usually name it something without a dot and move it out of there
[21:24] <holstein> but thats just so i can find it
[21:25] <Micky> ok I'm tryong
[21:30] <Micky> now it works, great !
[21:30] <Micky> thanks very much
[21:30] <Micky> holstein
[21:35] <holstein> Micky: cheers!
[22:35] <morgan> hi
[22:35] <morgan> can somebody help me with changing the keyboard layout_
[22:37] <morgan> I tried lxkeymap, but on the next reboot
[22:37] <morgan> it is reset to english layout
[22:39] <phillw> hi morgan, it is known bug 1068968 that is being worked on
[22:40] <phillw> please feel to subuscribe to that bug report as 'affects me', so that you receive updates on its progress.
[22:41] <morgan> can I set this via terminal as global_
[22:43] <phillw> reading through the bug, there does seem to be an update available... let me have a bit of a dig on where it is.... it may be a few minutes.
[22:46] <phillw> morgan: can you check which version of lxkeymap you have installed?
[22:47] <morgan> yes
[22:47] <morgan> Lxkeymap 0.7.99
[22:50] <phillw> morgan: there seems to be an update available from the lubuntu devs, if you'd like to try it out?
[22:53] <phillw> morgan: how would you describe your understanding of using terminal for such things as apt-get?
[22:55] <morgan> how should I install this version_ if I can change the the language via terminal on global settings it would be enough
[22:55] <morgan> I tried sudo dpkg-reconfigure keyboard-configuration
[22:56] <morgan> but nothing changed
[22:58] <phillw> you will need to temporarily enable the dev area to get the latest version.
[22:59] <phillw> morgan: the background for doing this is at https://wiki.ubuntu.com/Lubuntu/Testing/PPA_Testing but I'm more than happy to talk you though it once you have understood the general idea.
[23:45] <morgan>
[23:46] <morgan> phillw which ppa link I need to add? I can not see the link for LXKeymap
[23:48] <phillw> morgan: you need to head over to https://launchpad.net/~lubuntu-dev/+archive/staging (Do not worry about the warnings on that wiki page, our dev staging area is safe!).
[23:53] <morgan> I add the ppa and updated the repo
[23:53] <morgan> but there is no newer version
[23:55] <phillw> morgan: I suggest you raise a new bug (ubuntu-bug lxkeymap) and include the comment pointing it back to bug 1068968
[23:56] <phillw> Ley me know the new bug number and I'll give a gentle 'dig' to the team to ask if any progress has been made.
[23:56] <phillw> s/Ley/Let
[23:57] <phillw> include that you have used the staging ppa and the problem still exists.
[23:58] <phillw> morgan: cancel that!
[23:58] <phillw> I mis read the bug status, it is fix-commited, not fix-released.
[23:59] <phillw> log onto https://launchpad.net/bugs/1068968 then click affects me, then in comments add that you have tried the lxkeymap from ~staging.


[12:19] <PTO> Im trying to use MAAS on an IBM Bladecenter H, and when a node enlist in MAAS, the power IPMI configuration gets an internal IP <IP_ADDRESS> of the blade. How do I get around this in MAAS? Should I specify the AMM module IP instead or try to route the chasis internal network on the LAN?
[12:44] <parlos> @PTO I'm about to embark on a similar path; (same bladecenter). Does the MAAS correctly detect the blade?
[13:27] <roaksoax> PTO: maas can only manage machines inside the blade, not the blade itself
[13:27] <roaksoax> parlos: ^^
[13:30] <parlos> roaksoax, hrm, so the normal way to commision will be problematic (as that needs power control).
[13:33] <roaksoax> parlos: right, well maas will need to communicate directly to the machines. That said, I thought that was possible in these blades ? is it not ?
[13:33] <parlos> roaksoax I hope so..
[13:33] <parlos> Have to do a bit of RFTM then :)
[13:38] <parlos> I was quietly hoping that the MAAS 'detection' image (ie. the PXE booted kernel) would be smart enough to detect the BMC on the blade when it booted..
[13:44] <roaksoax> parlos: well there's no way for the machine to detect the blade, unless maas specifically supports the balde and you tell maas that there's a blade (in which case maas would discover the machines inside the blade)
[13:47] <parlos> roaksoax; the terminology Im used to is that a (IBM flavoured i guess), is: BladeCenter hosts blades, the blades are complete computers (cpu,mem and disc).
[13:49] <parlos> The major difference between a blade and a regular computer is the I/O connectivity.
[13:50] <parlos> However, if i compare to a 'real' device, im not sure where the BMC would be located. As, it would seem that it would be a part of the BladeCenter, not the blade it self (Cf. powering VMs)
[13:50] <parlos> However, if i compare to a 'real' device, im not sure where the BMC would be located. As, it would seem that it would be a part of the BladeCenter, not the blade it self (Cf. powering VMs via SSH)
[13:51] <PTO> roaksoax: When a blade PXE boots, it goes throught the rutines and powers off. It will enlist in mass and the power configuration is IPMI2 with the IP address <IP_ADDRESS> (blade1). To my understanding the Chassis internal Network (cin) is not accessible outside the bladecenter. Google'ing suggests that you configure the bladecenter AMM module as the IPMI host, but i cant quite figure out if this is the way to go?
[14:17] <parlos> PTO Is there an completely internal network? In my case we have two switches in the back (one active, one active-standby). But they are 'directly' connected to the blades.
[14:27] <roaksoax> so MAAS can manage machines in two ways, via a chassis or directly
[14:27] <roaksoax> via a chassis means that maas is told about a chassis and it discovers the machines inside, and power manages them via the chassis
[14:28] <roaksoax> directly, when machines have BMC's and maas can power managed them directly
[14:28] <roaksoax> we dont support bladecenter H as a "chassis" in MAAS, so to power manage the machine, we need to manage them directly
[14:28] <roaksoax> my understanding is that this is possible
[14:41] <PTO> roaksoax: How do you instruct MAAS to use the chais and not the IMM of the server?
[14:43] <roaksoax> PTO: you would need to create a new power driver
[14:56] <PTO> Bump... Thats not what i want to hear :-/
[17:01] <Charlie> Hi, would any one be able to offer some help? Just set up my first MAAS environment, added a physical node on the network MAAS looks at with DHCP/DNS. initially all looks to be ok and then it fails to commission my node.
[17:06] <Charlie> being new the MAAS, im having trouble understanding why this is failing
[17:07] <Charlie> looking in /var/log/maas/rsyslog/ for the node, I can see cloud-final.service: Main process exited, code=exited, status=1/FAILURE
[17:07] <Charlie> google tells me very little about this.
[17:11] <Charlie> Would anyone be able to assist?
[23:30] <edmz> how can I find the reason of a "Node installation failure - 'curtin' curtin command install" failed deployment?
[23:30] <edmz> this node was deployed. I decided to re-deploy and got this error.