[04:46] <exobuzz> erm - i386 	8 	598 jobs (11 hours)  holy cr*p that's a bit queue. have some of the builders been taken off to do something else ?
[04:47] <exobuzz> only 3 amd64 and 5 i386 builders. :(
[04:47] <StevenK> exobuzz: Yes, they are dealing with kernel SRUs.
[04:48] <exobuzz> i see.
[04:51] <exobuzz> thanks for the info.
[11:22] <apw> have the archive keys changed for onieirc?  getting BADSIG all of a sudden on 'update'
[11:34] <cjwatson> apw: not as far as I know
[11:34] <cjwatson> might be transient Release vs. Release.gpg skew?
[11:35] <apw> cjwatson, yeah i'll monitor it for a bit and see if it goes away ..
[11:36] <cjwatson> we probably ought to roll over the keys to something stronger at some point, but it's not currently planned
[13:05] <and7ey> Hi all! Need your help to compile openzwave-control-panel (http://code.google.com/p/openzwave-control-panel/source/browse/) Ubuntu 10.04. Now I am getting an error that file is not found - http://askubuntu.com/questions/59972/how-to-compile-openzwave-control-panel-on-ubuntu-10-04
[13:16] <and7ey> how can I fix the following error: configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
[13:32] <and7ey> what should I install to get rid of the following error: configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."  ?
[14:54] <Chipzz> and7ey: this is not the correct channel to be asking these questions in; the topic specifically mentions "not app development"
[14:54] <Chipzz> and the package you're missing is probably libtool or autoconf or somesuch
[15:08] <and7ey> Chipzz: ok
[15:53] <shnatsel> hello everybody
[15:54] <shnatsel> would anybody point me where can I get the code for building images from seeds?
[16:31] <sladen> shnatsel: -> #launchpad  might be able to point you to the specific code
[16:31] <shnatsel> sladen: thanks!
[16:31] <shnatsel> sladen: I've been looking for something I could run locally, actually :)
[16:33] <sladen> shnatsel: I must say, my mind has gone completely blank about how this stuff works at a low-level anymore
[16:33] <sladen> shnatsel: https://help.ubuntu.com/community/InstallCDCustomization  might offer some guidance
[16:33] <shnatsel> sladen: that's a good sign. That's a sign of progress and ease of development :)
[16:34] <sladen> shnatsel: if not, check about in 24 hours when the Monday-Friday people will be around
[16:34] <shnatsel> sladen: thanks!
[16:36] <shnatsel> sladen: that wiki page describes lots of manual ways to do it, I tried lots of them in the past and ended up using UCK. But I know Ubuntu uses something simple and automatic that parses seeds, so I'm looking for it :)
[16:36] <shnatsel> sladen: I think I'll write some documentation as soon as I find it
[17:17] <jtaylor> doko__: now that pari built on arm genus2reduction should build too
[17:40] <Florian> hello, I have a question about building a package using bzr bd
[17:41] <Florian> I created a patch using dquilt and refreshed, but when I issue bzr bd -- -S --us -uc it complains about not finding the patch file
[17:41] <Florian> Is there something I forgot?
[17:42] <Florian> the error I got was: "dpkg-source: error: cannot read monster-masher-1.8.1.orig.dVBshx/debian/patches/add-esound-as-dependency.patch: No such file or directory"
[17:46] <jelmer> Florian: is the patch file versioned?
[17:47] <Florian> what exactly do you mean? I did add the dquilt patch according to the debain maintainer guide http://www.debian.org/doc/manuals/maint-guide/modify.en.html
[17:48] <jtaylor> did you commit the patch? you ahve to do bzr add patch-file
[17:50] <jelmer> Florian: if you run "bzr st" the patch should be listed as "added" rather than "unknown"
[17:52] <Florian> jelmer, the patch is listed as unknown: unknown:
[17:52] <Florian>   .pc/.quilt_patches
[17:52] <Florian>   .pc/.quilt_series
[17:52] <Florian>   .pc/add-esound-as-dependency.patch/
[17:52] <Florian>   debian/patches/add-esound-as-dependency.patch
[17:52] <jelmer> Florian: you should be able to add it by running "bzr add debian/patches/add-esound-as-dependency.patch"
[17:53] <Florian> thanks, that did it!
[18:45] <highvoltage> stgraber: this one: https://bugs.launchpad.net/ubuntu/+source/speechd-up/+bug/316511
[19:32] <shbk> hello, I've found function   man 2 getcpu.  I included it successful, but when I compile I receive error: no such function. I opened file  /usr/src/linux-headers-2.6.32-33/include/linux/getcpu.h  and noticed that there are not any description of funcition, only this http://paste.debian.net/128405/    . what is this ? there is function?
[21:13] <mdke> pitti: sorry for being a pain, but please could you take a look at bug 841340 some time in the next couple of weeks, it will be needed to reenable stripping of documentation translations into the language packs for oneiric
[23:43] <Apteryx> Hi!
[23:45] <Apteryx> Could someone help me figure out how the build process works for the pulseaudio package? I'm trying to package 0.99.3 (instead of the 0.9.22 currently available), and am stuck on how quilt is used in the process.
[23:48] <TheMuso> Apteryx: What version of Ubuntu are you trying to package for?
[23:54] <Apteryx> TheMuso, I'm using Ubuntu 11.04 natty (32 bits).
[23:54] <Apteryx> and packaging for it.
[23:54] <TheMuso> Apteryx: Ok. The way quilt is used in the pulseaudio package is actually part of the source package format. Version 3.0 of the source package format uses quilt as the patch system, so the packager themselves do not need to include quilt commands in the rules file, or in the build dependencies.
[23:54] <TheMuso> So when you unpack a source format 3 package with patches included, these patches automatically get applied.
[23:55] <Apteryx> TheMuso, but for pulseaudio I don't think they are using format 3.0
[23:55] <Apteryx> There was nothing in ./debian/source/
[23:56] <Apteryx> So when building there was only a warning stating it was going to use 1.0
[23:56] <TheMuso> Apteryx: Yes you are correct, the natty pulse package is not source format 3, and uses quilt in the rules file and is a build dependency.
[23:59] <Apteryx> TheMuso, in the ./debian/rules file I tried to understand the "update-patch-series" target. They are using git format-patch to produce the series file (which I thought was processed by quilt).