[01:04] 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] 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] xnox, don't have any of those, just running bzr bd [01:12] 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] oh wait, nevermind... it did get built... guess my build-area is getting a little cluttered [01:55] hi all [01:55] I have a question regarding packaging data files [01:56] 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] Currently, there's one debian directory generating about 10 packages, the largest of which is 500 MB. [01:57] 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] Is there a way to reduce this size? [02:00] is 500 just static images/content? [02:00] ship it in a separate source package. [02:00] such that you upload/update it only when images change. [02:00] and not when game bugs are fixed. [02:01] it's just static content [02:01] so to do that, do I need to have separate debian directories? [02:02] Currently, the user does see several packages, but it's building as one package in Launchpad and generating multiple deb files [02:05] xnox: can I somehow target this 0.44.1 to Raring? :) [02:06] 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] 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] and only update it as needed. [02:10] ok [02:10] the other part of my question is that can the packages have the same source file? [02:11] everything comes in a .tar.gz file === FlannelKing is now known as Flannel [02:12] saiarcot895, xnox could probably answer that better than I, as could any of the MOTUs/devs/more expert users [02:14] ok [02:15] thanks, TheLordOfTime === murthy is now known as murthy_ === jackyalcine is now known as zz_jackyalcine === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [07:31] good morning [07:32] good morning [09:13] TheLordOfTime: cp mypkg_1.0.orig.tar.gz mypkg-dataonly_1.0.orig.tar.gz tadah =) [09:30] xnox: I set a milestone for Feb 28 :P [09:30] https://launchpad.net/ecere/+milestone/0.44.1 === dholbach_ is now known as dholbach [12:10] 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] Rhonda: I think Launchpad can cope with either but we do usually use -sa [12:19] backportpackage seems to use that [12:20] the version scheme is ~ubuntu.1 FYI [12:21] so like 1:1.10.5-1~ubuntu12.10.1 [12:23] for the no change ones you can use backportpackage -s raring -d oneiric -w . wesnoth-1.10 [12:24] Laney: Well, with -sa it would mean I have to upload the tar.bz2 with everything, which makes it a pain. ;) [12:24] try it without and see if you get rejected [12:25] And thanks for the hint, I'll update my patches. [12:27] I think I'll pass for backportpackage, I want to have the changes in my git. :) [12:27] * Laney nods [12:27] well, feel free to upload this [12:27] No need to update the patches for you? [12:29] I can review them in the queue [12:29] 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] well, usually the backporter acks and runs the script to do the backport himself [12:30] and uploads, then accepts [12:30] oh, don't forget to (LP: #xxxx) in your changelog too [12:30] Ah, right === almaisan-away is now known as al-maisan [14:38] Rhonda: you haz backports [14:48] Laney: u haz thanks === Quintasan_ is now known as Quintasan === al-maisan is now known as almaisan-away === bambee is now known as rperier === highvolt1ge is now known as highvoltage === zz_jackyalcine is now known as jackyalcine === yofel_ is now known as yofel [18:22] could someone update tp-logger from https://launchpad.net/~telepathy-kde/+archive/daily-builds/+files/telepathy-logger_0.8.0-0ubuntu1~ppa1.dsc === murthy is now known as murthy_ === jackyalcine is now known as zz_jackyalcine === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [22:19] could someone update tp-logger from https://launchpad.net/~telepathy-kde/+archive/daily-builds/+files/telepathy-logger_0.8.0-0ubuntu1~ppa1.dsc