[01:16] stgraber: Where'd queuebot run off to? [01:23] slangasek, https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/CommonInfrastructure [01:23] can you take a pass and add any other key feature changes that the foundations team has added this release? [01:25] ogasawara, ^ I've put the kernel in the CommonInfrastructure too, and pulled together the bits from the other release notes. Edit/improve as necessary [01:25] :) [01:29] skaet: I'm not sure we need to mention armhf linker changes in the release notes, given that there was no oneiric armhf release. [01:30] infinity, we do need to mention that armhf is now supported, and the default for arm ports though, this is one way. [01:31] skaet: upstart => James Hunt, not James Page [01:31] but if the specific linker issue isn't worth mentioning in your judgement, am fine with that. [01:31] oops [01:32] thanks cjwatson, fixed. [01:34] * micahg thought aufs was reenabled, did that not happen? [01:35] It did. Bug 943119 [01:35] Launchpad bug 943119 in linux "aufs.ko missing from the Precise kernels" [Medium,Fix released] https://launchpad.net/bugs/943119 [01:35] People should still migrate though [01:36] right, but shouldn't the release notes reflect reality though :) [01:36] AUFS has been disabled, anyone needing AUFS is encouraged to migrate to overlayfs. [01:36] Oh I agree [01:36] Just saying [01:36] I agree with what you're saying as well :) [01:36] (Also, the above is a run-on sentence, which we should avoid) [01:36] But it's >2:30am here, so bed [01:37] skaet: ^^ [01:39] cjwatson, sleep well. [01:41] skaet: this should probably also be mentioned under the kernel: https://lists.ubuntu.com/archives/ubuntu-devel/2012-March/034969.html [01:44] micahg, good point. added. Will let leann wordsmith a bit more. ;) [01:44] skaet: did you see the note about aufs above as well? [01:44] yup, just deleted the AUFS has been disabled, part. [01:46] skaet: you might want to add that it will be disappear in future LTS backport kernels per https://lists.ubuntu.com/archives/ubuntu-devel/2012-March/034880.html [01:47] michag, will let ogasawara decide if we want to point out future plans, or leave it alone. Thanks for bringing it up. [01:48] ogasawara, ^ your call. [01:49] sounds good [02:31] skaet: I'm puzzled by the overall structure of this page... this is far more technical detail than we've gone into for release notes in the past, is there guidance on who the audience is and the context in which this is going to viewed? [02:32] skaet: if it's really supposed to serve the same function as release notes in the past, I would cut everything about gcc/python/upstart, none of which rises to the level of warranting top billing in the release notes [02:32] (upstart logging is great, but users will discover that when debugging; until then they don't need it :) [02:33] slangasek, have broken it up to a per-product, and the kernel and foundations bits are in the common section. Thought here is to give users an overview as to what's in the release and structure it in a way we can extend for the .1, .2, etc. release. [02:34] slangasek, guidance is to give a more general feature overview for the users. If something is too detailed, strike it. [02:34] :) [02:34] I was just merging technical overview information from the prior releases as a starting point. [02:35] right [02:36] fwiw in the past we've scratched the technical overview info and started from scratch when doing the final release notes, because there's such a big disparity in the level of technical detail we want to give alpha/beta testers vs. users who are going to see links to these notes in the installer/upgrader [02:37] slangasek, https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/982859 - is update-manager appropriate, or should this get directed to desktop/skype? [02:37] Launchpad bug 982859 in update-manager "Upgrade to 12.04 breaks if skype is installed" [High,Confirmed] [02:37] how is breaking this up by product going to work in practice? [02:37] because there's a single release note URL that's passed in the installer... is that going to only point to the desktop bits now? [02:37] https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop [02:37] is the Desktop one.... [02:37] working on the server one. [02:38] want the installation requirements, instructions, etc. broken down per image. [02:38] looking at the skype bug [02:38] then our point releases can be linked off of the pages that have LTS. [02:38] skype is priority. more on this tomorrow. ;) [02:39] this looks like not-a-bug [02:40] OTOH, most reports of skype causing upgrade problems look like not-a-bug to me, so let me be sure [02:40] slangasek, Ursinha is still around if you want more details. [02:41] Ursinha: can you please file a separate bug report with upgrade logs for your skype upgrade issue? ^^ 10.04->12.04 vs 11.10->12.04 are going to need entirely separate debugging [02:41] Ursinha: and I expect that any analysis I do on the original submitter's logs is not going to apply to your case (non-multiarch vs multiarch, etc) [02:43] I'll do [02:44] Oh, since queubot's being unhelpful. [02:45] slangasek: There's a compiz-plugins-extra upload in the queue that could use someone !me approving. [02:45] Ursinha: taking a stab in the dark, though, I would guess that: 1) you installed skype from the skype.com website; 2) you selected the .deb listed as "64-bit" on the skype website; and possibly 3) you don't have the partner repository enabled [02:45] Actually, wait. When does universe freeze? [02:45] infinity: "later" [02:45] Maybe it doesn't need approval, it's a bug fix. :P [02:45] yeah [02:45] slangasek, my skype was skype:i386 [02:45] oh, interesting [02:46] I definitely want to see the logs then :) [02:46] sure, will find them [02:46] it's also possible this was caused by another annoying instance of temporary multiarch uninstallability and that it'll be a non-issue for release... but we'd better make sure [02:47] Most M-A upgrade bugs amount to that. [02:47] Which is annoying, when trying to find the real bugs in the haystack. :/ [02:47] well, the timing of this one is odd, because I thought everything of substance went through -proposed [02:47] in the past 24h [02:48] skype:amd64 Depends on skype-bin [ amd64 ] < none > ( none ) can't be satisfied! [02:48] that's the original submitter's issue [02:48] and is specific to 10.04->12.04 [02:48] What was the default compiler in oneiric? [02:48] gcc-4.6 [02:48] (.1) [02:49] Oh, kay. [02:49] Then I won't blame my gcc-4.5 upload for breaking Ursinha's upgrade. [02:49] (gcc-*-base being MA:same and all...) [02:49] hmm [02:49] I think we might just need to un-blacklist skype [02:51] because new skype:amd64 wants an i386 dependency; old skype:amd64 wants ia32-libs; new ia32-libs wants an i386 dependency; old ia32-libs wants lib32v4l-0 which I may have killed with fire [02:53] sigh; unintended consequences [02:53] hm, I guess one of the uninstallable packages today was lib32v4l-0... will check again [02:53] yeah, can't hold the stack back because it needs lib32v4l-0, which Depends: libv4l-0 (= 0.6.4-1ubuntu1), and we kinda don't want to hold that back [02:54] Ursinha: lib32v4l-0 is gone from the archive [02:54] it went away in oneiric [02:54] so that should not have been implicated in an oneiric->precise upgrade at all [02:57] although, libv4l-0's shlibs haven't changed since 0.5.0 [02:57] if we held that back on lucid upgrades, it should dtrt... there'd just be a handful of packages left to upgrade once multiarch got applied [02:57] (handfull == skype+ia32-libs+libv4l-0) [02:58] +wine [03:05] * infinity thinks it might be time to call it quits for the day. [03:06] * ScottK thinks infinity must be getting old and weak. [03:07] I won't disagree with that. [03:07] But you forgot fat. [03:08] I haven't seen you in person in awhile. [03:09] ScottK: lua-lgi synd [03:09] *syncd [03:09] OK. [03:13] Did someone else accept it already? [03:14] o/ [03:14] The fat man got there first. [03:14] OK. Good for you. [03:14] All the armhf symlink farming didn't entirely rot your brain. [03:15] Close. [03:18] Best bug report ever: "Don't know what happened! I was browsing Launchpad through Chromium browser." [03:23] * skaet pondering where to group Netboot images.... [03:23] In what sense? [03:27] infinity: someone typed something there.. are you saying you dont get bugs with "..." as the summary? want some? :) [03:28] infinity, group them with Server or Core or ...? [03:28] own page [03:29] Sarvatt: Heh. [03:29] skaet: From the POV of release notes, I'm not sure they really need mentioning at all. [03:29] infinity, we put links into where they get downloaded from [03:29] need to find a home for that [03:31] I suppose. Using netinst images is a pretty wildly technical thing, just pointing people at the installer-$arch directories doesn't help much. [03:32] People who know they need them probably know where to get them. [03:34] slangasek, odd enough I can't find any evidences that skype is the culprit right now looking at the logs [03:35] Ursinha: can you post them to a bug so I can have a look too (or post me the bug number if it's already filed)? [03:38] slangasek, I haven't file a bug yet, am trying to find a clue of what happened so I can look for duplicates; I've uploaded the /var/log/dist-upgrade folder here so you can look: http://people.canonical.com/~ursula/dist-upgrade.tar.bz2 [03:38] *filed [03:39] Oh, dangit, I forgot all the no-change rebuilds of cross-compilers. [03:39] Do dee doo... [03:40] Ursinha: yours is bug #902603 [03:40] Launchpad bug 902603 in taglib "When installing Multi-Arch: same (meta-)package for two architectures, dpkg considers one arch as completely disappeared" [High,Fix released] https://launchpad.net/bugs/902603 [03:41] oh, it's fix released? [03:41] apt-term.log: (Noting disappearance of libjpeg8, which has been completely replaced.) [03:41] it's fixed /in precise/; needs backporting to oneiric in SRU [03:42] slangasek, mark it for release note? [03:43] It really should be fixed in oneiric before we release. [03:43] skaet: even though it's intended to be published as an SRU before the release? [03:43] if SRU for oneiric goes out before release, then guess not. :) [03:44] until it's SRUed, I wouldn't be able to write a useful release note anyway. [03:44] "sometimes your upgrade might fail. If it does, turn it over, shake it, and try again." [03:44] lol [03:45] yeah, not ideal. [03:45] slangasek, do you have a safe workaround for that? I almost had to reinstall everything in order to fix the mess [03:46] * skaet --> zzz [03:46] Ursinha: dpkg -i /var/cache/apt/archives/dpkg_*.deb; dpkg -i /var/cache/apt/archives/libjpeg8_*.deb; apt-get -f install [03:46] skaet, good night :) [03:47] cool, adding that to release notes might do it for now [03:47] and to the bug (if not there) [03:47] Thanks Ursinha. :) [03:47] Ursinha: feel free to do so... in the meantime I'm going to get that SRU going :) [03:48] great :) [03:50] done [03:50] and thanks sladen [03:50] oops [03:50] slangasek, even [03:55] ok, dpkg sru uploading [04:11] Hrm, I should get added to ~ubuntu-sru so I can officially review and approve that for you. :P [04:34] night all [04:36] Ursinha: 'Night. [05:51] Good morning [06:00] pitti: o/ [06:00] hey infinity, how are you? [06:01] rejecting vte3, asking for reupload to -proposed [06:01] I'm alrightish. Kinda hoping I sleep tonight. :P [06:07] powerpc should recover from my compiler uploading pain in ~7h [06:07] Really wish we had that 3rd buildd already. :/ [06:09] yeah, just noticed [06:09] https://launchpad.net/ubuntu/precise/+builds?build_text=&build_state=pending [06:09] still four compilers to go [06:11] there are 3 or 4 remaining gnome 3.4.1 tarballs to do, doing now [06:11] gdc-4.6 will fail in the first 30 seconds. [06:11] And the others are all fairly quick builds, compared to gcc. [06:11] (Or the evil gcc-snapshot...) [06:16] -snapshot does the full fun of triple-bootstrapping and test suite, I guess [06:17] And builds every compiler in the suite. [06:18] That's the painful part. [06:20] queuebot is AWOL? [06:20] Yeah. [06:20] stgraber: Seems to have discovered life outside of IRC and hasn't noticed. ;) [06:21] queuebot: you'll get ice cream when you come back, promised! [06:21] Err, 's/: S/ s/' [06:40] cheese packaging is kindly waiting for a hug [06:41] s/packaging/package/ [06:46] Hahaha. [06:47] Accepted, and going to bed. :) [06:48] infinity: sleep well === doko_ is now known as doko [09:15] skaet: if you're breaking the release notes up, please make sure that the web team knows about it for the table of release note URLs by product/release/architecture maintained on www.ubuntu.com, so that the installer will link to them properly [09:19] infinity: and it's back ;) with some basic reconnection code now, hopefully that'll help [09:58] didrocks: ^ accepting, FYI [09:58] pitti: ah thans, the queue page is still not loaded here [09:58] pitti: tried to refresh 3 times… [09:58] thanks* [10:01] I have a updated app-install-data upload, should that go to -proposed at this point or can/could it still go to the main repo? [10:18] mvo: can go to precise, it's arch:all [10:18] ta [10:31] mvo: http://launchpadlibrarian.net/102317906/synaptic_0.75.9_0.75.9ubuntu1.diff.gz [10:31] mvo: why does that add a 00list? [11:32] pitti: it will use a different set of patches on ubuntu and debian (well, none on debian, some on ubuntu to set eg. changelog location). this is a side-effect of that its not a sync anymore === greyback is now known as greyback|lunch [12:24] Does the fix for bug 982883 require a UIFe? [12:24] Launchpad bug 982883 in ubiquity "Wrong color of top panel in ubiquity-dm" [High,Triaged] https://launchpad.net/bugs/982883 [12:24] It's a regression from 11.10 and looks fairly awful, so I'd like to get it fixed [12:25] I consider it a bug [12:25] but terminology aside, I'd also approve it as an UIFE [12:25] I suppose I should tell ubuntu-doc@ [12:28] posted to -doc and subscribed ubuntu-release for the exception request [12:29] cjwatson: the panel was fine 2-3 weeks ago, so it's a very recent regression, don't think we need a UIFe for that [12:29] cjwatson: I spent a day doing bugfixes on the panel during the installer sprint and it was definitely black at that point :) [12:30] ah, well, better safe than sorry [12:32] cjwatson: according to bzr, panel.png was dropped last thursday (12th) [12:32] ha [12:32] probably part of "Remove the need for gtk2-engines-pixbuf in the gtk2 theme, save some CD space" [12:59] rejected apt from oneiric-proposed per discussion on #ubuntu-devel [13:09] kdevelop was me. === greyback|lunch is now known as greyback [14:19] cjwatson, re: release notes, told web team about it last month, they were fine with approach. I'll be double checking the linkage as soon as they have the staging site up. [14:20] pitti, https://bugs.launchpad.net/unity/+bug/965323 seems to have a fix ready to go, and fixes a nasty regression. Any issues from your point of view (bad interactions) with other fixes already approved? [14:20] Launchpad bug 965323 in unity "Panel is transparent when Dash is open; no blur no average BG color" [Medium,In progress] [14:23] pitti, here I am for a discussion [14:24] pitti, affected are netbooks in particular. [14:25] all hardware not capable of opengl 2.x [14:25] so all netbooks and not recent laptops [14:27] was a regression introduced in unity 5.8.0 by a wrong commit, I basically reverted the commit so we can consider this patch safe and tested (it's the codebase of unity 11.10 and tested till 5.6.0, doesn't have any issue) [14:27] hm, I have a deja-vu about this; wasn't this recently discussed already: [14:27] ? [14:28] pitti, not that I am aare [14:28] *aware [14:28] pitti, well, maybe it was, but I fixed it safely so I'd like to see if we can ship 12.04 with that fix [14:29] so, no objection from me [14:29] ubuntu is installed on lots of netbooks, and many people don't even run upgrade, having such a broken experience at first glance it a bit embarassing :\ [14:29] great [14:30] thanks pitti, Cimi. [14:30] pitti, could you pls add your ack in the bug? [14:32] done [14:47] pitti, will you upload the translations before end of day? would like to get them included, and make any last minute size adjustment to the images for tomorrow, so we're ready with release candidates on Thursday. [14:48] https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule (LanguagePackTranslationDeadline) is today. [14:56] https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFRBS1NNREM5bWdYTGM3eEVwRFdyX1E#gid=0 [14:58] skaet: preparing the ubiquity-slideshow-ubuntu upload now, should be in the queue in ~10 min (depending on how quickly LP exports the translations) [14:58] Thanks stgraber! :) [15:06] I'm going to be doing a release upgrade on kapok and disabling builds on there while I'm doing it [15:07] Scream now if this is a terrible idea [15:10] deej, how long out of commission for? [15:10] skaet: Probably an hour or so [15:10] Hopefully less, but one never knows [15:10] hard -> lucid is a bit of a dance [15:10] *hardy [15:11] deej, not aware of anything critical in that period. (a day would be different ;) ) no screams from me. [15:11] Sweet [15:11] I'll let you know when I start and finish [15:12] Cardamom will be next once I've done kapok and ensured nothing went horribly awry [15:12] pitti: skaet: so you really want that we pushes this. this code path has not been tested for few weeks. I fell unconfortable pushing that [15:13] pitti: skaet: meaning, if it crashes on some various netbook as it did in the past, you agree to take the chance? [15:13] didrocks, screen shots from netbook look seriously wedged without it. do you have the bug numbers of the prior crashes? [15:14] skaet: we had some crashes on gboolean vs bool usage on amd64 [15:14] and this changes that [15:14] you can look at debian/changelog for some crashes with it [15:15] skaet: and we released oneiric with worst top panel effect, I'm really unsure why you want this now and not in the first SRU [15:15] but anyway, if you feel confident, I'll push it. I just don't want to be guilty if there are side-effects [15:16] didrocks, warning appreciated. We'll regress it out if side-effects occur. [15:17] Cimi, ^ [15:17] ok, I'm pushing the change [15:17] merging the patch, let's see how it goes [15:17] grub2: tested successfully by manjo, isolated to EFI paths [15:17] fixes abject boot failure [15:17] didrocks, gboolean vs bool is different [15:17] Cimi: is it [15:17] Cimi: doesn't seem in that case [15:18] didrocks, nux returns bool [15:18] didrocks, it was wrongly using FALSE [15:18] which requires an extra compiler instruction to translate FALSE into false [15:18] it is just saving one instruction, but the value is the same [15:18] I can use FALSE, but it is wrong [15:19] I still don't agree that's something that should get fixed now, it seems it didn't annoy anyone for the past 4 weeks (since 5;8) [15:19] but if you prefer it, ok, meanwhile, we still have wrong matching application on the launcher… [15:20] Cimi: please propose a packaging branch I'll sponsor you [15:20] didrocks, fine [15:20] didrocks, remember that each of us do a different job: I take care of those bugs, other take care of bamf or crashers [15:21] didrocks, it's not my fault if nobody is proposing fixes for the launcher [15:21] Cimi: I do but we keep having small UI changes and changes of changes for the past 4 months because "last visual change was bad" [15:22] didrocks, unfortunately visuals are affected to regressions like other changes. [15:22] didrocks, we need to add a strong framework for reftests [15:22] well most of the time it's presented for "harmless visual though" :) [15:22] but it's another story, and I will propose a talk at the ps sprint [15:23] Cimi: ready once you propose the branch [15:23] didrocks, I am of the opinion that we should not make a fuss on visuals [15:23] ok [15:23] will do [15:23] didrocks, what shall I do, cherry pick the diff? [15:23] didrocks, and propose with ~ubuntuX [15:23] Cimi: create a changelog and bzr merge the commit from trunk [15:23] ok [15:23] cool [15:29] didrocks, shall I wait for my branch to be merged to trunk? [15:30] I might need an UNBLOCK :) https://code.launchpad.net/~unity-team/unity/unity.fix-965323/+merge/102278 [15:30] Cimi: yeah, that tests passed and such [15:30] Cimi: no, we are not in freeze, so it will get merged at next run [15:30] let me look [15:30] Cimi: it's needs review still [15:30] Cimi: nobody approved the merge status itself [15:30] didrocks, I did [15:32] Cimi: next run is at 35, then 30 minutes for building and make check [15:32] ok [15:32] thx [15:34] yw [15:34] pitti: do you want to go with precise-proposed for that one as well? ^ [15:36] didrocks: if it's not too much trouble, yes [15:37] Cimi: please target precise-proposed in the changelog instead of precise FYI [15:37] ok [15:37] thx [16:05] hum, no Cimi? ok, doing the cherry-pick then [16:06] [Errno 111] Connection refused ? [16:07] am I the only one getting it? [16:08] ah, fine now [16:11] doko, I've rejected gcc 4.6, neither bugs listed appears to be release critical, feel free to educate me if I'm overlooking something. [16:14] skaet: pitti: unity uploaded ^ [16:14] didrocks, waiting on diff. thanks. [16:16] skaet: apport/kerneloops uploaded now [16:16] thanks pitti [16:16] pitti, can you review the unity upload? [16:17] sure [16:18] skaet: I think we should queue at least apport for a while, and upload it at the last minute only [16:18] especially while we are still getting new unity releases, etc. [16:18] we don't want to miss crashes from those [16:18] pitti, fair enough, will mark it as such on the pad [16:18] oh, speaking of which... [16:18] kerneloops is probalby fine, we won't get a newer kernel now [16:18] yeah, I think we need to fix those pads by UDS [16:19] given our lovely timeout behaviours [16:19] they didn't use to be so unstable [16:19] and we are so going to need them for UDS [16:19] do folks want me to switch to tracking on a WIKI instead [16:19] at UDS, we usually open and close, rather than come back to periodically, so probably won't be such an issue for there. [16:19] skaet: TBH, I'd rather reconnect every once in a while than always having to do the wiki overhead, but I don't have a strong opinion [16:20] slangasek, cjwatson, ScottK, infinity, (and other release team members who are using it ;) ) any strong preferences? [16:20] on pad vs. wiki? [16:20] I'd prefer Gobby. [16:20] what's the downside of the pad? [16:21] the pad is treacherous: it looks like it's up to date but half the time it fails [16:21] I find it completely awful in nearly every way [16:21] Have to reconnect all the time and can't tell if what you have is up to date. [16:21] hmm I've never noticed that with etherpad, maybe notes.kde.org is more reliable :) [16:21] With Gobby you know if you're connected or not and there's not all the overhead of the wiki. [16:21] Riddell: I don't think it requires relogin like the Ubuntu one does. [16:21] Google docs is another option [16:21] * infinity goes bouncing builds that failed due to ftpmaster being rebooted. :/ [16:22] ScottK: right there's no login [16:22] I don't really care whether it's dynamic or you have to reload [16:22] half way in between is the worst of both worlds [16:22] ScottK, Gobby sounds interesting indeed. Is there an instance set up somewhere we can use? [16:22] gobby.ubuntu.com [16:22] Recall, the Ubuntu one is run by the same people that decided a pastebin that requires a login to download text would be a good idea. [16:23] ScottK: which to be fair was due to widespread abuse [16:23] thanks cjwatson, google search didn't show it. :) [16:23] (AIUI) [16:23] Dunno. Other pastebins seem to manage without it. [16:23] Riddell: right, and the pad didn't use to do that either [16:23] seems like a recent regression [16:23] in pad.u.c., not in etherpad in general I mean [16:23] other pastebins expire much more aggressively, which seems like a different tradeoff [16:24] skaet: use notes.kde.org! [16:24] also pastebin.com is notorious for hosting some fairly malevolent stuff that I'm not surprised ubuntu.com doesn't want to host [16:24] gobby.ubuntu.com isn't around anymore. [16:24] oh, ok [16:24] yeah, was just there trying.... :( [16:25] are other etherpad instances as bad? titanpad / pad.ubuntu-uk.rg [16:25] org* [16:26] Laney, pad.ubuntu-uk.org had a nasty habbit of timeing out on me, and not letting me access it at the end of my day.... just when I wanted to do some updates. [16:26] I can probably provide a gobby server. Give me a minute. [16:28] skaet, slangasek: now please could you coordinate your actions? [16:29] slangasek, infinity: now that gcc-4.6 is in precise, I assume it is ok to upload the two linaro regressions fixes to precise-proposed? [16:29] doko: should be, yes [16:29] Doesn't Daviey have an etherpad that doesn't require login? [16:29] I'd prefer not to have to run gobby just to do this. [16:29] Ahh, yes pad.ubuntu-uk.rg. Laney already mentioned it. [16:29] We should get a Twitter account :P [16:30] doko: I'll just accept it from rejected. [16:30] doko: if you want the release team to pre-coordinate, get the release team to comment on the bug instead of just on IRC :) [16:30] infinity, would like some discussion first. [16:30] infinity: they should only be accepted as candidates for an SRU [16:30] skaet: mailout02.controlledmail.com port 6522 for Gobby. I'll invent and easier hostname in a minute. [16:30] skaet: The bugs should be fixed. Neither is RC, as you note, but this is being staged for -updates. [16:31] which means a) the SRU team should be who accepts it, not the release team, b) it should be documented on the pad (or whatever replaces the pad) [16:31] documented that it's not for -release [16:31] thanks [16:31] slangasek: Oh, fair point on the SRU team. But you're on it. :P [16:31] slangasek, infinity - please note on the pad its purpose so we don't loose track. [16:31] slangasek: And you already implied it was okay from your POV. [16:32] infinity: yep [16:32] * infinity lets vorlon deal with it. [16:32] slangasek, they python patch there too, same story? or release critical? [16:33] skaet: that was discussed on #ubuntu-devel, I've been on the phone though so haven't followed the thread just yet - ScottK has commented though [16:34] It's not release critical, but doko would prefer it in. I understand why he prefers it and since we're going via proposed, we can't break the archive like we did last time we tried it. [16:35] skaet, I don't care, as long as it get's into 12.04.01 [16:35] The only thing that breaks is if all arches don't build together. [16:35] We can fix this. [16:35] Though it means me offlining a PPC buildd to make it happen. [16:35] ScottK, is there a compelling reason we can't just get it in as an SRU at this point? [16:36] Ask doko [16:36] doko, would like more testing and ease it in as SRU if possible. 10.04.1 should be ok. [16:37] sure, we can do this. but then again, we'll have the parallel build issue, and that with hundreds of packages in sync [16:37] * ScottK hands skaet at 12. [16:38] away now until midnight [16:38] There's nothing (afaict) dangerous about the change, the danger is all in the build. [16:38] * skaet isn't seeing a good option here. [16:38] And we should have fixed that instead of reverting and forgetting about it, IMO. [16:38] But oh well. [16:40] infinity, can we do this in proposed, after the current set clears out? [16:40] skaet: gobby.kitterman.com exists now if you want to use it. [16:40] I copied the current pad over if you want to look and see. [16:40]