[00:40] <cjwatson> ccheney: I think you need to read the preseeding guide in more detail.  you need to preseed early questions on the kernel command line.  don't use debconf-get-selections for this, or look at questions.dat - it will only be confusing.
[00:41] <cjwatson> (so e.g. console-setup/layoutcode=us on the command line)
[00:43] <cjwatson> and don't preseed console-setup/layout or console-setup/variant at all; I don't think the guide advises that?
[01:13] <Caesar> bigon: I know, I'm the Debian maintainer of it
[02:18] <ccheney> cjwatson, ah ok, thanks
[02:19] <ccheney> cjwatson, it appears i had a seeded answer on the kernel command line but that it was wrong, oops
[03:15] <j1mc> hi all. the ubuntu doc-team is going to update the packaging guide.  if you have a bit of time, please complete our packaging-guide survey: http://is.gd/dr5Ef
[04:52] <RAOF> cjwatson: Are you still planning to merge console-setup from Debian?  If you are planning to do it soon I can drop some Ubuntu delta to the xserver.  If not, no worries.
[05:13] <un214> apt-get source sysvinit-utils gets sysvinit, which is missing the sysvinit-utils.install and related packaging files
[05:18] <pitti> Good morning
[05:19] <pitti> apachelogger: pong
[06:28] <pitti> there, all SRU queues empty
[06:49] <jdong> pitti: ah, it's a good feeling :)
[06:54] <jdong> pitti: whooo! Always a great feeling
[07:47] <dholbach> good morning
[08:28] <dholbach> can an archive admin please process the sync requests?
[08:33] <apachelogger> pitti: good morning :) is it save to assume that pot files only get imported from i386 builds?
[08:34] <pitti> apachelogger: pkgbinarymangler imports them from all architectures
[08:35] <pitti> but I'm not really sure how that works in Rosetta
[08:35] <pitti> dpm: ^
[08:38] <apachelogger> The thing is, since we are creating pot files at build time it adds quite some load, which we really should avoid on armel and the likes.
[08:43] <dpm> hey pitti, good morning, let me have a look
[08:45] <pitti> apachelogger: my guess is that it's enough to build it on one arch only
[08:45] <apachelogger> must be, because kde-l10n-* is arch: all :)
[08:45] <pitti> the interesting question is what would happen if different arches produce different pots
[08:46] <apachelogger> *nod*
[08:46] <pitti> whether rosetta will merge them, or randomly select one
[08:47] <geser> pitti: Thanks for the gnupg2 SRU upload. I somehow got the impression that I need an SRU ack first before seeking for sponsorship.
[08:48] <dpm> I can only confirm what pitti is saying: pkgbinarymangler uploads a tarball for each arch - I'm not sure what Launchpad does with them. Let me ask the Launchpad guys
[08:48] <pitti> geser: both approaches were in use until now; jdong just proposed the "always upload directly" approach or everyone now (which will help to speed up things)
[08:49] <dpm> the LP guys are on a sprint, I'll try to reach them later on
[09:14] <TimStarling> what happens if you have a package in two different distro versions, and the source hasn't been updated so the package has the same version, but you need to recompile it?
[09:15] <TimStarling> do you just bump the revision number?
[09:15] <joaopinto> TimStarling, assuming it's an universe package, #ubuntu-motu is a better channel for that question
[09:16] <TimStarling> it's not, but I might try there anyway
[09:17] <joaopinto> mvo, hi, is there a good reason for the APT's mirror: method to have the 6h Acquire::Mirror::RefreshInterval by default ? None of the other methods has such refresh, and it defeats the usual "sudo apt-get update" purpose
[09:17] <TimStarling> it's for our own APT repository that holds our in-house software, but I'm happy to adopt conventions from anyone who has thought about the issue
[09:20] <mvo> joaopinto: no, no good reason, initially it was meant to be a protection for the server, but that is silly
[09:21] <cjwatson> RAOF: I'd been putting it off because it's painful, but I guess I should queue it up for next.  Working on syslinux/gfxboot at the moment which is interesting in its own right
[09:23] <mvo> joaopinto: fixing that in trunk to make it 1min only
[09:24] <RAOF> cjwatson: That's cool.  gfxboot certainly sounds more fun!
[09:25] <wrinkliez> hey guys, im making my changelog for my application now.  what if it doesnt matter what distribution my program is for? do i put "all" in the changelog?
[09:28] <joaopinto> mvo, great, on getdeb we are evaluating to switch from http redirects to the mirror method, for the current release we will need to distribute a apt .conf to set the refresh to 0
[09:29] <mvo> yeah, in maverick that is oing to get fixed
[09:29] <joaopinto> for a web interface with frequent updates is crucial to have the cache refreshed from an updated mirror
[09:29] <joaopinto> so the mirror list will built from scanning a pool of mirrors
[09:29] <joaopinto> be
[09:34] <joaopinto> mvo, is there some documentation about the 'Packages' diffs support ? I think I have seen it on some archive, apt already supports them right ?
[09:35] <mvo> joaopinto: apt supports them, they are called "pdiffs" and you can get examples for this on the debian archive
[09:36] <mvo> joaopinto: but they are only useful if there is not too much churn in the packages files, as they are "sequential" (basicly just patches) and if your packages file is generated 10 times a day the user needs to download 10 patches
[09:36] <mvo> joaopinto: that may well be not efficient anymore
[09:36] <mvo> joaopinto: for stuff that is big and changes slowly they are great
[09:39] <joaopinto> right, not very useful for volatile repositories
[09:47] <cjwatson> RAOF: ... maybe
[09:48] <cjwatson> RAOF: current state is that kvm falls over with an internal error trying to run it, so I'm sitting here tracing through assembly code ... depends what you call fun
[14:51] <dmart> amitk: Hi, do you have a moment?
[14:53] <amitk> dmart: sure
[14:54] <dmart> Hi there... just wondering where you were on the arm-m-missing-security-features stuff?
[14:55] <dmart> amitk: Were you able to push your SECCOMP patch yet?
[14:55] <amitk> dmart: I'd gotten distracted with Linaro PM work, but I've just resurrected the patch today and will test it
[14:56] <dmart> Was there any difficulty there, or is it just a question of pushing the patch?
[14:56] <amitk> dmart: no difficulty, just too many balls in the air
[14:56] <amitk> I should have something this week
[14:57] <dmart> OK, cool - thanks.  Sounds like that will fit well within the proposed milestones
[15:11] <pitti> lamont: https://edge.launchpad.net/ubuntu/+source/mozart/1.4.0-5build1/+build/1776421 seems stuck (building for 4 days without any log), maybe this should be killed?
[15:19] <Keybuk> pitti: argh, could you NAK the -proposed upload of ureadahead from rtg please?
[15:20] <pitti> uh, there's not even a bug associated
[15:20] <Keybuk> indeed
[15:20] <pitti> ah, just wrong syntax
[15:20] <pitti> bug 501715
[15:20] <Keybuk> and the patch is about as wrong as tedg in a mankini
[15:21] <Keybuk> the upload, as is, will simply stop it from working entirely
[15:21]  * tedg sends photos in private message
[15:21] <pitti> *chuckle*
[15:21] <pitti> Keybuk: can you please elaborate on the bug? I'll set it to v-failed
[15:21] <Keybuk> sure
[15:22] <pitti> Keybuk: so it's bad enough that I should pull it from -proposed?
[15:22] <Keybuk> yes
[15:22] <Keybuk> it will truncate or wipe the buffer before even parsing it
[15:23] <asid> hello...we're 4 students looking for some idea for a project ....if anyone could suggest an idea for some feature\software that  you would like to see in linux, it would be great
[15:23] <pitti> Keybuk: done, bug updated
[15:24] <pitti> Keybuk: and hello BTW!
[15:24] <jussi> asid: which languge do you want to write in?
[15:24] <asid> at this stage we're open to just about anything....C\C++, web based, Java
[15:25] <jussi> asid: and how big of a project?
[15:25] <Keybuk> pitti: hello :-)
[15:25] <pitti> Keybuk: unrelated question, is anything wrong with the udev in bzr head? robert_ancell was asking about it, since the new bluez needs it
[15:25] <pitti> (well, at this point we should update to 160, but I wasn't sure whether you held it back intentionally)
[15:25] <Keybuk> pitti: it didn't boot
[15:25] <pitti> details!
[15:25] <pitti> :)
[15:25] <Keybuk> I didn't get as far as details ;)
[15:25] <Keybuk> it didn't boot, I didn't upload it
[15:26] <asid>  we're 4 college students (amateur coders) and this is for a major project ...perhaps 3-6 months
[15:26] <Keybuk> will investigate more probably at the sprint
[15:26] <pitti> Keybuk: no, I mean, that's such a small bug
[15:26] <pitti> sorry, that didn't quite come across as intended
[15:26] <Keybuk> ah
[15:26] <Keybuk> lol
[15:28] <ion> keybuk: Any in-progress Upstart 0.10 code you could publish? :-)
[15:28] <jussi> asid: do you have any things that you are particularly interested in?
[15:30] <asid> well actually we're amazingly  blank about what to do(on the day before an exam, I am usually bursting with ideas of better things i would rather do) ...
[15:31] <jussi> asid: hehe, well Im sure we can find something.
[15:38] <asid> we've been juggling ideas as random as MMOGs, browser-based 3d modelling tools, home automation etc....
[16:04] <lamont> pitti: buildd    7227  6.1  0.0   2136   536 ?        R    Jul10 388:29      |                                                               \_ /bin/sh /build/buildd/mozart-1.4.0/doc/utilities/latex2png /tmp/file0yXDun apptut-html 1 2 3
[16:04] <lamont> I'm guessing you're right
[16:05] <lamont> pitti: 787137711 bytes of logfile
[16:11] <cjwatson> could an archive admin review syslinux and gfxboot in NEW, please?
[16:12] <StevenK> cjwatson: Certainly
[16:12] <dholbach> nigelb, pedro_, JFo: ready for UDW later on?
[16:12] <pedro_> dholbach, yeah!
[16:12] <JFo> I am indeed :)
[16:17] <StevenK> cjwatson: Since syslinux is in main, where would you like extlinux to end up?
[16:17] <nigelb> dholbach: oh yeah! :)
[16:17] <dholbach> woohoo
[16:17] <cjwatson> StevenK: extlinux can go in universe for the time being, IMO
[16:18] <cjwatson> it shouldn't be dangerous in main, but there'll be nothing pulling it in there
[16:19] <StevenK> cjwatson: Okay, same question for gfxboot-dev
[16:19] <cjwatson> needs to be in main, it'll be a build-dependency of gfxboot-theme-ubuntu
[16:22] <StevenK> cjwatson: Accepted.
[16:24] <cjwatson> thanks
[16:26] <lamont> pitti: so I think it had a build log, it's just newlines after about line 4100 or so..
[16:26] <lamont> killed, fwiw
[16:29] <Keybuk> apw: apply! apply! apply!
[16:29] <apw> Keybuk, ok on my list ...
[16:41] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 3 about to start in 19 minutes in #ubuntu-classroom
[17:39] <ManDay> Can anyone tell me why the wacomutils have been taken out of the repos?
[17:40] <c_korn> ManDay: what is the package name ?
[17:56] <LucidFox> Oh great, the latest post on Planet Ubuntu says Twitter in huge letters
[17:56] <LucidFox> there is no escape, you can run but you can't hide...
[17:57] <azeem> wow, planet ubuntu has excessive drop shadows now
[18:02] <Keybuk> LucidFox: you would prefer it to say LucidFox in large letters?
[18:03] <LucidFox> No, I'm just sick of Twitter mentions everywhere, to the brink. Wrong place for me to rant about it, though
[18:04] <maco> azeem: has had for a while
[18:04] <Keybuk> you're sick of people mentioning micro-blogging on their blogs?
[18:04] <Keybuk> that's a bit like being sick of people mentioning their cameras on flickr isn't it?
[18:10] <LucidFox> Keybuk> Well, blogging and microblogging are... different things
[18:11] <LucidFox> one makes sense to me, the other doesn't
[18:12] <LucidFox> (or well, I can understand why *some people* would use it, but a) I can't understand why it's so massively popular to the point that every single site has button links with the T-word, and b) I don't use it myself, don't see the point, can't see why I ever would, etc.
[18:12] <Keybuk> lots of things don't make sense to me: Religions, Al Murray (The Pub Landlord), Wearing sunglasses in nightclubs, Fish, etc.
[18:13] <highvoltage> Keybuk: some people just have sensitive eyes!!!
[18:16] <davmor2> Keybuk: you missed off sysvinit :)
[18:18] <Keybuk> that makes sense
[19:59] <nuovodna> hi, will gtk 3.0 be in maverick repo ??
[21:00] <highvoltage> robbiew: is https://wiki.ubuntu.com/MaverickReleaseSchedule still acurate?
[21:00] <highvoltage> robbiew: sorry, I read step 24 as October 24. nm :)
[21:00] <robbiew> highvoltage: ;)
[23:10] <SpamapS> hmm, so why isn't rrdtool listed here: https://merges.ubuntu.com/main.html  if it is grossly out of sync w/ debian and has been since 2010-01-22?
[23:17] <cjwatson> SpamapS: bug in merge-o-matic, triggers when some Debian architectures are out of sync
[23:18] <cjwatson> SpamapS: Debian's archive software changed a while back to keep all the versions in Sources that correspond to any architecture, and hurd-i386 is way out of date (as usual)
[23:18] <cjwatson> SpamapS: I have half a patch for MoM to fix this but haven't had time to test it
[23:19] <SpamapS> cjwatson: Ahh, so is the fix to request a sync?
[23:19] <SpamapS> I mean, workaround
[23:19] <SpamapS> The dbi capabilities of the latest version are particularly appealing for some stuff I've been playing with. :)
[23:22] <cjwatson> SpamapS: you can request a sync or merge as appropriate regardless of what merge-o-matic says
[23:23] <cjwatson> there's a single change in Ubuntu; look at it and check whether it's still appropriate
[23:23] <cjwatson> if it is, prepare a merge (not hard to do by hand - fetch the base version from ftp.debian.org or snapshot.debian.org or whatever, diff Debian->Ubuntu, apply diff to new Ubuntu package, resolve conflicts, create new changelog entry at the top)
[23:23] <cjwatson> otherwise, request a sync