[00:46] jussi: Congratulations. [01:07] Quintasan: ping [01:07] debfx: define not working at all [01:08] apachelogger: hey, I have a problem with quilt can u help? [01:08] shadeslayer: the perfect diff is -urNad [01:09] depends how quick it is solvable [01:09] * apachelogger is about to pack and go to bed [01:09] jus one thing, in quilt there is stack of all the patches that someone is applyin. Right? [01:10] apachelogger: ^ [01:10] apachelogger: when will these patches be used by upstream? [01:11] c2tarun: when you tell upstream [01:11] or [01:12] after you tell them [01:13] apachelogger: so why is it that our patch gets applied to them and then we get an error? I mean what is the point of error? there should be a message that patche applied successfully [01:17] c2tarun: you would need a rather smart artifical inteligence to decide whether a patch was applied or whether the file just changed so drastically that the patch would no longer apply [01:17] in particular too smart to realize at this time with sensible effort [01:17] hence you as packager need to subsitute [01:17] and decide on your own whether it was applied upstream or not [01:21] so after we got an error yesterday Quintasan told that patch is applied so our file is useless so we removed it. but If it is for us to decide that patch is applied or not, how come he said so? [01:21] apachelogger: ^^ [01:22] he looked at the patch and the relevant source file [01:22] compared the two [01:23] and found that our patch was applied upstream [01:23] in the best case scenario the new file will just look like the one after the patch was applied [01:23] i.e. minus removed lines and plus added lines etc. [01:24] ok, one more thing, I have the .deb file with me. What should I do now? I mean u said that our archive don't have version 2.0, so what to do? [01:24] create a debdiff and poke Quintasan with it [01:24] !debdiff [01:24] A simple way to patch Debian/Ubuntu packages is to attach a debdiff to a bug report, or send it to the team which handles the package. Learn more about it from https://wiki.ubuntu.com/PackagingGuide/Howtos/Debdiff [01:25] apachelogger: ok, and can u please name some more packages whos latest versions we dont have in archives? [01:26] just look around at kde-apps.org or qt-apps.org [01:27] * apachelogger could not name an outdated package out of the top of his head [01:27] apachelogger: sure, thanks a lot :) [01:27] yw [01:35] there is an application kpassgen : http://kde-apps.org/content/show.php/KPassGen?content=108673 i couldn't find this application in our archives, its a good application. how can I get it added to our archives? [01:36] create a new package [01:36] * apachelogger goes packing [01:37] apachelogger: ok, then again create a debdiff and poke back in here? :) [01:38] no [01:38] !revu [01:38] REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [01:41] apachelogger: thanks :) [01:50] I am trying to pack an application, since there was no debian folder there i tried to dh_make, but got this error http://paste.ubuntu.com/561213/ [01:51] ok sorry i was in wrong folder :) [01:55] this is a changelog i created, can anyone please take a look http://paste.ubuntu.com/561217/ === muesli_ is now known as muesli [03:06] hi, i was hoping that 4.6 would fix my problem but it has persisted across several versions of kde. i've got a weird problem where the screen doesn't refresh or redraw properly. it's hard to explain so i've made an album here: http://imgur.com/a/yZXGp does anyone have any suggestions? [03:07] i've created a new user account to see if it helps. it had no effect. [03:09] my video card is an intel gma4500 on a latitude e6500 notebook. changing focus on the window fixes the problem, hence the camera pics, a print screen would fix the issue before it made the capture [03:11] http://www.youtube.com/watch?v=mp982flD6pk <- ScottK now that is a blizzard :p i took that video for 30 seconds and about died [03:12] it happens on gtk apps, on qt apps, on buttons, on text entry boxes (it's even happened as i've entered text here using konversation) [03:12] and obviously, it also happens on web pages [03:17] is this the right place to bring a problem like this? [03:19] Quintan: ping [03:19] Quintasan: ping [03:31] has anyone seen anything like this? [03:33] nixternal: I heard a rumour [03:35] it is nothing more than a rumor [03:35] what was the rumor? [03:42] that he lost power due to thundersnow? [03:42] or the rumor that he might be coming back to work on documentation? [03:43] bzr checkout in effect [03:50] nixternal: your return to doc work [03:50] yeah, that would be a huge rumor :p [03:50] who told you something like that? [03:50] i know you aren't reading planet.ubuntu.com :p [03:51] LOL [03:51] Well, there *is* twitter [03:52] twitter lies [03:53] * nixternal grabs his flashlight [03:53] LOL [03:54] nixternal: Meh. I was stationed at NAS Keflavik, Iceland during the worst winter they'd had in over half a century. The wind there has about 2,000 miles of clear ocean to get going before it hits. [03:55] the power wants to go out so bad here...the lights have flickered so much it is like a disco in my office [03:55] :D [03:55] ScottK: oh yeah, been to Keflavik, you can have that place [03:55] nixternal: I'll take the powerpc box if you really don't want it. [03:56] if anyone decides to look into my problem, i just discovered that disabling compositing appears to fix that issue. [03:56] ok, we can arrange that in the next week [03:56] Cool. [03:56] ansgar_: Probably Intel issues. Intel's been crap since about Intrepid. [03:57] lucid is where it went south [03:57] that's too bad. i had always assumed that they would be well supported [03:57] For my older Intel systems Lucid was an improvement over Karmic. [03:57] I finally fixed my dumb plymouth nvidia issues [03:58] ansgar_: They made some major changes and it's taking them a long time to get it sorted. [03:58] It is, by and large, gradually improving, but it seems like it's always something. [03:58] ansgar_: switch to xrender if you want compositing [03:58] i'll keep trying every now and then. [04:01] nixternal: that appears to work also. thanks. that'll at least get me drop shadows and some transparency. [04:02] a workaround is a lifesaver. that problem was so annoying. i'll get out of you guys' hair now. [04:02] thanks again [04:05] can anyone tell me the package for KDE4, i need to add that package into build-depends. [04:07] sweet, my new-to-me dell laptop I am getting has Mobile GM965/GL960 Integrated [04:08] hope it has ok graphics [04:08] i wants my blur [05:55] http://i.imgur.com/ahfvB.jpg how is that for some snow. we can't open our front door because the drift goes from the ground to the roof [05:59] Oh jeez... [05:59] I almost feel bad for wearing shorts and a T-Shirt today. [06:07] i just attempted to go out in shorts. bad idea, very bad idea [06:08] ScottK: will try today [06:09] i need a good video camera. we are going to go skitching in about an hour. fired up the snowmobiles, now it is time to play [06:16] nixternal: omg, wow [09:11] Quintasan: ping [09:25] apachelogger: ping === hunger_ is now known as hunger [09:33] apachelogger: when opening a dvd it doesn't do anything (no playback, no error message) [10:19] The bookmark editor (in krdc, konsole,...) is misbehaving badly in KDE 4.6. Is it just me? Misbehaving = editing or adding a bookmark is very hard. You can only do it one character at a time. After each character the editor jumps to the root of the bookmarks. [10:45] JontheEchidna: why have you dropped the ubuntu font patch from gtk2-engines-qtcurve? [11:00] apachelogger: ah ... Nur worked for me in the past [11:07] c2tarun: ping [11:08] Quintasan|Droid: yup hi [11:08] Quintasan|Droid: pong [11:09] c2tarun: about bug #408964 why are you dubling the work? [11:09] Launchpad bug 408964 in Ubuntu "[needs-packaging] kpassgen" [Wishlist,Fix committed] https://launchpad.net/bugs/408964 [11:09] Quintasan|Droid: doubling means? [11:09] c2tarun: When a package is in Debian and not in Ubuntu we can sync it [11:10] c2tarun: if you didnt notice I am the bug reporter and Im currently looking for sponsor in Debian [11:10] Quintasan|Droid: i didn't knew that, I just wanted to learn some packaging, I went to kde-apps downloaded its source code and packed it. It was fun u know :) [11:11] Quintasan|Droid: actually the fact is I am getting bored all day, so I decided lets pack something, it was good. but i dont know about the term sync? what is it? [11:12] damn [11:12] c2tarun: Well, its fine but you just wasted you time in the long term :( [11:12] c2tarun: https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging [11:12] c2tarun: these bugs contain whishes for new packages [11:13] c2tarun: please also check if they were requested in Debian so you can submit them to Debian directly and then we can sync it [11:13] c2tarun: If noone is currently assigned to any of these bugs and you feel like you can do it then assign yourself [11:14] Quintasan|Droid: actually i packed one more thing, wait [11:14] shadeslayer: This QuasselDroid thingy FC's at connectiob [11:15] Quintasan|Droid: hey i lost the bug number :( of the application i packed [11:15] c2tarun: Did you assign yourself to it? [11:15] Quintasan|Droid: yup [11:16] c2tarun: check on your launchpad profile [11:17] Quintasan|Droid: got it :) https://bugs.launchpad.net/ubuntu/+bug/710347 [11:17] Ubuntu bug 710347 in Ubuntu "[needs-packaging] schedio" [Wishlist,New] [11:17] Quintasan|Droid: i packed it, but what to do now i dont know. [11:17] You should upload the changes file to REVU [11:18] c2tarun: https://wiki.ubuntu.com/MOTU/Packages/REVU [11:18] actually i went to that wesite but failed to find the upload. [11:18] c2tarun: dput revu package_version_source.changes [11:18] c2tarun: Just read it, everything is there [11:19] I can't help you now since I'm currently busy enough pretending to be doing something on IT classess [11:19] Quintasan|School: sure :) i'll try to finish it [11:19] JontheEchidna: I found that my IT classess would be a good time to bug tiriage :P [11:20] c2tarun: You will probably have some problems at the beginning but you need to live through that and you will eventually get a hang of it [11:20] It's easy after a few tries :D [11:21] Quintasan|School: sure, in case of any problem i'll ask on #kubuntu-devel or #ubuntu-motu [11:22] shadeslayer: Do we have anything that needs mentioning in the blog post related to Project Neon? [11:23] c2tarun: I suggest that you should try getting every new package to Debian instead [11:24] Quintasan|School: hey one thing please, getting into Debian and Getting into ubuntu have same processes or different [11:24] c2tarun: Mostly their are the same [11:24] c2tarun: http://www.debian.org/doc/maint-guide/index.en.html#contents [11:25] c2tarun: This is actually the most helpful guide out there [11:26] c2tarun: what will be different is probably the Maintainer field in debian/control and version in debian/changelog [11:27] I don't think dependencies will change much [11:27] okay time's up for me [11:27] see you later [11:29] Quintasan|School: bye [11:43] I have made a short (2MB) movie of keditbookmarks 4.6 weirdness. http://dl.dropbox.com/u/296786/keditbookmarks-4.6.ogv Can anyone confirm this bug, or is there something wrong with my KDE? [11:56] [docmessages] zepires * 1218463 * (52 files in 21 dirs) Finished HEAD for now [13:05] debfx: bug 693892 might be an interesting alternative to kchmviewer [13:05] Launchpad bug 693892 in kdegraphics (Ubuntu) "create separate package for okular chm files" [Undecided,New] https://launchpad.net/bugs/693892 [13:05] alvin: sorry busy testing alpha 2 candidates today [13:05] Quintasan_: dont think so .... happy blogging :) [13:06] Riddell: That's good. Do they also contain KDE 4.6? [13:06] alvin: yes [13:07] Good. I'm now installing dbg packages (maverick) because 4.6 does have a lot of crashes here. (But the NFS kioslave works again! I'm so happy) === 30BAAR3ML is now known as zegenie [13:46] We need a 'kubuntu-bug'... I'm tired of the message "this is not a genuine ubuntu package" [13:46] bleep [13:49] no, you need a apport config file and hooks for all PPA packages (not really worth the trouble IMHO) [13:50] android: you have gone over to the google mobile side too? [13:50] Riddell: yup, have had it for some time now... [13:51] Riddell: just wish I could get Qt running here [13:53] mmmm snowpocalypse :) === tarun is now known as Guest78418 === Guest78418 is now known as c2tarun [14:55] brand new alpha 2 candidates for testing! http://cdimage.ubuntu.com/kubuntu/daily-live/20110201.1/ [14:56] all fresh and exciting [15:00] Riddell: in theory yes, but upstream doesn't support out-of-source building (the chm backend even uses private header files) [15:00] debfx: ah, well there goes that idea then [15:02] debfx: could you say so on the bug and close the bug? [15:06] claydoh_: how's the alpha 2 info page doing? [15:31] all new bluedevil out if anyone is looking for things to package [15:31] (and backport) [15:33] Riddell: you mean simple packaging? [15:34] c2tarun: feel free to take it up [15:34] i can assist [15:35] Riddell: sure then :) i wanna give it a try [15:35] apachelogger: listen to Tron Legacy OST [15:35] OMG WIN [15:36] idk if i like the movie more or the OST [15:36] debfx: I requested a sync (and dropped that patch) because its no longer the default gtk theme for us [15:41] Riddell: Ping [15:49] Mueheh when you can guys update kamoso :p now that we have QtGst already in :p [15:49] hi c2tarun [15:49] sorry was busy testing CDs [15:49] c2tarun: whats the problem? :) [15:50] hmm [15:50] shadeslayer: "OST"? [15:50] Riddell: official sound track [15:50] apparently kate was brutally ripped out of kdebase along with konsole [15:51] kate was in kdesdk [15:51] hi Riddell [15:51] c2tarun: do you have a natty machine to make the package on? [15:52] Riddell: uh ... why is it under kdebase now? :D [15:52] Riddell: ya i have a pbuilder for natty [15:52] https://projects.kde.org/projects/kde/kdebase/kate/ [15:52] c2tarun: well I'm not a big fan of using pbuilder for anything other than final testing [15:53] I'm sure there are ways to use it for packaging but I've never worked it out, I just use my local system or a chroot [15:53] (or an ec2 machine) [15:53] Riddell: actually I am very new, and since morning i packed two packages in trial and find pbuilder quite comfortable. [15:54] c2tarun: maybe you could show me how to use pbuilder :) === Quintasan_ is now known as Quintasan [15:54] Riddell: and in chroot I have to uninstall all the depend* each time i quit so as to keep it clean. [15:54] Riddell: U are Riddell, what i heard about u is u are whole and sole of kubuntu :P [15:55] Riddell: https://code.launchpad.net/~neon << Check the number of owned branches [15:55] Riddell: how can I show u ? [15:56] c2tarun: I can set up my machine so we can both share a screen session and do it together [15:56] Riddell: sure :) I am just assuming that u know how to do that, coz i have no idea :P [15:57] Riddell: You are NOT using pbuilder for building packages? :O [15:59] Riddell: anyway what is there for packing? [15:59] afiestas: Whenever you can link me to source :P [15:59] Quintasan: for final testing yes but for initial packaging I do it locally, pbuilder is mainly set up to simulate the build daemons as I see it [15:59] c2tarun, Riddell mind if i join in. I have been bugging shadeslayer for quite some time about pbuilder :p [16:00] :D [16:00] I have a ninja pbuilder with deps installed right in so I'm not wasting any time [16:00] s/in./in?/ [16:00] tazz meant: "c2tarun, Riddell min? if i join in. I have been bugging shadeslayer for quite some time about pbuilder :p" [16:00] tazz: welcome :) [16:00] tazz: you want to watch c2tarun teach me how to use pbuilder? [16:00] c2tarun: where can i find your ssh key? [16:00] Riddell, affirmative. [16:01] tazz: where can I find your ssh key? [16:01] Riddell: https://launchpad.net/~c2tarun [16:01] c2tarun: ssh ubuntu@ec2-174-129-46-138.compute-1.amazonaws.com [16:01] c2tarun: screen -x [16:01] Riddell, do i PM you my key ? [16:02] tazz: better to have it in your launchpad account [16:02] tazz: its a public key ... everyone can see it :P [16:02] tazz: (public key only of course, keep the private bit private) [16:02] Quintasan: ftp://ftp.solnet.ch/mirror/KDE/unstable/kamoso/2.0-alpha2/ :p [16:02] Riddell, i am at work, the i dont have my launchpad keys on me right now. [16:02] >unstable [16:03] apt-cache [16:03] brrr [16:03] shadeslayer, to avoid spamming the channel :) [16:03] tazz: well any way of getting it to me is fine [16:03] How can I add the URL of an upstream tracker (well, bugs.kde.org) to a bug in Launchpad? [16:03] brrr.... kate takes time to compile :S [16:05] c2tarun: are you in? [16:06] Riddell: ya [16:06] c2tarun: are you sure? you're not in the last log [16:07] Riddell: chk now [16:07] I'm looking for the 'remote bug watch' button [16:07] c2tarun: in the screen session? [16:07] tazz: ssh ubuntu@ec2-174-129-46-138.compute-1.amazonaws.com [16:07] tazz: screen -x [16:08] Quintasan: the idea is to have 2.0-final (aka stable) in a matter of weeks [16:08] depends on the number of bugs we get, but alpha1 show to us that 2.0 is damn stable :p [16:08] Riddell: ya I am there now [16:08] ah k [16:08] getting to it right now [16:08] c2tarun: type something [16:09] test it yourself if you can :p [16:09] c2tarun: excellent [16:09] tazz: are you in? [16:10] Riddell: yesterday I started to think what we should create something such "KDE OS group" so all people interested in KDE as in OS can work together [16:10] afiestas: QtGst as build dep or runtime dep? [16:10] what do you think? there is anything like that? [16:10] Quintasan: build [16:10] Riddell, i get this error http://paste.ubuntu.com/561471/ [16:10] c2tarun: do you know how to start packaging this? [16:10] Riddell: packaging this means? [16:11] tazz: try now [16:11] Riddell just made me think that teaching packaging on a EC2 machine is a good idea [16:11] Quintasan: the runtime dependencies are in: https://projects.kde.org/projects/playground/multimedia/kamoso/repository/revisions/0dbca3cd89eb5998a777e92265494e5e411051f6/entry/README [16:11] c2tarun: packaging bluedevil [16:11] Riddell, yes i am in. [16:12] tazz: in the screen session? [16:12] Riddell: i know how to start packaging [16:12] i used the command 'screen -x' [16:12] tazz: type something [16:12] i did [16:12] great :) [16:12] :D [16:12] c2tarun: ftp://ftp.kde.org/pub/kde/stable/bluedevil/1.0.2/src/bluedevil-1.0.2.tar.bz2 is the new source we want packaged [16:13] afiestas: oh god, that's a lots of deps :P [16:13] c2tarun: this is a maverick machine so it'll need a natty pbuilder or similar [16:13] c2tarun: take good care of bluedevil :p [16:13] Quintasan: the only runtime debs are gstreamer-base and gstreamer-good [16:14] c2tarun: want to go ahead and start packaging it? [16:14] Riddell: sure [16:14] c2tarun: are you doing anything? [16:15] Riddell: looking at the files [16:15] c2tarun: in the screen session? [16:16] Riddell: nope [16:16] Riddell: in the tarball u gave me. [16:16] c2tarun: can you work in the screen session so me and tazz can watch? [16:16] shadeslayer: dude, that album is so old my grama already listend to it... [16:16] Riddell: meh, it seems c2tarun doesn't quite get ssh yet [16:16] apachelogger: ah ... [16:17] Quintasan: yeah :( [16:19] c2tarun: ooh, something happened :) [16:19] it'll need a sudo apt-get update to fix those missing packages [16:19] i tried to install ubuntu-dev-tools [16:19] i see a couple of 404s [16:21] c2tarun: best install ubuntu-dev-tools [16:22] Riddell: which configuration? [16:22] c2tarun: No configuration [16:22] afiestas: can you grab latest packaging of kamoso in Ubuntu and tell me if the patches are still needed there? [16:22] that debconf popup is annoying [16:24] Quintasan: where can I see them? [16:24] wait, let me upload them [16:25] Riddell: one question, how can we get bluedevil-1.0.2 files? [16:26] c2tarun: wget ftp://ftp.kde.org/pub/kde/stable/bluedevil/1.0.2/src/bluedevil-1.0.2.tar.bz2 [16:26] wget is one of my favourite command line programmes :) [16:27] afiestas: http://people.ubuntu.com/~quintasan/ [16:27] afiestas: armel-qmax-fix, ( this is probably needed), kubuntu_01_.... and vlc11-build-fix [16:28] same here... [16:28] ffff [16:29] c2tarun: stuck? [16:30] ooh that worked :) [16:30] Riddell: :) [16:31] next time use tar -jxvf [16:31] yes, tar can do the bunzip2 step for you [16:31] Quintasan: I don't understand this one: http://people.ubuntu.com/~quintasan/kubuntu_01_fix_compile.diff [16:31] tazz Riddell: ok sure :) [16:31] why replace colorCount by a hardcode value? [16:32] afiestas: * Add kubuntu_01_fix_compile.diff to cope with GCC changes that cause Kamoso to FTBFS [16:32] afiestas: from changelog [16:32] I guess it is useless now [16:32] FTBFS ? :$ [16:32] Fails To Build From Source [16:32] tazz: tar knows to bunzip, no need to give it the -j [16:32] afiestas: silly acronym for "compile error" [16:33] http://people.ubuntu.com/~quintasan/armel-qmax-fix <--this should still be valid, I will include it for alpha2+1 [16:33] Awesome [16:33] afiestas: GStreamer: WARNING: interface library not found [16:33] maco, i am probably a old school guy ^^ lol [16:33] Quintasan: you're missing a package, just a second and I can tell you what it is [16:33] JontheEchidna: line earlier say it found gsteamer :O [16:34] but not the plugin libraries [16:34] libgstreamer-plugins-base0.10-dev [16:34] I think good are needed to [16:34] too* [16:34] shouldn't be needed as a build-dep, I don't think [16:36] Riddell: should I change the name in changelog? [16:36] c2tarun: no but the version number needs changed [16:36] c2tarun: oh I see, the "Ubuntu " bit should be your name and e-mail [16:37] afiestas: okay, stuff builds without patching, I guess I will refresh the ARM one [16:37] afiestas: the rest is not needed for now? [16:37] the vlc not (we don't use vlc anymore) [16:38] vlc-fix not, compile-fix (colourCount) not, arm maybe [16:38] Riddell tazz: can you please check the version number? [16:38] c2tarun: perfect [16:41] Riddell: how can i check that is there any pbuilder env there or not? [16:42] c2tarun: there's nothing there, this is a new machine [16:42] Riddell: ok so i'll create a natty one [16:42] I'm in the meeting now [16:43] go ahead, if you get stuck ask tazz or shadeslayer or Quintasan or anyone [16:43] back in 20 minutes [16:43] Riddell: sure [16:43] WTF [16:43] apachelogger: http://java.net/projects/hudson/lists/dev/archive/2011-02/message/0 [16:43] ROFL [16:43] read the whole thread [16:48] how can i conver *.tar to *.tar.gz? [16:48] what on earth is going on [16:49] vim is borken [16:49] Quintasan: actually I bunziped the *.bz2 to *.tar then *.tar to *.orig.tar [16:50] lol [16:50] Quintasan: oh.. i thought u talking with me. [16:50] c2tarun: dude, what on earth are you trying to do? [16:50] c2tarun: if you want to unpack the source just unpack it with tar [16:51] c2tarun: the .orig. is added with "mv" [16:51] like mv source-2.0.tar.gz source_2.0.orig.tar.gz [16:51] then u unpack it [16:52] its not tar.gz that is the prob, it is just tar :( [16:52] gzip -9 [16:52] gzip -9 tar [16:52] :O [16:52] seems we both like high compression :P [16:53] thanks folks :) [16:53] FFFFFFFFFFUUUUUUUUUUUUUU- [16:55] i got and error of make: dh: Command not found [16:56] c2tarun: apt-get install debhelper [16:57] afiestas: this is magic [16:57] somehow quilt refuses to do anything with this magical source :P [16:57] more like: sudo apt-get build-dep bluedevil ? [16:58] without sudo in chroot [17:00] Quintasan: ? [17:00] afiestas: no, nothing, somehow diff magically added some lines to itself [17:00] c2tarun: hi, back, doing ok? [17:00] Riddell: stuck actually, asking from tazz [17:01] there is a perl module missing. [17:01] "dh: unable to load addon kde" that's in pkg-kde-tools [17:01] so install pkg-kde-tools [17:03] Riddell: can u see the error now? actually it never asked for my key, just reported it not available. [17:04] c2tarun: that's fine, it's trying to gpg sign it but this machine doesn't have your gpg key so that failed, but otherwise the source package is successfully built [17:04] you can run debuild -S -us -uc to tell it not to gpg sign it [17:05] but the only difference is you won't get that "failed to sign" error [17:05] Riddell: but i thought that unsigned packages are invalid? [17:05] c2tarun: you only need to sign it if you are uploading to the archive or to a PPA, but we're not doing that yet [17:06] Riddell: http://paste.kde.org/3973 <-- can you review this? [17:06] Riddell: ok so i should move on. [17:06] and you don't have upload rights to the archive anyway so it wouldn't help if you signed it when we do want to upload it [17:06] c2tarun: yes [17:08] Quintasan: "Added more build-dependencies" you should say what those build-deps are [17:09] debian/patches/armel-qmax-fix confusing not having the ".diff" on the end of that [17:09] I renamed it [17:09] to kubuntu_01_fix_qmax_on_armel.diff [17:10] * Quintasan should have added that [17:10] Riddell: Should I copy and paste what I added to build-deps or I just can sum it up with gst stuff? [17:11] Quintasan: yes, and send the patch upstream :) [17:11] Quintasan: sum it up should be ok [17:11] afiestas said he will get the ARM stuff for the next release [17:11] "Standards-Version: 3.8.4" should be increased? [17:12] Riddell: I forgot the check the version of the control file :( [17:13] c2tarun: well the bluedevil package comes from Debian so I don't think it's important, Debian will update it at some point and we will merge back with them [17:13] whereas kamoso I think isn't from Debian [17:13] It is not [17:13] 3.9.1 is the newest one? [17:13] so we need to worry about such details [17:13] I mean standards [17:13] Quintasan: yes (last I heard) [17:14] Riddell: Okay, done, anything else you can think of? [17:14] Quintasan: 2.0-alpha2-0ubuntu1 that's wrong [17:14] version number is > 2.0 [17:14] I did that? @_@ [17:14] should be 2.0~alpha2-0ubuntu1 [17:14] Oh I did [17:15] So silly [17:15] Riddell: dude ... did you try Neon? [17:16] our own people don't try neon [17:16] *sigh [17:16] shadeslayer: yes but not recently, should I give it another go? [17:16] Riddell: please do :) [17:16] * Riddell adds to todo list [17:16] shadeslayer: >implying Riddell will notice anything else than breakage [17:16] PIM is all sorts of borked tho [17:17] Quintasan: alias project-neon = "break-my -KDE" [17:17] moar like [17:17] alias project-neon="lol where are my KDE settings" [17:17] lol i was just compiling KDE from trunk and the settings for all my users vanished. [17:18] ahahahahaha ^^ [17:18] tazz: Use Project Neon [17:18] or rather were broken, and i had to rm -rf ~/.kde/ [17:18] compiling KDE is now a thing of the past [17:18] Moar powa to the user/developer [17:18] Quintasan: we should corrupt people with project-neon [17:18] Riddell: I think its ready :) [17:18] tazz: https://launchpad.net/~neon/+archive/ppa [17:19] right after you fix SIP for neon [17:19] thanks c2tarun [17:19] :> [17:19] c2tarun: is there a build log? [17:19] tazz: and report back to #project-neon [17:19] shadeslayer: How it isnt working? [17:19] Riddell: don't know, how to check that ? [17:19] Quintasan, ok, i'll try to. [17:19] Quintasan: no SIP for Mav right now [17:19] c2tarun: someone who knows how pbuilder works should know [17:19] dudes: where does pbuilder put build logs? [17:20] shadeslayer: and what happens with this? [17:20] ../ [17:20] Riddell: :( [17:20] Quintasan: what happens with what? [17:20] shadeslayer: without SIP [17:20] Quintasan: we want SIP installed in /opt/project-neon [17:20] Quintasan: PyKDE4 doesnt build [17:20] shadeslayer: Just change it your self in rules [17:20] c2tarun: Riddell its in ../ [17:21] Quintasan: no you go and fix .... im done with bindings once and for all [17:21] hm? [17:21] Riddell: are u talking about last_ope*.log? [17:21] shadeslayer: You will learn something new [17:21] Quintasan: i dont want to see another debian/rules :P [17:21] specially SIP's [17:21] shadeslayer: ../ relative to what? [17:21] here it puts build logs in /var/cache/pbuilder/.../result/ (but I guess that's my pbuilderrc) [17:21] shadeslayer: Oh sure you do, you just don't know it yet [17:21] yofel: ^ [17:21] tell him it is the turth [17:22] c2tarun: oh yes, last_operation.log seems to be it [17:22] shadeslayer: you really *really* want to look at it [17:22] Riddell: well .. did you run pdebuild? or pbuilder foo.dsc ? [17:22] yofel: no i dont! [17:22] Yes you do [17:22] Riddell: see pbuilder did it for me :) [17:22] shadeslayer: I didn't run anything, c2tarun did it all [17:22] ah [17:22] c2tarun: did you run pdebuild or pbuilder? [17:22] shadeslayer: pbuilder-dist natty build *.dsc [17:23] ah [17:23] c2tarun: /var/cache/pbuilder/results then [17:23] yofel: http://i.imgur.com/JLc08.gif on shadeslayer [17:23] :D [17:23] shadeslayer: yup [17:23] LOL [17:23] shadeslayer: no [17:23] seems to be in ~/pbuilder/natty_result [17:23] :P [17:23] shadeslayer: ~/pbuilder/natty-results [17:23] oh, that would be pbuilder-dist [17:23] ah [17:23] not pbuilder [17:24] c2tarun: ive used pbuilder/pdebuild ... never tried pbuilder-dist [17:24] oh oh [17:24] right pbuilder-dist puts tarballs in ~ [17:24] s/~/~/pbuilder/ [17:24] shadeslayer: You did something wrong... Try s/you/me/ or tell me "help sed" [17:24] Riddell, yofel, shadeslayer: you can just specify the logfile via --logfile option [17:24] like [17:24] pbuilder --build --logifile ./BUILDLOG *.dsc [17:25] * Quintasan has that set as an alias [17:25] i just use pdebuild [17:25] I have in my pbuilderrc [17:25] PKGNAME_LOGFILE_EXTENTION="_$(dpkg --print-architecture).build" [17:25] PKGNAME_LOGFILE=yes [17:25] c2tarun: the package has built but it's important to check for any new build-dependencies, by looking at the output of cmake configure in the build logs [17:25] that gives me a /var/cache/pbuilder/natty-amd64/result/project-neon-kde-workspace_0_amd64.build [17:25] Riddell: build logs means that log file? [17:26] c2tarun: yes [17:26] Riddell: ok wait let me check [17:27] Riddell: but i tried to pack an application withno build-depends in control file, I got an error each time, them i update control file and again build the package till i got all the build dependencies there. [17:27] Riddell: no error means nothing missing [17:27] Riddell: http://paste.kde.org/3976 <-- this should be good [17:28] c2tarun: some build dependencies are required and cmake should fail if you don't have them, but often with KDE programmes the build-depdencies are optional and cmake will just print a warning if you don't have them [17:29] Riddell: ok, so i should look for warnings in that log file? [17:30] c2tarun: yes, the part I'm looking at now [17:30] "-- Configuring done" there would be a warning below that if there were missing build-depends [17:30] there isn't so it's all good [17:31] Riddell: okay.. got it [17:31] c2tarun: this only makes one .deb "bluedevil" which contains all the files, but often our source packages make many .debs and you have to split up the files into the right .deb [17:31] I'm not sure how you'd do that using pbuilder [17:32] also with libraries if they had symbols files you'd need to start compiling from the start after each try [17:32] Riddell: i am not getting the part of "source packages make many .debs " [17:32] which is why I prefer to compile on a local machine of chroot first, then if there's a problem you fix it and use debuild -nc (no clear) to build without having to start all over again [17:33] c2tarun: look at the kdetoys I just downloaded, there's several .install files to split up the compiled result into several .debs [17:34] Riddell: that is new for me, never saw like that? what should we do in that scenario? [17:34] after you compile that you need to check that all the files are getting put into a .deb [17:35] but I don't know how to do that with pbuilder [17:35] Riddell: do you know what'll will happen on using pbuilder here? [17:36] list-missing hook [17:36] be back in an hour or so guy, thanks c2tarun see you at conf.kde.in ? Riddell thanks, i owe you a beer, or whatever it is that you will when we meet :p [17:36] tazz: I'll be at conf.kde.in, do they serve mango lassi? :) [17:37] :D [17:37] i'll try to get you a mango lassi. [17:37] Riddell: can i try packaging with kdetoy? [17:37] lol [17:37] tazz: im pretty sure march isn't famous for mangoes [17:37] erm -e [17:38] shadeslayer, frooty + lassi. But shshhh dont tell that to Riddell [17:38] :S [17:38] ahahaha [17:38] tazz: or slice [17:38] c2tarun: there's no new version of kdetoys so it's just for an example [17:38] slice will be better :P [17:38] c2tarun: but go ahead, run debuild and compile it (no pbuilder) [17:38] Riddell: ok sure. [17:38] <\sh> Riddell: mango lassi? bad boy .. now I need to visit my indian restaurant [17:39] c2tarun: no -S [17:39] c2tarun: we'll do a full compile [17:39] Riddell: how? [17:39] c2tarun: sudo apt-get build-dep kdetoys will install the packages it needs [17:39] c2tarun: then just "debuild" to get it compiling [17:40] Riddell: can i open multiple files in emacs and run the same operation on all of them? [17:40] im yet to learn how to manipulate multiple files :S [17:40] shadeslayer: you're asking me how or you're asking permission? :) [17:41] Riddell: im asking you how :P [17:41] shadeslayer: I would set up a macro [17:41] control-x shift-( [17:41] do what needs to be done [17:41] control-x shift-) [17:41] then control-x e to run it [17:42] hmm [17:46] Riddell: i compiled it by debuild. [17:46] now wherer can i see the deb? [17:46] c2tarun: groovy, .debs are in .. [17:46] c2tarun: but to check if there are any files that aren't installed I'd run dh_install --list-missing [17:47] Riddell: do we need to check this? I mean how could it possible that any misses an install [17:47] any file* [17:49] c2tarun: if it's a new version of the software there's very likely to be new files [17:49] (in this case I've already edited the .install files so I know there will be missing files :) [17:50] Riddell: I am still not getting, you edited the install file but still debuild will check install file or not, so it will install all the apps in that file? [17:50] Riddell: or removed something from that file? [17:50] I removed something from a couple of files [17:51] so the .debs are built but they will be missing some files [17:51] got it :) let me check [17:52] c2tarun: missing files! [17:52] now you need to work out what .install file to add them to [17:52] Riddell: ya.... ok [17:52] often that's obvious from the name of the file, sometimes you have to go searching through the sources to see what application it comes from [17:53] how can we search through the sources to see what applications are missing? [17:54] c2tarun: you can search to see where a file comes from with e.g. find . -name [17:54] Riddell: like here I have no idea in which file do the three missing apps belong [17:55] Riddell: i am not able to scroll up in the terminal :( how to scroll up? [17:56] c2tarun: in a screen session I think it's control-a PgUp [17:56] no [17:56] control-a p PgUp [17:56] let me try [17:56] ah hah [17:56] trl+1 esc pgup [17:56] control-a [ PgUp [17:57] what is it? control+a then pgup? [17:57] control-a [ PgUp [17:57] square bracket there is important [17:57] Riddell: got it :) [17:57] press return twice to go out of scroll mode [17:59] Riddell: where is tmp? [18:00] c2tarun: debian/tmp is where the files get installed to after compile, then dh_install reads the .install files and moves them to debian/, then other scripts turn debian/ into the .deb [18:01] Riddell: but how come by find we can know that which install is missing from where? [18:02] c2tarun: first one is usr/share/icons/hicolor/32x32/apps/ktux.png [18:02] that's obviously part of ktux because it's called ktux.png [18:02] so add it to debian/ktux.install [18:03] Riddell: ok, but this was obvious by name, in case we cannot guess it by name then? [18:04] then you have to know a bit about how program sources work [18:04] Riddell: okay [18:04] I know that ./ktux/data/icons/hi32-app-ktux.png will get renamed to ktux.png and installed into the icons directory [18:04] Riddell: or we can just ask from the one who created the program :) [18:04] so the file came from ./ktux so it must be part of the ktux programme [18:05] yes, asking upstream if you are unsure is a sensible thing to do [18:06] Riddell: getting bit, how missing installs supports the fact that not using pbuilder-dist is better move [18:06] Riddell: we can check these missing installations after pbuilder as well (can't we?) [18:07] c2tarun: I don't think you can, once pbuilder is finished it deletes the build [18:07] yes, but only if you define it in debian/rules, you can't run dh_install --list-missing by hand after pbuilder finishes [18:07] you'd need to have a pbuilder hook that gets run during the build as Quintasan says [18:08] Riddell: but in chroot we have to install all the build-dependencies, ok. what if we are packaging a completely new source code with no debian folder? [18:08] c2tarun: then you make a debian/ folder [18:09] the README or INSTALL should explain what's needed [18:09] alternatively, you watch it fail in pbuilder on the configure step over and over [18:09] and keep adding what it said was missing [18:10] maco: today i packed kpassgen that have no info about build-dep* in README or INSTALL file. [18:10] :( @ upstream [18:10] you would need to read the output of cmake to know what it needs [18:10] maco: suppose all the depen* needed are already installed in your chroot, then our package will be created automatically with a blank control file. :( [18:11] c2tarun: a blank control file? [18:11] maco: means build-depends section blank, [18:11] mmm well then thatd mean that it only requires build essential...which would be odd [18:12] maco: yup, so either we uninstall all the dep* we installed before exiting chroot or it will all go wrong. [18:12] there's no perfect way to do it, but I'd read the cmake output and work out what packages it needs from that, then to be sure I'd got it right I'd build it with pbuilder [18:12] c2tarun: are you manually chrooting? [18:13] c2tarun: because if you use pbuilder, it *does* automatically uninstall all the deps it installed [18:13] maco: i think it does. [18:14] so i dont see where the problme is [18:14] if packages werent automatically uninstalled and you had cruft from previous builds, yes thatd be bad and screw up your "are my build deps right?" checks, but they are removed so it all works out [18:14] the problem is nowhere :) the thing is I was trying to understand why we should not use pbuilder directly :) [18:15] c2tarun: I don't think you can, once pbuilder is finished it deletes the build <-- this what you're wondering about? [18:15] you can chroot into it yourself too and view the log [18:15] ScottK has shown me how before [18:16] Riddell: can i log into pbuilder and see? [18:16] c2tarun: I only use pbuilder as a final check because it doesn't (easily) let you adjust a package then continue on [18:16] c2tarun: maybe but I don't know how [18:16] [messages] asserhal * 1218517 * trunk/ (38 files in 20 dirs) SVN_SILENT updated translations [18:17] c2tarun: anyway, I've tested the .deb for bluedevil and it's all working so I'll upload [18:17] thanks a lot of packaging, your ninja skills are good :) [18:17] Riddell: I dont think that till now I am a ninja :) [18:18] c2tarun: one issue is you turned the .bz2 into a .gz, we don't need to do that as .bz2 are supported directly these days and it's best to stay with what upstream gives us if we can [18:18] Riddell: I didn't knew that, I'll keep that in mind [18:19] * yofel wonders if we'll get .tar.xz support before KDE5 in launchpad... [18:20] c2tarun: oh and if you were interested you could backport this to maverick [18:20] Riddell: hey i dont understand the concept of backport, can you please explain me a bit? [18:22] c2tarun: maverick was released last year and now we're developing for natty and that's where our new packages go. but some people want to use maverick with the latest packages so we have a maverick-backports repository which has natty packages recompiled to run on maverick [18:22] c2tarun: so to get a backport you need to check that the package compiles and runs on natty [18:22] sorry, check that the package compiles and runs on maverick [18:23] Riddell: ya :) [18:23] then you file a bug and someone will approve it and it'll get put into maverick-backports [18:23] Riddell: can't I put it into maverick-backports by myself? [18:23] Just installed KDE 4.6 from kubuntu-backports, and KNotify is segfaulting... anyone have any ideas? [18:24] c2tarun: it gets put into maverick-backports with a script (to minimise errors) which is run by an archive admin (such as me) [18:24] Riddell: got it :) you are the Boss ;) [18:24] it shows two error messages about " can't write to /tmp//.kde/... [18:24] c2tarun: so I think you need to set up a maverick pbulider and check the package compiles there, then test the .deb installs and runs [18:26] Riddell: I don't know how to access files in home folder from pbuilder chroot [18:26] c2tarun: why do you need to? [18:27] Riddell: because to install inside pbuilder we have to log in into pbuilder chroot first. then only we can install ( I guess?) [18:28] c2tarun: if you're running maverick you can download the .deb onto your computer and install it there [18:29] but first set up the maverick pbuilder and build bluedevil in it [18:29] Quintasan: proptip: apt-cache policy debian-policy [18:29] insta-standards-version [18:29] *protip [18:30] Riddell: I have a maverick pbuilder and a natty pbuilder-dist onto my system, I can use the mav one [18:31] c2tarun: if you want to use the maverick pbuilder on your computer you should download (with scp) the bluedevil sources from the ec2 machine we've been using [18:31] Riddell: dont know how to do that :( [18:32] scp ubuntu@ec2-174-129-46-138.compute-1.amazonaws.com:bluedevil-1.0.1/new/* . [18:32] running that from your computer will use scp (ssh copy) to download the files [18:32] Riddell: what is scp anyway? [18:33] c2tarun: ssh copy [18:33] copies files using ssh [18:34] Riddell: Ya its downloading :) but creating a deb file on my net connection will take around an hour or more :( and it is 12:05 AM here, so I can't check it today. [18:34] c2tarun: you could also use that ec2 machine [18:35] * superfly wanders off to find help elsewhere [18:35] superfly: sorry I've not heard of such a problem and am busy with other things just now [18:36] c2tarun: or you could sleep and do it tomorrow :) [18:36] Riddell: but still I dont know how to access files of home folder from pbuilder. :( [18:36] you should not need to [18:36] c2tarun: why would you need to? you only need to do the same as you did before when building it for natty [18:37] create the pbuilder, build with .dsc file, .deb files should get made, download those and test locally [18:38] Riddell: test locally means on my system right? don't you think that'll effect my bluetooth software? [18:39] Riddell: bluedevil is already installed on my system. [18:40] c2tarun: maybe, that's what we need to test [18:40] if it breaks your bluetooth then we'll know not to release it to the world [18:40] if it works, then it should be ok to release to the world [18:40] Riddell: O_O [18:41] part of being a developer is the risk of having your own system broken :) but you can always install an older version [18:41] * superfly spies a few packages that weren't upgraded [18:41] perhaps that's the problem [18:41] Riddell: are u joking :( ok i'll install a kubuntu in virtual box and test it :) [18:41] its not like itd break it permanently.... [18:42] you'd just dpkg -i and install the old package and be back to normal [18:42] c2tarun: I tested the natty bluedevil .deb we made locally, I wouldn't upload software to the archive unless I've tested that it works first [18:42] Riddell: testing in virtual box will be fine or not? or I have on spare kernel on my system :) i can install KDE on that and test it ;) [18:43] c2tarun: you dont install packages per-kernel... [18:43] i dont know if a vbox would work for bt. does vbox recognise bt devices? [18:44] I also don't know if virtual box can talk to bluetooth [18:44] but there really wouldn't be a problem testing it on your machine, if it doesn't work just reinstall the old version [18:44] Riddell: sure :) i'll test it. [18:44] Riddell: but not today, i haven't called my gf since eve, i gotta go :( [18:45] good night c2tarun, thanks for packaging bluedevil, your ninja skills are strong [18:46] Riddell: I'll test it :) and come again on #kubuntu-devel by 16:30 UTC, till then bye. tc :) [18:52] good find yofel :) [18:52] :D [18:53] tazz: you're also interested in helping Kubuntu? === Mamarok_ is now known as Mamarok [19:09] Ah, there we go... that worked [19:10] superfly: what did you do? [19:11] I just installed the extra packages that hadn't been upgraded [19:11] forgot I needed to do a "full-upgrade" [19:16] night everyone [19:17] guid nicht shadeslayer [19:17] hehe [19:20] nini shadeslayer [19:24] Riddell, yes. [19:24] i plan to. [19:26] tazz: doing packaging or other stuff? [19:26] Riddell, yea, i already build rpms for my company. [19:26] so why not :) [21:17] [messages] fric * 1218562 * trunk/l10n-kde4/sk/messages/ (24 files in 13 dirs) Updated Slovak translation [21:19] whoot [22:56] [messages] kristofk * 1218568 * trunk/l10n-kde4/hu/messages/extragear-sysadmin/desktop_extragear-sysadmin_libqapt.po SVN_SILENT Hungarian translation updated [23:00] omg the CIA watches me:o [23:01] it has a filter on libqapt. I thought we had turned off l10n messages though [23:05] Whos bright idea was it to license the Kubuntu docs and KDE docs under different licenses? [23:05] :P