=== G_ is now known as G
[03:03] <jcjordyn120> i have a idea on the ubiquitty installer, I would like to be able to specify multible mount points on the custom partition screen
[04:48] <pitti> Good morning
=== kickinz1\afk is now known as kickinz1
[07:10] <spineau> doko: hello, I've proposed a patch to solve the update issues with plainbox-provider-resource-generic (https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-resource-generic/+bug/1493356) that with have on some arch.
[07:10] <ubottu> Launchpad bug 1493356 in plainbox-provider-resource-generic (Ubuntu) "plainbox-provider-resource-generic fails to update to 0.19-1 on some architectures" [Undecided,In progress]
[07:27] <dholbach> good morning
[07:41] <zzarr> hello! I installed ubuntu-lxc on a computer running Wily today, but it hangs on login, it seams to be a common problem, is there a solution?
[07:43] <zzarr> ohh, my bad, the package is called unity8-lxc
=== greyback|eod is now known as greyback
[09:02] <pitti> Laney, slangasek: do you understand dracut on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt ?
[09:02] <pitti> Laney, slangasek: we fixed kbd and console-setup yesterday, and now in a wily-proposed chroot "apt-get install dracut-config-generic dracut dracut-config-rescue" works
[09:03] <pitti> The following packages will be REMOVED:
[09:03] <pitti>   initramfs-tools mountall plymouth upstart
[09:03] <pitti> is it somehow complaining about that?
[09:03] <pitti> doko: ^ FYI
[09:03] <pitti> or does this need some hinting?
[09:05] <Laney> pitti: seems to be http://pastebin.ubuntu.com/12319635/
[09:05] <Laney> is there a matchin upload
[09:05] <Laney> matching upload* of initramfs-tools or something?
[09:05] <pitti> Laney: no, we are actually ahead of debian
[09:06] <pitti> Laney: yes, dracut does conflict to initramfs-tools, you can only have one provider of it
[09:06] <pitti> "it" == linux-initramfs-tool
[09:06] <pitti> Laney: i-t is Priority: important, is it due to that?
[09:06] <Laney> so it's a chain from those packages I listed in the intstall line
[09:07] <pitti> Laney: hm, console-setup and kbd got fixed already
[09:07] <pitti> to depend on i-t | l-i-t
[09:09] <pitti> Laney: ah, kbd hasn't made it yet: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kbd
[09:10] <pitti> boot test stuck since yesterday, argh -- /me pokes
[09:10] <pitti> Laney: so I guess that's why
[09:10] <Laney> yes, it's kbd
[09:10] <Laney> If the autohinter doesn't figure this out you can add an easy hint for it
[09:11] <pitti> Laney: I cancelled the boottest (running for 21h), I give it another chance, and if it hangs again I'll force kbd
[09:11] <pitti> then let's see whether that suffices
[09:11] <pitti> Laney: thansk!
[09:13] <doko> jamespage, there are test failures for python-pyeclib on powerpc
[09:13] <Laney> pitti: I wrote https://code.launchpad.net/~laney/ubuntu-archive-tools/update-output-helper/+merge/267970 a few weeks ago to make it a bit easier to debug these things btw
[09:13] <Laney> might be useful to have around
[09:13] <jamespage> doko, yes I know - and I am trying to resolve them
[09:13] <Laney> its current interface needs work but it's still helpful
[09:19] <doko> Laney, norwegian dep-wait (desktop)
[09:19] <Laney> what are you talking about?
[09:19] <doko> https://launchpad.net/ubuntu/+source/norwegian/2.0.10-7
[09:20] <darkxst> hey Laney pitti
[09:22] <pitti> sitter, Riddell: FYI, kwin tests regressed, so yesterday's KDE updates are stuck
[09:23] <Riddell> uh oh
[09:41] <Riddell> pitti: upstream says he knows and is working on how to fix the test rather than the code so I'll set it to ignore, do you know if I should use force-badtest or force-skiptest or both?
[09:41] <pitti> Riddell: I'd use force-badtest on that specific kwin version here
[09:41] <pitti> Riddell: that will unblock the packages that fail on the kwin reverse dependency too
[09:42] <pitti> Riddell: skiptest> unblock only that very package, regardless of hwo many test failures it triggered
[09:42] <pitti> Riddell: badtest> skip that particular test result, for any proposed package that triggers it
[09:42] <Laney> doko: it's going to fail to build anyway: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794152
[09:42] <ubottu> Debian bug 794152 in ispell "ispell: munchlist error detection is overly aggressive" [Important,Open]
[09:42] <Riddell> pitti: thanks
[09:42] <Laney> let's just leave it
[09:43] <Laney> hey darkxst
[09:44] <doko> Laney, then I ftbfs issue would at least document it
[09:44] <Mirv> powerpc chroot problem on fisher01 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+build/7889605
[09:45] <doko> given back
[09:48] <Riddell> pitti: do you know what's up here? http://autopkgtest.ubuntu.com/packages/d/debconf-kde/wily/ppc64el/
[09:48] <Laney> doko: component mismatch too
[09:49] <Laney> no point sorting that out if it won't work anyway
[09:53] <pitti> Riddell: "Temporary failure resolving 'ports.ubuntu.com'
[09:53] <pitti> Riddell: I'll retry
[09:53] <pitti> Riddell: i. e. that was already my retry from this morning's combing of excuses.html, apparently it needs retrying harder :)
[09:53] <Laney> I've seen a fair few of those lately
[09:54] <pitti> yeah, not sure what's up with those wolfe boxes
[09:54] <pitti> cjwatson: ^ wrt that, your last LP status report (thanks for that!) made me hopeful that ppc64el in scalingstack might be a thing RSN?
[09:59] <cjwatson> pitti: It's in the production testing phase, and needs some bits redeployed cleanly, but otherwise almost there
[09:59] <pitti> yay!
[10:04] <pitti> Riddell: http://autopkgtest.ubuntu.com/packages/d/debconf-kde/wily/ppc64el/ green again
[10:41] <Riddell> pitti: lovely
=== alkisg is now known as work_alkisg
[12:31] <jamespage> doko, pyeclib fixed....
=== fionnan_ is now known as fionnan
[13:20] <mdeslaur> slangasek: still no new edk2 in unstable?
=== Elimin8r is now known as Elimin8er
[13:47] <morphis> mterry: ping
[13:48] <mterry> morphis, hello
[13:48] <mterry> I mean pong  :)
[13:48] <morphis> mterry: hey!
[13:48] <morphis> regarding https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441
[13:48] <ubottu> Launchpad bug 1492441 in bluez (Ubuntu) "Cannot connect to 1byone bluetooth keyboard (after successfully pairing)" [Undecided,New]
[13:48] <morphis> can you check if you have the hidp kernel module loaded?
[13:49] <mterry> morphis, ok
[13:50] <mterry> $ lsmod | grep hidp
[13:50] <mterry> hidp                   24576  0
[13:50] <mterry> hid                   118784  1 hidp
[13:50] <mterry> bluetooth             507904  30 bnep,hidp,btbcm,btrtl,btusb,rfcomm,btintel
[13:50] <mterry> morphis, ^
[13:50] <morphis> ok
[14:00] <mterry> doko, man you're killing me with bug 1493037.  like 40 packages
[14:00] <ubottu> bug 1493037 in Ubuntu "lib*-perl dependencies of dh-golang and libtype-tiny-perl" [Undecided,New] https://launchpad.net/bugs/1493037
[14:01] <doko> mterry, that's why I'm filing it myself ;-P
[14:01] <mterry> heh
=== dannf is now known as dannf2
[14:10] <hallyn> gah.  it's a FAIL any time a dist-upgrade resets my xmodmap
=== work_alkisg is now known as alkisg
[14:53] <morphis> bdmurray_: thanks!
=== bdmurray_ is now known as bdmurray
[14:55] <bdmurray> morphis: no problem
[14:55] <doko> jamespage, python-oslo.service b-d's on routes, which is missing a MIR
[14:55] <jamespage> doko, should be just a binary only promotion I think
[14:55] <jamespage> routs is in main
[14:58] <doko> ok, done
[15:02] <jamespage> doko, ta
[15:18] <Teduardo> Howdy, does anyone know when Ubuntu will release a sendmail package that allows you to mitigate the logjam issue?
[15:23] <mdeslaur> Teduardo: do the instructions here not work? https://weakdh.org/sysadmin.html
[15:24] <slangasek> mdeslaur: no, edk2 still stuck in the Debian NEW queue
[15:28] <Teduardo> is there any way to contact a packager for a ubuntu package?
[15:32] <rbasak> Teduardo: packages in Ubuntu are team maintained. Try the ubuntu-devel-discuss@lists.ubuntu.com mailing list, or file a bug if it's an actionable item.
[15:45] <jpds> Teduardo: Also, postfix and exim4 seem to be the MTAs in main
=== greyback is now known as greyback|eod
[18:44] <jrwren> I wish there were links from packages.ubuntu.com to the source on lp
[18:45] <jrwren> oh, the bug reports link is close enough, nevermind me.
[18:49] <sarnold> jrwren: it's nice to have an lpsrc keyword search in firefox: "https://launchpad.net/ubuntu/+source/%s"
[18:50] <sarnold> jrwren: then you just open e.g. lpsrc apparmor to get right to the apparmor package
[18:52] <tarpman> I like pad.lv. → http://pad.lv/u/firefox
[18:56] <jrwren> sarnold: I need that, for sure.
[18:57] <jrwren> sarnold: i just learned duckduckgo has !lp search for launchpad. so close!
[19:00] <sladen> and yet, 10 years on  bugs.launchpad.net/NNNN  still doesn't work
[19:00] <sarnold> jrwren: hah! nice. with a ddg search provider for firefox then that'd just be ddg !lp foo   :)
[19:01] <sarnold> jrwren: I've got a 'ubug' for that, too, http://launchpad.net/bugs/%s
[19:01] <sarnold> jrwren: it's a nice complement to 'dbug' http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%s
[19:03] <tarpman> sarnold: bugs.debian.org/%s ;)
[19:03] <sarnold> tarpman: if only changing firefox search keywords wasn't a pain in the ass...
[19:56] <slangasek> mdeslaur: edk2 unblocked in Debian NEW, so should be syncable to wily shortly
[19:56] <slangasek> ("shortly" == "next 24 hours")
[19:56] <mdeslaur> slangasek: ah, great, thanks
[21:35] <ScottK> sladen: pad.lv/NNNNNN does work.
[21:36] <sladen> ScottK: yes.  I was not questioning that ;-)
[21:37] <ScottK> K.
[21:47] <lifeless> barry: https://bugs.launchpad.net/testtools/+bug/1488710 <- see my comment please
[21:47] <ubottu> Launchpad bug 1488710 in testtools "testtools is incompatible with newer versions of Twisted" [High,Triaged]
[21:48] <barry> lifeless: not sure what you mean by "namespaced"
[21:49] <lifeless> barry: ubuntu-ftbfs or something
[21:49] <lifeless> barry: since its not a ftbfs for anyone else atm
[21:49] <barry> too bad you can't tag bugtasks
[21:50] <lifeless> barry: yes, the its-not-quite-federated data model is a significant limiter here
[21:51] <barry> lifeless: i just removed the tags.  cjwatson's fix gets me almost all the way there.  still two failures; one i have fixed the other not so much yet
[21:52] <lifeless> barry: oh?
[21:52] <barry> lifeless: yep.  the odd one is test_run_list_failed_import
[21:52] <barry> it doesn't raise SystemExit
[21:54] <lifeless> barry: have you put a patch up for the other ?
[21:55] <barry> lifeless: not yet, i want to get it passing first and then i'll comment and/or submit a patch
[21:56] <barry> lifeless: i think i also need to dup #150 to #149
[21:57] <lifeless> done
[21:57] <barry> thx
[21:59] <barry> lifeless: in the meantime, this is the other patch i needed: http://paste.ubuntu.com/12324069/
[22:01] <barry> lifeless: and the last one i'm hunting: http://paste.ubuntu.com/12324090/
[22:03] <lifeless> we're getting a valueerror there?!
[22:04] <lifeless> I'd want to see where thats coming from - it may indicate a deeper problem
[22:04] <barry> lifeless: yes
[22:05] <barry> lifeless: but right now testtools is blocking several other packages so i'm just trying on bandaids that aren't too ugly
[22:05] <lifeless> barry: hang on, what version of testtools is this?
[22:05] <lifeless> that pastebin patches a test tht we don't have in that file...
[22:06] <barry> lifeless: ha.  1.4.0.  i guess that's old.
[22:06] <lifeless> barry: ahahahahahahahahahahahaahhaa]
[22:06] <lifeless> barry: yes. 1.8.0 is current
[22:06] <barry> lifeless: yay for ubuntu deltas :(
[22:06] <lifeless> barry: its not that old - nov last year
[22:06] <barry> and 1.8.0 is in experimental only right now
[22:07] <barry> lifeless: so maybe bandaiding isn't horrible for wily.  we'll definitely sync up again in x.  or should i push through an ffe and try to get 1.8.0 in from experimental?
[22:09] <lifeless> https://github.com/testing-cabal/testtools/compare/testtools-1.4.0...1.8.0
[22:10] <lifeless> so 1.6.0 is when we fixed up all the cruft and started depending on unittest2
[22:10] <lifeless> honestly, nothing is super critical
[22:10] <lifeless> devs are going to pip install anyhow
[22:10] <lifeless> so if 1.4.0 is whats needed for other things packaged in Ubuntu, thats fine
[22:11] <lifeless> there's no security issues that I can see
[22:11] <barry> lifeless: yeah, it's just a matter of bureaucracy ;/
[22:12] <barry> well, i think i'll spend a little more time trying to fix this, and if i get lucky, i'll just upload fixes to ubuntu to unblock everything else.  maybe by the time we sync for x, upstream will release a fixed version
[22:17] <lifeless> barry: heh, upstream works fine on 3.5 and 3.6 already
[22:18] <barry> lifeless: excellent
[22:18] <lifeless> barry: the only issue upstream has is the twisted version
[22:18] <lifeless> barry: and that cjwatson's patch will fix - its in fine tuning mode atm
[22:18] <barry> lifeless: ack
[22:19] <barry> lifeless: can you tell me what that test is supposed to do?
[22:23] <lifeless> barry: the one in your pastebin ?
[22:23] <barry> lifeless: yeah, the one that's still failing.  i *think* i know but it's very difficult to debug why it's not failing in the expected way
[22:24] <lifeless> barry: so prior to 1.6.0 we had code to handle python2's broken handling of non-text .py files
[22:25] <lifeless> barry: that test tests that such a file errors as either a TypeError or SyntaxError. I'm not sure why TypeError is considered valid
[22:25] <lifeless> barry: the test (and the code) is gone in 1.6, because we now use the rolling backport of linecache, which includes patches for tokenize, so it all just works
[22:26] <lifeless> barry: and we have text strings in the line cache, or None, consistently
[22:27] <lifeless> (git diff testtools-1.5.0 testtools-1.6.0 in the source tree will let you see this)
[22:27] <barry> lifeless: is it possible that py 2.7.10 may have changed in a way that causes this test to not error?
[22:27] <barry> lifeless: since i'm guess you never ran 1.4.0 against 2.7.10
[22:30] <lifeless> barry: hmm, I can't see anything trawling through hg
[22:30] <lifeless> barry: though I'm not happy with the issue 23838 patch :)
[22:30] <lifeless> but thats entirely different :>
[22:31] <barry> lifeless: yeah me neither going thru Misc/NEWS
[22:31] <barry> :)
[22:32] <barry> lifeless: since this test goes away in 1.8.0 would i make you puke on your keyboard if i just disabled it in 1.4.0 in wily?
[22:32] <barry> though i'm willing to do a bit more debugging, i want to unblock the other packages.  i know it's horrible
[22:34] <lifeless> barry: I think disabling it is probably fine, I very much doubt that other folk deliberately test with broken binary .py files in their tree
[22:34] <lifeless> we had the test because someone somewhere had that happen to them and testtools blew up
[22:35] <lifeless> so we wanted to blow up in a way that exposed the issue they had, not our innards
[22:35] <barry> lifeless: ack and thanks.  if i can't figure it out by the dinner bell, that's probably what i'll do
[22:35] <lifeless> it would be better to migrate to 1.6.0+, but I appreciate your position
[22:37] <lifeless> (and won't give you grief about it :))
[22:48] <cjwatson> lifeless: sorry, I had to sidetrack into other things, I shall get back to that branch before the end of the week
[22:48] <cjwatson> lifeless: I think I would appreciate it if a testtools developer could file the bug against twisted though, because otherwise I can foresee myself getting into playing telephone-game between two sets of developers and that seems less than ideally productive
[22:51] <lifeless> cjwatson: yup, I shall do that. That comment was mainly what-do-people-thing
[22:51] <lifeless> think
[22:52] <cjwatson> Thanks.  Since they seem to be trending away from exposing what testtools needs, probably good to let them know that somebody cares
[22:55] <lifeless> what I should do
[22:55] <lifeless> is submit a patch to their CI system to cross-test
[22:55] <lifeless> :)
[22:57] <cjwatson> lifeless: PR up to date now I think
[22:58] <cjwatson> Disentangling stuff in LP so that we can upgrade is still an open project :-/
[23:00] <lifeless> thank you