[01:03] <ScottK> slangasek: mesa's in New on all 4 archs now....
[01:03] <slangasek> ScottK: got it
[01:03] <ScottK> Thanks.
[01:54] <slangasek> ScottK: accepted now; sorry, got held up rejecting pacemaker
[02:12] <ScottK> slangasek: Thanks.
[15:40] <apw> skaet, when is the freeze going into effect for RC ?
[15:41] <apw> (and hi!)
[15:42] <robbiew> apw: FinalFreeze is tomorrow
[15:43] <apw> robbiew, so at midnight tonight local we freeze ?
[15:43] <apw> (go into freeze mode)
[15:43] <robbiew> apw: ah...well, technically yes
[15:43] <apw> robbiew, ok thats what i needed to know ... thanks
[15:43] <robbiew> apw: np
[16:22] <apw> robbiew, fyi people are saying netbook is throwing a white screen and is unusble, over on #ubuntu-devel
[16:22] <robbiew> apw: I think the latest mesa update broke it
[17:14] <slangasek> robbiew: broke what?  the freeze?
[17:15] <robbiew> slangasek: broke clutter
[17:16] <slangasek> hmm
[17:16] <slangasek> certainly possible... what hardware do people see this on?
[17:16] <robbiew> slangasek: I think conversations are being held on #ubuntu-x
[17:16] <robbiew> slangasek: jump to #ubuntu-x
[19:45] <slangasek> skaet: I'm puzzled by the ubuntu release notes task on bug #552613 - what's to be release-noted?
[19:45] <ubot4> Launchpad bug 552613 in xmlbeans (Ubuntu Maverick) (and 4 other projects) "[MIR] xmlbeans (affects: 1) (heat: 10)" [Wishlist,Won't fix] https://launchpad.net/bugs/552613
[20:04] <skaet> slangasek: noted from bug it should be revisted for Natty, but when asked how to flag it so it doesn't disappear into morass, was advised to flag it to release notes as mechanism to use as workaround.  Intuitively I was hoping for a release class of "future" or "Natty" to tag it against.   Better suggestion?
[20:05] <skaet> slangsek:  agree that nothing needs to be documented in release notes on this.   Its a kludge.
[20:05] <slangasek> skaet: huh, who told you to use /that/ as a workaround :P  the release-notes project is used for tracking actual pending issues in the release notes, I would've closed this bug as invalid if I had come across it doing release notes work :)
[20:05] <slangasek> skaet: I would suggest using the 'later' milestone
[20:05] <slangasek> which exists for this purpose, though we are perhaps not as diligent as we should be in revisiting such issues after a release
[20:09] <robbiew> slangasek: I told her to subscribe release notes,  but I assumed it was a bug that we wouldn't be able to address in 10.10...not a Wishlist,Won't fix issue :/
[20:10] <slangasek> ah, k :)
[20:10] <skaet> slangasek:  is the 'later' milestone documented somewhere?
[20:10] <slangasek> skaet: heh, probably not; I look to cjwatson for that precedent
[20:11]  * skaet wants to check she understands the semantics of when it should be used.   
[20:12] <skaet> slangasek:  will follow up with cjwatson then when see him next ;)
[20:12] <lamont> skaet: when we're gonna fix the bug "later"... it comes from warty days, when lots and lots of things were "yeah, yeah... NOT NOW"
[20:13] <lamont> but never really used like it could/should be, IMO
[20:16] <skaet> :)
[20:19] <slangasek> I think "later" is "when I get to the bottom of my todo list, I'll revisit"... 'nuf said
[20:54] <bjf> i'm having an issue with grub-pc not installing (both a dist-upgrade and now an install from iso) is this a know issue?
[20:55] <bjf> i'm trying to install to a two disk raid
[20:58] <bjf> i'm getting "grub-install /dev/sda" failed however I don't believe I have a '/dev/sda'
[20:59] <bjf> this is with maverick server amd64, today's iso
[21:26] <doko> good to see all the buildd
[21:26] <doko> ... buildds blocked by mozilla-security ...
[22:04] <cjwatson> skaet: I'm not sure it's documented unfortunately.  It exists as a milestone due to LP limitations - ideally we'd just create an empty natty distroseries and start targeting bugs to it, but unfortunately LP gets a bit confused if you try that
[22:05] <cjwatson> contrary to what lamont said, my memory is that the later milestone was invented in the edgy cycle
[22:06] <cjwatson> indeed you can tell this from the fact that it's attached to the edgy distroseries (the namespace for milestones within a distribution is flat): https://launchpad.net/ubuntu/edgy/+milestones
[22:06] <skaet> cjwatson:  thanks.   an empty natty distroseries is what I was hoping for initially as well.
[22:06] <cjwatson> anyway, the semantics are "should be revisited after release and probably attached to the next series"
[22:06] <cjwatson> or thus I remember them being anyway
[22:06] <cjwatson> bjf: not known, could do with a report with full logs
[22:07] <skaet> yup,  I was looking through that earlier today.    There's alot of cruft in the later queue that should probably be cleared out if we're going to start using it as the "next release"  in a standard fashion though.
[22:07] <bjf> cjwatson: it's from an iso install, how do I get logs?
[22:08] <bjf> cjwatson: note, i successfully installed to this same configuration some time ago, am trying an older iso
[22:12] <cjwatson> bjf: text mode or graphical?
[22:12] <bjf> cjwatson: it's server, so text mode
[22:13] <cjwatson> bjf: go back to the main menu and select "save debug logs"
[22:13] <bjf> cjwatson: ok, am in the middle of an install now, will do if I have the same problem, if I don't I'll go the dist-upgrade route and hit it again
[22:15] <cjwatson> it could be related to the change in grub2 1.98+20100804-4ubuntu6
[22:15] <cjwatson> I haven't done a RAID test since then
[22:24] <bjf> cjwatson: an install using the daily server iso from 09/05/2010 worked
[22:27] <bjf> cjwatson: that's Sep. 05 :-)
[22:28] <skaet> cjwatson:  thanks. will use the semantics as the working definition for now.  :)   Have added it to list of topics to revisit a bit after release is out, to get it a little more standardized and integrated into the processes.
[22:29] <bjf> cjwatson: am happy to try a dist-upgrade, anything special you'd like me to do?
[22:34] <cjwatson> bjf: a log from the current CD image would probably be better-controlled and easier to read
[22:34] <cjwatson> with the current CD image, put DEBCONF_DEBUG=developer on the kernel command line
[22:34] <cjwatson> skaet: *nod*
[22:34] <nigelb> 26
[22:36] <bjf> cjwatson: so a new install of the sept. 05 iso with DEBCONF_DEBUG=developer on the kernel command line?
[22:37] <cjwatson> no, current iso
[22:37] <cjwatson> unless that's a problem for you
[22:37] <bjf> cjwatson: no problem, just want to get you what you want
[22:37] <cjwatson> nigelb: 42
[22:37] <nigelb> cjwatson: 101010
[22:37] <bjf> cjwatson: so today's iso it is
[22:49] <cjwatson> dear archive admins who might think of processing NBS: please don't remove the -21 kernel, we're still using it
[22:52] <cjwatson> (done the things that can easily be done right now)
[22:53]  * slangasek acks
[22:55] <bjf> cjwatson: where will the logs be?
[22:55] <bjf> cjwatson: am installing now
[22:55] <cjwatson> bjf: "save debug logs" from the main menu will show them
[22:55] <bjf> cjwatson: ok
[22:56] <cjwatson> bjf: or you can switch to tty2, run 'anna-install openssh-client-udeb', then use scp to copy out /var/log/syslog and /var/log/partman
[22:56] <cjwatson> those are the two I actually need
[23:31] <lamont> cjwatson: edgy, warty, 'tever... something ending in a 'y' :-)
[23:32] <lamont> take my comment to be "a long time ago"
[23:49] <doko> lamont: see bug #630511 :-/
[23:49] <ubot4> Launchpad bug 630511 in python3.1 (Ubuntu Maverick) (and 2 other projects) "Support for multiprocessing broken in python3.1 (affects: 1) (heat: 8)" [Critical,Triaged] https://launchpad.net/bugs/630511
[23:50] <lamont> doko: was getting to that one
[23:51] <doko> I can work around it, but the main problems are the undiscovered things
[23:52] <lamont> doko: when building for release N, the *^%&*)%)^(^_) package should really not query the underlying kernel to decide what code it should generate.
[23:53] <doko> lamont: you're dreaming, how do you intent to face reality?
[23:53] <lamont> given that I have no way to run other than one kernel to build all of the distroarchseries, which one would you prefer me to break?
[23:54] <bjf> cjwatson: i'm trying to get you the logs, cant switch to vt2 or any vt at this point
[23:54] <doko> I assume that running the N-1 kernel would make things better. Can we discuss this / start a blueprint about this with the soyuz guys at UDS?
[23:54] <bjf> cjwatson: am booting from a usb key, is that mounted such that I can write the logs back to it?
[23:59] <bjf> cjwatson: nevermind, put the files onto another usb disk