styled in css which looses its bottom dotted border with Qt .4.8 [16:06] I guess we can live with that [16:07] yes [16:21] Riddell: I'll stick around with shadeslayer and tazz there. Might as well as get back on track with development this week [16:21] ^^ [16:32] meeting is started but may take an hour or so for kubuntu [16:39] shadeslayer: who the hell is responsible for calligra packaging? [16:39] I don't know [16:41] Quintasan: kubuntu is [16:41] why do you ask? [16:41] Riddell: whoever picks new release is the one policy? [16:42] Quintasan: parse error [16:42] can you rephrase? [16:43] Riddell: I wanted to know if there is anyone among us who is particulary commited to calligra packaging [16:44] Quintasan: oh well I tend to package new releases, if I happen to be in a coma or something I think others will get around to it eventually but not necessarily in time for each of their releases [16:44] and it's in debian so it's fairly simple [16:45] Riddell: I see, is it fine with you if I go ahead and add a few dependencies to the calligra meta-package? for example braindump doesn't get pulled [16:45] Riddell: Quintasan Can/Should we get telepathy kde into the archives? [16:45] shadeslayer: We can get and we should get them into archive [16:45] Not main at this point but universe for sure [16:46] Quintasan: okay, lets start working on those from monday? [16:46] shadeslayer: Nah [16:46] Hm? [16:46] I am in favour of waiting till 0.3 [16:46] Quintasan: sure, if it's good enough quality for calligra, packaging is in bzr [16:46] shadeslayer: everything gets renamed + codes moves once again [16:47] Quintasan: Right, I agree and should have made myself clearer, that's what I meant when I said lets get it into the archives [16:47] yeah [16:47] Riddell: I mean, it's being built but not installed when user installs calligra package. [16:47] Quintasan: do you want to take over the upload of 1:2.3.86-0ubuntu5 from me? [16:47] Riddell: I think I can [16:47] Quintasan: ssh key on launchpad? [16:48] Riddell: Providing something didn't go horribly wrong while I was not using my computer then it is there. [16:49] Quintasan: ubuntu@ec2-107-21-90-52.compute-1.amazonaws.com [16:49] run byobu on login [16:49] afternoon guys [16:49] shadeslayer: ".." [16:50] screen escape key is F12 [16:50] Riddell: I just dropped by to let you know, with apologies cause something's clearly gone awry, that the i386 build of libapogee2 failed. I haven't had a chance to read the build log yet to find out what went wrong though. [16:51] derp, I had just changed buffers when they started discussing about Kubuntu :P [16:51] Quintasan: so build that's all my changes, you'll need to do bzr co again since I've removed my ssh key [16:51] build it [16:52] debsign -r for remote [16:52] BarkingFish: blame -Werror=format-security [16:52] Also, the bug concerning syncing strigi has been rejected and marked invalid, the reason being is that it can't have libavcodec on the cd image, and strigi has bits of libavcodec as deps [16:52] the email said something about it having an Ubuntu delta [16:53] Riddell: remote debsign? @_@ [16:53] BarkingFish: that's interesting about libapogee2 suggests it's broken on all arches not just ARM [16:53] BarkingFish: that means there are some ubuntu specific changes that need to be incorporated [16:53] * Quintasan clearly needs to learn tricks like that [16:53] Quintasan: heh, debsign -r is awesome [16:53] Riddell: what concerns me is that it built locally but won't build remotely. [16:53] BarkingFish: oh I didn't know we had an ubuntu delta, that'll need reapplied then [16:54] BarkingFish: then there's some difference between your machine and the build servers and if we just find what that is then it's easy to fix [16:54] Riddell: his libapgee build in PPA failed with errors from -Werror=format-security [16:54] did that get turned on again? [16:54] Riddell: Ha ha, I feel like a lost child in that ec2 machine :D [16:55] brb [16:55] lol [16:55] yofel: I don't know [16:55] hm yeah, they did add that again [16:55] yofel@yofel-T510 $ dpkg-buildflags [16:55] CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security [16:56] Quintasan: do you want to upload qt too? [16:56] download the three packages, debuild -S, sign, upload https://launchpad.net/~kubuntu-ppa/+archive/experimental/+packages [16:56] Riddell: upload where? Archives? Don't have permissions for archives [16:56] oh derp [16:56] damn, I need to remove this highlight [16:57] shadeslayer: what what? Quintasan is in kubuntu-dev for uploading whatever list of packages that allows [16:57] I think it allows qt but not sure [16:58] yofel: Would that be something which I could fix locally in the code here? [16:58] Riddell: right, I have a highlight for "kubuntu" which is why I thought that you were talking to me [16:58] shadeslayer: in this channel? might not be the best channel for it :) [16:58] Yeah, had it for #ubuntu-meeting [16:59] but quassel doesn't allow channel wise highlights it seems [16:59] naugty quassel [16:59] BarkingFish: well, yeah, you need to fix the compiler warnings (now errors) that you see on https://launchpadlibrarian.net/89820921/buildlog_ubuntu-precise-amd64.libapogee2_2.2-0ubuntu2_FAILEDTOBUILD.txt.gz [16:59] Quintasan: have we lost you? [16:59] or as a hack filter -Werror=format-security out from the buildflags [17:00] I expect those errors require elite c++ skills [17:00] * Riddell out [17:01] I could give it a try [17:01] yofel: That's another thing. I only did the work for the i386 version, how come it sent up two versions for different archs to the ppa? [17:01] BarkingFish: as Riddell is probably right, for now add this to your debian/rules (at the top): [17:01] export DEB_CFLAGS_MAINT_STRIP := -Werror=format-security [17:01] export DEB_CXXFLAGS_MAINT_STRIP := -Werror=format-security [17:02] I'm on an i386, i wouldn't be able to do changes for an amd64 build on a 32 bit system, surely. [17:02] BarkingFish: you just upload the sources, the builder builds for 2 arches, amd64 and i386 [17:02] BarkingFish: it always builds for all architectures launchpads supports if you use "Architecture: any" [17:02] PPA's currently support i386 and am64 [17:03] ARGH [17:03] may just me being thick but I thought it wouldn't try to build for a 64 bit system using changes generated by a 32 bit system, but whatever :P [17:03] Riddell: Nah, just 450s latency [17:03] 8 minutes lag??? [17:04] Good lord! Are you using carrier pigeon? :) [17:04] BarkingFish: Nah, just yofel's core [17:04] well, he's using my core, but I never get *that* much lag [17:04] :P [17:04] WHAT THE HELL IS GOING ON ON THAT EC2 MACHINE [17:04] and my connection didn't drop, or the core would have reconnected [17:04] Y U NO PBUILDER [17:05] Quintasan: you shouldn't need pbuilder [17:05] That's what you get for using pbuilder [17:05] the ec2 is already a nice controlled environment [17:05] good ol' dpkg-buildpackage? [17:05] debuild -S [17:05] BarkingFish: it doesn't matter what architecture you're on yourself, you define what architectures will be built with the Architecture: setting in debian/control [17:05] yofel: where was that build log from? [17:05] BarkingFish: 'any' means build for all supported archs [17:05] just got that, singed with my keys [17:05] shadeslayer: BarkingFish's ppa [17:06] so once i've added this stuff to the debian/rules file, yofel - do I then have to go through the dch -i and debuild -S etc? [17:06] BarkingFish: right [17:06] BarkingFish: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture [17:06] yofel: and that would be where? [17:06] Quintasan: are you going to change the meta package? [17:06] shadeslayer: https://launchpad.net/~lightningstrike35/+archive/ppa/+packages [17:07] Riddell: Yeah, did you push your changes to the kubuntu-packaging? [17:07] cd calligra [17:07] durrr [17:09] and just to clarify, do those commands you gave me go right at the top of the rules file, or underneath the make commands? [17:09] ah yes [17:10] Riddell: ahh, found my way, one more thing, you just debuild if you want to test if it works or input some other magic? [17:11] Quintasan: debuild will build it (which takes ages and might not be necessary for trivial changes) [17:11] debuild -S for source [17:11] * Riddell really out [17:11] yofel: those export commands go at the very very top of the rules, right? [17:11] Riddell: Thanks [17:16] BarkingFish: right [17:16] ok, doing the rework now. I'll push up as soon as possible [17:17] BarkingFish: to be precise: put them after line 1 [17:17] (looking at your rules) [17:17] done [17:17] and pushed to the ppa [17:17] yofel: what key is lp using when trying to checkout branches? -_- [17:18] ssh [17:18] durr [17:18] how the hell i am supposed to pull the code then? xD [17:18] right, now all I have to do is sit and wait until it reaches the build queue and have another shot [17:18] yeah [17:19] BarkingFish: if you're ever curious about what's the current builder state: https://launchpad.net/builders [17:19] that;s ok, i figured out how to see how far off the pack is from being built, last night it was +7 hours! [17:21] not much different today -.- [17:21] :( [17:21] you obviously haven't been around during the days when that went up to >24h [17:21] thankfully that's a rare case ^^ [17:21] well at least I'll still be awake this time when it hits the build stage, I hope. It's only 5.20pm now [17:23] Not bad today actually, yofel - the queue is only 4 hours [17:23] for i386, it's 6.5h for amd64 [17:24] yofel: any ideas why lp won't let me fetch code from ec2 machine even though I have my ssh key there? [17:24] not without an error message [17:24] ah, did you do bzr whoami? [17:24] even so, I'll be around to get the results from both :) [17:25] I just broke bzr [17:29] anyway, I'm going to go for a little while, get on with some housework, and pop back later. I need to have a rest first :) [17:29] see you in a while [17:35] did I mention apogee code is horribly formatted [17:36] I find the ^M's funnier [17:36] shadeslayer: uploading calligra, if something screws up then blame me [17:36] someone obviously used a crappy texteditor [17:36] probably gedit [17:36] hehe [17:37] Also, glib is sooooooooo screwed up [17:38] yofel: heh, I had to open it in Kate [17:38] because it looked so horrible [18:04] yofel: I understand what the problem is, but still need to figure out how to fix :P [18:06] yofel: http://stackoverflow.com/questions/4419293/warning-format-not-a-string-literal-and-no-format-arguments [18:35] arf [18:35] Quintasan: does Calligra require dcmtk? [18:41] Quintasan: bug 702026 [18:41] Launchpad bug 702026 in dcmtk (Ubuntu) "[MIR] dcmtk" [Undecided,Incomplete] https://launchpad.net/bugs/702026 [19:20] BarkingFish: there? [19:21] yup [19:21] just trying to run a diff against a couple of folders with some odd stuff going on [19:21] Well, I have a patch for libapogee to fix that build [19:22] but for some reason patch -p1<../foobar.patch fails :/ [19:22] hm [19:23] Can you send a copy of that patch to my email address please, shadeslayer, and I'll take a look at it - I've not got long before the build goes through with yofel's hack on it. [19:23] If I can get the patch to work, I can cancel those builds [19:23] Give me 5 minutes [19:23] thanks [19:24] I'm trying to figure something out which I could do with help with anyway, shadeslayer [19:25] I have two folders here, both on different SD cards. I copied the contents of my old 2GB sd card to a new 4gb card, but 4 files have not copied over, and I need to find a way (other than searching 4800 odd files) to work out which didn't copy [19:25] i tried running a straight diff -r against the two, to compare them, but diff doesn't like doing that apparently [19:26] rsync? [19:26] never used it, no idea how to :) [19:27] but i'll give it a try, anything is worth it right now. Those files are needed by the satnav on my cellphone [19:27] BarkingFish: http://paste.kde.org/186302/ [19:27] rsync -av /from/dir/ /to/dir [19:27] watch out a bit with the last slash [19:27] ^^ Yep [19:28] I usually do rsync -avz .. but then it's usually over a network [19:28] z only makes sense over a network [19:28] * yofel uses that too then [19:28] yofel: see http://paste.kde.org/186302/ [19:29] oh noes [19:29] disregard patch [19:29] it's still broken [19:30] ok, well rsync says most of the receiving card is broken [19:30] broken? how? [19:30] rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.8] [19:31] and above that stands about 1300 files which failed verification and are marked with IO errors [19:31] Better : http://paste.kde.org/186332/ [19:31] ouch [19:32] Prettier : http://paste.kde.org/186344/ [19:32] :P [19:32] hm, looks sane IMO [19:33] i'll try and recopy the folder from the old card over to the new one [19:33] BarkingFish: nope, use rsync [19:33] BarkingFish: rather check 'dmesg' for any device errors first [19:33] I/O errors don't come out of the blue [19:33] Oh also, try using --partial [19:34] allows for partial copies of files [19:34] yeah there are device errors showing on the old card [19:34] http://pastebin.com/G3TQTt5s [19:34] yofel: I have no idea where to submit the patch thought [19:35] *though [19:35] Can't find the proper project [19:35] BarkingFish: can you try to reconnect that and see if that helps? [19:35] if not try --partial as shadeslayer said [19:36] ok [19:37] nope, partial fails as well [19:38] looks like I was copying to my new card just in time, i think the old one's on the way out [19:39] hell no. It's not the old card that's messed up. It's the new one [19:39] >:( [19:40] Hmmm .?.. can you copy small amounts of data [19:40] darn [19:43] don't sweat it for a mo, I'm gonna use partition manager and clear off the new card, rewrite the FS and try again [19:57] right, I rewrote the card, I'm just gonna give it a few brief moments to sort itself out, and I'll see how it goes [20:20] I've found out what the problem was with the copies [20:21] The old card had 4 files in one folder which were root owned, when I copied the whole contents of the card back again using sudo dolphin the whole lot went over. [20:24] Riddell: Would you please answer the "Which Qt to use" question in the Plans for Precise X upload message on ubuntu-devel? [20:25] You've been tracking the 4.8 progress and I haven't. === Alcine is now known as jalcine [20:42] shadeslayer: If syncing from Debian solves the problem then I do not think we have much to do in regard to that [20:43] Quintasan: My mind can only comprehend glib currently [20:43] it's in the "glib haxoring" mode :P [20:43] WHY SO MANY PEOPLE ADD ME ON G+ I DON'T EVEN KNOW THEM [20:43] Hahaha ... [20:44] Good luck then [20:44] Quintasan: its called "Social Networking" [20:44] :P [20:44] I'm going out for more beer [20:54] Hi Everyone i am new on Distributions development i want to make some changes on kde i want a tutorials on how i can program kubuntu not making programs to it [20:54] Sifrazooy: hi [20:55] shadeslayer hii [20:55] Sifrazooy: I'm not entirely sure I understand the question though [20:55] Sifrazooy: do you want to work on a kde app or do you want to work on kubuntu? [20:57] shadeslayer mmm its a bit confusing i know because i am confused my self , for example let us assume i want to make a new distribution for Kubuntu that when i click the right-click the mouse list will be in another language how i can handle the mouse list [20:58] Okay, so basically you want to make changes to the way kubuntu looks and behaves and name it as distro X\ [20:59] shadeslayer yup and i will totally change the whole system GUI's there will be some plasmoids that will help me but i want to change what it looks [20:59] Right, so, there is a Distro called linux mint that does this actively [21:00] in order to do this, you'll need to learn packaging, more specifically how to patch your packages at build time [21:00] shadeslayer i know there is a whole punsh of linux distributions out there but what i want to do i promise u it will be totally different :D ;) [21:01] shadeslayer let us skip that for now , i want to start with the GUI , changing panels for example [21:02] shadeslayer changing how it looks not adding an applet for it [21:03] Sifrazooy: well, any change that you do on your machine will be lost if you install on another machine [21:03] Sifrazooy: So in order to permanently change the looks of KDE, you need to patch the defaults [21:04] shadeslayer i want to play with panels make some sort of things appear on them when i do some actions not how they look as colors of there width or height [21:06] you'll need to be more precise than that [21:06] there are limitations to what KDE can and can't do [21:10] shadeslayer u mean that in order to do what i want i will have to extend KDE panels , bec. what i want is not avialable on KDE :S? [21:10] Sifrazooy: Your question was very vague, what exactly do you want do with your panels [21:12] shadeslayer i want to implement a program that will make and destroy some panels and add a temprorary icons on it [21:13] Sifrazooy: #plasma can help you out with that [21:13] Probably doable with DBus [21:14] shadeslayer as for DBus isn't there any tutorials how i can edit it [21:14] there are [21:14] evening [21:14] Sifrazooy: see http://techbase.kde.org/ [21:14] Hey Riddell [21:15] Quintasan: how did the uploading go? [21:15] shadeslayer thank you and sry for ur time :D [21:15] Sifrazooy: Glad I could help in some way [21:24] apachelogger: pingo [22:16] huh, yet more calligra errors on arm [23:02] what the hell is going on with the build system tonight? [23:03] I put the source changes up for libapogee2 at 17.20 with a 4 hour wait time on the i386 version. 7 hours later, it's still not built, and apparently has at least another 9 minutes before it does. [23:06] BarkingFish: perhaps it hates you :P [23:07] i wouldn't put it past it, EvilResistance [23:07] I sent the source changes 3 times yesterday before they finally went up :) [23:07] :P [23:07] how long does it take to build? [23:08] 'tis better though than the evil of mentors.debian.net... there's lintian errors in a package i uploaded there, the same errors dont exist on ubuntu [23:08] :/ [23:09] mikecb: Locally, about 30 seconds to a minute [23:09] weird [23:10] now it's telling me it's got 7 minutes to go, yet it was 9 minutes, 6 minutes ago. [23:10] Something is definitely weird as heck there. [23:18] i have seen that often (in ppa's), I bet the build servers are just getting hammered [23:18] bbut yeah, you probably ticked it off, I know I have :D [23:22] And I'm now even more ticked off. Even with yofel's hack from earlier, it's still failed to build on i386 [23:22] EvilResistance: Check lintian with --profile debian if you're preparing a package for Debian. [23:22] I think I'm gonna have to go with Riddell and see what's different on my machine to the build servers - it builds locally, fails on the ppa build though [23:23] BarkingFish: Where's the build log? [23:23] https://launchpadlibrarian.net/90003238/buildlog_ubuntu-precise-i386.libapogee2_2.2-0ubuntu3_FAILEDTOBUILD.txt.gz [23:24] if that's ones gone, I may as well cancel the build for the amd64 version, both are building from the same source.changes [23:24] and they both failed first time round [23:24] Different build flags on the buildd I'd guess based on /build/buildd/libapogee2-2.2/ApnCamData.h:43:1: warning: 'typedef' was ignored in this declaration [enabled by default] [23:25] Once the typedef was ignored, then it lead to the other errors. [23:25] Hm. [23:25] well I've nailed the amd64 build for now, no sense in wasting time waiting for it to fail on build :) [23:26] how do I clear my PPA out of files which have not built successfully? [23:28] BarkingFish: you dont [23:28] BarkingFish: just upload a version that is higher-numbered. [23:28] BarkingFish: failed-build packages dont get published in the PPA [23:29] well, he can delete the package if he wants to, but usually one does what EvilResistance said [23:30] oh ok. I'm retrying the build, incidentally, I was using the default build deps, for the current version, and since I'm not building this for the current version, I'm trying again with the proposed section as ppa dependencies [23:30] hm, I just noticed that the package uses CDBS [23:30] probably the variables need to be defined differently then [23:30] * yofel only knows dh7 packaging [23:31] BarkingFish: proposed has no effect for precise currently [23:31] that just means that '-proposed' will be used during the build [23:31] hm. Well I'd imagine the default one doesn't either :) [23:32] I was just following the bit where you set the deps for the ppa - "Select which packages of the Ubuntu primary archive should be used as build-dependencies when building sources in this PPA." [23:32] yeah, but that's not the problem here [23:32] the default compiler settings in precise are [23:33] :/ [23:33] your package will build fine on oneiric [23:34] yeah, but I'm building against the pbuilder stuff for precise, and it's building locally on my machine, so something between here and there is obviously borken. [23:34] BarkingFish: run pbuilder update and try again [23:34] ok [23:35] BarkingFish: It's almost certainly related to the way gcc processes typedefs now, adding -proposed is not going to help. [23:35] ScottK: it's -Werror=format-security that makes it fail [23:36] Right, but why? [23:36] ok, well I've cancelled the rebuild, and we've already stripped out -Werror=format-security from the make [23:36] i did that earlier by adding some lines to the debian/rules file [23:37] BarkingFish: that didn't have an effect, not sure why (I blame cdbs) [23:37] ScottK: shadeslayer did some patching, his result: http://paste.kde.org/186344/ [23:37] so adding that would help too [23:37] yofel: That's a thought. [23:37] * BarkingFish nips off to grab that paste [23:38] but I don't know how to add patches to cdbs [23:38] Google says that a missing include for stddef.h is related to such errors. [23:38] yofel: cdbs-edit-patch $patchname. [23:45] ScottK: yeah, well i fixed all the Lintian errors in my package, i just need to make sure it builds / executes right within Debian sid (currently installing squeeze then going to update) === valorie_ is now known as valorie [23:55] ScottK: Supposing you could search the code and add that stddef.h in, would that fix it on a rebuild, or would it mess things up? [23:55] assuming that a missing #include stddef.h was the problem [23:55] You've have to add it in a patch to the .h file where the warning comes up. [23:55] Then upload a new package with that change. [23:56] so I couldn't just directly code it in wherever it was missing, assuming it is missing...? [23:58] now what the myxzptlk is going on here? [23:59] the i386 build failed, right? Not according to this: https://launchpad.net/~lightningstrike35/+archive/ppa/+packages [23:59] The box to the right shows a green tick, "All builds built successfully" [23:59] the dropdown when you click the package shows both builds failed...