[02:09] <directhex> isn't python 2.7 out now? what about *that* shizzle, when upstreams are still sticking with 2.5?
[02:10] <ajmitch> it'll get there, one day
[02:11] <ajmitch> not sure if it'll be in maverick or not, I think it was suggested
[02:12] <directhex> well, mono 2.6.7 will be there, who needs python?
[02:12] <ajmitch> sane people
[02:13] <ajmitch> you see, people actually use python so they notice when it breaks
[02:13] <directhex> yeah, in every minor version bump. solid Enterprise software!
[02:13] <ajmitch> it's called Progress
[02:15] <directhex> bedtime.
[02:15] <ajmitch> farewell :)
[05:47] <simar> hello vish
[06:44] <bilalakhtar> Hello there. If in a merge, compat level is set to 6 but debhelper is >= 7 in build-deps, what should I do?
[06:44] <bilalakhtar> tumbleweed: u there?
[06:54] <bilalakhtar> Hello there. If in a merge, compat level is set to 6 but debhelper is >= 7 in build-deps, what should I do?
[07:00] <RAOF> Leave it as it is, generally.  Compat level and required debhelper version don't have to be the same.
[07:01] <RAOF> Because you can use debhelper commands found only in newer debhelper versions without necessarily wanting the changed behaviour of all the other debhelper tools.
[07:40] <dholbach> good morning
[08:22] <Rhonda> hmm, my link scrolled off already.  %-/
[09:57] <huats> morning
[10:03] <directhex> YokoZar, was there ever a reason discovered for why wine breaks when built with -Bsymbolic-functions ?
[10:03] <YokoZar> directhex: not to my knowledge
[10:04] <YokoZar> directhex: that PGO audio garbling issue was pretty weird
[10:04] <directhex> hm. i'm facing the same problem in the chromium bridge for moonlight (segfaults of built with -Bsymbolic-functions)
[10:46] <simar> Anybody knows to which package does these files belong pk11pub.h  secerr.h  pk11func.h  keyhi.h
[10:46] <simar> I'm try to solve a FTBFS
[10:48] <simar> What may be the cause of this in the build cause
[10:48] <simar> WeaveCrypto.h:44:21: error: pk11pub.h: No such file or directory
[10:48] <simar> WeaveCrypto.cpp:47:20: error: secerr.h: No such file or directory
[10:48] <simar> WeaveCrypto.cpp:49:22: error: pk11func.h: No such file or directory
[10:48] <simar> WeaveCrypto.cpp:50:19: error: keyhi.h: No such file or directory
[10:49] <simar> I have checked the debian/control two packages are not found on maveric but are avaliable on older systems..
[10:50] <jpds> libnss3-dev: /usr/include/nss/pk11pub.h
[10:51] <jpds> And so are the rest.
[10:51] <geser> libnss3-dev
[10:51] <jpds> geser: Morgen.
[10:52] <simar> jpds, xulrunner-dev is not found for maverick but exist in the debian/control file as a dep?
[10:53] <simar> jpds, I'm new to FTBFS . I need your help in this?
[10:53] <jpds> simar: I think you can remove that, and add libnss3-dev.
[10:54] <simar> jpds, http://launchpadlibrarian.net/50411959/buildlog_ubuntu-maverick-i386.weave_1.3-2_FAILEDTOBUILD.txt.gz   is the build log
[10:54] <simar> jpds, if you want to have a look
[10:55] <simar> jpds, i will just try it ... thanks though :)
[10:59] <geser> simar: the ubuntu mozilla team is checking if this package will stay in the archive (see the mozilla support policy) or get dropped. please contact them before wasting time on fixing this FTBFS.
[11:01] <simar> geser, Actually i had a class by danial on 12th on packaging, there he suggested that this one we can try for practise and ask if anthing goes wrong on #ubntu-moto
[11:04] <simar> jpds, still the same errors come .. :(
[11:04] <simar> In file included from WeaveCrypto.cpp:41:
[11:04] <simar> WeaveCrypto.h:44:21: error: pk11pub.h: No such file or directory
[11:04] <simar> WeaveCrypto.cpp:47:20: error: secerr.h: No such file or directory
[11:04] <simar> WeaveCrypto.cpp:49:22: error: pk11func.h: No such file or directory
[11:04] <simar> WeaveCrypto.cpp:50:19: error: keyhi.h: No such file or directory
[11:04] <simar> and even more i think :(((
[11:07] <shadeslayer_> hmm.. so once again... My LP page : launchpad.net/~rohangarg , should i apply for MOTU with that amount of contribution or should i contribute more???
[11:07] <shadeslayer_> ( before applying )
[11:11] <simar> shadeslayer, hi
[11:11] <shadeslayer_> simar: \o
[11:11] <shadeslayer_> simar: im at work currently ... wont be able to help alot :D
[11:11] <simar> shadeslayer, np :>
[11:11] <shadeslayer_> also.. im leaving for home in 2 mins
[11:12] <simar> shadeslayer, by the way best of luck for your MOTO app, :>>
[11:12] <shadeslayer_> simar: feel free to leave messages/PM's on my core account ( shadeslayer )
[11:12] <jpds> simar: chrisccoulson is the mozilla wiz, he might be more useful than me with your problem,
[11:13] <chrisccoulson> hi :)
[11:13] <simar> shadeslayer, i think you should be ... you really help by your own wish...
[11:13] <simar> shadeslayer, sure i will .. :))
[11:14] <shadeslayer_> simar: hehe :D
[11:14]  * shadeslayer_ catches jpds 
[11:14] <simar> shadeslayer, :D
[11:14] <shadeslayer_> jpds: any suggestions
[11:17] <shadeslayer_> ok gtg now... cya later... any suggestions go to shadeslayer :D
[11:17] <shadeslayer_> ill see them later :P
[11:22] <geser> simar: looks like dholbach picked a bad example
[11:23] <simar> geser, why?
[11:23] <simar> geser, could you suggest me a better?
[11:24] <simar> geser, that is easy for me..
[11:25] <geser> simar: because of the mozilla support policy that package (weave) might get removed from the archive because it's unsupportable in the long run
[11:25] <simar> geser, any better alternative please??
[11:25] <geser> one moment, I'm looking
[11:29] <simar> geser, thanks you so much for your effort :->>
[11:31] <geser> simar: openinvaders, see http://people.ubuntuwire.org/~lucas/ubuntu-nbs/32/open-invaders_0.3-1_lubuntu32.buildlog for the failure
[11:31] <geser> simar: kball (also from http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi) has the same problem
[11:34] <simar> geser, :)
[11:34] <simar> geser, i'm looking at it.
[11:37] <simar> geser, I thing, when sladesyaler means to leave message, does he mean to leave it on wiki ??
[11:53] <simar> geser, whats the difference between the list of FTBFS you provided http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi  and the the last one in /topic
[11:53] <simar> oh !!
[11:54] <simar> sorry for that
[11:54] <simar> :
[11:54] <simar> :(
[11:54] <jpds> Interesting topic.
[11:54] <simar> jpds, ya !!
[11:54] <simar> jpds, my mistake
[11:56] <simar> jpds, geser Whats the diff b/w http://qa.ubuntuwire.com/ftbfs and http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi list of FTBFS ?
[11:57] <geser> simar: the one on qa.ubuntuwire.com/ftbfs is the list of current FTBFS (from recent uploads to the archive) while the other is the result from a complete archive rebuild
[11:57] <geser> it has packages that build successfully in the past but don't anymore
[11:58] <simar> geser, ok and thats because of change in other dep package probably ...
[11:58] <simar> then i think rebuilds are easy to handle ...
[11:58] <geser> simar: the one on qa.ubuntuwire.com/ftbfs is the list of current FTBFS (from recent uploads to the archive) while the other is the result from a complete archive rebuild
[11:58] <geser> the second one has packages that build successfully in the past but don't anymore
[12:01] <simar> what a bad luck!! dget -xu https://edge.launchpad.net/ubuntu/+archive/primary/+files/open-invaders_0.3-1.dsc build successfully.
[12:01] <simar> using pbuilder
[12:01] <geser> in a maverick pbuilder?
[12:03] <simar> geser, ya I have set  DISTRIBUTION=maverick in ~/.pbuilderrc
[12:04] <simar> geser:- let me try kball then
[12:04]  * geser checks
[12:05] <geser> I can reproduce this in my AMD64 maverick pbuilder
[12:07] <geser> simar: check if your pbuilder is really for maverick: "pbuilder login" and then inside the pbuilder "cat /etc/apt/sources.list" and check if it lists maverick
[12:08] <simar> geser:- i'm checking
[12:08] <simar> geser in kball build log i've found
[12:08] <simar> Unpack source
[12:08] <simar> ─────────────
[12:08] <simar> gpgv: keyblock resource `/home/user/.gnupg/trustedkeys.gpg': file open error
[12:08] <simar> gpgv: Signature made Tue Apr  7 05:58:50 2009 CEST using DSA key ID 4B394F7E
[12:08] <simar> gpgv: Can't check signature: public key not found
[12:08] <simar> dpkg-source: warning: failed to verify signature on ./kball_0.0.20041216-6.dsc
[12:09] <simar> and src/gamemenu.cpp:224: error: 'mkdir' was not declared in this scope
[12:11] <simar> geser:- I think you are right i can see Lucid there
[12:11] <simar> root@simar-laptop:/# cat /etc/apt/sources.list
[12:11] <simar> deb http://archive.ubuntu.com/ubuntu/ lucid main universe multiverse restricted
[12:11] <simar> #deb-src http://archive.ubuntu.com/ubuntu/ lucid main universe multiverse restricted
[12:11] <simar> root@simar-laptop:/#
[12:12] <simar> geser:- but I have set DISTRIBUTION = maverick in .puilderrc
[12:15] <geser> did you add it after you created the pbuilder or before?
[12:16] <dholbach> geser: sorry for that
[12:23] <geser> dholbach: no problem, I only recently saw that it is probably affected by the Mozilla support policy
[12:35] <simar> geser:- I added after but then i run sudo pbuilder update shadeslayer told me this ..
[12:35] <geser> try "sudo pbuilder --override-config update"
[13:05] <tumbleweed> bilalakhtar: you pinged me?
[13:05] <bilalakhtar> tumbleweed: yes
[13:05] <bilalakhtar> tumbleweed: I needed help in something. someone else helped me
[13:05] <bilalakhtar> tumbleweed: sorry if I caused you some problem
[13:06] <tumbleweed> bilalakhtar: np
[13:06] <bilalakhtar> tumbleweed: My question was, if dh (>= 7) in build-deps, then compat=7 is necessary or not?
[13:06] <bilalakhtar> becoz in a merge, compat was 6 and dh >=7
[13:07] <tumbleweed> yeah, we don't things like that unless we have to
[13:27] <directhex> what are the consequences of not compiling with -Bsymbolic-functions?
[13:33] <geser> bug #230460 explains it a little bit, perhaps that's the case here too
[13:36] <directhex> geser, so is blanking LDFLAGS to fix a Bsymbolic-functions problem an acceptable path to take?
[13:39] <geser> directhex: if it solves then yes, please document it on https://wiki.ubuntu.com/CompilerFlags (like the libxfont1 entry) in that case
[13:41] <directhex> wine should be in that list
[13:42] <directhex> wine blanks ldflags, there's a link in debian/rules to rationale
[14:49] <Quintasan> dholbach: ping
[14:50] <dholbach> Quintasan: pong
[14:50] <Quintasan> dholbach: about daily builds, do you how can I force stripping debug libs?
[14:51] <dholbach> I don't think we do anything special to debug libs in PPAs
[14:51] <dholbach> but you can ask in #launchpad
[14:51] <dholbach> otherwise dh_strip should do its regular job, no?
[14:52] <Quintasan> nope, build log says stripping is disabled on PPA builds
[14:52] <Quintasan> james_w said he is working on it but it won't hurt if I could find some workaround
[14:53] <dholbach> I'm sorry, but I have no idea what's happening there
[14:53] <dholbach> does dh_strip not do its job in PPA builds?
[14:53] <james_w> Quintasan: I didn't say that, I said that dh_strip is getting called as normal in your build log
[14:53] <james_w> what is disabled on PPA builds is the stripping to -dbgsym packages that every Ubuntu package does
[14:54] <dholbach> ah ok, that makes more sense now
[14:54] <Quintasan> oh, I must've misread, sorry
[14:55] <Quintasan> james_w: you have mentioned something about missing -a switch to dh_stip, I can't find it in man dh_strip, what it does?
[14:55] <james_w> Quintasan: see "man debhelper"
[14:56] <Quintasan> oh, okay
[14:57] <Quintasan> I'll customize rules even further then
[15:00] <dupondje> can somebody take a look @ https://bugs.launchpad.net/ubuntu/+source/aegir-provision/+bug/543662
[15:01] <dupondje> its fixed in debian, just need sync :)
[15:07] <geser> dupondje: so file a sync request for maverick and extract the changes for an SRU for lucid (if you want to see it fixed there too)
[15:08] <dupondje> tought a normal bug would be ok ;) but i'll do a sync req
[15:11] <geser> dupondje: you can update that but to a sync request
[15:13] <dupondje> https://bugs.launchpad.net/ubuntu/+source/aegir-provision/+bug/605895
[15:22] <dupondje> geser: if you feel syncing it, feel free ;)
[15:24] <carstenh> dupondje: thanks again for taking care :)
[15:25] <dupondje> héhé np, its good bugs get killed :)
[15:26] <carstenh> dupondje: did you use a launchpad e-mail interface to file this bug? if you did, where can I find information about this?
[15:27] <dupondje> requestsync <package>
[15:27] <dupondje> :)
[15:27] <dupondje> console ftw!
[15:27] <carstenh> :)
[15:28] <dupondje> it's in ubuntu-dev-tools
[15:28] <wgrant> carstenh: https://help.launchpad.net/Bugs/EmailInterface
[15:29] <dupondje> you have more permissions btw in tru the email interface ?
[15:29] <dupondje> cause with requestsync I can set bugs as 'wishlist'
[15:29] <dupondje> with the http interface not :)
[15:34] <carstenh> wgrant: looks great, thanks :)
[15:39] <tumbleweed> micahg: btw I sat down and wrote a better grab-udd-merge lp:~stefanor/ubuntu-dev-tools/grab-udd-merge if you have any interest
[15:40] <micahg> tumbleweed: k, thanks :)
[15:40] <micahg> tumbleweed: I'll give it whirl this weekend
[15:41] <tumbleweed> cool. could use some testing
[16:18] <ari-tczew> statik: ping
[16:29] <ari-tczew> statik: ok, so I'm leaving message then: could you clean-up on https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda ? your link in MOTU field leads to another application instead MOTU (stricte developer) application.
[16:31] <micahg> ari-tczew: why is that a problem?
[16:32] <ari-tczew> micahg: mess
[16:32] <micahg> ari-tczew: it looks fine to me
[16:32] <ari-tczew> micahg: it not looks fine for me
[16:33] <micahg> ari-tczew: the DMB members already numbered the apps, why are you worrying about it
[16:34] <ari-tczew> micahg: hmm, maybe yes
[16:37] <dholbach> Day 4 of https://wiki.ubuntu.com/UbuntuDeveloper Week starts in 23 minutes in #ubuntu-classroomDay 4 of https://wiki.ubuntu.com/UbuntuDeveloper Week starts in 23 minutes in #ubuntu-classroom
[16:41] <ari-tczew> dholbach: above link now works
[16:41] <ari-tczew> s/now/not
[16:41] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek
[16:41] <dholbach> sorry
[17:01] <lfaraone> If a package does not have a patch system, would it be a bad idea to add one during a SRU?
[17:01] <micahg> lfaraone: yes :)
[17:17] <lfaraone> If foo-1.2-1 in Maverick fixes 20 high-value bugs that were in foo-1.1-1 that would all be candidates for SRU, and nothing else, can we upload foo-1.2-0ubuntu0.10.04.1
[17:19] <lfaraone> *?
[17:48] <simar> shadeslayer: hi
[17:48] <shadeslayer> simar: \o
[17:48] <shadeslayer> simar: a bit busy with koding.. but go ahead :D
[17:49] <simar> shadeslayer: should i write testimonials on your wiki, may help you in your MOTO app
[17:49] <shadeslayer> simar: MOTU.. and no.. im not applying right now :D
[17:49] <shadeslayer> maybe after another month
[17:49] <shadeslayer> or 2 weeks... if time permits
[17:50] <simar> shadeslayer: k, fine
[17:50] <simar> shadeslayer: go ahead with coding. c ya
[17:50] <shadeslayer> ciao
[18:01] <ari-tczew> slangasek: have you got some time for help?
[18:10] <slangasek> ari-tczew: afraid not right now, but you can ask and I'll answer as possible
[18:11] <ari-tczew> slangasek: I'd like to get a lesson about bzr merging from you.
[18:12] <slangasek> ari-tczew: my latency will be high, but I'm happy to answer your questions :)
[18:16] <ari-tczew> slangasek: so maybe another time, I prefer to active discussions
[18:16] <ari-tczew> but thanks for reply
[18:17] <slangasek> ok
[19:13] <fabrice_sp> porthose, did my email bring some improvement to your pb?
[19:15] <porthose> fabrice_sp, yes it did thx, busy testing the fix right now, will probably require an SRU :)
[19:16] <fabrice_sp> cool :-)
[20:03] <simar> geser: heya atleast i can reproduce the failed build of openinvaders ..
[20:06] <dupondje> fabrice_sp: can you SRU also ?
[20:07] <fabrice_sp> I can upload to -proposed, but it still needs a ubuntu-sru for acking
[20:07] <fabrice_sp> why?
[20:07] <dupondje> https://bugs.launchpad.net/bugs/605895
[20:07] <dupondje> should be added in lucid also, quite important bug ...
[20:08] <fabrice_sp> we can't SRU a new version
[20:08] <fabrice_sp> you should generate a minimal patch on the top of the lucid's version
[20:08] <fabrice_sp> even it the result is the same :-)
[20:08] <dupondje> ah didn't know :(
[20:09] <fabrice_sp> the versioning is different
[20:10] <fabrice_sp> !sru | dupondje
[20:11] <fabrice_sp> you have a link there to the versioning scheme and what to do
[20:11] <dupondje> will check, thx
[20:12] <fabrice_sp> thanks to you to help making ubuntu better ;-)
[20:13] <dupondje> always :)
[20:15] <ari-tczew> Quintasan: ping
[20:31] <ari-tczew> debfx: are you going to merge virtualbox-ose?
[20:35] <carstenh> fabrice_sp: this patch is minimal
[20:36] <fabrice_sp> carstenh, I'm not saying it's not: the version has to be different
[20:36] <carstenh> fabrice_sp: and i should remember that i should first read the complete discussion before i answer :)
[20:36] <fabrice_sp> :-)
[21:06] <ari-tczew> tumbleweed, lool, : new libsmbios version pushed to bzr. bug 591017
[21:09] <simar> dupondje: hi, could help me out with these FTBFS.
 any idea about this error init.cc:303: error: 'mkdir' was not declared in this scope
[21:10] <dupondje> sys/stat.h included
[21:10] <dupondje> ?
[22:04] <doctormo> OK odd
[22:04] <doctormo> No one in this room
[22:05] <simar> dupondje: This is a rebuild error. I think i must be..
[22:07] <BlackZ> doctormo: ask the question
[22:08] <simar> BlackZ: can you help me plz
[22:08] <doctormo> BlackZ: Oh well, my irc client shows no one in the room.
[22:08] <ajmitch> we don't really exist in your reality? :)
[22:08] <BlackZ> simar: if I don't know what's your problem I doubt I can
[22:09] <shadeslayer> ajmitch: or maybe different dimensions,connected through the IRC :P
[22:09] <doctormo> OK, so if you wanted to get a package into debian, your first job is to dput to REVU right?
[22:09] <shadeslayer> doctormo: no
[22:09] <shadeslayer> doctormo: if you want it in Debian it goes to mentors.debian
[22:09] <fabrice_sp> simar, don't assume it is: check the source
[22:10] <shadeslayer> doctormo: also,if you want it in Ubuntu,then it goes to revu
[22:10] <fabrice_sp> as we have a higher version of gcc in Maverick than in Lucid, some packages FTBFS because of missing headers
[22:10] <fabrice_sp> simar, ^
[22:10] <simar> BlackZ: I'm working on some FTBFS .. has really wired experience. Tried many but not successful in any :((
[22:10] <shadeslayer> but its always prefered that it goes to debian first and then ubuntu
[22:10] <shadeslayer> simar: want some easy ones?
[22:10] <porthose> doctormo, first you need to submit an ITP bug againts wnpp so you can close it in the changelog
[22:10] <BlackZ> hey fabrice_sp :p
[22:11] <simar> shadeslayer: ya, eager need ..
[22:11] <ajmitch> doctormo: what are you trying to get into debian?
[22:11] <doctormo> OK, so this is a complex process, I'm trying to condense it down to a single page. Something simple with commands or social instructions.
[22:11] <simar> fabrice_sp: i'm checking, thanks though for help :)
[22:11] <shadeslayer> simar: http://people.ubuntuwire.org/~lucas/ubuntu-nbs/64/kcollectd_0.9-2_lubuntu64.buildlog
[22:11] <shadeslayer> simar: ftbfs due to docbook issue
[22:12] <simar> shadeslayer: whats docbook issue?
[22:12] <shadeslayer> all docbooks should now be in 4.2 format,but i _think_ that this one has it in 4.1.2
[22:12] <fabrice_sp> simar, yw :-) And the one you picked i quite easy, and will show you how to patch , so it's a good example
[22:12] <shadeslayer> simar: hmm.. docbook == documentation for the app
[22:12] <ScottK> shadeslayer: Fixed kdesudo yet?
[22:12] <shadeslayer> ScottK: :S
[22:12] <ScottK> Is that a yes or a no?
[22:12] <simar> shadeslayer: ok
[22:12] <shadeslayer> ScottK: nope
[22:12] <shadeslayer> i was hacking on Qt :P
[22:13] <ScottK> Doesn't help with kdesudo ....
[22:13] <shadeslayer> hehe :P
[22:13] <shadeslayer> ScottK: also,i poked #kde-devel about it and they said they dont support kdesudo.. or something of that sort
[22:14] <ScottK> shadeslayer: They don't. It's not a part of core KDE.
[22:14] <shadeslayer> i think they said that its not a KDE module... dont remember the exact works
[22:14] <shadeslayer> *words
[22:14] <ScottK> It's not
[22:14] <shadeslayer> ScottK: ok,didnt know
[22:15] <shadeslayer> ScottK: ok what ill do is,ill fix digikam -> kdesudo -> other docbook ftbfs
[22:15] <ScottK> Great.
[22:15] <ScottK> digikam seems fine now though.
[22:15] <ScottK> ia64 built after apachelogger's pkg-kde-tools fix.
[22:15] <shadeslayer> uh..ok,ill just give it a run through pbuilder...
[22:16]  * ScottK didn't check.
[22:16] <ScottK> Good idea.
[22:16] <shadeslayer> just in case :D
[22:17] <shadeslayer> ScottK: need help with setting up krazy tho
[22:18] <shadeslayer> ScottK: i cant get it to check the docbook
[22:18]  * ScottK has never used it.
[22:18] <shadeslayer> omg... its checking
[22:18] <shadeslayer> i dont know.. it didnt yesterday
[22:29] <simar> shadeslayer: Thanks, I think i will work on it tomorrow :)
[22:29] <shadeslayer> np
[22:30] <fabrice_sp> simar, so you give up with the missing stat.h header?
[22:30] <simar> shadeslayer: Are there any resources present anywhere about fixing, like eg - the workflows how should we look to the problem step by step  ,,,
[22:31] <shadeslayer> simar: uh.. look at build log -> find error -> try to fix error with patch/missing dep/magic -> post debdiff here
[22:31] <shadeslayer> ( in a pastebin ofcourse )
[22:31] <shadeslayer> simar: but feel free to ask around if you get stuck
[22:32] <fabrice_sp> and google :-)
[22:32] <shadeslayer> like right now i am :P
[22:32] <shadeslayer> oh google++
[22:32] <shadeslayer> and google is failing me :D
[22:32] <fabrice_sp> :-)
[22:32] <simar> fabrice_sp: I tried grep -r Update()         function name but the there is no response . I don't know how to find the fnction from the src folder . There are indeed a lot of files there...
[22:32] <shadeslayer> simar: its grep -R foo path/to/foo.h
[22:33] <shadeslayer> or.. grep -R foo path/to/foo/
[22:33] <geser> simar: any success with the FTBFS I pointed to you?
[22:33]  * shadeslayer thinks that simar has too much of workload :D
[22:33] <fabrice_sp> ++
[22:33] <simar> geser: The same I'm working on..
[22:34] <fabrice_sp> the filename should appear in the compilation log
[22:34] <simar> geser: probably you could suggest something :(
[22:34] <fabrice_sp> simar, ^
[22:34] <geser> simar: where are you stuck?
[22:34]  * shadeslayer is going krazy due to krazy :S
[22:34] <simar> fabrice_sp:  i'm looking  at it ..
[22:34] <simar> geser: just a sec..
[22:37] <simar> g++ -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\"    -g -O2 -g -Wall -O2 -c -o graphics.o graphics.cc
[22:37] <simar> g++ -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\"    -g -O2 -g -Wall -O2 -c -o init.o init.cc
[22:37] <simar> init.cc: In function 'void save_hiscore()':
[22:37] <simar> init.cc:303: error: 'mkdir' was not declared in this scope
[22:37] <simar> init.cc: In function 'void load_config()':
[22:37] <simar> init.cc:336: error: 'mkdir' was not declared in this scope
[22:37] <simar> init.cc: In function 'void save_config()':
[22:37] <simar> These are the errors
[22:37] <simar> fabrice_sp: I think i got what you said
[22:38] <fabrice_sp> !pastebin|simar
[22:38] <fabrice_sp> but yes: the file to patch is init.cc
[22:38] <fabrice_sp> you see: it's not so complicated to find it ;-)
[22:39] <geser> more exactly src/init.cc
[22:39] <simar> fabrice_sp: geser sure i think i got it. i'm looking it..
[22:40] <geser> simar: and "sudo apt-get install manpages-dev && man 2 mkdir" to see what includes are needed for mkdir()
[22:41] <fabrice_sp> geser, how do you know the file is in src?! Some magic?
[22:41] <shadeslayer> ScottK: do we have something called just in time in kde trunk?
[22:41] <geser> fabrice_sp: I looked at the build log :) http://people.ubuntuwire.org/~lucas/ubuntu-nbs/32/open-invaders_0.3-1_lubuntu32.buildlog
[22:41] <fabrice_sp> lol
[22:41] <fabrice_sp> ok: time to go to bed! :-)
[22:41] <simar> geser: Thanks for the excellent trick. I just need these..
[22:42] <ScottK> shadeslayer: Not that I know of.
[22:42] <shadeslayer> ScottK: http://websvn.kde.org/trunk/quality/sanitizer/just-in-time.php?view=markup
[22:42] <shadeslayer> whee
[22:42] <fabrice_sp> bye all
[22:43] <shadeslayer> now i just have to figure out how to use it
[22:43] <porthose> me waves
[22:44] <simar> fabrice_sp: Thanks for you help. :>>
[22:45] <simar> geser: In man 2 mkdir . does it refer to second page of mkdir man page?
[22:48] <geser> simar: no, to the 2nd section in the man page categories (see man man)
[22:48] <geser> 2   System calls (functions provided by the kernel)
[22:49] <simar> geser: ok thanks you very much
[22:49] <geser> simar: there is also "man 1 mkdir" for the mkdir command one uses from the shell
[22:50] <simar> geser: I added the header files. Now i think I need to rebuild the package by debuild -S and then in debian directory dch -i to update the change log ..
[22:50] <shadeslayer> ScottK: digikam still fails
[22:50] <ScottK> Oh.  OK.
[22:50] <shadeslayer> same error as build log online
[22:51] <geser> simar: first update the changelog (dch -i) and the build the source package (debuild -S)
[22:51] <shadeslayer> but i know a fix.. just need to get the commands right..
[22:51] <simar> geser: ya i did update the change log.
[22:56] <simar> geser:
[22:56] <simar> I get these errors with debuild -S
[22:56] <simar> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or directory
[22:56] <simar> debian/rules:4: /usr/share/cdbs/1/rules/simple-patchsys.mk: No such file or directory
[22:57] <simar> Next time i will use pastebin
[22:57] <geser> sudo apt-get install cdbs
[22:58] <simar> geser: I hope it doesn't matter that i'm installingcdbs it in lucid, while building for maveric in pbuilder.
[22:59] <geser> no, as you only build the source package
[23:07] <simar> geser: debsign: gpg error occurred!  Aborting....
[23:07] <simar> geser: because of pub   2048R/FB16B2EF 2010-01-24
[23:07] <simar> uid                  Gursimran singh (Tutorial key) <simar.i3r@gmail.com>
[23:08] <simar> "Tutorial key" how to remove it. dch -i has created Gursimran singh only??
[23:09] <geser> you can ignore that error for now, package signing is only important when you want to upload the package somewhere (e.g. PPA)
[23:09] <geser> for test building in a pbuilder, it doesn't matter if the source package is signed or not
[23:11] <simar> k :)
[23:11] <geser> simar: IIRC you can edit the comment of a uid once you created it. either use "(Tutorial key)" also in the changelog or create a uid without that comment (you can revoke the uid with the comment if you don't need it anymore)
[23:11] <geser> s/can/can not/
[23:12] <simar> geser: I was trying it with gpg -edit-key
[23:16] <shadeslayer> btw how do i check in a rules file if a file exsists or not and copy it when it exsists?
[23:19] <geser> man [
[23:19] <geser> [ -e src ] && cp src dst
[23:20] <shadeslayer> geser: thanks :D
[23:20] <Quintasan> ari-tczew: pong
[23:20] <carstenh> I was not sure about set -e and foo && bar thus i used "if"
[23:22]  * shadeslayer goes back to Qt till digikam builds
[23:22] <carstenh> foo && bar works with set -e so just ignore me
[23:23] <geser> shadeslayer: you might need "[ ! -e src ] || cp src dst" so the return value from it is always 0 and make doesn't catch it as error
[23:23] <Quintasan> ari-tczew: couldn't answer earlier, someone tore my internet cable
[23:24] <shadeslayer> geser: uh,ok,ill let it build and see what error it reports,so that i know in the future :P
[23:24] <doctormo> Should I be uses cdbs to do patching?
[23:25] <ari-tczew> Quintasan: have you got time for sponsoring kadu merge?
[23:26] <Quintasan> ari-tczew: sure, give me the diffs
[23:26] <carstenh> doctormo: depends on whom you ask. cdbs was more popular before dh was invented.
[23:26] <ari-tczew> Quintasan: bug 602465
[23:26] <simar> geser: !!!! thank you very much !!!
[23:26] <geser> doctormo: it's up to you, but many like dh more than cdbs (http://people.debian.org/~cjwatson/dhstats.png)
[23:27] <doctormo> carstenh: If I'm using dh, does the rules file need to be updated to include anything? or will anything in debian/patches/*.patch be applied during the build?
[23:27] <simar> I made it. My first FIX of FTBFS ..
[23:27] <Quintasan> simar: gratz \o/
[23:27] <doctormo> geser: I'm writing documentation, so it's bes to document the right thing.
[23:28] <simar> Quintasan: thanks . All Credit to geser
[23:28] <shadeslayer> simar: go go!
[23:28] <simar> shadeslayer: ya, thanks
[23:28] <carstenh> doctormo: depends ... when you use dpkg source format 3.0 (quilt), patches are applied before debian/rules is run
[23:28] <Quintasan> ari-tczew: only this? did you test build?
[23:28] <simar> shadeslayer: now no stopping back !!!
[23:28] <shadeslayer> simar: good :D
[23:28] <ari-tczew> Quintasan: yea, built fine
[23:29] <Quintasan> ari-tczew: well, let me try it too
[23:29] <carstenh> doctormo: otherwise you would need to add an option to dh in debian/rules and maintain debian/patches/series
[23:29] <doctormo> If I've created the debian dir using dh_make and then used edit-patch to make some patches, what should I do to make sure patches are applied? or is nothing needed?
[23:30] <simar> shadeslayer: Do i need to upload the change now, may be by sponsership?
[23:31] <shadeslayer> geser: ^^
[23:31] <shadeslayer> !debdiff | simar
[23:32] <carstenh> doctormo: there are many ways (possibly too much) to create debian packages and maintain patches
[23:32] <shadeslayer> simar: so create a debdiff and pester MOTU's :P
[23:32] <shadeslayer> or file a bug..
[23:33] <simar> shadeslayer: yo sir !
[23:33] <simar> shadeslayer: :)
[23:33] <shadeslayer> :)
[23:34] <doctormo> carstenh: pick the best method, the most simple and I will document that one.
[23:34] <carstenh> doctormo: I just installed cdbs and still have no edit-patch command
[23:34] <Quintasan> ari-tczew: I'm not so sure about Standards 3.9.0 but rest seems fine
[23:34] <doctormo> ubuntu-dev-tools I believe
[23:34] <carstenh> so I have no idea about which tool we are just talking
[23:34] <Quintasan> no errors in build so far
[23:34] <Quintasan> shadeslayer: ^^
[23:35] <shadeslayer> Quintasan: of qt-kde?
[23:35] <ari-tczew> Quintasan: Standards-Version was changed in Debian, not by me, so don't care about it.
[23:35] <Quintasan> ari-tczew: debian has that? hmm
[23:36] <ari-tczew> Quintasan: do you see this change in my debdiff?
[23:36] <carstenh> doctormo: ok, found that manpage less thing
[23:36] <Quintasan> ari-tczew: oh, I applied to the wrong source
[23:36] <shadeslayer> geser: /bin/sh: [-e: not found << hehe
[23:36] <Quintasan> man, those ds1-3 sure are confusing
[23:37] <carstenh> doctormo: do you change an existing package or are you creating a new one?
[23:39] <doctormo> carstenh: In this documentation, we're making a new one.
[23:41] <carstenh> doctormo: ok, so you are following a documented example. you only get confused if you do something different from the way it is described because (as already mentioned) there are too many ways to maintain pachtes
[23:41] <carstenh> doctormo: which url do you follow?
[23:41] <Quintasan> ari-tczew: I get FTBFS with debian's source
[23:42] <ari-tczew> Quintasan: yes... but merge fixes FTBFS on maverick (read debian/changelog)
[23:43] <simar> shadeslayer: Please guide me further.
[23:43] <simar> simar@simar-laptop:~/open-invaders-0.3$ update-maintainer
[23:43] <simar> Maintainer email is set to an @ubuntu.com address - doing nothing.
[23:43] <simar> appears
[23:43] <Quintasan> ari-tczew: it fails in debian/rules
[23:43] <Quintasan> ari-tczew: not within depends
[23:43] <shadeslayer> simar: whats there to guide? jump from one FTBFS to another... :D
[23:43] <shadeslayer> and keep fixing
[23:43] <ari-tczew> Quintasan: lol, I don't understand.
[23:44] <ari-tczew> I can ask other sponsor and he will ack patch.
[23:44] <ari-tczew> because debdiff is fine
[23:44] <simar> shadeslayer: update-maintainer tool not setting the maintainers in debian/control
[23:45] <Quintasan> simar: change it by hand then :P
[23:45] <shadeslayer> :D
[23:45] <doctormo> carstenh: I'm not following an example, I'm _creating_ documentation. Although I am basing it on https://wiki.ubuntu.com/PackagingGuide/Complete I'm just not being very faithful because it's rather verbose.
[23:45] <shadeslayer> yep
[23:45] <simar> Quintasan: k
[23:46] <shadeslayer> simar: look at other packages and guess what it should be
[23:46] <shadeslayer> then we will tell you if its right or wrong
[23:46] <ari-tczew> Quintasan: so what's the decission?
[23:47] <carstenh> doctormo: I'll be back in 5 minutes and have a look at it then
[23:47] <simar> shadeslayer: I think the email of maintainer is @ubuntu.com so he's not of debian ..
[23:47] <Quintasan> ari-tczew: well, I can't get it to build netiher with our version or debian's version
[23:48] <Quintasan> maybe it's cause of my buggy pbuilder it because it is late and I'm doing it wrong
[23:48] <doctormo> I'mm put it to one side until someone can explain it in any reasonable none daft way.
[23:48] <simar> shadeslayer: example is in the patching guide though.. but think I should not change anything here ..
[23:48] <ari-tczew> Quintasan: have you got updated pbuilder?
[23:48] <shadeslayer> simar: can you pastebin the control file?
[23:48] <Quintasan> ari-tczew: of course
[23:49] <shadeslayer> !pastebin | simar
[23:49] <simar> shadeslayer: k
[23:49] <Quintasan> ari-tczew: I have a hook that updates the pbuilder each time a build starts
[23:50] <simar> shadeslayer: http://paste.ubuntu.com/464264/ . Its easy. :)
[23:50] <shadeslayer> simar: Maintainer: Siegfried-Angel Gevatter Pujals (RainCT) <rainct@ubuntu.com>
[23:51] <Quintasan> ari-tczew: besides, why are you debdiffing debian to ubuntu?
[23:51] <shadeslayer> that has to be changed i think
[23:51] <ari-tczew> shadeslayer: if maintainer has got @ubuntu.com domain, field won't be changed.
[23:51] <shadeslayer> geser: any suggestions ( imo change it to motu maitainers? )
[23:51] <shadeslayer> ari-tczew: ah.. ok
[23:51] <shadeslayer> simar: leave it as such
[23:51] <ari-tczew> and update-maintainer won't update
[23:52] <simar> shadeslayer: I guessed right.
[23:52] <ari-tczew> Quintasan: because this is very easy to look patch
[23:52] <shadeslayer> simar: yes
[23:52] <ari-tczew> every sponsor is sponsoring it for me.
[23:52] <shadeslayer> anyone know who the bughugger dev is ?
[23:52] <ari-tczew> including respect words, but please get more expierence with sponsoring
[23:53] <Quintasan> ari-tczew: well, I'm doing mergeres for kde packages and we do it in a different way
[23:55] <carstenh> doctormo: first of all I don't think that dh_make is good for learning packaging because it creates too much files one only seldom needs and might just confuse people learning packaging
[23:55] <carstenh> but that's debatable
[23:55] <doctormo> carstenh: that isn't my concern, my concern is ease of use and what is typically being used. dh_make is it.
[23:55] <ari-tczew> Quintasan: ok, if can't process it, please don't unsubscribe sponsors and other person will take a look. thanks
[23:55] <doctormo> Extra files are dealable and have been dealt with the in docs as deletable.
[23:56] <shadeslayer> geser: get ready to sponsor digikam
[23:57] <shadeslayer> well.. not for another 20 more mins atleast
[23:57] <shadeslayer> Quintasan: do we install .mo files?
[23:58] <shadeslayer> or are they stripped to translations>
[23:58] <carstenh> doctormo: yes, I know. reading the url takes a lot longer than writing one sentence :)
[23:58] <Quintasan> shadeslayer: I think they are stripped, but I'm not sure about digikam
[23:58] <shadeslayer> ScottK: ^^