[01:37] <mwhudson> adt-run ... --- qemu ~/adt-yakkety-amd64-cloud.img doesn't work for me at the moment
[01:38] <mwhudson> does it for everyone else? i made the image with adt-buildvm-ubuntu-cloud -r yakkety just now
[01:38] <mwhudson> failure is like this: http://paste.ubuntu.com/16484207/
[08:32] <mwhudson> pitti: is there a process for ignoring an autopkgtest failure for proposed migration? i synced openafs and it failed autopkgtest because of a kernel headers bug
[08:33] <pitti> mwhudson: kmods not building on amd64 is a known issue, kernel team is working on it (amd64 gcc now enables -fPIE by default which kernel modules stumble upon)
[08:33] <pitti> mwhudson: I regularly wave through these packages
[08:34] <pitti> mwhudson: the s390x regression is something else, though
[08:34] <mwhudson> oh i didn't even look at that
[08:35] <mwhudson> pitti: thanks for the yakkety / adt-run tip btw
[08:35] <pitti> mwhudson: no worries; this hit me by surprise too
[08:35] <pitti> was fairly hard to debug actually
[08:37] <pitti> mwhudson: might just be a flaky test of course (most likely), I'll retry
[08:38] <mwhudson> pitti: ok, if not i'll point the debian maintainer at it, he seems responsive at least
[08:38] <pitti> mwhudson: requeued, but test infra is still KDE-DoSed, so will take a while (http://autopkgtest.ubuntu.com/running.shtml)
[08:39] <mwhudson> pitti: yes, just saw that :-)
[08:39] <mwhudson> will see what's happened in the morning i guess
[08:42] <mwhudson> pitti: while you're here <wink> is there a simple way to configure one's adt-virt-qemu images to use an apt proxy?
[08:42] <pitti> mwhudson: which one are you using?
[08:42] <pitti> mwhudson: it has auto-detected and used apt-cacher-ng for ages
[08:42] <mwhudson> oh, adt-buildvm-ubuntu-cloud -p
[08:42] <mwhudson> pitti: i'm using squid-deb-proxy
[08:42] <pitti> mwhudson: and in 3.20.6 I generalized stuff to pick up any kind of proxy
[08:42] <pitti> mwhudson: so, -p or wait for .6 so that it should Just Work™
[08:42] <mwhudson> pitti: ah nice
[08:43] <mwhudson> pitti: will i need to rebuild images in 3.20.6?
[08:43] <pitti> mwhudson: same with adt-build-lx{c,d}
[08:43] <pitti> mwhudson: no, only if you want to change the proxy
[08:43] <mwhudson> ok
[08:43] <mwhudson> nice
[08:43] <mwhudson> now i just need a cloud-images.u.c mirror near me :-)
[08:44] <pitti> mwhudson: the workaround for the python entropy thing is on the adt-virt-qemu side, not in images
[15:35] <ibrahim> i want to know how did the SoftwareCenter issue passed all of the tests and Quality check?!
[15:39] <ibrahim_> although it is now fixed but it had to be spotted while doing any regular checks !
[15:52] <ibrahim_> how did the Software centre bug pass the QA regular check?
[15:57] <ibrahim_> how did the Software centre bug pass the QA regular check?
[17:17] <ibrahim_> how did the Software centre bug pass the QA regular check?
[18:27] <dobey> !patience | ibrahim_
[18:30] <ibrahim_> isn't this the official IRC of ubuntu QA ?? if the guys arent checking the isos before launching it so what are they doing!!?? sorry if i was rude but were are the devels ?? btw sorry for repeating the question
[18:32] <flocculant> ibrahim_: what bug exactly?
[18:32] <gQuigs> ibrahim_: I don't even know what Software center bug you are refferigng to
[18:32] <gQuigs> :P
[18:32] <flocculant> :)
[18:33] <flocculant> ibrahim_: also - this isn't just the Ubuntu QA channel - flavours use it as well
[18:33] <ibrahim_> istalling third party apps didnt work but its now fixed
[18:33] <ibrahim_> *installing
[18:34] <flocculant> ibrahim_: afaik there are 2 types of testing - autotesting and real people doing things
[18:34] <gQuigs> ibrahim_: you mean snappy apps or something else?
[18:34] <gQuigs> or just debs?
[18:34] <flocculant> I reported some stuff from really using it - some got fixed prior to release, some marked as invalid - it dropped in late in the cycle
[18:34] <ibrahim_> no its just  .deb apps
[18:35] <flocculant> gQuigs: there were things like Chrome failing
[18:35] <ibrahim_> it's now fixed but why did they release the distro with such a bug??
[18:35] <flocculant> ibrahim_: not seen properly perhaps?
[18:35] <gQuigs> ibrahim_: I'd check the ISO Testing TestCases
[18:36] <gQuigs> I'm guessing installing from a .deb isn't on the test list
[18:36] <flocculant> gQuigs: I'd be mightily surprised to see anything like that on an ISO testcase
[18:36] <ibrahim_> gQuigs_: Ok!
[18:37] <flocculant> and frankly wouldn't want to see it on there
[18:37] <flocculant> unless it was a 'Check installed apps' thing
[18:38] <gQuigs> they have an ISO base on and then an extended desktop test
[18:38] <flocculant> ibrahim_: I *do* know that the devs where responsive to pings about the software bugs - I contacted people on numerous occasions about things with my Xubuntu hat on
[18:38] <gQuigs> the desktop test should have it I think
[18:38] <flocculant> gQuigs: possibly - I only look at Ubuntu tests to check that a bug is *globalbuntu*
[18:39] <flocculant> so I can tell Xubuntu people it's not us ;)
[18:39] <ibrahim_> btw it was confirmed in xubuntu software cenetre too -_-
[18:40] <flocculant> ibrahim_: probably
[18:40] <ibrahim_> bcz its the same as ubuntu
[18:40] <flocculant> ibrahim_: but we STILL have no idea what bug you're talking about ::)
[18:40] <ibrahim_> hold on while i bring the link
[18:42] <ibrahim_> http://www.omgubuntu.co.uk/2016/04/ubuntu-16-04-deb-software-install-error
[18:42] <ibrahim_> here you go
[18:43] <flocculant> thought so
[18:43] <flocculant> anyway - I have no idea why it was released like that - luckily I'm just a volunteer on a community flavour :p
[21:26] <mwhudson> pitti: uh, did the openafs test re-run on s390x? i can't tell