[06:39] <Quintasan> Good morning.
[07:38] <dholbach> good morning
[07:42] <philipballew> good evining from CA dholbach
[07:45] <dholbach> hi philipballew
[07:46] <philipballew> how's wherever you are dholbach ?
[07:47] <dholbach> Germany's waking up, I guess :)
[07:48] <philipballew> haha, I think you were the man in the packaging how to video i watched 2 weeks ago?
[07:48] <philipballew> unless i am mastaken. the 4 part one or something?
[07:49] <dholbach> yeah, those are a bit dusty already :)
[07:50] <dholbach> but yes, that could well have been me :)
[07:50] <philipballew> they looked a little dusty. is there a newer packaging guide? I have some tar's I need to get goin on? i was thinking the debian maintainers guide?
[08:00] <ajmitch> morning dholbach
[08:00] <dholbach> hey ajmitch
[08:01] <dholbach> there's http://people.canonical.com/~dholbach/packaging-guide/html/ (which is being worked on right now, but at least the introduction should be there)
[08:02] <philipballew> seemes easy enough
[08:04] <philipballew> thanks!
[08:45] <oier__> good morning
[08:45] <oier__> is anybody up for reviewing my package indicator-bug? I already have one advocate and I am looking for second one http://revu.ubuntuwire.com/details.py?upid=9151
[11:13] <oier__> hi again, as many of you already know, I'm looking for a second advocate for my package indicator-bug at http://revu.ubuntuwire.com/details.py?upid=9151
[11:13] <oier__> I would love your help
[12:50] <dnivra> Laney: highvoltage: hey. Did you check out the packaging of openteacher at http://mentors.debian.net/debian/pool/main/o/openteacher/ ?
[12:52] <geser> dnivra: you need at least also python in Build-Depends
[12:52] <geser> have you tried to build it in a pbuilder?
[12:53] <dnivra> geser: I just started it the build process now.
[13:03] <tumbleweed> dnivra: I don't see a setup.py, so you'll need to write one (or use dh_install or dh_python2's undocumented pyinstall feature)
[13:03] <dnivra> that's odd. I was sure I added those fields yesterday. but they're nowhere to be seen! I was sure.
[13:03] <tumbleweed> also it doesn't look architecture specific
[13:04] <tumbleweed> oh, sorry they are documented, just not in the release I was looking at
[13:04] <dnivra> what did you mean by architecture specific?
[13:04] <dnivra> tumbleweed: ^^
[13:05] <tumbleweed> dnivra: you have "Architecture: any", but it should probably be "all"
[13:05] <highvoltage> dnivra: yesterday was a bit crazy, but I haven't forgotten about it
[13:05] <dnivra> highvoltage: no problemo. I was just asking that's all :).
[13:06] <dnivra> Oh right. Will change it.
=== med_out is now known as medberry
=== bambee_ is now known as bambee
=== medberry is now known as med_out
=== yofel_ is now known as yofel
=== s0ultekkie is now known as soultekkie
=== apachelogger is now known as birthdaylogger
[23:25] <wibblymat> I have a question about a package I'm trying to update. The Apache Solr and Lucene projects have been merged upstream so you get both in the same source tarball. If I want to update the solr package to the latest version, should I make both lucene2 and solr source packages be replaced?
=== med_out is now known as medberry
[23:29] <wibblymat> I guess another good question would be about the pacakge name. Lucene is now on version 3.4, which makes lucene2 a bad name. Why lucene2 in the first place? Is it better to have it as lucene3 or just lucene in the future?
[23:49] <cdunlap> Hello.
[23:49] <cdunlap> I have a quick 'man' page question
[23:49] <cdunlap> I am trying to add options to the mountall man page but I can't get a line break to be recognized
[23:50] <cdunlap> I am using gmanedit
[23:50] <cdunlap> is there something special you need to do, that I am obviously missing?