[12:28] <sistpoty> hi folks
[12:29] <ajmitch> hi sistpoty 
[12:29] <sistpoty> hi ajmitch
[12:29] <sistpoty> ajmitch: I get bounces from you via tiber
[12:31] <ajmitch> yeah, dsl is down at home, I fetched 100 or so mails elsewhere but exim was misconfigured
[12:31] <ajmitch> got them alright now, but I have to probably reenable bug mail
[12:31] <sistpoty> oh
[12:42] <jdong> quick question, what happened to the "request backport in" button on launchpad?
[12:42] <jdong> I'd like to close 70154 in Feisty but keep a Dapper and Edgy task on it open
[12:43] <fdoving> jdong: tried #launchpad ? 
[12:43] <jdong> will do
[12:44] <fdoving> they are usually very helpfull, don't know if this is the best time, though.. 
[12:45] <jdong> right
[12:46] <PriceChild> fdoving: why what's happenning?
[12:47] <fdoving> the clock is close to 0100 CET.
[12:47] <fdoving> and it's monday tomorrow.
[12:47] <fdoving> though, i don't know where the launchpad devs live.
[12:48] <PriceChild> oh ok
[12:48] <jdong> late is no excuse :D
[12:48] <jdong> lol
[12:48] <somerville32> mpt is around
[12:48] <somerville32> Lots of activity in #launchpad
[12:48] <somerville32> oh, lol
[12:49] <somerville32> Thats you
[12:49] <fdoving> there you go.. i'm off to bed.
[12:49] <fdoving> nite.
[01:40] <sebest> hello, is there a way to remove a package from REVU?
[01:41] <LaserJock> sebest: you can request it to be removed
[01:42] <sebest> LaserJock: oki, i'd like to remove "ps-watcher" because it's in feisty from debian
[01:42] <sebest> LaserJock: i have another question: i did a package, and it was accepted in universe, now a new upstream release is out, how can i have it include, should i post it to REVU again?
[01:43] <sistpoty> sebest: please do so
[01:43] <LaserJock> sebest: you could file a bug against the package and give a URL to a new source package
[01:44] <sebest> sistpoty, LaserJock: which solution is better? launchpad or REVU?
[01:44] <sistpoty> sebest: the best solution is to put it to a dgettable url and ping a motu with that url ;)
[01:45] <sistpoty> sebest: so either revu or a different place will do
[01:45] <LaserJock> I'm not really sure, but if you do use LP make sure to subscribe the ubuntu-universe-sponsors team
[01:45] <sistpoty> sebest: though revu has the advantage that a reviewer can make comments (same goes for a bug in lp)
[01:45] <sistpoty> hi LaserJock btw.
[01:46] <LaserJock> hi sistpoty, shouldn't you be in bed?
[01:46] <sistpoty> LaserJock: yes... probably in half an hour or so ;)
[01:46] <sistpoty> didn't do my security bug fix for today yet :)
[01:47] <sebest> sistpoty: i think i'm in trouble: "Error '553 Could not create file.'"
[01:47] <sistpoty> sebest: for revu?
[01:47] <sebest> yes
[01:47] <LaserJock> we're going to have to add a "Go to bed, now!" timer in here ;-)
[01:47] <sebest> i hit "ctrl+C"
[01:47] <sistpoty> LaserJock: hehe
[01:47] <sistpoty> sebest: what package? I'll clean it
[01:48] <sebest> innotop
[01:48] <sistpoty> sebest: gone ;)
[01:48] <sebest> my last question was related to launchpad and the packages that were accepted:
[01:48] <sebest> sistpoty: thanx :)
[01:48] <sistpoty> np
[01:49] <sebest> on this page: https://launchpad.net/~sebest/+packages
[01:49] <sebest> my packages are liste, but when i click on them, there is an error
[01:49] <sebest> and, i don't see them in feisty repository
[01:50] <sebest> eg: https://launchpad.net/ubuntu/feisty/+source/eaccelerator
[01:51] <sistpoty> sebest: probably still in the queue
[01:51] <sistpoty> sebest: https://launchpad.net/ubuntu/feisty/+queue
[01:51] <sebest> sistpoty: it was uploaded on 2006-12-16 17:00:05 CET
[01:52] <sistpoty> sebest: an archive admin needs to check these by hand first... and ubuntu archive queue is quite big atm. :/
[01:53] <sebest> sistpoty: 22 days is a lot :)
[01:53] <sistpoty> sebest: unfortunately 22 days is *not* a lot :/
[01:54] <sistpoty> there have been packages sitting far longer in the queue
[01:54] <sebest> sistpoty: btw , what is the queue? there a compiled?
[01:54] <sebest> is it an automatic process?
[01:54] <sistpoty> sebest: no... it's the queue of package, that an archive admin needs to look at byhand
[01:55] <sistpoty> sebest: there are two possibilities that a package lands in this queue: new sourcepacakge and new binary package (though new binary usually gets processed much faster))
[01:55] <LaserJock> https://launchpad.net/ubuntu/feisty/+queue
[01:56] <LaserJock> doh, sistpoty already said it
[01:56] <sebest> i don't need to do anything special except waiting, right?
[01:56] <sistpoty> sebest: right
[01:56] <sebest> ok :)
[01:56] <sistpoty> sebest: unless you get a reject ::P
[01:56] <sebest> he :)
[01:57] <sebest> btw, uploading to revu seems really slow today
[01:58] <sebest> 5 minutes to upload 60ko
[02:05] <sistpoty> we should really ban all php apps from universe *g*
[02:06] <LaserJock> sistpoty: hmmm, that'd take out quite a bit
[02:06] <LaserJock> less work, +1 ;-)
[02:07] <sistpoty> and much less security risks... e.g.: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=dokuwiki
[02:20] <sebest> what does NMU means?
[02:20] <sistpoty> sebest: non maintainer upload... you can ignore that for ubuntu
[02:21] <sebest> and for debian?
[02:21] <sebest> i'm trying to submit a package to mentors
[02:21] <sebest> i have the following lintian warning:
[02:21] <sebest> changelog-should-mention-nmu
[02:21] <sebest> source-nmu-has-incorrect-version-number 0.9.5-1
[02:22] <sistpoty> sebest: if anyone, who's not the maintainer or in the uploaders field makes a changelog entry, than that's a nmu
[02:22] <sistpoty> sebest: and then that should be mentioned in the changelog... 
[02:22] <sistpoty> sebest: and a patch to the previous version must go into bts
[02:22] <sebest> there is no maintainer as the package doesn't yet exist in debian
[02:23] <sistpoty> sebest: I don't recall the numbering scheme for nmu's right now, but iirc it should be 0.9.5-1.1
[02:23] <sistpoty> sebest: same name/email in debian/changelog as in control-file?
[02:23] <sebest> it seems to be case sensitive :)
[02:23] <sebest> thanx :d
[02:24] <sistpoty> np
[02:24] <zul> anyone seen this before? raise PyCentralError, "package has no field Python-Version"
[02:24] <sebest> last warning is about "not-using-po-debconf" but i'm not using po :s
[02:24] <zul> control has XS-Python-Version: current
[02:29] <crimsun> zul: what package?
[02:29] <zul> xen something has changed on me..
[02:31] <sebest> ok, it was in "man po-debconf"
[02:32] <zul> crimsun: i blame ajmitch 
[02:32] <LaserJock> zul: good call ;-)
[02:33] <LaserJock> although it's harder to blame him when his DSL has been down
[02:34] <zul> true...but its fun though
[02:40] <sebest> What about a wiki style REVU to create/update package in a community fashion?
[02:41] <sebest> people could correct/comment the debian/* files online from a browser
[02:42] <LaserJock> we are trying out using Launchpad
[02:42] <sebest> LaserJock: really? it would be really quicker to developp quality package
[02:43] <LaserJock> we have a team on LP where people can push branches
[02:43] <LaserJock> it's a hard problem
[02:43] <sebest> small typo could be fixed easily without the long process of : "editing , debuild, dput, revu"
[02:43] <LaserJock> REVU is pretty good
[02:43] <ajmitch> zul: I'm used to getting blamed
[02:43] <zul> i know you are
[02:44] <sebest> ajmitch: i upload eaccelerator packages to mentors.debian.net (if you are interested in this info)
[02:44] <ajmitch> ok
[02:44] <LaserJock> sebest: but it would really stink if people started messing with your packages and it wasn't just a typo
[02:44] <somerville32> LaserJock: What are we doing with lp?
[02:44] <somerville32> or plan to do?
[02:44] <LaserJock> somerville32: using it for REVU like activities
[02:44] <somerville32> Interesting
[02:44] <somerville32> docs?
[02:44] <sebest> LaserJock: this is the main issue with wikis
[02:45] <sistpoty> hm... imo an uploader can (and should) fix typos as well... but imo there is also an educational value...
[02:45] <LaserJock> somerville32: docs?
[02:45] <sistpoty> e.g. if someone needs to reupload 3 times because he can't get the orig.tar.gz right, he'll remember to not mess with it *g*
[02:45] <somerville32> LaserJock: spec?
[02:45] <sebest> LaserJock: but most of the time wiki still documents tend to improve (or you rollback :)
[02:45] <LaserJock> somerville32: there was an email to -motu
[02:46] <sebest> sistpoty: yes, but he could fixed it with its browser
[02:46] <LaserJock> sebest: yeah, but this is packaging and not docs. I think a wiki is less than idea
[02:46] <LaserJock> somerville32: most definitely
[02:46] <sistpoty> sebest: that's what I mean with educational value :O
[02:46] <sistpoty> :P
[02:46] <plugwash> don't debian policies require the orig.tar.gz to be messed with in the rather common case that not everything in upstreams official release is dfsg-free
[02:47] <sistpoty> plugwash: that case is pretty uncommon actually
[02:47] <sistpoty> plugwash: but yes, then it's ok
[02:48] <LaserJock> why? we should have dfsg packages if possible
[02:48] <sebest> sistpoty: this would be packaging 2.0 ;)
[02:48] <sistpoty> sebest: I guess bzr is packaging 2.0 *g*
[02:48] <sistpoty> s/is/will be/
[02:48] <LaserJock> mhm
[02:49] <sistpoty> but it's not ready yet imo
[02:49] <rexbron> crimsun: the issue I am finding is gcc is looking for python.c (provided by soma) in /usr/include/python2.4
[02:49] <LaserJock> yeah, there's some issues
[02:49] <sebest> sistpoty: 1.9, because you need a bzr client:)
[02:49] <LaserJock> joejaxx: pingy
[02:49] <joejaxx> LaserJock: pong
[02:50] <LaserJock> joejaxx: left a review of ubuntustudio-meta
[02:50] <joejaxx> today is not my day my screen session crashed :(
[02:50] <joejaxx> LaserJock: oh ok 
[02:50] <crimsun> rexbron: that's nasty; hack the Makefile.in as per necessary
[02:50] <rexbron> I will take a look
[02:50] <sebest> sistpoty: would be great to have a packaging IDE full web: editing and pbuildiing, i could click a button and it would pbuild on dapper/edgy/etc
[02:50] <rexbron> also, I was talking with upstream, they might provide a patch for it
[02:50] <rexbron> or at least look into it
[02:51] <crimsun> rexbron: that would be preferable
[02:52] <sistpoty> sebest: pbuilding would indeed be nice
[02:52] <LaserJock> sebest: well, Mark said we'll be getting pretty close to that soon
[02:53] <LaserJock> but I imagine it'll take a while to get there
[02:53] <sebest> LaserJock: the development of these features are closed source?
[02:53] <LaserJock> LP, yes
[02:54] <sistpoty> lol, I wanted to type sudo poweroff and instinctly typed sudo pbuilder *g+
[02:55] <LaserJock> heh
[02:55] <sebest> Is there any reason? I don't ask it to be gpl or anything, but it would be nice that the code is open to contribute to it
[02:55] <sistpoty> sebest: canonical is a company... they wan't to earn money after all ;)
[02:55] <LaserJock> it's a Canonical decision as for as I know
[02:55] <LaserJock> basically, they want to build a single place for people to go
[02:56] <LaserJock> and if they give out the code before it's ready it could cause problems
[02:56] <sebest> sistpoty: the code can't be open with a license that state that you can't use it commercially?
[02:56] <bhale> people need to move on from the OSS zealotry business
[02:56] <bhale> 1) no one is asking for the code to Google on a condition of using it
[02:56] <LaserJock> wow, out of the woodwork
[02:56] <bhale> 2) if you had the launchpad code, it would be useless to you
[02:56] <bhale> LaserJock: sorry, heard this a few too many times
[02:57] <LaserJock> yeah, I think it'd be very difficult to open source it at this point
[02:57] <sistpoty> sebest: I guess it could... but the code alone isn't the only thing to make money with there... as LaserJock said, they also want to create a single place were ppl. will go, which is kind of a business concept as well
[02:57] <bhale> its hard enough to run by Canonical
[02:57] <bhale> largeish staff of programmers and sysadmins
[02:58] <bhale> to play the devils advocate, it is slighly unsettling that the tools to build ubuntu are under Canonical's complete control
[02:58] <bhale> this is not that exciting of a point, because virtual no one other than elmo can run DAK, either
[02:59] <bhale> and has the same big lock on Debian
[02:59] <sistpoty> hehe
[02:59] <sebest> sistpoty: i don't see why people would go elsewhere if it were opensource
[02:59] <sebest> the value is not the sourcecode, but the data IMO
[03:01] <sebest> but i see reason for people NOT using it because it is closed source
[03:01] <LaserJock> well, but if every project had there own LP it would kinda defeat the purpose. I think that's the idea anyway
[03:02] <LaserJock> I don't know, I go back and forth with it
[03:02] <LaserJock> it's sometimes aggravating to have to bug LP people all the time
[03:02] <LaserJock> and sometimes there are obvious features that are missing
[03:03] <LaserJock> but on the other hand, I don't think it'd be as far along as an opensource project
[03:03] <LaserJock> and if *I* were to get code I couldn't do anything with it anyway
[03:03] <LaserJock> :-)
[03:10] <sebest> btw: bed time for me, good night all
[03:12] <LaserJock> cya
[03:13] <sistpoty> gn8 everyone
[03:24] <superm1> crimsun, ping
[03:25] <crimsun> superm1: contentless pong.
[03:25] <TheMuso> haha
[03:25] <superm1> contentless eh?
[03:25] <superm1> interesting concept...
[03:25] <crimsun> yes, please include what you're asking about in the ping
[03:25] <superm1> ah okay
[03:25] <superm1> crimsun, i switched the mythtv package over to use update-alternatives instead
[03:26] <crimsun> excellent
[03:26] <superm1> its much cleaner now
[03:26] <superm1> i'm glad you suggested that
[03:27] <bhale> crimsun, democracy player totally bombs on python2.5 here
[03:27] <crimsun> bhale: but works on 2.4?
[03:28] <bhale> crimsun: it works *more* :)
[03:28] <bhale> but not by much
[03:31] <crimsun> I can remove 2.5 (and just list 2.4 explicitly) in the next merge if 2.5 is a complete disaster
[03:31] <bhale> 2.5 crashes immediately, 2.4 shows the window and then crashes
[03:31] <bhale> this is the first time ive tried democracyplayer
[03:35] <ScottK> One could argue that 2.5 is better.  If it's gonna crash, might as well get it overwith.
[03:35] <crimsun> impressive, all 11 bugs are crashers
[03:37] <crimsun> ooh, nice, i10n error causes crash
[03:39] <LaserJock> hmm, it annoys me when mailing lists don't send me my own emails
[03:40] <ScottK> LaserJock: If it's a mailman list there's a setting for that.
[03:41] <LaserJock> ScottK: yeah, but I don't admin all the lists I subscribe too ;-)
[03:43] <persia> How should a sync be requested (the previous Ubuntu changes have been merged in Debian)?
[03:44] <jdong> hahaha, freudian slip of the day: Rockbox identifies "Thrash Metal" ID3 tag as "Trash Metal"
[03:44] <jdong> :D
[03:44] <LaserJock> persia: file a sync request bug and subscribe  ubuntu-universe-sponsors
[03:44] <persia> LaserJock: Thanks.
[03:44] <crimsun> u-u-s is largely non-functional presently
[03:45] <crimsun> better to just ping me with the bug #
[03:45] <crimsun> (due to the bug contact email going to only one person)
[03:45] <LaserJock> what?
[03:45] <LaserJock> why is that?
[03:46] <persia> crimsun: Ah.  Thanks.  The sync bug is #76590.  Other bugs to which I have subscribed u-u-s are #33580, #42622, and #78296.
[03:46] <crimsun> https://lists.ubuntu.com/archives/ubuntu-motu/2006-December/001047.html
[03:46] <Hobbsee> crimsun: did you want the email?
[03:46] <crimsun> Hobbsee: I'd like to see it set to a group email as it was, but you mentioned it's being worked on
[03:46] <Hobbsee> crimsun: actually, i can forward it to you, so we both get it
[03:46] <Hobbsee> i think...
[03:47] <crimsun> Hobbsee: that would rock, thanks
[03:47] <LaserJock> why don't we just have a mailing list?
[03:47] <LaserJock> that's the usual thing to do
[03:47] <Hobbsee> LaserJock: because i havent figured out how to get one, and my email hasnt been replied to yet
[03:47] <somerville32> Hobbsee, You need to e-mail rt
[03:47] <Hobbsee> somerville32: i did
[03:48] <Hobbsee> crimsun: where did you want it?
[03:48] <LaserJock> well, we can use tiber
[03:48] <Hobbsee> LaserJock: cool
[03:48] <Hobbsee> that'd work, i presume
[03:48] <LaserJock> I just think it's odd to be hung up for a lack of mailing list
[03:48] <crimsun> Hobbsee: my LP email would be fine
[03:49] <Hobbsee> LaserJock: indeed.  if we can get a mailing list on tiber, i'd appreciate that
[03:49] <LaserJock> I don't really read a lot of bug email ( I don't like how LP sends stuff) but surely people would find it useful
[03:49] <LaserJock> Hobbsee: just get siretart to do it
[03:49] <Hobbsee> siretart: ping?
[03:49] <siretart> Hobbsee: You sent me a contentless ping.  This is a contentless pong.  Please provide a bit of information about what you want and I'll respond when I am around.
[03:49] <Hobbsee> *grin*
[03:49] <Hobbsee> siretart: ping @ a mailing list for u-u-s on tiber
[03:50] <LaserJock> now we are going to have 2x as many pings
[03:50] <LaserJock> first the contentless ping
[03:50] <LaserJock> then the one with content
[03:50] <Hobbsee> indeed
[03:50] <LaserJock> :-)
[03:50] <Hobbsee> will he reply twice?
[03:50] <Hobbsee> plus your mention of his nick
[03:50] <jdong> which is why you ping with  random trash attached
[03:50] <Lathiat> ping +++ATH0
[03:51] <Hobbsee> heh
[03:51] <bhale> ATDT Lathiat 
[03:51] <Lathiat> NODIALTONE
[03:51] <bhale> :(
[03:51] <bhale> CARRIER LOST
[03:51] <Lathiat> you lose
[03:56] <somerville32> Ok
[03:56] <somerville32> Lets package.
[04:00] <ScottK> LaserJock: Mailman usually has the option to get your own postings at the user level too in the users page.  That's what I've always seen.
[04:01] <LaserJock> ScottK: oh, interesting, I'll have a look
[04:04] <LaserJock> darn, it'd be nice if you could subscribe to particular tasks
[04:04] <joejaxx> LaserJock: i can keep the package at the same version right?
[04:04] <LaserJock> yeah
[04:04] <joejaxx> ok
[04:11] <somerville32> For my pyneighborhood package, I'm just going to delete what I have and use cdbs
[04:11] <Hobbsee> hehe
[04:17] <somerville32> For debian/
[04:17] <somerville32> A lot of files can have the binary package appended to it
[04:17] <somerville32> like menu
[04:17] <somerville32> etc.
[04:18] <somerville32> It is preferred to have that even if there is only one binary package?
[04:18] <crimsun> it's not necessary, but it's the packager's preference.
[04:19] <LaserJock> somerville32: yeah, just abstract your way out of problems :-)
[04:21] <somerville32> When a makefile installs the files to the wrong place, I just have to patch the Makefile, right?
[04:23] <ajmitch> usually, yes
[04:29] <somerville32> With man pages
[04:29] <somerville32> What does the number at the end mean?
[04:29] <TheMuso> ajmitch: Heya!
[04:29] <persia> somerville32: The section.  man man for a description
[04:30] <somerville32> What do I do if all the source code is on the top level directory?
[04:30] <somerville32> I think I need to pass the directory for pysupport to look in or something
[04:30] <ajmitch> TheMuso: hello
[04:31] <TheMuso> ajmitch: How was your Christmas break?
[04:32] <ajmitch> it was pretty good
[04:32] <ajmitch> how about you?
[04:32] <ajmitch> so not really on irc :)
[04:32] <somerville32> oh wait, nvm
[04:33] <Hobbsee> ajmitch!!!
[04:33] <ajmitch> Hobbsee: yes?
[04:33] <Hobbsee> ajmitch: heya :)
[04:33] <ajmitch> hello
[04:34] <ajmitch> how's it going?
[04:35] <Hobbsee> good :)
[04:35] <Hobbsee> nah...
[04:38] <TheMuso> ajmitch: Twas good thank you.
[04:40] <Hobbsee> TheMuso: coming to the dinner after open day?
[04:41] <crimsun> oh, suck. More acroread CVEs that I can't do anything about.
[04:41] <TheMuso> Hobbsee: WOuldn't miss it. I hope you are.
[04:42] <TheMuso> Good.
[04:44] <ajmitch> hello crimsun 
[04:45] <crimsun> hello ajmitch 
[04:47] <LaserJock> ajmitch: me too :(
[04:47] <LaserJock> why can't they have LCA at google HQ? ;-)
[04:47] <TheMuso> LaserJock: Because then it wouldn't be LCA.
[04:48] <LaserJock> me neither
[04:48] <LaserJock> I think Mountain View almost did me in :-)
[04:50] <LaserJock> hmm, ERC
[04:51] <ajmitch> so has the motu council been formed yet?
[04:51] <Hobbsee> ajmitch: doubt it
[04:52] <Hobbsee> ajmitch: CC meeting is on tuesday
[04:52] <ajmitch> I thought it was mainly the TB it was blocked on
[04:52] <Hobbsee> oh yeah
[04:52] <Hobbsee> probably
[04:53] <ajmitch> until then, you can continue working
[04:53] <LaserJock> yeah, we seem to have lost a little of the "pre-Christmas" momentum
[04:53] <ajmitch> a little?
[04:54] <LaserJock> well, crimsun's still working
[04:55] <ajmitch> crimsun doesn't know how to stop
[04:55] <LaserJock> but we did lose the ajmitch factor ;-)
[04:55] <crimsun> it's bit-perfect crack-cocaine.
[04:56] <crimsun> I promise I'll check myself in MOTU anonymous soon
[04:56] <ajmitch> LaserJock: the ajmitch factor being the general noise in the channel, with no actual work?
[04:57] <LaserJock> crimsun: don't bother, it seems nothing can help the raging Ubuntu-holic MOTU :(
[04:58] <LaserJock> ajmitch: I was thinking "constructive discussion" but whatever ;-)
[04:59] <ajmitch> hah
[04:59] <ajmitch> funny man
[05:00] <LaserJock> perhaps I'll get to be the Castle Grayskull court jester :-)
[05:01] <LaserJock> I thought that was bddebian
[05:01] <ajmitch> nah
[05:03] <LaserJock> distributed uber-MOTUism
[05:03] <crimsun> you'll end up with a -lot- of md5 collisions.
[05:04] <somerville32> Do I use dh_install if the makefile installs the files anyhow?
[05:05] <LaserJock> no
[05:05] <somerville32> kk
[05:06] <somerville32> I think I've finally figured this out :] 
[05:06] <LaserJock> crimsun: are merge/sync requests going to u-u-s too?
[05:07] <Hobbsee> LaserJock: they already do
[05:07] <crimsun> they should as per normal
[05:08] <LaserJock> hmm, I don't see much
[05:08] <crimsun> Hobbsee: were you able to added me to the bug contact email forward?
[05:08] <crimsun> to add, sheesh
[05:08] <LaserJock> I just wondered
[05:09] <persia> Does anyone have an opinion on /usr/share/menu vs. /usr/lib/menu?
[05:10] <Hobbsee> crimsun: oh yeah, was goign to.  had to experiment to see if it'd work
[05:10] <Hobbsee> oh wait, no
[05:11] <Hobbsee> crimsun: i can forward it to you, and not get the bugmail, if you like
[05:12] <LaserJock> persia: http://www.debian.org/doc/packaging-manuals/menu.html/ch3.html#s3.1
[05:12] <persia> LaserJock: Thanks, although I'm not sure when a compliant menu file would be a binary :)
[05:13] <crimsun> Hobbsee: that'd be no better than the current situation :/
[05:13] <LaserJock> persia: I'm not really sure either
[05:13] <Hobbsee> crimsun: sure it is - you're reading the mail feed
[05:13] <crimsun> Hobbsee: bah
[05:14] <Hobbsee> crimsun: done
[05:15] <crimsun> ok, thanks.
[05:15] <crimsun> should I file a bug against RT, then, so we can move this along more quickly?
[05:16] <Hobbsee> crimsun: please do
[05:17] <somerville32> Hmm...
[05:17] <somerville32> It appears I'm actually installing to /debian/
[05:17] <somerville32> or, err..
[05:17] <somerville32> debian/
[05:18] <somerville32> *debian/pyneighborhood
[05:18] <somerville32> How do I get it to actually install it?
[05:28] <crimsun> somerville32: rephrase, please.
[05:29] <ajmitch> bye all
[05:29] <crimsun> cya ajmitch 
[05:29] <crimsun> somerville32: what are you trying to accomplish?
[05:29] <somerville32> pyneighborhood
[05:30] <somerville32> :)
[05:30] <crimsun> (phone)
[05:30] <somerville32> I've got three different attempts going at once
[05:30] <somerville32> And I just lost of my train of thought
[05:30] <somerville32> lol
[05:35] <LaserJock> somerville32: it's installing to debian/pyneighborhood ?
[05:35] <somerville32> LaserJock: Yeah
[05:35] <somerville32> my Makefile
[05:35] <LaserJock> ok, that's a good thing
[05:35] <somerville32> :)
[05:43] <somerville32> LaserJock: Does it install it after automagically?
[05:45] <LaserJock> somerville32: well, when your building you are actually building in a subdir
[05:46] <LaserJock> then once everything is in place it compresses it all up into a .deb
[05:47] <somerville32> Ah
[05:49] <somerville32> LaserJock: Are you busy?
[05:50] <LaserJock> kinda-ish
[05:50] <LaserJock> I'm at home cooking with the wife a little
[05:50] <somerville32> LaserJock, Lets do a MOTU classroom session, lol. I think that if I worked through one package with someone (and they were verbose), I'd have things down pat :)
[05:51] <somerville32> I'm just so frustrated with all the failed attempts I'm probably missing something simple
[05:53] <joejaxx> LaserJock: how do i delete the one i already uploaded?
[05:55] <joejaxx> somerville32: what are you trying to learn?
[05:55] <joejaxx> :)
[05:56] <somerville32> I'm trying to get packaging down
[05:56] <somerville32> lol
[05:56] <somerville32> But I always try it when I'm super tired
[05:56] <joejaxx> lol
[05:56] <somerville32> I can patch and all the stuff
[05:56] <joejaxx> try it when you are well rested :)
[05:56] <somerville32> It is building a package from scratch
[05:56] <somerville32> I understand most of it
[05:57] <somerville32> but the issue is actually installing the files, lol
[05:57] <joejaxx> lol
[05:57] <somerville32> and all the weird dh_ scripts
[05:57] <joejaxx> ah
[05:57] <somerville32> :D
[05:57] <joejaxx> oh ok
[05:57] <joejaxx> :)
[05:59] <joejaxx> somerville32: too bad there is not a ddel
[05:59] <joejaxx> lol
[06:02] <LaserJock> joejaxx: it's automatically overwritten
[06:02] <LaserJock> somerville32: well for dh_* they usually have pretty good man pages
[06:03] <somerville32> LaserJock: They aren't too bad :] 
[06:03] <LaserJock> I recommend going through your whole debian/rules and reading the man page for each dh_
[06:03] <joejaxx> LaserJock: just found that out i reuploaded them
[06:03] <joejaxx> when*
[06:04] <joejaxx> :)
[06:04] <joejaxx> i thought you might have had to delete them some kind of way
[06:06] <LaserJock> nope
[06:06] <LaserJock> REVU separates by time
[06:06] <LaserJock> that's why you can upload the same version
[06:08] <joejaxx> that is a nice feature:)
[06:33] <LaserJock> somerville32: ok, so you're having problems with file installation?
[06:33] <somerville32> LaserJock: Yeah, I see how I can fix it but it doesn't seem... logical
[06:34] <LaserJock> ok, so it's help to think about the build process
[06:34] <LaserJock> how does a .deb get built?
[06:34] <somerville32> Magic? :)
[06:34] <LaserJock> and how does it get installed?
[06:35] <crimsun> the great motuaholic deems it so, and It Is So.
[06:35] <LaserJock> hmm, not encouraging answers ;-)
[06:35] <crimsun> we bow before your infinite motuness.
[06:36] <joejaxx> LOL
[06:36] <somerville32> :] 
[06:36] <somerville32> I'm going to get a glass of Orange juice and then we can plow through this thing :)
[06:36] <Hobbsee|NotHere> crimsun: haha
[06:39] <somerville32> Lets start from the start (to make sure I got everything right)
[06:40] <somerville32> We visit http://sourceforge.net/projects/pyneighborhood/ to download the latest version (which is 0.4)
[06:40] <somerville32> We wait a few minutes for SourceForge.net to give us the file since it is so slow
[06:42] <somerville32> Direct link: http://superb-west.dl.sourceforge.net/sourceforge/pyneighborhood/pyNeighborhood-0.4.tar.gz
[06:44] <somerville32> So, I create a folder to work in
[06:45] <somerville32> I then decompress the gzip and untar then then recompress with gzip
[06:45] <somerville32> This produces the directory pyNeighborhood-0.4
[06:46] <somerville32> Which I rename to pyneighborhood-0.4 to meet package naming requirements
[06:46] <LaserJock> and then I tar'd it back up to pyneighborhood_0.4.orig.tar.gz
[06:47] <somerville32> I use dh_make
[06:48] <somerville32> dh_make -c gpl -e cody-somerville@ubuntu.com -f ../*.gz
[06:49] <LaserJock> k, I'm with you
[06:49] <somerville32> Should I use cdbs or just use single binary?
[06:50] <LaserJock> I did single binary
[06:50] <somerville32> Ok, so we've set it up and now it is time to start editing our debian files :)
[06:50] <LaserJock> if you're having problems understanding how the building works, abstracting it away to CDBS isn't going to help you learn, IMO
[06:50] <somerville32> I've been using single so far
[06:51] <somerville32> First, the easy stuff
[06:51] <somerville32> Modify changelog
[06:51] <somerville32> Change version to 0.4-0ubuntu1
[06:52] <crimsun> anyone running dapper amd64?
[06:52] <somerville32> unstable -> feisty
[06:52] <somerville32> Change comments to just "* Initial release"
[06:52] <somerville32> Save
[06:54] <somerville32> rm cron.d.ex emacs* init.d.ex manpage* post* pre* pyneighborhood-default.ex *.EX
[06:55] <somerville32> removed `cron.d.ex', removed `emacsen-install.ex', removed `emacsen-remove.ex', removed `emacsen-startup.ex', removed `init.d.ex', removed `manpage.1.ex', removed `manpage.sgml.ex', removed `manpage.xml.ex', removed `postinst.ex',removed `postrm.ex', removed `preinst.ex', removed `prerm.ex', removed `pyneighborhood-default.ex', removed `pyneighborhood.doc-base.EX'
[06:56] <LaserJock> k
[06:58] <LaserJock> somerville32: now what?
[06:58] <somerville32> Modify the rules file
[06:59] <somerville32> Umm... this is going to get tricky to rely everything I do back to here
[06:59] <somerville32> What about a gobby session?
[06:59] <crimsun> server?
[06:59] <LaserJock> it's all python, right
[06:59] <LaserJock> ?
[07:00] <somerville32> The package?
[07:00] <somerville32> The package is completely
[07:00] <somerville32> err..
[07:01] <somerville32> The program is programmed in Python, yes
[07:04] <LaserJock> is the canonical gobby server still up?
[07:05] <somerville32> Not sure
[07:06] <somerville32> I can try setting up a sobby server
[07:06] <LaserJock> yep, gobby.u.c
[07:07] <crimsun> standard port?
[07:08] <LaserJock> yep
[07:09] <somerville32> gobby.ubuntu.com 6523 ?
[07:09] <LaserJock> that or 6522, I can't remember
[07:10] <LaserJock> it's 22
[07:10] <somerville32> 6522
[07:16] <ajmitch_> yay
[07:17] <ajmitch_> only took 2 days to get DSL back at home
[07:18] <LaserJock> \o/
[07:54] <Fujitsu> keescook, what do you think about the vnc4 regression?
[07:54] <keescook> Fujitsu: I'm not sure how to debug it; it's an ugly side-effect of it getting recompiled against edgy libraries.  :(
[07:54] <Fujitsu> Looks like it.
[07:54] <Fujitsu> There's no way we can migrate the Dapper binaries over?
[07:55] <Fujitsu> (like the way they got into Edgy in the first place)
[08:02] <somerville32> :)
[08:02] <somerville32> gobby.ubuntu.com :)
[08:02] <somerville32> Who wants to come help me? :)
[08:02] <somerville32> lol
[08:14] <siretart> morning
[08:15] <siretart> Hobbsee|NotHere: hm. try via email perhaps?
[08:17] <ajmitch_> hi siretart 
[08:22] <siretart> huhu ajmitch_ 
[08:23] <somerville32> Ok, I'm confused again.
[08:23] <somerville32> lol
[08:24] <somerville32> My makefile will install it to debian/prefix/blah
[08:24] <somerville32> So...
[08:24] <somerville32> my debian/install file..
[08:24] <somerville32> Do I refer to the files as if they are in debian/prefix/blah/etc.
[08:24] <somerville32> or do I just do it relative to package root?
[08:27] <persia> somerville32: I use relative to the package root as the source location, and a shorthand (e.g. "usr/share/pixmaps") for the target location.  Note that only files that are not installed properly by the normal build process need to be included in debian/install
[08:27] <somerville32> How do I know if they are installed correctly or not?
[08:28] <somerville32> persia: Can you spare a few minutes to give me a hand?
[08:28] <persia> somerville32: I think the easiest way is to inspect the resulting deb (after dpkg-buildpackage) manually, but others inspect the actual buld tree.
[08:29] <somerville32> persia: Do you have gobby installed
[08:29] <persia> somerville32: sure.
[08:29] <somerville32> +?
[08:30] <persia> somerville32: Now I do, but I have never used it.
[08:30] <somerville32> Ok
[08:30] <somerville32> Join gobby.ubuntu.com
[08:30] <somerville32> :] 
[08:41] <dholbach> good morning
[08:42] <Lutin>  'morning dholbach
[08:42] <dholbach> heya Lutin
[08:45] <ajmitch_> hi daniel
[08:49] <somerville32> dholbach, I need your help :)
[08:49] <dholbach> hey andrew
[08:49] <dholbach> hey somerville32 - fire away
[08:49] <somerville32> dholbach, Do you have gobby installed? :] 
[08:49] <dholbach> yes
[08:50] <somerville32> Can you come take a peak at gobby.ubuntu.com?
[09:06] <somerville32> ${python:Depends} still isn't being replaced.
[09:08] <somerville32> persia: IT didn't install my man page
[09:12] <somerville32> persia, Is this when I use install? :] 
[09:12] <somerville32> oh wait
[09:12] <somerville32> I see what I may have done wrong
[09:15] <somerville32> Is this an acceptable error?:
[09:15] <somerville32> E: pyneighborhood: menu-icon-not-in-xpm-format /usr/share/pyNeighborhood/icons/pyneighborhood_48x48.png
[09:18] <somerville32> What does this error mean?
[09:18] <somerville32> E: pyneighborhood source: package-needs-python-policy-debhelper
[09:20] <persia> somerville32: The common workaround for that error is to create debian/pyneighborhood.xpm, and install it in /usr/share/pixmaps (with debian/install).  Menuing systems that use .desktop files will select the .png as the preferred format, and debian menu-based systems will use the .xpm.
[09:21] <somerville32> How do I make a .xpm?
[09:22] <persia> somerville32: execute `convert wherever/pyneighberhood_48x48.pgn debian/pyneighborhood.xpm`
[09:24] <somerville32> So I'll need to use install to install the .xpm icon
[09:24] <persia> somerville32: Yes.  debian/install is for all the miscellaneous files that don't get installed in the build.
[09:26] <somerville32> Ok
[09:26] <somerville32> :)
[09:26] <somerville32> I'm so close I can taste it
[09:35] <somerville32> persia: ping
[09:35] <somerville32> E: pyneighborhood; Manual page pyneighborhood.8 is not compressed.
[09:35] <somerville32> E: pyneighborhood; Manual page /usr/share/man/man8/pyneighborhood.8 is not compressed with max compression.
[09:35] <somerville32> E: pyneighborhood; Manual page /usr/share/man/man8/pyneighborhood.8 is not compressed using gzip.
[09:35] <somerville32> E: pyneighborhood; No manual page for binary pyNeighborhood.
[09:37] <persia> somerville32: Are you installing the binary in sbin?  Usually, section 1 is used for even administrative commands in bin, as these are available to normal users.
[09:37] <somerville32> no
[09:37] <somerville32> I'm installing it to /usr/bin
[09:38] <persia> somerville32: Is your package somewhere I can download it?
[09:38] <somerville32> I'll upload right now
[09:38] <somerville32> Ok
[09:38] <somerville32> uploaded to revu
[09:45] <somerville32> persia: 
[09:45] <somerville32> http://revu.tauware.de/details.py?upid=3991
[09:47] <persia> somerville32: First thing I notice is that you want to put the .xpm file in usr/share/pixmaps (and adjust the menu file)
[09:47] <somerville32> ok
[09:48] <somerville32> for png one too? (I'd have to patch upstream)
[09:49] <persia> somerville32: the png should definitely be in usr/share/pixmaps.  When upstream puts it somewhere else, I usually just copy it with an extra line in debian/install.  You'd also need a patch to change the .desktop (Icon=pyneighborhood_48x48)
[09:52] <somerville32> Would the patch start with a 20 now?
[09:52] <persia> somerville32: dh_python is deprecated.  As you are using dh_pysupport, this can be removed.
[09:52] <somerville32> persia: k
[09:52] <persia> somerville32: 20 is a fine number (anything larger than 10 is good).
[09:53] <somerville32> What should I call it?
[09:53] <somerville32> Are there any conventions?
[09:53] <persia> somerville32: I usually call them something like desktop-file-update, I don't know of a convention.
[09:56] <somerville32> Do, I can just change Icon=pyneighborhood_48x48.png
[09:56] <somerville32> Or leave out the file extension?
[09:56] <persia> somerville32: You don't need the .png (it is actually deprecated).  This lets themes use SVG (or whatever) if they prefer.
[09:57] <somerville32> ok
[09:57] <somerville32> done
[10:00] <persia> somerville32: You probably want to rename then manpage to use the mixed capitalisation used for the binary
[10:01] <somerville32> done
[10:01] <persia> somerville32: Adding dh_compress should solve a few of the warnings
[10:03] <somerville32> Does it matter where in the chain of dh_* scripts?
[10:04] <persia> somerville32: After dh_installman should be fine
[10:04] <persia> somerville32: My apologies, but I have no idea about W: pyneighborhood: description-synopsis-might-not-be-phrased-properly
[10:05] <somerville32> Hmm
[10:07] <somerville32> haha!
[10:07] <somerville32> I think I figured out my dependency issue
[10:07] <somerville32> I install to /usr/share/pyNeighborhood
[10:07] <somerville32> and the package is pyneighborhood
[10:07] <somerville32> So it would look for it in pyneighborhood
[10:07] <somerville32> haha
[10:15] <somerville32> Yes!
[10:15] <somerville32> :D
[10:15] <somerville32> I figured it out.
[10:16] <somerville32> After weeks of hacking... I have finally figured it out!
[10:16] <somerville32> :D
[10:16] <somerville32> Someone give me a hug
[10:17] <somerville32> :D
[10:21] <somerville32> E: pyneighborhood: menu-icon-too-big /usr/share/pixmaps/pyneighborhood_48x48.xpm: 48x48 > 32x32
[10:21] <somerville32> Is there an easy way to make it smaller?
[10:23] <persia> somerville32: I use GIMP - for a change like that (48->32), you may need to adjust the bits manually to make sure it still looks good afterwards, as 3/4 pixels tend not to be so clear.
[10:23] <somerville32> ...
[10:23] <somerville32> I have to be an artist too? :S
[10:23] <Fujitsu> This is why SVG is good.
[10:24] <somerville32> What are my options?
[10:24] <persia> Fujitsu: It doesn't help for debian menu files (which require 32x32 .xpm files, but generally, yet.
[10:24] <Fujitsu> True.
[10:25] <persia> somerville32: If you load the image into Gimp, there is a "Scale Image" entry in the "Image" menu.  If you aren't too concerned with the final result, just save the result of this operation as the .xpm file.  You can script it, but my gimp-fu isn't up to that.
[10:26] <somerville32> done :] 
[10:34] <somerville32> As for the phrase issue
[10:34] <somerville32> I think it is because I have a period at the end
[10:37] <somerville32> Is this permissible? W: pyneighborhood: menu-command-not-in-package /usr/share/menu/pyneighborhood:3 gksudo
[10:40] <somerville32> persia, Are you a MOTU?
[10:40] <persia> somerville32: No.  I just write patches.
[10:40] <lifeless> somerville32: what do you mean permissible ?
[10:41] <somerville32> lifeless: Would a MOTU advocate with that warning present?
[10:41] <lifeless> if your package is correct, then sure, whynot.
[10:41] <lifeless> but if the package is correct, and nothing is wrong, override the warning
[10:42] <persia> somerville32: http://huygens.ca.infn.it/cgi-bin/dwww?type=file&location=/usr/share/doc/lintian/lintian.html/ch2.html#s2.4 explains how
[10:42] <somerville32> Thanks
[10:43] <persia> somerville32: I can confirm the phrase issue was due to the period.  It should be removed.
[10:43] <somerville32> schweet :)
[10:44] <somerville32> I think I've packaged my first package successfully
[10:45] <somerville32> lifeless: Would you be able to do a quick review in a few minutes? I'm pretty sure the package is ready for advocating. :)
[10:45] <lifeless> nope, sorry.
[10:45] <lifeless> in meetings
[10:45] <somerville32> kk
[10:53] <somerville32> Does anyone know the new address for imbrandon's box?
[10:58] <crimsun> 56161 uploaded.
[10:59] <somerville32> Is that my SRU?
[11:00] <somerville32> Yes
[11:00] <somerville32> Thanks Crimsun :)
[11:02] <crimsun> somerville32: in the future, please append a number to proposed
[11:03] <somerville32> What do you mean?
[11:03] <somerville32> oh
[11:03] <somerville32> Right
[11:03] <somerville32> I read "append" and "send"
[11:03] <somerville32> *as
[11:05] <somerville32> crimsun: I'm just rebuilding my package. After I'm done, do you think you could review it for me? I think it is ready for advocating. :)
[11:05] <crimsun> sure. I'll be in and out for the next hour or so.
[11:05] <somerville32> Do you know whats up with imbrandon's build box?
[11:06] <somerville32> It times out when I try to connect
[11:06] <somerville32> and building the package takes like 5-6 minutes each time, lol - luckily this is a quick package to build.
[11:08] <somerville32> Btw, when do we change the urgency on the changelog? What does it do?
[11:10] <persia> somerville32: For Ubuntu it is almost never used.  For Debian, it controls what criteria must be met before the package can move from unstable to testing.
[11:11] <somerville32> k
[11:12] <somerville32> Alright!
[11:12] <somerville32> No more lintian errors
[11:12] <somerville32> Time to upload to revu :] 
[11:19] <somerville32> crimsun: http://revu.tauware.de/details.py?upid=3993
[11:22] <persia> somerville32: Just a note: you probably want to delete the 48x48 xpm, as it is not used.
[11:35] <\sh> happy new year and moins :)
[11:36] <persia> \sh: Happy new year
[11:53] <crimsun> somerville32: what is ./usr/share/python-support/pynei
[11:53] <crimsun> ghborhood.dirs
[11:59] <crippledcanary> could I please, please have anyone to look at http://revu.tauware.de/details.py?upid=3772
[12:06] <crimsun> crippledcanary: what's the deal with: -rwxr-xr-x root/root      1286 2007-01-08 03:06 ./usr/bin/.scribesclient    
[12:07] <crimsun> i.e., why is it hidden?
[12:10] <crimsun> crippledcanary: also, you need to b-d on python-support and use the Debian Python policy
[12:10] <crimsun> (which means you need python-all and python-all-dev as b-d, too)
[12:11] <crimsun> or just python-all-dev and python-support
[12:11] <crimsun> then you need to adjust scribes's Depends
[12:34] <crippledcanary> crimsun: I will fix the b-d and contact upstream about .scribesclient
[12:35] <pef> hello
[12:46] <crippledcanary> crimsun: if I add python-all, can I remove b-d on python then?
[12:46] <crimsun> crippledcanary: if you b-d on python-all-dev, you don't need python or python-all listed
[12:47] <crippledcanary> crimsun: should depends also point to python-all
[12:47] <crimsun> crippledcanary: no, python-all-dev depends on python-all
[12:48] <crippledcanary> yes -dev for b-d but shuld I use pyton-all for "d"
[12:48] <crimsun> crippledcanary: you should use ${python:Depends}
[12:49] <StevenK> crimsun: Give us idiots a chance to answer. :-P
[12:49] <crimsun> kk O:-)
[12:49] <fernando> moin all
[12:49] <Hobbsee> StevenK: now you'll be pressured into doing all the dirty work...
[12:49] <Hobbsee> hey fernando 
[12:50] <bhale> yay Hobbsee 
[12:50] <fernando> hey Hobbsee 
[12:50] <Hobbsee> hey bhale :)
[12:50] <crippledcanary> So if I use ${python:Depens} in d then all dependencies is grabbed from b-d?
[12:51] <StevenK> Hobbsee: What else is new? :-P
[12:51] <Hobbsee> StevenK: heh.
[12:51] <persia> Hobbsee: Thanks for adjusting the u-u-s list earlier
[12:51] <Hobbsee> persia: :)
[12:52] <Hobbsee> persia: adjusting it?
[12:52] <persia> Hobbsee: As previously noted, crimsun is indeed addicted to bugmail (thanks crimsun)
[12:53] <Hobbsee> persia: ahh :)
[12:53] <Hobbsee> persia: yes
[12:53] <Hobbsee> it's a little weird not seeing it in my inbox :P
[12:53] <Hobbsee> apparently you cant forward to two addresses in gmail.  shame
[01:04] <somerville32> Hobbsee, http://revu.tauware.de/details.py?upid=3993 ? Please :)
[01:06] <Hobbsee> somerville32: ask StevenK 
[01:07] <StevenK> Grrr!
[01:07] <Hobbsee> the mighty StevenK monster has woken up!  argh!
[01:07] <StevenK> :-P
[01:07] <crimsun> somerville32: did you fix the issue I asked about?
[01:07] <crimsun> (no response is a review-killer)
[01:28] <palski> is "Nominate for Release" used for ubuntu packages?
[01:29] <Fujitsu> palski, yes.
[01:32] <palski> Fujitsu: Since there are no release managers for ubuntu who is accepting nominations?
[01:32] <Fujitsu> palski, ubuntu-core-dev members can accept them.
[01:32] <Fujitsu> Which is rather annoying.
[01:32] <dholbach> palski: there are release managers
[01:33] <dholbach> Fujitsu: core-dev members can do what?
[01:33] <palski> lp says: "There is no release manager for Ubuntu" =)
[01:33] <Fujitsu> dholbach, accept release nominations.
[01:33] <Fujitsu> More stupid LP-imposed bottlenecks.
[01:33] <Fujitsu> Only the drivers of a distribution can accept them.
[01:34] <dholbach> palski: there's the ubuntu-release team
[01:34] <siretart> what does the nomination for release do?
[01:34] <dholbach> Fujitsu: Where does it say the process works like that?
[01:34] <Fujitsu> dholbach, in the code. It was discovered through practice.
[01:35] <dholbach> aha
[01:35] <Fujitsu> They say they'll look at it `post-1.0'
[01:35] <Fujitsu> It is quite an inconvenience.
[01:39] <siretart> Fujitsu: what's the deal with the 'Nominate for release' links?
[01:39] <Hobbsee> hey siretart :)
[01:39] <Fujitsu> siretart, what about them?
[01:39] <siretart> huhu Hobbsee 
[01:39] <siretart> Fujitsu: what are they for?
[01:39] <Fujitsu> Anybody can nominate, but only core-dev can accept them.
[01:39] <siretart> Hobbsee: you pinged me earlier?
[01:39] <\sh> new wine is on its way...
[01:39] <Fujitsu> They supersede the `Backport fix to releases' link.
[01:40] <Hobbsee> siretart: yep.  laserjock suggested it, can we get a mailing list for ubuntu-universe-sponsors on tiber please?
[01:40] <Hobbsee> \sh: yay :)
[01:40] <siretart> okay, but when should I click on the link? when to nominate?
[01:40] <siretart> Hobbsee: sure. do you want to admin it?
[01:40] <Hobbsee> siretart: you'd you tell me what i need to do in terms of adminning....
[01:40] <Fujitsu> siretart, it's for requesting fixes in stable releases, basically. Just adding a task for that distrorelease.
[01:41] <Hobbsee> s/you/ have to/
[01:41] <Hobbsee> siretart: i've never admined a list before - as long as it's not too difficult, then yeah, that's fine
[01:41] <Fujitsu> Hobbsee, that regexp won't work!
[01:41] <siretart> Hobbsee: no, its standard mailman and completely web driven
[01:42] <Hobbsee> siretart: right
[01:42] <Hobbsee> Fujitsu: no, probably wouldnt :P
[01:42] <StevenK> s/you /have to /
[01:42] <StevenK> Would, though
[01:42] <Fujitsu> StevenK, yep.
[01:43] <siretart> Hobbsee: btw, on tiber, there is no mailman installed. I'm setting one up on freiburg.tauware.de (my private vserver)
[01:43] <StevenK> Fujitsu: You don't have to tell me, I know. :-)
[01:43] <Fujitsu> StevenK, of course! You are one of the deities around here.
[01:43] <StevenK> siretart: If you want to add me as a list-admin, I'm happy to be one.
[01:44] <Fujitsu> tiber is another Canonical ServerPronto box, isn't it?
[01:44] <Hobbsee> siretart: cool :)
[01:44] <Hobbsee> StevenK: sure you are - you're a DD
[01:45] <StevenK> Just being a DD doesn't make me a deity.
[01:45] <Fujitsu> StevenK, why not?
[01:45] <siretart> Hobbsee: you should have mail with an initial password now
[01:45] <StevenK> Just because I have a account on a bunch of machines doesn't make me any more or less special than any of you guys.
[01:45] <siretart> StevenK: do you happen to know if mailman supports multiple list-admins?
[01:46] <siretart> Fujitsu: right
[01:46] <StevenK> I think it does.
[01:46] <siretart> hmm
[01:46] <StevenK> Oh, it does
[01:46] <siretart> ah, yes I found it
[01:46] <siretart> stevenk@ubuntu.com?
[01:46] <StevenK> Sounds fine
[01:47] <siretart> Hobbsee: StevenK and you are now listadmins. please pass StevenK the list password after you got/changed it
[01:47] <siretart> have fun! :)
[01:47] <StevenK> We'll be sure to tell you when we've broken it.
[01:48] <siretart> :)
[01:48] <StevenK> :-)
[01:48] <Hobbsee> siretart: coo, sure
[01:48] <Hobbsee> haha
[01:53] <Hobbsee> siretart: thanks for that
[01:54] <crimsun> rock
[01:55] <geser> Hobbsee: where to subscribe to the u-u-s ml?
[01:56] <Hobbsee> yay, kde
[01:57] <siretart> geser: http://lists.tauware.de/listinfo/ubuntu-universe-sponsors
[01:57] <siretart> geser: but let Hobbsee first do the initial configuration for the list
[01:58] <geser> ok
[01:58] <Hobbsee> hehe
[01:58] <Hobbsee> i have to figure *how* to
[02:08] <siretart> Hobbsee: slammed by mailman ;)
[02:08] <Hobbsee> siretart: sorry?
[02:09] <siretart> Hobbsee: I mean overwhelmed by the thousand of options you can set in the admin interface
[02:10] <Hobbsee> siretart: ah, yes :)
[02:19] <cypherbios> Hey people, 0.1~beta1+svn20070108-0ubuntu1 is an good number version? Or is wrong/too long??
[02:19] <cypherbios> s/number version/version number/
[02:20] <geser> looks ok to me
[02:21] <cypherbios> geser: thanks :)
[02:22] <persia> cypherbios: I'd recommend avoiding ~ unless you really need it: it breaks word selection in GNOME Terminal.
[02:23] <cypherbios> persia: hmm... but if I wont use this '~' the version number will break, won't?
[02:25] <persia> cypherbios: If it's a svn pull, I'd use 0.1+svn20070108-0ubuntu1, as it likely doesn't match a released beta.  If it's a released beta, you would do as well with 0.1+beta1.   As + is less than all the numbers, you shouldn't have any issues later, even if 0.11 is released.
[02:27] <geser> it depends on the next released version
[02:27] <cypherbios> persia: humm, make sense. So I think that 0.1+svn20070108-0ubuntu1 is more sane in this case, what you think?
[02:28] <geser> cypherbios: will the next released version be 0.1 or 0.2?
[02:28] <cypherbios> geser: probably will not have an new beta, the next upstream release will be 0.1
[02:28] <persia> cypherbios: That sounds fine to me.
[02:28] <cypherbios> geser: s/not have/haven't/
[02:28] <persia> cypherbios: If this is pre-0.1, you might want 0.0+svn... instead.
[02:29] <geser> cypherbios: 0.1 < 0.1+svn20070108
[02:30] <cypherbios> geser: 0.1~beta1+svn20070108 < 0.1 ?
[02:30] <enyc> There seems to be a problem (or many-day-delay) with upload -- https://launchpad.net/ubuntu/+source/qpsmtpd/+bug/78005 -- Version: 0.31.1-4ubuntu0.1~proposed1   has not appeared in the archive
[02:30] <Ubugtu> Malone bug 78005 in qpsmtpd "[SRU]  request: dapper:qpsmtpd fix for bug #72602" [Undecided,Unconfirmed]  
[02:31] <geser> cypherbios: dpkg --compare-versions 0.1~beta1+svn20070108 \< 0.1 && echo "yes"
[02:31] <Hobbsee> geser: you can subscribe now, i think
[02:34] <Hobbsee> siretart: email would have been fine, btw, or queried my |nothere, client :)
[02:34] <Hobbsee> siretart: or just wait for me online again :P
[02:40] <enyc> crimsun: see abevoe note, your upload appears to have not ggone trough
[02:40] <enyc> crimsun: aha... I have no w subscribed the archive admins... forgot that! lol
[02:42] <persia> Hobbsee: My message to Ubuntu-universe-sponsors awaits moderator approval.  Should I join the list to submit bugs there, or are you willing to accept spam?
[02:43] <Hobbsee> persia: um....
[02:44] <Hobbsee> persia: is that just your change on LP?
[02:45] <persia> Hobbsee: LP generated mail from me based on a change to the list.  The list bounced to me because it is members-only.
[02:45] <Hobbsee> persia: yes....that was supposed to be fixed...
[02:46] <geser> Hobbsee: "You have successfully confirmed your subscription request to the mailing list Ubuntu-universe-sponsors, however final approval is required from the list moderator before you will be subscribed. Your request has been forwarded to the list moderator, and you will be notified of the moderator's decision."
[02:46] <Hobbsee> geser: done
[02:46] <geser> thanks
[02:46] <StevenK> Hobbsee: Hrm?
[02:47] <Hobbsee> StevenK: persia's comments
[02:47] <persia> StevenK: LP is sending mail (as me) to U-U-S, and I receive a notice that it awaits moderator approval.
[02:48] <StevenK> persia: Approved.
[02:50] <persia> StevenK: Thanks, but my worry is that U-U-S will not receive new patches without extra effort.  That's fine for you and Hobbsee, but geser won't see the patches until one of you approves the message (or am I missing something)
[02:51] <Hobbsee> persia: explanation:  "hobbsee hasnt touched mailman before, this is still a work in progress"
[02:51] <geser> persia: I still can look them up in LP
[02:52] <persia> geser: Yes, but that's no different than from when Hobbsee was the only bug contact.  I say this because I've seen significant improvement in U-U-S processing since mail was distributed to additional people.
[02:53] <persia> Hobbsee: No worries: I'm just reporting my experience.
[02:54] <Hobbsee> right.  we're ignoring it till later.
[02:55] <Guard] [an> hello
[02:57] <Guard] [an> i'm new to building debian packages: let say i have an application that uses autotools, in a directory like myapp/ myapp/src myapp/data etc... would it be possible to generate multiple debian packages out of this ? like 1 package for the core application, and several packages for data/plugins ?
[02:57] <Guard] [an> or do i need to have one directory and 1 build script per plugin ?
[02:58] <geser> you can build several packages from one source
[02:59] <geser> you have to say which files belong to which package
[02:59] <persia> Guard] [an: It's possible, but note that building multiple packages from a single source is significantly more complicated than a one-to-one relationship.  You will need to configure your Makefiles to install to separate directories (or tour debian/ directory will be hard to maintain)
[02:59] <Guard] [an> then i guess i need to read the maintainer guide again :)
[03:00] <crimsun> enyc: I subbed u-a on Jan 6
[03:00] <crimsun> enyc: it has to be approved by u-a before it will be synced out to the mirrors
[03:00] <crimsun> enyc: that approval has yet to occur
[03:00] <Guard] [an> well i guess the 1 source for multiple packages pattern applies since most of the stuff additional packages have to install will end in /usr/share/myapp/plugins/
[03:01] <crimsun> siretart: / Hobbsee: cheers for the u-u-s list migration
[03:01] <Hobbsee> crimsun: i subscribed you to the u-u-s list, it's a WIP
[03:01] <persia> Guard] [an: Do any of the plugins conflict, would they be used by other packages, or are they really large (so the user doesn't want them all installed)?  It might be easiest just to install all the plugins.
[03:02] <crimsun> Hobbsee: seems to work well; got persia's latest change to 47299
[03:03] <Hobbsee> crimsun: cool.  that was manually approved
[03:03] <crimsun> oh, going through moderation?
[03:03] <Hobbsee> at the moment
[03:03] <persia> crimsun: It's Tuesday for most of Australia :)
[03:04] <Guard] [an> persia: it's very large so the user don't want them all, and it's really specific to my test application
[03:04] <Hobbsee> crimsun: right now, it's about 1am.  with two aussies, we'll deal with it in the morning :P
[03:06] <crimsun> persia: we have two different patches in 47299
[03:08] <persia> crimsun: neutrinomass's patch is only for the .desktop file.  Mine is a debdiff including that (and the Encoding line).
[03:10] <crimsun> persia: the Categories don't match
[03:10] <persia> crimsun: "Application" doesn't validate
[03:26] <geser> slomo: Hello, I'm looking at the merge of libsexymm 0.1.9-2. The only remaining change is the bump of build-depends libsexy-dev from >= 0.1.7 to >= 0.1.9. Merge or sync?
[03:30] <persia> crimsun: Umm..  What?
[03:31] <crimsun> persia: s/edgy/feisty/
[03:31] <persia> crimsun: OOps.  Which?
[03:31] <crimsun> cupsys-pt. Fixed and uploaded.
[03:32] <persia> crimsun:  Thanks.  Sorry about that.
[03:36] <enyc> crimsun: Oh I see, it needs another +1  (bug 78005)...
[03:36] <Ubugtu> Malone bug 78005 in qpsmtpd "[SRU]  request: dapper:qpsmtpd fix for bug #72602" [Undecided,Unconfirmed]  https://launchpad.net/bugs/78005
[03:37] <crimsun> enyc: no it doesn't, it has 3
[03:37] <crimsun> enyc: it has already been uploaded; it just has to be accepted by u-a
[03:41] <crimsun> enyc: note the accepted: http://adhd.irule.net/~crimsun/Screenshot.png
[03:58] <xopher-> Hi! Anyone have the time to check this out, Im sure its something trivial.. Having problems with prevu: http://rafb.net/p/yoSGGC52.html
[04:03] <Hobbsee> xopher-: bug jdong about prevu-crack
[04:03] <xopher-> You're not interested ? :P
[04:04] <Hobbsee> not overly.  more to the point of "he knows the code, none of us do"
[04:04] <xopher-> Anyway, should probably update prevu anyway, using some ancient version, could be fixed in a later version
[04:04] <xopher-> That's a good pointer
[04:04] <Hobbsee> ...
[04:05] <Hobbsee> of *course* you should be using the latest version, before coming to ask about error messages
[04:05] <Hobbsee> for bug fix releases, anyway
[04:06] <crimsun> but I -like- using known-broken versions.
[04:06] <crimsun> you know, and then I won't mention that I know it's known-broken.
[04:06] <Hobbsee> crimsun: :P
[04:06] <Hobbsee> crimsun: and you'll ask it of people who have never used it anyway?
[04:08] <xopher-> Hobbsee I was. Just wasn't 100.001% sure of it at the time, update could come any minute
[04:10] <bddebian> Heya gang
[04:10] <Hobbsee> heya
[04:10] <Lutin> heya bddebian
[04:11] <bddebian> Hi Hobbsee, Lutin
[04:11] <Hobbsee> OK, bedtime for me
[04:11] <bddebian> Gnight
[04:34] <Lutin> bddebian: could have a look to gfaim please ? =)
[04:34] <siretart> Hobbsee|NotHere: sorry?
[04:41] <cypherbios> geser: ping
[04:42] <geser> cypherbios: pong
[04:42] <bddebian> Lutin: Yeah, give me a bit
[04:42] <cypherbios> geser: Lintian says: "E: packagename: bad-version-number 0.1~beta1+svn20070108-0ubuntu1"
[04:42] <cypherbios> geser: it's normal?
[04:43] <Lutin> bddebian: ok, np :)
[04:44] <geser> cypherbios: sorry, I don't know. perhaps somebody else can answer this
[04:45] <cypherbios> geser: is about the package that we are talking about 1 hour ago, remember?
[04:46] <cypherbios> geser: btw, np :)
[04:46] <geser> yes, but I don't know if lintian is right
[04:47] <geser> Lutin: 01_gfaim.patch is leaking memory
[04:47] <cypherbios> someone knows if 0.1~beta1+svn20070108-0ubuntu1 is really an bad-version-number?
[04:48] <Lutin> geser: did I forget to free something ?
[04:48] <bddebian> cypherbios: What does lintian -i say?
[04:48] <persia> cypherbios: According to http://www.debian.org/doc/debian-policy/ch-controlfields.html, only alphanumeric and . + - : are allowed (no ~)
[04:48] <geser> Lutin: you free only if loc != NULL
[04:48] <cypherbios> bddebian: E: packagename source: bad-version-number 0.1~beta1+svn20070108-0ubuntu1
[04:49] <cypherbios> persia: hmm, but I need to do something to 0.1~beta1+svn... be less than 0.1-0ubuntu1
[04:49] <Lutin> geser: and whar is the pint to free something NULL ?
[04:50] <Lutin> what's the point*
[04:50] <xopher-> cypherbios if it's only for your own purposes, itll still work just fine, and be a lesser version. so why not use it. no one is perfect anyway
[04:50] <Lutin> geser: forget what I just said :)
[04:50] <persia> cypherbios: How about 0.0+svn20070108-0ubuntu1 (you previously indicated it was neither a 0.1 or beta1 release).
[04:51] <xopher-> or 0.0.99+, which would be closer to the 1.0
[04:52] <xopher-> s/1.0/0.1
[04:53] <cypherbios> xopher-, persia: hm, could be. There is no problem with 0.0.99+svn20070108-0ubuntu1 so?
[04:54] <persia> cypherbios: Personally, I prefer to avoid +, but it's commonly used for cvs/svn indicators, and that version is definitely < 0.1.
[04:54] <cypherbios> persia: thanks, will be 0.0.99+... so :)
[04:57] <cypherbios> bddebian: what you think about it?
[04:58] <bddebian> I see ~ used a lot these days so I dunno, sorry :-(
[05:00] <Lutin> bddebian, geser: ok, fixed now
[05:00] <dholbach> hiya proppy
[05:17] <persia> How does one request a retry of a build?
[05:18] <slomo> geser: sync
[05:28] <geser> persia: a failed build?
[05:30] <persia> geser: Yes  Rapidsvn failed to build 2006-12-15, due to an insufficient version of libsvn.  This has been fixed, and it should build now (it certainly builds locally for me).  I can generate a patch for a new version (with useful changes) if that is easier, but a rebuild fixes 90% of the known issue.
[05:31] <bddebian> Just do a -Xbuild1 push
[05:32] <persia> bddebian: Nah - if a new upload is required, I'd rather fix the other 10%.  I thought there might be a magic button in LP that would retry the build.
[05:33] <geser> persia: ask Mithrandir in #ubuntu-devel to give-back rapidsvn
[05:34] <persia> geser: Thanks.
[05:36] <cypherbios> bddebian: please, see if still +1 for you, if not leave some comments.
[05:37] <cypherbios> bddebian: http://revu.tauware.de/details.py?upid=3996
[05:41] <bddebian> Lutin: What is the purpose behind debian/legal.txt?
[05:41] <persia> cypherbios: If you are installing a .desktop, you need dh_desktop in order to refresh the user's active menus after the install.
[05:42] <cypherbios> persia: the Makefile does this, at make-time
[05:43] <persia> cypherbios: dh_desktop does postinst/postrm changes.  Your Makefile shouldn't.
[05:44] <cypherbios> persia: hmm...
[05:44] <cypherbios> persia: so, how can I do it?
[05:45] <persia> cypherbios: Add dh_desktop after dh_installman in debian/rules
[05:46] <cypherbios> persia: just it? or I need to do something else to dh_desktop recognise the .desktop file?
[05:46] <Lutin> bddebian: the very important prpose to show you that I'm kind of stupid =)
[05:47] <bddebian> Lutin: No, that's OK, I am just asking :-)
[05:47] <Lutin> bddebian: forgot to remove it
[05:47] <persia> cypherbios: Just that.  dh_desktop will change the postinst to call update_menus, which will then read the .desktop installed by the Makefile into the current session.
[05:47] <cypherbios> persia: so I keep the installation done by Makefile also, right?
[05:47] <bddebian> Lutin: No worries
[05:48] <persia> cypherbios: Yes.  Only add the one line.
[05:48] <cypherbios> persia: I got it, updating...
[05:48] <cypherbios> persia: tnx
[05:59] <cypherbios> persia: done ;)
[06:03] <Lutin> bddebian: ping ?
[06:03] <bddebian> Yo
[06:04] <Lutin> bddebian: imprec is a little wrapper script internally used by gfaim for printing
[06:04] <Lutin> do I really need to add a manpage for it ?
[06:05] <bddebian> Hmm
[06:06] <cypher1> arghh.. Proxy error (some upstream server error) when adding comments to launchpad.. does anyone else facing the same problem
[06:15] <Lutin> bddebian: ?
[06:17] <bddebian> Lutin: Hmm == I don't really know for sure :-)
[06:17] <Lutin> bddebian: ah ok :)
[06:17] <Lutin> bddebian: is there someone I could bug about that ?
[06:19] <cypher1> geser, i was looking at the genpower build failure
[07:02] <Nafallo> !info wlassistant
[07:02] <ubotu> wlassistant: User friendly KDE frontend for wireless network connection. In component main, is optional. Version 0.5.5-0ubuntu3.2 (edgy), package size 115 kB, installed size 572 kB
[07:20] <somerville32> Can anyone please review? http://revu.tauware.de/details.py?upid=3993
[07:36] <LaserJock> oh man
[07:36] <LaserJock> the inventor of Ramen noodles died Saturday
[07:37] <bddebian> Heya LaserJock
[07:38] <LaserJock> hi bddebian 
[07:39] <ajmitch> hi LaserJock 
[07:39] <bddebian> ajmitch!!
[07:44] <Nafallo> !info network-manager-gnome
[07:44] <ubotu> network-manager-gnome: network management framework (GNOME frontend). In component main, is optional. Version 0.6.3-2ubuntu6 (edgy), package size 245 kB, installed size 1608 kB
[07:45] <giskard> Nafallo, prr ;)
[07:45] <somerville32> Hi LaserJock
[07:45] <somerville32> LaserJock: I figured out all my issues :)
[07:46] <dholbach> somerville32: lucky you ;-)
[07:46] <Nafallo> giskard: hi mate :-)
[07:46] <somerville32> dh_pysupport looks at several different locations *based* on the package name.
[07:46] <Nafallo> giskard: you don't happen to have nm-svn packaged somewhere? :-)
[07:46] <somerville32> The program's name is pyNeighborhood
[07:46] <somerville32> So it installs to /usr/share/pyNeighborhood
[07:46] <bddebian> somerville32: reviewed
[07:47] <somerville32> However, the package name "pyNeighborhood" violates policy so is made to become "pyneighborhood".
[07:47] <giskard> Nafallo, no :( do you want it?
[07:47] <somerville32> So what I had to do was pass /usr/share/pyNeighborhood to py_support to make it looks there instead of /usr/share/pyneighborhood
[07:48] <somerville32> lol
[07:48] <LaserJock> somerville32: ahh, I see
[07:48] <somerville32> So simple yet I've been pulling my hair out for the last two weeks! :D
[07:48] <Nafallo> giskard: I was thinking about it. but I think the proper fix to my problem would be to use rt2x00 instead of rt2500 legacy driver. wext is fun to have I've heard ;-)
[07:49] <somerville32> bddebian, thanks :)
[07:49] <somerville32> Woot! One advocacy! :D
[07:49] <somerville32> LaserJock: Would you have time for a quick review? :)
[07:50] <zul> hey LaserJock 
[07:50] <LaserJock> somerville32: perhaps, what's the URL
[07:50] <LaserJock> hi zul 
[07:51] <somerville32> http://revu.tauware.de/details.py?upid=3993
[07:54] <LaserJock> and registers for Spring 2007 :/
[07:58] <LaserJock> hmm, so this is my 17th semester in a row
[07:58] <LaserJock> how pathetic
[07:58] <zorglu_> semester = 6month ?
[07:59] <LaserJock> well, technically they are about 15 weeks
[07:59] <LaserJock> but there's only 2 main ones a year
[07:59] <LaserJock> fall and spring
[07:59] <LaserJock> if I counted Summer it'd make me cry ;-)
[07:59] <zorglu_> so it is like 8.5 years....
[07:59] <zorglu_> quite a lot :)
[07:59] <LaserJock> yeah :/
[08:01] <zorglu_> phd at least ? :)
[08:01] <LaserJock> yeah
[08:01] <LaserJock> at least I better
[08:02] <zorglu_> well not that bad then :)
[08:07] <LaserJock> heh, my first "short" planet post :-)
[08:11] <somerville32> :)
[08:33] <LaserJock> somerville32: so are you liking dpatch ok?
[08:33] <somerville32> I love it!
[08:34] <LaserJock> somerville32: cool
[08:34] <somerville32> LaserJock: Did you get a chance to review yet? : )
[08:35] <LaserJock> working on it now
[08:35] <somerville32> Any complaints so far?
[08:36] <LaserJock> not really
[08:36] <LaserJock> I personally like to stick with 3.7.2 for Standards-Version
[08:36] <LaserJock> but that's no biggy
[08:41] <LaserJock> somerville32: the only thing I'm not sure about is your mixing pyNeighborhood and pyneighborhood
[08:41] <Adri2000> fam conflicts on gamin... so fam depencies should be replaced with gamin, right?
[08:42] <somerville32> LaserJock: pyNeighborhood is the upstream name. 
[08:42] <somerville32> pyneighborhood is the package name
[08:42] <LaserJock> somerville32: I know
[08:42] <persia> Adri2000: Most packages seem to use fam | gamin (both seem to have ongoing development)
[08:43] <somerville32> LaserJock: What would be the issue?
[08:45] <LaserJock> case-sensitive tab completion ;-)
[08:45] <Adri2000> persia: right
[08:45] <somerville32> LaserJock: I still don't see the issue. There are tons of commands that aren't all lowercase.
[08:46] <LaserJock> somerville32: I just like consistency :-0
[08:46] <LaserJock> :-) rather
[08:47] <somerville32> LaserJock: I'll keep that in mind for the future. :)
[08:53] <LaserJock> somerville32: ok, little bit of a problem
[08:53] <somerville32> Oh no :(
[08:53] <LaserJock> somerville32: the md5sums of the .orig.tar.gz doesn't match the md5sum of the tarball downloaded from the website
[08:54] <Lutin> Toadstool: pingus
[08:54] <somerville32> Is it because I did: gzip -d *; tar -xf *.tar; gzip *.tar ?
[08:54] <somerville32> (to unpack)
[08:54] <LaserJock> probably
[08:55] <somerville32> Is it... admissible?
[08:55] <LaserJock> I'd like it fixed :-)
[08:55] <somerville32> Can I fix it w/o re-uploading?
[08:56] <somerville32> I don't want to lose my 1 advocate, lol
[08:56] <Lutin> LaserJock: if you have a minute, could you have a look at gfaim on revu and tell me if you think I really should add a manpage for imprec ?
[08:56] <persia> When is the universe merge deadline again?
[09:01] <Lutin> persia: 8 feb iirc
[09:02] <LaserJock> somerville32: yeah, you can send me the correct .orig.tar.gz
[09:02] <LaserJock> somerville32: I think there is a wiki page on how to compress them right
[09:02] <somerville32> LaserJock : I think so too. I'll go read it.
[09:03] <persia> Lutin: Thanks.  I was worried it was sometime this month (and looking at the list of my patches that need to be merged).
[09:03] <somerville32> LaserJock: If I e-mail you the correct tarball, will you upload to universe? :)
[09:04] <Adri2000> question to MOTUs: If I want to fix a bug in a package which version is (example) 0.1.2-3 in ubuntu and 0.1.3-1 in debian, can I use the debian source, fix the bug and upload that without requesting a sync first? (I think the answer is yes, just to confirm)
[09:05] <persia> Adri2000: Yes, but you will want to document the merge with a merge bug, and be sure to upload as 0.1.3-1ubuntu1 (IANAM)
[09:05] <Adri2000> merge? if the current version in ubuntu has no change, it's not a merge
[09:06] <persia> Adri2000: Right.  I read that wrong.  Please ignore everything above except the part about the version number.
[09:06] <Adri2000> :p
[09:07] <crimsun> yes, you can upload 0.1.3-1ubuntu1.
[09:07] <LaserJock> somerville32: yes, I will
[09:07] <ajmitch> yes, you are expected to upload 0.1.3-1ubuntu1 as long as it's before UVF :)
[09:07] <Adri2000> crimsun: and I should generate a .changes file with change since the 0.1.2-3 ?
[09:08] <crimsun> yes.
[09:08] <Adri2000> changeS since the 0.1.2-3 version, ok
[09:08] <somerville32> If you upload something and the version is 0.7.0-beta3... would it be wrong if someone packages it as version 0.7.2?
[09:09] <somerville32> *0.7.3
[09:09] <crimsun> yes
[09:09] <somerville32> Well, someone did
[09:09] <somerville32> lol
[09:09] <somerville32> Or I think they did atleast
[09:09] <somerville32> picard 0.7.2-2ubuntu1
[09:09] <somerville32>  Component: universe Section: sound on Mon,  4 Dec 2006 00:32:12 +0100 by Lukas Lalinsky <lalinsky@gmail.com> 
[09:09] <somerville32>         picard     - Next-Generation MusicBrainz audio files tagger
[09:09] <ajmitch> then they shouldn't have
[09:09] <ajmitch> & they should be taken out the back
[09:09] <somerville32> http://musicbrainz.org/news/picard.html
[09:10] <somerville32> Latest release is 0.7.0 
[09:10] <Adri2000> crimsun: I will apply for membership tomorrow, if you want to say something at the CC...
[09:10] <somerville32> 0.7.0-Beta2 was released recently
[09:10] <somerville32> or not so recently?
[09:10] <Lutin> Adri2000: =)
[09:12] <somerville32> ajmitch, crimsun: nvm
[09:12] <somerville32> That page is old
[09:23] <LaserJock> somerville32: figure out the md5sum problem?
[09:23] <somerville32> Almost :] 
[09:26] <Lutin> LaserJock: if you have a minute, could you have a look at gfaim on revu and tell me if you think I really should add a manpage for imprec ?
[09:27] <LaserJock> Lutin: where does imprec get installed to?
[09:28] <somerville32> LaserJock: What did you get for a checksum?
[09:29] <LaserJock> somerville32: of the downloaded tarball?
[09:29] <Lutin> LaserJock: /usr/bin
[09:29] <somerville32> LaserJock: Yes.
[09:29] <LaserJock> somerville32: 1cecae28bb5753f39fb0b6a9a0f5364e
[09:30] <LaserJock> Lutin: it seems a little odd to do a manpage for it
[09:31] <LaserJock> Lutin: "Each program, utility, and function should have an associated manual page included in the same package. It is suggested that all configuration files also have a manual page included as well. Manual pages for protocols and other auxiliary things are optional."
[09:31] <Lutin> LaserJock: ok :)
[09:31] <Lutin> LaserJock: just wanted to be sure
[09:31] <LaserJock> Lutin: perhaps this is an "auxiliary thing" but I don't know
[09:32] <Lutin> I think it is
[09:32] <LaserJock> seems more like a utility
[09:32] <LaserJock> but an axiliary utility
[09:32] <Lutin> it's a oneline wrapper used internally for printing
[09:33] <LaserJock> my only thought would be that I don't know if /usr/bin is the best place to put it if it's just internal
[09:33] <Lutin> not even a utility that could be useful to someone/thing else but the program itself
[09:33] <LaserJock> but whatever
[09:33] <Lutin> LaserJock: where should I put it then ?
[09:35] <LaserJock> I don't know :-)
[09:36] <LaserJock> I think I'd probably just leave it as it is
[09:37] <Lutin> ok
[09:37] <somerville32> LaserJock: Link. I'm having problems connecting for some reason
[09:37] <somerville32> sf.net is horribly slow now with all their resource intensive javascript
[09:37] <Lutin> LaserJock: if you have some ime to review it then ... =)
[09:38] <LaserJock> hehe
[09:38] <LaserJock> Lutin: I'll put it on my todo list
[09:39] <Lutin> LaserJock: ok, thanks :)
[09:39] <somerville32> s/Link./Link?
[09:39] <LaserJock> is bddebian around?
[09:40] <bddebian> No :)
[09:40] <LaserJock> bddebian: oh well :(
[09:40] <bddebian> LaserJock: Whatcha need man?
[09:41] <LaserJock> bddebian: your review of gfaim
[09:41] <bddebian> Yeah?
[09:41] <LaserJock> there was a lintian warning about a binary without a man page
[09:41] <bddebian> Yeah, Linda warning, lintian error
[09:42] <LaserJock> IMO, it's ok
[09:42] <LaserJock> as the binary in question is an internally use wrapper with 1 line
[09:42] <bddebian> Lutin: Probably the best thing to do then would to just be to add a lintian override
[09:43] <LaserJock> bddebian: what do you think about it?
[09:43] <bddebian> Yeah, I think it's bogus but I'm no "policy" expert by any stretch :-)
[09:43] <shawarma> Why not move it to usr/lib/gfaim ?
[09:45] <Lutin> bddebian, LaserJock: do you both think an override would be ok ?
[09:45] <LaserJock> Lutin: yes
[09:45] <Lutin> ok
[09:45] <LaserJock> shawarma: "/
[09:45] <bddebian> shawarma: That's a thought too
[09:45] <LaserJock> bah
[09:46] <LaserJock> my paste doesn't work
[09:46] <LaserJock> LSB says "/usr/lib: Libraries for programming and packages"
[09:46] <LaserJock> s/LSB/FHS/
[09:47] <shawarma> bddebian: {,/usr}/{,s}bin should really only be for stuff that a user should be calling. If a user should be calling it, it needs a man page.
[09:47] <shawarma> LaserJock: libexec, then.
[09:48] <shawarma> /usr/lib includes object files, libraries, and internal binaries that are not intended to be executed directly by users or shell scripts. [22] 
[09:48] <Adri2000> crimsun: still here?
[09:48] <shawarma> "internal binaries"
[09:48] <shawarma> LaserJock: Also from FHS.
[09:49] <Lutin> bddebian, LaserJock: just dput'd gfaim, should be ok in a couple of minutes =)
[09:49] <LaserJock> shawarma: ah, that does look better
[09:50] <bddebian> Here's from the Debian policy manual:  "Each program, utility, and function should have an associated manual page included in the same package."
[09:50] <LaserJock> somerville32: you got a .orig.tar.gz yet? my trigger finger is getting tired ;-)
[09:50] <LaserJock> bddebian: but for "axuiliary things" it's optional
[09:51] <shawarma> bddebian: which section?
[09:51] <bddebian> Where's that stated?
[09:51] <LaserJock> I think /usr/lib/ is the best
[09:51] <bddebian> shawarma: 12.1
[09:51] <LaserJock> bddebian: right after the part you quoted
[09:52] <shawarma> bddebian: I think it's implied that it's only programs, utilities or functions that the end user should care about. 
[09:52] <LaserJock> I think the most "correct" way to do it is /usr/lib
[09:52] <shawarma> bddebian: There's no need to document every private funtion inside each program.
[09:52] <bddebian> :-)
[09:53] <LaserJock> shawarma: right, but those should also not be in /usr/bin ;-)
[09:53] <LaserJock> well, in seperate files anyway
[09:53] <shawarma> LaserJock: Exactly.
[09:54] <ScottK> I've got a packaging question that I'm not sure how to solve...  There is a PERL package that used to distribute two programs.  Upstream, because one of the programs was not going to be updated anymore, they broke it into two packages.  The other program has a new updated version.  Debian (and Ubuntu from Debian) currently has the last integrated version packaged.  Is there a way I can update a single existing package int
[09:54] <ScottK> r REVU?
[09:54] <geser> LaserJock: seems like I got g-c-u build with libgoffice-0
[09:55] <geser> can you test it?
[09:55] <imbrandon> no more noodles ;(
[09:55] <zul> there will always be noodles just no new noddles
[09:55] <imbrandon> ahh true
[09:55] <zul> and you are making me hungry
[09:56] <imbrandon> hehe
[09:56] <zul> crud its 4 already?
[09:56] <somerville32> LaserJock, almost got it :] 
[09:56] <imbrandon> 3 , shush
[09:57] <Lutin> LaserJock: so, /usr/lib or override ?
[09:58] <LaserJock> geser: certainly
[09:58] <LaserJock> Lutin: I now prefer /usr/lib :-)
[09:59] <geser> LaserJock: http://members.ping.de/~mb/gchemutils/
[09:59] <bddebian> doh
[10:00] <shawarma> *G* It's always fun to stop by, cause a stir, and the fade back into silence. :-)
[10:00] <LaserJock> mhm
[10:00] <bddebian> Yeah, "thanks" shawarma ;-)
[10:01] <somerville32> LaserJock, Ok. Just want me to upload to revu?
[10:01] <shawarma> bddebian: :-)
[10:01] <LaserJock> well, why don't you just send it to me, so I can just upload it
[10:01] <shawarma> bddebian: any time.
[10:02] <LaserJock> geser: ok, I've got it, building now
[10:02] <LaserJock> so much for a nice productive day at work
[10:03] <ajmitch> LaserJock: just ignore irc
[10:04] <somerville32> LaserJock: e-mail?
[10:04] <LaserJock> mantha@u.c
[10:05] <somerville32> Just the .org.tar.gz?
[10:05] <LaserJock> yep
[10:17] <somerville32> LaserJock, Did you get it? :] 
[10:18] <LaserJock> yep
[10:18] <somerville32> All goods? :] 
[10:18] <somerville32> Does an Archive Admin or something have to review it first?
[10:18] <somerville32> Or does it go right into Universe?
[10:21] <geser> somerville32: if it's a completely new package it needs to be reviewed by an archive admin
[10:22] <Toadstool> heya everybody
[10:22] <somerville32> How long should it take?
[10:22] <geser> the review? some days (it depends on the archive admins)
[10:22] <Lutin> heya Toadstool, how are you ?
[10:23] <somerville32> Who are archive admins?
[10:23] <somerville32> aka, who is someone I can bug, lol
[10:23] <Sp4rKy> heya Toadstool :)
[10:24] <Sp4rKy> please, i've a python app, but the install script is a bash script (install.sh). How can set cdbs to run install.sh and not setup.py for installation ?
[10:24] <Toadstool> hey Lutin, Sp4rKy 
[10:25] <bddebian> Hi Toadstool
[10:26] <Toadstool> Sp4rKy: take a look at /usr/share/cdbs/1/class/python-distutils.mk, you want to modify DEB_PYTHON_SETUP_CMD in your debian/rules
[10:26] <Toadstool> hey bddebian 
[10:26] <Sp4rKy> Toadstool: thx :)
[10:26] <Toadstool> Sp4rKy: and maybe a couple of other variables 
[10:27] <Toadstool> Sp4rKy: hint: the documentation for cdbs is cdbs itself :p
[10:27] <Sp4rKy> :)
[10:27] <bddebian> heh
[10:35] <Lutin> bddebian, LaserJock: gfaim should be ok now, could you have a look ? =)
[10:36] <Sp4rKy> Toadstool: strange, i've added the variable but it doesn't work
[10:37] <Sp4rKy> Toadstool: and the duckorp doc doesn't talk about smthg else
[10:40] <Toadstool> Sp4rKy: never really modified this variable, can I have a look at your package?
[10:41] <Sp4rKy> Toadstool: i just try smthg
[10:41] <Sp4rKy> and upload it if it doesn't work
[10:42] <Sp4rKy> ok, it "works"
[10:42] <Sp4rKy> but the issue is it's a bash install script
[10:43] <Sp4rKy> and python-distutils run python install.sh :/
[10:43] <Sp4rKy> so i shouldn't use python-distutils class :)
[11:00] <somerville32> Hobbsee :)
[11:00] <somerville32> Hobbsee, I got my package uploaded. Say yea for me! :)
[11:02] <Hobbsee> hey somerville32.  yay :)
[11:02] <ScottK> Now he gets to join the club waiting for NEW.
[11:03] <ajmitch> Hobbsee: you're up early
[11:03] <Hobbsee> ajmitch: yes.  meeting
[11:03] <ajmitch> poor soul
[11:05] <Hobbsee> indeed :P
[11:09] <cypherbios> bddebian: if you aren't busy, please say if still +1 from you [if needed]  for this package http://revu.tauware.de/details.py?upid=3999
[11:21] <LaserJock> somerville32: check your ubuntu-motu mailbox ;-)
[11:21] <somerville32> I have a ubuntu-motu mailbox?
[11:22] <somerville32> lol
[11:23] <geser> LaserJock: have you had time to test the g-c-u 0.6 debs?
[11:23] <crimsun> Adri2000: yes
[11:24] <Adri2000> crimsun: could you take a look at http://adrishost.homeip.net/~adri2000/ubuntu/toupload/doodle_0.6.6-1ubuntu1.debdiff please
[11:24] <crimsun> in 20 mins
[11:24] <Adri2000> to fix bug 78497 as specified in the changelog
[11:24] <Ubugtu> Malone bug 78497 in doodle "doodled package can't be removed" [Medium,Confirmed]  https://launchpad.net/bugs/78497
[11:24] <Adri2000> ok
[11:24] <crimsun> (meeting atm)
[11:24] <LaserJock> geser: gah, gimme a sec. I forgot about that
[11:30] <crimsun> LaserJock: which source package for pyneighbourhood did you upload?
[11:30] <LaserJock> crimsun: the one from REVU + fixed .orig.tar.gz
[11:31] <crimsun> does the generated binary still dump the dirs into /usr/share/python-support/ ?
[11:31] <crimsun> since somerville32 has seen fit to completely ignore the question from my reviewing
[11:33] <LaserJock> crimsun: you reviewed it?
[11:34] <bddebian> LaserJock: You gonna archive that upload? :-)
[11:34] <LaserJock> oh, crikey
[11:35] <crimsun> LaserJock: yes
[11:35] <Adri2000> shawarma: do you know how to apply the same fix you have just upload for listen to a perl program? :)
[11:35] <somerville32> crimsun: What question?
[11:35] <LaserJock> crimsun: ok, I don't see it on REVU
[11:36] <somerville32> Umm...
[11:36] <somerville32> pyNeighborhood doesn't generate a binary
[11:36] <crimsun> it absolutely does, what other deb are you going to install?
[11:37] <crimsun> it's fairly useless for a source package to not generate a binary package
[11:37] <somerville32> oh
[11:37] <somerville32> For the binary package, it places the source code in /usr/share/pyNeighborhood/src/
[11:37] <somerville32> and places a script in /usr/bin/
[11:37] <crimsun> the dirs issue that I pointed out 12 hours ago?
[11:37] <somerville32> crimsun: Didn't get it.
[11:38] <crimsun> LaserJock: do you still have the source package that you uploaded, and if so, may I download and pbuild?
[11:38] <LaserJock> crimsun: darn it you're right
[11:39] <somerville32> What did I do wrong?
[11:39] <LaserJock> somerville32: you are installing pyneighborhood.dirs to /usr/share/python-support
[11:40] <Sp4rKy> why a ls debian/packagename or ls debian/tmp with cdbs doesn't works ?
[11:40] <Sp4rKy> in the install/packagename:: section
[11:40] <Lutin> Sp4rKy: why do you want to ls ?
[11:41] <somerville32> LaserJock, What is pyneighborhood.dirs?
[11:41] <somerville32> From the dh_pysupport manpage:
[11:41] <somerville32> "       If a file named debian/pyversions exists, it is installed in /usr/share/python-support/$PACKAGE/.ver
[11:41] <somerville32>        sion.
[11:41] <somerville32> "
[11:42] <Sp4rKy> Lutin: it's a test, because a mv doesn't work :)
[11:42] <Lutin> Sp4rKy: oh, I see
[11:42] <Lutin> Sp4rKy: what package ?
[11:42] <Sp4rKy> entrance :D
[11:42] <Lutin> hehe
[11:42] <Lutin> nice =)
[11:42] <Toadstool> Sp4rKy: let me see your debian/rules
[11:42] <Sp4rKy> oh,no, devede  not entrance ^^
[11:43] <Sp4rKy> Toadstool: of course
[11:43] <Lutin> Sp4rKy: grrr =)
[11:43] <Sp4rKy> Toadstool: http://pastebin.ca/310626
[11:43] <Sp4rKy> Lutin: cdbs appears to doesn't work properly if i use tarball.mk && simple-patchsys
[11:43] <somerville32> crimsun, LaserJock: that file must be generated by the pysupport or something. I don't have a pyneighborhood.dirs file
[11:44] <Lutin> Sp4rKy: lol
[11:44] <LaserJock> somerville32: I see that
[11:44] <crimsun> it is generated by python-support
[11:44] <Lutin> Sp4rKy: I have about 20 packages which all uses simple-patchsys and tarball.mk perfectly
[11:44] <shawarma> Adri2000: Heh.. which one?
[11:44] <Lutin> Sp4rKy: are you talking about cdbs-edit-patches ?
[11:44] <Sp4rKy> Lutin: i guess :)
[11:44] <Sp4rKy> Lutin: indeed
[11:44] <Lutin> heh
[11:44] <crimsun> somerville32: my question is whether it's correct for your source package
[11:44] <Lutin> don't use it =)
[11:45] <LaserJock> crimsun: I'm afraid I don't see the problem. Is he installing the .py to the wrong place?
[11:45] <Sp4rKy> Lutin: grrr, why ?
[11:45] <crimsun> LaserJock: it's not a problem; see above
[11:45] <somerville32> crimsun, LaserJock: There are all kinds of .dirs file in /usr/share/python-support
[11:45] <crimsun> somerville32: of course
[11:45] <LaserJock> somerville32: but look at the contents
[11:45] <Toadstool> Sp4rKy: try to move your install/devede:: target after the include
[11:45] <LaserJock> somerville32: of yours
[11:46] <Lutin> Sp4rKy: patching the files the old way will take you less time than trying to make cdbs-edit-patches work properly =)
[11:46] <crimsun> the contents -should- be correct, but have you verified it?
[11:46] <somerville32> no
[11:46] <Sp4rKy> Lutin: ok ...
[11:46] <Sp4rKy> Toadstool: i try
[11:46] <crimsun> somerville32: that's all the question was
[11:46] <LaserJock> it points to the dir above teh actual .py files
[11:46] <Adri2000> shawarma: in fact I'm not sure your fix fixes the bug I'm thinking about. I'm thinking of that: killall gnome-panel and then the icon in the notification area doesn't re-appear, is it the bug you fixed?
[11:46] <LaserJock> I'm not sure it it matters
[11:46] <shawarma> Adri2000: Nope.
[11:47] <LaserJock> crimsun: it looks ok to me
[11:47] <crimsun> LaserJock: it's a process question
[11:47] <LaserJock> mhm
[11:48] <Sp4rKy> Toadstool: not better :/
[11:48] <Sp4rKy> Toadstool: http://pastebin.ca/310636
[11:48] <Sp4rKy> the last part of my build
[11:48] <LaserJock> crimsun: dget http://tiber.tauware.de/~laserjock/pyneighborhood/pyneighborhood_0.4-0ubuntu1.dsc
[11:48] <crimsun> persia: please don't unassign the person who uploaded your source package
[11:48] <Adri2000> sharms: ah :( I just tried killall gnome-panel and programs like rhythmbox, gaim reappeared, but checkgmail didn't, maybe you have an idea how to fix that... :)
[11:49] <Adri2000> shawarma* ^
[11:49] <persia> crimsun: What?  I don't remember doing that.  Which bug?
[11:50] <crimsun> persia: cupsys-pt
[11:50] <LaserJock> geser: still around?
[11:50] <crimsun> 47299
[11:50] <geser> LaserJock: yes
[11:50] <Hobbsee> bug 47299
[11:50] <Ubugtu> Malone bug 47299 in cupsys-pt ".desktop does not validate" [Unknown,Unconfirmed]  https://launchpad.net/bugs/47299
[11:51] <Hobbsee> ah
[11:51] <persia> crimsun: https://bugs.launchpad.net/ubuntu/+source/cupsys-pt/+bug/47299/+activity doesn't show any changes to assignee.  Did something go wrong?
[11:51] <shawarma> Adri2000: Hmm.. Not in perl, that's for sure. :-)
[11:52] <Adri2000> shawarma: okay :p
[11:52] <persia> crimsun: Ah, never mind, I see it now.  I didn't mean to do that.  Sorry.
[11:53] <crimsun> persia: (I use it to track self-blame for uploads ;)
[11:54] <Sp4rKy> so, sleep time
[11:54] <LaserJock> geser: well, it seems to work
[11:54] <Toadstool> Sp4rKy: change install/devede to binary-post-install/devede
[11:54] <Sp4rKy> gd night :)
[11:54] <LaserJock> geser: I'm just checking on your specific chages
[11:54] <Sp4rKy> Toadstool: i check
[11:54] <persia> crimsun: Wait, no.  I didn't paste that statusexplanation.  I am suspicious of the log.  I only set it Fix Released when it built on all architectures (which doesn't show in the log)
[11:55] <Toadstool> Sp4rKy: wait... do you ever call install.sh in your debian/rules? :)
[11:55] <persia> crimsun: Never mind.  I don't understand, but I'll try not to do it again.
[11:56] <Sp4rKy> Toadstool: no
[11:56] <Lutin> hehe, it maybe the cause then
[11:56] <Sp4rKy> Toadstool: in fact, i don't use it at all, and i only install files by hand
[11:56] <crimsun> persia: well, I won't rule out an LP boog
[11:56] <geser> LaserJock: please check if I got the conflict/replaces against the old packages right
[11:56] <Lutin> Sp4rKy: in the rules you pasted, you seem to install nothing
[11:56] <Toadstool> Sp4rKy: then, do you really think that anything will be installed in debian/devede/usr/bin/?
[11:56] <Sp4rKy> Lutin: Toadstool oh yep, it may be the cause ^^
[11:57] <Sp4rKy> Lutin: i use a .install file :)
[11:57] <Sp4rKy> Toadstool: works now !
[11:57] <Sp4rKy> with binary-post-install :D
[11:57] <Toadstool> ok great
[11:57] <Toadstool> cdbs dark magic
[11:57] <Sp4rKy> so, the last part of this package will be done tomorrow
[11:57] <Sp4rKy> sleep now 
[11:57] <Toadstool> good night
[11:57] <Lutin> g'night Sp4rKy
[11:58] <Sp4rKy> good night
[11:58] <Sp4rKy> thx Toadstool :)
[11:58] <geser> persia: see the second last change (assignee): old value = crimsun ; new value = 
[12:01] <persia> geser: Yes, some of my comments above are misinterpretation (the rendered page is significantly wider than my browser), but I still don't understand why it happened (and only for this bug, out of the many favours that crimsun has extended me recently).
[12:04] <LaserJock> geser: the only thing I might say is to maybe just add our Replaces/Conflicts, instead of replacing the Debian ones
[12:04] <persia> On an unrelated note, I have questions about sync's and drops.  If a package is dropped from Debian, will it automatically be dropped from Ubuntu?  Is a bug required to force it to drop before feisty release?  Also, if there is a newer Debian package, but it offers no tangible benefit, should it be sync'd?
[12:05] <LaserJock> persia: for the first, a bug needs to be filed if we want it gone
[12:05] <LaserJock> for the second, it's kinda up to the person doing it. if you don't think it's worthwhile then don't do it, IMO
[12:06] <geser> LaserJock: what's the point on conflicting on libgcu02ca which isn't in Ubuntu?
[12:06] <geser> for those who installed the Debian packages?
[12:06] <persia> LaserJock: Thanks.
[12:06] <LaserJock> geser: keeping tighter to Debian and yeah, if somebody installed the Debian .debs
[12:07] <geser> LaserJock: something else to fix?
[12:07] <LaserJock> geser: also, you need to take out the config.{sub,guess} out of your .diff.gz
[12:07] <LaserJock> geser: but the apps seem to work fine
[12:08] <LaserJock> geser: none of the libgoffice changes were on the core libraries
[12:09] <geser> LaserJock: how? I see several packages copying config.{sub,guess} from autotools-dev from the clean target
[12:09] <geser> that's why it's in the diff.gz
[12:09] <LaserJock> use filterdiff to get rid of them then
[12:10] <LaserJock> it's a mess to have them in debdiffs
[12:10] <geser> why do I need a debdiff?
[12:10] <LaserJock> well, you don't, but I did :-)
[12:11] <LaserJock> I like to check on what I'm changing from Debian
[12:11] <geser> I do it also, but I'm nearly used to skip over config.{sub,guess} when reading a debdiff
[12:12] <geser> persia: no, you need the original config.{guess,sub} from the orig.tar.gz
[12:13] <geser> else you get the removal of then in the diff.gz
[12:13] <LaserJock> I think probably the best solution is to put the config.{guess,sub} lines in configure: instead of clean:
[12:14] <LaserJock> but that's not what dh_make does