[00:51] <pleia2> need to do a better job of checking -news-team for things before publishing, I keep missing new member announcements (even for Americas board, which i'm on, and sometimes write!)
[08:10] <dholbach> good morning
[08:56] <dholbach> c_smith_, happy birthday!
[15:31] <dholbach> hey c_smith - happy birthday :)
[15:31] <dholbach> bkerensa, do you want to go with the Kernel team update tomorrow or rather one of the new contributor interviews you did before?
[15:33] <dholbach> hey iBkerensa
[15:33] <dholbach> do you want to go with the Kernel team update tomorrow or rather one of the new contributor interviews you did before?
[15:34] <iBkerensa> dholbach: kernel sounds good
[15:35] <iBkerensa> im getting ready to go to sleep now so ill check doc in 4 hours
[15:35] <dholbach> sure sure
[15:36] <dholbach> good night :)
[15:36] <iBkerensa> gnight
[15:36] <iBkerensa> kinda its 7am
[15:37] <dholbach> bkerensa, the only pic I found doing a quick research was https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-snc3/31973_396602342186_511662186_4670103_1936442_n.jpg (Kernel team at UDS-M)
[15:41] <c_smith> dholbach, thanks, sorry for the late response, had to go afk for a few.
[15:41] <dholbach> sure sure :)
[15:41] <dholbach> hope you're going to have a great day
[15:42] <c_smith> dholbach, also, excuse my inactivity, I'm currently can very rarely handle both Firefox and Xchat.
[15:42] <c_smith> even on XFCE.
[15:42] <dholbach> don't worry - that's totally fine
[15:43] <c_smith> yeah, I intend to get back on the ball when I get my main PC back.
[15:43] <dholbach> maybe we should have a chat together with bkerensa again and try to figure out how we best go about figuring early in the week who's going to do what
[15:43] <c_smith> well. g2g, cyall later.
[15:43] <dholbach> yeah, don't worry - it's totally fine :)
[15:43] <dholbach> see you! :)


[01:47] <FurretUber> What is the difference between the auto-resize and the entire disk tests? Their descriptions are exactly equal


