[03:29] <cpscotti> Hey everybody, could some motu review/advocate the harpia package ( http://revu.ubuntuwire.com/p/harpia ). It is a python app to generate computer-vision/image processing c code from block diagrams. It has alreade been uploaded to archive but got rejected due to some dependencies issues that were already fixed. Thanks a bunch!
[06:30] <dholbach> good morning
[06:30] <ajmitch> hi
[06:31] <dholbach> hi ajmitch
[06:32]  * ajmitch waves farewell to the laptop
[06:34]  * hyperair has just written a one-liner, crude pull-revu-source script =\
[06:37] <persia> hyperair, Um, why not just use dget?
[06:38] <dholbach> persia: maybe it does something like      pull-revu-source indiana-jones-and-the-last-crusade
[06:39] <persia> I generally like to read the comments anyway, but perhaps my URL dragging methods don't work for everyone.
[06:46] <hyperair> persia: the script uses dget. the whole point is to pass it a package and dget the dsc without needing to launch a browser
[06:50]  * kb9vqf says a few nasty things to his laptop
[09:49] <gaspa> geser: https://bugs.launchpad.net/bugs/372704 \o/
[09:54] <geser> that was fast, perhaps it's on egde tomorrow so I can adapt your other change to use it
[09:54] <gaspa> :)
[09:57] <slytherin> any docbook experts here?
[09:58] <persia> slytherin, You might try #ubuntu-doc, unless it's not Ubuntu-related.
[09:59] <slytherin> No. It is not ubuntu related.
[09:59] <persia> Not sure if they would help then, although they do tend to use docbook a lot.  They might trade for some good writeups of some of our tech :)
[10:01] <slytherin> I have very specific question about list item.
[10:01] <gaspa> slytherin: you make me remember that I completely forgot that w3m-xxx issue...
[10:03] <slytherin> :-)
[10:47] <Laney> What is the correct way to drop a binary package from a source package if the binary has an (= ${binary:Version}) depend on another -- libgnomescanui0: Depends: libgnomescan0 (= 0.4.1-0ubuntu4) but 0.6.2-0ubuntu1 is to be installed.
[10:48] <Laney> gnomescanui0 has been dropped
[10:54] <geser> what happens if you simply don't build it anymore?
[10:54] <geser> I don't see the problem currently
[10:55] <Laney> it breaks the dependency on the previously installed version (which no longer exists)
[10:55] <Laney> conflicts on the new libgnome0 could work
[10:57] <hyperair> don't both binary packages come from the same source package?
[10:57] <hyperair> if they do, won't it suffice to upload another version without the dependency?
[10:58] <Laney> they do, and that is what happened
[10:58] <Laney> but aptitude doesn't like it
[10:58] <geser> you need to transition the rdepends of libgnomescanui0 anyway, after that it should be safe to let apt remove libgnomescanui0 during dist-upgrade
[10:59] <Laney> there are no rdepends
[10:59] <hyperair> what does aptitude full-upgrade say?
[10:59] <Laney> that's what I was doing
[10:59] <geser> doesn't aptitude do a safe-upgrade by default?
[10:59] <hyperair> yeah it does
[10:59] <Laney> dunno, but I explicitly did full-upgrade
[10:59] <geser> i.e. it won't remove packages?
[10:59] <hyperair> hmm
[11:00] <hyperair> if you explicitly did, then it shouldn't be an issue
[11:00] <Laney> :(
[11:00] <hyperair> what does apt-cache policy libgnomescanui0 say?
[11:00] <Laney> apt-get does the right thing here btw
[11:00] <hyperair> eh? hmm
[11:00] <hyperair> aptitude fail =(
[11:01] <geser> doesn't have aptitude an option to explain why it choose a specific solution? (I don't use aptitude myself)
[11:01] <hyperair> 17:47:59 <Laney> What is the correct way to drop a binary package from a source package if the binary has an (= ${binary:Version}) depend on another -- libgnomescanui0: Depends: libgnomescan0 (= 0.4.1-0ubuntu4) but 0.6.2-0ubuntu1 is to be installed.
[11:02] <Laney> and the first solution it proposes is to hold back gnomescan0
[11:04] <hyperair> Laney: how about libgnomescanui0 provides libgnomescan0?
[11:04] <Laney> haha
[11:04] <Laney> horrible :(
[11:04] <hyperair> =p
[11:04] <hyperair> why was libgnomescan0 removed anyway/
[11:04] <cyberixae> How can there be a source package in the repository without any binary packages?
[11:04] <cyberixae> That seems to be the case here http://packages.ubuntu.com/search?keywords=gnome-shell&searchon=sourcenames
[11:04] <Laney> ui was removed, upstream doesn't do it any more
[11:04] <Laney> cyberixae: hasn't passed binary NEW is my guess
[11:05] <Laney> hyperair: if I run aptitude full-upgrade a second time after the rest of the upgrades are done it wants to remove it this time
[11:05]  * Laney shrugs
[11:05] <hyperair> Laney: ah. i've seen something like that before.
[11:05] <geser> cyberixae: failed to build yet (depwait for gnome-shell)
[11:06] <Laney> different proposal based on when you do it, weird
[11:06] <hyperair> more like based on what's remaining =\
[11:06] <cyberixae> I tought you'd normally fix that kind of stuff before uploading the source
[11:06] <Laney> but those two packages don't affect anything else
[11:06] <gnomefreak> do we support EeePC or better yet Eeebuntu?
[11:06] <Laney> no
[11:07] <Laney> that's a third party project afaik
[11:07] <gnomefreak> thank you so much :)
[11:07] <Laney> we are responsible for the packages that get installed though
[11:07] <geser> cyberixae: we usually try to minimize build errors but it doesn't work out in all cases
[11:07] <gnomefreak> Laney: thanks
[11:07] <Laney> it's perfectly fine for stuff to depwait
[11:08] <Laney> let computers do the boring scheduling work once you know it all fits together fine
[11:09] <hyperair> you waste buildd time =p
[11:09] <Laney> hardly
[11:09] <hyperair> hardly, but the time still exists =p
[11:10] <Laney> which time is more valuable?
[11:10] <hyperair> uh what?
[11:10] <Laney> computer time or developer time
[11:10] <hyperair> heh it depends =p
[11:10] <hyperair> but in this case i'd say developer time
[11:11] <hyperair> you could have cron or at dput it for you, though =p
[11:11] <Laney> heh
[11:12] <Laney> !
[11:15] <hyperair> oho
[12:42] <Laney> Could do with some help removing LVM snapshots created by sbuild: http://dpaste.com/64974/
[12:43] <Laney> wait
[12:43] <Laney> no, can't lvchange -an the snapshot either
[13:28] <bddebian> Heya gang
[13:50] <highvoltage> greetings db
[13:50] <highvoltage> greetings bddebian
[13:50] <bddebian> Hi highvoltage
[14:14] <maxb> Transferring an unanswered question from the #ubuntu-classroom dh7 session: How do you run conditional logic that must be run only when building the arch-indep packages - i.e. not on the non-i386 buildds?
[14:14] <maxb> I suspect the answer may involve shell conditionals testing the output of dh_listpackages, but would welcome comments on whether this is the "right way"/
[14:17] <james_w> maxb: would this be having build-arch and build-indep, or just the usual binary-arch and binary-indep split for install/creating the deb?
[14:17] <persia> maxb, You add a binary-indep rule, and do some stuff before/after calling dh binary-indep
[14:18] <maxb> What about stuff you need to do in the middle of the dh sequence? Example: python module package installs usr/lib/ into foo and foo-common. Then deletes *.so from the indep package and everything except *.so from the arch-dep package
[14:18] <persia> That sort of separation belongs in your dh_install hint files, I think.
[14:19] <persia> so it builds into debian/tmp, and foo.install vs. foo-common.install do the split.
[14:19] <persia> (and foo-common install is tossed for non-arch-all builds)
[14:22] <maxb> You can't say debian/tmp/usr/lib/!(*.so) in an .install file, though, can you?
[14:22] <alourie> dholbach_: a word in private?
[14:22] <dholbach_> alourie: sure
[14:23] <persia> maxb, Sure you can, but generally you just say "usr/lib/*.so" or some such, without the debian/tmp and let dh_install figure it out.
[14:24] <persia> Just need to use valid globs as parsed by dh_install (I forget if these are POSIX or perl)
[14:25] <maxb> Hmm... note I used a bash extended glob above - I don't think you can actually translate that into anything dh_install will process
[14:27] <persia> Well, if dh_install uses shell globs, you can force make to use bash, but that's considered a (mild) packaging bug.
[14:27] <persia> Check the dh_install code.
[14:29] <james_w> dh7 doesn't seem to be suited to doing actual arch-only builds though
[14:29] <maxb> No, it's perl globs, and they can't do what I want, which returns us to the initial question
[14:29] <persia> james_w, How do you mean "arch-only"?
[14:29] <maxb> "dpkg-buildpackage -B"
[14:29] <persia> maxb, Um, there's nothing a perl glob can't match, the syntax just gets ugly.
[14:30] <maxb> write me a perl glob which says "all files in usr/lib/ except ones matching *.so" and I'll believe that
[14:30] <maxb> They just aren't expressive enough for this
[14:30] <james_w> all files with an even number of matched and nested brackets?
[14:31] <james_w> maxb: that's possible in perl
[14:31] <persia> maxb, I'm not actually going to do that, but I'm convinced it's possible because perl was invented because awk globs were insufficient for a certain class of accounting file review activities.
[14:31] <maxb> Unless I'm totally missing something, it's not possible in a single glob expression
[14:32] <alkisg> language-pack-en depends on language-pack-en-base, and the opposite, language-pack-en-base depends on language-pack-en. How can the a user install them? I've tried dpkg -i <both of them> and it fails...(I'm trying to do something similar)
[14:32] <james_w> alkisg: give both at the same time to "dpkg -i"
[14:32] <persia> alkisg, Have you looked at the contents, control, and maintainer scripts for those packages?
[14:33] <persia> alkisg, Also, last time we talked about this, you were looking at Replaces.  What happened there?
[14:33] <alkisg> james_w: I've tried that, (for 2 similar packages of mine at least) and it failed, leaving the first of them in an unconfigured state.
[14:33] <alkisg> persia: that's what I'm looking into, and I'm stuck with this
[14:34] <persia> alkisg, Which bit is sticking?
[14:34] <alkisg> The fact that I cannot install 2 packages that depend on each-other
[14:34] <alkisg> (and the second one replaces the first)
[14:34] <alkisg> Do I need a third package (like language-support-en) that depends on both of them or something?
[14:35] <james_w> maxb, persia: you can't do that with dh_install
[14:35] <persia> alkisg, No, that doesn't matter.
[14:35] <persia> james_w, Um, why not?  That's how I do libraries when I package those.
[14:36] <persia> alkisg, But you don't want circular dependencies anyway.  That just leads to headaches.
[14:36] <james_w> persia: you have a glob to list all files in /usr/lib except for .so?
[14:36] <persia> Well, no, I list the files I want installed.  But I don't see any reason why one couldn't construct a nifty glob.
[14:36]  * persia is pedestrian about these things
[14:36] <maxb> persia: It's not possible. Perhaps you're confusing globs and regular expressions
[14:36] <james_w> persia: I'm saying you can't construct a nifty glob
[14:37] <alkisg> persia: circular dependencies seem a headache to me too, but I just thought I'd use the same (=similar) dependencies that language-pack* uses... OK, I'll just dump one dependency :) Thanks!
[14:37] <james_w> dh_install uses a non-nifty glob
[14:37] <persia> Ah.  That's unfortunate.
[14:37] <james_w> maxb: so you can either be a bit more explicit in the install files, or use an override and rm and just list usr/lib/* in each
[14:38] <persia> alkisg, If you want to use the same dependencies, you can, but you get to figure how the relation (and looking that those packages is probably your best guide).  The constrant recommendation is to not introduce circular dependencies.
[14:38] <alkisg> (in bash there's a GLOBIGNORE=*.so for this - ignore me if that's irrelevant)
[14:38] <persia> alkisg, We try to avoid using bash as a backing shell for make in debian/rules
[14:38] <maxb> james_w: Yup, that's what I said 20 minutes ago, and then persia tried to convince me otherwise :-)
[14:39] <alkisg> I'm moving my scripts away from bashisms too :)
[14:39] <james_w> maxb: well, you caused me to read the source of dh_install, so it wasn't useless :-)
[14:40] <maxb> So, i'm thinking that shell is the way to go here -      if dh_listpackages | egrep -q '^foo-common$'; then indeponlystuff; fi
[14:43]  * persia reads more about globs, and gets annoyed at the lack of negation
[14:44] <persia> maxb, Um, no.  What precisely are you trying to do?
[14:44] <persia> And when do you need it done?
[14:45] <maxb> I need dh_install to install usr/lib/ into a foo and a foo-common package, putting *.so into foo and not *.so into foo-common
[14:45] <persia> And you can't determine !*.so in advance?
[14:46] <maxb> It could be done, but it would be somewhat more fragile to upstream changes
[14:46] <persia> Well, yes, but that's often a good idea when dealing with libraries.
[14:47] <persia> But the other option is to have your build rule depend on build-arch and build-indep
[14:47] <persia> No, that won't help.  You just have a single build run.
[14:48] <persia> Right.  Got it.
[14:48] <persia> Or maybe not.
[14:48] <maxb> In a dh6 world, I'd just use binary-arch vs. binary-indep - simple
[14:48] <persia> Just be careful with upstreams.
[14:49] <persia> maxb, binary-arch and binary-indep still exist in dh7.
[14:49] <persia> But dh_install runs in build.
[14:49] <persia> (or rather, in install, but build depends on install)
[14:50] <james_w> build depends on install?
[14:50] <alkisg> persia: could you give me your advice on one last thing? I built the "base" package with all the files in it. Now I'm trying to build the "differences" package that only contains a few of those files that needed to be modified.
[14:50] <alkisg> Am I understanding this correctly in that I need to copy the modified files to a different directory before I make the "differences" package? I mean that the usual "orig.tar.gz" method does not apply here, because there's no "original source" in the "differences" package, right?
[14:50] <persia> No.  I'm wrong.  install depends on build.
[14:51] <alkisg> (I'm probably not making any sense :()
[14:51] <persia> alkisg, I don't know how to advise you.  I don't think following that model is the right way to handle updates, although I understand that you do, and your arguments.
[14:51] <persia> But if you must do it that way, the differences package as native is likely least bad.
[14:51] <james_w> maxb: do you really mean foo-common from /usr/lib?
[14:52] <james_w> maxb: the package puts arch-indep things in /usr/lib?
[14:52] <persia> Ah, good point!
[14:52] <maxb> I do. Python (a bit perversely, I accept) puts *.py in /usr/lib
[14:52] <persia> maxb, Does it put it directly in /usr/lib, or in /usr/lib/something?
[14:52] <alkisg> persia: but is there a way to handle it as not-native, while preventing it from being 100Mb?
[14:53] <maxb>  /usr/lib/pythonX.Y/dist-packages/...
[14:53] <persia> alkisg, Yes, but that's probably even worse.
[14:53] <persia> maxb, Then just have foo-common.install contain usr/lib/python?.?/
[14:54] <maxb> The *.so files are *also* there
[14:54] <persia> (or specify more closely if you know the values of X and Y)
[14:54] <alkisg> persia: OK, I don't want to take any more of your time. I appreciate all of your help, thanks a lot. :)
[14:54] <persia> maxb, In the same directory as the .py files?
[14:54] <maxb> yes
[14:54] <persia> I don't think they belong there.
[14:55] <persia> Ugh, or maybe they do.
[14:55] <persia> That's just broken.
[14:55] <james_w> nope
[14:56] <james_w> well, not for python
[14:56] <persia> Well, yeah.  I claim python is broken, not the specific package.
[14:56] <james_w> maxb: can you just have *.py in foo-common.install and *.so in foo.install?
[14:57] <james_w> most packages don't bother with a common for this though
[14:57] <maxb> For added fun, there's multiple levels of directory structure
[14:57] <james_w> nice
[14:57] <persia> maxb, Don't bother with -common.  That's going to be easier.
[14:57] <persia> Unless the volume of arch-indep data is so large to make it very useful.
[14:58] <maxb> 1.1MB indep vs 55K archdep
[14:58] <maxb> :-)
[14:58] <maxb> The package is mercurial, fwiw, which currently has a question in the changelog from the Debian maintainer wondering what the proper way to do this is.
[14:59] <POX> arch:all python packages should not have files in /usr/lib (hint: /usr/share/pyshared)
[14:59] <persia> And that's the key.  It was broken.
[14:59] <persia> Fix the build system :)
[14:59] <maxb> No. The files *are* in /usr/share/pyshared by the time the build finishes
[14:59] <persia> Or live with arch-dep
[15:00] <persia> maxb, So, what's the confusion then?  foo.install has usr/lib and foo-common.install has usr/share
[15:01] <maxb> dh_install has to separate the upstream-style installation into two packages - dh_pysupport only runs later, and rearranges the structure
[15:02] <persia> dh7 doesn't seem to call dh_pysupport, unless it's a hook.
[15:03] <james_w> it's an addon
[15:03] <james_w> /usr/share/perl5/Debian/Debhelper/Sequence/python_support.pm
[15:04] <persia> Hrm.  And I suppose it works the way it does for legacy reasons.
[15:08] <POX> .py files should be installed to the standard location (/usr/lib or /usr/local/*/dist-packages), dh_pysupport will move them to /usr/share/pyshared
[15:09] <POX> /usr/share/pyshared should *not* be used in setupy.py's install
[15:09] <persia> POX, So, how should one construct dh_install hint files to split a package?
[15:10] <POX> make sure you use one dir only (force python2.6 to install to site-packages, without local) and then use something like /usr/lib/*/site-packages/foo/bar.py
[15:11] <POX> (in package.install file)
[15:11] <persia> maxb, ^^
[15:20] <POX> persia: maxb: maybe '*-packages/foo/bar.py' will work as well (you'll not have to touch python2.6 stuff then)
[15:29] <slytherin> geser: maven-plugin-tools needs a class which is not available in any of the packages libraries. So untill the library is located and packages, the maven work can not continue. I have asked Ludovic Claude for help as he is working on the maven stack in Debian.
[15:42] <debfx> what's the best way to add a png icon to a package? base64 encoded?
[15:46] <AnAnt_> Hello, should I subscribe u-u-s to such a bug: LP 397456
[16:02] <maxb> slytherin: I'm intrigued... people can't even find the class?
[16:06] <james_w> does anyone else find "(Accepted)" being at the end of the subject suboptimal?
[16:06] <james_w> mails from soyuz that is
[16:07] <soren> james_w: Woould you rather have it read something else or would you rather have "(Accepted)" somewhere else on the line?
[16:08] <slytherin> maxb: I didn't find it in already packaged libraries. It is available somewhere in maven repositories in one of the jar files.
[16:08] <ScottK> james_w: I do find this.
[16:08] <james_w> soren: in thunderbird's collapsed mode you only get the first half of the subject
[16:08] <james_w> so I have to expand it to see whether my upload was accepted or not
[16:08] <slytherin> debfx: do you really need to add png icon? Won't SVG work?
[16:09] <slytherin> james_w: I agree, Accepted should be in start
[16:14] <debfx> hm I could use another icon that available as svg
[16:36] <SolarWar> can i create multile pbuilder enviroments
[16:44] <ScottK> Yes
[16:45] <vorian> SolarWar: yes
[16:48] <slytherin> SolarWar: https://wiki.ubuntu.com/PbuilderHowto
[16:49] <SolarWar> :) thanks I found it already
[17:19] <dholbach> Adri2000: HAPPY BIRTHDAY!
[17:25] <Adri2000> dholbach: ahaha, thanks, but it was 2 months ago, I was slow at updating the wiki page :p
[17:28] <cpscotti> Any motu there killing time? Could you check the harpia package ( http://revu.ubuntuwire.com/p/harpia ). It was uploaded to the archive but had some little issues (all corrected now, I think) and got rejected. I already fixed them and re-uploaded it. It is a python app to generate c source code for image processing/computer vision from block diagrams.
[17:33] <geser> al-maisan: Hi, do you plan to finish the magicor merge (as I've seen that you have a potential merge in your PPA) or is this merge free to take?
[17:33] <al-maisan> geser: that was the idea, yes.
[17:35] <geser> no hurry, I just wanted a confirmation as fabrice_sp asked me if this merge is free or not
[17:35] <al-maisan> geser: actually, I just checked my email again, "The source magicor - 1.1-1ubuntu1 is already accepted in ubuntu/karmic"
[17:35] <al-maisan> is this the version in question?
[17:36] <geser> https://edge.launchpad.net/ubuntu/+source/magicor still shows 1.0-2ubuntu1
[17:36] <geser> but 1.1-1 is on the to-be-merged list
[17:36] <al-maisan> geser: I'll be busy with some other work in the next few days .. so if you feel like taking care of the package please do so.
[17:36] <al-maisan> don't mind me :)
[17:37]  * al-maisan understood that somebody else merged 1.1-1 in the meantime
[17:38] <al-maisan> hmm .. no .. just checked it.
[19:19]  * marienjoanny marienjoanny 
[19:23] <candrews_> Can someone please work on open-vm-tools? https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/277556 contains the addition of DKMS and fixes other bugs in open-vm-tools. The package currently in karmic is unusable.
[19:34] <gnomefreak> reto`: there is a link in the topic for what you are looking for
[19:40] <rohitkg> can anyone suggest how to modify the rules file,while creating a debian package
[19:43] <maxb> rohitkg: Do not. Ever. Neither debian or ubuntu would accept such a package
[19:44] <rohitkg> maxb:u mean to say,i shouldn't modify anything inside it
[19:45] <binarymutant> what about postinst and preinst?
[19:45] <maxb> I mean that it would be bad to have a rules file which modifies itself during the build
[19:46] <rohitkg> actually i'm facing problems in understanding the rules file
[19:47] <gnomefreak> was libgdl-1-0 replaced with something in Karmic?
[19:48] <maxb> rohitkg: Ah. Well then, ask specific questions about what you'd like help with.
[19:49] <geser> gnomefreak: libgdl-1-2
[19:49] <gnomefreak> geser: thanks
[19:51] <rohitkg> maxb:i want to know about the diff. macros used
[19:52] <stefanlsd> rohitkg: the dh_ stuff?
[19:52] <maxb> rohitkg: That is too vague an inquiry to answer. Please clarify.
[19:52] <rohitkg> yeah those dh_stuffs
[19:57] <reto`> gnomefreak: ok, thanks
[19:58] <gnomefreak> reto`: np
[20:01] <ScottK> YokoZar: I can tell you that clamd will cost you 5-6 seconds on boot if you start it at boot on a modernish laptop.
[20:02] <YokoZar> ScottK: ok then that's unworkable I guess
[20:02] <YokoZar> Should load it on first open of an app that needs to be scanned then
[20:02] <ScottK> YokoZar: Makes sense.  You'd still want freshclam to start on boot, but that's a lot lighter.
[20:05] <YokoZar> ScottK: Gives a good place to use the "have the wine swishing around the glass while loading" graphic I thought of
[20:11] <ScottK> ;-)
[20:34] <maxb> rohitkg: the dh_ commands are a set of related utilities known as debhelper, and provided by the package of the same name. They have manpages, which are a good place to start discovering what an unfamiliar one does.
[20:34] <rohitkg> ok,i'll be going through that
[20:35] <rohitkg> maxb:which tool do you prefer for building debian packages?
[20:35] <maxb> debhelper. cdbs is scary
[20:36] <rohitkg> ok,i'll start with it
[20:37] <maxb> You might want to review the logs of the packaging training session that was held today in #ubuntu-classroot
[20:37] <maxb> oops
[20:37] <maxb> #ubuntu-classroom
[20:37] <rohitkg> ok
[20:45] <RoAkSoAx> Makefile.in, which seems to have been generated automatically, can be manually modified?
[20:49] <geser> as long as you don't regenerate them yes, I usually patch both the .am and .in so the changes don't get lost if someone regenerates it
[20:50] <geser> of course only if the change is small enough to be make by hand
[20:54] <RoAkSoAx> geser, ok awesome, thanks. :)
[22:31] <slytherin> geser: persia: Can either of you please review http://revu.ubuntuwire.com/p/excalibur-logkit whenever you get time?
[22:52] <Legendario> i am trying to pack a script which is not distribuited as a tarball, what should i do in order to not create a debian native package?
[22:54] <hyperair> Legendario: create a tarball first.
[22:54] <hyperair> Legendario: or create a package-version.orig directory
[23:01] <Legendario> hyperair, the software is a bash script. Should i pack it as a tar.gz file and append .orig to it?
[23:02] <hyperair> either way's fine =\
[23:03] <hyperair> the result should be the same anyways
[23:03] <Legendario> hyperair, what about the package-version.orig directory? how does it work?
[23:03] <hyperair> debuild will automatically generate the .orig.tar.gz from that directory
[23:03] <hyperair> that's all there is to it =\
[23:09] <Legendario> hyperair, another thing... I am having a bad time on trying to create a watch file. Can u help me with that?
[23:10] <hyperair> Legendario: watch files can only be created with tarballs
[23:10] <hyperair> afaik
[23:10] <hyperair> man uscan
[23:11] <Legendario> hyperair, so should i ignore the error shown?
[23:11] <hyperair> you'd probably be better off with a blank watch file and a get-orig-source rule.
[23:11] <hyperair> create a blank watch file
[23:11] <hyperair> with a comment saying why a watch file isn't applicable
[23:12] <hyperair> and then add a get-orig-source rule to your debian/rules which automatically grabs the script and then dumps it into a tarball automatically
[23:14] <Legendario> hyperair, any orientation on how to create a get-orig-source rule?
[23:15] <hyperair> http://www.debian.org/doc/debian-policy/ch-source.html <-- scroll down to the part about get-orig-source
[23:15] <hyperair> anyway i'm off to bed
[23:15] <hyperair> good night
[23:16] <Legendario> hyperair, thanks a lot
[23:16] <Legendario> good night
[23:16] <hyperair> you're welcome
[23:17] <Ampelbein> Legendario: maybe http://www.eyrie.org/~eagle/notes/debian/scripts.html helps with creating get-orig-source.
[23:17] <Legendario> Ampelbein, gonna readit. thanks
[23:21] <cpscotti> Hey everybody, could someone advocate the harpia package ( http://revu.ubuntuwire.com/p/harpia ). It is a python app to generate computer-vision/image processing c source code from block diagrams. It has already been uploaded to archive but got rejected due to some dependencies issues that were already fixed. Thanks a bunch!
[23:52] <binarymutant> can dh7 do cmake?
[23:53] <binarymutant> automagically like regular make I mean