[01:04] <psusi> I'm trying to build brasero with debug syms and I set nostrip in DEB_BUILD_OPTIONS, and lintian throws errors that the binaries are unstripped and aborts the binary package build... is this a bug in lintian?  sholdn't it recognize the nostrip option and not make this complaint?
[01:07] <xnox> psusi: lintian does not abort the build. as debs have been generated. lintian is not run by default, you probably enabled it in your hooks/scripts (sbuild, pbuilder, devscripts, debuild)
[01:12] <psusi> xnox, don't have any of those, just running bzr bd
[01:12] <psusi> xnox, the package appears to have been improperly upgraded to 3.0 (quilt)... it still includes all of the old cdbs helpers that are doing all of the heavy lifting... I suspect they are running lintian and aborting the build on lintian errors
[01:15] <psusi> oh wait, nevermind... it did get built... guess my build-area is getting a little cluttered
[01:55] <saiarcot895> hi all
[01:55] <saiarcot895> I have a question regarding packaging data files
[01:56] <saiarcot895> I'm packaging the data files for FlightGear Flight Simulator in my PPA, and users have to download about 700 MB each time there's an update.
[01:57] <saiarcot895> Currently, there's one debian directory generating about 10 packages, the largest of which is 500 MB.
[01:57] <saiarcot895> As far as I can tell, when there's an update, all of the packages get updated, and users have to download the full 700 MB again.
[01:58] <saiarcot895> Is there a way to reduce this size?
[02:00] <xnox> is 500 just static images/content?
[02:00] <xnox> ship it in a separate source package.
[02:00] <xnox> such that you upload/update it only when images change.
[02:00] <xnox> and not when game bugs are fixed.
[02:01] <saiarcot895> it's just static content
[02:01] <saiarcot895> so to do that, do I need to have separate debian directories?
[02:02] <saiarcot895> Currently, the user does see several packages, but it's building as one package in Launchpad and generating multiple deb files
[02:05] <ESphynx> xnox: can I somehow target this 0.44.1 to Raring? :)
[02:06] <ESphynx> xnox: I got the 64 bit support pretty much working... setting up the first complete toolchain right now :) And then I just have to tweak the bootstrapping process...
[02:10] <TheLordOfTime> saiarcot895, what xnox is saying is pull the static content out, and create a separate package for it (that is to say a complete debian/ directory, different source packag name, etc.)
[02:10] <TheLordOfTime> and only update it as needed.
[02:10] <saiarcot895> ok
[02:10] <saiarcot895> the other part of my question is that can the packages have the same source file?
[02:11] <saiarcot895> everything comes in a .tar.gz file
[02:12] <TheLordOfTime> saiarcot895, xnox could probably answer that better than I, as could any of the MOTUs/devs/more expert users
[02:14] <saiarcot895> ok
[02:15] <saiarcot895> thanks, TheLordOfTime
[07:31] <dholbach> good morning
[07:32] <geser> good morning
[09:13] <xnox> TheLordOfTime: cp mypkg_1.0.orig.tar.gz mypkg-dataonly_1.0.orig.tar.gz tadah =)
[09:30] <ESphynx> xnox: I set a milestone for Feb 28 :P
[09:30] <ESphynx> https://launchpad.net/ecere/+milestone/0.44.1
[12:10] <Rhonda> For backports, do I need to include the upstream source in the changes file, or can they get pulled from the raring pool?
[12:19] <Laney> Rhonda: I think Launchpad can cope with either but we do usually use -sa
[12:19] <Laney> backportpackage seems to use that
[12:20] <Laney> the version scheme is <original version>~ubuntu<numeric release being backporter to>.1 FYI
[12:21] <Laney> so like 1:1.10.5-1~ubuntu12.10.1
[12:23] <Laney> for the no change ones you can use backportpackage -s raring -d oneiric -w . wesnoth-1.10
[12:24] <Rhonda> Laney: Well, with -sa it would mean I have to upload the tar.bz2 with everything, which makes it a pain. ;)
[12:24] <Laney> try it without and see if you get rejected
[12:25] <Rhonda> And thanks for the <numeric> hint, I'll update my patches.
[12:27] <Rhonda> I think I'll pass for backportpackage, I want to have the changes in my git. :)
[12:27]  * Laney nods
[12:27] <Laney> well, feel free to upload this
[12:27] <Rhonda> No need to update the patches for you?
[12:29] <Laney> I can review them in the queue
[12:29] <Laney> all backports land there
[12:29]  * Rhonda . o O ( note to self, Laney reviews from queue, no need for bugreports )
[12:29]  * Rhonda hides. :)
[12:30] <Laney> well, usually the backporter acks and runs the script to do the backport himself
[12:30] <Laney> and uploads, then accepts
[12:30] <Laney> oh, don't forget to (LP: #xxxx) in your changelog too
[12:30] <Rhonda> Ah, right
[14:38] <Laney> Rhonda: you haz backports
[14:48] <Rhonda> Laney: u haz thanks
[18:22] <shadeslayer> could someone update tp-logger from https://launchpad.net/~telepathy-kde/+archive/daily-builds/+files/telepathy-logger_0.8.0-0ubuntu1~ppa1.dsc
[22:19] <shadeslayer> could someone update tp-logger from https://launchpad.net/~telepathy-kde/+archive/daily-builds/+files/telepathy-logger_0.8.0-0ubuntu1~ppa1.dsc