[09:47] <smb> cyphermox, when you come online. you might want to upload a signed-grub2 along with grub2 to trusty proposed. I am getting partial upgrade-only mode again
[10:22] <infinity> smb: I'll do that right now.
[10:22] <infinity> cyphermox: ^
[10:23] <smb> infinity, ah thanks
[10:27] <infinity> ^--- Self-reviewing that, it's just a grub version bump.
[10:28] <infinity> smb: Iz done.
[10:29] <smb> infinity, ok cool. I will check a bit later for it (and what else is pending in proposed)
[10:51] <infinity> tumbleweed: You around?
[10:53] <infinity> tumbleweed: Who owns the reverse-depends(1) server-side bits?  And, if it's you, could I ask you to add the debian-installer components to the Packages files you consider?
[10:53] <infinity> tumbleweed: Policy doesn't allow namespace overlap between debs and udebs, so it shouldn't cause any issues to just concat it all together.
[10:56] <infinity> tumbleweed: (Well, I suppose it could cause issues in your scripts, depending on how you process Provides, in some curious corner cases, but if that's a concern, you could have it not included in the default component set and require a --di switch or something)
[11:08] <doko> infinity, nodejs block-proposed ping. is this still necessary?
[11:09] <infinity> doko: I think so.  My "rebuild node-*" attempt didn't end well.
[11:09] <infinity> doko: I think we can maybe still get it in, but only if the rdeps get fixed up.  I've not had time to look at the failures, only to see that lots of stuff fails.
[11:10] <infinity> doko: See node-* in https://launchpad.net/~adconrad/+archive/ubuntu/ppa/+packages if you're curious.
[11:16] <doko> looks more like a task for the x-series ...
[11:17] <infinity> doko: Possibly, yes.  Though, it's also a bit curious.  See node-srs in wily-proposed.
[11:17] <infinity> doko: That version was specifically updated for node4 support, and built in Debian, but failed in Ubuntu.
[11:19] <infinity> doko: What's our toolchain delta these days?  Just --as-needed, or also still some tighter security/sanity flags?  Seems weird that these build logs should differ.
[11:19] <infinity> doko: g++-5 in both cases, but the debian CXX object builds cleanly, on Ubuntu, it's warning/error city.
[11:19] <doko> yes, security when the options are not passed using dpkg-buildflags
[11:21]  * infinity wonders if maybe node's build system needs to relax some flags or some such.
[11:21] <infinity> But yes, possibly an x-series task, if no one has the round tuits to dig deeper.
[11:24] <doko> chrisccoulson, infinity: looks like oxide-qt is missing some architecture specific bits, which are present in the other plethora of webkit versions. any reason for that?
[11:24] <infinity> I know nothing of oxide.
[11:25] <infinity> doko: Actually, I wonder if this node issue isn't node at all, but gcc5.  I should retry my rebuild tests without proposed enabled, using the old nodejs.
[11:26] <infinity> doko: (not that I'm saying gcc5 is broken, just that new warnings/error might have blown up the node world)
[11:27] <infinity> Still curious that it's working in Debian, though.
[11:27] <infinity> doko: Do the gcc-5 binary packages include a handy "here's the difference from Debian" note, or do I just need to read the source package and sort it out?
[11:30] <doko> infinity, no, best thing would be the diff of the debian dirs, and then maybe grepping for distrelease / derivative / distribution
[11:30] <infinity> doko: *nod*
[11:32] <chrisccoulson> doko, oxide is not webkit
[11:33] <doko> chrisccoulson, but it ftbfs in webkit ;-P
[11:33] <infinity> It sort of is.
[11:33] <doko> -- Running gyp
[11:33] <doko> gyp: Undefined variable platform_heap_asm_files in /«PKGBUILDDIR»/third_party/chromium/src/third_party/WebKit/Source/platform/blink_platform.gyp
[11:33] <doko> CMake Error at CMakeLists.txt:178 (message):
[11:33] <doko>   Running gyp failed
[11:34] <chrisccoulson> On those architectures, It's missing amongst plenty of other things, compilers for V8
[11:34] <doko> which is what nodejs 4.0 should provide ...
[11:34] <infinity> Which is now a solved problem in upstream V8, so oxide could use an update.
[11:35] <chrisccoulson> we use whatever chrome ships
[11:35] <infinity> Yay for everyone including static versions of everything. :/
[11:35] <infinity> (But bundling libraries is NEVER a problem!)
[11:36] <doko> chrisccoulson, firefox dropped my build fix
[11:36] <chrisccoulson> Trying to deliver frequent updates for something that has a dependency on a library with no stable ABI that's consumed by other applications in the archive would be significantly more of a problem
[11:36] <chrisccoulson> doko, what fix?
[11:37] <doko> http://launchpadlibrarian.net/219814387/firefox_41.0%2Bbuild3-0ubuntu1_41.0%2Bbuild3-0ubuntu2.diff.gz
[11:42] <infinity> doko: Was the pkgconfig thing intentional in that diff, or just an oops?
[11:42] <infinity> doko: (But thanks for the -latomic fix)
[11:43] <infinity> I still consider it a gcc bug that -latomic isn't somehow autodected as needed on platforms where it's required.
[11:43] <doko> oops
[11:43] <infinity> But I think I've seen more than one upstream bug where people disagree with me on that.
[11:43] <infinity> So I've never tried to argue it.
[11:44] <doko> gcc-5 in wily now has a workaround, but as firefox is uploaded to released versions as well, it should carry that patch
[11:44] <infinity> doko: Wasn't the gcc-5 workaround specifically about -latomic for some C++ atomics, not for the entire atomic family?
[11:45] <infinity> doko: As in, powerpc (and a few arches we don't build for) is still a unique snowflake that needs -latomic for pretty much all atomics, even from C.
[11:45] <doko> the former. but this was fixed upstream, but still showing on powerpc only
[11:47] <doko> yes, because the builtins aren't resolved to some instructions, but are left "unimplemented". but some support is missing, like 8byte atomics. that's why I was looking into the insighttoolkit4 build
[11:50] <doko> infinity, did you cancel the gdb build on armhf?
[11:50] <doko> for the test rebuild
[11:50] <infinity> Nope.
[11:51] <infinity> I've only been babysitting the PPC builders, since they're "special", I haven't even looked at armhf.
[11:52] <infinity> I'm tempted to just update the PPC builders to utopic kernels, so gdb and gcc stop killing them, but that feels like a total cop-out when we should be able to debug and fix 3.13.  But no one from either Canonical or IBM has found the time, so... :/
[11:56] <doko> pitti, one more debhelper merge?
[12:29] <pitti> doko: ENOVERB? I don't see any upload in unapproved?
[12:30] <doko> pitti, no, was asking if you would do it? it's in unstable, not ready for upload =)
[12:30] <Laney> I think he's asking for you to put one there
[12:30] <Laney> as TIL
[12:30] <Laney> cheeky
[12:30] <pitti> doko: ah; https://tracker.debian.org/news/717055 looks rather intrusive, and has new depends in universe (dh-strip-nondeterminism)
[12:31] <pitti> that looks a little intrusive at this point; are you looking for a particular fix?
[12:31] <doko> pitti, isn't 05 dropping that?
[12:31] <doko> th dh_movefiles thingy
[12:31] <pitti> not according to https://tracker.debian.org/news/717170
[12:31] <pitti> doko: ack, I'll cherry-pick that then
[12:32] <pitti> doko: https://anonscm.debian.org/cgit/debhelper/debhelper.git/commit/?id=c530fe28c07 ?
[12:33] <doko> pitti, yep
[12:34] <pitti> doko: ack; test-building
[12:39] <pitti> doko: ^
[12:41] <infinity> pitti: +1 for removing the errant .rej file too. :P
[12:41] <pitti> infinity: yeah, some dude forgot that on the last merge :)
[12:41] <pitti> careless people that
[14:06] <cyphermox> davmor2: I'm curious if it's the fact that it was missing a merge, or the fact that it was really really utterly broken, that makes my fixed usb-modeswitch work for you :)
[14:08] <davmor2> cyphermox: sorry how do you mean?  You asked for someone with a huawei to test it so I did
[14:08] <cyphermox> yes
[14:08] <cyphermox> the package was very very broken, not just for huawei
[14:09] <davmor2> cyphermox: I guess people don't use dongles as much so no one noticed
[14:09] <davmor2> cyphermox: the original package you mean not your fixed one right
[14:09] <cyphermox> yes
[14:10] <cyphermox> the original wouldn't trigger for a lot of dongles, I expect. I'm surprised, it doesn't seem like much change to make that not as popular; except maybe tablets.
[14:10] <davmor2> cyphermox: I have a mifi (3g accesspoint) so don't need the dongle
[14:31] <tumbleweed> infinity: yeah, I own them
[14:32] <tumbleweed> infinity: https://code.launchpad.net/~stefanor/+junk/reverse-deps
[14:42] <davmor2> cyphermox: in fact I have to switch the sim out of my mifi and put it in my dongle cause the sim in it is defunct
[14:47] <cyphermox> heh
[14:47] <cyphermox> I washed the best dongle I had once too many times, it no longer works
[14:48] <cyphermox> come to think of it, maybe it was the one good huawei dongle I had too
[14:48] <cyphermox> yup, oops.