[08:32] <flocculant> zequence: I did a couple of tests for you
[08:33] <flocculant> won't manage anymore today though
[08:43] <zequence> flocculant: I saw that. Thanks a bunch.
[08:43] <flocculant> welcome
[08:43] <zequence> Ross is helping out too. I'm just installing on a real machine for a change
[08:43] <flocculant> always useful :)
[09:40] <zequence> I'm not having much luck with paritioning, actually
[09:40] <zequence> Not able to use an existing partition, or delete an existing one and create a new one, so that the installation can go past "Creating ext4 file system..."
[09:42] <zequence> I have 4 logical partitions
[10:00] <zequence> Something a little buggy with the partioner. Created a primary partition, which ended up being called sd8
[10:01] <zequence> And, still can't get passed creating ext4 file system. Thinking that if I did a erase everything install it would work (usually does). I have installed 15.10 on this machine before. hmm
[10:03] <flocculant> zequence: I've not seen issues like that lately
[10:03] <flocculant> 32 or 64 bit?
[10:03] <zequence> 64bit. I
[10:04] <zequence> I'm doing a manual partitioning with gparted now
[10:04] <flocculant> I'll get a stick sorted and try here
[10:04] <zequence> This could be an issue with previous partioning and partitioning tables
[10:05] <zequence> When opening gparted, it talkes about cylinder sizes, and that for me usually means I need to reboot in order for things to be read correctly
[10:05] <zequence> gparted got stuck too
[10:06] <flocculant> and where you trying to use an old partition?
[10:06] <zequence> Well, both. But, it is the same old partition table
[10:07] <zequence> So, may be hard to reproduce this. This is a pre-UEFI laptop with one primary partition that originally had 4 logical partitions. Now, 3.
[10:07] <zequence> hmm, gparted pulled through eventually. Just took a while
[10:08] <zequence> Going to try installing without formatting this time
[10:08] <zequence> ..since it's now freshly formatted
[10:08] <flocculant> yep
[10:08] <flocculant> well if you get it to work I'll abort
[10:10] <zequence> The partioner wants to write changes though I haven't actually made any changes (use sd8 as ext for and assign / to it, but no formatting, or change in size)
[10:10] <zequence> That has happened to me a lot in recent years, so I suspect that is a bug too, but it usually doesn't stop me from installing
[10:11] <zequence> ext4, not "ext for"
[10:12] <zequence> Well, this worked
[10:12] <zequence> So, before next LTS, might be a good idea to do some partitioning testing to try to dig up some bugs that need to be fixed
[10:13] <flocculant> yep
[10:14] <flocculant> obviously the trouble with that is getting people to test as early as possible
[10:14] <zequence> A lot of disk partion editing tools seem to have some problems lately, something to do with gpt I think, from now knowing at all what happens under the hood
[10:15] <flocculant> I'd assume so - don't have any gpt disks here
[10:15] <zequence> This should not be a gpt disk, but probably newer installations might default to it. At least you need it for disks past 2TB sizes
[10:15] <flocculant> yep
[10:16] <flocculant> buying a new disk soonish - will be making sure max 2Gb :p
[10:16] <zequence> haha
[10:16] <flocculant> will scratch my head over gpt when I need to - not before :p
[10:25] <flocculant> zequence: well it appeared to not have any trouble with partitions here
[10:26] <zequence> flocculant: Ok
[10:26] <flocculant> perhaps report it as a bug - you can at least then link it on your release notes
[10:26] <flocculant> I put one on ours that one person reported that's not been confirmed yet too
[10:27] <zequence> I'm not sure yet which is what. Could be my hard drive is getting sick
[10:27] <flocculant> yep
[13:43] <gb3700> _@
[15:00] <slickymasterWork> reviewing now flexiondotorg
[15:00] <slickymasterWork> ups, I meant flocculant :P
[15:01] <flocculant> thanks - should be pretty straight forward
[15:01] <flocculant> I can do the merging and packages.qa updates then get on with the other load
[15:33] <flocculant> balloons: you might think it's early, but can you get xenial added to packages.qa.ubuntu.com asap - we're going to be pushing package testing pdq ;)
[15:34] <balloons> flocculant, sure thing
[15:34] <balloons> I'll add the release if you want to migrate things over :-)
[15:37] <balloons> http://packages.qa.ubuntu.com/qatracker/milestones/350/builds
[15:45] <flocculant> balloons: awesome - thanks :D
[15:49] <flocculant> wish they could be weighted though :p
[15:49] <flocculant> have to jiggery pokery with testsuite names it seems
[15:49] <flocculant> that bit's set up at least \o/
[15:50] <flocculant> balloons: so it seemed that ecploratory didn't work too well - so we're trying both this time
[15:52] <slickymasterWork> flocculant. https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1508808/+merge/275364
[15:52] <slickymasterWork> all done
[15:53] <flocculant> slickymasterWork: thanks slickymasterWork
[15:54] <slickymasterWork> sure
[16:02] <flocculant> that's the priority stuff for us done and ready to roll :)
[17:31] <tsimonq2> when are the first Xenial images gonna be released?
[17:31] <tsimonq2> few weeks?
[17:32] <teward> i don't even think the Xenial archive is open yet
[17:33] <tsimonq2> hmm
[17:33] <tsimonq2> so what now for Wily?
[17:33] <teward> * Topic for #ubuntu-devel is: Wily (15.10) Released! | Archive: closed   Topic for #ubuntu-release is: Released: Trusty 14.04.3, Wily 15.10 | Archive: closed, britney block in place
[17:33] <teward> so yeah, archive ain't open perhaps
[17:34] <tsimonq2> so wait...are we just waiting for terrible bugs now?
[17:34]  * teward shrugs
[17:34] <teward> i'm on standby for what I expect to be a flurry of nginx bugs appearing
[17:34] <tsimonq2> well then where do I ask?
[17:34] <teward> ('cause server person here :P)
[17:35] <teward> tsimonq2: here, maybe in -release
[17:35] <teward> but i'd say 'don't expect it immediately', and 'give it a little bit'
[17:35] <tsimonq2> ok
[17:35] <teward> with today being release day it's one of those "prepare for hell many will probably report bugs" days, I think
[17:36] <tsimonq2> oh gawd
[17:37]  * tsimonq2 pats teward on the back
[17:37] <tsimonq2> good luck, buddy
[17:37] <teward> heheheh
[17:37] <teward> i have a limited package scope
[17:37] <teward> and most of the issues in Vivid on upgrade for nginx were configuration errors, not package issues
[17:37] <teward> :P
[17:37] <teward> but I digress
[17:37]  * teward waits for the flood
[17:38] <flocculant> tsimonq2: turns up when it turns up