User1: User2 mesa's in New on all 4 archs now....
User2: User1 got it
User1: Thanks.
User2: User1 accepted now; sorry, got held up rejecting pacemaker
User1: User2 Thanks.
User3: skaet, when is the freeze going into effect for RC ?
User3: (and hi!)
User4: User3 FinalFreeze is tomorrow
User3: robbiew, so at midnight tonight local we freeze ?
User3: (go into freeze mode)
User4: User3 ah...well, technically yes
User3: robbiew, ok thats what i needed to know ... thanks
User4: User3 np
User3: robbiew, fyi people are saying netbook is throwing a white screen and is unusble, over on #ubuntu-devel
User4: User3 I think the latest mesa update broke it
User2: User4 broke what?  the freeze?
User4: User2 broke clutter
User2: hmm
User2: certainly possible... what hardware do people see this on?
User4: User2 I think conversations are being held on #ubuntu-x
User4: User2 jump to #ubuntu-x
User2: User6 I'm puzzled by the ubuntu release notes task on bug #552613 - what's to be release-noted?
User5: 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
User6: User2 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?
User6: slangsek:  agree that nothing needs to be documented in release notes on this.   Its a kludge.
User2: User6 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 :)
User2: User6 I would suggest using the 'later' milestone
User2: which exists for this purpose, though we are perhaps not as diligent as we should be in revisiting such issues after a release
User4: User2 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 :/
User2: ah, k :)
User6: User2  is the 'later' milestone documented somewhere?
User2: User6 heh, probably not; I look to cjwatson for that precedent
 * skaet wants to check she understands the semantics of when it should be used.
User6: User2  will follow up with cjwatson then when see him next ;)
User7: User6 when we're gonna fix the bug "later"... it comes from warty days, when lots and lots of things were "yeah, yeah... NOT NOW"
User7: but never really used like it could/should be, IMO
User6: :)
User2: I think "later" is "when I get to the bottom of my todo list, I'll revisit"... 'nuf said
User8: 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?
User8: i'm trying to install to a two disk raid
User8: i'm getting "grub-install /dev/sda" failed however I don't believe I have a '/dev/sda'
User8: this is with maverick server amd64, today's iso
User9: good to see all the buildd
User9: ... buildds blocked by mozilla-security ...
User10: User6 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
User10: contrary to what lamont said, my memory is that the later milestone was invented in the edgy cycle
User10: 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
User6: User10  thanks.   an empty natty distroseries is what I was hoping for initially as well.
User10: anyway, the semantics are "should be revisited after release and probably attached to the next series"
User10: or thus I remember them being anyway
User10: User8 not known, could do with a report with full logs
User6: 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.
User8: User10 it's from an iso install, how do I get logs?
User8: User10 note, i successfully installed to this same configuration some time ago, am trying an older iso
User10: User8 text mode or graphical?
User8: User10 it's server, so text mode
User10: User8 go back to the main menu and select "save debug logs"
User8: User10 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
User10: it could be related to the change in grub2 1.98+20100804-4ubuntu6
User10: I haven't done a RAID test since then
User8: User10 an install using the daily server iso from 09/05/2010 worked
User8: User10 that's Sep. 05 :-)
User6: User10  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.
User8: User10 am happy to try a dist-upgrade, anything special you'd like me to do?
User10: User8 a log from the current CD image would probably be better-controlled and easier to read
User10: with the current CD image, put DEBCONF_DEBUG=developer on the kernel command line
User10: User6 *nod*
User11: 26
User8: User10 so a new install of the sept. 05 iso with DEBCONF_DEBUG=developer on the kernel command line?
User10: no, current iso
User10: unless that's a problem for you
User8: User10 no problem, just want to get you what you want
User10: User11 42
User11: User10 101010
User8: User10 so today's iso it is
User10: dear archive admins who might think of processing NBS: please don't remove the -21 kernel, we're still using it
User10: (done the things that can easily be done right now)
 * slangasek acks
User8: User10 where will the logs be?
User8: User10 am installing now
User10: User8 "save debug logs" from the main menu will show them
User8: User10 ok
User10: User8 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
User10: those are the two I actually need
User7: User10 edgy, warty, 'tever... something ending in a 'y' :-)
User7: take my comment to be "a long time ago"
User9: User7 see bug #630511 :-/
User5: 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
User7: User9 was getting to that one
User9: I can work around it, but the main problems are the undiscovered things
User7: User9 when building for release N, the *^%&*)%)^(^_) package should really not query the underlying kernel to decide what code it should generate.
User9: User7 you're dreaming, how do you intent to face reality?
User7: 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?
User8: User10 i'm trying to get you the logs, cant switch to vt2 or any vt at this point
User9: 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?
User8: User10 am booting from a usb key, is that mounted such that I can write the logs back to it?
User8: User10 nevermind, put the files onto another usb disk
ubuntu-release
Ubuntu IRC