[08:56] <Daviey> Hello friendly release team!  Would someone be able to look at the FFe for bug #727342.  Essentially, a new upstream snapshot which is ahead of Debian Sid because the current version works with Debian kernel, but not ours.  The version string is still less than Sid (due to version scheme change), so we won't have problems syncing when Debian catch up.
[08:56] <ubot4`> Launchpad bug 727342 in open-vm-tools (Ubuntu) "FFE: open-vm-tools kernel module failed to build (affects: 25) (dups: 32) (heat: 352)" [Critical,New] https://launchpad.net/bugs/727342
[08:57] <Daviey> Serge has tried to cherry pick a patch, but it was taking a long time, seemed large (concerns of instability, with a large diff)
[08:58] <Daviey> I'm also concerned launchpad is going to run out of bug numbers, based on the incoming dupes. :)
[11:12] <ScottK> So is the plan for touch related packages and FFe's "Meh, whatever" this cycle?  They seem to be a bit late to the party with a lot of stuff.
[16:43] <slangasek> lamont: what's wrong with errno.h on allspice? http://launchpadlibrarian.net/66510432/buildlog_ubuntu-natty-amd64.e2fsprogs_1.41.14-1ubuntu2_FAILEDTOBUILD.txt.gz
[16:44] <stgraber> skaet: when you have a minute, can you look at: bug 736227 ?
[16:44] <ubot4`> Launchpad bug 736227 in software-center (Ubuntu) "Feature Freeze Exception for weblive support in software-center (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/736227
[16:45]  * skaet looking
[16:48] <doko> slangasek: are there any processor specific optimizations? allspice is newer hardware
[16:48] <slangasek> doko: it's simply failing to find the errno definition... I don't know why that would be processor-specific
[16:48] <lamont> slangasek: because it's now a function, not an extern int.
[16:48] <lamont> ?
[16:49] <lamont> I wonder if it builds on osageorange?
[16:49] <lamont> which should be same-class hardware as allspice
[16:50] <slangasek> lamont: e2fsprogs is /trying/ to include errno.h; it has worked in all my local builds, worked in ppa - but I did see this same failure on one of the metallic ppa buildds (osmium?  thorium?), cleared up when I retried and it got built on a different machine
[16:51] <lamont> slangasek: so I'd expect it to reproduce on osageorange in the natty dchroot.  if not, holler and I'll dig into it on allspice.  ok??
[16:51]  * lamont is neck deep in some other stuff atm
[17:00] <GrueMaster> pitti: I just finished testing the new imx51 kernel for bug 605042.  Works fine.  It can be released at your earliest convenience.
[17:00] <ubot4`> Launchpad bug 605042 in eglibc (Debian) (and 14 other projects) "[armel] java fails to start with eglibc-2.12-0ubuntu4 (affects: 2) (heat: 22)" [Unknown,Unknown] https://launchpad.net/bugs/605042
[17:01] <pitti> GrueMaster: thanks, can you please mark v-done?
[17:02] <GrueMaster> There was no v-needed tag, but sure.
[17:02] <pitti> uh, process fail then
[17:03] <GrueMaster> Why fail?  Kernel works.
[17:03] <slangasek> lamont: ah, didn't recognize osageorange as a porter box name, I don't think I've ever used the x86_64 porterbox :)  right, will dig into it, thanks
[17:03] <pitti> GrueMaster: I mean, it should have gotten a v-needed tag together with the "plz test me" comment
[17:04] <pitti> GrueMaster: (nevermind)
[17:04] <GrueMaster> ah.  :P
[17:05] <GrueMaster> Well, added v-done for scripting purposes.
[17:05] <lamont> slangasek: osageorange is the new ronne
[17:05] <slangasek> ack
[17:11] <doko> GrueMaster: re-openened the eglibc task
[17:11] <GrueMaster> why?
[17:16] <GrueMaster> doko?
[17:17] <doko> GrueMaster: because the back-out of the eglibc checkin should be reverted
[17:19] <slangasek> lamont: not reproduced on osageorange
[17:19] <GrueMaster> Ah.  Now I see it in the changelog.
[17:35] <Daviey> Is anyone from the release team able to look at the FFe posted waaaaay above?
[17:59] <skaet> Daviey,  looked at it earlier this morning, and felt a bit intimidated by the scope of changes, so was hoping that one of the other members of the release team who may have more familiarity with the open-vm-tools could comment.   It looked to me like there were some API changes, and am wondering about the testing with it so far.   Have added comments to that effect into the bug directly.
[18:00] <Daviey> skaet, I appreciate it!
[18:01] <Daviey> hallyn, ^^
[18:16] <lamont> slangasek: sigh
[18:20] <hallyn> skaet: Daviey: AIUI it provides both the server and client so api changes shouldn't matter.  A few commenters on the bug have tested it.  I don't have/use vmware so haven't yet...  i can try installing it next week, but note that 'regression' can't apply to the merge since it's unusable now.
[18:20] <hallyn> skaet: thanks for taking a look :)
[18:23] <slangasek> lamont: when you have a moment, could you tell me what crabapple's hw specs and kernel version are?  Trying to diagnose another unreproducible build failure
[18:23] <lamont> bbg3 for starters
[18:24] <skaet> hallyn,  before we pull it in, would like to know its not going to cause issues with current kernel we're using.
[18:24] <lamont> Processor       : ARMv7 Processor rev 5 (v7l)
[18:24] <lamont> Hardware        : Freescale MX51 Babbage Board
[18:24] <lamont> Linux crabapple 2.6.31-608-imx51 #22-Ubuntu Fri Feb 4 20:50:41 UTC 2011 armv7l GNU/Linux
[18:25] <lamont> slangasek: going to lunch shortly, btw
[18:25] <slangasek> lamont: ok, thanks
[18:25] <hallyn> skaet: oh, i could run ltp on a host with the modules built in.
[18:25] <slangasek> lamont: have a good lunch :)
[18:26] <hallyn> skaet: though i'm off after today, so afraid again that's working into next week :(
[18:27] <pitti> GrueMaster: copied to -updates
[18:27] <GrueMaster> Cool, thanks.
[18:27] <lamont> slangasek: kakadu == crabapple, fwiw
[18:27] <slangasek> lamont: righty-o
[18:28] <skaet> hallyn,  makes me feel a bit better that ltp on a host can run.  :)
[18:28] <lamont> the arm buildds are currently {*aceae,amelanchier}:beaglexm, else bbg3
[18:28] <slangasek> lamont: still, that means I can't pass the bug off to a Linaro assignee who doesn't have kakadu access, AIUI
[18:28] <lamont> slangasek: building a chroot on allspice now, will try e2fsprogs in it after lunch
[18:28] <skaet> hallyn,  on the other hand, pulling it in now, and you not being around for a few days if things go south, doesn't sound like a great idea ;)
[18:29] <GrueMaster> lamont: New kernel for the bb3 pool.  Should help with some issues, namely openjdk.
[18:29] <slangasek> ah, so if the kernel's being updated anyway, perhaps that makes my question go away
[18:30] <lamont> GrueMaster: is that built in -proposed or so?
[18:30] <lamont> dammit... lunch.  afk
[18:31] <lamont> I have a meeting that I need to be back for
[18:32] <hallyn> skaet: yeah, today might not be the best day.  Mind you I don't really have any knowledge on vm-tools anyway, I just attacked it bc it looked like kernel module build fixup work
[18:32] <hallyn> skaet: if we wait until next week, that not necessarily too late?
[18:32] <hallyn> if so, then i'll aim to install vmware so i'm ready for more testing
[18:36] <skaet> hallyn,  its definitely a balancing act.   no easy answers.
[18:39] <hallyn> skaet: ok, well it definately seems too late for this week.  I'll try for monday then.  thanks
[18:39] <hallyn> Daviey: thanks
[18:40] <Daviey> Well, could things with that package go any further south?
[18:40] <Daviey> Am i mistaken that this is stuff for use within a virtual machine?
[18:41] <Daviey> Currently, it's totally non-functional.  Worst case scenario is renders a natty vmware virtual machine non-functional, surely.
[18:41] <hallyn> Daviey: partially.
[18:41] <hallyn> Daviey: the kernel modules go on teh host.  the userspace package sits int he guest and talks to the host
[18:41] <Daviey> Ah, that changes things.
[18:41] <Daviey> I can see the concern now.
[18:41] <hallyn> Daviey: still, the kernel modules would only affect users who install the modules of course
[18:42] <hallyn> yeah so ltp seems a worthwhile check
[18:42] <hallyn> but 'couldn't go any further south' still seems right
[18:51] <Daviey> hallyn, I assume you have installed the package, not just had others test it?
[19:15] <hallyn> Daviey: yes, i've installed it on my machine.  I have not however ran vmware to test the guests
[19:16] <hallyn> Daviey: note that i'm in no way emotionally attached or invested in the bug or the merge, so anyone who wants to test, change, merge something different, or make changes to mine and propose, should feel free :)
[19:17] <Daviey> heh, it's just the bug count that is frustrating my inbox :)
[19:17] <hallyn> lol
[23:14] <slangasek> skaet: multiarch lib uploads progressing; the biggest problem we've seen is that cmake doesn't like having libraries moved outside the search path it knows about, so koffice now FTBFS because /usr/lib/libc.so is gone (no bug report filed yet AFAICS)