[00:41] <slangasek> lamont: hmm, remind me why 'inet protocols = ipv4' is still the default in postfix? :)
[00:41] <lamont> because
[00:42] <lamont> any bug from lintian telling me that I'm not using quilt will cause me to go back to version 1.0 packaging
[00:42] <slangasek> huh?
[00:42] <lamont> sorry.  just reacting to ubotu
[00:43] <slangasek> ah
[00:44] <lamont> but then, hey, that's what lintian overrides are all about, right?
[00:44] <cjwatson> honestly?  I think if you aren't actually making use of quilt, then for the most part it makes more sense to use 1.0 packaging; otherwise you're basically just doing 1.0 transliterated into 3.0 (quilt) and it doesn't really help all that much
[00:45] <slangasek> unless you want to use it for the bz2 support
[00:45] <slangasek> or the binary diff support
[00:45] <slangasek> :)
[00:45] <cjwatson> the exception is if you want to have binary files in the Debian delta, in which case a 3.0 format is useful
[00:45] <lamont> cjwatson: well, I got this really nicely worded bug asking me to switch to 3.0(quilt)
[00:45] <cjwatson> or that
[00:45] <lamont> which I promptly tagged wontfix, and then reconsidered
[00:45] <lamont> I have a vcs.  I don't need another vcs in the source package
[00:46] <cjwatson> I find them to be usefully complementary, but I guess I can't really be bothered to get into a religious debate. :-)
[00:47] <cjwatson> but briefly, the quilt approach lets me store evolving information about a logical patch (which may change over time) without having to rebase my history to death and render it incomprehensible
[00:47] <lamont> I like to have my source where I can bisect it, and do other useful diff-like things, without needing to delve through patch files to notice things
[00:48] <cjwatson> uh
[00:48] <lamont> but yeah, it's at least largely religious.  as long as you don't modify an older patch which patches files that are in later patches (that'd be a rebase of the parent branch, and that's just evil)
[00:48] <cjwatson> so do I, and 3.0 (quilt) is the first patch-system format to give me that property
[00:48] <cjwatson> because I store the package with patches applied
[00:48] <lamont> that does have some potential
[00:49] <slangasek> lamont: so ipv4-only is just a 'because'?
[00:49] <lamont> I do admit that I interpreted "quilt" as that old piece of crap that implements about 1/2 of a 1980s VCS and (correctly) claims to be better than dpatch as its only selling point
[00:50] <lamont> slangasek: ipv6 is real.  people are using it.  I got tired of the complaints.
[00:50] <slangasek> that setting is going to cause an increasing amount of grief over the next couple of years :)
[00:50] <slangasek> whu?
[00:50] <slangasek> yes, ipv6 is real, and I am using it, which is why I'm asking about the default to *not* allow it in postfix
[00:50] <lamont> or are you saying ipv4-only is the current default?
[00:50] <slangasek> yes
[00:50] <lamont> oh, that's total crack
[00:50] <lamont> I should fix that
[00:50] <slangasek> which caused me to accidentally drop mail from Patty's laptop on the floor over the weekend when I reorganized the ipv4 network, oops
[00:51] <lamont> meh.  actually, ipv4-only is an upstream default.  I guess I get to poke wieste about it
[00:51] <slangasek> because I thought nothing cared about the ipv4 IP of that server anymore :)
[00:51] <cjwatson> quilt is certainly not exactly a brilliant vcs - I don't really think of it in that category
[00:51] <lamont> and lack of testing caused you marital grief?  ouch
[00:52] <slangasek> no, she's on percocet this week for wisdom tooth post-op
[00:52] <slangasek> so she's happy - I'm the one unhappy about unreliable mail ;)
[00:52] <lamont> cjwatson: the use model of dpatch that evolved into quilt was 100% around what basically amounts to a VCS.  and then I had a task of importing quilt/dpatch patches into SVN, and we discovered the pain that is gratuitous rebases
[00:52] <lamont> slangasek: when she's done being high, that's when you're in trouble... :-p
[00:53] <cjwatson> it's a patch queue, which is not quite the same as a VCS
[00:53] <lamont> cjwatson: except in how people used it
[00:53] <cjwatson> in particular it makes no pretence of being able to retrieve older versions of things (assuming you don't regard patches as static)
[00:53] <lamont> but yeah, it led to a kneejerk reaction to any sentence involving "patch system" or "quilt"
[00:54] <cjwatson> http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-03-25-thoughts-on-3.0-quilt-format.html is a summary of my initial experiences
[00:54] <cjwatson> as a historic patch-system-hater
[00:54] <lamont> ah, added point: my pain was from the debian kernel package, which _did_ endeavor to do exactly that...every past verison of the package was recoverable from the current version
[00:54]  * slangasek is reminded again that he needs to work on getting the patch delta down so he can move pam to 3.0 (quilt)
[00:54] <lamont> at least in the then-time
[00:55] <slangasek> well, that's a special case
[00:55] <slangasek> :)
[00:55] <lamont> slangasek: special in the committed sense
[00:55] <slangasek> "you need to be GPL compliant and you're doing *what*?!"
[00:56] <cjwatson> (also, the most common complaint about quilt is answered by 'quilt shell'
[00:56] <cjwatson> )
[00:58]  * ScottK is sure he'll get over it eventually, but unpacking with patches applied does not work at all well with his mental model of a package.
[01:00] <cjwatson> unpacking with patches unapplied was the reason I was a conscientious objector to patch systems. ;-)
[01:01] <cjwatson> I feel very strongly that users should not have to run funny commands (and run untrusted code from a package they just downloaded, often!) in order to see what code is going to be compiled
[02:10] <flupke> hello, what is the trick in ubuntu's alsa that makes flashplugin use pulse ? I'd like to keep this functionnality with the latest alsa drivers
[02:12] <TheMuso> flupke: As long as you don't remove/modify any files in /usr/share/alsa then it will continue to work./
[02:16] <flupke> TheMuso, thanks for the info, alsa-lib sources do write files in /usr/share/alsa, I'll try to keep the ubuntu package that owns these files
[02:18] <TheMuso> flupke: Ok. The files in hte Ubuntu package have been modifed to load an extra file which checks to see if pulse is running. If pulse is running, then the default device is created that redirects alsa apps to pulse.
[02:30] <flupke> TheMuso, works like a charm by just keeping /usr/share/alsa/alsa.conf, thanks a lot
[02:31] <TheMuso> np
[05:24] <pitti> Good morning
[05:24] <pitti> tkamppeter: hello
[05:25] <pitti> tkamppeter: I'm on an early shift this week
[05:28] <ion> Morning
[05:58] <pitti> tkamppeter: nice work on the fingerprint additions to the printing DB!
[05:58] <pitti> hey ion
[06:02] <LucidFox> If I'm making an -Xubuntu1 upload, but not going to include any of the previous Ubuntu changes, do I need to include previous Ubuntu debian/changelog entries, or can I leave in just the Debian changes?
[06:03] <micahg> LucidFox: is it currently -XubuntuY?
[06:03] <LucidFox> yes - to be more precise, it's pinta 0.3-2ubuntu1, and I'm going to upload 0.4+dfsg-1ubuntu1, which is -1 with a new patch, and the old Ubuntu changes merged upstream and dropped
[06:04] <micahg> LucidFox: so why does it need an ubuntu1 upload?
[06:04] <LucidFox> Because the Debian version is broken on Maverick as is
[06:04] <LucidFox> needs a patch for cairo 1.9.x
[06:06] <LucidFox> (for that matter, the current version in Maverick is broken too, but it wasn't discovered before Debian packaged a new release)
[06:06] <micahg> LucidFox: ah, ok, so I would think it won't hurt to keep the changelog since we're keeping an Ubuntu change
[06:06] <LucidFox> micahg> But we aren't keeping the existing Ubuntu changes, only introducing a new one
[06:06] <LucidFox> The Ubuntu changes in -2ubuntu1 were merged upstream.
[06:07] <micahg> LucidFox: right, but as long as we're carrying any changes, why not keep the history in the changelog?
[06:53] <TheMuso> c
[06:58] <didrocks> bigon: re:brasero-tracker. on it, thanks
[07:31] <dholbach> good morning
[07:31] <pitti> hey dholbach, good morning
[07:31] <dholbach> hey pitti
[07:42] <baptistemm> hi there
[07:42] <baptistemm> StevenK, around ? I would you to renew my membership to bluetooth group
[07:43] <bilalakhtar> Can someone please get https://edge.launchpad.net/ubuntu/+source/krename/4.0.4-2ubuntu1/+build/1864396 rebuilt?
[07:50] <bilalakhtar> Can someone please get https://edge.launchpad.net/ubuntu/+source/krename/4.0.4-2ubuntu1/+build/1864396 rebuilt?
[07:51] <micahg> bilalakhtar: you should ask in -motu
[07:52] <pitti> bilalakhtar: done
[07:52] <micahg> or maybe not :)
[07:52] <bilalakhtar> pitti: thanx again, apporty!
[07:52] <pitti> lol
[07:53] <pitti> that's the first time someone calls me that
[07:53] <bilalakhtar> .query pitti
[07:53] <bilalakhtar> sorry
[07:58] <tkamppeter> pitti, hi
[07:59] <tkamppeter> pitti, thanks for uploadfing the Epson key, seems that the Epson guys are firewalled out of the public key server network.
[08:02] <pitti> tkamppeter: good morning
[08:04] <tkamppeter> pitti, now the OpenPrinting web server is ready for automatic download, and it is your turn to fix/update Jockey, once to let Jockey only search and download the printer driver when a printer is detected and second, the signature support.
[08:04] <pitti> I saw the bug, thanks
[08:05] <bilalakhtar> pitti: it appears that the armel build failed again. What could be the direct solution? Package builds fine in other architectures.
[08:05] <tkamppeter> pitti, early shift? Does Canonical establish a 24/7 developer presence now?
[08:06] <pitti> tkamppeter: heh, no; I just have to get up at 6 this week, so I can just as well start early
[08:07] <pitti> tkamppeter: but given how we are distributed around the planet we have that round-the-clock coverage anyway
[09:08] <apw> i have a recently upgraded maverick system in which the cursor is being turned off after approx 1s everywhere on the screen ... like it used to do inside an gnome-terminal only
[09:08] <cjwatson> ditto
[09:09] <apw> i also think its causing a flickering cursor over gnome-terminal and menu items after approx 1s of stationaryness
[09:09] <pitti> this is from the unclutter package, I think
[09:09] <pitti> it was added right before alpha-2
[09:09] <apw> pitti, hrm ... any idea if it has any configuration?
[09:10] <pitti> no, I never used it so far; I'm still on lucid
[09:10] <apw> as it seems to be turned on without my permission
[09:10]  * pitti redirects complaints seb128wards
[09:12] <cjwatson> for me it mostly causes a problem in evince, where it spikes CPU activity
[09:12] <cjwatson> which is bug 385034 I guess
[09:13] <pitti> hm, I'm on lucid, no unclutter, and the mouse cursor still disappears in gnome-terminal after some seconds
[09:13] <pitti> (which is good IMHO)
[09:13] <apw> cjwatson, confirmed ... killall unclutter sorts out the issue
[09:13] <pitti> but I'm not sure where I configured this
[09:13] <pitti> or _if_ I did
[09:13] <apw> right ... thats a default i think, but configurable.  unclutter is busted poo which is halving my battery life ... grrr
[09:13] <pitti> ah, it disappears as soon as I start typing in a terminal
[09:14] <pitti> apw: it might just have been an experiment; I think there were more complaints
[09:14]  * pitti summons seb128
[09:14] <cjwatson> adding -noevents to /etc/default/unclutter gets rid of the flicker
[09:14] <cjwatson> (EXTRA_OPTS)
[09:15] <apw> cjwatson, eah i see that mentioned in the bug ... hrm
[09:15] <apw> i want to know how to configure it, as turnign off my mouse cursor everywhere is new behaviour i may not want
[09:16] <cjwatson> man unclutter
[09:33] <apw> cjwatson, current install is utter garbage ... joy
[09:33] <apw> plymouth is triggering a kernel panic
[09:35] <cjwatson> apw: on mode switch?
[09:35] <cjwatson> or on something else?
[09:35] <apw> cjwatson, looks to be closing something, the framebuffer from the stack trace ... so perhaps when its quitting
[09:36] <apw> removing splash sorts it out
[09:36] <cjwatson> but kernel bug rather than X bug?
[09:36] <apw> cjwatson, yep kernel should never panic :)
[09:37] <cjwatson> ... that's what I thought
[09:37] <cjwatson> was it triggered by GRUB starting the kernel in graphics mode?
[09:37] <apw> cjwatson, no this is a vanilla grub
[09:39] <cjwatson> apw: https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/030995.html
[09:39] <cjwatson> if it's 1.98+20100710-1ubuntu1, it may be starting in graphics mode by itself
[09:40] <apw> ahh i see, i susepct the issue is not grubs fault though.  the panic is pretty severe, using this mutex the one at 0, bang
[09:46] <pitti> seb128: good morning
[09:46] <pitti> seb128: cjwatson and apw have some problems with unclutter
[09:47] <seb128> like flickering and cpu use?
[09:47] <apw> seb128, i would describe it as wholy broken :/
[09:47] <apw> yep and eating my battery yes
[09:47] <pitti> seb128: at least in gnome-terminalaand gedit the mouse cursor already disappears when typing; this is on lucid without unclutter; shouldn't this be enough?
[09:48] <seb128> https://launchpad.net/bugs/16492
[09:48] <seb128> comment on this bug
[09:48] <pitti> will do
[09:48] <seb128> don't blame the messenger, I don't agree with the change but it was a sabdfl request
[09:48] <seb128> basically
[09:49] <apw> seb128, so is someone going to fix the fact it eats ones machine ?
[09:49] <cjwatson> I don't particularly care about the change as such, FWIW
[09:49] <cjwatson> it's only the implementation problems
[09:49] <apw> even if we ignore the fact its a rather gratuitous change without a graphical ticky to turn it off
[09:50] <seb128> apw, I guess we will either fix it or roll it out of the default installation
[09:50] <seb128> depending of the ressources we have to fix issues
[09:50] <seb128> but it's nice to have feedback and know about its issues to start
[09:50] <apw> well its a very severe effect, it halves my battery life
[09:50] <seb128> I can't confirm that
[09:50] <pitti> seb128: subscribed and commented, thanks for the pointer
[09:50] <apw> do you not see it on your maverick installs ?  which of course all your machines should be by now
[09:50] <seb128> pitti, you can install it on lucid btw
[09:50] <seb128> pitti, if you want to test
[09:51] <pitti> sure, but I'm actually quite happy as it is now
[09:51] <seb128> apw, no, my laptop and mini don't have that issue
[09:51] <pitti> I could install it to test flicker/battery life, sure
[09:51] <seb128> apw, they both are intel boxes though if that makes any difference
[09:51]  * apw wonders how that can be
[09:51] <apw> seb128, mini ?  mini 10v ?
[09:52] <seb128> yes
[09:52] <apw> seb128, on my mini10v i am seeing 500 wakeups per second with 100% occupancy of max MHZ, which all stops when i hit killall unclutter
[09:53] <seb128> well to be fair I don't watch battery use
[09:53] <seb128> and that box doesn't have a fan to tell you there is something eating cpu
[09:53] <seb128> but I don't notice flickering
[09:53] <apw> the flickering over gnome-terminal is impossible to miss.  i also see it on menu items after 1 sec
[09:53] <seb128> how do you see the wakeups?
[09:53] <apw> powertop
[09:53] <apw> it appears as rescheduling interrupts
[09:53] <seb128> well no flickering there
[09:54] <apw> do yo uhave the degfault config for unclutter?  -noevents is slated to fix it
[09:54] <cjwatson> seb128: I don't use gnome-terminal, but I noticed flickering in evince
[09:54] <seb128> https://bugs.edge.launchpad.net/ubuntu/+source/unclutter/+bug/385034
[09:54] <cjwatson> yes, I found that bug during this discussion today, see scrollback
[09:54] <apw> yep thats sounds like the bug
[09:55] <cjwatson> ah, I guess you joined after that
[09:55] <seb128> right
[09:55] <cjwatson> and that option does indeed work around that problem, as I also said in scrollback
[09:55] <seb128> it doesn't happen to everybody for sure and I can't confirm it there
[09:55] <seb128> but it might be trigger by some external factor or other running software
[09:57] <apw> ok
[09:57] <apw> so does one
[09:57] <apw>  o
[09:57] <apw> f
[09:57] <apw> of the affected users need to fix it then?
[09:59] <seb128> apw, I will try to debug a bit but could be something we can work on next week during the sprint
[09:59]  * apw takes his test box off his keyboard :(
[09:59] <apw> seb128, ok
[10:00] <apw> cirtianly i can reproduce it at will with a gnome-terminal, as i can use that to run the two options and show the difference
[10:00] <seb128> apw, did that start today?
[10:00] <seb128> we have unclutter on since before alpha2
[10:01] <seb128> I'm wondering if something triggered the issue for people who didn't have it before
[10:01] <seb128> I've no upgraded yet today so maybe it will start being buggy as well after updates ;-)
[10:02] <cjwatson> I noticed it a couple of days ago, I think
[10:04] <apw> seb128, this machine was updated to maverick this morning, so all new to it
[10:10] <DreadKnight> i get some lame internet laging in 10.10
[10:10] <DreadKnight> it occurs often
[10:13] <crankyadmin> Hey, does anybody have any idea when Ruby1.9 will become default in 10.04 LTS?
[10:15] <dupondje> dholbach: https://bugs.launchpad.net/ubuntu/+source/pybootchartgui/+bug/596475 -> it does have the change from -3 ?!
[10:15] <dholbach> dupondje: http://launchpadlibrarian.net/50625726/pybootchartgui.debdiff
[10:15] <dholbach> dupondje: not in the changelog - it does not apply
[10:18] <dupondje> ah the changelog indeed :) tought the change in the code :)
[10:18] <dupondje> wasn't clear :)
[10:42]  * mvo stares at pyhon-support and wishes it would be less silly. why - oh why - does it try to byte-compile gnome-codec-install on python2.4
[11:00] <geser> is there a reason that sync requests are processed slowly in the recent days?
[11:01] <tumbleweed> geser: ack-sync them yourself?
[11:05] <Laney> I've noticed this actually
[11:07] <geser> tumbleweed: if it's expected now that we upload our syncs now oneself, I can do it, but isn't the syncpackage script is some "grey zone"? It works but the archive admins prefer not to see it used.
[11:31] <BlackZ> bdrung: ping
[11:43] <tumbleweed> geser: oh, I wasn't aware of that - I've been using it
[13:48] <Kano> hi, when will http://packages.ubuntu.com/ work for maverick?
[13:50] <geser> Kano: it's in the work, the hard part is to find someone who has access to it
[13:50] <Kano> also when will libdrm 2.4.21 be in maverick? thats required for libva for intel
[13:51] <Kano> you can update nouveau too then
[13:52] <geser> Kano: if you don't get here an answer, try asking in #ubuntu-x
[13:52] <dholbach> shadeslayer, dpm, Riddell, Laney: ready for later on?
[13:53] <shadeslayer> dholbach: go go UDW :D
[13:53]  * shadeslayer just started on notes
[13:53] <Laney> somewhat!
[13:53] <dholbach> :-)
[13:53] <dholbach> awesome - I' m so looking forward to it
[13:53] <dpm> dholbach, not yet, but I'll be! :-)
[13:54] <shadeslayer> dholbach: you didnt ping Rhonda :P ... well.. shes not here anyways :P
[13:54] <dholbach> and zyga neither :)
[13:54] <shadeslayer> yeah :D
[13:55]  * shadeslayer looks up super secret ninja links in kubuntu wiki
[14:41] <dholbach> does anybody know where this comes from?
[14:41] <dholbach>  E: Invalid Release file, no valid components
[14:41] <dholbach>  E: debootstrap failed
[14:41] <dholbach> it's with maverick's debootstrap (used by pbuilder)
[14:55] <dholbach> mvo, cjwatson: ^ do you have an idea about my question above?
[14:56] <ogra> dholbach, http proxy ?
[14:57] <ogra> or any broken local archive
[14:57] <dholbach> ara: ^ do you know which mirror it uses?
[15:02] <ara> dholbach, I am using de.
[15:03]  * ara changes to the main archive to see what happens
[15:04] <ara> ah, no, I was using the main archive
[15:05] <dholbach> hrm
[15:06] <mvo> dholbach: seems to be working for me (tm)
[15:06] <mvo> no idea what is going on
[15:07] <mvo> dholbach: if its reproducable, have you tried with --verbose
[15:07] <ara> it is me who is having the issue, I will try that
[15:14] <ara> dholbach, sudo debootstrap --verbose --variant=buildd maverick /var/chroot/maverick
[15:14] <ara>  worked just fine
[15:14] <ara> it seems to be an issue in pbuilder
[15:15] <micahg> can I please get an SRU ack for a Mozilla security upload? bug 563535
[15:15] <dholbach> ara: I hope you get a chance to work on your original problem now :-P
[15:20] <ara> dholbach, hehehe, first I need to see if their is such a bug reported in pbuilder and, if not, report it ;-P
[15:22] <jdstrand> micahg: fyi, I'm not on the ubuntu-sru team, but that bug is not formatted according to StableReleaseUpdates and therefore won't show up on their reports. perhaps I am missing something?
[15:22] <micahg> jdstrand: no, I thought we just need an ack for the ones that go through -security?
[15:23]  * micahg can format it
[15:23] <jdstrand> micahg: I have no context here. there isn't a formal policy for putting SRU material through -security. we did it in the past as an exception
[15:24] <jdstrand> micahg: if this is a regression caused by the recent tbird security update, we just fix it in -security
[15:24] <micahg> jdstrand: no, this was a problem in 3.0 release version
[15:25]  * jdstrand is still lost
[15:25] <jdstrand> maybe I am dim
[15:25] <jdstrand> micahg: this is an upstream bug?
[15:25] <micahg> jdstrand: no, this is a bug in our wrapper script that I added for 3.0 in Lucid
[15:26] <jdstrand> micahg: so that sounds like a regular SRU then. is there a pending upstream security update that you are just trying to fix along the way?
[15:26] <micahg> jdstrand: yes, 3.0.6 next week
[15:27] <jdstrand> micahg: I see. I would either format the bug so that it ends up on their radar or ask a member of the ubuntu-sru directly
[15:27] <micahg> jdstrand: k
[15:29] <dupondje> dholbach: https://bugs.launchpad.net/ubuntu/+source/pybootchartgui/+bug/596475 I attached new debdiff
[15:29] <dholbach> dupondje: I'll have a look tomorrow if nobody else beats me to it
[15:30] <dupondje> fine :)
[16:26] <bigon> the "new" version (v4) of dhcp client/server is in debian , will maverick have it? or are we still use the v3?
[16:28] <cjwatson> I guess Caesar should advise on that
[16:32] <ari-tczew> slangasek: thanks for sponsoring
[16:36] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 2 starts in 24 minutes in #ubuntu-classroom
[16:37] <doko> asac, fta: are there thunderbird-3.1 packages somewhere?
[16:37] <asac> micahg: ^^
[16:37] <fta> doko, there're use to be one in the mozilla-daily ppa, but it's staled. micahg will work on it
[16:38] <fta> doko, i'm no longer an active mozilla maintainer btw
[16:38] <doko> fta: ahh, ok
[16:41] <dholbach> zyga: ready for later on? :)
[16:49] <dholbach> Riddell: all set for later on?
[16:50] <Riddell> dholbach: yes I am now
[16:50] <dholbach> yeeehaw
[16:51] <Riddell> dholbach: people should install qt4-qmlviewer, is there a place to advertise that?
[16:51] <dholbach> Riddell: https://wiki.ubuntu.com/UbuntuDeveloperWeek/Sessions
[17:13] <micahg> doko: I'll try to have TB3.1 in the PPA this weekend
[17:52] <Caesar> bigon: there's some divergence between the Ubuntu and Debian versions of DHCP
[17:52] <Caesar> pitti has patched it in the past
[17:53] <Caesar> I'd love to see it in Maverick, but I personally dislike some of the patches that have been added in Ubuntu
[17:57] <Riddell> slangasek: you blacklisted sabayon from syncs, could you comment on bug 598380 ?
[18:10] <joaomello_> Hi guys, i want to help developing ubuntu, i know python and a little C language, where should i start?
[18:14] <arand> joaomello_: The currently ongoing ubuntu developer week might be of interest? https://wiki.ubuntu.com/UbuntuDeveloperWeek
[18:15] <joaomello_> thanks for the link
[18:25] <slangasek> Riddell: IIRC, sabayon was blacklisted because it had been removed from Debian, no?
[18:25] <Riddell> slangasek: that's what the comment says
[18:25] <slangasek> Riddell: in which case it's fine to unblacklist now that it's available again
[18:25] <slangasek> shall I go ahead and do that?
[18:26] <Riddell> slangasek: please do
[18:26] <Riddell> I'll do the sync then
[18:27] <slangasek> Riddell: blacklist updated
[18:28] <Riddell> groovy, sorted
[18:30] <mdz> neat: [ 1181.314999] chromium-browse[3502]: segfault at 42ddd671 ip 42ddd671 sp 42ddd671 error 4 in DejaVuSans.ttf[aca0a000+9b000]
[18:31] <mdz> I never saw a segfault in a font before
[18:31] <ion> heh
[18:37] <slangasek> ttx: regarding your change to samba-common.postinst - rather than throw a message telling users to copy the default smb.conf over when the file is missing, why not do this for the user?
[18:46] <ttx> slangasek: ISTR someone raised a policy argument against that solution, lemme check the bug
[18:47] <slangasek> well, the policy argument is weak :)
[18:49] <ttx> slangasek: then I misunderstood you back then: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/312449/comments/6
[18:50] <slangasek> ttx: or perhaps I'm being inconsistent!
[18:50] <ttx> slangasek: I wouldn't suggest anything like that :)
[18:55] <slangasek> ttx: tried to dig up context for that comment from me and failed.  Policy does say that local changes to config files must be preserved during a package upgrade (Policy 10.7.3), but it's debatable whether nuking the config file and rendering the package uninstallable should count...
[18:56] <slangasek> ttx: btw, is the comment accurate?  Does the install actually fail now, or does it just complete with a non-existent config?
[18:58] <slangasek> heh - it looks like 'start smbd' returns success, and then smbd dies afterwards :/
[18:58] <slangasek> darn foregrounded process supervision
[18:58] <Laney> ping re: the sync queue — looks like it hasn't been processed for a while
[18:59] <geser> Laney: looks like Riddell is processing it right now
[18:59] <Riddell> that I am
[18:59] <Laney> ah, sexy
[19:00] <Riddell> although I'm about to stop for a bit to do an exciting talk on declarative UI programming in #ubuntu-classroom
[19:00] <ttx> slangasek: it fails. The message allows for easy spot of duplicated and we have a canned response to handle those now
[19:00] <slangasek> ttx: are you sure it still fails since the conversion to upstart? :)
[19:01] <ttx> slangasek: ah
[19:01] <slangasek> because my testing says it doesn't
[19:01] <ttx> slangasek: well, no
[19:01]  * Laney does love a bit of declarative programming
[19:01] <slangasek> (and that this is a bug)
[19:01] <ttx> slangasek: you tested it more recently than I did.
[19:02] <ttx> slangasek: about context for the comment: I took it back then from one of the multiple duplicates of this bug, that's all I remember
[19:03] <slangasek> ok
[19:04] <YokoZar> could someone on Lucid with ATI open source drivers please echo $LIBGL_DRIVERS_PATH  for me
[19:04] <YokoZar> (on amd64)
[19:05]  * Laney sees 8 new LP mails :)
[19:05] <Laney> syncs be good
[19:29] <asid> hello me and my friends are 4 people in need of a project to work on, and all seem to suffer from ideas block.....we've have limited experience in using linux(but a few months time to familiarise with it) .....could you  guys suggest some ideas for  a project (perhaps a feature you want to implement in linux)
[19:33] <Laney> asid: there are many many ideas on brainstorm.ubuntu.com
[19:35] <asid> thanks for the link......am looking at it .....if you guys have any idea for a project for ppl please give suggestion
[19:41] <ari-tczew> now on maverick, update-manager shows description instead package name. is it a bug or new feature?
[19:41] <sladen> asid: thank you for your interest.  Work in Ubuntu is generally done either in response to fixing a bug report requiring the change ( https://bugs.launchpad.net/ubuntu/+bugs ), or planned via specifications
[19:43] <ari-tczew> asid: I think that you can start with Ubuntu development - syncs, merges, security updates :)
[19:46] <asid> thanks for replies.....well bug fixes really doesnt sound like an idea for a project...also we do not need it to be automatically incorporated into the next release of  Ubuntu, we just need  an idea for a  reasonably sized project to work on that could be useful in Ubuntu
[19:52] <apachelogger> pitti: ping
[20:12] <highvoltage> anyone else having trouble accessing Canonical's website?
[20:13] <apw> cjwatson, ok this is a prototype of a new approach: http://people.canonical.com/~apw/misc/fbcon-handoff2.ogv
[20:13] <ion> highvoltage: Worksforme™
[20:13] <apw> cjwatson, this one works on the assumption that the empty areas of the VT are transparent and not updated
[20:15] <ion> Looks nice
[21:12] <BlackZ> bdrung: ping
[21:18] <bdrung> BlackZ: pong
[21:19] <BlackZ> bdrung: do you have the time to look at bug #554823 ?
[21:34] <ccheney> is there a format for the preseed file documented anywhere?
[21:37] <cjwatson> ccheney: in the installation-guide
[21:37] <cjwatson> appendix b
[21:37] <ccheney> ok thanks
[22:01] <bdrung> BlackZ: slangasek already commented the merge request.
[22:03] <BlackZ> bdrung: oh, I'm not subscribed there, sorry
[22:03] <BlackZ> subscribing now
[22:03] <BlackZ> thanks slangasek
[22:17] <bdrung> BlackZ: you need to subscribe ubuntu-sponsors once address slangasek's questions
[22:20] <BlackZ> bdrung: yes, I will. I didn't see the bzr branch, sorry. However I emailed Daviey to see if he still wants to do the merge
[22:26] <hv> is the "blank screensaver" broken? if you happen to click or press a key when it starts fading to black, it does not stop.
[22:49] <ccheney> cjwatson, it keeps popping up asking me for the country, isn't that supposed to be resolved with the following?
[22:49] <ccheney>  - d-i console-setup/ask_detect boolean false
[22:49] <ccheney>  - d-i console-setup/layoutcode string us
[22:49] <ccheney> it seems to not be enough :-\
[22:50] <ccheney> and is there anything i can look at source-wise to be able to determine what i need to override if I see something like this again?
[22:51] <slangasek> country != keymap ?
[22:51] <ccheney> hmm maybe so, i see at the bottom of the docs it tells how to dump all questions that should help i suppose
[23:05] <ccheney> slangasek, i tried adding more and it still gets stuck at the question asking 'origin of the keyboard' http://pastebin.ubuntu.com/463202/
[23:06] <slangasek> ccheney: what's the source for those preseed values?  I wasn't aware that there were any keyboard layouts called 'USA'
[23:06] <slangasek> but I'm generally not current when it comes to d-i preseeding info, sorry
[23:07] <ccheney> i tried running: debconf-get-selections
[23:07] <ccheney> but perhaps i need the --installer variant which seems to not work on my box due to cdebconf being missing
[23:07]  * ccheney wonders if just installing that package would show me the needed info
[23:08] <ccheney> hmm, no
[23:08] <ccheney> debconf: DbDriver "di_questions": could not open /var/log/installer/cdebconf/questions.dat
[23:09] <ccheney> perhaps i need to run that off a cd
[23:59] <bigon> Caesar: regarding dhcpv4 it brings ipv6 support both on server side and client + in networkmanager