[00:08] <ajmitch> cpscotti: you're still depending on things like libv6-dev & gcc - surely they aren't required to run the package, but only to build it?
[00:09] <cpscotti> the harpia package is a c source code generator
[00:09] <cpscotti> ajmitch: and it builds it on runtime
[00:09] <ajmitch> how evil :)
[00:09] <cpscotti> yep
[00:10] <cpscotti> you go on connecting blocks (like in simulink... in a flowchart manner) and it generates the code.. compiles.. and runs
[00:10] <cpscotti> =]
[00:10] <ajmitch> interesting
[00:11] <cpscotti> u can use your webcam as an input (or any pic, any video file) and apply many computer Vision/image processing algorithms on it and see the results in real-time
[01:20] <binarymutant> does Empathy use Mono? Just curious not trolling fyi
[01:21] <Ampelbein> binarymutant: no, it does not.
[01:21] <binarymutant> ty Amaranth :)
[01:22] <Ampelbein> Ampelbein. it's Ampelbein. ;-)
[01:23] <binarymutant> ah yes sorry
[01:23] <binarymutant> the tabs always get me :(
[01:23] <Ampelbein> i know that problem.
[01:23] <Ampelbein> binarymutant: no need to be sorry, btw. I was joking.
[03:08]  * masterkernel is away: Away
[03:08] <dcraven> So I'm making a new package for Karmic, and I need to include a patch (I'm using quilt). I assume I need to include the change that the patch makes in the changelog file. So I just mention it like any other change or does it have to refer to the patch somehow?
[03:09] <nhandler> masterkernel: Could you please disable that away script?
[03:09] <nhandler> dcraven: Just mention it like any other change. You should also include a patch header
[03:11] <dcraven> Patch header eh?
[03:11]  * dcraven goes to look that up.
[03:11] <dcraven> Thanks for the advice nhandler.
[03:11] <vorian> patch headers for the win
[03:12] <nhandler> dcraven: It is just a comment at the top of the patch file explaining what the patch does, linking to the upstream bug (You did send the patch upstream, right ;) ), etc.
[03:13] <dcraven> Oh. I can just edit the diff stick a comment up there. Good idea.
[03:15] <vorian> dcraven: https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines
[03:16] <dcraven> Thanks guys.
[03:34] <dcraven> Ugh.. lintian want's me to make a manpage for this bloody package :/
[03:36] <RAOF> Yup.  It'll do that.
[03:36] <persia> dcraven, help2man can help with that, if it has --help.
[03:38] <dcraven> persia: Nice tip. I'll cross my fingers that this has --help. :)
[03:39] <persia> THe page would still benefit from manual editing, but it gives a decent starting framework.
[03:39] <dcraven> persia: Cool.
[03:49] <dcraven> So does the manpage need to be added with a patch or can I just stick it in the package? And yes I'll send it upstream :)
[03:50] <nhandler> dcraven: Just put it in the debian directory, no patch needed
[03:50] <persia> Well, that's kinda a patch, but it's certainly easier that way.
[03:51] <dcraven> In the debian dir. Good call.
[03:52] <nhandler> persia: True, but he doesn't need to use something like quilt to add it
[03:53] <persia> Right.
[04:32] <nellery> is pull-debian-source failing for anyone else with the latest version of ubuntu-dev-tools (0.75)?
[04:33] <ajmitch> nellery: failing on what way?
[04:33] <ajmitch> lots of perl errors?
[04:34] <nellery> ajmitch: http://paste.ubuntu.com/212377/
[04:35] <nhandler> nellery: Let me check on that
[04:35] <ajmitch> nellery: same as what I get, but I suspect that's a debian problem
[04:35] <ajmitch> http://qa.debian.org/madison.php?package=php5&a=&b=&c=&s= is showing postgres errors
[04:35] <nellery> I know there was a new version released today
[04:35] <nellery> ah
[04:37]  * ajmitch is getting the same errors with 0.74
[04:46] <coolbhavi> hello team if nobody has any objections I ll prepare diffs for https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/391165
[04:47] <geofft> wait, isn't that bug fixed?
[04:51] <ScottK> coolbhavi: Also dpkg is in Main, so #ubuntu-devel is a better place to discuss.
[04:56] <coolbhavi> geofft, I mean packages affected by that bug
[05:01] <geofft> oh, okay
[05:40] <RoAkSoAx> Hey guys, what can ccause this kind of build errors: Makefile:262: .deps/main.Po: No such file or directory
[05:40] <RoAkSoAx> the ones related to .deps ?
[07:02] <dholbach> good morning
[07:32] <\sh> moins
[08:20] <siretart`> morning motu!
[08:23] <\sh> hey siretart`
[08:23] <ajmitch> hey siretart`, \sh
[08:25] <siretart`> hey \sh, hi ajmitch!
[08:25] <siretart`> what do you think about bug #374900 ?
[08:25] <\sh> siretart`: I'm in NBG tomorrow...I don't know if I'm staying overnight ... when it's possible we could catch up for a beer :)
[08:26] <siretart`> \sh: wow, sounds great! :-)
[08:26] <siretart`> \sh: do you still have my mobile number?
[08:30] <\sh> siretart`: yepp :)
[08:31] <\sh> siretart`: I'll call you :)
[08:32] <StevenK> RAOF: Around?
[08:46] <\sh> siretart`: your bug doesn't sound good...
[08:47] <siretart`> strictly speaking, the package seems pretty unredistributable to me
[08:48] <siretart`> but before proposing to pull out that package, I wanted to hear opinions
[08:49] <\sh> siretart`: reading the sentence: ISO/IEC gives
[08:49] <\sh> users of the MPEG-2 NBC/MPEG-4 Audio standards free license to this
[08:49] <\sh> software module or modifications thereof for use in hardware or
[08:49] <\sh> software products claiming conformance to the MPEG-2 NBC/ MPEG-4 Audio
[08:49] <\sh> standards.
[08:50] <persia> Does that mean we just have to claim conformance somewhere to suddenly have a license?
[08:51] <siretart`> wtf is a 'free license'?
[08:51] <soren> Strictly speaking, it doesn't say "a free license", but just "free license".
[08:51] <persia> I think it's a verb.
[08:52] <soren> Which one?
[08:52] <soren> And how so? :)
[08:53] <siretart`> the package is in pretty miserable shape anyway. it claims GPL, whereas there are several licenses in the package, including LGPL and MPL.
[08:59] <RAOF> StevenK: Yeah, am now.
[09:40] <dstansby> Hi guys, just wondering if anyone could help me with a small problem I'm having.
[09:40] <dstansby> I'm trying to build a package using dkpg -S, and I'm getting the following error message:
[09:40] <dstansby> 'You must specify a valid ANT_HOME directory!'
[09:41] <persia> dstansby, Building Java source packages usually requires all the build-depends to be installed.
[09:41] <dstansby> Thanks, I'll isntall all the build deps and see what happens then
[09:42] <dstansby> Is there a command that I can use to automatically isntall all of the build-deps of a package?
[09:43] <fabrice_sp> dstansby, sudo apt-get build-dep <package>
[09:43] <dstansby> fabrice_sp: Thanks :)
[09:43] <fabrice_sp> ;-)
[10:06] <dupondje> 381 builds on i386 for PPA :) lol its crazy
[10:14] <fabrice_sp> geser, do you plan to work on the merge of magicor?
[10:16] <fabrice_sp> fyi, I've sent the differences to Debian
[10:18] <geser> fabrice_sp: the magicor changes look pretty ubuntu specific to me because of our changes to cdbs
[10:19] <geser> fabrice_sp: it looks like al-maisan started to work on a merge as he has a merged package in his PPA
[10:20] <fabrice_sp> geser, ok. I'll ping him if Debian accept the changes (the change is not harmful in Debian)
[10:20] <fabrice_sp> and look after another merge :-)
[10:21] <dholbach> directhex: are you up for repeating your packaging sesssion at UDW?
[10:21] <dholbach> maybe with the Debian gang again? :)
[10:21] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep
[10:25] <ajmitch> oh what a shame, most of the slots are filled up already on there :)
[11:27] <directhex> dholbach, yeah, probably
[11:27] <directhex> also, Laney for CC!
[11:28] <Laney> for what now
[11:28] <dholbach> directhex: great - could you get in touch with the people with whom you'd like to hold the session? I'm trying to round up speakers :)
[11:28]  * Laney wills Banshee to stay alive long enough to get tunes onto his phone
[11:30] <directhex> Laney, http://daniel.holba.ch/blog/?p=443 !
[11:30] <Laney> hah
[11:30] <Laney> I think not
[11:31] <Laney> jpds for CC!
[11:32] <directhex> how about nyu, then?
[11:34] <jpds> Laney: Haha, that would be interesting.
[12:26] <lamothe> I just asked a user to enable apport for Jaunty so he can send me the details for a segfault that I can't replicate.  Have I done the wrong thing?  I was doing some reading which suggested that enabling apport for a stable release is not really a good thing to do.
[12:27] <lamothe> I assume that it's just the submission to LP that's the issue.
[12:28] <ScottK> lamothe: No.  It's a fine thing to do for trouble shooting.  We just don't want piles of duplicates in LP.  Even submission of a small number of bugs is fine particularly if you are going to triage them.
[12:28] <lamothe> dholbach: Thanks for uploading Me TV to Karmic.
[12:29] <lamothe> ScottK: For sure I will be dealing with it.  Thanks for the response.
[12:30] <dholbach> lamothe: no worries
[12:36] <ogra> siretart, ping
[13:36] <cypherbios> Hey guys. There is a bug report on Launchpad regarding an issue with the package "aptoncd" (LP 272509). This bug was already been fixed upstream, but was never updated on the Ubuntu package (I am one of the upstream guys).
[13:37] <cypherbios> Would be great if some MOTU packaged it for Karmic, and hopefully for intrepid too
[13:40] <cypherbios> This bug is considered critical and lots of users are complaining about it
[13:40] <cypherbios> If someone can lend me a hand, I will be around
[13:41] <fabrice_sp> cypherbios, you can submit yourself submit an update to the package
[13:42] <Laney> what happened to Rafael?
[13:43] <Laney> wait, that's you!
[13:43] <Laney> why is it so dead in Debian?
[14:04] <cypherbios> fabrice_sp: I would like someone more experienced and skilled to do that instead of me
[14:05] <cypherbios> fabrice_sp: there is a lot of packaging rules that have been updated since the last package I made and I haven't been able to keep up with
[14:05] <Laney> cypherbios: why didn't you orphan it?
[14:07] <cypherbios> Laney: because I have been almost dead (virtually, for personal reasons) for the last few months
[14:07] <Laney> ok
[14:07] <Laney> well if you don't intend to maintain it any more then that's what you should do
[14:07] <cypherbios> Laney: could you point me of how to do that?
[14:07] <Laney> reportbug -B debian wnpp
[14:07] <Laney> follow the screens
[14:09] <cypherbios> Laney: thank you. I will do that
[14:15] <fabrice_sp> cypherbios, I don't see any new release. Is it just a patch to apply to the package?
[14:16] <fabrice_sp> I'm looking at https://sourceforge.net/projects/aptoncd/files/
[14:16] <cypherbios> fabrice_sp: the upstream project is hosted at launchpad and there is no public release besides the direct packaging from the bzr repo
[14:16] <fabrice_sp> oh
[14:16] <fabrice_sp> ok
[14:16] <cypherbios> fabrice_sp: here it is http://lauchpad.net/aptoncd
[14:18] <cypherbios> fabrice_sp: there is a lot of web presence that must be changed regarding this project (remove the sf.net project page, redirect to launchpad, etc...)
[14:18] <cypherbios> fabrice_sp: I gotta go. If you are to do something about the package and need anything, please just let me know
[14:19] <fabrice_sp> cypherbios, ok: I'll have a look
[14:19] <cypherbios> thank you. I really appreciate that
[14:53] <alkisg> I heard something here the other day, and I was wondering... if I put (LP: #396567) to a line in my changelog, will publishing the .deb to my ppa automatically close the bug in launchpad?
[14:55] <persia> alkisg, It isn't supposed to do that, and I think it doesn't anymore, although it once did.
[14:55] <alkisg> Thank you persia :)
[14:56] <persia> You might try it, but do so with a bug you know you're fixing, and watching, and if it does, unclose it until the fix can go from your PPA into the repo.
[14:56] <alkisg> Ah, the PPA is the official repo for this, so I don't really mind if it closes it!
[14:57] <gaspa> who should I bother to be added as a reviewer in revu?
[14:58] <persia> alkisg, If It's a bug against Ubuntu, I care if it closes it, because then the bug status of the Ubuntu task is incorrect, and nobody is going to put effort into pushing the fix into Ubuntu.
[14:59] <ScottK> Bug 396567
[14:59] <persia> gaspa, Me.
[14:59] <alkisg> persia: yeah, I got it; but it's for an app of my own, hosted only on my ppa, so it's not a problem either way...
[14:59] <persia> alkisg, So, there's no Ubuntu task on the bug?
[15:00] <gaspa> persia: cool, can you please add me? :P
[15:00] <persia> gaspa, Yes.
[15:00] <gaspa> :)
[15:00] <alkisg> persia: no; it's just a bug against my scripts, e.g.: https://bugs.launchpad.net/sch-scripts/+bug/396567
[15:00] <gaspa> bothered.
[15:01] <persia> alkisg, I'm not sure that would close then.  I don't think there is any upload-closes-bug for anything other than an Ubuntu task, although you could ask in #launchpad
[15:01] <persia> gaspa, done
[15:01] <gaspa> thanks a lot, persia
[15:02] <alkisg> persia: ok, I just uploaded the bug-closing version, I'll just watch it for some time to see if it automatically closes... if not, I'll close it myself, np... Thanks!
[15:20] <\sh> wow...google chrome os
[15:21] <persia> Just another thin client, no?
[15:21] <\sh> should run on arm and x86...linux kernel as base and a new windowing system
[15:22] <\sh> applications should run on this basement as web apps
[15:22] <\sh> no android stuff as they say
[15:23] <persia> I wonder if it's the same sort of stripped linux that was Android, or if it's full linux, with some directfb/chrome fast-loading interface overlay.  I suppose we'll see in time.
[15:24] <\sh> first appliances should hit the market in the second half of 2010 ... if it's true what heise wrote
[16:09] <siretart> ogra: pong?
[16:10] <ogra> siretart, does the ubuntu-burning team plan to update the cdrecord packages in the ppa for newer releases than intrepid ?
[16:11] <ogra> there is a heated discussion (including joerg) going on on the ubuntu-users ML
[16:11] <siretart> ogra: I'm on the leave, I'll checkout ubuntu-users
[16:11] <azeem> oh my
[16:11] <siretart> ogra: if you find someone to do the upload, sure.
[16:11] <ogra> i think there would be some interest of some people to have the upstream version packaged
[16:12]  * ogra doesnt want to get his hands dirty or be anyhow connected to joerg, else i would :)
[16:12] <siretart> mh, that'd be too late for me
[16:12] <ogra> ... just to have silence again on the ML
[16:13] <siretart> ogra: I'm on the leave, I'll query you tonight or tomorrow and give you a status update on the matter, ok?
[16:13] <ogra> take your time, not urgent to me ... just wanted to know if there are any plans
[16:13] <ogra> or if it was completely dead
[16:14] <siretart> my status: blocked on joerg
[16:14] <siretart> anyway, cu later!
[16:21] <ogra> siretart, thanks
[16:36] <sn9> debfx: are you gonna put vbox3 in jaunty, too?
[16:41] <debfx> sn9: I can try to get it into jaunty-backports
[16:42] <sn9> debfx: it's not even in your ppa
[16:44] <debfx> sn9: usually I'm waiting until it's uploaded to karmic
[16:45] <therm> hello everbody
[16:46] <sn9> why?
[16:48] <therm> has anyone a tip how to get my package into my pbuilder-chroot?
[16:48] <debfx> sn9: as I'm not a motu, Daniel reviews the package and sometime does additional changes
[16:48] <sn9> ah
[16:49] <sn9> you don't trust yourself with your own ppa; understandable
[16:51] <debfx> :)
[16:52] <debfx> mainly it saves me from uploaded the packages twice
[16:53] <sn9> also understandable
[16:55] <debfx> therm: your package isn't in a repository?
[16:56] <therm> debfx: No it is on Revu, and I was asked to test if it builds with pbuilder
[16:59] <debfx> therm: have a look at https://wiki.ubuntu.com/PbuilderHowto
[16:59] <sn9> i thought pbuilder was used for the ppa's
[17:00] <debfx> basically first you need to create the pbuilder chroot: sudo pbuilder create --distribution karmic --override-config
[17:01] <debfx> and then build the package with: sudo pbuilder --build --distribution karmic x.dsc
[17:01] <therm> debfx: ahh ok
[17:04] <therm> debfx: thanks
[17:32] <RoAkSoAx> Hey guys, I'm packaging an APP, and when debuilding it, it shows me this: Makefile:262: .deps/main.Po: No such file or directory
[17:32] <RoAkSoAx> make[2]: *** No rule to make target `.deps/main.Po'.  Stop.
[17:33] <RoAkSoAx> When compiling it, that warning is not showed since all the files under .deps/ are created
[17:33] <RoAkSoAx> but they are not when packaging it, anyone know what could be wrong?
[17:57] <therm> debfx: pbuilder is now moaning about that the depending packages are not installed...how to install them?
[17:57] <therm> debfx: something like
[17:57] <therm> debfx: pbuilder-satisfydepends-dummy depends on debhelper (>= 5); however:  Package debhelper is not installed.
[17:59] <debfx> therm: it should automatically install the required packages after printing those messages
[18:02] <therm> debfx: The following packages have unmet dependencies:
[18:02] <therm>   pbuilder-satisfydepends-dummy: Depends: libswt-gtk-3.4-java which is a virtual package.
[18:02] <therm> The following actions will resolve these dependencies:Remove the following packages:pbuilder-satisfydepends-dummy
[18:03] <therm> debfx: and later on Current status: 0 broken [-1].
[18:03] <therm> Aptitude couldn't satisfy the build dependencies
[18:03] <therm> E: pbuilder-satisfydepends failed.
[18:03] <therm> debfx: any idea?
[18:04] <therm> debfx: may it has something to do that this is in universe
[18:04] <therm> '?
[18:05] <sn9> change your depends
[18:05] <debfx> therm: not really sure, there seems to be a package conflict, can you post the whole output somewhere (pastebin ...)
[18:07] <therm> debfx: http://pastebin.com/d4eb2751a
[18:09] <therm>  debfx: added an othermirror with karmic universe and now it loads some packages
[18:09] <therm> debfx: maybe thats it
[18:21] <therm> debfx: yeah that was it, it builds fine now
[18:22] <debfx> great :)
[18:23] <toabctl> net
[19:08] <stas> hi guys, I got a problem, I'm trying to rebuild a package and I succeeded using dpkg-buildpackage
[19:08] <stas> -sa
[19:09] <stas> but when uploading to my ppa
[19:09] <stas> it got refused cause I didn't use debuild -S
[19:09] <stas> I'm trying to follow th docs on rebuilding the same package with debuild -S
[19:09] <geser> which error message do you get emailed?
[19:10] <stas> Upload rejected because it contains binary packages. Ensure you are using `debuild -S`, or an equivalent command, to generate only the source package before re-uploading. See https://help.launchpad.net/Packaging/PPA for more information.
[19:10] <stas> geser: a
[19:10] <stas> K
[19:10] <stas> Iam I doing something wrong?
[19:10]  * stas sorry for typos
[19:11] <geser> you seem to be trying to upload both source and binary
[19:11] <geser> build with debuild -S -sa or dpkg-buildpackage -S -sa to build only a source package and dput the _source.changes file
[19:12] <stas> ok, let me try
[19:12] <geser> if you already have the .orig.tar.gz uploaded once you can skip the -sa switch
[19:29] <therm> someone out there who knows in wich package "org.osgi.core-1.2.0.jar" is in?
[19:29] <therm> could find this
[19:29] <therm> not
[19:30] <Pici> therm: Have you looked on packages.ubuntu.com? or with apt-file?
[19:31] <therm> Pici: I looked with apt-file but could not find this, I hoped that someone knows this, I may has a different name and so I dont find it
[19:31] <therm> it
[19:32] <therm> it is for h2(java database)
[19:42] <stas> geser: thank you, it seems to work
[19:43] <stas> last question, I'm rebuilding packages for nexenta where I need to upload also the debs
[19:43] <stas> in my ppa the build job is done by soyuz?
[19:43] <stas> so I don't have to upload the builds?
[19:44] <azeem> stas: right
[19:44] <stas> I see. smart move :)
[19:44] <stas> thank you guys
[19:44] <geser> stas: the buildd takes your source upload, builds it and puts the debs in your PPA
[19:45] <stas> :)
[20:25] <RoAkSoAx> heya guys, do you now by any chance which packages provides this : GTK+ 2.10.0 or later, GNOME Desktop 2.16.0 or later, GStreamer 0.10.0 or later  ?
[20:26] <geser> for build dependencies?
[20:26] <slytherin> RoAkSoAx: libgtk*-dev, libgnome*-dev, libgstreamer*-dev.
[20:26] <RoAkSoAx> geser, for Depends
[20:27] <sn9> there should be a script to autodetect dependencies
[20:27] <RoAkSoAx> slytherin, thanks, though I need for Depends rather than Build-Depends :)
[20:28] <slytherin> RoAkSoAx: you don't need to add dependencies manually, use ${shlibs:Depends} (please check variable spelling for correctness)
[20:28] <RoAkSoAx> slytherin, ok then :)
[20:28] <RoAkSoAx> thans
[20:28] <geser> they should be detected by dh_shlibdeps, you usually don't put them yourself in Depends
[20:28] <RoAkSoAx> thanks*
[20:28] <RoAkSoAx> ok thanks geser :)
[20:33] <RoAkSoAx> One more question. When the tarball comes in .tar.bz, should I unpack it, create a .tar.gz and on debian/rules add get-orig-source right?
[20:35] <therm> I do have here a built.xml wich is download jar-file from an webserver, what is recommendet to do with this?
[20:36] <therm> arghh my english^^
[20:39] <geser> check if the jar it needs are already packaged, package them if necessary and use them during the build (the buildd don't have net access anyways)
[20:42] <therm> geser: there are 4 libs wich are downloaded, 3 of them are in repos, 1=org.osgi.core-1.2.0.jar I didnt know. But how to disable this if the compile statement requires the donwload statement?
[20:46] <slytherin> RoAkSoAx: check manpage of uscan. You will probably simply need to add 'uscan --verbose --repack' to get-orig-source
[20:47] <slytherin> therm: I believe it (osgi) is one of the eclipse components. You can patch build.xml such that compile does not have dependency on download. But I am not sure if your build will work in that case.
[20:49] <therm> slytherin: Ok, will do this, wasnt sure if this is allright. Osgi has something to do with eclipse...I wanted to probe if eclipse-common-nls has it
[20:49] <therm> slytherin: but then the download section came
[20:50] <RoAkSoAx> ok thanks slytherin  :)
[21:00] <directhex> slytherin, --repack doesn't produce deterministic gzips
[21:00] <slytherin> directhex: what do you mean?
[21:01] <directhex> slytherin, run it three times, get three different md5sums on orig
[21:01] <directhex> slytherin, --repack is why we have fakesyncs
[21:03] <slytherin> oh, that. But isn't that because the timestamp of gz file gets changed?
[21:04] <debfx> how do you call quilt when using override_dh_... style rules?
[21:04] <debfx> I know about dh --with-quilt but don't want to use it due to backportability
[21:33] <Laney> we *could* fix --repack
[21:49] <Ampelbein> nellery: hi there. apparently you uploaded isight-firmware-tools just when I commented on bug 393049. ;-) I think for such a change a ubuntu-diff is not necessary, in particular when the current debian package has a newer version and fixes the issue.
[21:49] <Ampelbein> nellery: see http://packages.qa.debian.org/i/isight-firmware-tools.html, though it's not noted in the changelog,it's still fixed.
[21:49] <nellery> Ampelbein: just saw that
[21:50] <nellery> the maintainer didn't document it in the changelog, and I didn't see a bug filed for it
[21:50] <nellery> I missed that
[21:50] <Ampelbein> nellery: yeah, i was thinking about forwarding the change to debian and decided it would be better to first check the new package.
[21:51] <nellery> either way I think it's worth requesting a sync for it
[21:51] <Ampelbein> nellery: that's a good example for why we need every single change to be documented.
[21:51] <nellery> Ampelbein: yep.. I saw another that that maintainer didn't document, but there was a bug filed for it.
[21:51] <Ampelbein> nellery: do you want to request the sync or should I do it?
[21:52] <nellery> Ampelbein: I can take care of it
[21:52] <Ampelbein> nellery: ok, thanks.
[22:16] <RoAkSoAx> Hey guys where can I find which variables (info about them) handles directories in debian/rules: such as CURDIR, DEB_SOURCE_PACKAGE, etc
[22:33] <chrisccoulson> RoAkSoAx - the debian policy manual can be useful. also check out http://cdbs-doc.duckcorp.org/en/cdbs-doc.xhtml
[22:34] <chrisccoulson> CURDIR is exported by make though. it's specified in the manual for GNU make: http://www.gnu.org/software/make/manual/make.html
[22:47] <evanrmurphy> https://wiki.ubuntu.com/PackagingGuide/Complete#CDBS%20with%20Simple%20Patchsys%20(Example%20Package:%20pmount) explains how to write a patch for package pmount with cdbs-edit-patch. But how do you apply the patch after it's written, just with "debian/rules patch"?
[22:55] <RoAkSoAx> evanrmurphy, if you have added the includes, they it will be patched automatically
[22:56] <evanrmurphy> thanks, RoAkSoAx :)
[22:57] <RoAkSoAx> :)
[23:10] <binarymutant> is elgibc replacing glibc in Karmic or the next release?
[23:11] <pochu> binarymutant: do you mean eglibc?
[23:11] <pochu> heh yeah
[23:11] <binarymutant> ah yes :)
[23:11] <pochu> I read elglibc :)
[23:11] <pochu> no decission has been made TTBOMK
[23:11] <pochu> I mean
[23:11] <pochu> not in karmic for sure
[23:11] <binarymutant> k, thanks pochu :)
[23:12] <pochu> no decission has been made whether karmic+1 will switch to eglibc or will stay using glibc
[23:28] <ScottK-desktop> It might be Karmic yet depending on how much difference there is.
[23:29] <binarymutant> it's already in unstable that's why I ask
[23:29] <binarymutant> but I didn't know if glibc is synced or is maintained differently like the kernel
[23:33] <ScottK-desktop> We merge from Debian.
[23:33] <ScottK-desktop> It's not like the kernel.
[23:33] <binarymutant> ah ok