[06:21] What happens in cases like https://launchpad.net/ubuntu/+source/tomahawk <-> http://packages.qa.debian.org/t/tomahawk.html ? The Debian package sounded far more interesting, and I had hoped Trusty would get it. [07:29] Unit193: we might want to recommend that Debian change the name of its source package to python-tomahawk :) [07:30] although, well: https://lists.debian.org/debian-wnpp/2013/08/msg01629.html [07:30] so maybe we should consider changing the name of our source package :P [07:31] I'll look into that for u-series; remind me [07:31] Python source packages are normally named without python- though, yeah. Would really make sense to do that, and there won't be a binary package overlap at least. [07:31] I have a merge pending for Unicorn too, if you don't mind. :P [07:32] unless they come out with Python bindings for the Tomahawk player :P [07:33] Unit193: stop living in your delusion that it will be called "Unicorn" [07:33] in any case, we refer to them by their adjectives [07:34] Logan_: Well I do like Uakari better, yes. :D [07:34] that reminds me of that Python distribution, Wakari [07:35] But anywho, do you like dscs? :/ [07:35] no, Anaconda is their distribution; Wakari is the web service [07:35] that's an odd question [07:36] We're on -motu, makes sense to me. [07:36] I guess "poorly-phrased" would be a better adjective [07:36] what does "like" mean? [07:37] Accept, prefer, tolerate, choice of a mix. [07:45] Unit193: don't have a strong opinion either way === mchro- is now known as mchro [13:42] Unit193 and Logan_: The python-foo naming policy applies to binary packages, not source packages. It often makes sense for them to be the same, but not always. === deekej is now known as deekej_ === deekej_ is now known as deekej__ === deekej__ is now known as deekej === DalekSec_ is now known as DalekSec