/srv/irclogs.ubuntu.com/2013/08/05/#kubuntu-devel.txt

=== Guest84363 is now known as wgrant
smartboyhwWhoohoo my main PPA is now 6GiB:)04:03
smartboyhwDamn, quantal 4.10.97 is now just last step away from ready, but I just can't make kate and pykde4 happy...04:11
shadeslayersmartboyhw: no endorsements is fine, I didn't get any as well, it was mostly that the the most active developers should be familiar with your work05:13
smartboyhwshadeslayer, uh05:23
smartboyhwOK:P05:23
shadeslayerdid someone setup a doodle?05:23
smartboyhwThen the wiki page really needs an update05:23
smartboyhwshadeslayer, let me go and setup one05:24
shadeslayerif not I can send an email out regarding that since Riddell is out05:24
shadeslayersmartboyhw: cool05:24
smartboyhwshadeslayer, where should we hold the meeting?05:26
smartboyhwHere or #ubuntu-meeting?05:26
jussihere is usual05:26
jussishadeslayer: we all thought you were crap, but we liked you so much we let you in :P :P :P :P : P :P05:27
valoriepffff05:27
smartboyhwjussi, LOL05:27
smartboyhwpffffff05:27
shadeslayer:)05:27
* jussi hugs shadeslayer05:28
* shadeslayer huggles jussi back05:28
smartboyhwPlease enter a value.05:28
smartboyhwWhat!?!?05:28
shadeslayerjussi: oh and btw, you've lost alot of weight :O05:28
smartboyhwI can't even set the title......\05:28
shadeslayerjussi: or maybe you just look good in the camera :P05:28
jussishadeslayer: 13 kg05:28
shadeslayerjussi: congrats :D05:29
jussishadeslayer: still about 10 to go05:29
shadeslayerjussi: is that Elodi's doing :P05:29
shadeslayerkeeping you up at night, making you run after her etc05:29
jussishadeslayer: no, its just my love of bacon... m Im on a bacon diet! :D05:29
shadeslayerthere's a bacon *diet* ? :D05:29
jussinot quite, but my diet includes bacon...05:30
jussiI started in feb, and Ive now lost 13kg. I wonder what ill look like in feb next year05:30
* shadeslayer needs to start working out as well, I've gotten so fat -.-05:31
jussihehe05:31
jussishadeslayer: its funny, when you are big, workouts are soo hard, you give up. but if you can modify your diet and loose a little, then the workouts come much easier05:32
shadeslayeroh05:33
shadeslayerI'm not as big as you yet, I can still start05:33
shadeslayerI'm just lazy ...05:33
jussishadeslayer: ++ I know that feeling, careful or youll end up as big as i was05:35
shadeslayerjussi: yeah, hopefully will be better once I move05:35
jussishadeslayer: where are you moving to ? finally coming to join me here in .fi? 05:36
ScottKHe'd freeze in a week.05:36
ScottKEven in summer.05:36
jussihaha05:37
jussiScottK: come on, we had 30C yesterday!05:37
smartboyhwScottK, shadeslayer you should have received an invitation of the Doodle poll now. I shall post the public address to kubuntu-devel mailin list soon05:37
shadeslayerjussi: I'm planning to acclimatize to Barcelona first :P05:38
shadeslayergot it05:38
ScottKDidn't get it yet, but I greylist, so it's not surprising.05:39
smartboyhwScottK, I used ubuntu@kitterman.com05:43
smartboyhwThank you shadeslayer05:44
shadeslayeroh drat, I did not factor in various other meetings into my doodle stuff05:45
* shadeslayer goes back to change05:45
ScottKDoodled.05:49
smartboyhwshadeslayer, sure05:52
smartboyhwScottK, thanks05:52
smartboyhwWhoa, it looks like 13:00 UTC of 9th (Fri) is the most popular right now05:53
=== smartboyhw changed the topic of #kubuntu-devel to: Kubuntu - Friendly Computing | https://trello.com/kubuntu | https://notes.kde.org/p/kubuntu-ninjas 4.10.97 saucy/archive raring/beta quantal/staging precise/read_notes_on_pad | 13.10 Alpha 2 released | 13.10 milestoned bugs tagged Kubuntu http://goo.gl/vHRjj | Kubuntu Developers please vote at http://doodle.com/2mwfbh9b7pbz3qzk
soeegood morning05:59
valoriehttp://fossforce.com/2013/07/whats-your-favorite-foss-or-linux-blog/ - Martin's blog is leading06:21
shadeslayeryofel: http://paste.kde.org/p61a77235/07:57
shadeslayeryofel: that's for precise07:57
jussisigh08:00
jussisilly kde, why do you show everyone whats on my screen when waking up?08:00
apacheloggerporn leakage?08:11
tsdgeosjussi: given how "unstandard" ubuntu's sleeping methods are i would not blame kde apps so quickly08:11
jussiapachelogger: no, work laptop. 08:11
jussitsdgeos: heh... I guess. in any case, Kubuntu has a bug08:11
apacheloggeryou know08:12
apacheloggerI still think we should simply adopt systemd :P08:12
shadeslayer^^08:12
shadeslayerand make it not crippled08:12
apacheloggercuz the upstart-logind bastard child of hell seems to not be so great :P08:12
shadeslayerapachelogger: put it in the agenda for the meeting?08:13
apacheloggerwhat meeting?08:13
jussiapachelogger: topic :D08:13
shadeslayer^^08:13
apacheloggerwait what08:14
apacheloggerit's in the topic too08:14
apacheloggerdafuq08:14
* jussi hugs apachelogger08:14
jussiapachelogger: sounds like you need a coffee...08:14
apacheloggerso I was out for the weekend and today I turn on the magic box which makes light come out of this very dark mirror08:14
apacheloggerand I look at my mail08:14
apacheloggerand there's 3 threads about smartboyhw's membership thing08:15
apacheloggerand now I also find it on IRC08:15
yofelshadeslayer: hm, that's better than what I got 08:15
shadeslayeryofel: oh08:15
apacheloggertales from "how to make apachelogger not care" :P08:15
yofelthough amarok and kde-workspace don't belong on the removal list08:15
shadeslayeryou don't say :P08:15
yofel^^08:15
apacheloggerxserver-xorg08:16
apacheloggerthat seems x driven though08:16
apacheloggerlibgl1-mesa-dri or that maybe, seeing as X possibly deps on that08:16
apacheloggerah08:16
apacheloggernow I get it08:16
apacheloggerwe are pulling in the lts enablement stack?08:17
shadeslayeryes08:17
apacheloggeraaaaahhhhhhhhh08:17
apacheloggeryes, linkage seems kaput in workspace then08:17
apacheloggerkwin wants regular x, doesn't get it, goes away08:17
shadeslayerchecking08:18
apacheloggeramarok doesn't quite make sense though08:19
apacheloggerat least on raring it doesn't have any deps on any other package marked for removal08:20
apacheloggerdeps libx11-6, which may or may not be the cause here08:22
shadeslayerDon't think it's libx1108:23
shadeslayerbecause there is no libx11 LTS backport08:23
apacheloggerwell, there's nothing else :P08:24
* apachelogger hates writing changelogs -.-08:26
apacheloggershadeslayer: actually you could just let apt tell you :P08:26
apacheloggerapt-get -o Debug::pkgProblemResolver=yes dist-upgrade08:26
apacheloggeror somesuch business08:26
yofelright08:26
shadeslayer*nod*08:27
yofelsmartboyhw: uh, the pykde build failure is pretty clear though, python-qt4 depends on sip-api-8.1, while python-sip provides sip-api-10.008:28
yofelyou python-qt4 is too old08:29
yofel*your08:29
yofeldoodled btw.08:30
shadeslayerhttp://paste.kde.org/p1ee7c81a/08:31
shadeslayerwe need to rebuild amarok against the new HWE stack as well I think08:38
yofeloh right08:38
yofelI'll backport the beta08:38
yofel2.7 crashes with 4.11 anyway08:38
shadeslayerack08:38
* shadeslayer looks at kde-workspace then08:39
shadeslayeraha08:40
shadeslayerBroken kde-window-manager-common:amd64 Depends on libgl1-mesa-glx [ amd64 ] < 8.0.4-0ubuntu0.6 > ( libs )08:40
yofeldpkg-shlibdeps is fun, isn't it?08:42
shadeslayer^^08:43
yofel$ cat debian/libgl1-mesa-glx-lts-raring.shlibs 08:47
yofellibGL 1 libgl1-mesa-glx | libgl108:47
afiestassmartboyhw: yes08:47
yofeluhm08:47
shadeslayer*facedesk*08:47
yofelI think we need to ask the X folks how this is *supposed* to work08:48
* shadeslayer pokes X people08:48
yofelso...09:18
yofelwe have the choice between 2 not recommended things we can do :/09:18
yofela) default to mesa 8 (not recommended by martin)09:20
yofelb) explicitely pull in the mesa stack with manual depends (not recommened by ubuntu-x)09:20
shadeslayerdo a) and ask users to install the lts stack?09:21
yofelprobably the best solution indeed, at least it's the one with the least amount of breakage potential09:21
shadeslayeryep ^^09:22
shadeslayeronly that this means we get to upload everything again09:22
yofelwell, shouldn't be much of an issue09:23
yofelbut qt and meta need to be fixed too09:23
shadeslayer*nod*09:23
shadeslayeroh09:23
shadeslayeryofel: can't we just make meta depend on the LTS stack09:23
yofelwell, it already *does*09:23
yofeldoesn't help09:23
shadeslayeruhm right09:24
shadeslayeroh?09:24
yofelThe following packages will be REMOVED:09:24
yofel... kubuntu-desktop kubuntu-full09:24
shadeslayer:/09:24
shadeslayeryofel: but isn't that because of kde-window-manager09:24
shadeslayerso if we fix everything to build against regular mesa, but make the meta package depend on the HWE stack09:25
shadeslayerthen during the upgrade it'll pull in the new HWE stack09:25
yofelit'll remove the meta packages on upgrade. But that would at least provide an easy way to install the HWE stack09:25
yofelthat's what kubuntu-lts-backport is supposed to do currently09:26
yofelbut just trying to install that ends up with09:27
yofel kubuntu-lts-backport : Depends: xserver-xorg-lts-raring but it is not going to be installed09:27
shadeslayero_o09:27
yofelshadeslayer: ok, how about this: revert back to default mesa, allow kubuntu-desktop to use both and provide kubuntu-lts-backport to install the full HWE stack09:29
shadeslayeryofel: yeah, that's what was going through my mind as well09:29
yofelthen lets go with that. I'll upload a qt rebuild09:30
shadeslayerbut didn't you just say that kubuntu-lts-backport isn't installable?09:30
yofelno here, and 'apt-get install kubuntu-lts-backport xserver-xorg-lts-raring' results in: http://paste.kde.org/pbb07556c09:31
yofel*not here09:31
yofelbut that package doesn't really do much right now:09:32
yofelkubuntu-lts-backport09:32
yofel  Depends: linux-image-generic-lts-raring09:32
yofel  Depends: xserver-xorg-lts-raring09:32
yofeland I think we'll need at least the manual dependencies on mesa09:33
yofelapt-get install kubuntu-lts-backport libgl1-mesa-glx-lts-raring09:34
yofellooks much better09:34
yofelqt uploaded09:42
shadeslayerack09:43
shadeslayerI suppose I could go for a quick nap :P09:44
yofelgo ahead, this'll take 4h ^^09:44
jussishadeslayer: or have a swordfight... :D http://xkcd.com/303/09:44
shadeslayerjussi: oh that was this morning09:45
jussihaha09:45
shadeslayerwhen Qt tests were running :)09:45
smartboyhwapachelogger, yofel sorry for spamming mailing list09:48
smartboyhwyofel, yeah I know..09:48
smartboyhwafiestas, oh good:)09:48
yofelwhat about the ML?09:48
smartboyhwyofel, I mean apachelogger receiving 3 emails:P09:49
yofelah09:49
apacheloggerwell, in all fairness, I am important like that09:49
smartboyhwapachelogger, yes, you are VERY important:)09:49
apacheloggerI am now working 3 hours and am still reading backmail from the weekend09:50
apacheloggerquite the drag -.-09:50
smartboyhwapachelogger, where's kubotu?09:51
apacheloggervacation09:52
smartboyhwapachelogger, .....09:52
smartboyhwIf you would kindly make it back?09:52
afiestassmartboyhw: as soon as a package reaches the ftp, it means it is ready for download/package/etc09:53
smartboyhwafiestas, yeah, I've packaged it here already:)09:53
afiestasI haven't announce it (or Dan) because we are busy09:53
afiestasawesome! thanks09:53
apacheloggerhm09:53
afiestascan I get an update of Kubuntu freeze?09:54
afiestasI'd like to release KScreen 1.1 before it09:54
smartboyhwafiestas, Kubuntu Freeze? You mean, Feature Freeze?09:54
apacheloggerjussi, tsimpson: didn't we have an upstart/init.d script for kubotu?09:54
* apachelogger kubuntu freezes afiestas09:54
smartboyhwapachelogger, +109:54
apacheloggerAugust 29th09:54
apacheloggerWarning /!\ FeatureFreeze, Beta 1 Freeze (for opt-in flavors)09:54
tsimpsonapachelogger: we don't09:54
apacheloggertsimpson: curious09:54
smartboyhwafiestas, FeatureFreeze and Beta1Freeze is on August 29th09:54
apacheloggerI guess I should write one then ^^09:55
tsimpsonyou can create a cron job too/instead09:55
tsimpsonif you do write an upstart job, I'd like that :)09:55
apacheloggersame amount of work as the trick is figuring out how to get a screen with kubotu started as my user09:56
apacheloggerwhich is why I thouht we had a script because I definitely remember working on that09:56
apacheloggeroh well09:56
tsimpsonalso, we'll be moving ubottu.com to 13.04 soon (as soon as I get everything transferred to the new server)09:56
apacheloggerat least manually starting kubotu gives me the chance to update it every once in a while ^^09:56
smartboyhwkubotu: newversion libkscreen 1.0.109:57
smartboyhwHAHAHA09:57
kubotuhttps://bugs.launchpad.net/bugs/120840909:57
apacheloggerkubotu: hey09:58
kubotumorning apachelogger :D09:58
smartboyhwkubotu: newversion kscreen 1.0.109:59
kubotuhttps://bugs.launchpad.net/bugs/120841310:00
tsimpsonapachelogger: you can pass -b when starting the bot to background it too, so no need for screen10:01
smartboyhw-queuebot/#ubuntu-release- Unapproved: accepted ibus-cangjie [source] (raring-proposed) [0.0.1~git20130325-0ubuntu1.1]10:02
smartboyhwOops, wrong chan:P10:02
* smartboyhw is supposed to post it in another one, sorry folks10:02
smartboyhwyofel, any time to review kscreen and libkscreen?10:08
smartboyhwIt's in https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+packages10:08
smartboyhw(A new PPA:P)10:08
smartboyhwHmm, why are you guys more free on Fridays? :O10:09
apacheloggertsimpson: yes, but I like having it on a screen :P10:15
shadeslayerhm, 4.12 beta releases happen within one week10:15
tsimpsonok then10:15
apacheloggerit's an OCD thing ^^10:15
shadeslayernot sure if that's enough time to get them out quickly enough :/10:15
shadeslayernot to mention Kubuntu get's about 15 days of upstream support \o/10:16
shadeslayer( assuming Kubuntu is released in the middle of April )10:16
shadeslayerfor an LTS release that sounds awesome10:17
apacheloggerfails to compute10:17
shadeslayerhttp://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule10:17
shadeslayerTuesday, April 29 2014: KDE 4.12.5 release10:17
shadeslayeroh actually, if previous release is any indication, the x.04 release is made towards the end of the month10:19
yofelshadeslayer: less time between releases also means less changes we need to take into account10:30
yofelso I think it would work (for beta2+)10:31
shadeslayerright, just saying that by the time we'll be done with beta 1 , beta 2 will be close to tagging10:31
smartboyhwshadeslayer, as in 4.11 anyway10:31
smartboyhwyofel, will you review kscreen?10:32
shadeslayernope10:32
smartboyhwand libkscreen ofc10:32
yofelshadeslayer: not in the next 6h10:32
shadeslayerBeta 1 and Beta 2 had 2 weeks in between them10:32
yofeler, smartboyhw^10:32
shadeslayerI can have a look10:32
smartboyhwshadeslayer, great10:32
yofelyeah, 1 week is a bit short10:32
smartboyhwshadeslayer, they are in https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+packages10:33
yofelconsidering we need at least 2 days to actually get the beta out10:33
shadeslayerI am not sure why Riddell didn't send the suggestions we decided on to the ML10:33
yofelleaves at most 5 days for testing10:33
shadeslayer2 days? hah, first Beta usually takes alot more time10:33
shadeslayernew deps, new files and what not10:33
smartboyhwyofel, how long did we take to get Beta 1 ou?10:33
yofelin *saucy*, not saucy+1 because that needs another 2 days or so until it's through -proposed10:33
smartboyhwin 4.11?10:33
shadeslayerwell, 4.12 comes out post saucy release10:34
shadeslayerthat's what I was talking about10:34
yofelsure, I'm talking about testing10:34
shadeslayeruhm, last 2 sentences make no sense :P10:34
yofelwell, we can do the beta backports *fast*10:34
shadeslayer4.12 comes out post saucy, so we put it in saucy + 1 first10:34
yofelbuilding in saucy+1 archive takes longer10:34
yofelso less testing in the dev release10:34
shadeslayerright10:35
yofelthat's all I said10:35
shadeslayer*nod*10:35
shadeslayerbackporting is fast10:35
yofelbeta1 packaging takes about a week usually, which is why I said beta2+10:35
yofelbeta1 will never see a release in kubuntu with *that* schedule I fear10:35
shadeslayerafiestas: tsdgeos ^^10:36
shadeslayerand upstream will get loads of bug reports post 14.04 release10:36
yofelbut that's an estimate based on recent experience10:36
shadeslayernothing we can do about that as well10:36
yofelare there git moves planned for 4.12?10:36
yofel(kdewebdev?)10:36
tsdgeosshadeslayer: thought luck for you i guess :D10:37
tsdgeoslet's delay the world because i'm slow!10:38
smartboyhwSo, we will be uploading to devel soon...10:38
smartboyhwProbably saucy+110:38
yofelif we don't have git splitups we can do beta1 within 4 days I believe10:38
smartboyhwThe *rolling release* symlink thing.10:38
yofelsmartboyhw: wasn't that meant to be an *additional* target?10:39
tsdgeosshadeslayer: if oyu can't get beta1, you can do beta2, or you can start working on "non beta tarballs" if that helps, or...10:39
shadeslayertsdgeos: depends entirely on how much you change :P10:39
yofelsmartboyhw: though unification would make sense I guess10:39
smartboyhwyofel, well it seems like we can upload to it10:39
shadeslayerif there are alot of changes, then it'll take time10:39
yofelshadeslayer: well, we have kdelibs and kde-workspace frozen10:39
smartboyhwYou can still ofc upload to saucy, saucy+110:39
shadeslayeryofel: right, but there are like a bazillion other things 10:40
yofelnot that much, if anything it's finding out what dependencies need to be updated10:40
yofelthat easily causes a day of delay10:40
yofelthough we could do that *before* beta1 really10:40
smartboyhwGoing for a swim..10:43
smartboyhwRiddell, please vote on the Trello:P10:43
yofeltsdgeos: one thing though: are you sure you can keep the release dates? with tagging and release on the same day in 4.11 we had a few cases where the tars were online a day or two after the tagging.10:43
yofelConsidering we only have 1 week to work with them such a delay becomes a problem10:43
shadeslayersmartboyhw: diffs look sane to me10:46
shadeslayersmartboyhw: will upload once they're built10:46
Riddellsmartboyhw: vote on trello?10:54
shadeslayerRiddell: he probably meant doodle10:58
Riddellok done11:01
shadeslayerRiddell: and what happened to the suggestion we made regarding having a growing period between bug fix releases?11:06
yofelgrowing period?11:06
shadeslayeryeah, like 4.12.1 3 weeks after 4.12, 4.12.2 6 weeks after 4.12.111:07
shadeslayerso on and so forth11:07
yofeloh that11:07
yofeldunno11:07
shadeslayer*shrug* as long as I don't have to deal with bug reports and all of them go upstream ;)11:09
yofelshadeslayer: sure, all of them will be RESOLVED EOL though11:09
=== vinay is now known as Guest26148
yofelwell, probably not11:10
yofelbut still11:10
smartboyhwRiddell, thank you!12:30
smartboyhwHmm, probably 16th 13:00 UTC then.....12:31
smartboyhwRiddell, is it that you wanted a news release for calligra 2.7.1? It has migrated into -release now12:36
Riddellsmartboyhw: oh cool if it's migrated and raring and precise are done then go for it12:49
smartboyhwRiddell, no precise sorry13:02
smartboyhwIt can't work without g++-4.713:03
smartboyhwI can only do Quantal13:03
BluesKajHey folks13:07
QuintasanRiddell: Do we support things like 12.04 -> 13.04?13:08
Quintasanor it's only LTS -> LTS upgrades that we support?13:08
davmor2Quintasan: update-manager -d will take you out of the lts→lts 13:14
Quintasandavmor2: I might be dumb but wouldn't -d install saucy?13:14
QuintasanCurrent development release is saucy iirc13:15
davmor2Quintasan: d'oh yeap sorry13:15
davmor2Quintasan: it in software-properties-gtk for me on ubuntu so I'm assuming there is a qt version maybe?13:15
highvoltage/win 1713:16
smartboyhwhighvoltage, !?13:16
Quintasandavmor2: I see. I forgot about that, thanks.13:19
davmor2Quintasan: http://ubuntuone.com/0us1fr5yKrdhJ3YTWIcBmp13:19
smartboyhwMMm13:25
smartboyhwhttp://www.techradar.com/news/software/operating-systems/ubuntu-derivatives-5-of-the-best-ubuntu-based-distros-117031413:25
smartboyhwWe are only at No.3 behind Ubuntu GNOME and Bodhi Linux...13:25
smartboyhwOh no, it's 4th:(13:25
smartboyhwAh, it's actually score damn:P13:26
smartboyhw4/5 that's quite good13:26
yofelsmartboyhw: are you actually sure it failed with gcc-4.6? because we do have 2.7.0 in the precise backports13:27
smartboyhwyofel, g++13:27
smartboyhwNot gcc13:27
yofelsame thing13:27
smartboyhwyofel, somebody give me the backlog13:28
smartboyhwo 2.7.013:28
smartboyhw*of13:28
yofeluh, look at the ppa?13:28
smartboyhwyofel, looking13:29
smartboyhwyofel, I think it's because I'm missing out some cmake things...13:31
smartboyhwYeah13:32
smartboyhwSorry:P13:34
yofelnah, backporting to precise isn't straight forward for most packages sadly :/13:36
smartboyhwyofel, uploaded a new version:P13:36
smartboyhwHmm, this time it's amd64 PPA build queue in busy state13:44
Quintasanherp13:52
Quintasan$8M is it13:52
afiestashey, is the akonadi systemtray still being installed by default?14:07
smartboyhwshadeslayer, is kscreen and libkscreen ready?14:08
shadeslayersmartboyhw: I was afk, I can upload now14:08
smartboyhwshadeslayer, great, afiestas :)14:08
smartboyhwOh, digikam is now officially 3.3.014:09
smartboyhwkubotu: newversion digikam 3.3.014:09
shadeslayersmartboyhw: file SRU bugs for raring?14:09
kubotuhttps://bugs.launchpad.net/bugs/120848214:10
smartboyhwshadeslayer, OK 14:11
smartboyhwshadeslayer, maybe just reuse the old bugs to upgrade the software version14:11
smartboyhwAnd nominate for Raring?14:11
smartboyhwkscreen and libkscreen has MRE available:)14:11
shadeslayersmartboyhw: yeah I suppose you could nominate those bugs for raring14:13
smartboyhwshadeslayer, you nominate;P14:14
smartboyhwI don't have the privileges...14:14
shadeslayerdone14:14
smartboyhwshadeslayer, I think it will be better if you prepare the SRU, you can upload directly:)14:15
smartboyhwI mean, I've done 1 SRU myself14:15
smartboyhwBut that one has nobody to upload at all:P14:15
shadeslayeruploaded for saucy14:15
smartboyhwUh oh, digikam download is real slow14:17
shadeslayeryou don't say14:18
shadeslayerwith the embedded libs and what not :)14:18
ScottKafiestas: It is.  Akonadi isn't reliable enough yet not to have it.14:18
ScottK(or if it isn't, it's a bug, IMO)14:19
afiestasScottK: then it is being installed?14:19
ScottKIt is in raring.  IDK for sure about saucy.  It should be.14:20
afiestasremoving of it was specifically recommended by kdepim-developers, and the by the time akonadi maintainer14:20
afiestasand from what I remember it was super evil, in one of the UDS I told you to remove it following Volker advice and iirc you said you would (and I remember seeing it gone)14:20
afiestasbut for some reason, it is on a friend's laptop and in my parent's (my parents laptop has been upgraded from previous versions)14:21
shadeslayer!find akonaditray saucy14:21
ubottuFile akonaditray found in app-install-data, edubuntu-artwork, kde-l10n-ar, kde-l10n-bs, kde-l10n-ca, kde-l10n-ca-valencia, kde-l10n-cs, kde-l10n-da, kde-l10n-de, kde-l10n-el (and 39 others) http://packages.ubuntu.com/search?searchon=contents&keywords=akonaditray&mode=&suite=saucy&arch=any14:21
shadeslayer!find /usr/bin/akonaditray saucy14:22
ubottuFile /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg14:22
shadeslayeryep, we ship it in saucy ^^14:22
ScottKafiestas: I use it on roughly a daily basis to restart akonadi stuff that's messed up.14:22
afiestasI compile everything, and I don't have it14:22
afiestasScottK: maybe you need to restart it daily because you are using it14:23
afiestasit was *super* evil iirc, and I haven't seen any change on it14:23
ScottKThen what's the alternative?14:23
ScottKakonadiconsole is super dangerous.14:23
afiestasakonadictl restart, I guess14:23
shadeslayer^^ which is what I use14:23
afiestasshadeslayer: so it is not in rarin?14:24
shadeslayerafiestas: it is14:24
shadeslayer!find /usr/bin/akonaditray raring14:24
ubottuFile /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg14:24
shadeslayerI'm merely saying that it is also present in saucy14:24
afiestasoks, can we check backwards?14:24
afiestasI do remember that you guys removed it and I remember agreeing on that in an UDS14:25
* shadeslayer checks precise and quantal14:25
afiestasshadeslayer: thanks14:25
ScottKIt's there.  I've used it since we switched to akonadi based pim.14:27
smartboyhwshadeslayer, so you want me to do the SRU or you?14:27
shadeslayerafiestas: ScottK I don't think precise has it, probably because 4.8.5 didn't have it?14:27
shadeslayersmartboyhw: I was reviewing the diffs14:28
afiestasshadeslayer: it did14:28
shadeslayeroh14:28
smartboyhwshadeslayer, oh 14:28
shadeslayer!find /usr/bin/akonaditray precise14:28
ubottuFile /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg14:28
shadeslayerstupid bot, didn't give me that reply in a query14:28
smartboyhw!find /usr/bin/akonaditray lucid 14:28
smartboyhwLOL14:28
ScottKshadeslayer: http://packages.ubuntu.com/search?suite=precise&arch=any&mode=exactfilename&searchon=contents&keywords=akonaditray14:28
shadeslayerright14:29
shadeslayerlike I said, didn't give me a hit in the query14:29
afiestaswait, maybe we removed it from being autostarted ?14:29
afiestashaving it packaged should be ok I guess, as long as it is not started automagically14:29
smartboyhwshadeslayer, BTW next time, don't upload kscreen and libkscreen at the same time:P14:30
afiestasif somebody like ScottK wants to use it, that's ok 14:30
shadeslayersmartboyhw: why not?14:30
shadeslayerafiestas: it's not started automatically here14:30
smartboyhwshadeslayer, because all the kscreen are now in dep-wait14:30
shadeslayersmartboyhw: and it'll resolve automatically14:30
smartboyhwshadeslayer, actually, how long does it take to automatically resolve?14:31
ScottKafiestas: Until akonadi is substantially more reliable, I think it's important to have a GUI way to restart it.14:31
ScottKIf that's not it, I'm happy to have another.14:31
shadeslayersmartboyhw: soonish after libkscreen is built14:31
smartboyhwshadeslayer, good:)14:31
afiestasScottK: you can bring that to kdepim-devel I guess, I know you are really frustrated with kdepim, but restarting akonadi is not the solution anyway14:38
ScottKI don't know what is?14:38
afiestasreporting bugs, providing feedback (specially now that we have a maintainer with time) etc14:39
afiestaswe went through a similar process with nepomuk, it turned out nice14:40
afiestasI trust same will happen now that Dan is a maintainer with time14:40
ScottKIt has steadily gotten better.14:41
ScottKBut in the mean time, I have to have working mail and when akonadi services get hung, it has to be restarted.14:42
shadeslayerScottK: btw do you have an idea why Nepomuk in Kubuntu uses unix odbc whereas Debian uses iodbc 14:49
shadeslayerI know we have a patch, but do you know the history behind it?14:49
ScottKYes.  I don't recall the details, but it was slangasek that did it.14:49
shadeslayerokay, opinions on going back to iodbc since that's what upstream recommends?14:50
* vHanda eaves14:50
vHanda*waves14:50
shadeslayerhey hey :)14:50
vHandaI read the entire bug report, and I'm not sure what to do now.14:50
shadeslayerI see, and why was this change introduced?14:51
vHandasome clashes with mysql or some other db. And since iodbc hadn't been updated in a couple of years they decided to drop it14:52
vHandaoverall, both work perfectly and they are supposed to 14:52
vHandabut I do get a lot of bug reports regarding high memory usage of virtuoso which I can reproduce, but they seem to happen more often with unixodbc. Anway, I haven't tested this properly14:52
shadeslayerany demerits to using unixodbc instead of iodbc?14:52
vHandaso just let the situation be14:53
shadeslayerokay then14:53
vHandaI'll bug you people if I find a convincing reason to switch - the main reason was that virtuoso maintains iodbc so it theoretically should work better14:53
vHandawith virtuoso14:53
yofelshadeslayer: for reference if you want to read through it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63930014:55
ubottuDebian bug 639300 in soprano "please build against unixodbc-dev instead of libiodbc2-dev" [Important,Open]14:55
shadeslayersmartboyhw: I'm waiting for kscreen to finish compiling on saucy then I'll upload to raring-proposed14:58
smartboyhwshadeslayer, oh great:)14:59
smartboyhwYes, digikam finally arrived14:59
smartboyhwI mean, to my computer:P15:00
shadeslayerfamous last words15:00
smartboyhwshadeslayer, LOL15:02
smartboyhwHmm, I can't install one of the build-dep15:03
yofeldid they add yet another thing?15:13
smartboyhwyofel, no15:14
smartboyhwIt's my fault obviously:P15:14
=== ajcortes is now known as jjg1965
shadeslayersmartboyhw: libkscreen uploaded for raring-proposed15:17
* shadeslayer forgot to subscribe ubuntu-sru to the bug -.-15:17
smartboyhwshadeslayer, whoa~!15:17
shadeslayerwait15:17
smartboyhwshadeslayer, kscreen is just waiting to migrate:P15:17
smartboyhwshadeslayer, don't forget: kscreen and libkscreen has a MRE15:17
shadeslayerScottK: is subscribtion still necessary even though we have an MRE now?15:17
* shadeslayer subscribes anyway15:23
ScottKBetter to do so.15:24
shadeslayerright, done already, waiting for you in the queue :)15:24
ScottKshadeslayer: Before I accept this one, can we get 1.0-0ubuntu1~ubuntu13.04.1 verified?15:30
shadeslayer1.0 is still in -proposed :S15:35
ScottKYes.  No one verified it.15:36
shadeslayerScottK: okay, good thing VBox has a feature to add number of monitors, testing using that 15:37
smartboyhwWell, I will close the Doodle poll tomorrow night probably15:56
smartboyhwFor now, good night guys. Tomorrow you will see digikam 3.3.0 (final) packaged from me....15:57
smartboyhwAnd also, fiddling with opencolorio:P15:57
smartboyhw(For calligra 2.7.1)15:57
shadeslayerScottK: kscreen works, please move to updates15:59
debfxhm those time slots aren't very europe-friendly15:59
ScottKshadeslayer: Please say so in the bug.  Bug #1195806 16:01
ubottubug 1195806 in libkscreen (Ubuntu Raring) "libkscreen and kscreen SRU to raring" [Undecided,Fix committed] https://launchpad.net/bugs/119580616:01
smartboyhwdebfx, but I need to make it Asian-friendly...16:01
shadeslayerScottK: already done16:01
smartboyhwAnd it's Europe friendly already......16:01
smartboyhwIt's afternoon for you guys16:01
shadeslayersmartboyhw: it's not asian friendly tbh :P16:01
smartboyhwshadeslayer, yes16:01
smartboyhwBut, I need to fit the Europeans:P16:01
shadeslayerfor me it's late in the evening16:02
smartboyhwshadeslayer, me too you don't think16:02
shadeslayeryeah ;)16:02
smartboyhwshadeslayer, when is 13:00 UTC for you?16:02
debfxafternoon? the first slot is 9-10 am16:02
shadeslayer18:3016:02
smartboyhwshadeslayer, for me it's 21:3016:02
shadeslayer^_^16:02
smartboyhwOops, 21:0016:02
smartboyhwdebfx, well it's sort of European-friendly already....16:02
smartboyhwIt's morning16:03
smartboyhwI can't even make it after the last time slot16:03
shadeslayerdon't disturb debfx's sleep :P16:03
smartboyhwshadeslayer, :P16:03
ScottKshadeslayer: Where's kscreen?16:03
shadeslayerScottK: I haven't uploaded that yet, I went for dinner after uploading kscreen16:03
debfxnow I'm confused. looks like doodle ignored my time zone setting16:03
yofeldebfx: 9am? first slot is 1PM16:03
smartboyhwshadeslayer, you mean libkscreen...16:03
yofelUTC16:03
smartboyhwdebfx, LOL16:03
ScottKOK.16:03
shadeslayerwhat smartboyhw said16:03
shadeslayeruploading kscreen now16:04
ScottKAnd marking up the bug for the last one?16:04
debfxyeah it asked me for my time zone and then ignored what I selected :/16:04
yofelmeh16:04
smartboyhwdebfx, LOL16:04
shadeslayerScottK: last one?16:04
smartboyhwAnyways, is it European-friendly now? ;)16:04
ScottKBug #1195806 16:04
ubottubug 1195806 in libkscreen (Ubuntu Raring) "libkscreen and kscreen SRU to raring" [Undecided,Fix committed] https://launchpad.net/bugs/119580616:04
debfxyes indeed :)16:04
ScottKYou didn't say you tested it and mark it verification done.16:05
shadeslayerScottK: commented, fixed the tag16:05
ScottKOK16:05
smartboyhwIt might NOT be American-friendly though.... Sigh16:05
yofelsmartboyhw: still working on digikam or did your pc overheat already? ^^16:05
shadeslayersmartboyhw: can't be helped16:06
smartboyhwyofel, it's sleep time. Digikam work done actually16:06
smartboyhwMaybe you want me to upload?16:06
smartboyhwto PPA ofc16:06
yofeljust commit to bzr and I'll look at it16:06
smartboyhwyofel, sure16:06
smartboyhwThank you debfx 16:07
smartboyhwEh, now the most popular selection is Monday....16:07
smartboyhwuh oh16:07
shadeslayerScottK: kscreen up as well16:13
smartboyhwyofel, done.16:13
smartboyhwGood night16:13
shadeslayersmartboyhw: ^^16:13
ScottKOK.16:14
=== ajcortes is now known as jjg1965
ScottKafiestas: Why did you remove class AbstractBackend from src/configmonitor.h in libkscreen 1.0.1?  Is that a binary compatible change?16:15
afiestasScottK: we don't keep binary comnpatibility16:15
ScottKBTW, 1.0 is released to updates.16:15
afiestasand we haven't removed it I think :s16:16
afiestasat least not in prupose :/16:16
ScottKIt is in other files, but that being remove from src/configmonitor.h is in the diff.16:16
afiestasthe include?16:16
shadeslayerScottK: I think it's a forward include16:16
shadeslayerafiestas: https://launchpadlibrarian.net/146842526/libkscreen_1.0-0ubuntu1~ubuntu13.04.1_1.0.1-0ubuntu1~ubuntu13.04.1.diff.gz16:17
ScottKafiestas: see the end of http://launchpadlibrarian.net/146842526/libkscreen_1.0-0ubuntu1~ubuntu13.04.1_1.0.1-0ubuntu1~ubuntu13.04.1.diff.gz16:17
shadeslayerlast line16:17
ScottKYeah.16:17
shadeslayerScottK: yeah, from what I understand it's a forward include and can be dropped16:17
ScottKafiestas: It's fine not to keep binary compatibility, but you need to bump the so name when you don't.16:17
afiestaswe did I think16:22
afiestas1.0.1, no?16:22
afiestasor 1.1 is required if we break it?16:22
yofelafiestas: on ABI breakage you would have to bump the SOVERSION, for you that's libkscreen_VERSION_MAJOR16:56
yofelbut we're fine here as fas Howard was concerned16:56
yofel*as far as16:57
afiestaswe bump the minor, isn;t that enough?16:58
afiestasI don't want to end up with soversion 2516:58
afiestasand call it libkscreen 2.016:58
yofelno, it wouldn't be enough for a BIC change16:59
yofeland libkscreen is at 22...17:00
yofeler17:00
yofellibkdcraw17:00
yofelbut ok, bad example17:00
yofelafiestas: nothing prevents you from using longer SOVERSION's though... libattica has '0.4'17:01
afiestasso, from 1.0.1 to 1..0.1 iok?17:05
yofelyou're mixing VERSION and SOVERSION, you can set VERSION to whatever you want, SOVERSION only needs to change if you remove symbols from the library 17:07
yofelcurrent SOVERSION is '1'17:07
=== dantti_laptop|2 is now known as dantti_laptop
afiestasoh I thought we had it unified17:13
yofelit is partly, first part of the VERSION is the SOVERSION, you if you change the libkscreen version to 2.0.0 you change the SOVERSION17:14
yofelnot sure if that coupling make sense, but it's ok as long as the ABI isn't broken in between17:15
shadeslayerhm, is there a way we can express this in a install file : "Install everything under /usr except for these 2 files"17:16
yofelshadeslayer: 'rm' in rules17:19
shadeslayernah, that's fairly less than ideal17:20
yofelwell, then you can just add all files except for the 2 you want to install to the install file17:21
yofelthat's the debian way17:21
* yofel would prefer that anyway17:21
=== rdieter_ is now known as rdieter
ScottKlibkscreen/kscreen accepted for raring17:57
shadeslayerScottK: thx18:00
yofeldo we have a todo list for all those MRE's we got?18:00
yofelor do we actually have the full list documented somewhere?18:01
ScottKAFAIK, no TODO.  The full list is on the MRE wiki page.18:01
yofelok, thanks18:01
=== sayakb_ is now known as sayakb
ScottKafiestas and shadeslayer: I did some investigation and I can restart failed akonadi services from within kmail --> settings --> configure kmail, so no objection to dumping akonaditray.19:03
soeesomeone can look at some crash report ?20:27
soeehttp://pastebin.com/azpWgDuH20:27
valorieinteresting, I just ran update and upgrade, and kscreen was held back23:53
Riddellvalorie: hmm Quintasan said that I think23:55
RiddellI'm pretty sure I checked and the replaces/breaks was correct23:55
valorielaunchpad might just be slow or something23:58
valoriedang it, no ahoneybun23:58
valoriethat article gave highest marks to bodhi linux for their documentation, so I looked it up: http://www.bodhilinux.com/mob_documentation.php23:59
valorieit is very well organized and cute23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!