[06:28] barry: do you think that the git-buildpackage FTBFS is actually a pychecker+python2.7 problem ? [15:04] hello [15:04] wgrant: this page seems to be hanged: http://qa.ubuntuwire.org/multidistrotools/all.html === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [19:23] if i say override_dh_auto_build, and pass a -I/path/to/include on the make line, is that additive, in addition to the paths autotools already know about? or does it replace any existing values? === bcurtiswx_ is now known as bcurtiswx [21:06] Hi [21:06] I have a question.. If I create a chroot using pbuilder-dist for natty like [21:07] $sudo pbuilder-dist natty create [21:07] can I have another chroot pbuilder using say .. pbuilder-dist maverick create and maintain them side by side?? [21:08] yes [21:08] Don't call pbuilder-dist with sudo. It handles escalation and using sudo when needed. [21:08] But yes. [21:19] Thanks [21:20] ScottK, But I have already called it with sudo and its building my enviroment for natty. I hope it will not cause any harm..?? [21:21] I used this sudo pbuilder-dist natty create [21:21] simar: Should be fine, but it's not the best way to do it. [21:21] pbuilder-dist natty create would have worked too. [21:22] ScottK, ok, so I will try this in future .. and for the one that I'm going to build for maverick.. [21:22] ScottK, But do I need to rebuild for natty or it will work for my purpose. i'm a beginner [21:23] simar: I think it will. Worst case it puts some files in the wrong place and you have to move them a bit. [21:23] You won't need to redo it. [21:24] ScottK, ok I will hope it will work.. if it don't I will ping you then.. [21:24] ScottK, Thanks for help :)) [23:13] siretart: I have prepared a patch for you - libva ;-) [23:19] i'm putting my first dep-5 copyright file together. there's a COPYING file at the top-level. most files have copyright/license headers (that match the COPYING file), but a few short ones don't. i know the author and know that his intent was for the COPYING file to apply to all files. can i just do a single Files: * block? [23:30] also, did the papercuts guys (vish?) ever come up with guidelines on how package descriptions should be written? [23:34] broder, When dealing with that sort of thing, I usually make an estimate about whether the content of a file is worth copyrighting (short files without expression may not be). [23:34] If it is, best to get upstream to fix it (people failing to add copyright/licensing information to XML is the most common case I see). [23:35] In the case of autotools files, I've seen a number of folk add extra clauses to a DEP-5 copyright. [23:35] But the important thing is that you are representing the state of the files *as they are published*, rather than by a guess at author intent (some folk embed email from authors in debian/copyright to clarify things). [23:36] And that requirement isn't different between DEP-5 and other types of debian/copyright files. [23:36] *nods*