[01:08] ScottK: None mentioned. === Guest22703 is now known as jbicha === jbicha is now known as Guest72586 === Guest72586 is now known as jbicha_ [06:39] infinity: skaet: bug 960893 [06:39] Launchpad bug 960893 in clutter-1.0 "Clutter is unable to find a valid input backend and abort the execution on ARM" [High,Confirmed] https://launchpad.net/bugs/960893 [06:39] this is the bug that's currently causing clutter-gst to fail [06:40] then empathy will break as well, blocking the arm images [06:40] I'm currently debugging it, but my local build will take a few minutes still to finish [06:41] so will probably continue it tomorrow [06:41] basically clutter is completely broken on arm atm === mmrazik is now known as mmrazik|afk === mmrazik is now known as mmrazik|afk [09:11] infinity: Are the opportunity targets for arm server still valid? [09:31] skaet: hi you got a second, can you look at https://bugs.launchpad.net/unity-2d/+bug/960194 please? [09:31] Launchpad bug 960194 in unity-2d "[UIFe] Use average color of wallpaper to tint launcher/dash/panel/hud" [Low,Confirmed] [09:51] Daviey, so this bug 960311 is a bit funny [09:51] Launchpad bug 960311 in linux "Networking on Dell PowerEdge R300 with Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express is not functional" [High,Incomplete] https://launchpad.net/bugs/960311 [09:52] brendand: oh? [09:52] Daviey, that error pops up kind of non-deterministically [09:52] Daviey, at the moment it seems to effect every release [09:52] brendand: can i sugegst taking this to #ubuntu-kernel .. smb is looking into it. [09:53] Daviey: where do you discuss arm issues? there seems to be no mailing list for them [09:55] Riddell: #ubuntu-arm ? [10:05] Daviey: oh well. [10:13] hey lool, are you the guy who knows about the arm images? where do I ask about them not working? [10:21] hey Riddell [10:23] hello knome [10:23] Riddell, in bug 959504, we asked a permission to tweak the ubuntu studio ubiquity slideshow to fit netbooks (reduce height). can we do the same for xubuntu, as long as we promise to take care of any possible doc screenshots too, which was the condition for US too? do you want me to file another bug just for this (our content is totally the same, we're just modifying the height, and making some things fit a little better)? [10:23] Launchpad bug 959504 in ubiquity-slideshow-ubuntu "[UIFe] ubuntu studio slideshow requires update" [Undecided,Triaged] https://launchpad.net/bugs/959504 [10:24] knome: are there screenshots elsewhere like on websites? [10:24] at least not on ours [10:25] knome: file a bug then and I'll approve it [10:25] okay, thanks [10:25] there is a kernel update (linux) sitting in the queue, this contains the fix for older powerpc UP machines [10:26] apw: multipath-modules-3.2.0-19-generic-di ? [10:26] Riddell, ahh is that why its pending, a new udeb [10:26] apw: got a FFe for that? [10:27] Riddell, ignore me, i thought it was caught in the beta freeze, but thats 2 days out isn't it [10:27] i'll go find out :) [10:27] aye not until tomorrow euro evening [10:29] Riddell, bug 961041 [10:29] Launchpad bug 961041 in ubiquity-slideshow-ubuntu "Xubuntu slideshow doesn't fit netbook screens" [Undecided,New] https://launchpad.net/bugs/961041 [10:30] Riddell, ok it seems although its a new udeb, its actually existing functionality those modules were built-in before and we should always have had the names udeb, anyhow, as we are not in freeze there is no rush and i'll get with the normal process [10:34] Riddell: Hmm I worked on ARM images many months ago; I'm not sure who is in charge for them today, the usual suspects I would hint at would be infinity, ogra_, janimo, NCommander [10:35] Riddell: but it depends on the image; e.g. AC100 might be handled by different people than imx or omap if we still have these [10:36] Riddell, whats the symptom on the arm issue? [10:38] AC100 does have a mailing list btw. [10:39] Riddell: why is #ubuntu-arm not a suitable place to ask? [10:42] knome: accepted! [10:42] Riddell, thanks :) [10:43] apw: my pandaboard doesn't boot (and I've had this conversation plenty on irc and wish to move it to a mailing list) [10:43] Daviey: because of the usual communication differences between irc and mailing lists [10:44] Riddell, kernel issue ? [10:44] apw: probably [10:44] odd i am sure someone is meant to be boot testing those regularly [10:44] Riddell: with the ARM team essentially being divided into the different engineering teams.. i'm not sure a generic list makes sense.. We don't have an amd64 mailing list either :) [10:45] apw: yes they are, and I have also had this conversation lots, and so I would like to move it to a mailing list where it can be explained properly [10:45] Daviey: where should I go then? [10:45] there is a need for a place people can discuss arm issues [10:46] Riddell, fine and you are welcome to go do that, i am not interested per-see the specifici issue, i am interested in there being one and our testing not bringing it to our attention [10:46] the meta issue is more worrying [10:46] Riddell: my first port of call would be ogra_, now on foundations [10:46] apw: blame Grue then for not having enough pandaboards :) [10:47] Daviey: yes, I have already had this conversation with him. next? [10:47] apw: pgraner is working hard on creating a panda lab for automated testing of arm dailies btw. [10:47] Riddell: what was the outcome? [10:48] Daviey: he didn't know the problem [10:48] Daviey, yeah i heard rumors, though i am pretty sure we also test on panda before upload, so if its a kernel issue i am wondering how thats occured [10:48] Riddell: what is the bug number? [10:48] Daviey: I haven't got a bug number because I haven't tracked down a bug [10:49] Riddell: "does not boot" is probably a bug.. having a centralised bug to push data, is probably more useful than irc conversations or a mail. [10:49] :) [10:49] Riddell: even if you raise it against the Ubuntu project, rather than a package. [10:50] Daviey: a bug without a package will never get much attention [10:50] Riddell: right, but it would stop you having to repeat the symptoms.. and the patterns you have followed. A mail referencing a bug, might then be useful. [10:50] Daviey: where would the mail go? [10:51] Riddell: where would you send a mail if you saw the same issue with amd64? [10:51] Riddell: ubuntu-devel, i'd say. [10:51] mm [10:52] Daviey: so if that doesn't work will you give in and accept the need for an ubuntu-arm mailing list? (like you already have an ubuntu-server-arm but that is too specific to be useful to anyone) [10:52] Riddell: setting up ubuntu-server-arm was a mistake IMO. [10:53] mv ubuntu-server-arm ubuntu-arm voila, useful list [10:53] Riddell: I'm not against the idea, but equally - special casing one architecture seems odd to me. [10:53] arm is an odd architecture [10:53] Riddell: and, as i am discovering.. so is i386 with SMP :) [10:54] Riddell: All i have learned so far about this is, 'does not boot' .. is there serial console output? [10:55] Daviey: yes http://starsky.19inch.net/~jr/tmp/precice-arm-boot.txt [10:55] as already reviewed by grue and ogra who say "oh weird, it's trying to use ext3" [11:00] Riddell: can you try a different SD card please? [11:00] Daviey: done [11:01] I've already had this conversation [11:01] it works fine on the validatoin image, it works fine for oneiric, it works fine enough for ubuntu server precise [11:02] Riddell: can you see why having this coversation on a bug would be helpful? :) [11:03] ...or a mailing list [11:03] since I have nothing to file the bug under [11:03] Riddell: $ grep -i CONFIG_EXT4 /boot/config-VERSION | pastebinit ? [11:03] Riddell: linux (Ubuntu) :) [11:04] Daviey: I don't currently have it setup with the broken desktop image [11:05] Riddell: *please* raise a bug with the steps you have done so far, and what you know.. I'll reproduce myself. [11:06] Daviey: nobody has been able to recreate it so far so I suspect you won't be able to [11:06] Riddell: okay, i won't try then.. Problem solved. [11:07] oh do try, I just am skepitcal it'll work alas [11:08] Daviey: but you've booted an ubuntu desktop precise image ? [11:09] Riddell: no, only server.. but i'm willing to go that extra mile for you.. if you raise a bug with steps to reproduce :) [11:10] Daviey: ok, will do [11:14] i'd say if its not booting that filing it against the kernel is appropriate in the first instance, if its bootloader or something else we can punt it [11:16] thanks [11:16] Riddell, and paolo says he booted uses precise on his panda every day, he is downloading todays image to test that [11:16] I know it works for other people, I need it tested with rev 1A pandaboard [11:20] Riddell, thats definatly 1A not A1 ? [11:20] apw: probably A1 [11:21] yes A1 [11:21] Riddell, ok so paolo has the exact same board rev then good [11:21] Riddell: ah, mine is A2 [12:07] Riddell, ok paolo tested his A1 with this image: http://cdimage.ubuntu.com/daily-preinstalled/current/precise-preinstalled-desktop-armhf+omap4.img.gz and it booted and he was able to install it [12:10] Riddell, did we get a linux bug filed yet? i'll add it there too if so [12:13] apw: not yet I'm afraid === greyback is now known as greyback|lunch [12:52] Riddell: multipath-modules> that's not FFe-worthy - it's a bug-fix (regression, module that used to be available in the installer now being missing). I've accepted it. [13:01] thanks cjwatson [13:08] Riddell, arm discussions should happen where powerpc discussions happen ;) [13:08] Riddell, hint ... ubuntu-devel ML :) [13:08] Riddell, whats your issue exactly ? [13:11] ogra_: the same one I've been talking to you and grue about [13:11] bug 961133 [13:11] Launchpad bug 961133 in linux "Ubuntu Desktop ARM Images do not boot on my Pandaboard" [Undecided,Incomplete] https://launchpad.net/bugs/961133 [13:11] and there is still no explanation i can give you, the images work on all my pandas with different SDs [13:11] yes [13:12] i seriously dont know what you boot there, but it cant be an ubuntu image if rootfstype= is set [13:13] there was never any ubuntu image where this option showed up [13:13] it is the ubuntu desktop image for precise [13:14] I change the boot file to remove "quiet splash" [13:14] cant be, unless you hacked it ... you shouldnt get all that kernel messages on serial at all [13:14] ah [13:14] k, that explains the serial output [13:15] but you seem to have changed a lot more [13:15] "vram=16M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait" [13:15] that cant boot [13:15] clearly, that's my whole problem :) [13:15] I move the boot.scr file to Env.txt and remove the first line of non-human readable characters [13:15] well, try a fresh image, dont modify it [13:16] I have [13:16] you also removed the ability to use an initrd [13:16] (it doesnt load one at all) [13:16] I am not aware of doing that [13:16] how did I do that? [13:16] well, your serial output says so [13:17] by putting some weird boot.scr/preEnv.txt in place [13:17] that's not the same thing as me doing it conciously [13:17] https://launchpadlibrarian.net/97732667/precice-arm-boot.txt cleasrly shows that [13:17] I have been doing what grue has told me to, mv boot.scr Env.txt [13:18] it should only load boot.scr ... and then uIamge and uInitrd in that order [13:18] ugh [13:18] that cant work [13:18] boot.scr has a binary header [13:18] yes, which was I told to remove [13:18] well, you have a preEnv.txt there [13:19] seriously, zero out the card and write it with a freshly pulled image [13:19] seriously, I have [13:19] ogra_: how about this log? http://starsky.19inch.net/~jr/tmp/arm/ubuntu-precisebeta1-armhf-noquiet [13:19] same thing [13:20] see the kernel cmdline [13:20] well that's just the same, mv boot.scr Env.txt and remove "quiet splash" [13:20] (also the uBoot messages are very important, please include them in such logs) [13:20] right, dont do that ;) [13:21] give me the serial output of a freshly downloaded and dd'ed image, lets see if it loads initrd [13:21] and to be 100% sure, make sure to zero out the card before dd'ing [13:21] ogra_: ok I'll do that, the machine is currently in use so we'll need to wait for that to finish [13:22] ogra_: what's the command for that? [13:22] well, i'm at the foundationd installer vsprint atm, so i'll work until 22:00 UTC [13:23] sudo dd if=/dev/zero of=/path/to/your/SD/device bs=1M count= [13:23] i would suggest something like 10-20M for the count= value [13:23] that should definutely wipe the boot partiton [13:24] thanks [13:24] the device needs to actually be the device, not a partition [13:25] i.e. if you use a USB reader something like /dev/sdb ... not sdb1 ... or with a native SD reader mmcblk0, not mmcblk0p1 or p2 or whatever [13:25] same thing as if you write the SD [13:26] yes === greyback|lunch is now known as greyback [15:03] pitti, given ubuntu-docs is asking for a week extension to the freeze to get the unity documentation into shape, we're going to be putting pressure on the translators. If we give an exception to the NonLanguagePackTranlationDeadline of a week for just the ubuntu-docs' portion (make it the same as the LanguagePackTranslationDeadline), will that still give us enough time to prep for the CandidateWindowStarts? [15:03] https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule [15:06] skaet: sounds ok to me [15:06] the images that we build on that Thursday won't be final anyway [15:06] we'll need to build new fresh langpacks, and will almost certainly have bug fixes which we want to pull int [15:06] pitti, actually we are trying very hard for those images to potentially be shippable. [15:06] ...o the release [15:07] skaet: well, we can't put the langpack translation deadline and "final image" on the same day [15:07] pitti, its on Tuesday [15:07] :) [15:07] ah [15:08] well, then the ubuntu-docs deadline should be on that day, too [15:08] but still, why cut the bug fix window by a whole week? [15:08] skaet, pitti: just checking but will monday 16th still be ok for GNOME updates? [15:08] it's 3.4.1 tarballs day [15:08] we certainly want potentially releasable images on that day, but that's not the same as "don't allow any bug fixes any more" [15:09] who's the release driver for beta 2? [15:10] ttps://wiki.ubuntu.com/PrecisePangolin/ReleaseTaskSignup [15:10] -> cjwatson and me [15:13] seb128, its after FInalFreeze (12th). [15:13] Hi can someone look again at: https://bugs.launchpad.net/unity-2d/+bug/960194 [15:13] Launchpad bug 960194 in unity-2d "[UIFe] Use average color of wallpaper to tint launcher/dash/panel/hud" [Low,Confirmed] [15:13] skaet, right, that's why I'm asking [15:14] skaet, pitti: that's something we pointed at UDS, we need to get .1 in or we will create a lot of extra work for us or lower quality by missing a month of bug fixes [15:14] I think we need to review the uplaods and check the diffs (we'll do anyway, as we'll be frozen) [15:15] many updates are just translation updates, which are fine; and for the real bug fixes, looking at a particular one makes it a lot easier to say yay or nay than a blanket exception [15:15] as usual, final freeze again just means that uploads are reviewed by the release team [15:16] pitti, I'm just trying to make sure it's still ok, because if it's not we need a plan B, i.e snapshoting or backporting fixes earlier [15:18] Monday should just about make it for the langpack deadline, so we'll catch the updated translations as well [15:20] seb128, pitti, its the bug fixes and regression potential I'm worried about here. Is there any way we can the fixes in before the final freeze? [15:20] skaet: yes, with essentially doubling the work [15:20] skaet, we can, but it might end of having to backport patches over 15 tarballs and spending days of work doing that [15:21] skaet: and working on weekends [15:21] let them shake out, and then just sync to pick up the translations. [15:21] skaet: we can still reject patches which might cause regressions, after all [15:21] pitti, but might we end up rejecting the entire tar ball if the same problems are noticed on the 16th? [15:22] yes, in unapproved it's just "take the whole thing" or "reject" [15:22] but as I expect that most changes should be fine, it's still a net win [15:22] and usually the uploader reviews the changes in advance anyway [15:22] knowing that GNOME is hard frozen [15:22] ups, ignore that [15:22] they will not between .0 and .1 [15:23] but it's on bug fix only mode, usually it's a net win as pitti says [15:23] we really need to get back to the pre-maverick rhythm [15:23] moving the release cycle back three weeks in maverick really hurt our alignment with gnome [15:23] right, we had the same discussion last cycle [15:24] pitti, I think we're getting closer now, but yeah, this sort of glitch is hurting. [15:24] infinity: sorry to bother you, but freeze on it's way, can you take look at: https://bugs.launchpad.net/unity-2d/+bug/960194 [15:24] Launchpad bug 960194 in unity-2d "[UIFe] Use average color of wallpaper to tint launcher/dash/panel/hud" [Low,Confirmed] [15:28] jbicha, ^ what is the impact of this change from greyback - have those screenshots been done already? [15:50] skaet: greyback: we use Unity 3D for screenshots, any changes to Unity 2D that make it more like 3D are awesome [15:50] jbicha_: that's good to know. We've other small visual tweaks to make to close the gap, so I'm happy that isn't causing you any difficulties [15:52] greyback: no, I don't believe that'll be a problem [15:52] greyback, based on jbicha_'s response, consider the change approved (and based on the comments in the bug), I'll go add a note there now. [15:52] jbicha_: ok thank you. I'll contact you if I'm concerned we're pushing it :) [15:52] skaet: thank you [15:52] this is basically all the mention we have of 2D: https://help.ubuntu.com/11.10/ubuntu-help/fallback-mode.html [15:53] jbicha_: awww :( [15:53] greyback: if you have extra text you want to add, just send it to us; we still have another day or so before Docs Freeze :) [15:54] jbicha_: nah I'm good. That does summarize all Unity2D does. [15:55] I'm especially interested in a simple answer to the question "how can I tell whether I'm running 2D or 3D?" [15:56] jbicha_: probably best answer is to look for a shadow under the panel. Other visual differences are much harder to spot. The Alt tab not being fancy is another big indicator [15:56] skaet: thanking you [15:56] oh I already said that. duuuh [15:56] greyback, np. :) [17:37] skaet: good afternoon, I've got a proposal for the Docs Freeze :) [17:38] jbicha_, yup, see the backscroll for discussion of how we can accomodate or not. ;) [17:38] lol [17:38] oh, I missed the backscroll, busy day [17:39] jbicha_, :) anyhow, I'll respond to your email properly, I think there's a plan that can work. [17:40] we probably need to relook at these deadlines at UDS [20:24] AHOI release team! https://lists.ubuntu.com/archives/ubuntu-release/2012-March/000990.html [20:24] (yes, it's me again, and this won't be the last before beta freeze :|) [20:26] it'd be helpful to attach a patch rather than the whole new file [20:29] cjwatson, you're right. I should have asked for the diff, file itself looked straightforward enough, but diff would indeed make it clearer what changed. [20:31] i can create a patch file, but i need to find out how to create one. [20:32] https://wiki.ubuntu.com/FreezeExceptionProcess [20:32] has the commands. :) [20:32] short version: 'diff -u old-file new-file' [20:33] yup..:) [20:34] i added an actual patch file. [20:34] that's not a huge change... :) [20:35] thanks knome. its approved now. [20:35] thanks. i'll commit :) [20:36] err, i don't ;) [20:36] * knome doesn't have rights [20:36] hahah, i'll forward :) [20:44] what specific time is the freeze tomorrow? [20:45] kees, 2100 UTC [20:45] skaet: thanks! [20:45] np [20:46] skaet: we just received an updated seccomp patch set which kees is hoping to land in beta-2 [20:46] skaet: I'm hoping to get a kernel feature in before the freeze, but it sounds like it might need a bit longer to build. [20:46] heh, what ogasawara said :) [20:47] skaet: given the time of freeze tomorrow, if I uploaded a kernel now it might not make it before the deadline [20:47] ogasawara: by "make it" you mean build everything and get the meta package bumped? [20:47] kees: yep [20:47] * kees nods [20:49] ogasawara, if its ready to go, lets get it started, I assume its got goodness/bug fixes that are wanted for beta2. [20:49] skaet: so, I guess I'm asking for a pre-emptive freeze exception for a very long kernel build. :) [20:49] skaet: yeah, I've got some people very interested in trying this goodness (it's been long-awaited) [20:50] skaet: I've got his patches, just want to kick off a few test builds/boots before uploading. it does have goodness that the Chrome security team would like for Beta-2 [20:51] ogaswara, kees - make sure no regressions, and then go ahead. flag when its uploaded, and we'll respin to catch it if it hasn't finished when the dailies kick off tomorrow. [20:51] skaet: ack [20:52] * kees hugs skaet and ogasawara [21:03] zul, have rejected quantum, details in PM [22:14] skaet: FWIW, ARM/Ubuntu/desktop will be unbuildable for beta-2 unless bug 960893 is fixed in time. [22:14] Launchpad bug 960893 in clutter-gst "Clutter is unable to find a valid input backend and abort the execution on ARM" [High,Confirmed] https://launchpad.net/bugs/960893 [22:15] skaet: So, we can remove it from the preinstalled pipeline pending that bug closure. [22:15] skaet: (kubuntu, ubuntu-server, core, etc will all still be fine) [22:16] infinity, thanks for flagging, probably worth reseting the tracker and adding it to there, so we have a record. [22:16] Well, it's not an image bug, so much as a "we can't build images at all" bug. [22:16] So, I'm not sure how trackable that is in the tracker. [22:18] once the bug is fixed, the image can be built (I'll just consider that as a rebuild trigger) [22:18] :) [22:19] pad.ubuntu.com has been reset for beta 2 [22:19] bug added. [22:19] pitti, ^ [22:19] skaet: Check, I ammended you note. [22:20] infinity, yup, saw it flash infront of my eyes, real time. [22:20] MAGIC TECHNOLOGY. [22:20] lol, indeed [22:27] infinity: I got the fix for it [22:27] infinity: just checked and it worked [22:27] infinity: preparing the debdiff now [22:28] skaet: ^ [22:28] rsalveti: <3 [22:28] rsalveti: Do you need it sponsored, or are you a core-dev? [22:28] infinity: would need someone to sponsor [22:28] * skaet hugs rsalveti [22:28] will update the bug and ping you directly [22:28] rsalveti: And is it a fix to clutter itself? [22:29] rsalveti: Cause that's broken right now for other reasons. :P [22:29] yup, fixing the symbols as last upload failed for all archs and disable the egl flag properly [22:29] rsalveti: (I assume your diff is against the latest version) [22:29] yes [22:29] rsalveti: "Fixing" the symbols is the wrong fix for the current FTBFS. [22:29] rsalveti: Unless you mean "making it produce those symbols again by adding the missing configure flag and/or build-deps". [22:30] infinity: yup [22:30] rsalveti: Oh, in that case, shiny. I'll be happy to test and sponsor. [22:30] great, will ping you back in a few [22:31] skaet: BTW, I'm going to jam an eglibc security-fix-only upload in under the wire too. [22:31] skaet: It slipped from my radar for a while, and sbeattie just berated us for it. :P [22:31] infinity, what testing has it had? [22:31] * skaet gets nervous about eglibc and scope of change... [22:31] skaet: The same patches are present in all stable releases. [22:32] skaet: Just not precise. [22:32] skaet: So, I'd say it's had fairly wide testing. ;) [22:32] infinity, that's a little less worrisome. :) thanks. [22:39] infinity: is bug 759545 going to make B2? [22:39] Launchpad bug 759545 in ubuntu-release-notes "user prompted to update unmodified grub configuration during Ubuntu server upgrade" [Undecided,Fix released] https://launchpad.net/bugs/759545 [22:41] Daviey: It'll get looked at during B2 week (and maybe even fixed locally), but I'm not sure if it'll make it in (probably not). [22:42] infinity: what about for release? [22:42] Daviey: It's vaguely near the top of my list, so yeah. [22:43] * Daviey hugs infinity [22:43] infinity: *ideally*, i'd like it fixed before kernel freeze.. so there is a good chance it'll be exposed for real.. :) [22:43] infinity: Go straight to UDS, collect beer. [22:44] (from me) [22:44] I do like beer. [22:44] o/ [22:54] cjwatson, https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/961218 :(( [22:54] Launchpad bug 961218 in debian-installer "Lubuntu and Xubuntu alternate images fail to find kernel modules" [Undecided,New] [23:00] skaet, is precise already frozen? asking when I can start the test rebuild [23:00] lol [23:00] doko: It's not Thursday yet. :P [23:00] doko, everyone else is wanting more time... and you're wanting it to start :D [23:01] doko, its tomorrow at 2100 UTC for the freeze, but I'm expecting the builders to stay busy for a while (kernel rebuild may trail over) [23:03] any chance there's an AA willing to do a srcNEW review for mosh in a week or so? (it's currently in debian, but maintainer has asked me to wait until he rolls a new release before trying anything) [23:03] i can repay you in beer and/or cookies at UDS [23:10] broder: I like cookies. [23:10] infinity: i live in sf, so i can even offer *fresh* cookies :) [23:10] ! [23:11] hmm, ok [23:12] infinity: sounds like we have the beginnings of a deal. i'll start on the other miscellaneous paperwork, and ping you once everything's in order. thanks [23:14] broder: I'll be in SF in a week and a half, if you'd like to try bribery, rather than reward. [23:14] *cough* [23:14] haha. i'll dredge up my cookbooks :) [23:19] * micahg would think it better to start the rebuild before the weekend as there will probably be a lot of buildd downtime [23:20] micahg, there is Friday to start things off. [23:20] indeed [23:27] infinity: just attached the debdiff to the bug: https://launchpadlibrarian.net/97800087/clutter-1.0_1.9.16-0ubuntu2.debdiff [23:27] rsalveti: My hero. [23:27] tested it locally but also pushed to canonical-arm ppa to test it properly [23:27] was also able to build clutter-gst [23:27] on ARMHF [23:27] so that should solve our issues [23:27] also tested with the SGX driver, and clutter seems to be working on EGL again after these changes [23:28] nice news to end the day on, thanks rsalveti! :) === bladernr_ is now known as bladernr_afk [23:29] skaet, i have some news too. we have two more FFe's, which to ubuntu-release was subscribed a moment ago... :) [23:29] rsalveti: I'm guessing that if cogl is brokering GL/EGL, you could have dropped the libgl-mesa build-deps for !arm too? [23:29] rsalveti: But that's nitpicking. :) [23:29] infinity: no, that's related with another thing [23:29] rsalveti: Fair enough. [23:29] we still need it for x86, but can't yet on arm [23:29] rsalveti: awesome, thanks! [23:30] jbicha: hey! [23:30] rsalveti: One last thing, if the egl symbols are now gone, do we need to do an rdep rebuild for everything on ARM that linked to clutter? :/ [23:30] knome, ack [23:31] infinity: I really don't think anyone was using that directly [23:31] Here's hoping. [23:31] But it might be worth double-checking that soon. :P [23:31] yup [23:31] Anyhow. All looks good. [23:31] once that hits the archive we can test the clutter related packages again [23:31] jbicha: I'll sponsor this for rsalveti, unless you felt the urge? [23:32] skaet, was that "you can go ahead"? O:) *whistles* [23:32] and would need to trigger a rebuild for clutter-gst [23:32] once that lands [23:32] rsalveti: Yeah, that's simple enough. [23:32] infinity: feel free to do it if you like [23:32] jbicha: Doing. [23:33] wow, our amd64 builders are really fast [23:34] knome, it means I'm postponing my dinner to go look at it. :) [23:34] thanks! [23:39] knome: gotcha; seed fiddling required, I'll look tomorrow morning [23:40] infinity: if you still didn't push it, wait a sec [23:40] cjwatson, thanks :) [23:40] ppa build finished successfully on amd64 but it seems that the arm build is not going well [23:40] armel [23:40] will check the logs [23:41] rsalveti: Haven't uloaded yet. [23:41] Nor uploaded. [23:41] infinity: ping you back in a few [23:41] Sure. [23:41] I wish I could build as fast as the amd64 builder on arm :-) [23:42] distcc, cross-compile, more hamsters? [23:42] still, io is the problem [23:42] I got an imx6 with sata [23:42] but it's quite unstable [23:43] cjwatson: I imagine the issue is that they both just inherit the platform seeds for that. [23:43] indeed [23:44] Need to figure out how to fix that preferably without having to duplicate the seed. [23:44] Yeah... [23:44]