[10:35] <psivaa> infinity: cjwatson: Reported bug 1143999 for print server installation failures with today's images
[10:35] <ubot2`> Launchpad bug 1143999 in Ubuntu CD Images "Unmet dependancies fail to install raring print server" [Undecided,New] https://launchpad.net/bugs/1143999
[10:56] <psivaa> xnox: ^
[10:59] <xnox> psivaa: ogra and infinity were discussing colorhug falling out of main for a while and hence breaking the CDs on #ubuntu-release. Do you idle on #ubuntu-release and read the scrollback?
[11:00] <xnox> (well that's the extend to which i understood the problem)
[11:00] <ogra_> right, that broke the last live image builds
[11:06] <psivaa> xnox: for me it does not say anything conclusive, and i saw the problem in daily smoke, hence the bug
[11:09] <xnox> psivaa: ok, but release team had bells to notify about such things even before automatic daily smoke testing was in place. =)))) me ponders how we can integrate the release reports and smoke-testing together.
[11:10] <psivaa> xnox: leaving you ponder :D
[11:11] <xnox> =))))))))))
[11:11] <xnox> thanks.
[11:11] <psivaa> :)
[11:12] <xnox> ogra_: was colorhug bug on http://people.canonical.com/~ubuntu-archive/testing/raring_probs.html when it was present or only in component missmatches?
[11:13] <ogra_> no idea, adam looked deeper into it, i only noticed the missing dep
[12:15] <infinity> xnox: It would have shown on raring_probs, yeah.
[12:19] <xnox> infinity: right so QA are automatically testing instability of the default tasks from the images (not sure if it's with or without network connectivity), such that if those are in raring_probs as well, they will fail and QA come running to pester us.
[12:19] <infinity> xnox: Yeah, we have some points of overlap in QA there obviously, and timing is everything.
[12:20] <infinity> Not that I mind redundant QA.  At least things are less likely to be missed.
[12:20] <infinity> And lord knows QA has never been our strongest suit, so the more, the merrier.
[12:20] <xnox> infinity: now the question is: should we make raring_probs go away and never be visible, or should we make jenkins jobs to depends on "raring_probs.html is clean" and/or go into amber state if there are raring_probs.
[12:21] <infinity> xnox: I'd rather probs didn't go away, cause it's far more readable for me than jenkins output.
[12:21] <xnox> by "go away" i mean "always display a beer mug"
[12:21] <xnox> =)
[12:21] <infinity> But making jenkins realize that if something's showing up in probs or component-mismatches, that it's a known issue that doesn't need a bug, that could be useful.
[12:22] <infinity> Closing the bug didn't exactly take effort either, though, so whatever.
[12:22] <xnox> infinity: cuase yeah, I don't think filing bugs is most productive use of qa & release engineering time.
[12:22] <infinity> I've spent more time talking about it than I did dealing with it. :P
[12:22] <xnox> but it's not the first bug of this kind ;-)
[13:34] <xnox> cjwatson: there are two "chinese timezones bugs": one cannot set beijing at the timezone map, the other kylin wants to preseed timezone map step. Did you have a chance to look at the latter? If now, what where your thoughts and I guess I can poke it.
[13:45] <cjwatson> xnox: I haven't had a chance to attack the latter problem yet, but I still consider it on my plate
[13:47] <xnox> cjwatson: ok. I will be looking at the former in a bit again.
[15:05] <|Frederik> Is an installation with LVM and ecryption in uefi mode supported? With 12.10 desktop installer, my system refuses to boot from the installed system. with 13.04 daily image, it fails early in the installation process.
[15:07] <xnox> |Frederik: it is meant to work, but I haven't had a chance to test it in uefi mode yet. My uefi/sb capable desktop arrives at the end of this week.