[00:01] <apol> hi
[00:02] <apol> can someone help me with this error please?
[00:02] <apol> https://launchpadlibrarian.net/97408293/upload_3520464_log.txt
[00:02] <apol> :) << good guy face
[00:07] <apol> ó.ò
[04:39] <ScottK> fabo: libzip is all done.
[04:56] <littlegirl> Hey there, I'm probably doing pulling and committing and all that in the wrong order, and as a result I've run into a snag where my copy diverges from the one on the server. Here's what I've got: http://paste.ubuntu.com/891753/ Any help with what I should do next so that I can push my commit without messing up jjesse's commits would be appreciated. (:
[05:53] <littlegirl> Hey there, I'm probably doing pulling and committing and all that in the wrong order, and as a result I've run into a snag where my copy diverges from the one on the server. Here's what I've got: http://paste.ubuntu.com/891753/ Any help with what I should do next so that I can push my commit without messing up jjesse's commits would be appreciated. (:
[05:56] <fabo> ScottK: thanks!
[06:32] <littlegirl> Hey there, I'm probably doing pulling and committing and all that in the wrong order, and as a result I've run into a snag where my copy diverges from the one on the server. Here's what I've got: http://paste.ubuntu.com/891753/ Any help with what I should do next so that I can push my commit without messing up jjesse's commits would be appreciated. (:
[06:35] <micahg> littlegirl: bzr rebase?
[06:35] <littlegirl> micahg: I don't know what that means. (:
[06:36] <micahg> littlegirl: it's a command to rebase what you have based on the committed branch, you'll need the bzr-rewrite package, 'bzr help rebase' for more info
[06:37] <littlegirl> micahg: Will it grab the commits that someone else made to Launchpad and give them to me locally so that my copy is exactly like the one on Launchpad?
[06:37] <micahg> littlegirl: yes, and recommit yours on tops as long as you don't have conflicts in the same files
[06:38] <littlegirl> micahg: That sounds perfect. Thanks for the info. Is there any chance I'll screw things up if I use it incorrectly?
[06:39] <littlegirl> micahg: Hmmm: E: Couldn't find package bzr-rewrite
[06:39] <micahg> littlegirl: idk, I guess it's always possible, but only your local branch would be affected, I wouldn't worry as long as you pay attention to the prompt
[06:40] <micahg> littlegirl: which release are you on?
[06:40] <littlegirl> micahg: Of Bazaar?
[06:40] <micahg> Ubuntu
[06:40] <littlegirl> Kubuntu 10.04 LTS.
[06:40] <micahg> littlegirl: that's why, it's called bzr-rebase there
[06:41] <littlegirl> micahg: Installed, thanks. (:
[06:45] <littlegirl> micahg: One other thing. It says I need to know the upstream location. Would that be branch lp:kubuntu-docs which is where I originally pulled from, or would it be the parent location mentioned by bzr in the link I posted, which is  http://bazaar.launchpad.net/~ubuntu-core-doc/kubuntu-docs/precise/
[06:45] <micahg> littlegirl: one should be an alias for the other
[06:45] <micahg> yep, so either one is fine
[06:46] <littlegirl> micahg: Okay, I'm gonna try it. (:
[06:49] <littlegirl> micahg: Hmmm, not working. 
[06:49] <littlegirl> bzr rebase --dry-run --pending-merges http://bazaar.launchpad.net/~ubuntu-core-doc/kubuntu-docs/precise/
[06:49] <littlegirl> bzr: ERROR: No pending merges present.
[06:49] <micahg> littlegirl: not a pending merge :)
[06:50] <littlegirl> I tried it with the upstread address both ways.
[06:50] <micahg>  bzr rebase --dry-run lp:kubuntu-docs should work
[06:51] <micahg> or at least tell you if there are issues
[06:52] <littlegirl> micahg: That gave me no message either way. Is that good?
[06:53] <micahg> add -v
[06:53] <micahg> idr
[06:54] <littlegirl> Weehaw! http://paste.ubuntu.com/891829/
[06:54] <littlegirl> micahg: Thank you so much!
[06:55] <micahg> littlegirl: you're welcome, thank you for your work on Kubuntu
[06:55] <littlegirl> micahg: Any time. I'm trying to help get the docs in shape in time for the freeze, but these little issues get in my way and then I'm lost for a while. (:
[06:55] <micahg> littlegirl: just ask here, lots of people to help
[06:56] <littlegirl> Are you familiar with the Kubuntu docs?
[06:56] <micahg> nope :)
[06:56]  * littlegirl has a few questions. (:
[06:56] <micahg> Darkwing would be a good person, but he might be sleeping
[06:57] <littlegirl> micahg: Yeah, he's been hard to reach recently. (:
[06:57] <micahg> he was around ~8 hrs ago
[06:58] <littlegirl> Oh, I would have loved to have chatted with him!
[07:01] <littlegirl> micahg: Thank you so much for your help - that worked perfectly. I was able to get my commit in, too, which would have been sad otherwise, because that was a huge file to edit. (:
[07:03] <micahg> glad to help
[07:06] <littlegirl> Heh, I was so excited to have it working that I didn't pay attention to the command when I entered it for the push and I submitted it as branchname instead of the name of the sub-branch I was working in. (:
[07:28] <littlegirl> micahg: Do you use DocBook?
[07:28] <micahg> nope
[07:28] <littlegirl> I'll have to find a DocBook wizard at some point. (:
[07:29] <littlegirl> By the way, I wrote up the solution you gave me to my error so that if it happens again I can do it again. (:
[08:00] <Riddell> littlegirl turning into a new docs master then
[08:23] <fabo> Riddell: micahg: I need a sponsor for krename (oneiric-proposed) bug 849882
[08:23] <fabo> package available in https://launchpad.net/~fboudra/+archive/ppa
[08:24] <Riddell> fabo: looking
[08:26] <Riddell> fabo: it's not clear what's needed, is this a SRU or a backport?
[08:26] <fabo> Riddell: SRU
[08:27] <fabo> initially, I thought it was a backport. then micah told me to make a SRU for a crash
[08:27] <Riddell> fabo: so the 4.0.7-1ubuntu1  in your PPA to oneiric-proposed?
[08:27] <fabo> yes
[08:31] <Riddell> fabo: lovely, uploaded.  I had to change the maintainer to something ubuntu-ish.  please subscribe ubuntu-sru to bug 849882 and make clear you want a SRU which is in the queue now
[08:31] <fabo> thanks
[08:32]  * fabo should fix his devscripts conf
[11:20] <shadeslayer> Riddell: could you upload bug 958683 as well?
[11:21] <Riddell> shadeslayer: as well as what?
[11:21] <shadeslayer> uh, I saw you uploaded a SRU fix earlier
[11:21] <shadeslayer> which is why the "as well"
[11:23] <Riddell> gotcha
[11:24] <shadeslayer> thanks
[11:25] <Riddell> shadeslayer: have you tested this?
[11:25] <Riddell> shadeslayer: do you have a simple test case?  that needs added to the bug
[11:26] <shadeslayer> I haven't but someone else did, leme get the nick
[11:26] <shadeslayer> DoctorPepper
[11:26] <shadeslayer> hmm ... he isn't around
[11:27] <Riddell> shadeslayer: got a real name or e-mail for Pepper?
[11:27] <shadeslayer> Steps to Reproduce:
[11:27] <shadeslayer> 1. create a folder "测试" and a empty file in it.
[11:27] <shadeslayer> 2. set option display parent folder in dolphin's information panel.
[11:27] <Riddell> shadeslayer: oh cool, where's that from?
[11:29] <shadeslayer> from the KDE Bug report
[11:29] <shadeslayer> see bug 858970
[11:30] <Riddell> shadeslayer: you're probably better not to start a new bug in this sort of case, that just makes it harder for people to find out the back story
[11:30] <Riddell> shadeslayer: please add those steps to the SRU bug report along with a failed and succcessful outcome
[11:30] <shadeslayer> oh ... so I should set the title of that bug as SRU?
[11:31] <shadeslayer> or should we proceed with the new bug now that I've already filed it
[11:31] <Riddell> we'll just stay with the new one for now
[11:31] <shadeslayer> cool
[11:32]  * shadeslayer adds new info
[11:33] <shadeslayer> as for a email for Pepper, nope, but he's usually around in the evenings
[11:34] <Riddell> "Uploaded to oneiric-proposed, awaiting approval from ubuntu-sru"
[11:34] <Riddell> thanks for that shadeslayer 
[11:34] <Riddell> remember to test it again once ubuntu-sru do approve
[11:35] <shadeslayer> sure will do
[11:41] <shadeslayer> !find hlibrary.mk
[12:17] <Whiskey`Wonka> hello. im being told to come here for support with a couple issues, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651748 being one
[12:17] <Whiskey`Wonka> and i have not found the bug # for the other (its mentioned in that one) about having to manualy track down package depends
[12:19] <Riddell> Whiskey`Wonka: I'm afraid aptitude isn't supported by us, we do KDE
[12:19] <Riddell> it's not supported by any team in ubuntu as far as I know
[12:19] <Whiskey`Wonka> yea i figured
[12:19] <BluesKaj> hiyas all
[12:19] <Whiskey`Wonka> so what package system DO you support
[12:20] <Riddell> Muon
[12:20] <Whiskey`Wonka> >.<
[12:20] <Riddell> and in ubuntu generally  apt
[12:20] <Whiskey`Wonka> ap-get is borked too
[12:20] <Whiskey`Wonka> as is muon
[12:20] <Whiskey`Wonka> but muon is far better today then 6mo ago, so yay
[12:22] <Whiskey`Wonka> can we somehow get better errors then 'libqt4-opengl could not be marked for isntallation or upgrade' when /its already installed/
[12:23] <Whiskey`Wonka> i guessing its a depends issues (thats what has led me here to begin with)
[12:23] <Whiskey`Wonka> but no other details to fix it then 'can not be marked'
[13:21] <Riddell> afiestas: 13:11 < janimo`> slangasek, Riddell the acpi-support changelog mentions dropping power.sh when kubuntu starts using upower, not sure if that is the case, it is an old comment
[13:21] <Riddell> 13:14 < slangasek> janimo`: power.sh should definitely go away if kubuntu is using upowerd now
[13:21] <Riddell> afiestas: in #u-d I presume it uses upower now?
[14:55] <Riddell> li
[14:55] <Riddell> tsk
[15:13] <apol> hi
[15:13] <apol> does anybody know where "software-properties-kde" comes from?
[15:14] <Riddell> apol: I wrote it :)
[15:14] <apol> yay
[15:15] <apol> Riddell: I'm considering working on some UI for muon-installer-qml to be able to add/remove/list sources
[15:15] <Peace-> Riddell: :)
[15:15] <Riddell> apol: cool
[15:15] <Riddell> apol: well it's there for the taking, it hasn't been touched in some years
[15:15] <apol> Riddell: is there any way we can share code with software-properties-kde?
[15:16] <Riddell> apol: yes, software-properties-kde is just one GUI and software-properties-gtk is another
[15:16] <Riddell> so you can certainly make a third with QML
[15:16] <Riddell> although you'd need to work out the best way to integrate QML with PyQt, bulldog98_ has been looking at that
[15:16] <apol> Riddell: yes, but the idea was to do it in-process
[15:17] <Riddell> that's more tricky then
[15:17] <apol> is this a library?
[15:17] <Riddell> no it's a python app, and there are some shared classes between the kde and gtk UIs but no defined API
[15:17] <apol> I see
[15:18] <Riddell> you could port it to use policykit
[15:18] <Riddell> and make a dbus API
[15:18] <Riddell> then get muon-mobile to talk to that
[15:18] <Riddell> but that's effort
[15:18] <bulldog98> apol: problem with PyQt is, that you can only insert QObjects into the qml context, no QDeclarativeItems possible
[15:19] <Riddell> bulldog98: what does that mean in terms of ability to use PyQt with QML?
[15:19] <apol> bulldog98: that shouldn't be a stopper, never needed this :P
[15:20] <bulldog98> Riddell: you can use pure qml and use slots and signals to connect, but it’s not possible to write a new Item, e.g. a keyboardview
[15:20] <bulldog98> apol: for the installer that would be a good thing to have ^
[15:21] <apol> m?
[15:21] <apol> why?
[15:21] <apol> the keyboard is usually provided by the OS
[15:21] <apol> we're not talking about a mobile app anyway
[15:22] <bulldog98> apol: it’s a view to show the current keyboard layout
[15:23] <apol> I don't know what you're talking about then
[15:23] <Riddell> apol: he's been looking at changing our ubiquity installer into QML, it has a page which shows the keyboard layout you have selected
[15:23] <apol> ahhh
[15:24] <apol> i was thinking of something different when you said installer, sorry
[15:24] <bulldog98> apol: code is at kde:scratch/kolberg/ubiquity-mockup
[15:24] <apol> in that case you can do different things, you can create a c++ qml plugin just for that component
[15:24] <apol> which would be really easy
[15:25] <bulldog98> apol: which is what I did
[15:25] <apol> if you don't want to compile anything, you'll have to reimplement it in QML, which shouldn't be that hard either
[15:25] <bulldog98> apol: but I had to port the python code to c++
[15:25] <apol> but then you'll have to feed it to QML
[15:25] <apol> note that QML is thought in a way so that all painting is done by QML
[15:26] <apol> so consider the c++ plugin a hack ;)
[15:27] <bulldog98> apol: still it works quite good :P
[15:27] <apol> ;)
[15:28] <sreich> qml qml qml qml ;p
[15:29] <Riddell> Qt Quick!  qml is just an implementation detail :)
[15:30] <sreich> well i can't very well say Qt Quick 4 times fast, can i? :)
[15:31] <Riddell> sure you can, it's only two syllabols, QML is three
[15:52] <tsdgeos> Riddell: QML is two too
[15:53] <tsdgeos> you say "kyu- mel"
[15:53] <tsdgeos> not "kyu - em - el"
[15:53] <Riddell> I've never heard it pronounced like that
[15:53] <Riddell> these crazy Qt people pronouncing things in unintuitive ways
[15:55] <sreich> haha yeah
[16:04] <afiestas> Riddell: yes we use upower since 4.6 I think
[16:04] <afiestas> didn't know about the power.sh thing, sorry :/
[16:04] <Riddell> afiestas: lovely thanks
[16:12] <Riddell> ok who broke kubuntu-active?
[16:12] <Riddell> the package doesn't depend on anything
[16:14] <Riddell> debfx: ever feel like you're being watched? http://www.phoronix.com/scan.php?page=news_item&px=MTA3MjI
[16:18] <Riddell> Michael Larabel are you here?  do you just sit in IRC channels waiting for gossip to come your way?
[16:18] <apol> yes... I saw that, quite weird... :P
[16:24] <sreich> lol
[16:24] <Peace-> vnc
[16:27] <micahg> Riddell: fabo: technically, the krename SRU should've been versioned 4.0.7-1ubuntu0.1
[16:31] <ScottK> micahg: There's not a firm policy on SRU versioning beyond collision avoidance.
[16:31] <micahg> ScottK: since when?
[16:32] <ScottK> Since forever.
[16:32] <Riddell> the page just says "pick a version number" but I agree adding .1 is the best way
[16:32] <ScottK> People generally sort of follow the security guidelines, but there's no requirement to do so.
[16:32] <ScottK> Nor is there any reason to have a more firm requirement.
[16:32] <maco> following the security guidelines is what ive been told is good practice
[16:33] <micahg> hmm...ok, I stand corrected :), it does say it's a well working scheme, but not required
[16:33] <maco> you wont be thrown in the stocks for not doing so, but your sponsor might FTFY
[16:33] <micahg> the advantage though is that it's clear it's an SRU and not a regular release upload
[16:33] <Riddell> micahg: FTFY?
[16:33] <micahg> *dev release
[16:33] <maco> Riddell: Fix That For You
[16:34] <sreich> kids and their acronyms..
[16:34] <Riddell> maco: sorry wrong tab completion :)
[16:34] <Riddell> sreich: I think geeks are just as guilty as youngsters in using acronyms
[16:34] <sreich> :)
[16:35] <maco> when someone quotes another person in an online discussion and thinks they got something not quite right, or not strongly enough, they might adjust the quote and say "FTFY" as their text below, though in that case its past-tense 'fixed'
[16:35]  * micahg will stop getting so bent out of shape about versions
[16:35]  * jalcine adds ftfy into his book.
[16:36] <Riddell> jalcine: no!  rebel and use full words!
[16:36] <maco> i think itd be *nice* to firm up the policy on version numbers, and the security method is nice to avoid collisions with next-dev-version
[16:36] <jalcine> :P I'm a youngster, it's what I do.
[16:36] <jalcine> Sometimes things get tl;dr
[16:36] <maco> jalcine: tl;dr amuses me in that its now morphed, among some people into "Teal Deer: "
[16:37] <sreich> so instead you have a book of filled with acronyms?
[16:37] <maco> "Teal Deer: they got away"
[16:37] <sreich> isn't that, in itself, tl;dr?
[16:37] <sreich> irony?
[16:37] <jalcine> O.O lol
[16:38] <debfx> Riddell: yeah seems like phoronix is becoming an irc log dumping ground in addition to the benchmark graph spam
[16:38] <jalcine> D:
[16:38] <jalcine> he notices the fallacies!
[16:42] <Riddell> I can never remember what tl;dr is, does it mean I'm getting old if I don't know all the acronymns?
[16:42] <Riddell> hi jalcine, I don't think we've met, pleased to meet you
[16:43] <jalcine> hey Riddell :)
[16:43] <jalcine> The pleasure's mine :)
[16:43] <jalcine> I typically hang here and help when I can, otherwise just observing. :)
[16:44]  * jalcine looks at all of the smilies.
[16:44] <ScottK> Riddell: I know that one.  Old isn't your problem ...
[16:44] <jalcine> That's how you don't get a job
[16:45] <tsdgeos> Riddell: too long, didn't read
[16:47] <Riddell> tsdgeos: too late, I stopped reading this conversation some lines ago :)
[18:35] <shadeslayer> ScottK: I can haz access to ARM boxen?
[18:36] <shadeslayer> Need to testbuild a new patch from digikam upstream
[18:55] <ScottK> Yes.
[18:55] <ScottK> shadeslayer: Where's your ssh public key?
[18:55] <shadeslayer> ScottK: https://launchpad.net/~rohangarg/+sshkeys
[19:11] <yofel> can someone with a proprietary graphics driver try to reproduce bug 959031? I'm not sure what to blame
[19:21] <yofel> apachelogger: are you going to upload your new plymouth and ksplash? If yes, someone needs to change the default KDM background to match that
[19:24] <debfx> blaming the graphics driver is usually right
[20:30] <debfx> yofel: I found a workaround for that oxygen-gtk3 bug
[20:32] <yofel> oh?
[20:34] <debfx> yofel: http://pkgs.fedoraproject.org/gitweb/?p=oxygen-gtk3.git;a=commitdiff;h=13f9165ca9a8392dd674dd3db85398636b949796
[20:34] <debfx> seems to be a bug in gtk3
[20:35] <yofel> kde bug 295831
[20:36] <yofel> debfx: thanks for finding that
[20:38] <debfx> and uploaded
[20:38] <yofel> \o/
[20:58] <ScottK> debfx: Quassel 0.8.0 is out.  Do you want to do your apparmor changes now too?
[20:59] <debfx> ScottK: I've uploaded those already
[20:59] <ScottK> Ah.  OK.
[20:59] <ScottK> I'll do 0.8.0 then.
[21:01] <debfx> Sput: how about merging my ssl certificate patches now? :)
[21:04] <Sput> debfx: what was that again?
[21:04] <Sput> should those have gone int 0.8.0?
[21:04] <debfx> Sput: http://bugs.quassel-irc.org/issues/1109 and http://bugs.quassel-irc.org/issues/1110
[21:05] <Sput> meh, someone should have mentioned those or created MRs for those :/
[21:05] <Sput> (you probably did mention those, but my brain is not capable of storing such things)
[21:08] <debfx> I think I pinged you when I posted them but that was a few month ago
[21:09] <Sput> debfx: yeah, I was way too busy the past year (still am), so everything that wasn't turned into a merge request at gitorious slipped past me pretty much
[21:09] <Sput> and our good triagers probably missed those patches as well
[21:10] <Sput> anyway, there will be e 0.8.1 :)
[21:12] <debfx> yay :)
[21:15] <ScottK> debfx: Should we take those as distro patches?
[21:19] <Riddell> kubuntu active on arm! http://starsky.19inch.net/~jr/tmp/DSCF6658.JPG
[21:20] <ScottK> Ship it.
[21:20] <debfx> ScottK: yes, if Sput approves them
[21:20]  * ScottK looks at Sput
[21:22] <Sput> just glanced at them, haven't tested (and don't know too much about the stuff), but I assume you did the testing already
[21:23] <Sput> and codewise looks fine to me
[21:24] <Sput> I don't think I have a way to actually test the chained ca stuff, so I'll have to trust you :)
[21:25] <debfx> yeah I've tested them against 0.7 but it seems like the ssl code hasn't been touched since then
[21:25] <Sput> no, we didn't touch that
[21:27] <Riddell> http://blogs.kde.org/node/4546  Kubuntu Active on ARM
[21:29] <Sput> debfx: Tucos was nice enough to turn your patches into MRs, so they won't get lost in the future :)
[21:32] <ScottK> debfx: I've got a test build going without your patches, but if you've got time to do it, please go for it (I have to leave for awhile soon).
[22:22]  * ScottK does it.
[23:05] <micahg> ScottK: debfx: re quassel and the core using expired certs, is that the default or an option?