[04:55] <pitti> Good morning
[04:57] <pitti> rbasak: it actually was removed recently: https://launchpad.net/ubuntu/+source/python-unit/+changelog
[04:58] <pitti> rbasak: so I suppose it needs to be rewritten to use the standard unittest instead?
[06:58] <dholbach> good morning
[08:48] <seb128> diwic, TheMuso, can we get the patch mentioned on https://bugs.launchpad.net/fedora/+source/pulseaudio/+bug/1425447 uploaded to wily?
[08:49] <seb128> diwic, I appreciate it might not fix the issue but it might fix some problems and is better than nothing
[08:49] <TheMuso> seb128: Will take a look first thing tomorrow.
[08:49] <seb128> TheMuso, thanks
[09:08] <diwic> TheMuso, ok, thanks, let me know tomorrow if you have any problems with it
[09:09] <seb128> diwic, TheMuso, thanks
[09:22] <seb128> hum
[09:22] <seb128> gvfs doesn't migrate because of
[09:22] <seb128> autopkgtest for nemo 2.6.7-1: amd64: Pass, armhf: Regression
[09:22] <seb128> but http://autopkgtest.ubuntu.com/packages/n/nemo/wily/armhf/ is green
[09:24] <seb128> Laney, thanks
[09:24] <seb128> (he retried it)
[09:26] <Laney> secret backchannels
[09:26] <Laney> he crossed my palm with silver
[09:26] <seb128> ssssush
[09:27] <pitti> seb128: argh, that again; fixing
[09:31] <seb128> pitti, https://errors.ubuntu.com/problem/7f52b91a3a4b716e9d8f59ad80d8681e8479870a seems like it started with your fix to bug #1476010
[09:31] <seb128> or maybe the fix didn't work
[09:32] <seb128> the errors just have ubuntu10 records
[09:32] <seb128> https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1504897 is a launchpad report
[09:34] <pitti> seb128: that's indeed weird -- we got LP reports for earlier versions (which triggered this bug report in the first place), how come that errors has no single instance of it?
[09:34] <seb128> unsure :-/
[09:35] <pitti> (yeah, was a rhetorical question)
[09:37] <rbasak> pitti: ah, I missed that. Thanks. I'll look into it
[09:38] <rbasak> .
[09:40] <seb128> pitti, right, I know, just e.u.c is suboptimal sometimes (like for those reports it also doesn't include useful logs)
[09:58] <doko> query pitti
[09:58] <doko> pitti, http://autopkgtest.ubuntu.com/packages/s/s3ql/wily/ppc64el/
[09:58] <doko> triggered by python-setuptools, but not run?
[09:59] <doko> same for lava-dispatcher? http://autopkgtest.ubuntu.com/packages/l/lava-dispatcher/wily/amd64/
[10:08] <pitti> doko: ack, fixing
[10:09] <pitti> doko: python-pex got broken by either new wheel or by newer python-pex, so I figure I'll force-skiptest for setuptools
[10:09] <pitti> same for python3.5
[10:11] <doko> yes, I assume it's wheel. python-setuptools is bug fixing only. yeah for upper version dependencies
[10:27] <rbasak> pitti: uploaded fixed nut, hopefully. It's interesting to note that now that Python 2 isn't installed by default on Wily cloud images, my test run also broke for that. I had to explicitly add Python 2 as a test dependency.
[10:27] <rbasak> We're probably going to see many more of these.
[10:28] <pitti> rbasak: ah, thanks
[13:47] <dupondje_> stgraber: there? Just notice your https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1501588 bug
[13:47] <dupondje_> seems like I hit the same problem here
[13:47] <dupondje_> found anything more?
[13:47] <rbasak> slangasek: FYI, deleting python3.4 3.4.3-1ubuntu1~14.04.1 from trusty-updates caused some knock-on effects regressing Docker images in bug 1505164. It seems to me that uploading a higher reverted version might have avoided that, though I don't know that it wouldn't cause other issues from the rebuild.
[13:57] <seb128> tyhicks, hey, I noticed there was some discussions on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566 ... do you know what's the status?
[14:22] <Odd_Bloke> doko: Regarding https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768, Cory Benfield (lukasa on IRC) has just commented on the bug, and let me know that he'd be happy to help with any requests-y/urllib3-y problems that we hit in future.
[14:58] <ricotz> doko, hi, fyi https://launchpad.net/~ricotz/+archive/ubuntu/staging/+sourcepub/5491942/+listing-archive-extra
[15:08] <stgraber> dupondje_: no, I've been traveling and so couldn't do much more tests since I only have a wpa enterprise network at home
[15:10] <stgraber> dupondje_: I tried downgrading wpasupplicant and then a whole bunch of different kernels and even a different linux-firmware, without any luck, I'm sure I missed something but won't be able to try again for another couple of weeks :(
[16:21] <ben___> is it possible to pass arguments to a configure script when building a package via debuild?
[16:23] <cjwatson> ben___: configure arguments are controlled by debian/rules
[16:24] <cjwatson> ben___: may be implicit if it's using the short dh rules style, which is usual these days, but there's an example of adding to the default configure arguments in "man dh"
[16:24] <ben___> cjwatson: thanks
[16:27] <doko> ricotz, why do you ping *me*?
[16:58] <doko> tdaitx, do you still plan to update squid3 to the current subminor version release?
[17:03] <ricotz> doko, sorry, you already merged/updated it in the past so you are likely familiar with it a bit
[17:04] <doko> mehh, won't replace mvo as apt maintainer ...
[17:10] <Laney> but then you get to be a deity
[17:26] <tdaitx> doko, yes, the debdiff is @ https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178
[17:48] <barry> doko: thanks for the urllib3 fix in trusty
[18:42] <slangasek> rbasak: uploading a higher reverted version would also cause problems because the shlibs for libpython3.4 would be wrong; but we'll hopefully have a fix back in trusty-updates shortly
[19:32] <mvo> doko: wuut? apt? could you give me some context please?
[19:35] <mvo> doko: if anything needs fixing/merging in apt, please let me know tomorrow and I will have a look
[20:17] <tyhicks> seb128: I need to make the last set of changes that Raphael pointed out in message #35 and then we should be able to upload the fix to Ubuntu
[20:17] <tyhicks> seb128: me finding time to do that and give it the needed amount of testing will be difficult
[22:42] <seb128> tyhicks, ok, thanks for the reply, I guess it's not going to be fixed for 15.10, hopefully somebody can work on it for the lts though
[23:50] <tyhicks> seb128: I'm confident that I'll have it fixed for the LTS and SRU'ed accordingly