=== Guest84363 is now known as wgrant [04:03] Whoohoo my main PPA is now 6GiB:) [04:11] Damn, quantal 4.10.97 is now just last step away from ready, but I just can't make kate and pykde4 happy... [05:13] smartboyhw: 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 work [05:23] shadeslayer, uh [05:23] OK:P [05:23] did someone setup a doodle? [05:23] Then the wiki page really needs an update [05:24] shadeslayer, let me go and setup one [05:24] if not I can send an email out regarding that since Riddell is out [05:24] smartboyhw: cool [05:26] shadeslayer, where should we hold the meeting? [05:26] Here or #ubuntu-meeting? [05:26] here is usual [05:27] shadeslayer: we all thought you were crap, but we liked you so much we let you in :P :P :P :P : P :P [05:27] pffff [05:27] jussi, LOL [05:27] pffffff [05:27] :) [05:28] * jussi hugs shadeslayer [05:28] * shadeslayer huggles jussi back [05:28] Please enter a value. [05:28] What!?!? [05:28] jussi: oh and btw, you've lost alot of weight :O [05:28] I can't even set the title......\ [05:28] jussi: or maybe you just look good in the camera :P [05:28] shadeslayer: 13 kg [05:29] jussi: congrats :D [05:29] shadeslayer: still about 10 to go [05:29] jussi: is that Elodi's doing :P [05:29] keeping you up at night, making you run after her etc [05:29] shadeslayer: no, its just my love of bacon... m Im on a bacon diet! :D [05:29] there's a bacon *diet* ? :D [05:30] not quite, but my diet includes bacon... [05:30] I started in feb, and Ive now lost 13kg. I wonder what ill look like in feb next year [05:31] * shadeslayer needs to start working out as well, I've gotten so fat -.- [05:31] hehe [05:32] shadeslayer: 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 easier [05:33] oh [05:33] I'm not as big as you yet, I can still start [05:33] I'm just lazy ... [05:35] shadeslayer: ++ I know that feeling, careful or youll end up as big as i was [05:35] jussi: yeah, hopefully will be better once I move [05:36] shadeslayer: where are you moving to ? finally coming to join me here in .fi? [05:36] He'd freeze in a week. [05:36] Even in summer. [05:37] haha [05:37] ScottK: come on, we had 30C yesterday! [05:37] ScottK, shadeslayer you should have received an invitation of the Doodle poll now. I shall post the public address to kubuntu-devel mailin list soon [05:38] jussi: I'm planning to acclimatize to Barcelona first :P [05:38] got it [05:39] Didn't get it yet, but I greylist, so it's not surprising. [05:43] ScottK, I used ubuntu@kitterman.com [05:44] Thank you shadeslayer [05:45] oh drat, I did not factor in various other meetings into my doodle stuff [05:45] * shadeslayer goes back to change [05:49] Doodled. [05:52] shadeslayer, sure [05:52] ScottK, thanks [05:53] Whoa, it looks like 13:00 UTC of 9th (Fri) is the most popular right now === 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 [05:59] good morning [06:21] http://fossforce.com/2013/07/whats-your-favorite-foss-or-linux-blog/ - Martin's blog is leading [07:57] yofel: http://paste.kde.org/p61a77235/ [07:57] yofel: that's for precise [08:00] sigh [08:00] silly kde, why do you show everyone whats on my screen when waking up? [08:11] porn leakage? [08:11] jussi: given how "unstandard" ubuntu's sleeping methods are i would not blame kde apps so quickly [08:11] apachelogger: no, work laptop. [08:11] tsdgeos: heh... I guess. in any case, Kubuntu has a bug [08:12] you know [08:12] I still think we should simply adopt systemd :P [08:12] ^^ [08:12] and make it not crippled [08:12] cuz the upstart-logind bastard child of hell seems to not be so great :P [08:13] apachelogger: put it in the agenda for the meeting? [08:13] what meeting? [08:13] apachelogger: topic :D [08:13] ^^ [08:14] wait what [08:14] it's in the topic too [08:14] dafuq [08:14] * jussi hugs apachelogger [08:14] apachelogger: sounds like you need a coffee... [08:14] so I was out for the weekend and today I turn on the magic box which makes light come out of this very dark mirror [08:14] and I look at my mail [08:15] and there's 3 threads about smartboyhw's membership thing [08:15] and now I also find it on IRC [08:15] shadeslayer: hm, that's better than what I got [08:15] yofel: oh [08:15] tales from "how to make apachelogger not care" :P [08:15] though amarok and kde-workspace don't belong on the removal list [08:15] you don't say :P [08:15] ^^ [08:16] xserver-xorg [08:16] that seems x driven though [08:16] libgl1-mesa-dri or that maybe, seeing as X possibly deps on that [08:16] ah [08:16] now I get it [08:17] we are pulling in the lts enablement stack? [08:17] yes [08:17] aaaaahhhhhhhhh [08:17] yes, linkage seems kaput in workspace then [08:17] kwin wants regular x, doesn't get it, goes away [08:18] checking [08:19] amarok doesn't quite make sense though [08:20] at least on raring it doesn't have any deps on any other package marked for removal [08:22] deps libx11-6, which may or may not be the cause here [08:23] Don't think it's libx11 [08:23] because there is no libx11 LTS backport [08:24] well, there's nothing else :P [08:26] * apachelogger hates writing changelogs -.- [08:26] shadeslayer: actually you could just let apt tell you :P [08:26] apt-get -o Debug::pkgProblemResolver=yes dist-upgrade [08:26] or somesuch business [08:26] right [08:27] *nod* [08:28] smartboyhw: uh, the pykde build failure is pretty clear though, python-qt4 depends on sip-api-8.1, while python-sip provides sip-api-10.0 [08:29] you python-qt4 is too old [08:29] *your [08:30] doodled btw. [08:31] http://paste.kde.org/p1ee7c81a/ [08:38] we need to rebuild amarok against the new HWE stack as well I think [08:38] oh right [08:38] I'll backport the beta [08:38] 2.7 crashes with 4.11 anyway [08:38] ack [08:39] * shadeslayer looks at kde-workspace then [08:40] aha [08:40] Broken kde-window-manager-common:amd64 Depends on libgl1-mesa-glx [ amd64 ] < 8.0.4-0ubuntu0.6 > ( libs ) [08:42] dpkg-shlibdeps is fun, isn't it? [08:43] ^^ [08:47] $ cat debian/libgl1-mesa-glx-lts-raring.shlibs [08:47] libGL 1 libgl1-mesa-glx | libgl1 [08:47] smartboyhw: yes [08:47] uhm [08:47] *facedesk* [08:48] I think we need to ask the X folks how this is *supposed* to work [08:48] * shadeslayer pokes X people [09:18] so... [09:18] we have the choice between 2 not recommended things we can do :/ [09:20] a) default to mesa 8 (not recommended by martin) [09:20] b) explicitely pull in the mesa stack with manual depends (not recommened by ubuntu-x) [09:21] do a) and ask users to install the lts stack? [09:21] probably the best solution indeed, at least it's the one with the least amount of breakage potential [09:22] yep ^^ [09:22] only that this means we get to upload everything again [09:23] well, shouldn't be much of an issue [09:23] but qt and meta need to be fixed too [09:23] *nod* [09:23] oh [09:23] yofel: can't we just make meta depend on the LTS stack [09:23] well, it already *does* [09:23] doesn't help [09:24] uhm right [09:24] oh? [09:24] The following packages will be REMOVED: [09:24] ... kubuntu-desktop kubuntu-full [09:24] :/ [09:24] yofel: but isn't that because of kde-window-manager [09:25] so if we fix everything to build against regular mesa, but make the meta package depend on the HWE stack [09:25] then during the upgrade it'll pull in the new HWE stack [09:25] it'll remove the meta packages on upgrade. But that would at least provide an easy way to install the HWE stack [09:26] that's what kubuntu-lts-backport is supposed to do currently [09:27] but just trying to install that ends up with [09:27] kubuntu-lts-backport : Depends: xserver-xorg-lts-raring but it is not going to be installed [09:27] o_o [09:29] shadeslayer: 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 stack [09:29] yofel: yeah, that's what was going through my mind as well [09:30] then lets go with that. I'll upload a qt rebuild [09:30] but didn't you just say that kubuntu-lts-backport isn't installable? [09:31] no here, and 'apt-get install kubuntu-lts-backport xserver-xorg-lts-raring' results in: http://paste.kde.org/pbb07556c [09:31] *not here [09:32] but that package doesn't really do much right now: [09:32] kubuntu-lts-backport [09:32] Depends: linux-image-generic-lts-raring [09:32] Depends: xserver-xorg-lts-raring [09:33] and I think we'll need at least the manual dependencies on mesa [09:34] apt-get install kubuntu-lts-backport libgl1-mesa-glx-lts-raring [09:34] looks much better [09:42] qt uploaded [09:43] ack [09:44] I suppose I could go for a quick nap :P [09:44] go ahead, this'll take 4h ^^ [09:44] shadeslayer: or have a swordfight... :D http://xkcd.com/303/ [09:45] jussi: oh that was this morning [09:45] haha [09:45] when Qt tests were running :) [09:48] apachelogger, yofel sorry for spamming mailing list [09:48] yofel, yeah I know.. [09:48] afiestas, oh good:) [09:48] what about the ML? [09:49] yofel, I mean apachelogger receiving 3 emails:P [09:49] ah [09:49] well, in all fairness, I am important like that [09:49] apachelogger, yes, you are VERY important:) [09:50] I am now working 3 hours and am still reading backmail from the weekend [09:50] quite the drag -.- [09:51] apachelogger, where's kubotu? [09:52] vacation [09:52] apachelogger, ..... [09:52] If you would kindly make it back? [09:53] smartboyhw: as soon as a package reaches the ftp, it means it is ready for download/package/etc [09:53] afiestas, yeah, I've packaged it here already:) [09:53] I haven't announce it (or Dan) because we are busy [09:53] awesome! thanks [09:53] hm [09:54] can I get an update of Kubuntu freeze? [09:54] I'd like to release KScreen 1.1 before it [09:54] afiestas, Kubuntu Freeze? You mean, Feature Freeze? [09:54] jussi, tsimpson: didn't we have an upstart/init.d script for kubotu? [09:54] * apachelogger kubuntu freezes afiestas [09:54] apachelogger, +1 [09:54] August 29th [09:54] Warning /!\ FeatureFreeze, Beta 1 Freeze (for opt-in flavors) [09:54] apachelogger: we don't [09:54] tsimpson: curious [09:54] afiestas, FeatureFreeze and Beta1Freeze is on August 29th [09:55] I guess I should write one then ^^ [09:55] you can create a cron job too/instead [09:55] if you do write an upstart job, I'd like that :) [09:56] same amount of work as the trick is figuring out how to get a screen with kubotu started as my user [09:56] which is why I thouht we had a script because I definitely remember working on that [09:56] oh well [09:56] also, we'll be moving ubottu.com to 13.04 soon (as soon as I get everything transferred to the new server) [09:56] at least manually starting kubotu gives me the chance to update it every once in a while ^^ [09:57] kubotu: newversion libkscreen 1.0.1 [09:57] HAHAHA [09:57] https://bugs.launchpad.net/bugs/1208409 [09:58] kubotu: hey [09:58] morning apachelogger :D [09:59] kubotu: newversion kscreen 1.0.1 [10:00] https://bugs.launchpad.net/bugs/1208413 [10:01] apachelogger: you can pass -b when starting the bot to background it too, so no need for screen [10:02] -queuebot/#ubuntu-release- Unapproved: accepted ibus-cangjie [source] (raring-proposed) [0.0.1~git20130325-0ubuntu1.1] [10:02] Oops, wrong chan:P [10:02] * smartboyhw is supposed to post it in another one, sorry folks [10:08] yofel, any time to review kscreen and libkscreen? [10:08] It's in https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+packages [10:08] (A new PPA:P) [10:09] Hmm, why are you guys more free on Fridays? :O [10:15] tsimpson: yes, but I like having it on a screen :P [10:15] hm, 4.12 beta releases happen within one week [10:15] ok then [10:15] it's an OCD thing ^^ [10:15] not sure if that's enough time to get them out quickly enough :/ [10:16] not to mention Kubuntu get's about 15 days of upstream support \o/ [10:16] ( assuming Kubuntu is released in the middle of April ) [10:17] for an LTS release that sounds awesome [10:17] fails to compute [10:17] http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule [10:17] Tuesday, April 29 2014: KDE 4.12.5 release [10:19] oh actually, if previous release is any indication, the x.04 release is made towards the end of the month [10:30] shadeslayer: less time between releases also means less changes we need to take into account [10:31] so I think it would work (for beta2+) [10:31] right, just saying that by the time we'll be done with beta 1 , beta 2 will be close to tagging [10:31] shadeslayer, as in 4.11 anyway [10:32] yofel, will you review kscreen? [10:32] nope [10:32] and libkscreen ofc [10:32] shadeslayer: not in the next 6h [10:32] Beta 1 and Beta 2 had 2 weeks in between them [10:32] er, smartboyhw^ [10:32] I can have a look [10:32] shadeslayer, great [10:32] yeah, 1 week is a bit short [10:33] shadeslayer, they are in https://launchpad.net/~smartboyhw/+archive/packaging-staging-1/+packages [10:33] considering we need at least 2 days to actually get the beta out [10:33] I am not sure why Riddell didn't send the suggestions we decided on to the ML [10:33] leaves at most 5 days for testing [10:33] 2 days? hah, first Beta usually takes alot more time [10:33] new deps, new files and what not [10:33] yofel, how long did we take to get Beta 1 ou? [10:33] in *saucy*, not saucy+1 because that needs another 2 days or so until it's through -proposed [10:33] in 4.11? [10:34] well, 4.12 comes out post saucy release [10:34] that's what I was talking about [10:34] sure, I'm talking about testing [10:34] uhm, last 2 sentences make no sense :P [10:34] well, we can do the beta backports *fast* [10:34] 4.12 comes out post saucy, so we put it in saucy + 1 first [10:34] building in saucy+1 archive takes longer [10:34] so less testing in the dev release [10:35] right [10:35] that's all I said [10:35] *nod* [10:35] backporting is fast [10:35] beta1 packaging takes about a week usually, which is why I said beta2+ [10:35] beta1 will never see a release in kubuntu with *that* schedule I fear [10:36] afiestas: tsdgeos ^^ [10:36] and upstream will get loads of bug reports post 14.04 release [10:36] but that's an estimate based on recent experience [10:36] nothing we can do about that as well [10:36] are there git moves planned for 4.12? [10:36] (kdewebdev?) [10:37] shadeslayer: thought luck for you i guess :D [10:38] let's delay the world because i'm slow! [10:38] So, we will be uploading to devel soon... [10:38] Probably saucy+1 [10:38] if we don't have git splitups we can do beta1 within 4 days I believe [10:38] The *rolling release* symlink thing. [10:39] smartboyhw: wasn't that meant to be an *additional* target? [10:39] shadeslayer: 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] tsdgeos: depends entirely on how much you change :P [10:39] smartboyhw: though unification would make sense I guess [10:39] yofel, well it seems like we can upload to it [10:39] if there are alot of changes, then it'll take time [10:39] shadeslayer: well, we have kdelibs and kde-workspace frozen [10:39] You can still ofc upload to saucy, saucy+1 [10:40] yofel: right, but there are like a bazillion other things [10:40] not that much, if anything it's finding out what dependencies need to be updated [10:40] that easily causes a day of delay [10:40] though we could do that *before* beta1 really [10:43] Going for a swim.. [10:43] Riddell, please vote on the Trello:P [10:43] tsdgeos: 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] Considering we only have 1 week to work with them such a delay becomes a problem [10:46] smartboyhw: diffs look sane to me [10:46] smartboyhw: will upload once they're built [10:54] smartboyhw: vote on trello? [10:58] Riddell: he probably meant doodle [11:01] ok done [11:06] Riddell: and what happened to the suggestion we made regarding having a growing period between bug fix releases? [11:06] growing period? [11:07] yeah, like 4.12.1 3 weeks after 4.12, 4.12.2 6 weeks after 4.12.1 [11:07] so on and so forth [11:07] oh that [11:07] dunno [11:09] *shrug* as long as I don't have to deal with bug reports and all of them go upstream ;) [11:09] shadeslayer: sure, all of them will be RESOLVED EOL though === vinay is now known as Guest26148 [11:10] well, probably not [11:10] but still [12:30] Riddell, thank you! [12:31] Hmm, probably 16th 13:00 UTC then..... [12:36] Riddell, is it that you wanted a news release for calligra 2.7.1? It has migrated into -release now [12:49] smartboyhw: oh cool if it's migrated and raring and precise are done then go for it [13:02] Riddell, no precise sorry [13:03] It can't work without g++-4.7 [13:03] I can only do Quantal [13:07] Hey folks [13:08] Riddell: Do we support things like 12.04 -> 13.04? [13:08] or it's only LTS -> LTS upgrades that we support? [13:14] Quintasan: update-manager -d will take you out of the lts→lts [13:14] davmor2: I might be dumb but wouldn't -d install saucy? [13:15] Current development release is saucy iirc [13:15] Quintasan: d'oh yeap sorry [13:15] Quintasan: it in software-properties-gtk for me on ubuntu so I'm assuming there is a qt version maybe? [13:16] /win 17 [13:16] highvoltage, !? [13:19] davmor2: I see. I forgot about that, thanks. [13:19] Quintasan: http://ubuntuone.com/0us1fr5yKrdhJ3YTWIcBmp [13:25] MMm [13:25] http://www.techradar.com/news/software/operating-systems/ubuntu-derivatives-5-of-the-best-ubuntu-based-distros-1170314 [13:25] We are only at No.3 behind Ubuntu GNOME and Bodhi Linux... [13:25] Oh no, it's 4th:( [13:26] Ah, it's actually score damn:P [13:26] 4/5 that's quite good [13:27] smartboyhw: are you actually sure it failed with gcc-4.6? because we do have 2.7.0 in the precise backports [13:27] yofel, g++ [13:27] Not gcc [13:27] same thing [13:28] yofel, somebody give me the backlog [13:28] o 2.7.0 [13:28] *of [13:28] uh, look at the ppa? [13:29] yofel, looking [13:31] yofel, I think it's because I'm missing out some cmake things... [13:32] Yeah [13:34] Sorry:P [13:36] nah, backporting to precise isn't straight forward for most packages sadly :/ [13:36] yofel, uploaded a new version:P [13:44] Hmm, this time it's amd64 PPA build queue in busy state [13:52] herp [13:52] $8M is it [14:07] hey, is the akonadi systemtray still being installed by default? [14:08] shadeslayer, is kscreen and libkscreen ready? [14:08] smartboyhw: I was afk, I can upload now [14:08] shadeslayer, great, afiestas :) [14:09] Oh, digikam is now officially 3.3.0 [14:09] kubotu: newversion digikam 3.3.0 [14:09] smartboyhw: file SRU bugs for raring? [14:10] https://bugs.launchpad.net/bugs/1208482 [14:11] shadeslayer, OK [14:11] shadeslayer, maybe just reuse the old bugs to upgrade the software version [14:11] And nominate for Raring? [14:11] kscreen and libkscreen has MRE available:) [14:13] smartboyhw: yeah I suppose you could nominate those bugs for raring [14:14] shadeslayer, you nominate;P [14:14] I don't have the privileges... [14:14] done [14:15] shadeslayer, I think it will be better if you prepare the SRU, you can upload directly:) [14:15] I mean, I've done 1 SRU myself [14:15] But that one has nobody to upload at all:P [14:15] uploaded for saucy [14:17] Uh oh, digikam download is real slow [14:18] you don't say [14:18] with the embedded libs and what not :) [14:18] afiestas: It is. Akonadi isn't reliable enough yet not to have it. [14:19] (or if it isn't, it's a bug, IMO) [14:19] ScottK: then it is being installed? [14:20] It is in raring. IDK for sure about saucy. It should be. [14:20] removing of it was specifically recommended by kdepim-developers, and the by the time akonadi maintainer [14:20] and 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:21] but 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] !find akonaditray saucy [14:21] File 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=any [14:22] !find /usr/bin/akonaditray saucy [14:22] File /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg [14:22] yep, we ship it in saucy ^^ [14:22] afiestas: I use it on roughly a daily basis to restart akonadi stuff that's messed up. [14:22] I compile everything, and I don't have it [14:23] ScottK: maybe you need to restart it daily because you are using it [14:23] it was *super* evil iirc, and I haven't seen any change on it [14:23] Then what's the alternative? [14:23] akonadiconsole is super dangerous. [14:23] akonadictl restart, I guess [14:23] ^^ which is what I use [14:24] shadeslayer: so it is not in rarin? [14:24] afiestas: it is [14:24] !find /usr/bin/akonaditray raring [14:24] File /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg [14:24] I'm merely saying that it is also present in saucy [14:24] oks, can we check backwards? [14:25] I do remember that you guys removed it and I remember agreeing on that in an UDS [14:25] * shadeslayer checks precise and quantal [14:25] shadeslayer: thanks [14:27] It's there. I've used it since we switched to akonadi based pim. [14:27] shadeslayer, so you want me to do the SRU or you? [14:27] afiestas: ScottK I don't think precise has it, probably because 4.8.5 didn't have it? [14:28] smartboyhw: I was reviewing the diffs [14:28] shadeslayer: it did [14:28] oh [14:28] shadeslayer, oh [14:28] !find /usr/bin/akonaditray precise [14:28] File /usr/bin/akonaditray found in kdepim-runtime, kdepim-runtime-dbg [14:28] stupid bot, didn't give me that reply in a query [14:28] !find /usr/bin/akonaditray lucid [14:28] LOL [14:28] shadeslayer: http://packages.ubuntu.com/search?suite=precise&arch=any&mode=exactfilename&searchon=contents&keywords=akonaditray [14:29] right [14:29] like I said, didn't give me a hit in the query [14:29] wait, maybe we removed it from being autostarted ? [14:29] having it packaged should be ok I guess, as long as it is not started automagically [14:30] shadeslayer, BTW next time, don't upload kscreen and libkscreen at the same time:P [14:30] if somebody like ScottK wants to use it, that's ok [14:30] smartboyhw: why not? [14:30] afiestas: it's not started automatically here [14:30] shadeslayer, because all the kscreen are now in dep-wait [14:30] smartboyhw: and it'll resolve automatically [14:31] shadeslayer, actually, how long does it take to automatically resolve? [14:31] afiestas: Until akonadi is substantially more reliable, I think it's important to have a GUI way to restart it. [14:31] If that's not it, I'm happy to have another. [14:31] smartboyhw: soonish after libkscreen is built [14:31] shadeslayer, good:) [14:38] ScottK: you can bring that to kdepim-devel I guess, I know you are really frustrated with kdepim, but restarting akonadi is not the solution anyway [14:38] I don't know what is? [14:39] reporting bugs, providing feedback (specially now that we have a maintainer with time) etc [14:40] we went through a similar process with nepomuk, it turned out nice [14:40] I trust same will happen now that Dan is a maintainer with time [14:41] It has steadily gotten better. [14:42] But in the mean time, I have to have working mail and when akonadi services get hung, it has to be restarted. [14:49] ScottK: btw do you have an idea why Nepomuk in Kubuntu uses unix odbc whereas Debian uses iodbc [14:49] I know we have a patch, but do you know the history behind it? [14:49] Yes. I don't recall the details, but it was slangasek that did it. [14:50] okay, opinions on going back to iodbc since that's what upstream recommends? [14:50] * vHanda eaves [14:50] *waves [14:50] hey hey :) [14:50] I read the entire bug report, and I'm not sure what to do now. [14:51] I see, and why was this change introduced? [14:52] some clashes with mysql or some other db. And since iodbc hadn't been updated in a couple of years they decided to drop it [14:52] overall, both work perfectly and they are supposed to [14:52] but 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 properly [14:52] any demerits to using unixodbc instead of iodbc? [14:53] so just let the situation be [14:53] okay then [14:53] I'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 better [14:53] with virtuoso [14:55] shadeslayer: for reference if you want to read through it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639300 [14:55] Debian bug 639300 in soprano "please build against unixodbc-dev instead of libiodbc2-dev" [Important,Open] [14:58] smartboyhw: I'm waiting for kscreen to finish compiling on saucy then I'll upload to raring-proposed [14:59] shadeslayer, oh great:) [14:59] Yes, digikam finally arrived [15:00] I mean, to my computer:P [15:00] famous last words [15:02] shadeslayer, LOL [15:03] Hmm, I can't install one of the build-dep [15:13] did they add yet another thing? [15:14] yofel, no [15:14] It's my fault obviously:P === ajcortes is now known as jjg1965 [15:17] smartboyhw: libkscreen uploaded for raring-proposed [15:17] * shadeslayer forgot to subscribe ubuntu-sru to the bug -.- [15:17] shadeslayer, whoa~! [15:17] wait [15:17] shadeslayer, kscreen is just waiting to migrate:P [15:17] shadeslayer, don't forget: kscreen and libkscreen has a MRE [15:17] ScottK: is subscribtion still necessary even though we have an MRE now? [15:23] * shadeslayer subscribes anyway [15:24] Better to do so. [15:24] right, done already, waiting for you in the queue :) [15:30] shadeslayer: Before I accept this one, can we get 1.0-0ubuntu1~ubuntu13.04.1 verified? [15:35] 1.0 is still in -proposed :S [15:36] Yes. No one verified it. [15:37] ScottK: okay, good thing VBox has a feature to add number of monitors, testing using that [15:56] Well, I will close the Doodle poll tomorrow night probably [15:57] For now, good night guys. Tomorrow you will see digikam 3.3.0 (final) packaged from me.... [15:57] And also, fiddling with opencolorio:P [15:57] (For calligra 2.7.1) [15:59] ScottK: kscreen works, please move to updates [15:59] hm those time slots aren't very europe-friendly [16:01] shadeslayer: Please say so in the bug. Bug #1195806 [16:01] bug 1195806 in libkscreen (Ubuntu Raring) "libkscreen and kscreen SRU to raring" [Undecided,Fix committed] https://launchpad.net/bugs/1195806 [16:01] debfx, but I need to make it Asian-friendly... [16:01] ScottK: already done [16:01] And it's Europe friendly already...... [16:01] It's afternoon for you guys [16:01] smartboyhw: it's not asian friendly tbh :P [16:01] shadeslayer, yes [16:01] But, I need to fit the Europeans:P [16:02] for me it's late in the evening [16:02] shadeslayer, me too you don't think [16:02] yeah ;) [16:02] shadeslayer, when is 13:00 UTC for you? [16:02] afternoon? the first slot is 9-10 am [16:02] 18:30 [16:02] shadeslayer, for me it's 21:30 [16:02] ^_^ [16:02] Oops, 21:00 [16:02] debfx, well it's sort of European-friendly already.... [16:03] It's morning [16:03] I can't even make it after the last time slot [16:03] don't disturb debfx's sleep :P [16:03] shadeslayer, :P [16:03] shadeslayer: Where's kscreen? [16:03] ScottK: I haven't uploaded that yet, I went for dinner after uploading kscreen [16:03] now I'm confused. looks like doodle ignored my time zone setting [16:03] debfx: 9am? first slot is 1PM [16:03] shadeslayer, you mean libkscreen... [16:03] UTC [16:03] debfx, LOL [16:03] OK. [16:03] what smartboyhw said [16:04] uploading kscreen now [16:04] And marking up the bug for the last one? [16:04] yeah it asked me for my time zone and then ignored what I selected :/ [16:04] meh [16:04] debfx, LOL [16:04] ScottK: last one? [16:04] Anyways, is it European-friendly now? ;) [16:04] Bug #1195806 [16:04] bug 1195806 in libkscreen (Ubuntu Raring) "libkscreen and kscreen SRU to raring" [Undecided,Fix committed] https://launchpad.net/bugs/1195806 [16:04] yes indeed :) [16:05] You didn't say you tested it and mark it verification done. [16:05] ScottK: commented, fixed the tag [16:05] OK [16:05] It might NOT be American-friendly though.... Sigh [16:05] smartboyhw: still working on digikam or did your pc overheat already? ^^ [16:06] smartboyhw: can't be helped [16:06] yofel, it's sleep time. Digikam work done actually [16:06] Maybe you want me to upload? [16:06] to PPA ofc [16:06] just commit to bzr and I'll look at it [16:06] yofel, sure [16:07] Thank you debfx [16:07] Eh, now the most popular selection is Monday.... [16:07] uh oh [16:13] ScottK: kscreen up as well [16:13] yofel, done. [16:13] Good night [16:13] smartboyhw: ^^ [16:14] OK. === ajcortes is now known as jjg1965 [16:15] afiestas: Why did you remove class AbstractBackend from src/configmonitor.h in libkscreen 1.0.1? Is that a binary compatible change? [16:15] ScottK: we don't keep binary comnpatibility [16:15] BTW, 1.0 is released to updates. [16:16] and we haven't removed it I think :s [16:16] at least not in prupose :/ [16:16] It is in other files, but that being remove from src/configmonitor.h is in the diff. [16:16] the include? [16:16] ScottK: I think it's a forward include [16:17] afiestas: https://launchpadlibrarian.net/146842526/libkscreen_1.0-0ubuntu1~ubuntu13.04.1_1.0.1-0ubuntu1~ubuntu13.04.1.diff.gz [16:17] afiestas: see the end of http://launchpadlibrarian.net/146842526/libkscreen_1.0-0ubuntu1~ubuntu13.04.1_1.0.1-0ubuntu1~ubuntu13.04.1.diff.gz [16:17] last line [16:17] Yeah. [16:17] ScottK: yeah, from what I understand it's a forward include and can be dropped [16:17] afiestas: It's fine not to keep binary compatibility, but you need to bump the so name when you don't. [16:22] we did I think [16:22] 1.0.1, no? [16:22] or 1.1 is required if we break it? [16:56] afiestas: on ABI breakage you would have to bump the SOVERSION, for you that's libkscreen_VERSION_MAJOR [16:56] but we're fine here as fas Howard was concerned [16:57] *as far as [16:58] we bump the minor, isn;t that enough? [16:58] I don't want to end up with soversion 25 [16:58] and call it libkscreen 2.0 [16:59] no, it wouldn't be enough for a BIC change [17:00] and libkscreen is at 22... [17:00] er [17:00] libkdcraw [17:00] but ok, bad example [17:01] afiestas: nothing prevents you from using longer SOVERSION's though... libattica has '0.4' [17:05] so, from 1.0.1 to 1..0.1 iok? [17:07] you'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] current SOVERSION is '1' === dantti_laptop|2 is now known as dantti_laptop [17:13] oh I thought we had it unified [17:14] it is partly, first part of the VERSION is the SOVERSION, you if you change the libkscreen version to 2.0.0 you change the SOVERSION [17:15] not sure if that coupling make sense, but it's ok as long as the ABI isn't broken in between [17:16] hm, is there a way we can express this in a install file : "Install everything under /usr except for these 2 files" [17:19] shadeslayer: 'rm' in rules [17:20] nah, that's fairly less than ideal [17:21] well, then you can just add all files except for the 2 you want to install to the install file [17:21] that's the debian way [17:21] * yofel would prefer that anyway === rdieter_ is now known as rdieter [17:57] libkscreen/kscreen accepted for raring [18:00] ScottK: thx [18:00] do we have a todo list for all those MRE's we got? [18:01] or do we actually have the full list documented somewhere? [18:01] AFAIK, no TODO. The full list is on the MRE wiki page. [18:01] ok, thanks === sayakb_ is now known as sayakb [19:03] afiestas 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. [20:27] someone can look at some crash report ? [20:27] http://pastebin.com/azpWgDuH [23:53] interesting, I just ran update and upgrade, and kscreen was held back [23:55] valorie: hmm Quintasan said that I think [23:55] I'm pretty sure I checked and the replaces/breaks was correct [23:58] launchpad might just be slow or something [23:58] dang it, no ahoneybun [23:59] that article gave highest marks to bodhi linux for their documentation, so I looked it up: http://www.bodhilinux.com/mob_documentation.php [23:59] it is very well organized and cute