[01:07] hi skaet, still around? [01:07] hi micahg, yup, what's up? [01:08] skaet: 1st, I have to apologize, I forgot to tell mr_pouit that gmusicbrowser needed an FFe for the sound menu integration, should I file a bug and get a retroactive FFe? [01:09] I think he assumed I already got it, but it got lost in the shuffle [01:09] micahg, yes please. [01:09] skaet: ok, thanks, second, what to do with cairo-dock, bug 723994 [01:09] Launchpad bug 723994 in cairo-dock (Ubuntu Natty) (and 1 other project) "FFe: Please update Cairo-Dock to 2.3.0~0rc1 version (affects: 2) (heat: 16)" [Wishlist,New] https://launchpad.net/bugs/723994 [01:10] you were waiting for some things to land, where are they? [01:10] * skaet hasn't looked at the bug yet, and probably should :/ [01:10] s/yet/today [01:10] skaet: so, now he tells me the Debian package isn't good and we should just use his version, so I'm a little confused, maybe he was hoping Debian would take his changes [01:11] I was hoping we would just be able to sync, but that's not possible apparently [01:12] micahg, my preference is to leave it on the bench then for a while, and sort it out after beta1 comes out. [01:12] skaet: we can still upload then? Does UiF factor in? [01:13] It does. [01:13] But right now, we're at UIF as well. [01:13] UIF/BetaFreeze was 2300 UTC [01:14] ugh, ok [01:14] * skaet should send out a note. Was chasing too many loose ends earlier. Will do now [01:16] skaet: bug 742185 [01:16] Launchpad bug 742185 in gmusicbrowser (Ubuntu) "FFe: Please Sync gmusicbrowser (universe) 1.1.7-1 from Debian unstable (main) (affects: 1) (heat: 8)" [Wishlist,New] https://launchpad.net/bugs/742185 [01:17] changed title to look less actionable :) [01:18] * micahg will have to go hunt for whale food now... [01:27] skaet: anyways, thanks [01:38] micahg, gone in and added comments, and subscribed ubuntu archive admin. [01:38] skaet: no need, it's already in [01:38] heh [01:38] okie [01:38] that's why I changed the title and apologized :) [01:39] :) [01:39] * skaet needs to get that note out now... === slangasek changed the topic of #ubuntu-release to: Beta Freeze in effect! | Natty Narwhal Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release managers with beer | we accept payment in cash, check or whale food | melior malum quod cognoscis [02:22] slangasek: it's because y'all keep stuffing huge builds through arm, and breaking sleeves and stuff [02:22] breaking wut [02:23] and hey, the biggest thing I stuffed through the arm queue today was php5 [02:23] so don't look at me ;) [02:23] well, all y'all [02:23] by which I mean DOKO [02:24] though to be fair, that's mostly because he got a bunch of huge phat packages dropped on his head a few years back [02:24] doko_: gcj-4.5 is also playing shooting-gallery with the armel targets. [02:25] * lamont plays whack-a-mole with the outdated gcj-4.5 (-ubuntu1) on hubbard [02:26] lamont: I'm about to upload chromium in a couple hours :) [02:30] yeah, and I think the double gcj-4.5 upload is due to a multiarch buglet, so you can blame that one on me anyway [02:31] lamont: actually if you're short armel builders, I can save chromium for the weekend [02:36] hmm, is this new, all uploads need manual approval until release or until beta freeze is over? [02:37] slangasek: heh [02:38] anyway, the obviously mad armels are all stuffed back into the race [02:38] the not-obviously mad ones will eventually be obviously mad [02:38] but I need to go do some admin work on my daughter's laptop before she bursts into pouting [02:49] j/48 [09:29] skaet, could i get an NSS upload in to natty (it fixes the same issue as bug 741528, and is a pretty safe change)? [09:29] Launchpad bug 741528 in firefox-3.5 (Ubuntu Karmic) (and 15 other projects) "Compromised Comodo SSL certificates puts users at risk (affects: 1) (heat: 258)" [Medium,Fix released] https://launchpad.net/bugs/741528 [09:37] right, we're going to be wanting queuebot then [11:20] ScottK: mx51> linux-linaro-mx51 is going to need to be promoted to main to make this work. Can you deal with any exception bugs or whatever that you feel are needed for that? [11:21] Sure. [11:21] chrisccoulson: I'd suggest go ahead and upload and someone will review it in the queue. [11:21] ScottK: can I keep on calling it imx51 in d-i, or is mx51 better? [11:21] I don't know the meanings of the terms [11:22] ScottK, thanks [11:22] cjwatson: I'm not sure. I'd say let's try to take the shortest path to success, but I'm not sure. [11:23] it's not significantly harder either way; I'm more interested in what's right [11:23] grepping for imx51 and changing it to mx51 is easy enough [11:23] if that's the right thing to do [11:24] but if they're just different names for the same thing, I'll stick with imx51 [11:24] I'll ask and see if I can find out. [11:24] thanks [11:28] cjwatson, i think linaro implemented something in flash kernel thats called mx51 [11:30] hrm [11:30] we have pleany of imx arches now in the code [11:32] and the efika HW doesnt have a subarch check at all [11:32] (so from flash-kernel perspective the name doesnt matter) [11:34] flash-kernel doesn't care about the d-i image name anyway, only about what archdetect says [11:34] (given that the kernel will likely only run on efika i would suggest calling it efikamx or some such though) [11:34] (and certainly archdetect names should be static) [11:34] hm, if that were the right name shouldn't it also be the kernel package name though? [11:35] I don't really like *inventing* names for d-i images [11:35] I'd rather either stick with current (inertia) or else match the kernel package name [11:35] well, flash-kernel nowadays checks for "imx5"|"mx51" and for "Freescale MX51 Babbage Board", "Freescale MX53 LOCO Board" and for "Genesi Efika MX (Smartbook)" | "Genesi Efika MX (Smarttop)" [11:35] i dont think archdetect has the latter two at all [11:38] so is mx51 a more general term than imx51? [11:38] i think they are different subarches [11:38] http://www.genesi-usa.com/products/efika says "Freescale i.MX515" [11:39] so I guess imx51 is still accurate? [11:39] so confusing [11:39] well, i havent been involved with mx51 at all, thats a pure linaro thing, what i know is that their kernel partially works on the nettop and should also work on the babbage [11:40] * ogra_ checks how their kernel is called [11:40] -mx51 [11:40] so call the subarch that then :) [11:40] ok [11:41] is there any reason to leave the imx51 subarch in place in d-i? [11:41] no [11:41] or can I rename it to mx51? [11:41] ok [11:41] only historical ones probably, but i doubt we'll ever to a ludic image rebuild [11:42] and if so, likely not with this d-i :) [11:42] (god, my typing sucks) [11:43] ScottK: also, is there a bug for this feature in general? if so, can it have a d-i task? [12:42] cjwatson: I'll be sure to add it once I write it. [12:52] cjwatson: It's 742430 [12:53] ta [12:59] skaet: can i get a FFE for new cobbler and openstack snapshot they are both in universe [13:05] zul: Please just file the bugs and we'll look at them. [13:15] cjwatson: I was going to subscribe ubuntu-mir to the bug and ask about promotion after someone approved the FFe. I've discussed this with skaet and she OK'ed it, so I can either wait for her or some other release team member can mark it approved. [13:27] cjwatson: So now I look around and that's not all. I was under the impression that we had images for Kubuntu Mobile on n900 already. We don't. This already has an FFe (724534), but it's kernel, linux-n900 (which is based on Linaro's) is also in Universe. Sigh. [13:27] This image is also on the manifest. [13:28] Do pre-installed images need D-I changes? [13:29] Riddell: ^^^ [13:31] I didn't know we were planning on having images for n900, would be awesome though [13:32] It's been on the manifest for the entire cycle. [13:34] I don't think preinstalled images need d-i, but perhaps ogra could confirm [13:34] only oem-config [13:35] but you need a relatively complex debian-cd setup [13:36] My head hurts. [13:36] ogra_: Does headless need D-I? [13:37] no, as i said above, only uses oem-config [13:37] I thought that was pre-installed. [13:37] But great if it's both. [13:38] cjwatson: If we do the Kubuntu image as a preinstalled image then I don't think we need mx51 support in D-I then. Which also means we don't need to promote the kernels, right? [13:39] you need the kernels for preinstalled too indeed [13:39] well, not on account of d-i at any rate; I don't know what preinstalled images require/prefer in that department [13:39] preinstalled is pretty much identical to live images with its requirements [13:40] ogra_: But does the kernel need to be in Main? [13:40] hmm, i dont think so [13:40] cjwatson, we have a universe mirror antimony can access, right ? [13:40] It does for D-I, so avoiding that for the propsed linaro based images would be a really good thing. [13:41] debian-cd pulls bootloader and kernel from the archive during build so both need to be accessible from the cdimage server (antimony) [13:42] if thats the case it should work without promotion [13:42] antimony can use universe for images that are configured that way, yes [13:42] it's separated a bit to avoid universe leaking into main-only images by accident [13:44] well, the debian-cd post-boot-armel+mx51 script needs to be created (preferably by someone having the HW), it needs to be able to pull the bootloader from the archive and pulls the kernel and initrd from the livefs builder livefs [13:44] -livefs [13:45] i see that kubuntu-mobile already has universe enabled in livecd-rootfs [13:45] It does. [13:45] so it should be able to find the kernel there [13:46] So it's mainly the debian-cd work that needs doing? [13:46] kubuntu hasnt though [13:46] Ah. Right. [13:46] that will likely need more changes [13:47] How about Ubuntu Headless? Is that Main only? [13:47] you need to add a switch for COMP i guess [13:47] yes, headless is main only [13:47] headless) [13:47] LIST="$LIST minimal^ standard^" [13:47] LIVELIST="$LIVE_BOOT_SCRIPTS" [13:47] ;; [13:47] thats all headless sets as defaults [13:48] Because if we could just do the mx51 headless image, then I wouldn't worry about the Kubuntu one for this cycle. [13:48] n900 should be doable already since Kubuntu Mobile already has Universe enabled. [13:48] headless is completely focused on serial though [13:49] Right, but if one edits boot.scr before booting it to remove the oem-config preseed, then it should work, right? [13:50] theoretically yes, untested though [13:50] For mx51 I'd be willing to try it. [13:50] (I've got hardware) [13:50] we currently set console= to serial and preseed debian-installer/framebuffer=false [13:51] theoretically removing both should get you framebuffer oem-config in debconf mode [13:51] So if we could get the image built, I could try it and see. [13:52] If it works, then we can go from there. I think "If you don't want to work via serial, do X, Y, Z" is not an unreasonable release note. === apachelogger is now known as releaselogger [13:55] do you have a bootloader in the archive ? [13:56] and a working boot.scr [14:08] skaet, bug 703230 [14:08] Launchpad bug 703230 in pango1.0 (Debian) (and 2 other projects) ""rm: cannot remove `/usr/share/doc/libpango1.0-0': Is a directory" when updating to 1.28.3-4 (affects: 3) (dups: 3) (heat: 79)" [Unknown,Fix released] https://launchpad.net/bugs/703230 [14:11] ScottK, i see u-boot-linaro-efikamx as well as u-boot-linaro-mx51evk ... with which in turn strikes me that livecd-rootfs wont be able to handle a kernel with linaro in the name OOTB, that will need a change too [14:12] OK. Sorry. Got distracted by $WORK. I'll look at this later. === smspillaz|zzz is now known as smspillaz [16:04] skaet, cjwatson: please approve openjdk-6 and openjdk-6b18 (multiarch library path) === bjf is now known as bjf[afk] [16:52] are unseeded package uploads still welcome? [16:55] micahg: generally yes, though they'll still go through the queue for review and avoidance-of-buildd-load [16:56] ok, also, will the archive be open again after beta or remain moderated, I wasn't sure based on the beta freeze e-mail [16:58] https://wiki.ubuntu.com/BetaFreeze clarifies I think [16:59] we'll be open for 10 days after beta-1, then hard-freeze for beta-2 [17:00] right, that's what I remember from the last 2 cycles, just wanted to make sure something didn't change since we switched to a beta 2 [17:00] eh, relatively close at least :) [17:01] cjwatson: you commented last release about sync with Debian uploads, when should those stop, hard freeze? [17:02] I did? [17:02] cjwatson: yeah, I uploaded enigmail that just basically merged a Debian changelog [17:03] err, wasn't sync, was a merge [17:04] cjwatson: was this upload: https://launchpad.net/ubuntu/+source/enigmail/2:1.1.2-1ubuntu1 [17:05] I'm just wondering where the point is to only sync/merge where we gain something instead of just being in sync or ready for sync [17:11] micahg: that sort of tidy-up should only really run up to Debian import freeze IMO [17:11] later than that there must be better things to do o:) [17:12] substantive syncs are fine whenever a corresponding direct upload with the same change would be, IMO [17:13] cjwatson: ok, will keep in mind for the future, thanks [17:20] may i upload the ftbfs fix for lintian or should i wait until the beta freeze is lifted? === bjf[afk] is now known as bjf [17:29] bdrung: Go ahead and upload. [17:29] Worst case it sits in queue. [17:30] k, done [17:32] bdrung: The tests you dropped: Did Debian drop them too? [17:33] ScottK: no, but they are worthless with our two changes [17:42] bdrung: I don't get the no-upstream-changelog change. IIRC we are shipping at least partial changelog in all packages. [17:43] ScottK: some of the test cases produced the no-upstream-changelog warning, but the testcase didn't expected it. [17:44] Sounds like something that shouldn't be. [17:45] robbiew [17:45] zul: what's up [17:46] ScottK: look at the test cases. they do not carry an upstream changelog. [17:46] OK. [17:46] * bdrung has to leave now. [17:46] Did you file a bug with Debian on this? [17:46] ScottK: not yet, but i will forward it. [17:46] OK. [17:46] robbiew: sorry misfire [17:47] zul: lol [17:47] bdrung: Accepted. [17:50] parted and dmraid should either go together or not at all [18:00] robbiew: why the proposal to drop netboot support for !x86? (https://wiki.ubuntu.com/NattyNarwhal/ReleaseImageContacts) [18:02] slangasek: x86? [18:02] uh [18:02] no, !x86 [18:02] :) [18:02] the netboot images are free as long as we're doing an existing d-i build for the arch [18:02] agreed, netboot support should be kept even if there are no testers IMO - it's actively painful to remove them [18:02] slangasek: I can't test them...and that was a requirement [18:02] slangasek, no ones signed up to test them, d-i's will keep building [18:03] skaet: I can't make them stop publishing without doing violence to d-i [18:03] cjwatson, don't want you to [18:03] "Drop from that wiki page" [18:03] ;) [18:03] where are you proposing to drop them from, then? [18:03] I don't understand [18:04] Not publishing them as part of the 11.04 artifacts. [18:04] This is all back to the UDS discussions on not publishing images we don't test. [18:04] to where? you mean http://cdimage.ubuntu.com/netboot/11.04/ or something? [18:05] yes, [18:05] (those are just links, sure, they're easy to drop) [18:05] I don't want the dailies to stop. [18:05] ok [18:05] :) [18:06] slangasek: while you are at it, please accept openjdk-6 too (and python2.6, python3.1, python3.2) [18:06] doko_: ack, looking [18:06] only openjdk-6 is on the dvd, but not on the cd's [18:09] will try to get binutils fixed over the weekend [18:33] * lamont does another round of armel buildd restoration [19:17] cjwatson: I've uploaded linux-2.6.38-7.39, could I get it approved in the queue please? [19:23] ogasawara: done [19:23] cjwatson: thanks === releaselogger is now known as apachelogger [21:38] FYI ... ^ bikeshed upload I had okay'd with ScottK earlier this week; I missed a one-liner in the Makefile to get the change to take effect [21:38] I'll review it. [21:39] kirkland: Accepted. [21:39] ScottK: thanks [21:39] You're welcome. === bjf is now known as bjf[afk] [22:50] pango1.0 in unapproved is a multiarch upgrade-handling fix we'll want for beta [23:08] slangasek: accepted; I think we want the same the other way round too? [23:09] from the plymouth side it just needs to be made more robust wrt these files being missing; plymouth itself shouldn't depend on pango, only plymouth-label does [23:09] so a bit of tuning is still needed there [23:10] well, OK; I just noticed that new plymouth and old pango1.0 broke, and had been meaning to say something about it [23:11] yeah, we should fix it that way 'round too - I just think a better fix is in order than Breaks [23:11] we shouldn't simply ignore those files being missing since that would result in no text being displayed (AIUI) [23:11] I suppose we could fall back to the text theme or something [23:12] not that text gets displayed currently /anyway/ of course [23:12] I think Breaks might result in a more consistent user experience though [23:12] it gets displayed correctly for me - I can't reproduce that bug, so far [23:12] at least IIRC [23:12] ah - I can reproduce the bug, and will see what I can figure out [23:13] that'd be lovely, thanks - plymouth bugs I can't reproduce are no fun at all [23:13] I should probably check again mind you [23:14] works on nouveau, modulo the need to alt-f1/f7 before it shows anything (which I should investigate, but that's separate) [23:15] that's with plymouth in the initramfs? [23:15] it may be that the hook is missing something else for the initramfs case === bjf[afk] is now known as bjf [23:33] hm, now, I didn't think to try that - no, plymouth is not in the initramfs [23:35] I have some time nowish, I'll wedge together an initramfs test case [23:38] good call, I think that's it [23:39] I don't see the blanked-out areas here like were in the image in the bug, but I don't see text either, having touched /forcefsck [23:39] so that should be amenable to strace debugging [23:44] cool [23:56] the effective diff in the grub2 upload (it's a merge, so maybe not trivial to work out which changelog entries matter) is: [23:57] - Fix crash when extending menu entry line beyond 79 characters [23:57] - Switch back to framebuffer page zero before loading the kernel (basically fixes black-screen that occurred on average 50% of the time when switching VTs on fglrx, and possibly broke other things too) [23:57] - Stop grub-setup being really slow if the first partition isn't near the start of the disk [23:58] plymouth> looks like missing libGL symlink, am poking [23:58] \o/