[10:40] <nuvolari> Maaz: tell kbmonkey enjoy: http://www.linuxandlife.com/2011/12/8-text-based-applications-in-linux.html
[10:40] <Maaz> nuvolari: Sure, I'll tell kbmonkey on freenode
[13:13] <inetpro> nuvolari: nice list
[18:03] <octoquad> hi all!
[18:03] <Kilos> hiya superfly octoquad and others
[18:03] <superfly> hi Kilos, octoquad
[18:04] <Kilos> looks like neil either forgot his lappy in ahab land or is taking a break from pc's
[18:04] <Kilos> nuvolari, is als ok daar seun
[18:05] <Kilos> ?
[18:05] <Kilos> Maaz, coffee on
[18:05]  * Maaz flips the salt-timer
[18:09] <Maaz> Coffee's ready for Kilos!
[18:09] <Kilos> Maaz, ty
[18:09] <Maaz> Enjoy Kilos
[18:37] <zeref> YaawwN
[18:55] <zeref> heh, cant use compiz with gnome3
[18:59] <zeref> these "absa" notifications are starting to get annoying
[19:01] <superfly> zeref: Gnome3 or Gnome Shell?
[19:02] <zeref> oops
[19:02] <zeref> the shell
[19:06] <Kilos> night guys. sleep tight
[19:06] <Kilos> good luck tomorrow superfly 
[19:06] <Kilos> be thinking of you
[19:06] <superfly> thanks Kilos
[19:07] <superfly> zeref: Gnome Shell doesn't use compiz, it uses clutter
[19:43] <tumbleweed> superfly: any progress with your packgae?
[19:47] <superfly> tumbleweed: nope, just been reading documentation and stuff
[19:47] <superfly> But I think I do see the differences in the packages - well, at least in the rules files
[20:11] <superfly> tumbleweed: in your opinion, should I upgrade the package format, or rather just fix up the existing package? or are they one and the same thing? ;-)
[20:12] <tumbleweed> superfly: IIRC your package was pretty straight-forward, so not that much work, either way
[20:12] <superfly> Maybe for now fix it up, and then look at upgrading it later?
[20:12] <tumbleweed> personally I'm not a CDBS fan, and prefer not to bring new packages into the archive, using it
[20:12] <tumbleweed> but that's not rejection material
[20:18] <superfly> tumbleweed: is there a way we can do what we do in the Makefile without CDBS?
[20:18]  * tumbleweed tries to find suprefly's code again
[20:19] <tumbleweed> found it
[20:20]  * superfly goes back to see the beets package
[20:20] <superfly> s/see/look at/
[20:21]  * tumbleweed has a quick go at reworking it in debhelper
[20:22] <superfly> tumbleweed: can you pastebin me what you're doing please? so that I have a better understanding of what is going on
[20:43] <tumbleweed> superfly: why are you installing the python bits in a different way to everything else?
[20:44] <superfly> tumbleweed: not too sure... I just followed cocooncrash's lead :-)
[20:44] <tumbleweed> normally one uses a Makfile for everything or setup.py for everything
[20:44] <tumbleweed> (the makefile is allow to call setup.py)
[20:45] <superfly> well, because this is a PyQt4 application, it needs to do a few things that Qt4 apps do, but it also needs to be installed like a Python app
[20:45] <tumbleweed> ok, but you can make your setup.py do whatever you want, it could handle the qt translation stuff
[20:45] <superfly> I looked at the "eric" package (the PyQt4 IDE) and it was extra complicated
[20:46] <tumbleweed> right now to install it, you have to run both setup.py install and make install
[20:46] <superfly> yeah, I figured as much
[20:46] <tumbleweed> usually in that situation, one makes the makefile call setup.py for you
[20:46] <superfly> yeah, I was thinking that would be the way to do it
[20:47] <tumbleweed> general tip: whenever you are writing a series of ;-separated commands (such as a loop) in a makefile, put a set -e; in front of it
[20:47] <tumbleweed> otherwise you'll miss failures
[20:48] <superfly> yeah, I read that in the documentation, but thanks for reminding me 
[20:49] <tumbleweed> you don't need pyversions an dpycompat
[20:52] <tumbleweed> superfly: here's a really quick pass http://paste.debian.net/148367/
[20:53] <tumbleweed> that's dh instead of CDBS, and dh_python2 instead of pysupport
[20:53] <tumbleweed> next, I'll try and move it out of the sysetm python-path, it doesn't need to be importable for everyone
[20:55] <tumbleweed> oh, you need to include the licence statement (not the complete licence, that can be referred to in /usr/share/common-licences) in debian/copyright
[20:55] <superfly> right. that's easy enough to do
[20:56] <tumbleweed> and the format of that file has changed a little since you last use dit
[20:56] <tumbleweed> http://dep.debian.net/deps/dep5/
[20:56] <tumbleweed> btw, dh_python2 can generate the dependencies from requires in the setup.py, if you want
[20:58] <superfly> tumbleweed: it's cool, at this stage we know the dependencies, and they vary slightly from distro to distro, so I think making them manual might be less hassle in the long run
[20:59] <tumbleweed> yeah, same with ibid
[20:59] <tumbleweed> it makes more sense to go the requires route if you are dealing with python people rather than distro people
[21:02] <tumbleweed> python-sqlite... you know python contains sqlite these days, right?
[21:03] <superfly> tumbleweed: yes, but the python-sqlite package is for SQLite 2.8, which the old Windows version of OpenLP uses, so it's there so that people can import from it
[21:03] <superfly> the new version (i.e. this version we're packaging) uses SQLite 3, which is part of Python :-)
[21:04] <tumbleweed> right, you probably only need to Recommend or Suggest it then
[21:04] <tumbleweed> (recommends are installed by default, for almost everyone)
[21:04] <superfly> OK
[21:04] <superfly> yeah, it's only used in 2 or 3 places in the code, and even there it's a conditional import, as it were
[21:05] <superfly> if it's not there, the code doesn't fall over
[21:05] <tumbleweed> ah, right, yes, it shouldn't crash without it
[21:05] <tumbleweed> bonus points if it says "you need ... for this to work"
[21:06] <tumbleweed> oh, the debian packaging includes the makefil
[21:06]  * tumbleweed simplifies further
[21:07] <tumbleweed> http://paste.debian.net/148368/ <- install to a private location
[21:08] <superfly> tumbleweed: well, it says something of the sort :-)
[21:14] <tumbleweed> superfly: http://paste.debian.net/148377/
[21:14] <tumbleweed> got rid of the Makefile, it wasn't doing anything *that* useful, and moved those bits into debian/rules
[21:17] <tumbleweed> the "using two build systems on after another" thing works great in CDBS, but not so well in dh...
[21:40] <chigambamukoko> is everyone here based in Sa?
[21:43] <superfly> mostly
[21:44] <chigambamukoko> I miss home
[21:44] <chigambamukoko> I miss the African Mornings
[22:00] <superfly> tumbleweed: ping
[22:03] <tumbleweed> yup
[22:05] <superfly> tumbleweed: how old is debhelper v7 ?
[22:06] <tumbleweed> Maaz: rmadison debhelper
[22:06] <Maaz> tumbleweed: *blink*
[22:06] <tumbleweed> pish
[22:06] <tumbleweed> it was in lenny, lucid, and hardy-backports
[22:07] <tumbleweed> OTOH, dh_python2 is pretty new. It's only in squeeze, maverick and later
[22:08] <tumbleweed> actually, I'm using debhelper 7.0.50 which wasn't in lenny or hardy-backports (but I think I have a local hardy backport of it somewhere)
[22:08] <tumbleweed> and lenny has a 8.0.0 backport
[22:08] <superfly> We currently use Launchpad's PPA service to build packages for 10.04, and I'm just wondering if I need to keep our current package for the PPA, and this "new" one for Debian
[22:09] <tumbleweed> dh_python2 was supposed to be backported to lucid. Just nobody has doen it yet
[22:10] <tumbleweed> the packages it produces have less moving parts (more reliable), and are faster to install / remove
[22:19] <superfly> tumbleweed: OK, thanks for all of this... I had to do a little manual patching, because one or two small things changed in the package since you last looked at it
[22:19] <superfly> I think everything is fine
[22:20] <tumbleweed> superfly: can you post it somewhere and I'll have a look?
[22:21] <superfly> uh, sure, I'll just commit it and push it up to LP quickly
[22:23] <superfly> tumbleweed: http://bazaar.launchpad.net/~raoul-snyman/openlp/debian-package/files/head:/resources/debian/debian/
[22:25] <tumbleweed> superfly: looking...
[22:25] <tumbleweed> (oh, btw, I did notice a fair number of lintian warnings and errors that should still be dealt with)
[22:27]  * superfly makes a note of that
[22:28]  * tumbleweed likes new packages to be lintian-clean
[22:28] <tumbleweed> then they can stay lintian-clean
[22:28] <superfly> tumbleweed: how do I build this package on my local machine?
[22:28] <superfly> Oh, I'm all for lintian-clean :-)
[22:33] <tumbleweed> superfly: so, it's not entirely trivial because of your odd layout
[22:33] <tumbleweed> normally, it's just "debuild -uc -us" (-uc -us meaning don't both signing)
[22:33] <tumbleweed> or bzr bd -- -uc -us for a bzr branch
[22:35] <tumbleweed> easiest option here is: bzr export ../openlp-1.9.7
[22:35] <tumbleweed> cd ../openlp-1.9.7
[22:35] <tumbleweed> ln -s resources/debian/debian .
[22:35] <tumbleweed> debuild -uc -us
[22:36] <superfly> let me give that a go then
[22:36] <tumbleweed> err and then that'll break because your package has changed from the .orig.tar.gz
[22:36] <tumbleweed> so you may want to temporarly change debian/source/format to 3.0 (native)
[22:36] <superfly> OK
[22:37] <tumbleweed> (keeping your packaging in your main branch, in an unusual subdir, is something tools are not going to like you for)
[22:38] <superfly> what should I do instead, keeping in mind that we have build or packaging systems for mulitple platforms
[22:38] <tumbleweed> don't bother too much about keeping your packaging in the branch up to date
[22:38] <tumbleweed> rather have something workable there
[22:38] <tumbleweed> but keep the packaging for the version in the archive separately
[22:39] <superfly> currently I keep the stuff in bzr up-to-date, and then when an update comes through, I copy it over to a specific location on my VPS, which submits the nightly builds for us
[22:40] <tumbleweed> you don't use launchpad's built-in daily builds?
[22:40] <superfly> no, I think we started this before Launchpad started their built-in daily builds
[22:41] <tumbleweed> also, in practice, daily-build packaging teends to have different needs to in-debian packaging
[22:42] <superfly> tumbleweed: yep, that's why I decided to rather separate them now
[22:42] <superfly> I moved that stuff out to another directory
[22:43] <tumbleweed> superfly: "either version 2 of the licence." ?
[22:43] <superfly> heh
[22:44] <superfly> lemme fix that :-)
[22:45] <tumbleweed> if you meant "or later", change the licence to GPL-2+
[22:46] <superfly> no, I meant GPL2 only
[22:46] <superfly> Just trying to double-check the text
[22:50] <tumbleweed> superfly: lintian says
[22:50] <tumbleweed> P: openlp source: source-contains-prebuilt-windows-binary resources/windows/psvince.dll
[22:50] <tumbleweed> P: openlp source: unknown-copyright-format-uri http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
[22:50] <superfly> OK, the first one I know, but the resources directory should not be packaged
[22:51] <superfly> the second one I'll have to double-check the format
[22:52] <tumbleweed> superfly: the package just contains everything that's in the .orig.tar.gz (i.e. everything you release as your source tarball)
[22:52] <tumbleweed> if that's necessary for your windows builds, you may want to find an alternative, or a way to build it (I don't know what it is)
[22:53] <superfly> right
[22:53] <superfly> I'll check how the orig.tar.gz is built
[22:54] <tumbleweed> of course, we can also construct a separate source tarball for Debian (and debian packages often have to do this, to remove nasty stuff), but that's non-ideal
[22:54] <tumbleweed> *packagers
[22:57] <superfly> well, that stuff shouldn't be in the nightly builds either, so I should really work on how to eliminate it in any case
[22:59] <tumbleweed> oh, whoops, those were only the source package lintian warnings. I let you off lightly :)
[22:59] <superfly> Thanks for all your help tumbleweed. I need to get to bed, a long day ahead of me tomorrow!
[22:59] <tumbleweed> you'll also hit:
[22:59] <tumbleweed> P: openlp: no-upstream-changelog
[22:59] <tumbleweed> W: openlp: embedded-javascript-library usr/share/openlp/openlp/plugins/remotes/html/jquery.js
[22:59] <tumbleweed> W: openlp: binary-without-manpage usr/bin/openlp
[23:00] <tumbleweed> (don't woryr about no-upstream-changelog, if you don't have it, you don't have it)
[23:00] <tumbleweed> np, night.