[03:46] <faina> I'm trying to build packages for the firefox sync server, and have a question about packaging python mako templates.
[03:48] <faina> should the templates be compiled to .py files and then included -- done some how in the debian/rules, or should I try to figure out some where to cache them when compiled after installation?
[12:24] <maxb> Hm, if a package was removed from Debian in plenty of time before DebianImportFreeze, and there are no ubuntu modifications, shouldn't it have automatically been removed from oneiric too?
[12:43] <jtaylor> I don't think its automatic
[12:43] <jtaylor> must be requested
[12:43] <tumbleweed> maxb: removal isn't automatic, archive admins occasionally look at removals in Debian
[12:43] <tumbleweed> it's not necessary to explicitly request it when Debian has removed it
[13:09] <maxb> ah
[14:05] <bdrung> persia: re your dmb mail: all this should be documented somewhere (e.g. wiki page)
[15:12] <ansgar> Does Ubuntu already allow packages (both source and binary) to use XZ compression?
[18:13] <persia> bdrung: Absolutely.  If the TB doesn't change it, let's put it in the wiki
[18:14] <Laney> Basically it's what (most of us) thought we were doing anyway.
[18:14] <Laney> but thanks for spelling it out
[18:14] <persia> I should probably rely less on memetic transmission and more on documentation :)
[18:15] <Laney> at least it's in the ML archives
[18:15] <Laney> that's a form of documentation.
[18:16] <persia> I thought it was in the minutes of some meeting before.  Anyway, we should have iut in the wiki, as we'll forget again in another couple years.
[18:18] <Laney> yep. after the tb speaks.
[18:23] <faina> I was trying to build a debian package of the firefox sync server and ran into a python packaging policy question. They're using mako templates which compile to .py files. I was trying to figure out if it'd be better to compile the templates into the package, compile them into a cache directory at runtime on the installed systemm, or compile them when the package is installed.
[18:28] <persia> faina: Create the .py files at build time.  Let the system generate the .pyc files at install time.  Do not build anything at package creation time.
[18:30] <faina> Ok, I'd almost convinced myself that the template compiling should be done at install time, as that'd be like the current .py -> .pyc policy.
[18:30] <faina> But I think compiling at build time would be a lot easier
[18:31] <persia> Indeed.  Saves lots of compute cycles worldwide.
[18:32] <faina> why is there the build .pyc at install-time policy? Oh... because you don't know which versions of python are installed
[18:32] <persia> Right :)
[18:33] <faina> thank you... I've been trying to figure out a good answer to that question for a couple of days
[22:33] <jMCg> Hello happy people.
[22:34] <jMCg> I'm a traffic server dev, and I'm trying to repro this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632546
[22:35] <jMCg> On Natty this builds fine, so if I get this right, these symbols don't exist in Natty's libssl.
[22:36] <tumbleweed> jMCg: daemonkeeper was just asking the same questions in #debian-ubuntu on OFTC
[22:37] <jMCg> tumbleweed: I'll be there for less.. uh.. stuff.
[22:37] <tumbleweed> you'll only see this occur in pre-release natty or oneiric. ld stopped using --as-needed by default for natty release, because not all packages were building yet