[00:02] <directhex> nggggg
[00:02] <directhex> well, the problem with some of the more esoteric arches is availability of porter hardware
[00:02] <directhex> e.g. i expect giving alexrp root on a ppc64el box for a week would yield a fixed port
[00:03] <directhex> but canonical don't give externals access, and ppc isn't that common anymore unless you have space at home for pseries, and all the money
[00:04] <directhex> lack of hw is why ppc64 is broken, too. i can't investigate since there's no debian porterbox for debian-ports arches
[00:05] <directhex> right, bedtime
[10:29]  * amjjawad is away: Be Right Back :)
[13:08] <utlemming> stgraber: I need to add a bunch more types for the test suites for EC2
[13:10] <utlemming> stgraber: specifically "Ubuntu Server EC2 HVM ({SA-East-1, Asia-Pacific-SouthEast-Australia, Asia-Pacific-NorthEast, US-West-1)}" and "Ubuntu Server EC2 HVM-Instance Store (<all regions>)"
[13:41]  * amjjawad is back (gone 03:12:18)
[13:43] <knome> amjjawad, could you please not use public away messages? thanks.
[13:43] <amjjawad> ?
[13:47] <cjwatson> amjjawad: "13:41  * amjjawad is back (gone 03:12:18)" - people generally don't care, please turn that feature of your client off
[13:47] <amjjawad> cjwatson, I do hate IRC just for the record :) so I know little bit about it
[13:47] <amjjawad> I have no idea how to turn that off
[13:48] <amjjawad> I use XChat and I choose away when I'm away, that is all.
[13:48] <knome> amjjawad, afaik, you didn't have that turned on before. ask the xchat channel how to disabled that.
[13:48] <knome> -d
[13:48] <cjwatson> Google for "xchat disable public away messages
[13:48] <cjwatson> "
[13:49] <amjjawad> why not that is a problem?
[13:49] <cjwatson> Looks like "/set away_show_message off", perhaps
[13:49] <amjjawad> I don't even come here unless I have to :) I'm not an IRC user at all
[13:49] <amjjawad> now*
[13:49] <cjwatson> Because it shows as real-conversation activity in the channel rather than things that IRC clients can automatically determine is uninteresting
[13:49] <cjwatson> Also because people asked you to
[13:50] <cjwatson> It's polite
[13:50] <xnox> amjjawad: 132 people spent 3 seconds of their productivity time, reading that message, causing 2 context switches =)
[13:51] <amjjawad> I don't know much about it so I will try to search on Google :) or even better not use it :)
[13:51] <amjjawad> xnox, wow? didn't know that :)
[13:51] <amjjawad> sorry about the 3 seconds that I wasted from your time :)
[13:51]  * infinity notes that xnox has a very inefficient string parsing engine in his brain.
[13:52] <infinity> amjjawad: It's not about "wasted time", it's that if all 132 people in the channel has verbose away/back messages, the entire channel log would just be spam from people going away and coming back.
[13:52] <cjwatson> amjjawad: The point is, imagine how unreadable the channel would be if every one of the 132 people (or whatever) in the channel decided to have their IRC client tell us when they're going out to the toilet.
[13:52] <cjwatson> Right, that.
[13:52] <infinity> amjjawad: So, either you're a unique snowflake who needs to tell us when he's around, or none of us should do it.  We're opting for recommending the latter. :P
[13:52]  * knome giggles at the mental image
[13:52] <amjjawad> Again, I know nothing about IRC so could we please move on and point taken, I will do my best to not use that :)
[13:52] <knome> "* cjwatson is off to the gents"
[13:53] <amjjawad> all my teammates know I hate IRC
[13:53]  * jpds tries to imagine #ubuntu like that.
[13:53] <amjjawad> I'm forced to use it from time to time
[13:53] <amjjawad> so point taken, thanks :)
[13:53] <knome> jpds, ow, my head!
[13:53] <cjwatson> OK, you don't need to go on about how much you hate IRC either :)
[13:54] <amjjawad> 2nd point taken :)
[14:24] <bregma> hey, we've got a critical fix in -proposed, what are the chances we can get it migrated to release withing the next couple of hours?
[14:25] <cjwatson> it'd help to say what it is :)
[14:25] <bregma> well, I was hoping someone would ask
[14:26] <bregma> this is a fix to Nux for bug #1282884
[14:26] <ubot2`> Launchpad bug 1282884 in nux (Ubuntu) "compiz crashed with SIGSEGV in __dynamic_cast()" [Critical,In progress] https://launchpad.net/bugs/1282884
[14:26] <plars> xnox: psivaa said he or davmor2 talked to you already about the server install failures - is there a fix coming soon for that?
[14:27] <xnox> plars: yeah.
[14:27] <xnox> plars: did you open a bug report number for it?
[14:28] <plars> I didn't, but perhaps psivaa or davmor2?  If not, I'll be happy to open one
[14:28] <cjwatson> stgraber: Do you have any Edubuntu, Ubuntu Kylin, or Xubuntu rebuilds still planned for beta 1 (I see they're all marked as ready)?  If not would it be OK if I unblocked nux?
[14:28] <davmor2> plars: it was psivaa
[14:28] <psivaa> plars: xnox: i haven't, do you want a bug report for that?
[14:29] <knome> cjwatson, no rebuild planned for xubuntu. i don't know what nux is, but i'll leave unblocking it to your judgement :)
[14:30] <xnox> plars: psivaa: that's ok, i'll just reopen the existing one, that i've closed.
[14:30] <psivaa> xnox: ack
[14:30] <highvoltage> cjwatson: no rebuilds planned for edubuntu.
[15:19] <cjwatson> stgraber,bregma: nux unblocked
[15:27] <stgraber> so for Beta 1, I'm planning for a mid-afternoon release. I've got a couple of meetings now but will prepare the announcement after that.
[15:27] <stgraber> (mid-afternoon eastern time, so in 4-5 hours)
[15:28] <stgraber> utlemming: I'll try and get those done in a tiny bit
[15:34] <infinity> stgraber: Does that mean you're happy with the ISOs and we can unblock?
[15:34] <infinity> (the world, I mean)
[15:34] <stgraber> infinity: not the whole world yet, still waiting for Kubuntu and Lubuntu to mark them ready
[15:34]  * infinity nods.
[15:34]  * highvoltage copies and pastes edubuntu notes so long
[15:40] <utlemming> straber: thank you kindly
[15:40] <highvoltage> stgraber: hmm... where will the note links be?
[15:52] <Riddell> stgraber: marking kubuntu as ready, I'm about to run away for a long weekend, shadeslayer and apachelogger are your contacts
[16:01] <stgraber> Riddell: ok, thanks
[16:19] <stgraber> utlemming: HVM is 64bit only right?
[16:19] <utlemming> stgraber: yes, only 64-bit
[16:21] <stgraber> utlemming: ok, I have added the products, still have to link the tests and add them to the trusty manifest
[16:24] <stgraber> utlemming: all done
[16:31] <stgraber> highvoltage: what are you referring to?
[16:35] <stgraber> highvoltage, shadeslayer, apachelogger, zequence, knome, amjjawad, darkxst, elfy: http://pad.ubuntu.com/trusty-beta1-announcement
[16:35] <stgraber> I'm still doing some sed on that though :)
[16:38] <highvoltage> stgraber: yes that's it
[16:43] <directhex> infinity, so, for now, ubuntu1 my mono 3.2.8 upload to re-enable ppc64el, so those binaries build & that blockage on proposed->main transition goes away?
[16:46] <infinity> directhex: Yeah, that's what I'd advise.  If I don't get it fixed by final freeze, we can back it out and tear out all the dependant binaries, but I'm pretty confident we'll get someone on the case.
[16:47] <infinity> directhex: Or were you asking me to do the ubuntu1 upload?  I can do that.
[16:47] <directhex> infinity, i can do it now, that's fine
[16:48] <infinity> Kay, cool.  Thanks.
[16:48] <directhex> huh, i hadn't looked at this diff in detail before, it's not just tinkering in debian/, it's a substantial body of work
[16:49] <directhex> i may have misrepresented that when i said i wasn't happy about it having been unilaterally uploaded. wonder how much of this helps on BE powerpc64
[16:50]  * infinity downloads to look.
[16:50] <infinity> Also, whee, 78MB orig?  Really?
[16:53] <infinity> Oh, indeed, that's a lot more patch than doko's changelog implied...
[16:55] <infinity> directhex: I'll hunt down where that came from, so we can get it properly fixed.
[16:59] <infinity> directhex: Okay, so some of this is upstream.  Not sure how much...
[17:01] <directhex> infinity, not seeing much of it in master
[17:02] <directhex> beyond the existing bitrotted ppc64
[17:02] <infinity> directhex: Yeah, I think the first file I checked happened to be a fluke on that score.
[17:02] <cjwatson> Riddell,ScottK,Mirv,didrocks,asac: any/all of you up for subscribing to https://blueprints.launchpad.net/ubuntu/+spec/core-1403-qt5-versioning (scheduling late)?
[17:02] <infinity> directhex: So, wherever doko got this mystery patch from was someone who had pulled some bits from upstream and then got to work on the porting.  I'll hunt that all down and sort it out.
[17:03] <infinity> (Sadly, I think doko just disappeared for the weekend, but I'll figure it out)
[17:03] <infinity> directhex: In light of that "someone was obviously working on porting it" thing, though, I feel more confident about re-enabling it and assuming it'll get fixed.
[17:03] <asac> cjwatson: you rock :)
[17:03] <didrocks> cjwatson: sure
[17:03] <asac> cjwatson: thats a UDS session?
[17:04] <ogra> asac, obviously
[17:04] <cjwatson> that's the idea
[17:04] <ogra> (see the "Sprints" part
[17:04] <ogra> )
[17:04] <directhex> infinity, i think that's fair
[17:04] <asac> i didnt open yet.
[17:04] <asac> :)
[17:04]  * asac subscribes
[17:04] <asac> cjwatson: who will come with the proposals to discuss?
[17:04] <asac> nevermiund
[17:04] <cjwatson> there's a whiteboard with notes
[17:04] <asac> let me read it first
[17:05] <directhex> infinity, seems the biggest gap here was a lack of coordination with the debian packaging team, then - especially by whomever was writing patches this sophisticated
[17:06] <directhex> swapping out target registers isn't casual hackery
[17:07] <xnox> infinity: i've had similar mistery patches from doko for e.g. boost port, that i've upstreamed. he didn't tell me where he got them from...
[17:07] <infinity> directhex: Fail on doko's part for the really non-verbose changelog and not forwarding to Debian.  Fail on the mystery porter's part for this not being upstream.  I'll try to make sure both are appropriately chastised (once I figure out who that second party is...)
[17:07] <Laney> hahaha
[17:08] <Laney> I love that doko has kidnapped some people to live in his basement and work on porting software for scraps of food every few days
[17:08] <xnox> infinity: i wonder if the mystery porter, is doko, intoxicated hard....
[17:09] <knome> if it is, i guess i want that booze to be able to write sophisticated code
[17:09] <xnox> Laney: don't give out foundation's secretz.
[17:09] <Laney> the klose peak
[17:09] <directhex>  20 files changed, 363 insertions(+), 281 deletions(-)
[17:09] <infinity> xnox: I guarantee it's not.
[17:09] <directhex> this is pretty comprehensive work, and yes, i'm happy to include this in an ubuntu1 for now. if it goes upstream, it can be a patch branch in -4
[17:11] <directhex> the changelog fooled me as to the scope of the changes
[17:11] <infinity> directhex: You and me both.
[17:20] <directhex> signing/uploading.
[17:20] <infinity> directhex: Many thanks.
[17:20] <directhex> infinity, looks like 1 file gained doko's changes between 3.2.3 and 3.2.8, but none of the rest of it is upstream
[17:20] <directhex> and that might be an unrelated fix
[17:21] <infinity> directhex: I've already hunted down the porter in question, and we'll be working on both upstreaming and fixing.
[17:21] <directhex> infinity, is that canonical confidential, or can you name them?
[17:21] <infinity> directhex: It's vaguely confidential until they make themselves known via a pull request. :/
[17:22] <directhex> infinity, that's fine
[17:25] <directhex> infinity, are you also doing BE ppc64? i'm curious whether this patch set affects BE ppc64, but my only means to test that is to upload something to Experimental & keep an eye on buildd.debian-ports.org for a few days
[17:26] <infinity> directhex: Hah, loving the changelog comment.
[18:01] <xnox> stgraber: Laney: does qa tracker allow to trigger respins of the "daily" milestone?
[18:02] <stgraber> yes
[18:03] <xnox> stgraber: may i have rights, to trigger e.g. ubuntu desktop and ubuntu server respins on daily images? =) e.g. i don't like waiting a day to see automated jenkins results, after landing fixes to bugs that automation picked up.
[18:04] <xnox> stgraber: or shall i wait, and / or poke people? E.g. please respin ubuntu-server i386/amd64 to pick up new grub-installer, which should make server.iso promotable to current again.
[18:05] <xnox> stgraber: also, all testing is complete and almost everything marked as ready. Isn't it past respin point, and thus freeze block should be lifted?
[18:06] <stgraber> xnox: waiting for lubuntu
[18:06] <stgraber> but yeah, if I don't hear back from Julien by then, I'll lift the freeze in an hour or so
[18:07] <xnox> stgraber: thanks.
[18:07] <stgraber> as for respin access, I'd to think about how to structure that, possibly making ~ubuntu-installer have product ownership access to some of the images, will have to think about it
[18:21] <stgraber> JackYu: hey there, can you update: http://pad.ubuntu.com/trusty-beta1-announcement
[18:36] <stgraber> flood gates opened
[18:39] <seb128> stgraber, \o/
[18:48] <xnox> stgraber: well, i wish to only be able respin dailies.... but milestones and dalies are the same thing, when milestone is active
[18:52] <stgraber> ok, that's all the flavours, doing publishing now
[18:52] <stgraber> utlemming: feel free to do your bits now (if any)
[18:53] <utlemming> stgraber: ack, and done already :)
[19:01] <shadeslayer> stgraber: \o/
[19:07] <rtg> infinity, when you get a moment could you approve linux-firmware 1.79.11 in Precise ? Its causing issues for some folks 'cause I removed the iwlwifi firmware from the kernel package. See bug #1285727 - guess I should have waited.
[19:07] <ubot2`> Launchpad bug 1281964 in linux-lts-saucy (Ubuntu) "duplicate for #1285727 Firmware iwlwifi-7260-7.ucode is missing" [Undecided,Confirmed] https://launchpad.net/bugs/1281964
[19:09] <infinity> rtg: We still have .10 in proposed.  What's meant to happen with that?
[19:10] <rtg> infinity, supersede it and approve the SRU bugs ?
[19:10] <infinity> rtg: Looks like releasing .10 would fix this... Unless there's a reason it shouldn't be?
[19:11] <rtg> infinity, the commit logs from Intel are totally confusing, but the second one 'iwlwifi: update firmware for 7260 / 3160 devices' actually adds a new file and API revision that a stable update added to the 3.11 kernel
[19:11] <rtg> which is why I'd like to see 1.79.11 get released
[19:12] <infinity> rtg: Sure, just saying that this "missing iwlwifi-7260-7.ucode" is in .10
[19:12] <infinity> rtg: And .10 appears to be tested, just that no one marked all the bugs v-done.
[19:13] <rtg> infinity, right you are. the second commit adds -8 which is for trusty.
[19:13]  * infinity nods.
[19:13] <infinity> So, let's release .10 and then accept .11 for testing.
[19:13] <rtg> infinity, works for me
[19:14] <infinity> First bit done.
[19:17] <infinity> rtg: Maybe we should consider pulling firmware into the PPA and tracking it with shanky, so we don't misplace updates that are needed to match kernels.
[19:18] <rtg> infinity, I think I've got everything we need for Trusty LTS, so there shouldn't be anymore changes.
[19:18] <rtg> it might help for the Trusty linux-firmware package though
[19:18]  * infinity nods.
[19:19] <rtg> I'll bug bjf
[19:19] <infinity> rtg: Anyhow, .10 should push out to mirrors soon enough and close that particular bug for you (well, you'll have to close it by hand, I leave that to you).
[19:19] <infinity> rtg: And .11 accepted to proposed.
[19:19] <rtg> saw that. thanks
[19:44]  * seb128 shakes fist at ppc, so 4 builders, all taken by private jobs
[19:45] <infinity> seb128: Is there something that desperately needs building or the world will explode, or is that just a general complaint?
[19:46] <seb128> infinity, just annoying to see everything else blocked, seems like we could keep/spare 1 builder for "normal business"
[19:46] <infinity> seb128: Security updates are "normal business".
[19:46] <infinity> And intentionally scored higher than everyone else, too. :P
[19:46] <seb128> well, more annoyed that the delay for my build is "one hour" and I wanted to see the result before eod
[19:47] <seb128> but that's not an important one, so just ignore me
[19:47] <xnox> infinity: i have a weird request -> and android-copyright binary be published into universe component, or should enabled multiverse in ubuntu-touch-meta?
[19:47] <xnox> infinity: s/and/can/
[19:47] <infinity> xnox: That sentence needs more English.
[19:47] <xnox> infinity: yeah, let me try again.
[19:48] <xnox> infinity: i have a weird request -> could you move bin:android-copyright (built by a source package in multiverse) be published into universe component. Or instead should I be enabling multiverse component in ubuntu-touch-meta package, since it needs android-copyright seeded.
[19:48] <seb128> infinity, let's say I'm just glad we don't have security fixes for webkit, qt and webkit, or we would block the archive for a week :p
[19:49] <infinity> xnox: multiverse source packages can't build binaries in universe, no.
[19:49] <xnox> infinity: ok.
[19:50] <infinity> xnox: Which part of Android's license makes it non-free?
[19:50] <infinity> (I haven't looked, just curious)
[19:51] <infinity> Or do we have binary blobs in there or something? :/
[19:51] <bdmurray> infinity: someone wants to do an SRU for d-rats to multiple releases with the same package version? Is that possible?
[19:51] <infinity> bdmurray: Sort of.
[19:52] <infinity> Given that it's already the same version, it's not unacceptable to suggest maintaining that status quo.
[19:53] <infinity> bdmurray: What would need to happen is an upload to precise, -3ubuntu0.1, and then copy it with binaries to Q/S
[19:53] <bdmurray> Ah, so you can't copy it from S to Q/P?  I already approved the Saucy SRU.
[19:54] <infinity> bdmurray: Depending on how anal you are, you can copy to Q/S-proposed and make them verify three times, but at least it only needs to be uploaded once.
[19:54] <infinity> bdmurray: No, can't copy back.  (Well, you can, but you'll probably break it).
[19:54] <infinity> bdmurray: We guarantee no toolchain backward compatibility, only forward. :P
[19:55] <infinity> So, in the case of C stuff, you'd get a libc dep too high, for instance.  In this case (python mess), maybe the dh_pyupport or other debhelper bits try to do something that older releases hate.
[19:55] <bdmurray> infinity: okay, thanks.
[19:56] <infinity> bdmurray: Pretty much a lost cause at this point, just ask them to do a precise SRU as well.  And I wouldn't bother with Q, unless it's a seriously nasty bug.
[19:56] <bdmurray> well the app doesn't work at all
[19:56] <infinity> Doesn't work at all seems alright, to be honest. :P
[19:57] <infinity> No one who's been running quantal for the last year is relying on that app, I'd assume.
[19:57] <infinity> But, up to the uploader and you if they want to do it.  *shrug*
[19:58] <xnox> infinity: binary blobs, which are included in the built images, which came from the other package.
[19:59] <xnox> infinity: android-src-vendor, is in multiverse, is a build-dep of android package. and blobs from android-src-vendor included in android.
[20:00] <xnox> infinity: the non-free bit of their license is "non-commerical usage"
[20:00] <infinity> xnox: Well, the binary blobs are non-free entirely. :P
[20:00] <xnox> and well the fact that those blobs are without source and not-modifyable.
[20:00] <infinity> xnox: So, yeah, build-depending on that explains it.
[20:02] <xnox> infinity: so i need to enable multiverse on ubuntu-touch-meta, since althought android-copyright is seeded, it wasn't actually so far been included on the images and thus our legal tab, doesn't show all the notices it should.
[20:13] <stgraber> beta1: publishing done, waiting for mirrors to update and torrent to publish
[20:14] <apachelogger> \o/
[20:15] <stgraber> to make things all round and nice, let's say I'll send the announcement in 45min
[20:16] <xnox> infinity: hm, that will not help, as multiverse component is not enabled on the touch images... (well at least in apt-sources), but i think it wouldn't be enabled during image builds. And i don't want to break touch image generation....
[20:16] <stgraber> that should be enough for bittorrent and leaves some more time for Kylin to update the announcement text (or I'll just point to their website and call it done)
[20:16] <infinity> xnox: It could be enabled.  *shrug*
[20:16] <infinity> xnox: Or you could build the copyrights thing from a free source package. :P
[20:16] <xnox> infinity: yeah, i don't want mutliverse enabled thought.
[20:17] <xnox> infinity: cause that has a potential flood gate.
[20:17] <infinity> Which flood gate is that?
[20:17] <xnox> infinity: right, let me work on extracting them properly into a standalone package.
[20:17] <xnox> infinity: well, things that are seeded and have depends | multiverse-package.
[20:18] <xnox> infinity: or i could get android package into restricted, and complete it's m.i.r.
[20:23] <stgraber> amjjawad, knome, elfy: I see you guys jumped the gun a bit ;)
[20:24] <amjjawad> stgraber, I didn't send anything yet but about to
[20:24] <knome> stgraber, yeah, oops, i quickly saw the topic change on this channel and thought it was out so...
[20:24] <knome> my bad
[20:24] <stgraber> amjjawad: I just saw your announcement in my rss feed
[20:24] <knome> don't blame elfy
[20:24] <knome> (this time)
[20:24] <amjjawad> I finished the post on our website already
[20:24] <amjjawad> but didn't send anything yet
[20:25] <amjjawad> I however had to update the link on the website :)
[20:25] <stgraber> amjjawad: well, your post is on planet.ubuntu.com already ;)
[20:25] <amjjawad> so now, I can safely send with a working link ;)
[20:25] <amjjawad> Xubuntu team were a bit hurry ;)
[20:25] <amjjawad> stgraber, oh, that was quick hehe
[20:26] <stgraber> anyway, doesn't really matter, though I expect the torrent links to still be broken at the moment.
[20:30] <elfy> stgraber: I try to keep him under control - but it's not easy :)
[20:30] <stgraber> elfy: haha :)
[21:00] <ScottK> cjwatson: Subscribed.  Thanks.
[21:01] <stgraber> beta1 announce is out
[21:02] <stgraber> cjwatson, slangasek: can one of you let my e-mail to u-d-a through please?