[10:32] <lordievader> Good morning.
[10:34] <clivejo> morning lordievader
[10:35] <lordievader> Hey clivejo, how are you?
[10:35] <clivejo> good thanks, and you?
[10:36] <lordievader> Doing okay here :)
[11:02] <clivejo> yofel: would you ping me when you are free
[11:02] <clivejo> I think I have done something bad to kio
[11:31] <blaze> clivejo: what's the problem?
[11:32] <clivejo> I dont know :(
[11:32] <clivejo> Ive confused myself again
[11:32] <blaze> clivejo: you can use other lib package as a tempalte
[11:33] <blaze> *template
[11:33] <clivejo> I tried to fix the unstable branch
[11:33] <clivejo> and realised there was no stable branch
[11:38] <clivejo> this one package is breaking about 100 others :(
[11:39] <clivejo> http://kci.pangea.pub/job/xenial_unstable_kio/
[11:47] <blaze> clivejo: show me control file
[11:48] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/tree/debian/control?h=kubuntu_unstable
[11:55] <blaze> looks fine
[11:56] <clivejo> KCI-W :: Patch fix_kfreebsd_build in VCS but not listed in debian/series file.
[11:56] <clivejo> its commented out
[11:56] <clivejo> should I remove that patch totally?
[11:57] <clivejo> I dont know what that lib does, so the description is just copied
[11:57] <clivejo> its new for 15.19.0
[11:57] <clivejo> which is available in depot now
[12:03] <blaze> clivejo: this patch is not needed in ubuntu
[12:04] <clivejo> grrr
[12:04] <clivejo> what have I done!
[12:04] <blaze> m?
[12:05] <clivejo> I seem to have merged with master somewhere
[12:05] <blaze> and maybe everything is broken because of two new packages libkf5kiogui5 and libkf5kiogui-dev
[12:05] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/tree/debian/changelog?h=kubuntu_unstable
[12:06] <clivejo> how did that first changelog entry get there
[12:06] <BluesKaj> Hiyas all
[12:07] <clivejo> this is xenial branch changelog - http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/tree/debian/changelog?h=kubuntu_xenial_archive
[12:12] <blaze> UNRELEASED is not what we want here :)
[12:13] <clivejo> Im gonna go clear my head
[12:13] <clivejo> so confused
[12:53] <estan> hi folks. there's pyqt5-dev-tools, which installs pyuic5 and pyrcc5, and which depend on python3, but there's no similar packages for developers working with python2 (those scripts would work under both python2 and python3 i think).
[12:54] <estan> i'm packaging my python2/pyqt5 app in a docker container, and this forces me to pull in python3 just to be able to run pyuic5 and pyrcc5 as part of my packaging.
[12:55] <estan> shouldn't there really be a python-pyqt5-dev-tools (for python2) and then the current pyqt5-dev-tools should be renamed to python3-pyqt5-dev-tools?
[12:57] <estan> (as you can see, pyqt5-dev-tools is currently the only package that provides these scripts: http://packages.ubuntu.com/search?searchon=contents&keywords=pyuic5&mode=exactfilename&suite=wily&arch=any , leaving python2 devs having to install python3)
[12:58] <estan> in other distros which doesn't use such aggressive package splitting, the scripts are installed by both the "python2 pyqt5" package and the "python3 pyqt5" package (with the scripts renamed to avoid conflicts).
[13:05] <blaze> estan: better be to address that to Debian Python Modules Team as they're original maintainers of this package
[13:15] <soee> oh lord http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-PRIME-Sync-V3
[13:24] <estan> blaze: ah yes.
[14:47] <clivejo> blaze do you know how to do debian merges?
[14:49] <blaze> clivejo: you don't have access to their git, right?
[14:49] <clivejo> I do
[14:49] <clivejo> Ive done from kmine to konsole on this list
[14:50] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.12.1_xenial.html
[14:50] <clivejo> Id like someone to check them over
[14:50] <blaze> oh, better wait for Philip
[15:54] <ScottK> estan: Our original plan was not to provide PyQt5 for python2 at all since we figured people would be porting to python3 faster than it turned out to be the case.  Please file a bug in the Debian bug tracker and we can take a look at it.
[16:10] <estan> ScottK: ah. alright .
[16:11] <estan> would love to go python3. what's holding us back for this project is VTK, which we don't want to build ourself. but 7.0 is in the process of being packaged, and supports Python 3.
[16:12] <estan> just hope the debian-science-maintainers will make a python3 version of that package.
[16:13] <estan> (e.g. "python3-vtk7")
[16:13] <ScottK> If upstream already supports it, it's not usually that hard.
[16:15] <estan> yea. i e-mailed the guy who's working on it and he seemed homeful they'll have it done at the same time as the other vtk7 packages.
[16:16] <estan> but packaging that is going to take a while, so we need to workg against VTK 6.2 for now , which means python2.
[16:21] <estan> *hopeful.
[16:53] <estan> ScottK: alright, i filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814023
[17:08] <ScottK> Thanks.
[18:51] <clivejo> anyone here?
[18:53] <clivejo> Ive archived a Trello card and I dont know how I did that!
[18:59] <blaze> lol
[19:02] <clivejo> not having a good day today
[19:02] <clivejo> should have never got out of bed!
[19:05] <blaze> relax, just relax
[19:06] <clivejo> think Ill go back to kolab
[19:10] <clivejo> dont think I can break anything there!
[19:18] <ScottK> With a laptop, there's no need to leave bed to cause problems ...
[19:19] <clivejo> I dont like working in bed :P
[19:22] <clivejo> ScottK would you mind checking my mergers?
[19:22] <ScottK> Sorry, I don't know enough about the state of Kubuntu stuff to know if they're right.
[19:22] <ScottK> If you have a specific question, I can try to answer it.
[19:23] <clivejo> do you know why maxy has only updated some apps to 15.12.1 and others to 15.12.0?
[19:25] <clivejo> ScottK: for example - http://anonscm.debian.org/cgit/pkg-kde/applications/zeroconf-ioslave.git/commit/
[19:26] <clivejo> http://download.kde.org/stable/applications/15.12.1/src/zeroconf-ioslave-15.12.1.tar.xz
[19:26] <ScottK> Usually it's because there were no changes in the point release.
[19:26] <clivejo> yet otheres are - http://anonscm.debian.org/cgit/pkg-kde/applications/umbrello.git/commit
[19:27] <clivejo> oh right
[19:27] <clivejo> so we package it regardless of changes?
[19:28] <ScottK> Typically, but I'm not sure it makes sense.
[19:28] <mparillo> clivejo: perhaps you accidentally hit c with a card selected and archived the card? http://webapps.stackexchange.com/questions/24271/how-to-undo-card-archive-on-trello
[19:29] <ScottK> I think Kubuntu needs to decide if they want to sync from Debian when they can and how it impacts the VCS strategy.
[19:29] <clivejo> god knows what I did!
[19:29] <ScottK> Personally, I think you would be better off to sync as much as you can.
[19:29] <clivejo> ScottK: is there a way to auto sync
[19:30] <ScottK> If there's no Ubuntu diff, it's automatic from Debian Unstable prior to Debian Import Freeze.
[19:30] <ScottK> After that or if there's a diff, then it's not automatic.
[19:31] <ScottK> It's trivial for an developer to do.
[19:31] <ScottK> Also it needs to be done manually from Experimental.
[19:32] <clivejo> mparillo: can you see the card again, in backlog?
[19:34] <mparillo> There are maybe a dozen archived cards. Or did you mean you already restored it to backlog? which card?
[19:34] <mparillo> Debian Merges?
[19:34] <clivejo> I think I restored it
[19:34] <mparillo> I see that at the top
[19:34] <clivejo> yup
[19:34] <clivejo> ah good
[19:50] <ScottK> estan: We looked into it and it turns out it's not easy to do what you want without breaking building of existing packages.  Given your situation, you might want to look into equivs as a mechanism to avoid python3 for now.  It's a gross hack, but it may be just the gross hack you need.
[19:57] <estan> ScottK: aha. even making python recommended instead of required is problematic? (see my followup correspondence with Dimitri). if so, then i'll look at equivs (hadn't heard of it, thanks).
[19:57] <ScottK> It is.  I've been reading the bug.
[19:57] <estan> okay. yea i can see how things would break.
[19:58] <estan> the "clean" solution imho would be to have separate packages, e.g. pyqt5-dev-tools -> python3-pyqt5-dev-tools and then a new python2-pyqt5-dev-tools, but Dimitri seemed not so amused with that idea (don't blame him :)).
[19:59] <estan> i mean, if you're going to split these commands into a separate packages, then separate packages for python2 and 3 would be the logical conclusion.
[19:59] <estan> *a separate package.
[20:00] <ScottK> Right, but then duplicating the C++ parts would be weird.
[20:01] <estan> ah yes. can't really give those pythonX- prefixes :/
[20:05] <ScottK> What we discussed was making two new binary packages for the python bits that they existing one would depend on.
[20:05] <ScottK> That would work, but it's excessive for a three line wrapper.
[20:05] <estan> yea. i can understand that.
[20:06] <estan> it's just, to me, having to install python3 just to run a binary (!) is excessive, heh.
[20:06] <estan> and i guess changing the dependency to python2 is out of the question? that has some logic too, it's the lowest version of python that is actually required by the scripts.
[20:06] <estan> (that's what e.g. Arch does: https://www.archlinux.org/packages/extra/x86_64/pyqt5-common/)
[20:07] <ScottK> No.  Arch is fundamentally insane when it comes to Python.
[20:07] <ScottK> They made /usr/bin/python point to a python3 version and that's nuts.
[20:08] <ScottK> It's entirely their fault it was necessary to invent /usr/bin/python2 to work around their idiocy.
[20:08] <estan> yea. i've heard all about that.
[20:08] <estan> (anyway, i was wrong. they don't even register a direct dependency on any python for that package.)
[20:10] <estan> but alright. i'll live with this until we can move our project to python3, or i'll look at equivs.
[20:11] <estan> should be able to switch as soon as a python3-vtk7 is created (in the works).
[20:13] <estan> should i close the bug with a reference to this conversation, or wait for some e-mail feedback?
[20:14] <estan> (yea, equivs seems like a hack, but it would actually be OK. i'd only have it in the Dockerfile, with a big fat comment.)
[20:21] <ScottK> Yep.  That's why I suggested it.
[20:22] <ScottK> Easier if you close it.
[20:39] <estan> alright, closed, thanks for looking into it.
[20:56] <ScottK> No problem.