[04:32] <cjwatson> mapreri: Oh, it did work after all.  http://autopkgtest.ubuntu.com/packages/p/pbuilder/xenial/s390x/
[04:32] <cjwatson> dobey: done
[09:38] <mapreri> cjwatson: oh, thank you.  and nice to see it actually passes the test ;)
[11:54] <LocutusOfBorg> infinity, ping about arrayfire build on arm64 real hw :)
[11:55] <LocutusOfBorg> as you can see now it builds everywhere thanks to you
[13:54] <r0x> Do you ever heard about bulk file compilation?
[15:07] <LocutusOfBorg> hi, somebody please retry arrayfire/arm64 on some real hardware. it is always failing on emulated stac
[15:07] <LocutusOfBorg> stack
[16:46] <jamespage> cjwatson, hmm - ok - I see that's tied up in the ivy/maven explosion...
[20:31] <robert_ancell> popey, do you review click apps?
[20:32] <popey> robert_ancell, i do
[20:32] <popey> got one in the queue?
[20:32] <robert_ancell> popey, I've got the last update of mines marked for manual review. I think it's due to the warning "Could not find compiled binaries for architecture 'multi' lint_architecture_specified_needed"
[20:32] <popey> yeah, the .mo files?
[20:33] <popey> there is a workaround
[20:33] <robert_ancell> popey, yeah, is this a known problem?
[20:33] <popey> yes, there's a bug for it, dholbach filed
[20:33] <robert_ancell> I was hoping you'd know :)
[20:33] <popey> the workaround is set arch to be armhf, i386, amd64 in the manifest
[20:33] <popey> rather than "all"
[20:33] <robert_ancell> popey, I have that
[20:33] <popey> oh
[20:33] <robert_ancell> It worked for the last few uploads, but not this last one
[20:33] <robert_ancell> Wondering if the checker changed
[20:34] <popey> https://bugs.launchpad.net/click-reviewers-tools/+bug/1530894
[20:34] <robert_ancell> popey, ta
[20:35] <robert_ancell> ok, I'll try and re-upload without the arch hack.
[20:36] <popey> i just get a warning
[20:36] <popey> when i review the one in the store
[20:36] <popey> so happy to approve it
[20:37] <popey> you have arch 'multi'
[20:37] <popey> not explicitly listing the arches
[20:37] <robert_ancell> popey, they are listed in the manifest, the resultant click is marked "multi"
[20:37] <popey> odd
[20:37]  * popey approves anyway
[20:37] <popey> done
[20:37] <robert_ancell> popey, ta
[22:27] <momken> Hello
[22:28] <momken> whenever I try to build a deb package from source package I get an error
[22:29] <momken> e.g. I ran "pbuilder-dist trusty build ../gnome-calculator_3.10.2-0ubuntu2.dsc". The dsc file is build by myself after changing source a little for test purposes
[22:30] <momken> but it gets this error in downloading some packages:
[22:30] <dobey> 3.10.3 is already in trusty updates
[22:30] <momken> Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main libgnutls26 amd64 2.12.23-12ubuntu2.3
[22:30] <momken>   404  Not Found [IP: 91.189.92.201 80]
[22:30] <momken> Fetched 6370 kB in 7min 10s (14.8 kB/s)
[22:30] <momken> E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/gnutls26/libgnutls26_2.12.23-12ubuntu2.3_amd64.deb: 404  Not Found [IP: 91.189.92.201 80]
[22:30] <momken> E: Unable to correct for unavailable packages
[22:30] <dobey> pbuilder-dist trusty update
[22:31] <momken> dobey, I know, I am just testing the build process to learn how to build a package
[22:32] <dobey> your apt cache is outdated in the pbuilder chroot. you need to run the update
[22:37] <momken> dobey: Oh, interesting. I couldn't guess that myself. Thank you very much
[22:38] <momken> dobey, Just a question: Are the apt-cache files of my pbuilder located in ~/pbuilder/aptcache/ubuntu/ ?
[22:39] <dobey> no