[10:02] <tjaalton> doko_: I've uploaded a new xmlrpc-c but without the buildflags trickery, hoping that those won't be needed anymore. if it breaks on !x86 I'll add something back that fits the new d/rules
[10:02] <tjaalton> migrated it to dh, it builds fine against the default flags
[10:03] <tjaalton> still waiting for seanius to be announced MIA...
[10:19] <zequence> Hi. Before FF, I'd very much like to have ubuntustudio-live uploaded (a new package that will replace ubuntustudio-live-settings). Should I go through MOTU? bug: 946591
[10:19] <ubot2`> Launchpad bug 946591 in ubuntustudio-live "Add ubuntustudio-live to trusty repositories" [Undecided,Confirmed] https://launchpad.net/bugs/946591
[10:20] <infinity> zequence: If you don't find a victim^Wsponsor before I wake up tomorrow, poke me and I'll help out.
[10:20] <zequence> infinity: Thanks :)
[16:33] <tkamppeter> Can someone tell me why gutenprint 5.2.10~pre1 did not make the transition from trusty-proposed to trusty? I uploaded ~10 other packages today which all made the transition.
[16:34] <Laney> tkamppeter: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gutenprint
[16:35] <cjwatson> https://launchpad.net/ubuntu/+source/gutenprint/5.2.10~pre1-0ubuntu1/+build/5615671
[16:35] <tkamppeter> Laney, is the problem that it does not build on PowerPC?
[16:35] <cjwatson> Correct
[16:36] <tkamppeter> Does it mean that this new version needs to be fixed on PowerPC before FF?
[16:36] <cjwatson> It needs to be fixed soon, not necessarily before FF
[16:36] <cjwatson> But ideally
[16:37] <tkamppeter> cjwatson, can it be put into trusty manually without the PowerPC fix?
[16:37] <cjwatson> No.
[16:37] <cjwatson> I mean it can but I won't.
[16:38] <cjwatson> We don't regress architecture support unless there's no other choice.
[16:38] <cjwatson> And in this case it would have fallout, so I wouldn't be happy with regressing that.
[16:40] <xnox> tkamppeter: the byte_order macros look wrong... let me propose a patch.
[16:41] <Daviey> cjwatson: Whilst I entirely support that model, I thought the effort to keep powerpc as a first class arch failed?
[16:42] <cjwatson> proposed-migration's policy is entirely independent of which architectures are supported/first-class/whatever.
[16:42] <cjwatson> It applies to all architectures.  If you've built before, you have to keep building.
[16:43] <cjwatson> https://wiki.ubuntu.com/ProposedMigration
[16:43] <xnox> tkamppeter: is it just not the case of missing brackets and semicolon as the compiler error says? http://paste.ubuntu.com/6960742/
[16:43] <Daviey> Yes, I get that.. I just thought that was being undone for powerpc.
[16:43] <xnox> tkamppeter: let me try to build it on powerpc.
[16:44] <Daviey> (anyway, it's good :)
[16:45] <xnox> Daviey: sure, but missing ";" and mismatched ")" say a lot about code quality, doesn't it?! =)
[16:45] <cjwatson> No, powerpc not being a first-class architecture long predates proposed-migration even existing; and I don't think it would be overall beneficial to unapply that policy for powerpc.
[16:45] <xnox> Daviey: especially for something in main.
[16:46] <Daviey> Agreed
[16:46] <cjwatson> We can override it in special cases by removing the binaries for powerpc, if there's just no chance of that architecture continuing to be supported for a given package.  But I'm generally reluctant to do that for anything with reverse-dependencies on that architecture, and certainly not when it's just a case of nobody having put even minimal effort into fixing it yet.
[16:46] <mlankhorst> what about arm64? :P
[16:47] <mlankhorst> seeing how long the build queue is
[16:47] <xnox> mlankhorst: only regressions block... and it's reasonable to not regress.
[16:47] <cjwatson> It backs up occasionally, but not severely enough to consider it "not keeping up".
[16:47] <cjwatson> Particularly since arm64 is not exactly an architecture we can decide not to care about.
[16:48] <mlankhorst> sure I can, I'll still try to keep it building though
[17:06] <tkamppeter> xnox, it cannot be simply missing brackets as it builds on other architectures. Perhaps missing macros for PowerPC?
[17:07] <xnox> tkamppeter: yes, it can be just that. cause brackets are missing on bigendian code-path.
[17:07] <xnox> tkamppeter: out of all ports, powerpc is the only one bigendian that we have.
[17:43] <xnox> tkamppeter: tested on a debian powerpc porter box, and it is just missmatch parenthesis and missing semicolon.
[17:43] <xnox> tkamppeter: uploaded.
[17:43] <xnox> tkamppeter: can you upstream the patch? or where do i submit it?
[17:49] <tkamppeter> xnox, post on the Gutenprint mailing list, https://lists.sourceforge.net/lists/listinfo/gimp-print-devel, Gimp-print-devel at lists dot sourceforge dot net
[17:50] <tkamppeter> xnox and thank you for yopur quick fix.
[17:53] <xnox> tkamppeter: no worries, although i thought infinity already fixed one of the printing packages with a missing )); before.
[18:34] <tkamppeter> xnox, thank you very much.
[20:05] <bdmurray> it looks to me like pd-aubio should be sync'ed from debian (it was split out aubio) and multimedia-soundsynthesis depends on it.  Is that correct?
[20:12] <rbasak> I've been waiting all day for a bunch of no-change rebuilds in universe on arm64 to free up migrating php5 past -proposed. The queue doesn't seem to be getting shorter. I presume these builds are getting trumped by arm64 main builds? I'm not sure I've got all the packages (at least two remaining). Will there be any issue with feature freeze here? No features on the rebuilds I suppose; just the new php5 itself is a feature.
[20:16] <stgraber> since it's already been uploaded and just stuck in proposed, that shouldn't be a problem
[20:19] <rbasak> OK, thanks.
[20:59] <cjwatson> rbasak: Sorry, some of that is probably my fault - I was going through the auto-sync dry-run report looking for obvious and reasonably safe syncs of RC bug fixes and such
[21:01] <rbasak> cjwatson: no problem. I guess they'll get built in the end. You already helped enough unsticking it yesterday.