[03:49] <Logan_> infinity: can you please explain how this is possible? https://buildd.debian.org/status/logs.php?pkg=libquantum&arch=ppc64el
[03:50] <StevenK> Logan_: It was retried, and built sucessfully?
[03:51] <Logan_> StevenK: well yes, but why did it work the second time? I thought it would require an autoreconf to build properly on ppc64el
[03:52] <StevenK> Logan_: It symlinks /usr/share/misc/config.{guess,sub} into the build dir, so perhaps autoconf was changed on ppc64el ?
[04:18] <Logan_> StevenK: it was a libtool issue the first time, not a config.{sub,guess} issue
[07:06] <Unit193> pitti: Good morning.
[07:53] <infinity> Logan_: That's curious, since it seemed to magically fix its libtool macros.
[09:44] <cjwatson> Logan_,infinity,StevenK: there was something central that improved the chances a good deal for packages that weren't reconfigured; I think https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760395
[09:45] <cjwatson> but I wonder if it built correctly
[09:46] <cjwatson> p/usr/lib/libquantum.so.8.0.0: ELF 64-bit LSB shared object, 64-bit PowerPC or cisco 7500, version 1 (SYSV), dynamically linked, BuildID[sha1]=d286f4ec7d9af649b7a26e1b938e6d4f1e65c297, stripped
[09:46] <cjwatson> looks ok
[09:47] <cjwatson> doesn't seem to actually end up passing -m elf64ppc to the linker
[10:00] <infinity> cjwatson: I'm confused as to how that would fix the libtool macro issue...
[10:00] <cjwatson> because ld -m elf64ppc now magically works I think
[10:00] <cjwatson> you can see in the build output that it's using ld -m elf64ppc both times
[10:00] <infinity> cjwatson: So all our libtool mangling is unnecessary now?
[10:01] <cjwatson> I don't know enough to go that far
[10:01] <cjwatson> but it seems to have let us get away with more
[10:01] <infinity> Cause yeah, that should be -m elf64lppc
[10:01] <cjwatson> I'm still a lot more comfortable with autoreconfing anyway
[10:01] <infinity> Note the 'l'.
[10:01] <cjwatson> e.g. because I'm not sure whether that -m elf64ppc might ever leak through into actual build commands
[10:02] <cjwatson> so I certainly wouldn't go dropping the patches we have
[10:02] <infinity> I guess I'm scared that it would be misbuilding things as the wrong endian.
[10:02] <infinity> Anyhow, lunch.
[10:10] <mlankhorst> ugh..
[10:10] <mlankhorst> infinity: I don't suppose I could upgrade libgbm1 in trusty once? :P
[11:00] <infinity> mlankhorst: Upgrade it to what, and why?
[11:09] <mlankhorst> version in utopic, conversion to dri-loader should hopefully mean no further upgrades needed
[11:21] <mlankhorst> oh hm. trusty might be recent enough
[11:21] <mlankhorst> I'll give it a shot, this would simplify things a lot. :)
[11:58] <rbasak> jpds: as strongswan 5.1.3-0ubuntu1 is unlikely to get fixed this week, perhaps we can just delete it from utopic-proposed and release Utopic with 5.1.2-0ubuntu2 as it is in Trusty. Then there won't be any additional maintenance burden over Trusty, and we can merge Debian's 5.2.0-2 next cycle. Any objection?
[11:58] <rbasak> (this assumes it rebuilds OK on Utopic, although I don't think we'll actually have to do that)
[12:45] <Riddell> pitti: is there a tech board meeting tomorrow?
[13:32] <pitti> Riddell: there is, yes
[13:33] <pitti> darkxst: FYI, systemd 215 (with all Ubuntu changes) in my PPA: https://plus.google.com/u/0/107564545827215425270/posts/DaDxtzbWWsH
[13:40] <Riddell> pitti: what time? where?
[14:26] <pitti> Riddell: 15:30 UTC in #ubuntu-meeting-2
[14:27] <mvo> Riddell: thanks for the app-install-data reminder, its uploaded now
[14:59] <Riddell> pitti: golly, that isn't documented anywhere
[15:07] <pitti> Riddell: ah right, https://wiki.ubuntu.com/TechnicalBoardAgenda is lagging behind
[15:09] <Riddell> pitti: nor is http://fridge.ubuntu.com/calendars/
[15:40] <rbasak> pitti: while you're looking at that, it'd be nice if it were easier to find logs or minutes of previous minutes. They aren't all there. Just a link added every week to the irc logs would be useful - I struggled to find that the other week.
[16:39] <jderose> so i'm trying to get a trace of this https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1366351 with glib, gtk dbg packages installed... but apport isn't letting me because it's already been reported so many times (although i don't think with the dbg packages installed)
[16:39] <jderose> is there a way for me to force apport to file the bug anyway, or at least attach a new trace to lp:1366351 ?
[16:54] <sarnold> jderose: try apport-collect 1366351
[16:55] <jderose> sarnold: just figured that out and did, but thank you!
[16:56] <jderose> sarnold: so the warnings  from apport-collect didn't make it clear to me what the prefer/most helpful workflow is here. did i make a mess of lp:1366351? should i have done anything differently?
[16:58] <sarnold> jderose: heh, I was just about to say "probably fine" but I see Logan_ disagrees :) I'll defer to him, sorry for steering you that way..
[17:04] <jderose> sarnold: yeah, i just saw that. oops :P
[19:50] <Logan_> infinity: per that discussion, does that mean that an autoreconf should still happen for e.g. libquantum?
[19:51] <Logan_> doko too ^
[19:51] <doko> ENOCLUE which discussion
[19:52] <Logan_> oh, about adding the ppc64el target to binutils
[19:53] <Logan_> doko: https://www.dropbox.com/s/sixz1k1fnz5elg0/Screenshot%202014-10-13%2015.53.20.png?dl=0
[19:53] <Logan_> I had noticed that libquantum built successfully after a second try, which confused me: https://buildd.debian.org/status/logs.php?pkg=libquantum&ver=1.1.1-3&arch=ppc64el
[20:31] <cjwatson> Logan_: I would be inclined to keep it
[20:31] <cjwatson> Logan_: It's the right thing to do anyway and may help with future ports
[20:33] <jungle_bg_> There is a problem with the git repo for the saucy kernal source. I have been trying to get the ubuntu kernal source for saucy. This failed for me and someone else in #ubuntu confirmed:  git clone git://kernel.ubuntu.com/ubuntu/ubuntu-saucy.git
[20:40] <cjwatson> jungle_bg_: Probably best to ask on #ubuntu-kernel.
[20:53] <darkxst> pitti, great, I will try it out
[22:27] <slycheese> Does anyone know if it's possible to present as a USB client on hardware running XUbunu (via OTG)?
[23:38] <hallyn> slangasek: drat!  somehow the cgmanager in unstable ended up ont having the patch it needed.  (my local copy did, so something sad happened)  I've pushed 0.33-2 to mentors containing the needed patch for debian bug 757348
[23:38] <hallyn> :(
[23:39]  * hallyn forces himself to shut down before he misses the whole night's sleep
[23:45] <xnox> bdmurray: thanks =)