[02:07] <ScottK> shadeslayer: You've got kde-workspace FTBFS to look at.
[07:30] <Peace-> #bash
[07:33] <apachelogger> #zsh
[07:43] <debfx> #nologin
[08:28] <shadeslayer> ScottK: *grumble* arm *grumble*
[08:40] <shadeslayer> apachelogger: Riddell I talked with cj last night a bit, he asked me to email ubuntu-devel/release requirements for Kubuntu next
[08:56] <Riddell> shadeslayer: I'm wondering if we really want to use the PPA, there doesn't seem to be much advantage over the archive
[08:56] <shadeslayer> Riddell: sure there is
[08:56] <Riddell> what's that?
[08:56] <shadeslayer> Riddell: by having the PPA enabled OOTB we can keep up with plasma 5 releases
[08:57] <shadeslayer> and KF5 releases
[08:57] <shadeslayer> since we cannot land those in the archive
[08:57] <shadeslayer> which is helpful for upstream
[08:57] <shadeslayer> I think that's the big point of having the PPA enabled OOTB
[08:57] <shadeslayer> quick feedback for upstream to iterate and improve plasma 5 quickly
[08:58] <Riddell> that's assuming we stay on utopic indefinately
[08:58] <shadeslayer> you don't plan to abandon utopic as soon as it's released right? :P
[08:59] <Riddell> dunno, we stopped updating trusty soon with kf5 stuff, if you want crack of the day you have to live with updates
[08:59] <Riddell> otherwise we'll be packaging beta stuff for multiple releases which I'm not sure we have the peoplepower for
[09:00] <apachelogger> ^ packaging for multiple releases should be equal to packaging for one release and then running a script, if it is not then the process is flawed
[09:00] <Riddell> apachelogger: then why are you against packaging for 12.04LTS?
[09:01] <shadeslayer> Riddell: right, why did we stop packaging KF5 for trusty?
[09:01] <apachelogger> shadeslayer: qt
[09:01] <apachelogger> Riddell: because policy
[09:02] <apachelogger> I wasn't against packaging 4.13 for precise, I was against packaging .0 knowing that the policy would then tell us not to package .1 and .2 and .3
[09:03] <Riddell> apachelogger: then why have that policy?  the reason is it takes time and effort to make backports
[09:08] <apachelogger> no, the reason is that a) you don't want to do backports for 5 years beacuse at some point the foundation requirements will change and a backport becomes either hard or impossibru and half an hour per backport per release also becomes a time consuming effort if releases>=4, so you need to draw a line somewhere which is where this comes in: b) we want to encourage LTS users to stay on the LTS edge if they want to stay on the KDE edge by 
[09:08] <apachelogger> facilitating early LTS->LTS upgrades to get testing such that once the LTS->LTS upgrade path goes life everything works flawelessly and the LTS release has all major issues ironed out
[09:10] <apachelogger> all that being said, I fail to see what LTS backport support has to do with utopic backport support (which would be 9 months vs. 24months for LTS)
[09:12] <shadeslayer> not to mention that just because the build depends are sorted out, doesn't mean things will work at runtime, so then one has to invest time in sorting out bug reports that people report when running applications
[09:13] <shadeslayer> wat https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1324805
[09:15] <apachelogger> shadeslayer: flawed process
[09:16] <apachelogger> been saying that for years
[09:16] <shadeslayer> apachelogger: as in, KDM is broken ? :P
[09:16] <apachelogger> by the time an update lands in a PPA one needs to know that it works
[09:16] <apachelogger> currently we do not which is already a problem right there
[09:17] <shadeslayer> ah, PPA thingums
[09:17] <apachelogger> shadeslayer: no, that I've been saying for a couple of weeks
[09:17] <apachelogger> kdm broken
[09:17] <apachelogger> everyone keeps ignoring me asking who is looking at bugs
[09:17] <shadeslayer> apachelogger: https://www.youtube.com/watch?v=1Isjgc0oX0s
[09:22] <Riddell> apachelogger: possibly this means nobody is
[09:22] <apachelogger> yup
[09:23] <Riddell> shadeslayer: so will you send an e-mail to the release list?
[09:27] <Riddell> shadeslayer: or do you want me to?
[09:29] <shadeslayer> Riddell: I'll draft up something
[09:29] <Riddell> hmm, I can't find where sgclark put kde-baseapps for review
[10:20] <apachelogger> qtcreator with recommends pulls in mir stuff btw
[10:23] <Riddell> sigh
[10:31] <mcstr_> hey guys... im so happy my bug i reported yesterday got fixed the same day :)
[10:31] <mcstr_> impressive
[10:32] <Riddell> awooga!
[10:32] <Riddell> go us!
[10:32] <thelionroars_> https://www.youtube.com/watch?v=sXrOoODYPNE
[10:32] <mcstr_> yep thx riddell for ya help yesterday
[10:34] <Pali> Riddell: packages should be ready, I included also alsa/pa fix for phonon-backend-gstreamer
[10:34] <Pali> https://launchpad.net/~pali/+archive/kubuntu-backports/+packages
[10:35] <Riddell> Pali: awesome!
[10:35] <Riddell> Pali: you tested them?
[10:35] <Pali> yes, now I'm using it
[10:36] <Riddell> Pali: ok, I'll give it a test too and copy it over to the PPA
[10:42] <sgclark> Riddell: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/kde-baseapps5
[10:42] <Riddell> ah hah :)
[10:43] <yofel> that should be named kde-baseapps really
[10:43] <Riddell> yes I think that should be just kde-baseapps
[10:43] <sgclark> ok
[10:43] <Riddell> it's a new version of kde-baseapps bits, not co-installable
[10:43] <Riddell> same for the binaries, dolphin5 should be just dolphin
[10:44] <Riddell> (libkonq5 keeps its number at the end as a library soversion)
[10:44] <sgclark> ok fixing
[10:45] <Riddell> although libkonq5 is from kdelibs4 land, it should be bumped for the kf5 version
[10:45] <Riddell> which could be your second upstream patch :)
[10:46] <yofel> *does* it have a different ABI? (I would assume it does, should still be checked)
[10:46] <sgclark> Riddell: also maintainer gave a ship it for my review request, should I push it? Or wait for a KF5 person to also ok it?
[10:47] <Riddell> it must do, linking to qt5/kf5 will mess with the abi somehow I'm sure
[10:47] <yofel> most likely, right
[10:47] <Riddell> sgclark: oh excellent, push away
[10:47] <sgclark> What is an ABI and how do I check it?
[10:47] <Riddell> sgclark: it's all the symbols that a library exports, we list them in .symbols files
[10:48] <Riddell> API is the source code interface like setFont() method and QPushButton class
[10:48] <Riddell> which is used by human programmers
[10:48] <sgclark> ok
[10:49] <sgclark> makes sense
[10:49] <Riddell> and ABI is when it gets compiled into a shared library and end up with what you see in .symbols files and is used by compiled programs using that library
[10:49] <Riddell> the rules of what makes changes in the ABI are very obscure, especially in c++, one reason why programming a library is so difficult
[10:50] <Riddell> this is fun to read if you're a massochist http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++
[10:51] <sgclark> I am trying to learn everything I can, so thank you, on my reading list
[10:52] <Riddell> just use python, then you don't have to worry about that :)
[10:53] <BluesKaj> 'Morning folks
[10:53] <Riddell> sgclark: before you git push your change to kde-baseapps  remember to git pull --rebase  to bring in any changes already in the archive
[10:54] <Riddell> the --rebase bit confused me for a while
[10:54] <sgclark> Riddell: they gave me a gitup script to do that
[10:59] <Peace-> Riddell:  i can't undestand something here does it work or not ? https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1310773
[10:59] <Riddell> sgclark: who's they?
[10:59] <Peace-> Riddell: here it doesn't work but i have asked to some guys and they said me that is working properly
[11:00] <Riddell> Peace-: I guess it doesn't work for the bug reporter
[11:00] <Peace-> tried with phonon vlc and phonon gstreamer
[11:00] <sgclark> Riddell: KDE folks I working with when I was contributing to their docs
[11:06] <shadeslayer> can anyone c++filt this symbol _ZN9KSysGuard7ProcessD1Ev@ABI_4_1
[11:06] <sgclark> Riddell: here http://www.davidfaure.fr/scripts/gitup
[11:07] <shadeslayer> ah
[11:08] <shadeslayer> nvm
[11:08] <sgclark> Riddell: and here is the blog on gitup http://blogs.kde.org/2012/10/19/updating-git-checkout-finally-easy-svn
[11:13] <Riddell> sgclark: nifty
[11:31] <sgclark> Riddell: so I forgot to ut the review request number in the commit message, anyway I can fix this? :(
[11:33] <Riddell> sgclark: no just close the review request manually on reviewboard
[11:33] <Riddell> and congratulations on being an elite KDE coder :)
[11:34] <sgclark> Riddell: yay:)
[11:52] <ScottK> shadeslayer: I'm very much against any regular use of PPAs as part of what we define as a Kubuntu release.
[11:53] <ScottK> If upstream wants updates to end users, they can produce releases that are suitable for that purpose.
[12:38] <Riddell> yofel: hmm, we should sort out this server toot sweet, did you get anywhere?
[12:40] <shadeslayer> Karma: 66641 < only 25 more to go
[12:43] <shadeslayer> ScottK: rather than opposing upstream, why can't we adjust our workflows a bit to accomodate faster cadence cycles
[12:44] <ScottK> shadeslayer: Shipping things from outside the Ubuntu archive is a fundamental change to what Kubuntu is.
[12:44] <shadeslayer> because a faster cadence cycle in the beginning is good overall, since upstream will get better feedback
[12:44] <ScottK> If people want to do stuff on top of Kubuntu in a PPA, that's fine.
[12:45] <ScottK> We do that all the time now.
[12:47] <ScottK> It's not a question of workflow, but how you define what the project is.
[12:47] <shadeslayer> btw didn't we decide all of this at the meeting? to deliver things via the PPA
[12:47] <Riddell> we did, but now I'm wondering why
[12:48] <ScottK> shadeslayer: We did not for kf5.
[12:48] <ScottK> I think we need to rediscuss it for plasma next.
[12:50] <ScottK> shadeslayer: BTW, I'm not accepting the 4.13.2 SRU until 4.13.2 is built on utopic.  i.e. you're blocking it by not fixing your workspace upload.
[12:50] <yofel> we did say we would have a seperate image that allows the PPA for kf5 and plasma. We did not talk about adding a PPA in the default setup
[12:50] <shadeslayer> ScottK: I fixed it, but it's still FTBFS
[12:50] <shadeslayer> so not really
[12:50] <shadeslayer> fixing it again
[12:50] <apachelogger> ppa in default setup? 
[12:50] <apachelogger> wut?
[12:51] <shadeslayer> ^^
[12:51] <ScottK> I was going to say, that's an odd definition of fixed.
[12:51] <yofel> Riddell: dang no, life got in the way of memory, sorry. There was some paperwork that would allow server account transfer, but maybe best ask the current owner as he'll have to fill out half of that
[12:52] <shadeslayer> FWIW I'm not proposing the regular ISO + PPA, I'm talking about a separate ISO than the regular one which has the PPA enabled
[12:52] <yofel> didn't we already decide to do that for utopic?
[12:53] <shadeslayer> I thought we did
[12:53] <apachelogger> yes we did
[12:53] <yofel> we did, but we did also note that it's temporary
[12:53] <shadeslayer> yep
[12:53]  * apachelogger doesn't understand what all the fuzz is about again
[12:53] <ScottK> shadeslayer: Not for kf5 though, that's supposed to go in the archive.
[12:54] <Riddell> yofel: do you have any pointers to it?
[12:54] <yofel> ScottK: IIRC the whole point of the discussion was kf5
[12:54] <yofel> Riddell: sec
[12:54] <ScottK> No, the PPA image thing was for plasma next.
[12:54] <ScottK> At least IIRC.
[12:54] <apachelogger> which will require or at least want a newer frameworks
[12:55] <yofel> Riddell: should be http://faq.hosteurope.de/view.php?mode=open_object&content_id=7446 - but it's all german
[12:55] <apachelogger> so the proposed action plan was land frameworks in the archive so people can easily get access for porting
[12:55] <Riddell> yofel: and paper, what millenium is this again? :)
[12:55] <shadeslayer> what apachelogger said
[12:55] <yofel> Riddell: please note the "german" :P
[12:56] <yofel> we love paperwork
[12:56] <yofel> it does allow fax at least
[12:56] <apachelogger> that being said, I am also not opposed to the idea of not landing frameworks either and instead add a button in discover that allows people easier access
[12:57] <apachelogger> as not having things in the PPA potentially keeps us more flexiable with packaging changes, but I guess we'd be fine either way, so eventually someone will have to land frameworks in utopic archive :P
[12:59] <yofel> well, I would not land frameworks in utopic at all unless we have a user of it in the archive
[12:59] <yofel> if it's in the archive we have to provide some level of support for it
[12:59] <Riddell> this is why I'm currently preferring just putting plasma 5 in the archive
[12:59] <Riddell> although it does mean renaming a bunch of source and binary packages
[12:59] <yofel> plasma5 needs framworks...
[13:00] <apachelogger> yofel: the support is that it doesn't break
[13:00] <yofel> apachelogger: + security support
[13:01] <yofel> so if we don't really intend to maintain it, I would rather it's not there at all
[13:01] <yofel> *not have it there
[13:01] <apachelogger> yofel: security support?
[13:02] <yofel> the rare CVE?
[13:02] <apachelogger> yofel: security support?
[13:02] <yofel> upstream security advisory?
[13:02] <apachelogger> why would we offer security support?
[13:02] <apachelogger> we are not even using it
[13:02] <yofel> because it's our responsibility as maintainer o.O?
[13:02] <apachelogger> and upstream's POV is use latest
[13:02] <apachelogger> yofel: no it is not?
[13:02] <yofel> it very much is
[13:02] <apachelogger> universe may get security updates
[13:03] <apachelogger> or it may not
[13:03] <apachelogger> there is no rule that says whoever puts something in universe must provide security support
[13:03] <yofel> I think our opinions of support differ here
[13:03] <apachelogger> we do not offer support, it's there, if you want to port your software to frameworks you can use it, we do not provide support
[13:03] <yofel> well duh, lets just call the whole release we provide unsecure then
[13:04] <apachelogger> FRAMEWORKS IS NOT PART OF ANY RELEASE
[13:04] <apachelogger> it is in universe
[13:04] <apachelogger> that's all
[13:04] <ScottK> apachelogger: Most of KDE is in Universe.
[13:04] <yofel> and who but us cares about that?
[13:04] <yofel> if we put something in the archive, someone will use it and complain
[13:05] <apachelogger> Universe
[13:05] <apachelogger> The universe component is a snapshot of the free, open-source, and Linux world. It houses almost every piece of open-source software, all built from a range of public sources. Canonical does not provide a guarantee of regular security updates for software in the universe component, but will provide these where they are made available by the community. Users should understand the risk inherent in using these packages. Popular or well 
[13:05] <apachelogger> supported pieces of software will move from universe into main if they are backed by maintainers willing to meet the standards set by the Ubuntu team. 
[13:05] <yofel> so if we're not using it, don't put it there
[13:05] <apachelogger> upstream wants it easily available
[13:05] <yofel> upstream also wants it up to date
[13:05] <apachelogger> [14:56] <apachelogger> that being said, I am also not opposed to the idea of not landing frameworks either and instead add a button in discover that allows people easier access
[13:05] <apachelogger> and Scott doesn't want it in the PPA
[13:06] <yofel> a button in an archive package that adds a PPA isn't allowed AFAIR
[13:06] <apachelogger> so what we discussed at the meeting is: put it in the archive so it is available, develop plasma in PPA for possible adoption in 15.04
[13:06] <yofel> that was about the rejection reason for ubuntu tweak
[13:07] <yofel> I don't quite remember the discussion ending like that, but maybe my memory is buggy
[13:08] <yofel> and I don't see how a PPA is not "easily available"
[13:08] <yofel> it's not like we're requiring a dozen of them
[13:13] <Riddell> Pali: 4.13.2 working well from your archive, but you've missed out a few packages, maybe you're using an old package list, the games and utils and oxygen are missing
[13:15] <Riddell> or maybe there's no upstream changes and so the scripts didn't backport it
[13:15] <yofel> that
[13:17] <Riddell> the plasma 5 image should be called a remix anyway, we want to make it clear it's not fully stable
[13:17] <shadeslayer> ^^
[13:21] <Riddell> options 
[13:21] <Riddell> options are 1) use neon 5 scripts to make an image using the PPA and call it kubuntu-not plasma 5 remix
[13:22] <Riddell> use the ubuntu-cdimage scripts with ppa and call it kubuntu-not plasma 5 remix, but the ubuntu-cdimage scripts with ppa code is not yet merged and untested
[13:22] <Riddell> 3) whatever the heck unity 8 are doing, something with derived distributions is it?
[13:23] <Riddell> 4) put it in the archive, involves renaming packages and marking that it won't get updates
[13:23] <Riddell> and call it kubuntu plasma 5 remix
[13:23] <Riddell> I like 1) and 4)
[13:30] <ScottK> 4 is close to what we did with KDE4 4.0, right?
[13:30] <Riddell> yep
[13:30] <ScottK> That seemed to go OK (from our PoV of the packages).
[13:30] <ScottK> 4.0 itself was horrible, but that wasn't our fault.
[13:30] <Riddell> :)
[13:37] <ScottK> The more I think about it, the more I think both KF5 and plasma 5 should just go in the archive and be done with it.
[13:37] <ScottK> Now that Qt5 5.3 is in, we actually have that option.
[13:37] <shadeslayer> note that if we go with our own scripts, we probably won't get UEFI support
[13:37] <shadeslayer> needs some magic that I don't fully understand
[13:37] <ScottK> So I vote #4.
[13:38]  * shadeslayer proposes 2
[13:39] <Riddell> shadeslayer: but that can't happen unless colin or someone wants to merge those patches in and test them, seems like making life harder on us
[13:39] <shadeslayer> Riddell: actually, I talked to Colin last night and he asked me to send him details on requirements
[13:39] <shadeslayer> so he can write code on the cdimage size
[13:39] <shadeslayer> *cdimage side
[13:40] <Riddell> yep, might be do-able, but I'd still be nervous since unity8 people have considered it and decided not to
[13:41] <shadeslayer> I think that's because they have different requirement than ours ...
[13:42] <shadeslayer> Colin said that as long as we don't mess with packages that are required in the debootstrap stage, it should be fine
[13:43] <Riddell> so advantage is we could update after release, we wouldn't have to rename source or binary packages.  disadvantage is it goes against lots of policies so we'd need to mark is as not really kosher
[13:46] <shadeslayer> I don't think it's a matter of policies since it will be a remix, just that it'll be built by the official CD image infra ... we still call it a remix in release
[13:48] <yofel> well, there should be a big red UNSUPPORTED banner
[13:52] <shadeslayer> why?
[13:53] <shadeslayer> we won't provide security updates, sure, but support is limited to fixing bugs in our packaging and updating it whatever upstream releases
[13:54] <yofel> hm, I might've misunderstood how the renaming was intended
[13:54] <yofel> might be fine
[14:01] <apachelogger> we don't provide support for anything because no one ever reads bug reports, so I guess it's fair if we stick the banner everywhere really
[14:04]  * sgclark giggles
[14:05] <sgclark> I actually want to learn that, where is a good place to start?
[14:05] <apachelogger> https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[14:05] <apachelogger> this list gets aaaaaaaaaaaaaaaaaallll the launchpad bugs we care about
[14:06] <sgclark> ok ty
[14:25] <shadeslayer> apachelogger: I fixed all the bugs there
[14:25] <shadeslayer> so lies
[14:25] <shadeslayer> we don't have any bugs
[14:37] <Riddell> shadeslayer: I think for now e-mail colin to see if he's happy to implement images with PPAs and if it'll be available before too long (a month or less I'd think)
[14:38] <shadeslayer> Riddell: I'll draw up requirements, post them here, we can discuss on Monday and I can send them off on Monday
[14:43] <Riddell> okay dokay
[14:44] <ScottK> shadeslayer: Can we use the same derived distro thing phone is using?
[14:44] <ScottK> If it's going to be !in the archive, we might as well be as consistent with other stuff as possible.
[14:45] <shadeslayer> ScottK: we could, but CD image is going to take quite a bit of time
[14:45] <shadeslayer> ( for the derived thing )
[14:45] <ScottK> Does that have to be done for phone anyway, or would it be just for us?
[14:46] <shadeslayer> I thought phone images go through jenkins
[14:46] <shadeslayer> don't know enough about those though
[14:46] <ScottK> They still have to create the images some way.
[14:50] <shadeslayer> ScottK: http://irclogs.ubuntu.com/2014/06/19/%23ubuntu-release.html#t22:13
[14:52] <ScottK> shadeslayer: Thanks.
[14:53] <ScottK> Send your mail and let's discuss.
[14:53] <shadeslayer> I hate ARM
[14:53] <shadeslayer> hate it hate it hate it
[14:53] <shadeslayer> stupid missing symbols again
[14:54] <Riddell> shadeslayer: are you looking at 4.13.2 in utopic?
[14:54] <shadeslayer> Riddell: not really, workspace has managed to give me a headache
[14:55]  * shadeslayer sighs
[14:56] <shadeslayer> yofel: http://paste.kde.org/plp2mx8zi
[14:56] <shadeslayer> yofel: http://paste.kde.org/p6p9vwcke
[14:56] <shadeslayer> yofel: any clue what's going wrong there
[14:59] <shadeslayer> ah
[14:59] <shadeslayer> nvm
[14:59] <yofel> ^^
[15:00] <shadeslayer> hm nop
[15:00] <shadeslayer> yofel: ok so, what's wrong? :P
[15:02] <yofel> hm, good question
[15:02] <shadeslayer> yofel: found it
[15:02] <shadeslayer> dest=series
[15:02] <shadeslayer> should be dest='series'
[15:03] <shadeslayer> I hate optparse/argparse in python
[15:03] <shadeslayer> makes so little sense when you read the docs
[15:03] <apachelogger> Riddell: btw, wordpress appears to be able to post to g+ somehow
[15:03] <apachelogger> so there must be some sort of write input for it
[15:06] <Riddell> it may be these sodash people are just lying and they haven't implemented it
[15:09] <Riddell> shadeslayer: remember I have an arm machine if you need one
[15:10] <shadeslayer> "You have exceeded the login limit. Please wait a few minutes and try again."
[15:11] <shadeslayer> I have possibly forgotten my blog password
[15:13] <apachelogger> Riddell: dunno, sodash does more than just post stuff somewhere from what I understand, so it may entirely be that it doesn't provide else they need, I am just saying xD
[15:31] <shadeslayer> scru u too armhf
[15:32] <Riddell> analitza not happy, 3d symbols disappeared
[15:32] <Riddell> on arm
[15:33] <Riddell> although you wonder why they were ever there since arm doesn't do gl
[15:35] <apachelogger> someone should make the ubuntu planet not list old posts because the <updated /> date has changed 
[15:35] <apachelogger> #braindead
[15:43] <genii-borkbork> Hi, is ksplash currently broken on Utopic? It doesn't even come up right now after latest dist-upgrade
[15:44] <genii-borkbork> ( sits forever on lightdm background picture after login)
[15:46]  * genii-borkbork makes a fresh pot of coffee
[15:46] <shadeslayer> yofel: hurray : http://paste.kde.org/psjkrex5u
[15:46] <shadeslayer> not sure why it's happening
[15:49] <yofel> you're the error master today
[15:54] <shadeslayer> aha
[15:54] <shadeslayer> I know
[15:54] <shadeslayer> oh wait
[15:54] <shadeslayer> no I don't
[15:57] <shadeslayer> yofel: it's weird, error indicates that the file is not fully written to the disk
[15:57] <shadeslayer> can't imagine how that happens
[15:58] <yofel> is your code any different from the old buildlog fetching script?
[15:58] <yofel> or well old code, there was no seperate script IIRC
[15:59] <genii-borkbork> Going to tinker and return.
[15:59] <shadeslayer> not really
[16:02]  * Riddell publishes http://www.kubuntu.org/news/kde-sc-4.13.2
[16:02] <Riddell> Pali: ↑
[16:02] <Riddell> Pali: thanks much for the packaging, do stick around if you want to continue to be an elite kubuntu ninja
[16:13] <BluesKaj> hmm, splash screen doesn't load and the process stops completely, unless I use the virtual konsole/tty,  login and startx ... any other similar reports?
[16:16] <lordievader> BluesKaj: genii reported it just now.
[16:17] <BluesKaj> lordievader, ok good
[16:20] <BluesKaj> genii logged off tho
[16:20] <shadeslayer> hah
[16:20] <shadeslayer> we tried to boot the 8.04 64 bit ISO
[16:20] <shadeslayer> it doesn't boot
[16:20] <shadeslayer> at all
[16:20] <shadeslayer> grub fails
[16:24] <BluesKaj> shadeslayer, maybe the HW is too new and not recognized
[16:40] <sgclark> santa_ kde-baseapps is still a major work in process and not ready for human consumption
[16:41] <Riddell> shadeslayer: feeling retro?
[16:42] <santa_> sgclark: I guess, but I think my merge request is right anyway
[16:44] <sgclark> santa_ aka that branch is being removed altogether
[16:44] <santa_> why?
[16:46] <sgclark> dropping the 5 as suggested to me by the authority. Also several other changes in the works.
[16:47] <sgclark> I can apply your change or you  can wait for merge requests when I complete the new one
[16:48] <santa_> whatever works better for you
[16:56] <shadeslayer> Riddell: heh yeah
[16:58] <Riddell> debian change to k3b to compile "Disable the FFmpeg plugin" I guess we need to follow
[16:58] <Riddell> it doesn't compile currently
[16:59] <santa_> Riddell: hey, if debian's people doesn't reply to your epoch vs renaming question ... which way would you take? epoch?
[16:59] <Riddell> santa_: I don't know, no epoch would be the safe one I guess as it's harder (impossible?) to remove an epoch
[17:01] <santa_> yeah, because, well, when I'm done with the mass merge proposal I was planning to release this in an experimental repo of siduction and see if I get useful feeback from users
[17:02] <santa_> so I would need to to figure it out, tbh I think I will go with a renaming (which could be reverted later)
[17:02] <santa_> for the reason you mentioned: it can be reverted
[17:04] <BluesKaj> Power Management settings are totally disregarded after the last update/upgrade ...shuts everything down when the laptop lid is closed no matter what the settings are.
[17:05] <BluesKaj> dicsconnects the wifi, blacks the scrn etc
[17:06] <BluesKaj> there's no delay , it's instant
[17:06] <BluesKaj> it's seriously broken
[17:08] <yofel> do you have a running kded4 process?
[17:09] <BluesKaj> yofel, none that i can see in sys mon
[17:09] <yofel> then that must've crashed at some point
[17:10] <yofel> does anything happen if you start it now?
[17:11] <BluesKaj> start ?
[17:11] <yofel> just open konsole and run kded4
[17:12] <BluesKaj> already running
[17:13] <yofel> uhm, just now you said it's not running, or did you start that yourself?
[17:13] <Riddell> what's the script to retry all the kde sc packages in the main archive?
[17:14] <yofel> kubuntu-retry-builds from kubuntu-automation
[17:24] <Riddell> hmm, doesn't want to work
[17:24] <Riddell> just says Can't retry for every package
[17:24] <Riddell> and if I add --force I get a backtrace about an AssertionError
[17:25] <shadeslayer> ScottK: I think kde-workspace should be fine in utopic
[17:25] <shadeslayer> can you please approve 4.13.2 ?
[17:34]  * Riddell discovers --forcedepwait
[17:48] <BluesKaj> kded4 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
[17:48] <BluesKaj> KDE Daemon (kded) already running.
[17:49] <BluesKaj> Application may misbehave.... heh it seems that it is 
[17:54] <sgclark> Riddell: can you  take a look at https://git.reviewboard.kde.org/r/118851/
[19:01] <sgclark> Riddell: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/kde-baseapps ready for review