[00:07] <cjwatson> infinity: I've implemented (hopefully) more correct partial suite merging in britney2; that allowed 11 extra sources to migrate, including the qapt transition
[00:08] <cjwatson> infinity: opal/ptlib is blocked by t38modem
[00:09] <cjwatson> infinity: (which may be just a rebuild; I haven't checked)
[00:11] <cjwatson> infinity: I suspect that this will result in various binaries appearing in NBS for raring with everything magically green and ready to remove; if that's the case, feel free to remove them but I'd appreciate a note of what you removed just this once to confirm my theory
[00:20] <cjwatson> (that probably goes for everyone, but I wanted specific handoff since I'll be sleeping shortly and then travelling)
[00:24] <slangasek> cjwatson: before you go, any thoughts on my question on #ubuntu-devel, before I start changing the section of packages in raring,p/q-proposed/updates?
[00:26] <cjwatson> let me catch up over there ...
[00:36] <jbicha> oh, so we're trying to avoid nbs from even entering ubuntu+1?
[00:39] <jbicha> I kind of need something like http://people.canonical.com/~ubuntu-archive/nbs.html to help track those
[00:40] <cjwatson> yes, a raring-proposed version of the NBS tracker is on the known list
[00:41] <cjwatson> I asked Ursinha-afk to take a pass through ubuntu-archive-tools and fix up anything remaining that needs adjustments for -proposed (some will just need to be flipped over, while some may need two versions, and some may need something more sophisticated)
[00:41] <cjwatson> jbicha: however, in the meantime, you can track them in http://people.canonical.com/~ubuntu-archive/proposed-migration/ once you get used to the output format
[01:12] <cjwatson> infinity: ignore previous comment about NBS; I've confirmed and processed the output now
[01:24] <infinity> cjwatson: t38modem is porting, not a rebuild, I'll poke at it later.
[01:26] <infinity> jbicha: Yeah, the plan is to make transitions happen in -proposed, except for wildly exceptional circumstances.  And, in general, if you think your circumstance is exceptional, it's probably not.
[01:27] <jbicha> infinity: it looks like all of the other ptlib/opal rdepends are fine with just a rebuild
[01:27] <infinity> jbicha: I already did everything else.
[01:27] <infinity> jbicha: Keep up. ;)
[01:27] <infinity> jbicha: t38modem is all that's left, and I have it half done here.
[01:33] <jbicha> infinity: oh, well cool then
=== gridcube_ is now known as GridCube
=== smartboyhw_ is now known as smartboyhw
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
[16:33]  * stgraber copies whopsie, apport, nux and compiz from quantal-updates to raring-proposed as those weren't uploaded or copied to the dev release (or were 0-day SRUs)
[16:35] <stgraber> my quick check for packages in dev release being older than those in the -updates pocket of stable release for a standard desktop install also detected firefox and thunderbird, but those two are already in raring-proposed, they're just failling to build on non-x86...
[17:28] <xnox> I don't know if something is blocked, but dailies are currently only generated for omap4 and amd64-mac =)
[17:29] <stgraber> i386 gives empty logs and I've seen some amd64 failures in my mails. I was assuming that something was wrong with the i386 build chroot but didn't investigate more as I don't quite need a working daily yet :)
[17:30] <xnox> ack. =) I want a working daily =)
[17:33] <stgraber> hmm, no useful log for i386... I'll kick a manual build of the i386 livefs and see if I can get something
[17:33] <stgraber> ok, it's failling immediately with "No valid suites to build for"
[17:37] <stgraber> so I guess that confirms my theory that something's broken on cardamom with the i386 build chroot for raring as that error message appears to come from the build server. Not much I can do myself to fix that sadly.
[18:20] <slangasek> infinity: ^^ is the broken build env on cardamom for livefses something you can help with?
[20:13] <slangasek> mdeslaur: hey, why is munin in quantal-proposed with no bugs referenced in the changelog?  Is this something you're gathering feedback on out-of-band before copying to -security?
[20:13] <mdeslaur> slangasek: yes
[20:13] <slangasek> mdeslaur: ok, just making sure
[20:13] <mdeslaur> slangasek: It's going to be published in -security this week
[20:13] <mdeslaur> slangasek: thanks
[20:36] <infinity> stgraber / slangasek: I still have an open ticket for livefs chroots.  Not much that can be done on the weekend.
[20:39] <slangasek> infinity: ah, didn't know there was one open already - thanks
[20:39] <slangasek> is that a "chroots not created yet" issue?
[20:39] <infinity> slangasek: Aye.
[20:39]  * slangasek nods
[20:40] <infinity> I'll poke Haw when he's around and see how dreadfully busy he is.
[20:40] <slangasek> this nexus7 is frustrating; I didn't realize the extent to which my dvorak muscle memory failed to translate to hunt-n-peck for onscreen keyboards
[20:40] <slangasek> and onboard cleverly uses the configured keyboard map... so I have to pick my poison
[20:41] <infinity> Switch to Dvorak on your Android phone, too, and let the problem work itself out over the next week of pain?
[20:42] <slangasek> swype doesn't support dvorak
[20:42] <slangasek> at least, not last I looked
[20:43] <infinity> Yeah, the only keyboard I have installed that speaks Dvorak is Hacker's Keyboard, but it doesn't do swipey things.
[20:44] <stgraber> I just gave up and plugged a physical keyboard to the tablet, I can't get used to typing more than 10 words on an onscreen keyboard
[20:45] <maxb> ... and I thought my problems dealing with moving between US and UK QWERTY layouts were bad ... this conversation is giving me perspective :-)
[20:45] <slangasek> stgraber: OTG FTW :)
[20:45] <infinity> stgraber: It's weird.  I finally got used to typing on phones (and am quite fast at it), but I find tablet keyboards just entirely the wrong combination of form factor and onscreeniness to be usable.
[20:45] <stgraber> yep and we even got that nice OTG to host adapter with the tablet ;)
[20:46] <slangasek> maxb: heh, uk<->us is probably harder because of the similarity, the qwerty and dvorak maps are at least stored separately in my brain so that there's a clean switch between them... I just don't have any corresponding dvorak hunt'n'peck because the issue has never come up :)
[20:46] <infinity> (And this isn't a bitch about Onscreen, in my case, I find the Android keyboard and the iOS one equally unusable on tablets)
[20:47] <infinity> Maybe I'm that 1% of the market that netbooks are still aimed at, for that very reason.
[20:48] <slangasek> now I just need a USB video device so I can plug the nexus into my KVM
[20:48] <stgraber> infinity: I almost got used to using swype on my phone, though it's still a pretty slow input method and I have to constantly switch between languages (I write using english technical words to french speaking friends who have german names...)
[20:49] <slangasek> stgraber: german names + english tech -> custom dictionary? :)
[20:50] <slangasek> I'm pretty irritated in general with the version of swype included in the T-Mobile ICS load
[20:50] <slangasek> pros: includes more languages by default so I can swype in my language of choice.  cons: thinks it's ok to autocorrect me when I've typed out a word instead of swyping it
[20:53] <stgraber> slangasek: according to google, the nexus 7 doesn't do MHL, so no luck at getting any kind of external video output then :(
[20:53] <slangasek> MHL?
[20:54] <maxb> HDMI output from a USB-ish thing
[20:54] <stgraber> some weird hack that phone manufacturers use to get both USB and HDMI on a USB port
[20:54] <slangasek> hmm
[20:54] <stgraber> if it did, you could have bought a splitter, then get both USB and an HDMI output from the tablet which would have been pretty handy to plug it on a kvm :)
[20:55] <maxb> I don't think MHL necessarily supports USB and HDMI simultaneously
[20:55] <slangasek> right; even without that though, there are USB video devices that are supported by X, and I've heard they might work with varying degrees of success
[20:56] <stgraber> oh, the displaylink devices, yeah, I've been meaning to try one of those again, last time all I could get was a green screen but that was a while ago (when I still had access to one of those)