[17:29] <qwebirc69617> tgm4883: just wondering if you got a response about compiling in crystal hd support?
[17:42] <superm1> qwebirc69617: the source package is only in precise, so it does present some logistical problems
[17:42] <superm1> https://launchpad.net/ubuntu/+source/crystalhd
[17:42] <Zinn> [launchpad.net] âcrystalhdâ package : Ubuntu
[17:42] <superm1> were you wanting this on 0.24 or 0.25?
[17:43] <qwebirc69617> I've got a test machine running 11.10 with 0.24-fixes so I was hoping for that
[17:43] <superm1> well we'll need to backport it all the way back to lucid to make that happen
[17:43] <superm1> on both PPAs then
[17:43] <qwebirc69617> ouch
[17:44] <qwebirc69617> I'd be willing to test it on 0.25 but I don't have a test 0.25 backend set up yet
[17:46] <qwebirc69617> Is it a big job to compile it myself?  I haven't looked into that yet
[17:46] <qwebirc69617> figured I'd ask here first
[17:46] <superm1> it shouldn't be a very big job to compile it yourself
[17:46] <superm1> we have a recipe for spitting out your own packages actually if you want to try stuff like that
[17:47] <superm1> http://mythbuntu.org/wiki/recipes
[17:47] <superm1> patching and building from source
[17:47] <Zinn> [mythbuntu.org] Recipes | Mythbuntu
[17:48] <qwebirc69617> that'd be nice to try...I'll take a look.....does this mean you're going to leave it for now or would this be something that gets added when time is available?
[17:49] <superm1> well i'd like to get it added when time is available
[17:51] <qwebirc69617> ah....thanks....is there a way to tell what compile options have been used for a package?
[17:51] <superm1> if you run mythfrontend --version
[17:51] <superm1> it will tell you all the compile options that were included
[17:52] <qwebirc69617> cool...didn't know that....thanks again
[17:52] <superm1> sure
[18:07] <qwebirc69617> superm1: one more question, how would I specify the --enable-crystalhd compile flag using the build-debs.sh script?
[18:36] <superm1> qwebirc69617: do one successful build without it first, and then switch into the work directory/bzr-fixes and modify it in debian/rules
[18:36] <superm1> then bzr commit -m "enable crystal HD locally"
[18:36] <superm1> so that it won't get overwritten during the clean phase
[18:37] <superm1> and run build-debs.sh again
[18:37] <qwebirc69617> I was running the first step and it errors at this line
[18:37] <qwebirc69617> packaging/deb/build-debs.sh: 175: get-build-deps: not found
[18:38] <superm1> ah that means that you're missing a tool
[18:38] <superm1> what package did that come from
[18:38] <superm1> (and we should be checking for that package too)
[18:38] <qwebirc69617> I'm not sure....it was installing all the missing packages and then stopped
[18:39] <qwebirc69617> the previous line is this
[18:39] <qwebirc69617> ubuntu-dev-tools is already the newest version.
[18:39] <superm1> hmm, maybe it used to be in ubuntu-dev-tools but got moved somewhere else
[18:42] <superm1> ah i see it was removed on sep 10
[18:42] <superm1> try using 'mk-build-deps -ir'
[18:42] <superm1> i'll fixup the script later on for that
[18:43] <qwebirc69617> I just noticed it was removed too
[20:51] <qwebirc69617> superm1: just got back to this....mk-build-deps looks like it needs a package name where get-build-deps doesn't
[20:52] <superm1> qwebirc69617: you can try to feed it the package name or the path to the control file i think
[20:53] <qwebirc69617> is it a variable in the script?
[20:54] <superm1> qwebirc69617: based on where pwd is at that time, I think you can just call it like 'mk-build-deps `pwd`/debian/control