[00:17] NCommander: How goes armel and kde4bindings? [01:11] ScottK, I know the problem, discussing with upstream on the fix [01:13] ScottK, the problem is that qreal != double on ARM [02:12] NCommander: I'd appreciate it if you'd push your changes via the bzr repo when you have them. [02:13] JontheEchidna: ^^ You too. [02:37] So I put mine there. [02:37] ok [05:06] JontheEchidna: You awake? [05:09] I guess not. [08:54] * Riddell off to San Francisco, ciao [09:44] hi there [10:13] apachelogger: Hey, around? [10:14] apachelogger: The kde4bindings issue you mentionned needs some upstream advice [10:14] apachelogger: Could you recommend someone from kde4bindings upstream or kdelibs which would help us move the issue forward? (it was forwarded upstream by NCommander already) [10:15] apachelogger: Basically kdelibs mixes qreals and doubles in its API and sip generates improper code as the result, either or both of these need to be fixed, but we need to discuss this with upstream to make sure we don't try to fix sip when it might not be one of its goals, or change kdelibs when it was the proper type to use [10:17] Crap the kde4bindings regression now breaks kdebase-workspace as well [10:27] lool, ? [10:27] NCommander: python-kde4 not installable (see armel build log) [10:28] Well python-kde4 is built out of kde4bindings ... [10:28] (and that's specifically what's FTBFSing in kde4bindings :-)) [10:51] NCommander: "< lool> Crap the kde4bindings regression now breaks kdebase-workspace as well" === _neversfelde is now known as neversfelde === glade88_ is now known as glade88 [12:28] lool, how is it a regression, it never built before :-) [12:33] NCommander: It built for me here [12:33] it never built on the builders [12:33] Wouldn't build at the time I uploaded it because I came just after some new kde uploads [12:33] kdebindings is a different package [12:33] What do you try to do? [12:34] huh? [12:34] lool: Did you see we have a bzr repo for kde4bindings now? [12:34] https://code.edge.launchpad.net/~kubuntu-members/kdebindings/ubuntu [12:34] ScottK: Oh cool, no I didn't [12:34] ScottK: I've been following the issue closely, but NCommander has been doing the analysis and is trying to write a patch [12:35] ScottK: It's likely that NCommander comes up with a kdelibs patch first AIUI [12:35] lool, got the patch [12:35] lool: OK. I know he knows about it already. [12:35] need to compile it to see if my fix will actually work [12:35] ScottK: Will all kde packages be imported like this? [12:36] lool: Yes, but we went ahead with this one first because yesterday we had literally 3 different people working on 4 different problems in the package. [12:36] apachelogger is getting it set up. [12:36] We tried this once before in Gutsy and it was just too slow to be usable then. [12:37] Why don't we just install git on something ... [12:37] *runs* [12:39] ScottK: Are these branched from the Debian packaging repo in some way? [12:39] lool: No. [12:48] lool: Sime is the pykde dood, for kdelibs you can just go to #kde-devel and start crying ;-) [12:49] lool: apparently dfaure is around, he knows a fair about kdelibs [12:52] accessibility, admin, artwork uploaded [12:58] apachelogger: Ok, thanks [13:03] edu, games and graphics uploaded [13:06] NCommander: I poked dfaure and he said that kdelibs needs fixing but we should ask on kde-core-devel@ in case someone has an objection (due to the abi change on arm / wince) [13:07] lool, cool. Thank you, assuming my patches work the way they are supposed to, I'll post to the list [13:07] NCommander: thanks [13:13] NCommander: I'd love being Cc:ed when you send the patch to the kde list! :) [13:14] You shall :-) [13:14] thanks [13:14] (I need to make sure we're not going to break something unexpectantly, it seems fine on x86, so if we can get kde4bindings to build, we probably can get the rest of KDE to build) === glade88_ is now known as glade88 [13:17] What the equivalent of kdesvn for bzr? [13:17] ScottK: got your email [13:18] JontheEchidna: I sent you email? [13:19] multimedia, pim and plasma-addons uploaded [13:19] ScottK: about bzr, I assume that's what you pinged me about? [13:19] ScottK: qbzr [13:19] JontheEchidna: No. [13:19] ScottK: it doesn't have a complete gui though [13:19] oh, you sent that to -devel [13:19] Yes. [13:19] apachelogger: Thanks. [13:20] ScottK: you have to access the individual parts manually (bzr qdiff or bzr qlog for example) [13:20] No, the reason I pinged you is there's a guy on #ubuntu-motu (aib) looking for help with packaging a cmake based project. [13:21] oh [13:22] Does he still need help? [13:22] * JontheEchidna uploads the rest of KDE to k-u-t [13:27] sdk, toys, utils and webdev uploaded [13:27] JontheEchidna: congrats to your first release packaging coordination [13:28] next time you shouldn't exceed the release day by 1.4 weeks :P [13:28] JontheEchidna: I'd imagine. It'd be nice if someone who understood cmake at least said hi to him. [13:29] I guess I should hang out in #ubuntu-motu more [13:29] JontheEchidna: He's wanting to package http://grey.colorado.edu/emergent (he's upstream) and they've moved to cmake in their latest release. [13:29] JontheEchidna: You should. It'll help when you submit your MOTU application. [13:30] that app looks interesting, the icon more like crap though [13:38] apachelogger: so what can we do next time to make sure packaging takes longer? Start packaging the week of Christmas? :P [13:40] apachelogger: OK. I've installed qbzr. Where does it's documentation hide? /usr/share/doc/qbzr has debian/changelog and copyright in it. [13:41] ScottK: http://bazaar-vcs.org/QBzr [13:41] also bzr help $COMMAND [13:42] JontheEchidna: we should be quicker next time due to reduced fiddeling, it is crucial that we a) get the stack 100% finished ASAP b) get everyone to use the hooks c) enhance QA with new batscripts [13:42] apachelogger: OK, so what's the $EXPLITIVE command to actually make the gui start? [13:43] Or is it I have to start the GUI per command? [13:44] ScottK: that is what I tried to communicate earlier ;-) [13:45] apachelogger: OK. Got it now. [13:45] So it's a GUI that you need to know command line commands to invoke. [13:45] Sounds like they collaborate with Launchpad developers. [13:46] ^_^ [13:46] ScottK: they just didn't came round to make a gui around the gui AFAIK [13:46] apachelogger: Thanks again for the pre-brief on the mysql stuff. [13:47] It seems that went reasonably well. [13:47] *nod* [13:52] \sh: will the poor kubuntu ninjas get a server for their magic? [13:52] I just thought of yet another usecase ;-) [13:52] * ScottK notices debian Bug #507655 and wonders if someone is interested? [13:52] Debian bug 507655 in krypt "[krypt] Add Krypt to the Debian package list" [Wishlist,Open] http://bugs.debian.org/507655 [13:54] * apachelogger looks and hopes that doesn't beak KDE like the last LUKS effort did [14:37] asac just pointed me at http://bazaar.launchpad.net/~mozillateam/firefox/firefox-3.0.head/revision/380 [14:39] whoa, I thought they weren't gonna do that === tobias_ is now known as hunger [14:40] Ho. [14:41] apachelogger: What is the status of KDE 4.2 in jaunty? Made any progress yet? [14:41] * hunger is currently running gnome since KDE 4.2 does not work at all here:-( [14:43] hunger: everything except kdenetwork should be uploaded by now, I think [14:43] its building right now [14:43] asac++ [14:44] ~karma asac [14:44] karma for asac: 1 [14:44] ~karma [14:44] karma for JontheEchidna: 2 [14:45] Great! [14:45] Thanks guys! === smarter_ is now known as smarter [14:46] Wahoo! Spam folder is now under 20,000 (I didn't look at it for 6 months). [14:47] wow [14:47] gmail++ for throwing that stuff away automagically [14:47] JontheEchidna: Are you running Intrepid? [14:47] ScottK: yus [14:48] * JontheEchidna is not crazy enough to run Jaunty yet [14:48] JontheEchidna: Now that 4.1.80 is pretty well in the can, would you be up for coordinating validation of 4.1.3 so we can get it into -updates. [14:48] * ScottK thinks 4.1.4 will be here soon .... [14:49] 4.1.4 is going to be a bit later than usual since they're shifting focus to KDE 4.2 [14:49] It doesn't seem to be happening by itself and so someone needs to take the bull by the horns .... [14:49] I think I did verification for a few of the packages, I think I can do the rest too [14:50] Right. It gets tagged in a week. [14:50] oh man, already? [14:50] Yeah. [14:50] KDE 4.2 beta2 gets tagged in a week too [14:50] funnies [14:50] wow it never slows down for you all does it? [14:50] Well if it wasn't later, it'd have been tagged a week ago. [14:50] thankfully for us... [14:51] apachelogger: we might need two bat teams for this [14:51] Well this is the POC for KDE4 into -updates. If this goes well it should be smoother next time. [14:52] Beta 2 should be a lot easier than beta 1 though. [14:52] yeah, usually we can at least develop the packaging by building against the old versions [14:52] JontheEchidna: as captain janeway put it "The minute we split up we loose every advantage this crew got." :P [14:52] Lesson learned for next time is get 4.2 -> 4.3 done before the 4.3 beta so we've got the kinks out before the beta hits and people care. [14:53] ScottK: only hunger really cares about it ;-) [14:53] apachelogger: I am in awe at your vast repository of Star Trek-like wisdom [14:53] but, think about it... that could have been a lot worse with the hardy vs. intrepid packaging [14:53] backporting is really just adding a changelog entry nowadays [14:54] in fact, we could streamline that process [14:54] It's packaging 4.1.4 and 4.2b2 at the same time that worries me [14:54] NCommander: I just took a look at the changes JontheEchidna and I did to the packaging you sent... you didn't add new files to any .install, didn't notice that 3 new games were added and sent one that FTBFS [14:54] apachelogger: he expected it to FTBFS on missing files [14:55] why did he send then? [14:55] because it didn't FTBFS [14:55] Apparently other packages will FTBFS in the event of missing files [14:55] apachelogger, I was told kde4.mk --list-missing, there was no output [14:56] make -f debian/rules list-missing [14:56] pbuilder hooks [14:56] Nice to know that's documented [14:56] JontheEchidna: the FTBFS was due to universe vs. main [14:56] Am I the only one in the world who actually uses --fail-missing in his rules files? [14:57] hm, that is worth a thought, it would still only go into the hooks [14:57] there are wrong missings [14:57] Personally, I think its absolutely insane to not have at least list-missing on as always a default [14:59] it's timewaste on the buildds [15:00] And more of a time waste if you forget to do it, upload a package, and then watch it FTBFS [15:00] There have been more than a few bug reports like that over the years [15:00] that is the reason I created hooks :P [15:01] I don't use pbuilder hooks because it is less like an actual build environment [15:01] That being said [15:01] Had I known kde4.mk didn't have list-missing [15:01] I would have checked it manually :-P [15:01] So I accept full fault on that [15:03] * apachelogger doesn't care if NCommander accepts fault as long as he doesn't do it (again) :P [15:03] NCommander: anywho, perfect documentation of changes I gotta say [15:04] Wait, what? [15:04] * NCommander is currently so caffiene depleted ATM ... [15:04] NCommander: of the changes you made, all were documented perfectly [15:04] that it is [15:04] Oh good [15:04] now what did I want to ask [15:04] what? [15:05] * NCommander is currently experiencing a broken English parser and requires things extremely clear [15:05] Did we get the patch for kde4bindings? [15:05] No, not yet [15:05] I'm still testing building everything [15:05] With --list-missing? [15:06] It will likely take another day for everything to build on ARM [15:06] stupid bindings [15:06] JontheEchidna: This would probably be a good time then for you to throw anything useful from the latest Debian upload at bar. [15:06] maybe we should debundle python from bindings [15:06] ugh, I haven't gotten to it yet [15:06] apachelogger: Wouldn't help right now since that's where are immediate problem is. [15:06] * JontheEchidna projects his anger onto kde4bindings [15:07] ScottK: not right now, but in general he new build chain is going to cause problems [15:07] Agreed. [15:07] bindings is causing a lot of work to update [15:07] Because I need build everything on ARM [15:07] and since workspace depends on pykde we need to have bindings ready before we can do anything [15:07] NCommander: Care to look at the latest Debian revision for useful additional bits while you are waiting? [15:08] apachelogger: I think this should be at least discussed upstream first. [15:08] ScottK: agreed [15:09] does anyone know where the pthread patch in kdemultimedia come from? [15:09] ...because we were talking about changelog keeping [15:12] * JontheEchidna out for a bit [15:13] * apachelogger thinks JontheEchidna did add that patch :P [15:20] hi [15:20] are there any packages of kde 4 beta 1 for kubuntu? [15:21] I don't think so, usually they putthemon the homepage. [15:21] siekacz: There are some currently building for jaunty. [15:22] siekacz: I'd recommend against upgrading to jaunty at this time though. [15:22] You could always run in a VB [15:22] i know [15:22] * VM [15:23] but compilling will kill my CPU [15:23] chris062689: VMs are for wimps:-) [15:23] im not going to install Jaunty with 4.2 in a production environment! :D [15:23] They are also being uploaded to a PPA for Intrepid. [15:23] Are you Krazy? [15:23] chris062689: Good plan. [15:24] I would love just to help with the Kubuntu project.. [15:24] But I don't know HOW :( [15:24] chris062689: My box is running jaunty already. I get bored too easy on stable distributions. [15:24] chris062689: Run the unstable release and nag people about bugs:-) [15:25] Well, i want to be more on the developing / packaging side [15:25] I want to help push updates through and the such [15:25] uh [15:25] perfect :) [15:25] I guess launchpad is the way to go right now though...... [15:25] chris062689++ [15:25] huh? [15:25] chris062689: https://wiki.ubuntu.com/HelpingKubuntu [15:25] chris062689: did you ever do packaging? [15:26] no [15:26] But i want someoen to show me the ropes, so I can [15:26] smarter: ping [15:26] bisou? [15:26] oh, i hope you won't get bored after a few weeks :) [15:27] pong apachelogger [15:27] jpds: kiss [15:27] chris062689: meet smarter [15:27] smarter: meet chris062689 [15:27] hi [15:27] Hmm? [15:27] Hello.. [15:27] what's the matter? [15:27] chris062689: smarter is one of the universe maintainers and will now become your helping hand [15:27] ah, sweet. [15:28] hmm? :p [15:28] smarter: chris062689 wants to become a leet packager [15:28] Would you mind another form of communication? Since I'm in class right now, and may have to log off (like AIM or MSN) [15:28] I guess IRC is fine though...... [15:28] well, I don't really have time to teach you a lot of thing, but can point you to good tutorial [15:28] ok [15:28] tutorials even [15:29] basicly how it goes it [15:29] I use the source to create a deb [15:29] then submit it to the "Masters" [15:29] and then... it goes into the repo? [15:29] basically, yes [15:29] AIM, MSN are proprietary... you might consider using a free version like jabber. [15:29] well, in a way ;-) [15:29] s/version/protocol/. [15:29] which does it go in? unsupported? Community? [15:30] what we call universe [15:30] ok [15:30] I want to build a few emulators for use [15:30] https://wiki.ubuntu.com/PackagingGuide/Complete is rather good on the "I use the source to create a deb" part [15:30] Ubuntu repos are really not that great for emulation [15:30] ScottK: I should have kbzr and our packaging branches ready by tomorrow (hopefully) [15:30] The first packages I want to build are for PCSX2, Playstation, etc [15:31] * apachelogger heads home [15:31] I guess I can experiment [15:31] if you want the package to go in Ubuntu, make sure the app is open source [15:31] 2nd part is explained by https://wiki.ubuntu.com/MOTU/Packages/REVU [15:31] apachelogger: Oh, ja, richtig. [15:31] hey jpds [15:32] salut smarter [15:32] chris062689: There are always people here that will be happy to answer specific questions. [15:32] okie dokie [15:32] I'll probably try to hang out here more often. :D [15:32] I think PCSX2 is a GTK based app though [15:33] Do GTK apps still look ugly in QT / KDE? [15:33] chris062689: Sure. GTK is ugly:-) [15:33] the problem with using GTK apps in QT is the file browser and such, it's so.. not native! [15:33] in theory, they're supposed to get somewhat integrated with the gtk-qt-engine [15:33] chris062689: You can ask to have the Qt themes applied to GTK apps though in the config center. [15:33] chris062689: there's a workaround for that [15:33] config center, in.... [15:33] it's called KGTK and gives a nice kde dialog to your gtk app [15:34] but it's a hack [15:34] oh, hacks are bad :( [15:34] Sure, but sometimes better than the alternative. [15:34] but heck we'll worry about that later, heh [15:34] What I don't understand is.. [15:34] PCSX2 is built as a GTK app [15:34] BTW, anyone knows why gtk-qt-engine won't work on a freshly installed Kubuntu 8.10? [15:35] How do you... seperate it into PCSX2-core and PCSX2-Qt and stuff like that, I assume it would be up to the programmer's of PCSX. [15:35] smarter: By design it doesn't pull in any Gnome stuff, just works if the packages are there. Maybe you need to install stuff. [15:36] From what I can tell, KDE 4.2 is really stable [15:36] When I tried using the Live CD, only a few apps crashed, but a lot more features :) [15:37] Is KDE 4.2 going to backported to 8.10? [15:37] since it's going to release in Jan. [15:37] ScottK: well, gtk-qt-engine is already installed, GTK2_RC_FILES env variable is set but neither firefox nor thunderbird use the qt engine, so I don't really know what "stuff" I could install [15:37] chris062689: yup [15:37] The plan is to put it in intrepid-backports once it's released [15:37] ok. [15:38] Dunno then. [15:38] I can just IMAGNIE how long that takes to compile :P [15:38] oh yes, especially on my Celeron D 341 [15:39] dang [15:39] I have a E7200 @ 3.7 [15:39] I'm fine with a DualCore, I don't feel I need the power of a Quad. [15:39] Celeron @ 2.5 GHZ [15:39] 5 years oldish [15:39] my PC is 3 years OLD [15:39] heh [15:39] I just built mine a few months back [15:39] I love it :) [15:40] Plus I was suprised everything works OOTB in Linux, so that's a plus. [15:40] these number in your nick are your birthdate? [15:40] Ubuntu was slow on my old HP (256MB , 3Gh Celeron) [15:40] yeah [15:41] I should probably think of a new nick, heh [15:41] Now i have 512 MB ram, but i had 2 GB and someone put 2x256 DDR to DDR2 slots, and... :) [15:41] is that your birthday? [15:41] 06 - 26 - 89 [15:42] my birthday: 05 - 01 - 92 :) [15:44] yeah jjesse [15:44] chris062689, are you from USA, Canada, or something like this? [15:44] USA [15:44] FL [15:45] nice, and I'm from Poland :) [15:45] lol [15:46] yeah I mean heck, I have a ton of free time, and want to help Kubuntu become on-par with Ubuntu in terms of support / features / stabibility. [15:46] So I figure I'll loan my time /energy whenever I can [15:46] I also want to dribble in KDE 4 C++ programming [15:48] as you know, you need to be a proffesional C++ programmer :) [15:48] Hmm? [15:48] Well, yeah.. Which I'm not, meh, but still I figure I can make little plasmoids or something [15:49] to write plasmoids better is Ruby, Python :) [15:49] siekacz: It's just like anything else; determination and hard work. [15:49] oh, it's not good to write em in C++/ [15:49] You'd recomend python or ruby? [15:49] I would recommend python or ruby [15:49] i have a few python books laying around......... [15:50] if you know C++, python is easy to learn [15:50] i started to write scripts in Python it's quite easy [15:50] I don't know C++ *sighs* [15:51] python is what happens when you marry a shell and a programming language [15:51] one of main python's advantages is that you don't need to compile any more :) [15:51] I know ABOUT python, but not much about the actual programming [15:51] chris062689: http://www.mindview.net/Books/TICPP/ThinkingInCPP2e.html [15:52] ive done programming in DM, and PHP, so I have a pretty good foundation [15:52] (also HTML, CSS, etc) [15:52] chris062689: http://docs.python.org/tutorial/index.html [15:52] better to write plsmoids is python :) [15:52] I learnt it from reading the guides http://wiki.python.org/moin/BeginnersGuide [15:53] chris062689: Still, there's tons of information out on the web about programming. [15:53] is it possible to write plasmoids in C++? [15:54] of course [15:54] I think so. [15:54] seeing as plasma is written in C++, i'd hope so :p [15:54] KDE is C++ before everything else [15:54] yeah [15:54] but if your C is buggy it can bring down plasma, so it's preferrable to write it in a scripting language [15:54] oh, plasma is better than i thought :) [15:54] I don't know C, I know C++ :) [15:54] s/C/C++ [15:54] I know PHP, CSS, HTML..... [15:54] Nothing to be used in KDE lol [15:54] And if you can get books, I suggest: http://www.amazon.co.uk/dp/020170353X/ for C++. [15:55] I already have a book [15:55] and two python books [15:55] C++ is a low-level programming language so it can crash plasma :) [15:55] For 'scripting languages' we tend to prefer Python. [15:55] heh [15:55] So C++ for low, Python for script [15:55] Gotcha [15:55] * smarter read C++ Primer, pretty good [15:56] * ScottK heads out for a while to take the wife's dog to the vet. [15:56] ScottK: Unless you go by the name of aplg. [15:56] :P [15:56] jpds: Yes, well there is that. [15:56] some thinks are easier done in python than C++, and some things are easier done in C++ than python [15:56] Number one on the list of conversations I don't want to have with my wife: [15:56] * Honey, why is there chocolate in the bath tub? [15:56] buggy python script will just not work [15:56] "Sorry your dog died while you were out of town. I was too busy working to take him to the vet." [15:57] See you later. [15:57] hope it feels better [15:57] or.. doesn't die..... meh [15:57] siekacz: you know, python script can have runtime failures too [15:58] but it is harder to crash whole plasma in python [15:58] and some of these failures could be catched by a C/C++ compiler if the code was C/C++ [15:58] The ONLY reason I use GNOME at home is because it's more stable at this point, when 4.2 comes out, I'll switch full KDE4 [15:58] siekacz: no idea, but I don't think there really is a difference [15:58] siekacz: not necessarily, as it's python bindings so it uses C++ to interface with plasma [15:59] so it's translating python code in C++ "esentially" [15:59] *essentially [15:59] well, binding it to C++ calls [15:59] it uses a lot of pointers behind the scenes [15:59] and, as we all know, pointers are evil [16:00] python is just easier than C++ [16:00] true that [16:00] not always [16:00] I'm working on something which is just too difficult in python, so I'm writing it in C++ [16:01] well, most things are good for Python === santiago-pgsql is now known as Guest57461 [16:01] stdin, low-level programming, right? [16:01] But if you need to make a HUGE app, you need C++ [16:01] siekacz: no, a GUI installer [16:02] i thought about linux, not windows [16:02] who's using windows? [16:02] No one [16:02] Windows is evil, dang [16:02] I use sometimes vista on my poor PC and at school [16:03] stdin: i'm runing vista right now [16:03] I usedto [16:03] jjesse: say 3 Hail Mary's and all will be forgiven [16:03] But with the recent WINE updates, I an run all of my games, except L4d [16:03]