[20:29] <thomi> hi barry, have you got a moment?
[20:29] <barry> thomi: hi!  sure
[20:29] <thomi> I'm trying to package the current version of selenium from pypi into a debian package, and it's a real mess
[20:30] <thomi> debian/watch doesn't seem to work (but looks cvorrect to me), patches in d/patches don't apply to new version, and new version contains binary .so files, that I'm not sure what to do with
[20:30] <thomi> ummmmm
[20:30] <thomi> let's start with that last one :D
[20:30] <barry> yuck
[20:31] <thomi> I guess it's a 'Bad Idea' to put .so files in a source package?
[20:31] <barry> oh, very much so
[20:31] <barry> also policy violating :)
[20:31] <thomi> :(
[20:31] <barry> can they not be built from source?
[20:32] <barry> (or maybe they can, but the build process is hidden upstream?)
[20:33] <thomi> there's certainly no way to build them in the .tar.gz that you download from pypi
[20:33] <barry> that's not exactly free software then is it?
[20:34] <thomi> well, the problem is that the tarball on pypi doesn't match their actual source code
[20:35] <barry> ew
[20:35] <barry> thomi: you might have to build the orig.tar.gz from $vcs branch
[20:35] <thomi> hmm, ok, I'll take a look
[20:36] <thomi> there's some debian server that allows you to download a tarball of a tag from google code, right?
[20:36] <barry> not that i know of
[20:36] <thomi> oh :(
[20:37] <barry> there are various ways to write a d/rules get-orig-source to checkout a tag.  it depends on what upstream is using for vcs
[20:37] <thomi> oh no: "Selenium uses a custom build system called crazyfun"
[20:37]  * thomi bangs head on desk
[20:37] <thomi> oh! it gets better!
[20:37] <barry> i still don't get it.  .so are platform dependent, so how can they possibly include them in their tar.gz?
[20:38] <thomi> "...we are in the process of replacing this with buck"
[20:38] <thomi> barry: they include a .so for every platform
[20:38] <thomi> and every arch
[20:38] <barry> *every* :)
[20:38] <thomi> well
[20:38] <thomi> x86 and amd64
[20:39] <thomi> all the good ones :D
[20:39]  * barry packs up his sparc machine
[20:39] <barry> and arm
[20:39] <thomi> arm? no one uses arm :P
[20:40] <barry> obscure platform
[20:42] <thomi> barry: so the upstream vcs includes bindings for all sorts of languages, including ones we don't support (C#)
[20:42] <thomi> what do I do to those files? Keep them in the source package, or strip them somehow?
[20:43] <barry> i'd probably keep them in the source package, but just ignore them for purposes of debian binary builds
[20:43] <thomi> ok
[20:51] <thomi> barry: what's the best way to aproach this? It sounds like you'd make an empty folder with just a debian/ directory in it... what tools would you use to build it from there? I've never managed to get that working very well
[20:52] <barry> thomi: are you going to try to get this into debian after the freeze?
[20:52] <thomi> barry: hmm.. probably not
[20:53] <thomi> Ii mean, I know I should
[20:53] <thomi> but I don't have the patience TBH
[20:53] <thomi> but *someone* should :D
[20:54] <barry> looks like python-selenium has a debian maintainer.  best to contact them about that
[20:54] <barry> ah, it's even in sid/non-free, and way behind upstream
[20:54] <barry> and behind in ubuntu
[20:54] <thomi> barry: Sascha Girrulat ?
[20:55] <barry> yeah
[20:55] <thomi> why is it in nonfree?
[20:55] <barry> thomi: no idea, but if it's got those .so's in it back then, that would probably explain it
[20:55] <thomi> hmmm
[20:57] <barry> thomi: so i'd probably start with `bzr branch ubuntu:python-selenium` and work from that branch.  maybe.  could be a lot of trouble if you need tons of modifications.  yeah, i guess this isn't going to be much fun
[20:57] <barry> thomi: if you start from scratch, create an empty debian/ and steal as much as you can from the ubuntu package
[20:58] <thomi> barry: that should be the same as what 'apt-get source python-selenium'; gets me, right?
[20:58] <barry> thomi: you might also reach out on ubuntu-devel and ubuntu-motu to see if anyone can give you a hand
[20:58] <barry> thomi: more or less.  could be less if the udd importer is broken on that package ;)
[20:58] <barry> so yes, you could start with that
[20:59] <barry> (and you can always create a bzr branch from the .dsc)
[20:59] <barry> just to have some local version control to make your life easier, not for any upload requirements or what not
[21:01] <thomi> ok, if i'm using upstream vcs as the source then there's not much I can steal  from the existing package
[21:13] <barry> it's a start at least
[21:13] <barry> maybe only d/rules will need to be rewritten
[21:13] <thomi> reading the git section of https://wiki.debian.org/onlyjob/get-orig-source scares me
[21:14] <barry> upstream is git?
[21:14] <thomi> yeah
[21:14] <thomi> https://code.google.com/p/selenium/source/list
[21:14] <barry> man, i know there are simpler examples.  not sure i can put my finger on one though
[21:15] <thomi> oooh! google code exports tarballs for every tag
[21:15] <thomi> such as: https://selenium.googlecode.com/archive/selenium-2.44.0.tar.gz
[21:15] <barry> hey, that could be much easier
[21:15] <thomi> so I can use d/watch after all
[21:15] <barry> cool!
[21:22] <thomi> barry: neither of their (two) build systems are packaged. Do I need to package those first?
[21:23] <barry> sadly yes
[21:23]  * thomi dies a little on the inside
[21:25] <thomi> ....they invoke their build systems by running a java .jar file
[21:25] <thomi> I feel like this source code is mocking me now
[21:26] <barry> it's certainly laughing at you from hell
[22:50] <balloons> veebers, adding json should be this simple :-) https://code.launchpad.net/~nskaggs/autopilot/add-json-build/+merge/247912
[22:50]  * veebers looks
[22:50] <veebers> balloons: heh nice, that is simple :-) /me tests
[22:55] <veebers> balloons: looks good to me
[23:11] <balloons> veebers, awesome :-)