[00:42] hey, the global menu in akregator started working randomly... [00:48] ScottK: phonon now officially commits to the kde minor point release policy [01:09] * debfx watches the dots while running pull-debian-source kdeartwork [01:11] oh, I should go to bed [01:12] ScottK: is it leate yet? [01:17] JontheEchidna: you haven't converted some cdbs cruft to dhmk in kdeartwork [01:17] JontheEchidna: I'll fix that and upload [01:18] armel opengl stuff? [01:18] yep [01:18] yeah, I wasn't sure how to exactly do that [01:19] kubuntu on arrrrrm [01:19] * micahg is trying to make xubuntu on arm [01:24] micahg: that is just wrong, you should make kubuntu on arrrrm :P [01:24] also I should really go to bed [01:24] like desperately [01:24] nites [01:25] JontheEchidna: http://bazaar.launchpad.net/~kubuntu-packagers/kdeartwork/ubuntu/revision/112#debian/rules [01:26] oh, cool [01:26] simple [01:38] yeah it is [01:38] uploading kdeartworks however is not that easy [01:57] could one of you core-devs please merge https://code.launchpad.net/~debfx/ubuntu-seeds/kubuntu.oneiric/+merge/63320 [01:58] should help us a bit to return to a sane image size [02:53] debfx: sure [02:55] debfx: done, thanks [04:55] randalogger: No. It's not late yet. [04:55] It's still before midnight here. [04:56] randalogger: The arm boxen are back up, but the 100 box doesn't have it's bigger /var/cache mounted. I missed one step in the instructions when directing what needed doing to bring them back to life. [04:57] It should be fine for building stuff smaller than Qt. [04:57] I'll be home tomorrow evening and can fix it properly then. === jjesse_ is now known as jjesse [09:03] yofel: I think we can drop the dolphin-plugins transitional package as it isn't in lucid [10:44] debfx: yes, as long as the new 4.6.3 package never makes it back into natty, anything that gets put into natty in some way needs it [10:45] so I would say keep it and drop it for 4.7 [10:50] yofel: I hope no one puts 4.6 into natty [10:51] ah, wait [10:51] depends if we want to resync the natty PPA with the new packaging [10:51] yofel: when you upgrade to natty the transitional package gets pulled in [10:52] yofel: nevermind, I confused natty with lucid [10:52] yes, I'm just thinking whether we want to put 4.6.5 with new or old packaging into natty-updates. If we use new ones it might not work [10:54] we don't want the new ones, such drastic packaging changes don't qualify for a SRU [10:54] k, then drop it [10:58] has anyone found a way to make authentication in launchpadlib work? [10:59] as in login_with() ? [11:00] not sure, whatever ubuntu-dev-tools uses in natty [11:01] uh, no idea, they had some manager-credentials command or so IIRC [11:01] that was the old system afaik [11:02] * debfx tries the unencrypted storage backend [11:02] then they probably use the keyring now [11:07] yeah, the kwallet backend seems to be broken beyond repair [11:21] yay [11:23] randalogger: do you know anyone we could poke for https://git.reviewboard.kde.org/r/100157/ ? [11:47] ScottK: I only get connected to 2 arms, what gives? [11:50] randalogger: I got my mx53 today :D [11:50] Quintasan: ScottK ^^^:D [11:53] debfx: sho [11:53] in #konversation [11:53] that is eike hein [11:54] s/that/he [11:54] cant type while people talk all the time [11:56] jussi: congrats [11:57] randalogger: I cant wait to get home and play :) [12:17] * Quintasan 's PC is working [12:17] jussi: \o/ [12:18] jussi: I almost got it sorted out, now they whine about that the package says price is $149 whereas I have paid $99 [12:18] oh lol [12:18] Quintasan: want a scan of one of the vouchers? [12:19] I asked Freescale to send FedEx a statement that it is $99 indeed and I still got no response [12:19] jussi: Sure, I wonder if they will accept one but it is worth a try [12:19] Yay :) [12:19] Quintasan: pm me your email addy [13:14] randalogger: I didn't check all 4, so I'm not sure. I'll check it in detail tonight when I've got physical access to the boxen again. [13:18] ScottK: okok [13:19] ScottK: not doing anything right now anyway [13:20] !find autoreconf.mk [13:20] File autoreconf.mk found in dh-autoreconf === rdieter is now known as rdieter_work [15:41] can any one help me pack a deb file here ? i think my problem is it has two executibles being build. after running debuild i do get a deb file but its list of installed files do not list anything for /usr/bin [15:43] sithlord48: Is this a package you intend to try to get into the official repository? [15:43] ScottK: no my ppa, [15:44] sithlord48: #ubuntu-packaging is the best place to ask about that then. [15:44] yea no answer there. [15:44] It's OT here since this channel is about Kubuntu development. [15:44] we refactor all KDE MM userbase pages to be one sentence related to .prn [15:45] highly efficient \o/ [15:51] ScottK: is packaging not part of development [15:51] sithlord48: Packaging for random PPAs is not part of Kubuntu development. [16:37] huh [16:43] for some reason my extra cmake flags are not picked up during kdeedu compilation, http://paste.kde.org/77881/ [16:44] not even -DMARBLE_PLUGIN_PATH [16:44] and just noticed something else [16:45] shadeslayer: You did notice we're not using CDBS anymore, right? [16:45] ScottK: i haven't modded any part of the rules except line 10 to 13 [16:45] and line 19 ofcourse [16:48] Isn't debian-qt-kde.mk for CDBS? [16:48] * ScottK thought there was something different for DH. [16:48] dhmk or some such. [16:48] ScottK: depends if it's 2/ or 1/ [16:48] ^^ [16:48] 1/ is cdbs, 2/ dhmk [16:48] Ah. [16:48] It's 2 [16:48] Good then. [16:49] http://paste.kde.org/77887 << fixed it a bit [16:49] * ScottK is leaving for the airport, so good luck. [16:49] cya [16:50] here's the build log where you can see it doesn't pick up any of the options : http://paste.kde.org/77893 [16:50] lin 1953 [17:20] okay figured it all out [19:04] evening [19:04] http://paste.ubuntu.com/617719/ <--- wtf ? [19:04] (line 6) [19:05] do you need oneiric's pkg-kde-tools to build the Debian 4.6.3 packages? [19:06] LaserJock: yes, but it's also in natty-backports [19:07] bambee: that looks about right if you're on oneiric [19:07] don't dist-upgrade ;) [19:08] how do you upgrade your oneiric ? [19:08] I've got a fix for bug 785433 in Qt pushed as a merge proposal at https://code.launchpad.net/~utouch-team/qt/touch-end-fix/+merge/63417 [19:08] Launchpad bug 785433 in qt4-x11 (Ubuntu) "Touch end events not handled" [Medium,In progress] https://launchpad.net/bugs/785433 [19:08] would someone be able to review it? [19:12] bambee: aptitude safe-upgrade? I have like 100 packages held back here, not upgradable [19:12] or I'll remove KDE [19:12] * bambee tests safe-upgrade [19:13] does /almost/ the same thing as apt-get upgrade [19:15] yofel: it does the trick, thanks ;) [19:36] jussi: Re-Scheduled 04-JUN-2011 [19:59] <_Groo_> hi/2 all [19:59] <_Groo_> could anyone explain to me why kamoso alpha is being installed when we have 2.0 final in backports? [19:59] <_Groo_> for natty [20:00] <_Groo_> see http://paste.ubuntu.com/617752/ [20:01] <_Groo_> its not respecting the version number, or the number is wrong [20:02] <_Groo_> and installing the alpha instead of the backports 2.0 final [20:03] <_Groo_> i had to force it with apt-get install kamoso=2.0-0ubuntu1~natty1 [20:21] _Groo_: afaik we have an apt-pin in natty so backports aren't installed by default [20:22] _Groo_: can you show me the apt-cache policy output? [20:27] <_Groo_> hi/2 all [20:28] _Groo_: afaik we have an apt-pin in natty so backports aren't installed by default [20:28] _Groo_: can you show me the apt-cache policy output? [20:31] <_Groo_> yofel: http://paste.ubuntu.com/617768/ [20:32] <_Groo_> also kamoso 2.0 and 2.0 alpha are broken, cant acess the /dev/video, 2.0.2 backported works just fine with phonon [20:32] <_Groo_> same hardware works with cheese for ex [20:32] <_Groo_> and kopete [20:35] <_Groo_> yofel_: anything that pops out? [20:38] <_Groo_> hello? [20:49] sorry, had some connection issues === yofel_ is now known as yofel === rdieter_work is now known as rdieter [20:51] _Groo_: see that -backports has a priority of 100? So if you install a package it will be taken from there, but it won't be upgraded automatically if there's a new version in -backports === valorie_ is now known as valorie [21:00] <_Groo_> yofel: how do i change that? and from all i knew, this is new in natty, maverick didnt had that pin [21:01] it is new, usually that would be in /etc/apt/preferences[.d/] [21:02] <_Groo_> nothing backports related in preferences.d [21:02] not sure how they set that then [21:03] <_Groo_> found it [21:03] where? [21:03] <_Groo_> its in apt.conf.d [21:03] <_Groo_> apt.conf.d/50unattended-upgrades [21:03] <_Groo_> updated, proposed and backports are commented out :P [21:03] <_Groo_> which kinda defeats the purpose of having them :P [21:04] hm, I think that does something else [21:04] <_Groo_> well then i dont know :P [21:05] <_Groo_> grep doesnt show any entires for backports besides the source.list ones [21:05] <_Groo_> and that [21:05] since natty backports aren't installed automatically but once you install a package from backports it gets upgrades from there [21:05] kamoso 2.0.2 simply hasn't been backported to natty [21:06] <_Groo_> debfx: just backported it.. its the only one working btw [21:06] <_Groo_> 2.0 and alpha are both broken [21:06] <_Groo_> no video pops out [21:06] <_Groo_> only 2.0.2 fixes it for me [21:06] <_Groo_> kopete and cheese work just fine [21:06] file a backport request [21:07] <_Groo_> how do i change the pin then?? im clueless [21:07] _Groo_: add something like this to /etc/apt/preferences, should override it: [21:07] Package: * [21:07] Pin: release a=natty-backports [21:07] Pin-Priority: 500 [21:08] <_Groo_> yofel: cant... someone forgot to add libqtgstreamer-dev to natty [21:08] <_Groo_> which is strange since it backports just fine with the same code from oniric [21:08] you probably don't want to pin backports like that [21:09] _Groo_: the package is called qtgstreamer-dev in natty [21:10] <_Groo_> debfx: oh [21:10] <_Groo_> -.- [21:10] <_Groo_> this is apachelogger fault, im sure of it!!!! [21:10] well, that's what the configuration was before natty, but yeah, usually 100 sounds right for backports [21:11] <_Groo_> debfx: so, what am i suposed to do, to make sure backports are used always? same for proposed [21:12] _Groo_: if you are sure that you want everything from backports do what yofel posted [21:13] erm, -proposed should really not be at 500 [21:13] you might as well run oneiric then (ok, not as bad, but possibly so) [21:14] <_Groo_> yofel: if i had proposed its because i WANT to use proposed [21:14] <_Groo_> if now, whats the point? [21:14] <_Groo_> how do i keep track of whats going in proposed then? [21:15] you check natty-changes ML for what what uploaded to -proposed and help with the SRU testing? [21:15] s/what what/what was/ [21:15] yofel meant: "you check natty-changes ML for what was uploaded to -proposed and help with the SRU testing?" [21:15] *SIGH* [21:15] <_Groo_> Package: * Pin: release a=natty-backports Pin-Priority: 500 Package: * Pin: release a=natty-proposed Pin-Priority: 500 [21:16] people had lots of problem when -proposed had normal pinning [21:16] <_Groo_> something like this to have both? [21:16] <_Groo_> i like to live on the edge [21:16] it was difficult to test the packages in isolation, that's why it was changed I believe [21:16] well, -proposed wasn't enabled by default for a reason [21:16] exactly [21:16] <_Groo_> exactly, but if i enable it i want to use it [21:17] _Groo_: but the point of using it was for testing individual packages, not the whole repo [21:17] yes, for SRU testing, it's not meant to be used in general [21:17] and for SRU testing you need to be able to update only one specific package [21:17] <_Groo_> i prefer to update and see what breaks [21:17] <_Groo_> and come here shouting [21:17] <_Groo_> like kamoso [21:17] having the pin is easier than constantly: enable -p -> update and test -> disable -p [21:17] <_Groo_> ho btw [21:18] <_Groo_> if anyone is using fancy tasks [21:18] <_Groo_> a very very bad news [21:18] <_Groo_> its broken in 4.6.3 UNTIL you recompile it [21:18] <_Groo_> you have 2 scenarios [21:18] that's SRU material :P [21:18] <_Groo_> one: it will crash plasma-desktop imediatly as soon as you update [21:18] <_Groo_> two: it will crash plasma-desktop when you click on configure [21:19] <_Groo_> solution:? recompile it with 4.6.3.. i know.. it should be ABI compatible... but plasma is .. well... plasma... :P [21:19] _Groo_: proposed has priority 500 by default, you only need to change it for backports [21:19] <_Groo_> just try it :D [21:19] <_Groo_> debfx: k, done :) [21:20] well, blame aseigo probably :P, but file a bug about it and we can get it rebuilt [21:20] <_Groo_> debfx: so let me guess this straight... backports which are packages already tested as 100.. proposed whihc is the :"denagerous" stuff as 100? [21:20] <_Groo_> very logical :P [21:20] <_Groo_> yofel: test it! [21:20] <_Groo_> yofel: i always like to test if im not crazy [21:21] <_Groo_> yofel: about the package i mean.. im crazy as it gets [21:21] which was that, smooth-tasks? [21:21] <_Groo_> plasma-widget-fancytasks [21:21] <_Groo_> oh btw [21:21] _Groo_: the barrier to get something into proposed is much higher than backports [21:21] <_Groo_> acroread is broken in 64bits [21:22] ah right, proposed is at 500 [21:22] I just pin that to 100 here ^^ [21:22] <_Groo_> it tries to force to install nspluginwrapper, which breaks in 64, should have be changed for flash64 or nothing at all [21:22] <_Groo_> i remade the partners package and its working like a charm now [21:23] <_Groo_> so, 3 bugs... [21:23] <_Groo_> 1 - kamoso is broken [21:23] file a bug, flash64 isn't released, so rather remove the dep [21:23] <_Groo_> 2 - acroread is broken in 64 [21:23] if it doesn't require it this should be a recommends anyway [21:23] <_Groo_> yofel: yeah, for 64 bits you need, it wont install [21:24] <_Groo_> yofel: it was in previous version, dont know who was the genius who decided to force it [21:24] <_Groo_> brian thomason [21:24] <_Groo_> where are my laser glasses [21:25] <_Groo_> 3 - plasma-widget-fancy is broken if you use 4.6.3 from backports, need to be added to backports too and recompiled with that code [21:25] <_Groo_> you welcome :P [21:25] ah, that's the PPA, right, need to go home, then I can upload a rebuild [21:25] wait, you can do that yourself! [21:26] <_Groo_> yofel: yeah [21:26] <_Groo_> yofel: im at work... no way to upload it from here [21:26] <_Groo_> and im an unoficial minion [21:26] heh, then I'll do it later [21:26] <_Groo_> im not gonna put my dirty paws in the ppa without being told so [21:26] <_Groo_> apachelogger or other officer would hunt me down like a dog [21:27] heh, well, I'm gone, bbl [21:27] <_Groo_> yofel: did you test fancy? [21:27] not yet, my battery's empty :P [21:27] <_Groo_> yofel: ah ok :D [21:27] <_Groo_> btw after it crashes, it crashes plasma always [21:27] <_Groo_> so be ready to compile it locally and replace it [21:28] <_Groo_> cause your precious desktop wont go up again [21:28] <_Groo_> or edit plasma-appletsrc and remove it [21:28] <_Groo_> if you are lucky and it doesnt crash plasma right away [21:28] <_Groo_> it will as soon as you hit configure [22:29] * yofel just noticed he can't install fancytasks as it depends on libkonq5a [22:30] can someone rebuild that in oneiric? [22:35] * Quintasan can't request rebuilds :< [22:44] Quintasan: why not? [22:44] no idea why [22:44] Or I am looking in the wrong place [22:45] where are you looking? ^^ [22:46] debfx: launchpad site for [22:46] you just download the package, call dch -R, build it and upload [22:46] oh [22:48] maybe even needs a SRU in natty: bug #750925 [22:48] Launchpad bug 750925 in plasma-widget-fancytasks (Ubuntu) "Fancy Tasks widget crashes plasma" [Undecided,New] https://launchpad.net/bugs/750925 [22:48] yofel: it depends on libkonq5-dev 4:4.5.2 :S [22:49] >=, doesn't change the fact that it depends on the wrong binary package [22:50] oh wait [22:51] so it just a rebuild in oneric [22:51] oneiric [22:52] and probably in natty [22:53] debfx: do we need to do SRU's for rebuilds? [22:53] Quintasan: yes [22:54] * Quintasan tests in oneiric first [23:00] It's not pinning. Backports is set to be a 'not-automatic' repository. The results are similar. [23:09] ScottK: yes, but pinning can override the not-automatic flag [23:10] OK. [23:11] yofel: lol, on oneiric [23:12] after a rebuild [23:12] it depends on libkonq5abi1 [23:12] no idea [23:12] That's the new packagename. That's what I'd expect. [23:12] so it is the desired behavior in oneiric? [23:13] Yes. [23:13] * Quintasan goes to build natty [23:14] ScottK: has the not-automic and but-upgrades been introduced for automatic backports->backports updates? [23:15] debfx: Yes, if I understand the question correctly. === randalogger is now known as info === info is now known as infologger [23:18] ScottK: are you familiar with kdemultimedia at all? [23:19] LaserJock: If the criteria is 'at all', yes. [23:19] What's the question? [23:19] well, I got what i thought would be a good stab at a merge [23:19] but it doesn't build [23:20] What's the error? [23:20] it fails in ffmpegthumbs with a : error: 'CODEC _TYPE_VIDEO' was not declared in this scope [23:20] I wondered if it might have something to do with disabling xine [23:21] It might also have something to do with our switch from ffmpeg to libal source. [23:21] It could also be GCC 4.6 related. [23:22] * Quintasan will file SRU tomorrow [23:22] yofel: uploading rebuild to oneiric [23:23] LaserJock: You're not the only one: https://bugs.kde.org/show_bug.cgi?id=274666 [23:23] KDE bug 274666 in general "ffmpegthumbs-4 6 3 fails to build with libav-0 7_beta2 (Gentoo bug #369515)" [Normal,Unconfirmed] [23:23] Not GCC 4.6 then. [23:24] LaserJock: I'd see if you can build it against Natty. That would give us an idea if it was related to Oneiric toolchain or not. [23:25] ScottK: oh, ok, good idea [23:26] ScottK: I tried the vanilla debian package on oneiric and it died at the same place [23:26] yofel: should work in oneiric soon [23:27] LaserJock: I'm pretty sure it's an upstream issue. The question is where. [23:27] The bug I pointed you at is from Gentoo, so probably not our fault. [23:28] Good night. [23:28] libav broke API compatibility in 0.7 [23:29] LaserJock: ^^^ There you go. Please whine to siretart. [23:30] might be worth checking the svn repository, maybe it already got fixed [23:30] Good point. [23:30] Particularly with 4.6.4 being close to release. [23:34] there's a tracker for the libav transition: http://people.canonical.com/~ubuntu-archive/transitions/libav.html [23:35] micahg: does it also track the required patches? ;) [23:35] debfx: I'm sure patches are welcome :) [23:36] Yeah, they're welcome here too.