[12:15] <StevenHarperUK> so I need to look at python distutils, and work out how to get it all working with that first : then do the correct packaging...
[12:15] <ajmitch> yeah
[12:15] <StevenHarperUK> OK this si good info
[12:16] <ajmitch> there are quite a few applications in ubuntu that you can download with 'apt-get source packagename' if you have source repositories enabled
[12:16] <StevenHarperUK> It does work now as a package, even on LIVE CD's, but I can see why I need it distro unspeific
[12:16] <StevenHarperUK> Ta Ill try that
[12:16] <ajmitch> you've got some very distro-specific stuff in there, like python-support directories
[12:16] <ajmitch> that should be all handled automatically by debian helper scripts
[12:16] <StevenHarperUK> Yes I want to lose them
[12:17] <StevenHarperUK> they do nothing atm anyway
[12:17] <StevenHarperUK> There from the Package I was copying
[12:17] <ajmitch> it looks like you looked at a binary package, rather than the source
[12:18] <ajmitch> looking at the source package would probably have made your job much easier: )
[12:18] <StevenHarperUK> Yes I bet
[12:18] <StevenHarperUK> I had to hand make the package : check my build.xml and build.sh :P
[12:19] <StevenHarperUK> Some nightmares making the Hashes of all the files
[12:19] <StevenHarperUK> I knew I was doing ot wrong
[12:20] <StevenHarperUK> OK thanks for all the Help, I have other commitments tonight, but ill be trying all  this tomorrow : keep your eyes on the REVU for it ---- Steve
[12:36] <Burgundavia> LaserJock: you around?
[12:43] <imbrandon> gnight all
[12:43] <dabaR> Hey, nigbt
[12:59] <sacater> imbrandon: gnight, thanks, i got membership
[12:59] <sacater> LaserJock: same to you, thanks very much
[12:59] <sacater> ScottK: and you, thanks
[12:59] <sacater> pochu: thanks to you as well :D
[01:01] <_Enchained> hi motus
[01:01] <_Enchained> can anyone remove this package from revu : http://revu.tauware.de/details.py?upid=5252 ?
[01:02] <_Enchained> and review this one : http://revu.tauware.de/details.py?upid=5323 :p
[01:09] <joejaxx> man it has been a long day
[01:18] <jmg> hokay, lets see if the gutsy upgrade works today.
[01:22] <sacater> joejaxx: youre day is TEENY compared to mine
[01:23] <joejaxx> jekil: keep your feisty kernel lol
[01:23] <joejaxx> grr
[01:23] <joejaxx> jmg: *
[01:23] <joejaxx> i am running gutsy with the feisty kernel
[01:23] <joejaxx> sacater: :P
[01:24] <jmg> joejaxx: but im trying to test to see if a bug is fixed in the gutsy kernel
[01:24] <sacater> joejaxx: i havnt slept for 38 hours
[01:24] <sacater> go me
[01:24] <joejaxx> sacater: that is nothing :P
[01:25] <sacater> joejaxx: go on...
[01:26] <sacater> joejaxx: what is that, ive heard it but never actually looked it up
[01:26] <ajmitch> a chronis inability to sleep
[01:27] <ajmitch> s/chronis/chronic/
[01:27] <sacater> ooh
[01:27] <LaserJock> I most definately don't have insomnia
[01:27] <LaserJock> I get 8-10 hrs of sleep
[01:27] <joejaxx> sacater: yeah it is not fun either
[01:28] <joejaxx> :(
[01:28] <LaserJock> otherwise I'm toast the whole day
[01:28] <sacater> its not hard to never sleep, provided you know what you are doing
[01:28] <joejaxx> well i get 9 hours more development time i guess you could say
[01:28] <LaserJock> heh
[01:28] <sacater> i mean, there is one guy who hasnt slept for a decade
[01:29] <joejaxx> his body takes second-cycle naps i assure you
[01:30] <LaserJock> about the only time I've gone more than 24hrs is silly trips to UDSs
[01:30] <joejaxx> there is no way he could stay up with no rest/sleep/hibernation/whateveryouwanttocallit for 10 years
[01:30] <joejaxx> LaserJock: you should see the picture of me on the first day haha
[01:31] <joejaxx> i look so bad
[01:31] <joejaxx> i never thought i looked that tired
[01:31] <LaserJock> heh
[01:31] <LaserJock> I arrived in Sevilla around noon on the first day of UES
[01:32] <LaserJock> so I went from the plane straight into BOFs
[01:32] <ajmitch> heh
[01:32] <joejaxx> oh wow
[01:41] <AndyP> i can't wait til i'm in a position to fly around the world attending linux conferences and suchlike, at the moment i
[01:41] <AndyP> 'm pretty bogged down
[02:09] <superm1> ScottK, ping
[03:02] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[03:05] <nixternal> ryanakca: did you package this one from scratch?
[03:06] <nixternal> never mind
[03:06] <nixternal>  * Initial release :)
[03:06] <nixternal> is it in Debian yet?
[03:08] <nixternal> and that answer would be no as well. since you got the hang of it for this package, why don't you create one for Debian Unstable and then file an ITP (once it has been OK'd of course)..and then you can just request a sync
[03:09] <nixternal> forgot I was using a lab machine for a sec
[03:09] <_Enchained> this package is waiting also for a review ;) http://revu.tauware.de/details.py?upid=5323
[03:09] <_Enchained> if anyone has a little time
[03:39] <ScottK> superm1: Pong
[03:40] <superm1> Hi ScottK.  I updated that package's debian/copyright.  i wanted to see if I could get you to look it over again?
[03:41] <crimsun> dabaR: sorry, was called away to a meeting.  Any progress?
[03:41] <ScottK> superm1: I have a little time I think.  What's the link to the new version?
[03:41] <superm1> ScottK,  http://revu.tauware.de./details.py?upid=5324
[03:44] <ScottK> superm1: debian/copyright looks much better.  Please wrap lines to be less than 80 characters. 
[03:45] <superm1> ah me and my spoiled 1600x1200 laptop display :)
[03:45] <ScottK> superm1: Why are you installing lgpl.txt in debian/docs?
[03:45] <superm1> because it was shipped with the package
[03:45] <superm1> just like a COPYING file would be installed
[03:45] <superm1> (and have the same contents) as what lgpl.txt had
[03:47] <ScottK> But we already have a copy of lgpl in /usr/share/common-licenses/LGPL.  I suppose that makes sense.  Don't change it if no one else complains I guess (I'm a new MOTU, so I'm not yet all knowing).
[03:50] <superm1> well on my last package,  it was indicated that a full copy of the GPL or LGPL or what not needs to be provided *with* the package
[03:50] <crimsun> (have to distribute copies of whatever licenses under which the source, etc., is)
[03:50] <ScottK> OK.  Leave it then.
[03:50] <leonel> hello ScottK ..
[03:51] <ScottK> hello leonel
[04:01] <leonel> ScottK: is there a wiki page with the clamav status ?
[04:08] <LaserJock> evening all
[04:09] <Hobbsee> hi LaserJock 
[04:09] <ajmitch> hello LaserJock 
[04:10] <LaserJock> hi Hobbsee and ajmitch 
[04:12] <ajmitch> shame I'll probably be busy or asleep for the Q&A sessions
[04:12] <ajmitch> 00:00UTC is 12:00 here, so it'll be just in my lunchtime when I head out
[04:12] <LaserJock> maybe at some point we could do an OpenDay
[04:13] <LaserJock> having Q&A sessions with MOTU School sessions
[04:13] <crimsun> just send your questions to LaserJock; he'll answer them -and- send a pony!
[04:13] <ajmitch> yay ponies!
[04:13] <LaserJock> uggg
[04:13] <Hobbsee> mmm...ponies
[04:13] <superm1> omg ponnies!
[04:13] <LaserJock> crimsun: you severly underestimate my knowledge :-)
[04:14] <crimsun> you're right, I know you're part of the MOTU trinity, so I shouldn't doubt you.
[04:14] <LaserJock> blah :(
[04:15] <LaserJock> I can't even think
[04:15] <ajmitch> he answers questions before they are asked?
[04:15] <LaserJock> s/underestimate/overestimate/
[04:15] <crimsun> ;)
[04:15] <LaserJock> see, I can't be a deity with typos like that
[04:17] <superm1> although that is very deity like to correct your mistake with a regex, LaserJock 
[04:19] <crimsun> he's just testing us, anyhow.
[04:45] <superm1> ScottK, that one line that was > 80 lines was shrunk and uploaded, if you did a build, could you leave some comments/advocating or not advocating on revu?
[05:18] <ScottK> superm1_: Probably not tonight.  It's getting late and I'm not sure I know enough yet to advocate that package.  I will try and take a look at it tomorrow and see.
[05:18] <superm1_> great thanks ScottK i appreciate it
[05:32] <joejaxx> any of you all see this? https://launchpad.net/ubuntu/+ppas
[05:33] <LaserJock> of course ;-)
[05:34] <nixternal_> oi oi MOTU land
[05:34] <superm1> LaserJock, could I bug you for a little for a revu?
[05:34] <LaserJock> not tonight sorry
[05:35] <crimsun> LaserJock is special.  Remember that not only is he a part of the MOTU trinity, he's the MOTU liaison to the LP dev team.
[05:35] <crimsun> you can assume he knows about "it" already.
[05:35] <LaserJock> heh
[05:35] <LaserJock> Fujitsu usually knows twice as much as I do when it comes to LP
[05:35] <nixternal_> he knew about it before you pressed enter on that dput line
[05:35] <LaserJock> but I've got my connections ;-)
[05:36] <nixternal_> he is telepathic
[05:36] <nixternal_> or is it psychopathic
[05:36] <LaserJock> the latter I'm sure
[05:36] <nixternal_> aren't we all though
[05:36] <LaserJock> siretart caught a good PPA bug today though
[05:37] <Hobbsee> the main one?
[05:37] <Fujitsu> That was a nice bug, yes.
[05:37] <nixternal_> haha, tonight my instructor fell for the Church of Emacs and St. Ignucious and how I am not allowed to use Microsoft software
[05:37] <nixternal_> holy smokes I about died
[05:37] <Fujitsu> nixternal_: Hahah.
[05:37] <LaserJock> nixternal_: heh
[05:37] <nixternal_> I even gave her the link tot he Church of Emacs site
[05:37] <nixternal> silly netsploits
[05:38] <LaserJock> darn, why has nixternal changed color in my irssi :/
[05:38] <LaserJock> how annoying
[05:38] <nixternal> haha
[05:38] <nixternal> I am colorpathic
[05:38] <LaserJock> you were orange
[05:38] <LaserJock> now you're blue
[05:38] <nixternal> good, Kubuntu blue!
[05:38] <nixternal> muhehe
[05:39] <LaserJock> hmm, that reminds me
[05:39] <LaserJock> I don't think I've really been in KDE since Feisty was released
[05:39] <nixternal> LaserJock: remember Edgy? :p
[05:39] <crimsun> he should remember edgy.  That's when he was appointed to the trinity.
[05:40] <nixternal> was he appointed or did he just automagically (either by the grace of a higher being or by...Linux for Humans!)
[05:40] <nixternal> gah
[05:40] <nixternal> hit enter to soon
[05:40] <nixternal> I ruined that one
[05:40] <joejaxx> lol
[05:42] <LaserJock> ok, gimme a sec
[05:45] <LaserJock> phew, back
[05:45] <LaserJock> now in KDE
[05:46] <LaserJock> awesome, my CPU is 0MHz
[05:46] <LaserJock> think of all the battery I'm saving
[05:46] <Fujitsu> Heh.
[05:46] <LaserJock> I have no idea what you just said
[05:46] <Fujitsu> Yes, it was very badly put.
[05:47] <joejaxx> actually there is a bug in ppa already
[05:47] <ScottK> Good night all.
[05:47] <joejaxx> https://launchpad.net/fedora/+ppas
[05:47] <joejaxx> example^
[05:47] <superm1> night ScottK 
[05:47] <crimsun> this hit 'n' run "please help" business doesn't not compute.
[05:47] <crimsun> 'night
[05:48] <Fujitsu> The `Latest Uploads' part of a distro page show PPA uploads with the rest, and links to /ubuntu/gutsy/+source/package/release-that's-only-in-ppa, so being a 404.
[05:48] <jsmidt> Is Hobbsee around?
[05:48] <Hobbsee> jsmidt: somewhat, yes.
[05:48] <LaserJock> Fujitsu: oops
[05:48] <Hobbsee> TheMuso: ping
[05:48] <TheMuso> Hobbsee: You sent me a contentless ping.  This is a contentless pong.  Please provide a bit of information about what you want and I will respond when I am around.
[05:49] <joejaxx> lol
[05:49] <TheMuso> Hobbsee: Heya.
[05:49] <jsmidt> Hobbsee, I was wondering, you rejected my bug which was fine saying it was a sync not a merge.  But dont you requests syncs through bug reports too?
[05:49] <jsmidt> I am wondering what I did incorrectly
[05:49] <Hobbsee> jsmidt: i did - you'll see a filed one later.  i used the requestsync script
[05:49] <Hobbsee> nothing - it's just easier to use a script to file the sync request, rather than letting you manually write one, and going back to ack that
[05:50] <jsmidt> Okay, should I use that script in the future?
[05:51] <Hobbsee> you could - but if you do, change the code so it subscribes ubuntu-universe-sponsors, instead of ubuntu-archive, as you're not a MOTU
[05:51] <Hobbsee> TheMuso: hi!
[05:52] <TheMuso> Hobbsee: How goes it?
[05:52] <jsmidt> Okay, thanks Hobbsee 
[05:52] <Hobbsee> TheMuso: assignmenst and such.  i really should go into uni, but hte wifi there is dead
[05:52] <TheMuso> heh
[05:54] <Hobbsee> jsmidt: no problem
[05:54] <Hobbsee> jsmidt: i requested the sync of kile originally, and knew it didnt end up building - it's one of the packages we maintain inside debian, and just sync across
[05:55] <Hobbsee> prior knowledge about a package helps - that happens for a fair few of the kde packages in ubuntu
[05:55] <jsmidt> Makes sense.  
[06:39] <LaserJock> ok, I need some expert advice
[06:39] <LaserJock> I'm removing the gnuchess building from gcompris
[06:40] <LaserJock> is it best to comment out all building parts
[06:41] <StevenK> LaserJock: You can go either way. Doing either of commenting it out or removing it will show it has changed. I find it's up to personal preference.
[06:42] <crimsun> I tend to comment out unless I know it's just not going to be used again, and then I note as much in debian/changelog.
[06:42] <crimsun> but yes, very much preference
[06:42] <LaserJock> but do I need to take out all references
[06:43] <LaserJock> s/need/should/
[06:43] <crimsun> "all references"?
[06:43] <crimsun> across the source package?
[06:43] <crimsun> i.e., what's the scope of your change?
[06:44] <LaserJock> I took everything out of the configure{,.in} and Makefile.{am,in}
[06:44] <LaserJock> gcompris has a chess game that uses gnuchess
[06:45] <LaserJock> I need to stop it from building that part
[06:45] <crimsun> hmm, there's no --disable-gnuchess or --with-gnuchess=no ?
[06:46] <LaserJock> heh, you'd think so, but no
[06:46] <LaserJock> this package basically doesn't use configure flags like it should
[06:46] <LaserJock> it only has the generic flags
[06:47] <crimsun> well, you can do as you've done (which may invoke an autoreconf [or its effects]  due to timestamp skew - haven't looked at the actual source package)
[06:47] <crimsun> doesn't ultimately matter, I suppose, since you'll have to regenerate configure regardless
[06:47] <LaserJock> blah
[06:48] <LaserJock> I'll just try to build it and see
[06:48] <crimsun> that's kind of gross
[06:48] <crimsun> worth an upstream wishlist bug report IMO
[06:48] <LaserJock> well, you'd think they'd do something
[06:49] <LaserJock> you can't install gnome-games and gcompris at the same time
[06:50] <Burgundavia> oh geez
[06:51] <LaserJock> and so I gotta hack away at gcompris
[06:51] <LaserJock> since they don't provide any configure flags
[06:52] <Burgundavia> why not provide a patch upstream to have a configure flag?
[06:52] <LaserJock> well, that would be nice
[06:53] <crimsun> is there no configure.ac?
[06:53] <StevenK> Hrm. I don't have any autobork foo to suggest how to do that.
[06:54] <LaserJock> crimsun: no
[07:00] <LaserJock> blah blah blah
[07:00] <crimsun> ok, I'm not current with the gnome-games situation [if there's any conflict at hand] 
[07:01] <crimsun> it seems Sid's source package generates an additional binary package that Gutsy's doesn't, but Gutsy has a newer source version.  That's not relevant, is it?
[07:01] <LaserJock> gnome-games has a conflicts/replaces with gnuchess
[07:01] <LaserJock> so gnuchess was dumped to Universe
[07:01] <LaserJock> gcompris is in Main and deps on gnuchess, therefore FTBFS, boom
[07:02] <crimsun> do you mean build-deps or deps?
[07:02] <LaserJock> build-deps
[07:02] <crimsun> if it's only a deps, it certainly shouldn't FTBFS
[07:02] <crimsun> ah
[07:03] <crimsun> nasty.  So gcompris can either dep on gnome-games and thus drag in the gnome stack, or...
[07:04] <crimsun> ah, edubuntu-desktop already Recommends gnome-games
[07:05] <LaserJock> gcompris doesn't build with gnome-games
[07:05] <crimsun> so without the configure hook, is gnuchess functionality still enabled in gcompris?
[07:05] <crimsun> what physically is configure seeking (should be noted in config.log)?
[07:06] <Hobbsee> LongPointyStick: 
[07:06] <Hobbsee> hmm.  still exists
[07:06] <Hobbsee> that's going to time out as soon as i go out, i'm s ure it is.
[07:08] <LaserJock> crimsun: gimme a sec, it's a 100MB source package
[07:12] <crimsun> ok, I need an un[ ,well less-] biased opinion if anyone has time.  Suppose that a user accuses the dist-upgrade process of muting a fairly standard mixer element that's visible in nearly all known audio configurations via KMix, the GNOME volume applet, etc., e.g., 'PCM'.  User then says that the dist-upgrade broke his/her sound but doesn't check the mixer setting.  Are you more inclined to think this is a PEBKAC or a failure in the dist
[07:12] <LaserJock> crimsun: here's the relevant section of the configure http://paste.ubuntu-nl.org/23215/
[07:13] <Fujitsu> crimsun: PEBKAC. Mixer settings can change arbitrarily, and users should really look there first.
[07:13] <Hobbsee> crimsun: well, the dist shouldnt mute the sound midupgrade
[07:13] <crimsun> It's fairly obvious to me that it's a PEBKAC, but I'm a bit too entrenched and thus biased, so I'm seeking opinions.
[07:13] <Hobbsee> although basic troubleshooting is good
[07:13] <Fujitsu> The upgrade shouldn't do it, but it's OK.
[07:14] <Hobbsee> depends if you're aiming to "Just work"
[07:14] <crimsun> right, I'm trying to establish whether "Just work" should -always- be the mantra.
[07:14] <LaserJock> well, I'd be annoyed
[07:15] <LaserJock> but I would probably check the mixer first before filing a bug
[07:15] <crimsun> right, but should I presume that the user will?
[07:15] <crimsun> should I presume, even, that the user -should-?
[07:16] <LaserJock> ideally it'd be nice to fix that kind of thing
[07:16] <LaserJock> but it'd be wishlist for me
[07:17] <LaserJock> crimsun: it looks like it's just finding the gnuchess binary, but I'm not sure
[07:17] <crimsun> I'd like to avoid 1) treating the user as an idiot by assuming (s)he doesn't know what (s)he's doing and thereby proactively sanitising all mixer elements and levels on every boot; 2) not doing "enough" to have sound "Just work".
[07:18] <crimsun> One problem is that I really don't know whether an app or a new kernel or the user himself/herself muted the mixer element(s) in question.
[07:18] <LaserJock> mhm
[07:20] <crimsun> LaserJock: that's what it seems.  I'd just kill that entire section and regenerate configure, then use a hard Depends on gnome-games.
[07:20] <Hobbsee> now there's two...double trouble!
[07:20] <crimsun> or does gnome-games not suffice even as a runtime dep?
[07:20] <LaserJock> crimsun: I honestly have no idea
[07:20] <crimsun> i.e., meaning does gcompris -have- to use gnuchess?
[07:21] <LaserJock> I was just going to kill the chess game from gcompris
[07:21] <LaserJock> but maybe I can s/gnuches/glchess/
[07:21] <LaserJock> I think glchess is what's produced by gnome-games
[07:21] <crimsun> LaserJock: careful, killing that could be a regression from 6.06 LTS ;-)
[07:21] <LaserJock> like I care
[07:22] <LaserJock> oops, was that out loud/
[07:22] <LaserJock> ?
[07:22] <jmg> yes
[07:22] <crimsun> I didn't see anything
[07:22] <nixternal> hahaha
[07:22] <nixternal> crimsun: whistle blowing is bad!
[07:23] <jmg> nixternal: it is?
[07:23] <jmg> why
[07:23] <LaserJock> bah, this stupid package is just so big
[07:23] <nixternal> whistle blowing == snitching or telling on someone
[07:24] <LaserJock> 40MB just to install the .deb
[07:24] <nixternal> damn
[07:24] <crimsun> ***MEMORY-WARNING***: glchess[16911] : GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
[07:24] <crimsun> nice.
[07:24] <LaserJock> umm, where did that come from?
[07:24] <crimsun> I invoked glchess from zsh
[07:25] <crimsun> (gutsy)
[07:25] <LaserJock> hmm
[07:25] <LaserJock> sounds like a winner
[07:25] <crimsun> note that gnome-games binary contains /usr/games/glchess and /usr/games/gnome-gnuchess
[07:26] <LaserJock> hmm
[07:26] <crimsun> not being familiar w/ either, it looks like the latter is used by the former
[07:26] <LaserJock> I wonder if I should talk with gcompris upstream
[07:27] <LaserJock> this went from a simple sync to messy and not fun real quick
[07:27] <StevenK> LaserJock: Fun, innit?
[07:28] <Fujitsu> Doesn't Debian have the new gnome-games?
[07:28] <LaserJock> yep
[07:28] <Fujitsu> Oh, demoted to universe.
[07:28] <LaserJock> that's where we got the packages I think
[07:28] <LaserJock> so people are going to hit this sooner or later
[07:29] <crimsun> well, the first thing I'd establish is whether gcompris has a hard runtime dependency on gnuchess.  If so, does build-depending on gnome-games and using /usr/games/gnome-gnuchess as $GNUCHESS suffice?
[07:29] <LaserJock> it just looks like Edubuntu is the first
[07:29] <LaserJock> crimsun: right, that makes sense
[07:30] <crimsun> if you absolutely can't hack gcompris's build to use gnome-games, then I'd have a conf call with gcompris and gnome-games
[07:30] <crimsun> err, not conf call, but ... you get the idea
[07:30] <LaserJock> heh
[07:31] <crimsun> if, in fact, you -can- get gcompris to work with gnome-games, I'd just kill the crap in configure* anyhow.
[07:31] <crimsun> You shouldn't have to build-dep on gnome-games.
[07:32] <LaserJock> I guess this will go in my core-dev resume :-)
[07:32] <crimsun> definitely some gross, not shiny, crack
[07:32] <Hobbsee> mmm....crack...
[07:33] <jmg> mmm 
[07:33] <LaserJock> hmm, it does look like it's just providing a wrapper around gnuchess
[07:33] <LaserJock> gnuchess_bin = g_build_filename( exec_prefix, "bin", "gnuchess", NULL);
[07:34] <crimsun> eww.
[07:34] <crimsun> you could hack that to use gnome-gnuchess from gnome-games
[07:35] <LaserJock> mhm
[07:35] <crimsun> gnuchess_bin = g_build_filename( exec_prefix, "games", "gnome-gnuchess", NULL);
[07:35] <crimsun> tehehe
[07:37] <LaserJock> I guess I could do the same with the ./configure
[07:37] <LaserJock> but I'm not sure why it's a build-dep
[07:37] <LaserJock> I guess maybe to get the path right?
[07:38] <crimsun> it looks like bin/gnuchess is hardcoded, though
[07:38] <crimsun> it's a pointless build-dep
[07:41] <LaserJock> alrighty, I've got to get to bed
[07:41] <crimsun> 'night
[07:41] <LaserJock> but I think I know what I need to try/do
[07:41] <LaserJock> thanks crimsun 
[07:41] <crimsun> np
[07:42] <Hobbsee> aiee, the evil badger song...
[07:47] <jussi01> crimsun: how did you go with that review of mnemosyne?
[07:48] <crimsun> jussi01: haven't yet.
[07:49] <crimsun> don't worry, it's queued.
[08:02] <jussi01> ok, I dont know if my last question got through, (connection sucks) but crimsun, how did you go with the review of mnemosyne yesterday?
[08:03] <Hobbsee> [15:48]  <crimsun> jussi01: haven't yet.
[08:03] <Hobbsee> [15:49]  <crimsun> don't worry, it's queued.
[08:04] <jussi01> Hobbsee: crimsun thanks
[08:04] <jussi01> :D
[08:57] <LaserJock> crimsun: hah, I just did one s/gnuchess/gnome-gnuchess/ in the ./configure and it finds gnome-gnuchess and builds fine
[08:57] <Fujitsu> LaserJock: Aren't you in bed?
[08:58] <highvoltage> Fujitsu: laptops ftw :)
[09:01] <LaserJock> highvoltage: exactly
[09:04] <LaserJock> anybody running gutsy?
[09:13] <Fujitsu> LaserJock: I am; for what do you wish?
[09:16] <elkbuntu> Fujitsu, a million dollars, kthxbai
[09:25] <LaserJock> darn it, he left
[09:26] <Admiral_Chicago> who?
[09:26] <LaserJock> Fujitsu
[09:27] <Admiral_Chicago> ah i found my way over to MOTU by some odd chance
[09:35] <dholbach> good morning
[09:36] <LaserJock> hi dholbach 
[09:37] <dholbach> LaserJock: heya - great that the MOTU announcements made it to the fridge! your work, I suppose?
[09:37] <LaserJock> yeah, they just made me a Fridge editor
[09:37] <LaserJock> because of Behind MOTU 
[09:37] <LaserJock> so I'm trying to liven things up a bit ;-)
[09:37] <dholbach> ROCK ON
[09:38] <LaserJock> yeah, the hits to Behind MOTU tripled after putting that article on there
[09:38] <LaserJock> I was a bit surprised
[09:38] <dholbach> rock and roll :)
[09:38] <LaserJock> so for sure putting stuff on Fridge is a good thing
[09:39] <LaserJock> if we get some sort of weekly or monthly report going I'd like to put that on the Fridge
[09:40] <dholbach> I suggest we stick to UWN - keeping a report regular is not very easy if people on that team are busy with stuff already
[09:41] <LaserJock> yes, I remember our old MOTU Report
[09:42] <dholbach> exactly
[09:42] <dholbach> I tried it with the bughelper reports too and they were a good thing, I'm just to busy to keep them going
[09:43] <LaserJock> things are a tad easier I think now
[09:43] <LaserJock> reporting REVU uploads and SRUs on -motu provides some info
[09:44] <LaserJock> new MOTU, teams, etc. are good
[09:45] <dholbach> I think I'll do a call for wiki-ing more regularly
[09:46] <dholbach> there's a lot we can do to improve the situation by writing things done - even if it's just a "hey, somebody should write a blurb on <some topic> - I don't find useful information and explained it at least 4 times already" or "the guy I mentor had problems with ... - let's write something down"
[09:48] <LaserJock> for sure
[09:49] <Ash-Fox> Wikis are useful because it additionally means the person can figure out what todo when there isn't a 'mentor'
[09:50] <dholbach> exactly
[09:50] <dholbach> I'll also ask the people I mentor to write things down they found hard to do, which will give us more QA for mentoring
[10:17] <crimsun> LaserJock: yes, but if you already know that's all it needs -at run-time-, then just kill the build-dep
[10:17] <highvoltage> how do I check with which flags something in Ubuntu has been compiled with? for example, I'd like to check whether libsasl2 was compiled with "--with-ldap"
[10:17] <highvoltage> any tips?
[10:18] <crimsun> highvoltage: apt-get source libsasl2; more foo/debian/rules
[10:18] <highvoltage> crimsun: ah, thanks!
[10:18] <crimsun> (presuming you have the deb-src entry for main active)
[10:19] <crimsun> you can also inspect the diff.gz for debian/rules
[11:38] <paran> is it possible to write comments on packages in REVU without being MOTU?
[11:40] <StevenK> Sure, on your own uploads.
[11:41] <paran> no, on some others package
[11:41] <StevenK> Only if you're a reviewer.
[11:42] <paran> but then you need to be a motu
[11:43] <paran> at least according to the wiki
[11:51] <Adri2000> some people are reviewer without being motu
[11:53] <crimsun> those people are extraspeshallike.
[12:00] <dholbach> whooooo - lots of people signing up for ubuntu-motu-mentors
[12:01] <crimsun> :)
[12:02] <dholbach> if only half of them turn into MOTUs, ......... :-D
[12:02] <imbrandon> dholbach, i got someone i'm mentoring ( as of today ) off list, should i have them signup or anything ?
[12:02] <dholbach> imbrandon: sounds like a good idea
[12:03] <dholbach> imbrandon: I'll add some notes about best-practices on the MOTU/Mentoring/Mentor page
[12:03] <imbrandon> i know this guy will become a MOTU, he is my old boss ( moved to a new company )
[12:03] <dholbach> imbrandon: who is it? do you have the LP ID?
[12:03] <dholbach> rock and roll
[12:03] <imbrandon> mocker ( in here e.g. IRC and LP )
[12:03] <imbrandon> dholbach, ^^
[12:03] <dholbach> thanks for mentoring!
[12:03] <crimsun> ah crap, I just subbed
[12:03] <imbrandon> :)
[12:03] <imbrandon> subbed?
[12:04] <dholbach> crimsun: subscribed you already :)
[12:04] <crimsun> ...and then I read the mod list
[12:04] <paran> crimsun: ok. any reason that everybody can't make comments? (off course only motus should be able to advocate)
[12:05] <crimsun> paran: it may have been anti-spam at the time.
[12:05] <paran> crimsun: should be possible to verify your login agains launchpad or something
[12:06] <dholbach> imbrandon: added to the wiki: http://wiki.ubuntu.com/MOTU/Mentoring/Mentor
[12:07] <imbrandon> dholbach, rockin
[12:07] <imbrandon> brb
[12:09] <crimsun> paran: it's something worth raising on the -motu mailing list and adding to the next MOTU meeting's agendum if necessary
[12:10] <txwikinger> Morning folks
[12:10] <crimsun> hi.
[12:11] <paran> crimsun: Ok. I'l send a mail, thanks :)
[12:26] <DarkSun88> Hi all
[12:26] <dholbach> hi DarkSun88
[12:26] <DarkSun88> Hi dholbach :)
[12:28] <thedonvaughn> is there a ubuntu packaging help channel?
[12:28] <thedonvaughn> sorry to ask in here, but i'm not having luck :)
[12:28] <dholbach> thedonvaughn: this is the right place
[12:29] <thedonvaughn> has anyone else had issues creating a pbuilder environment for gutsy?  I keep getting error: chroot <path> mount -t proc proc /proc  debbootstrap failed
[12:30] <thedonvaughn> of course path is the path to my pbuilder chroot, just left that out for easier typing :)
[12:30] <pochu> thedonvaughn: are you running gutsy?
[12:30] <dholbach> thedonvaughn: that's a known bug and being worked on aiui
[12:30] <thedonvaughn> pochu, yes
[12:30] <thedonvaughn> dholbach, ah ok.. that's basically what i wanted to know.  i'll go search for that bug so i can follow/help.  thanks
[12:32] <thedonvaughn> what are you guys doing to contribute packages to gutsy's universe?  just not building with pbuilder? :)
[12:32] <dholbach> thedonvaughn: I set up my pbuilder before, so it works for me - you can still just build the package locally and once you put it up for review somebody else will test and build it in a chroot/with pbuilder
[12:33] <dholbach> so no need to be blocked on a broken pbuilder :)
[12:33] <thedonvaughn> yah that's what i figure.. cool.
[12:34] <thedonvaughn> what a cool channel, glad i found this
[12:35] <dholbach> thedonvaughn: thanks a lot for helping us out!
[12:35] <thedonvaughn> i work at a datacenter, and we use ubuntu as our workstations.  I'm the one who makes all of our work related programs, scripts, debugging tools etc etc into .deb packages for easy mass deploys :)
[12:35] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[12:35] <thedonvaughn> dholbach, welll... not technically yet... BUT I do plan to.  I really want to infact
[12:36] <dholbach> excellent
[12:37] <thedonvaughn> not new to making .deb's tho and been using debian for atleast 8 years.  ubuntu is excellent and now that gutsy is real new i plan to help out MOTU where i can.  i've already begun researching on the wiki and i've been triaging when i can at launchpad
[12:37] <dholbach> if you need any help, let us know - do you have some patch or package you're working on already?
[12:40] <thedonvaughn> well i was just gona build some of work tools against gutsy's environment.. that's it.  for ubuntu, nothing at the moment.  if memory serves, there was a link for packages needing help?  I was going to start there and see if there is anything i use alot or am pretty familiar with.
[12:41] <thedonvaughn> i would like to see avant-window-navigator, but i'm assuming that package has already been uploaded to REVU... and not sure if it'd be cleared through yet.  
[12:41] <thedonvaughn> i should check that :)
[12:41] <Lutin> p
[12:41] <Lutin> err.
[12:43] <dholbach> thedonvaughn: http://wiki.ubuntu.com/MOTU/Bugs has lists of bugs that might be easy to fix or are being mentored
[12:45] <pochu> And today it's a Hug Day :)
[12:45] <dholbach> yoohoo
[12:45] <thedonvaughn> :)
[12:45] <thedonvaughn> dholbach, right on, i'm gona explore that 
[12:45] <dholbach> rock and roll
[01:00] <dholbach> who of you will be in the 0 UTC Q&A session tonight?
[01:01] <dholbach> (that's in 13 hours from now)
[01:01] <dholbach> I won't make it as it's 2:00 in the morning for me
[01:02] <Lutin> won't be here either, I'm on the same timezone
[01:02] <asac> dholbach: will you be there?
[01:03] <asac> dholbach: oh i can't read
[01:03] <asac> :)
[01:03] <dholbach> np :)
[01:03] <dholbach> I'm sure some people from the US can make it
[01:03] <dholbach> Lutin, asac: 12:00 UTC should be better for us
[01:03] <asac> dholbach: probably get commitments before release next time :)
[01:03] <asac> dholbach: in one hour?
[01:03] <dholbach> asac: we agreed on the times in the MOTU meeting
[01:04] <dholbach> asac: tomorrow, so in 25h :-)
[01:04] <dholbach> #ubuntu-classroom
[01:04] <cyber> hello everybody
[01:05] <asac> dholbach: k will be here
[01:05] <dholbach> hiya cyber
[01:05] <Lutin> dholbach: heh, sure :)
[01:05] <cyber> dholbach: i'm new in here
[01:06] <cyber> i'm entering for first time
[01:06] <dholbach> welcome to the channel then, cyber
[01:06] <dholbach> how's it going?
[01:06] <cyber> may i introduce my self
[01:06] <cyber> i'm from bulgaria (little country next to greece)
[01:07] <cyber> i like the ubuntu idea
[01:07] <dholbach> excellent :-)
[01:07] <cyber> and i inspired from the work of all to make it hapen
[01:07] <cyber> and i want to get involved
[01:07] <cyber> to help 
[01:08] <dholbach> cyber: that's great to hear
[01:08] <cyber> i'm a programmer
[01:08] <dholbach> you can check out http://wiki.ubuntu.com/MOTU/Documentation (the Ubuntu Packaging Guide is a good read) and http://wiki.ubuntu.com/Contributing has some useful links too
[01:08] <cyber> thanks
[01:09] <dholbach> if you need any help, just ask in here, somebody will help you getting started :)
[01:09] <cyber> thanks
[01:09] <dholbach> thank YOU :)
[01:13] <asac> cyber: what kind of programming do you have skills in?
[01:21] <cyber> mainly in php
[01:21] <cyber> also c++
[01:23] <cyber> asac: my job is webdeveloper
[01:23] <cyber> but firs i started programming in c++
[01:24] <asac> cyber: do you know javascript as well?
[01:24] <cyber> nope but i use ready scripts in my web pages
[01:24] <asac> what is a "ready script" ?
[01:24] <cyber> sorry for my english
[01:25] <cyber> for "ready scripts" i mean scripts made by other
[01:26] <asac> ah ok
[01:27] <cyber> the php programming i do myself
[01:32] <pochu> cyber: providing you know c++, you might be interested in the gnomemm Ubuntu team :) https://launchpad.net/~ubuntu-gnomemm
[01:34] <pochu> dholbach: btw, that page (Documentation/Wishlist) ^ is empty here ?
[01:34] <pochu> I mean, it doesn't exists. Did you really create it?
[01:35] <cyber> pochu: as i sayd i'm very new to ubuntu. Can you tell me in few words what is this project gnomemm about
[01:35] <cyber> of course i know what gnome is :)
[01:35] <bmm> crimsun: I'm back. Have you found any new things I need to change on http://revu.tauware.de/details.py?upid=5295 ?
[01:35] <cyber> and i'm familiar to the basics
[01:37] <pochu> cyber: sure :) It takes care (triage bugs, upload new upstream versions, request syncs and do merges...) of the gnomemm related packages: https://bugs.launchpad.net/~ubuntu-gnomemm/+packagebugs
[01:39] <RainCT> Hey
[01:41] <cyber> i'll take a look on the links you gave me and make some installs
[01:41] <cyber> see you
[01:42] <cyber> bye
[01:42] <jekil> hello
[01:43] <dholbach> pochu: MOTU/Documentation/Wishlist - sorry
[01:45] <pochu> ah, ok :)
[02:09] <xxxxx1> morning guys!
[02:14] <ScottK> Good morning xxxxx1
[02:15] <xxxxx1> ScottK :)
[02:21] <ScottK> Adri2000 or Lutin: On DaD, it seems when a package comes back onto DaD it comes with the comment that was there from the previous upload (at least in some cases).  Spamassassin and Scapy are two recent ones.
[02:23] <Lutin> ScottK: thanks for pointing this out, I'll have a look at it asap
[02:26] <pschulz01> Where do I install python programs?
[02:26] <RainCT> how can I find easy to solve bugs?
[02:26] <pochu> RainCT: bitesize tag in Launchpad
[02:26] <pochu> pschulz01: what do you mean?
[02:27] <pschulz01> pochu: I'm packaging a python program.. 
[02:27] <pschulz01> pochu: I know nothing about python.
[02:27] <pochu> pschulz01: I think python-central or python-support install the files in the right place.
[02:28] <pochu> pschulz01: the python policy will be a big help then :) http://www.debian.org/doc/packaging-manuals/python-policy/
[02:28] <pochu> At least it has been for me :)
[02:29] <pschulz01> pochu: Ta.
[02:29] <ScottK> pschulz01: Does your python package have a setup.py?
[02:29] <pschulz01> Yes.
[02:29] <pochu> RainCT: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bitesize
[02:30] <pschulz01> ScottK: Does that help?
[02:30] <RainCT> pochu: ok thanks
[02:30] <ScottK> pschulz01: Yes.  You might want to apt-get source pyyaml and look at that as an example.  
[02:31] <ScottK> pschulz01: If you've got a good setup.py, it's generally very easy with pysupport and cdbs.
[02:32] <pschulz01> ScottK: Wow.. 7 line 'rules' file.
[02:32] <ScottK> Yeah.  As I said, easy.
[02:32] <ScottK> If you let the tools do the work for you.
[02:33] <pschulz01> ScottK: So I don't need to use 'dh_make'
[02:33] <pschulz01> ScottK: :-)
[02:33] <ScottK> Nope.
[02:35] <ScottK> pschulz01: Which version of pyyaml did you get?
[02:35] <pschulz01> 3.04
[02:36] <ScottK> OK.  You might want to download the Gutsy version (3.05) as the package you have has a patching system and a few other things you won't need.
[02:37] <pschulz01> brb
[02:39] <ScottK> dholbach: Mind if I have a go at the clamtk merge?
[02:42] <pschulz01> ScottK: Ok.. back again
[02:42] <jussi01> hello everyone
[02:42] <Nafallo> hmm
[02:42] <Nafallo> no \sh?
[02:43] <ScottK> Hello jussi01
[02:43] <jussi01> ScottK: got a minute toe review mnemosyne?
[02:43] <pschulz01> python-support or python-central ?
[02:43] <kink> hi, I'm a DD with a question. There's a number of bugs reported against my packages in launchpad, which have been fixed in newer versions that are also in ubuntu now. Is there a way to close these bugs?
[02:43] <jussi01> ScottK: :d
[02:44] <TheMuso> kink: Got bug numbers?
[02:44] <Fujitsu> kink: Click on the package name in the `Affects' line and set the status to Fix Released.
[02:44] <jussi01> :D
[02:44] <ScottK> pschulz01: Either.  Generally I'd say python-support unless you need a feature that python-central supports and python-support does not.
[02:44] <kink> Fujitsu, anyone's free to do that?
[02:44] <pschulz01> ScottK: Can I just copy the 'rules' file?
[02:44] <Fujitsu> kink: Right.
[02:44] <kink> Fujitsu, great, will do. thanks.
[02:44] <ScottK> pschulz01: Probably.  Try that for a start.
[02:45] <pschulz01> ScottK: and install cddb?
[02:45] <pschulz01> cdbs?
[02:46] <ScottK> What you should do it make sure it's a build-dep in debian/control and then build in a pbuilder, chroot, or something similar.  Pbuilder will pull in the build-dep's for you.
[02:46] <ScottK> kink: Welcome.
[02:46] <pschulz01> ScottK: Ta..
[02:47] <dholbach> ScottK: not at all
[02:48] <ScottK> dholbach: OK.  I got it then.
[02:51] <RainCT> How can I fix #59036 ?
[02:51] <dholbach> bug 59036
[02:51] <ubotu> Launchpad bug 59036 in doc-base "`Index' value missing for format `info'" [Low,Confirmed]  https://launchpad.net/bugs/59036
[02:52] <xxxxx1> hello Hobbsee
[02:53] <dholbach> RainCT: weird... it looks like adding a line to a file in bzip2 would fix the problem
[02:54] <Hobbsee> hey xxxxx1!
[02:54] <Hobbsee> hi dholbach!
[02:55] <Hobbsee> :D
[02:55] <highvoltage> *grouphug*
[02:56] <imbrandon> lolcode *has* to becomes a full lang
[02:56] <imbrandon> dholbach!
[02:56] <imbrandon> Hobbsee!
[02:57] <Hobbsee> imbrandon!!!
[02:57] <StevenK> There's far too much exclaiming going on.
[02:57] <imbrandon> heh
[02:57] <imbrandon> hrm i wonder if i could muster up enough c++ skillz to write an lolcode intrepriter
[02:58] <StevenK> How about a easier problem?
[02:58] <imbrandon> like ?
[02:58] <StevenK> Learn to spell intrepreter correctly, first?
[02:58] <imbrandon> hahaha
[02:59] <zul> or "skills"
[02:59] <imbrandon> nah, 
[02:59] <zul> uh huh
[02:59] <RainCT> dholbach: I already have that line it says that should fix it on /usr/share/doc-base/bzip2
[03:00] <dholbach> RainCT: and it doesn't fix it?
[03:01] <ScottK> dholbach: Since this is the first Debian package for clamtk (we've been on our own previously), this is a big merge.  I'll do it, but the Debian package is radically different.  Should my approach be to stick with the Debian approach and just add stuff we have that they don't (like the man page)?
[03:01] <RainCT> dholbach: dunno... I'm not going to upgrade from dapper to edgy :p
[03:02] <dholbach> RainCT: ok
[03:02] <StevenK> ScottK: You should try and stay as close to Debian as you can.
[03:02] <dholbach> ScottK: stick to the debian package, I don't even mind if you change the maintainer field
[03:02] <ScottK> OK.  WIll do.
[03:03] <dholbach> I packaged it ages ago, when I looked at the UniverseCandidates list
[03:03] <RainCT> dholbach: and shouldn't it be assigned to bzip2, since it says to add a line to /usr/share/doc-base/bzip2?
[03:03] <ScottK> dholbach: OK.  
[03:04] <dholbach> RainCT: I don't know enough about the bug to say that. Sorry.
[03:04] <kink> RainCT, that bug should be against bzip2, not doc-base
[03:04] <kink> RainCT, recent doc-base became more strict about packages shipping wrong doc-base files
[03:04] <kink> so you need to fix the package that ships the wrong file, i.e. bzip2
[03:16] <RainCT> kink: how can I check if the file is wrong?
[03:24] <mruiz> hi all
[03:25] <xxxxx1> mruiz: hello
[03:27] <mruiz> dholbach: my problem with debootstrap is still there :(
[03:27] <dholbach> I know
[03:28] <dholbach> but as I said... if you're on gutsy already, you can work on that, so no need to be blocked because pbuilder doesn't work
[03:28] <mruiz> yes!
[03:28] <dholbach> somebody whose pbuilder works will test it
[03:28] <StevenK> The debootstrap problem should be sorted out next mirror pulse.
[03:29] <imbrandon> nice
[03:29] <mruiz> :)
[03:29] <imbrandon> sudo apt-get install python-ply python-ply-doc
[03:29] <imbrandon> err
[03:30] <StevenK> Password:
[03:30] <imbrandon> NOPASSWD: ALL 
[03:30] <imbrandon> :)
[03:30] <StevenK> I much prefer sudo adduser <> sudo
[03:31] <imbrandon> StevenK, seen the python lolcode parser ?
[03:31] <StevenK> Nope
[03:31] <imbrandon> one sec
[03:31] <imbrandon> :)
[03:32] <kink> RainCT, see the top message at that bug
[03:33] <imbrandon> StevenK, http://paste.ubuntu-nl.org/23243/
[03:34] <StevenK> I'm this >< close to getting a spoon to make the badness stop.
[03:34] <mruiz> dholbach: remember that I resolved the conflicts... now I have to do:  debuild -us -uc -rfakeroot -k0D3FD8A9 ?
[03:34] <imbrandon> StevenK, a spoon ?
[03:34] <Hobbsee> to gouge his eyes out with
[03:35] <StevenK> Exactly.
[03:35] <dholbach> mruiz: to just build it       debuild -us -uc      is enough
[03:35] <ScottK> dholbach: How strongly do you feel about the no first run patch in clamtk.  It looks to me like except for that, it's a sync.
[03:35] <dholbach> mruiz: debuild uses -rfakeroot itself and -us -uc means: don't sign it (so no -k option needed)
[03:36] <mruiz> dholbach, why without signature ?
[03:36] <dholbach> ScottK: I patched that out ages ago, because it said that it's only needed on Fedora or something, but if it does not hurt, we can drop it
[03:36] <dholbach> mruiz: because you build it locally to test it, no?
[03:36] <imbrandon> heh
[03:36] <dholbach> mruiz: if you want to build a source package, you might want to run       debuild -S -sa   
[03:36] <ScottK> dholbach: It doesn't mention Fedora any more, it just says on some distros you need to edit .conf files.
[03:36] <dholbach> hm, ok
[03:36] <dholbach> not sure if it's still needed
[03:38] <ScottK> dholbach: You don't need to edit the .conf files in Ubuntu or Debian, so the patch is technically correct, but I think it's a trivial detail not worth keeping an Ubuntu diff for.  How about I ask for a sync and send the patch to Debian via BTS and let the Debian maintainer decide if he want it?
[03:38] <ScottK> want/wants
[03:38] <dholbach> ScottK: right, let's drop it
[03:38] <ScottK> OK
[03:38] <ScottK> Thanks
[03:39] <dholbach> thank YOU
[03:42] <mruiz> dholbach: I got some warnings
[03:42] <ScottK> dholbach: You might be glad to know that the Debian package has all the Ubuntu debian/changelog history in it, so that doesn't get lost on the sync.  I'm going to take that as a sign the maintainer was aware of the no first run patch and not file a bug in BTS.
[03:43] <dholbach> mruiz: which ones?
[03:43] <dholbach> ScottK: sounds like it, yes
[03:50] <mruiz> dholbach, I had a problem with my virtual machine. Afterwards, I tried again with "debuild -us -uc" and I got many errors : http://paste.ubuntu-nl.org/23245/
[03:52] <pschulz01> Where does pbuilder get it's 'apt/sources' from? I trying to hit a local apt-cacher.
[03:53] <dholbach> dpkg-source:  new version is symlink
[03:53] <dholbach> dpkg-source:  old version is nonexistent
[03:53] <dholbach> mruiz: ^ what did you do?
[03:54] <mruiz> when my virtual machine was "frozen" I press Ctrl+C
[03:55] <dholbach> dpkg-source: warning: source directory `./mod-bt-0.0.19+p4.2340-1ubuntu1' is not <sourcepackage>-<upstreamversion> `mod-bt-0.0.19+p4.2340'
[03:55] <dholbach> dpkg-source: warning: .orig directory name mod-bt-0.0.19+p4.2340-1ubuntu1.orig is not <package>-<upstreamversion> (wanted mod-bt-0.0.19+p4.2340.orig)
[03:55] <dholbach> I suppose you have a mismatch between the version number in debian/changelog and the directory you're working in
[03:56] <mruiz> dholbach: what's your suggestion ?
[03:56] <dholbach> make sure that the version numbers are correct
[04:01] <ScottK> dholbach: Would you believe the sync is already done.  It was run 6 minutes after I filed the bug.
[04:02] <dholbach> I just saw it on -changes ;-)
[04:02] <mruiz> dholbach: wait me 5 minutes, please
[04:02] <dholbach> ubuntu awesomeness
[04:02] <dholbach> mruiz: take your time - I'm working on other things in the meantime
[04:02] <mruiz> no worries!
[04:02] <dholbach> ScottK: thanks for looking into that
[04:03] <ScottK> dholbach: No problem.  It looks to me like 2.32 actually works with clamav 0.90.x, unlike 2.31, so I'm going to file a feisty-backport request once it builds.
[04:04] <dholbach> rock and roll :)
[04:04] <imbrandon> StevenK, too bad he dident license the lol.py or i would package it for gutsy 
[04:04] <imbrandon> :)
[04:04] <StevenK> No, not bad. *GOOD*.
[04:04] <imbrandon> heh
[04:05] <imbrandon> my buddy at work was like , wow i could program in that
[04:05] <mocker> imbrandon: wassup punk.
[04:05] <imbrandon> heya mocker , david said he is gonna learn lolcode
[04:05] <imbrandon> :)
[04:06] <mocker> Is that the IM IN YOU LOOP language?
[04:06] <imbrandon> yea
[04:06] <mocker> hah.
[04:06] <imbrandon> http://paste.ubuntu-nl.org/23243/
[04:06] <mocker> Saw that on somethingawful this morning.
[04:07] <imbrandon> there is a working python intrepeter , not 100%
[04:07] <imbrandon> but works
[04:07] <mocker> people have too much free time. :)
[04:07] <imbrandon> lol
[04:08] <imbrandon> you see my mail about the classes >?
[04:08] <imbrandon> the MOTU classes
[04:09] <dholbach> who of you will be in #ubuntu-classroom at 0:00 UTC later?
[04:09] <StevenK> Probably me.
[04:09] <dholbach> rock
[04:09] <StevenK> Given it's in 14 hours or so
[04:10] <Hobbsee> StevenK: 10
[04:10] <StevenK> Oh right, yes.
[04:10] <mocker> imbrandon: Not yet.
[04:10] <pochu> @now
[04:10] <ubotu> Current time in Etc/UTC: May 30 2007, 14:10:36 - Current meeting: Edubuntu
[04:10] <mocker> imbrandon: Been... busy.
[04:10] <mocker> imbrandon: Looking at buying a house. :)
[04:14] <imbrandon> mocker, sweet
[04:14] <imbrandon> in OP ?
[04:14] <mocker> Guh.
[04:14] <mocker> last.fm bought by CBS
[04:14] <mruiz> dholbach: now works! And I have warnings again: warning, `debian/libapache2-modbt-perl/DEBIAN/control' contains user-defined field `Original-Maintainer'
[04:14] <mocker> imbrandon: Eh, currently looking all over the place.
[04:15] <mruiz> and -> Ubuntu merge policy: when merging Ubuntu packages with Debian, -v must be used
[04:16] <dholbach> mruiz: http://wiki.ubuntu.com/DebianMaintainerField
[04:16] <dholbach> mruiz: ignore the Original-Maintainer warning
[04:16] <mruiz> ok
[04:17] <gnomefreak> -vVersion#  isnt it?
[04:18] <mruiz> dholbach: what's about the Ubuntu merge policy?
[04:18] <ScottK> Yes, but if you are making a debdiff for someone else to upload, it's not necessary.
[04:19] <dholbach> mruiz: man dpkg-buildpackage and read about -v
[04:28] <dabaR> crimsun: OK, now I have a proper pbuilder log file, would you like to see the lines that contain "png"?
[04:29] <dabaR> crimsun: We are trying to make the .install file to move the .png into /usr/share/pixmaps
[04:32] <mruiz> dholbach: what's the next step to test the package locally ?
[04:33] <dholbach> mruiz: it built? were you able to install and test it?
[04:33] <mruiz> yes, built
[04:35] <dholbach> does it install, look good?
[04:35] <mocker> imbrandon: Showed a coworker ubuntustudio.
[04:35] <dholbach> if so, you could get a debdiff from the debian to the merged version and send it to me, I'd review it then
[04:35] <mocker> He's installing now. :)
[04:36] <imbrandon> mocker, sweet
[04:36] <leonel> gooood morning  everyone  !
[04:39] <gnomefreak> are we planning for e17 to be in gutsy?
[04:39] <imbrandon> is e17 ever gonna release ?
[04:39] <gnomefreak> i doubt it
[04:39] <imbrandon> before duke nukem forever
[04:43] <gnomefreak> imbrandon: they say in the distant future
[04:45] <vijay2000> hi all i am trying to package 
[04:45] <vijay2000> brasero 
[04:46] <Hobbsee> vijay2000: why?
[04:46] <vijay2000> i have downloaded the source from https://launchpad.net/ubuntu/+source/brasero/0.5.2-0ubuntu1 and i have run th e command  dpkg-source -x brasero_0.5.2-0ubuntu1.dsc
[04:46] <vijay2000> now where will i get the updated version to which we need to package
[04:47] <vijay2000> i was told that i will get the information in debian/copyright 
[04:47] <Hobbsee> the website listed in debian/copyright
[04:47] <vijay2000> debian/copyright has It was downloaded from http://sourceforge.net/projects/bonfire/
[04:47] <vijay2000> now in site which one i need to download 
[04:48] <vijay2000> 0.5.1 released  or New stable release 0.5.0  or Brasero-0.4.92  
[04:48] <vijay2000> the version i downloaded from LP is 0.5.2
[04:49] <Hobbsee> what makes you think taht there is an updated version?
[04:50] <vijay2000> if we dont have a updated version then y we need to go for a packaging ..i am a newbie so my question might sound silly
[04:50] <Hobbsee> what makes you think taht we "need to go for a packaging"?
[04:50] <gnomefreak> vijay2000: 0.5.2 is in gutsy
[04:50] <Hobbsee> as in, what's telling you that it needs updating?
[04:51] <vijay2000> i was asked by my mentor to try out for packaging of brasero
[04:51] <Hobbsee> right.  who was the mentor?
[04:52] <Hobbsee> and have you asked them why?
[04:52] <vijay2000> daniel is my mentor . i thought we have a updated version 
[04:52] <vijay2000> so i am yet to ask him up 
[04:52] <gnomefreak> cant really learn anything from a package that doesnt fail to build atleast 10 times :(
[04:53] <Hobbsee> dholbach: poke
[04:53] <vijay2000> yes tats true 
[04:53] <Hobbsee> gnomefreak: that used to
[04:54] <vijay2000> i was working on clamtk package 
[04:54] <gnomefreak> vijay2000: is it dholbach or another daniel?
[04:54] <vijay2000> since that was synced by ScottK 
[04:54] <vijay2000> dholbach
[04:54] <gnomefreak> we have 2 that i know of that are mentors atm unless crimsum pulled out already
[04:55] <ScottK> vijay2000: clamtk finally got into Debian, so now that's what we'll work off of.
[04:56] <vijay2000> yes i know it got into debian successfully
[04:56] <vijay2000> that is why i started working on brasero
[04:56] <ScottK> I'll also ask for a backport to Feisty once it's built in Gutsy.
[04:57] <Q-FUNK> is burgundavia gone or currently Burgwork ?
[04:57] <vijay2000> ok
[04:57] <gnomefreak> Q-FUNK: same person
[04:58] <asimon> Greetings, two questions. If a package in REVU got uploaded, how long does it usually take to appear in the distro? And if a revu package got accepted and is part of universe, whats the right way for an update? A bug report with a debdiff? Thanks.
[04:59] <vijay2000> now should i work on brasero or should i wait for a backport of clamtk
[05:02] <ScottK> I've got a Debian BTS/Unstable-Testing migration question....  If a package in Unstable (say python-numpy) doesn't work with the Unstable/Testing version of another package (say python-scipy), but there is a new version of python-scipy sitting in experimental, is it appropriate to file a bug against python-numpy that essentially says needs to migrate to Testing with python-scipy non-broken version and not before?  I'm trying to encourage the new
[05:02] <ScottK> python-scipy out of experimental so I can merge it.
[05:02] <ScottK> vijay2000: What is there to do on brasero?
[05:03] <vijay2000> ScottK: nothing there to work on :)
[05:03] <sacater> imbrandon: now that Im a member, does that change my ability to get a space on that server for irssi and screen
[05:03] <jsgotangco> sacater: congrats btw
[05:04] <ScottK> vijay2000: I think your answer is work on neither clamtk nor brasero as there is nothing to be done for either.
[05:04] <jsgotangco> wasn't able to attend today's CC since it was dawn on my side
[05:04] <vijay2000> ScottK: yes you are right
[05:10] <sacater> jsgotangco: thanks
[05:21] <_MMA_> Hey guys. If you can give ward__ a little compile/package help that would be super.
[05:22] <Ash-Fox> _MMA_, I can help. I am not a MOTU though.
[05:22] <_MMA_> np.
[05:22] <ward__> indeed
[05:23] <ward__> thanx _MMA_ 
[05:23] <ward__> i'm trying to install gephex (www.gephex.org) for several days
[05:23] <_MMA_> Maybe a PM if need be.
[05:23] <ward__> settle it trough PM ?
[05:23] <_MMA_> Crap. ward__ Your not identified.
[05:23] <ward__> (sorry i'm a first timer in this channel)
[05:24] <_MMA_> Oh well.
[05:24] <ward__> _MMA_, i know, but its possible to set it to receive PM's from unidentified anyway
[05:24] <Ash-Fox> Looking quickly at the site, the latest version doesn't have a .deb package and only comes as sourcecode
[05:24] <_MMA_> ward__: Dont worry. We all were. Chat with Ash-Fox. Make a temp channel if need be.
[05:25] <ward__> Ash-Fox, the deb for the 0.4.3 version doesn't work either
[05:25] <ward__> unmet dependencies that are not installable
[05:25] <Ash-Fox> It's better to talk here, no? I mean there are all these MOTUs that can offer help.
[05:25] <ward__> libqtc102-mt
[05:25] <Ash-Fox> ward__, yeah, I would suggest grabbing the latest source package..
[05:26] <ward__> Ash-Fox, i would suggest the 0.4.3 package because the 0.4.4 got compiled but the GUI was not working right at all
[05:26] <Ash-Fox> You will want to install the package 'build-essential' too
[05:26] <ward__> Ash-Fox, is allready installed
[05:27] <Ash-Fox> Okay I'll go with the http://www.gephex.org/download/src/gephex-0.4.3b.tar.bz2 source file then..
[05:27] <ward__> Ash-Fox, i still have the output from make from my last try if u want?
[05:27] <ward__> i've got it pastebinned
[05:27] <ward__> (the last part)
[05:27] <Ash-Fox> I'm going to try compiling it here first.
[05:27] <ward__> Ash-Fox, ok
[05:28] <ward__> Ash-Fox, thanx in advance for looking into it
[05:34] <gnomefreak> is it safe to push epiphany-browser (<< 2.19) to epiphany-browser (<< 2.20) as a depend 
[05:34] <gnomefreak> or << 2.19~
[05:36] <Ash-Fox> Bunch of QT dependencies.. wee
[05:37] <ward__> Ash-Fox, indeed
[05:37] <ward__> 0.4.3 = qt3, 0.4.4 = qt4
[05:37] <ward__> (is qt garbage or did they just not use it right?)
[05:38] <Ash-Fox> A shame they didn't leave us with the deb source package on the site
[05:38] <Ash-Fox> ward__, I love QT, but I have no opinion on QT4 yet.
[05:38] <ward__> its a shame so many people cannot use the software because its so hard to compile
[05:39] <Ash-Fox> Huh... I get the feeling  0.4.3 doesn't like GCC4
[05:40] <ward__> Ash-Fox, never even though of that possibillity
[05:40] <ward__> Ash-Fox, i need to go walk the dog before it rains, i'll be back in 15 minutes ok?
[05:40] <Ash-Fox> Sure
[05:40] <ward__> ok thanx
[05:40] <ward__> brb
[05:41] <ward__> (should my connection fall away, i'll come back)
[05:41] <ward__> damn dynamic ip lol
[05:45] <Ash-Fox> ward__, yep, it doesn't like GCC4 (I'm sure there is some stupid flag for GCC4 to get it to work with older stuff but I don't remember it.). You need to: sudo apt-get install gcc-3.4; export CC=/usr/bin/gcc-3.4; mkdir ~/bin; ln -s /usr/bin/gcc-3.4 ~/bin/gcc
[05:46] <Ash-Fox> Then just run ./configure and make. After doing so you should delete the ~/bin/gcc symlink you made (it was made because the make file ./configure generates isn't correct, even though ./configure applies certain settings for gcc-3.4 set in the $cc variable
[05:47] <Ash-Fox> Anyhow, it should compile and work then.
[05:48] <Ash-Fox> Oh, before ./configure, you will want to check that 'gcc' is pointing to the new gcc symlink you made by checking the version using 'gcc --version', if it's incorrect, just start a new terminal window and it should be correct then.
[05:50] <vijay2000> can anybody tell me how to set a auto reply 
[06:05] <Ash-Fox> Ugh, I must of had some bad sausages, stomach cramps.
[06:18] <Adri2000> ScottK: when removing a package from the list, DaD should remove the appropriate lines from the file comments, but indeed it seems that it didn't work in some cases (which is very strange), we are looking into it
[06:19] <ScottK> OK.  Good luck.
[06:20] <Lutin> true that. looks like it's all about luck indeed
[06:29] <ward__> Ash-Fox, thanx i will try
[06:29] <ward__> Ash-Fox, you got it working that way?
[06:33] <ward__> and then one more thing: how do i delete the symlink again? (its like the second time i ever needed to make a symlink)
[06:37] <kink> ward__, you can remove symlinks with 'rm'
[06:41] <ward__> kink, Ash-Fox my version keeps telling me 4.1.2
[06:41] <ward__> kink, Ash-Fox i uninstall gcc4 and reinstall it afterwards?
[06:42] <kink> ward__, my knowledge is about symlinks
[06:42] <ward__> kink no problem
[06:42] <ward__> kink, can i check if the symlink is there? (i got not error while creating it)
[06:42] <kink> ls -l
[06:43] <Ash-Fox> ln -s /usr/bin/gcc-3.4 ~/bin/gcc
[06:43] <Ash-Fox> then start a new terminal and do 'gcc --version'
[06:43] <ward__> Ash-Fox, same problem
[06:43] <Ash-Fox> you will need to re export cc again
[06:43] <ward__> Ash-Fox, and symlink was allready there too
[06:43] <Ash-Fox> That shouldn't be possible...
[06:44] <ward__> Ash-Fox, re-export cc sounds like chinese to me
[06:44] <Ash-Fox> ~/bin takes priority over /usr/bin ..
[06:44] <Ash-Fox> Did you even install gcc-3.4 ?
[06:44] <ward__> Ash-Fox, gcc-3.4 was allready installed
[06:44] <Ash-Fox> export CC=/usr/bin/gcc-3.4 <- that
[06:44] <ward__> same thing as installing it i thought
[06:45] <ward__> Ash-Fox, i did that too, i didn't forget anything
[06:45] <ward__> shall i try it again from the top?
[06:45] <Ash-Fox> No, if the symlink isn't working, theres no point
[06:45] <ward__> only the export line?
[06:45] <Ash-Fox> If the symlink isn't working, theres no point
[06:46] <ward__> Ash-Fox, maybe i can just remove the symlink and remove gcc4? (untill gephex is compiled)
[06:46] <Ash-Fox> Are you sure starting a new terminal doesn't make it work?
[06:46] <ward__> Ash-Fox, yep, tried several new ones
[06:47] <Ash-Fox> type 'ls -s ~/bin/gcc' for me?
[06:47] <ward__> ok
[06:47] <ward__> 0 /home/ward/bin/gcc
[06:47] <ward__> working
[06:49] <ward__> won't it work if i temporarely uninstall gcc 4 ?
[06:49] <Ash-Fox> No
[06:49] <ward__> damn
[06:49] <ward__> i'll jsut retry from the top once more
[06:49] <Ash-Fox> What does 'ls -l ~/bin/gcc' say?
[06:49] <Ash-Fox> Paste the full line
[06:51] <ward__> ward@ubuntu:~$ ls -l ~/bin/gcc
[06:51] <ward__> lrwxrwxrwx 1 ward ward 16 2007-05-30 18:37 /home/ward/bin/gcc -> /usr/bin/gcc-3.4
[06:53] <Ash-Fox> try 'sudo -i -u ward' then do 'gcc --version'
[06:53] <Ash-Fox> I suspect the terminal sessions aren't truely starting from scratch.
[07:06] <dholbach> hey giskard
[07:12] <ward__> Ash-Fox, you were right
[07:12] <ward__> version is ok now :-)
[07:14] <mruiz> I want to modify a changelog... somebody know what's the meaning of "XSBC"-Original-Maintainer ?
[07:14] <ward__> Ash-Fox, it seems like less warnings but still a lot
[07:16] <Ash-Fox> THere is nothing wrong with warnings
[07:16] <Ash-Fox> Warnings are not errors.
[07:16] <ward__> Ash-Fox, something else, if make ends, can i do sudo checkinstall so i end up with a deb?
[07:16] <ward__> crap
[07:16] <ward__> same error as last time :(
[07:16] <geser> mruiz: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s5.7 , "User-defined fields"
[07:16] <Ash-Fox> I don't know.
[07:17] <ward__> http://paste.ubuntu-nl.org/23291/
[07:17] <ward__> that's the error i get now when doing make
[07:17] <zul> ward__: checkinstall is evil and shouldnt be used
[07:17] <ward__> Ash-Fox, 
[07:17] <ward__> zul, ok then i wont
[07:18] <ward__> i think this is probably the problem now:
[07:18] <ward__> i386/dsputil_mmx.c:662: error: can't find a register in class `GENERAL_REGS' while reloading `asm'
[07:18] <mruiz> thanks geser !
[07:20] <ward__> this is probably a problem with ffmpeg someone else from the mailinglist once had, he solved it by putting the recent ffmpeg source into the gephex source (in contrib/ )
[07:20] <ward__> should i try to do that? or would that be a bad idea?
[07:21] <Ash-Fox> I don't know the code so I can't say
[07:21] <Ash-Fox> But worth a try
[07:22] <ward__> yeah because it seems to happen in ffmpeg
[07:22] <ward__> en that helped me compile gephex 0.4.4 too
[07:22] <ward__> lets try it :-)
[07:22] <Ash-Fox> I'd take the ffmpeg from the .4 package 
[07:33] <ward__> Ash-Fox, you're not gonna believe this...
[07:34] <ward__> Ash-Fox, i fixed last error by replacing ffmpeg by the dvn ffmpeg
[07:34] <ward__> but...
[07:34] <ward__> http://paste.ubuntu-nl.org/23294/
[07:34] <ward__> another error...
[07:35] <ward__> is there some software with those errors? :s
[07:35] <ward__> jesus
[07:37] <ward__> its liek an adventure compiling that program
[07:37] <ward__> adventure in errorland
[07:38] <dholbach> can somebody check out / improve http://wiki.ubuntu.com/MOTU/Recipes/PackageUpdate ?
[07:39] <ward__> Ash-Fox, any idea what this problem might be?
[07:39] <shawarma> dholbach: Any particluar reason you don't mention uupdate?
[07:40] <dholbach> shawarma: it doesn't use debian/watch and I wanted to show what happens 'behind the scene' - I'm happy to have a recipe about uupdate and debian/watch
[07:42] <dholbach> oh... dpkg-source -x missing
[07:43] <shawarma> dholbach: Or just dget -x.
[07:43] <dholbach> AndyP: can you add a     dpkg-source -x brasero_0.5.2-0ubuntu1.dsc    call after step 5)?
[07:43] <dholbach> oh
[07:43] <dholbach> or add dget -x
[07:43] <AndyP> dholbach: sure, no problem
[07:43] <dholbach> thanks shawarma, thanks AndyP
[07:43] <dholbach> you ROCK
[07:44] <shawarma> \o/
[07:44] <dholbach> yooohooo - motu mentoring power :-)
[07:44] <dholbach> it'd be nice to have them on the ubuntu-motu-mentors list
[07:45] <dholbach> and add checking them out as a 'requirement' for people who are looking for a mentor
[07:51] <dholbach> what about  http://wiki.ubuntu.com/MOTU/Recipes/Debdiff ?
[07:55] <ward__> got to go
[07:55] <ward__> Ash-Fox, if u have suggestions, please tell them anyway, i will check the log when i get back
[07:56] <ward__> (that goes for anyone offxcourse)
[07:59] <dholbach> oops, did not commit it....  http://wiki.ubuntu.com/MOTU/Recipes/Debdiff 
[08:07] <vijay2000> hi i am getting the following error when i build the brasero package http://paste.ubuntu-nl.org/23302/
[08:08] <vijay2000> i am using dapper
[08:09] <geser> vijay2000: libgtk2.0-dev from dapper is to old (2.8.17-1ubuntu5 < 2.10.0)
[08:09] <vijay2000> so you mean there is no other way to build it in dapper
[08:10] <geser> you can try to lessen the build-depends but it still may fail
[08:11] <vijay2000> so the only solution to the prob is i need to upgrade to fiesty
[08:11] <geser> yes
[08:12] <vijay2000> geser: thanks :)
[08:12] <geser> edgy would be enough but when you are upgrading you can upgrade to feisty
[08:13] <LaserJock> quick C questions, #ifndef WIN32 indicates the start of a preprocessing section for when WIN32 is set?
[08:13] <LaserJock> or is it when it's not set?
[08:13] <geser> ... for when WIN is not set
[08:13] <geser> ifndef == if not defined
[08:14] <LaserJock> yeah, I just say the n right as it hit Enter :/
[08:14] <LaserJock> *saw
[08:16] <dholbach> congratulations Martinp23: your first upload :)
[08:17] <Martinp23> :) woo!
[08:17] <dholbach> do we have new contributors who want to do uploads to fix libgnome-speech3-dev -> libgnome-speech-dev?
[08:18] <dholbach> we have lsr, gok, gnopernicus and gnome-orca up for grabs
[08:18] <dholbach> http://wiki.ubuntu.com/MOTU/Recipes/Debdiff will help with that
[08:19] <dholbach> don't be shy :)
[08:19] <Kmos> :-)
[08:20] <AndyP> dholbach: may I play on the whole "recipe" idea and use ingredients/method/garnish headings? :)
[08:21] <dholbach> as long as it doesn't confuse people, I'm happy with that :)
[08:21] <Martinp23> dholbach: iirc, the gok I just did is on libgnome-speech-dev
[08:21] <dholbach> Martinp23: absolutely right
[08:22] <superm1> hey guys, any takers for a few moments to do a revu?
[08:24] <AndyP> dholbach: https://wiki.ubuntu.com/MOTU/Recipes/PackageUpdate i think it might need some more work, but how do you like it so far?
[08:25] <dholbach> AndyP: I like it very much
[08:25] <AndyP> :)
[08:27] <LaserJock> dholbach: \o/ for ubuntu-motu-mentors
[08:27] <dholbach> yeehaw :)
[08:28] <AndyP> i need to go read up for my computability theory exam tomorrow but if anyone wants to work on that page any further, go right ahead, i think it's looking quite helpful for new contributors :)
[08:29] <dholbach> I'll inform persia about it (as he wanted to do it initially) and maybe we can announce it on ubuntu-motu-mentors some time tomorrow
[08:29] <dholbach> thanks a lot AndyP
[08:29] <AndyP> you're welcome
[08:37] <dholbach> do we have new contributors who want to do uploads to fix libgnome-speech3-dev -> libgnome-speech-dev? we still have lsr, gnopernicus and gnome-orca up for grabs -- http://wiki.ubuntu.com/MOTU/Recipes/Debdiff will help with that
[08:37] <jussi01> dholbach, what is required?
[08:38] <dholbach> change the build-depends
[08:46] <gnomefreak> dholbach: i havent found a way to satisfy the build deps as they are now in repos it needs epi=2.18 that isnt in repos maybe build it on feisty with right build-deps and than build on gutsy?
[08:48] <dholbach> gnomefreak: we can't upload to feisty
[08:48] <dholbach> so it should work and build on gutsy
[08:48] <gnomefreak> not upload but build
[08:48] <gnomefreak> epiphany-browser-dev (>= 2.18), epiphany-browser-dev (<< 2.19),
[08:48] <gnomefreak> that is causing issues
[08:49] <gnomefreak> i can change it to << 2.20~ but still cant satisfy them
[08:50] <dholbach> yes, we need to build on gutsy
[08:50] <gnomefreak> im thinking make changes build on feisty take source build on gutsy (that way i satisy the depends since i changed them for gutsy on feisty
[08:50] <gnomefreak> ^^ long way around
[08:52] <gnomefreak> ill let you know if i find another way around. i need to take break atm
[08:52] <dholbach> you can build it in a gutsy chroot or a gutsy pbuilder
[08:52] <dholbach> that way you don't need to update to gutsy
[08:53] <gnomefreak> i have gutsy chroot the problem is it depends on packages in feisty not in gutsy
[08:54] <gnomefreak> unless i install epi. 2.18 from feisty in gutsy but i think thats a major change
[08:57] <dholbach> yes, you need to bump debian/control too
[08:59] <RainCT> keescook: hi. how did you said I can continue the dpkg-buildpackage if only the debian folder changed?
[09:00] <keescook> RainCT: try and see if "fakeroot debian/rules binary" works for you.  running that multiple times should let to make changes to the debian/ tree without needing to recompile the second time.
[09:03] <ScottK> keescook: Would you take feisty/edgy-security updates for Bug #108907?
[09:03] <ubotu> Launchpad bug 108907 in aircrack-ng "Merge with 0.7-3 from debian unstable (#SA24880)" [Undecided,Confirmed]  https://launchpad.net/bugs/108907
[09:04] <keescook> ScottK: certainly, if someone can prepare (and test) some debdiffs, I'd be happy to upload them
[09:05] <ScottK> keescook: OK.  I'll take a look at it and see what i can do.
[09:07] <DarkSun88> Hi all
[09:14] <keescook> hiya DarkSun88
[09:25] <ScottK> keescook: It looks like Bug #108907 and Bug #116615 refer to the same issue.  Which one do you want to use as the master bug?
[09:25] <ubotu> Launchpad bug 108907 in aircrack-ng "Merge with 0.7-3 from debian unstable (#SA24880)" [Undecided,Confirmed]  https://launchpad.net/bugs/108907
[09:25] <ubotu> Launchpad bug 116615 in aircrack-ng "aircrack-ng -- buffer overflow" [Medium,Confirmed]  https://launchpad.net/bugs/116615
[09:26] <keescook> ScottK: hmm.. let's use 108907 as the master.
[09:26] <ScottK> keescook: OK.  Would you please confirm the task against Feisty.
[09:27] <keescook> ScottK: yup, one sec
[09:27] <keescook> ScottK: oh, I can't approve nominations at the moment.  launchpad changed things a bit, but I'll get those powers back soon
[09:28] <ScottK> keescook: OK.  Now that I'm MOTU, I had thought I'd have been able to do that.  Maybe it's not just me then...
[09:28] <keescook> ScottK: once LP gets fixed, you will
[09:29] <geser> use https://bugs.launchpad.net/ubuntu/feisty/+source/aircrack-ng/+bug/108907 and click on "needs fixing here" as a workaround
[09:29] <ubotu> Launchpad bug 108907 in aircrack-ng "Merge with 0.7-3 from debian unstable (#SA24880)" [Undecided,Confirmed]  
[09:31] <ScottK> geser: Thanks.  That worked.
[09:46] <evand> Can someone take a look at 117834 and let me know if I'm on the right track.
[09:54] <lionel> hi evand
[09:54] <evand> hello lionel 
[09:54] <mathiaz> hi. I'd like to package an init script that is started from the rcS.d directory. Should I set the Default-Start tag in the init script ?
[09:54] <lionel> you're on the right track, but few things to change
[09:54] <ScottK> keescook: It looks to me like the 0.6.2 code (what we have in Feisty) is fundamentally different than what is in 0.7 and later (the known vulnerable version).  The only spot in the source that was checking packet size that I found in that file for 0.6.2 seemed to me to look for packets to large.  Based on my inspection of the source, I think that Edgy/Feisty are not vulnerable.  I am not in a position to actually try the exploint though (only
[09:54] <ScottK> one wireless card right now).
[09:54] <evand> ok
[09:55] <lionel> first, you should attach debdiff, not paste it in the body
[09:55] <lionel> it easier for others to download to test and to upload :)
[09:55] <keescook> ScottK: ah, interesting.  one of the reporters claimed it was.  I can check into it.
[09:55] <evand> lionel: ah, I was using the script pitti wrote, will fix in the future.
[09:55] <pochu> evand: If just left a comment in the report. You should always notice every diff with Debian in the changelog :)
[09:56] <pochu> s/If/I/
[09:56] <ScottK> keescook: I think he misunderstood as he reported a fix in 0.7, but it's actually a 0.7 vulnerability that was fixed in 0.9.
[09:56] <keescook> aaah
[09:56] <evand> I also put [Evan Dandrea]  in there by mistake which I see now
[09:56] <lionel> as pochu said
[09:56] <lionel> (you add a build-dep that is not in the changelog
[09:57] <crimsun> mathiaz: # Default-Start:     S
[09:57] <ScottK> keescook: Please have a look as I'm operating on the ragged edge of my expertise here.
[09:57] <lionel> it seems that there were former releases of the package
[09:57] <lionel> (in Ubuntu)
[09:57] <lionel> and changelog entries are missing
[09:57] <keescook> ScottK: yup, reading now
[09:57] <lionel> evand: do you use MoM or DaD for the merge ?
[09:57] <mathiaz> crimsun: and then update-rc call in postinst will deal with everything ?
[09:58] <evand> indeed, that came from the Debian change
[09:58] <evand> I think I used the script from MoM
[09:58] <evand> I stand corrected
[09:58] <evand> from DaD
[09:58] <ScottK> keescook: Now I'm looking at the second bug report that has an Etch debdiff.  Maybe it'll change my mind...
[09:58] <pochu> evand: you have also removed the previous Ubuntu changes ;)
[09:58] <evand> yikes
[09:58] <pochu> e.g. the nice icon :)
[09:58] <lionel> evand: between which version did you debdiff ?
[09:59] <pochu> bug #76996
[09:59] <ubotu> Launchpad bug 76996 in amule "better icon for amule" [Wishlist,Fix released]  https://launchpad.net/bugs/76996
[09:59] <keescook> ScottK: the debian debdiff seems to imply there is still a partial fix for 0.6.2
[09:59] <pochu> lionel: I'd say debian 2.1.3-3 and Ubuntu 2.1.3-2ubuntu1
[09:59] <ScottK> keescook: Agreed.
[09:59] <mathiaz> crimsun: how can I specify the number which should be used ?
[09:59] <evand> 2.1.3-2ubuntu1 and the newly created 2.3.3-3ubuntu1
[09:59] <crimsun> mathiaz: you'll still need to pass the appropriate parameters to update-rc.d.  See its man page.
[10:00] <evand> err 2.1.3
[10:00] <crimsun> mathiaz: (examples there)
[10:00] <ScottK> keescook: I'd been looking at the information in the other bug...
[10:00] <pochu> evand: -3ubuntu1? Do you mean -3?
[10:00] <lionel> evand: it should be between last Debian package and Ubuntu merged
[10:00] <evand> ahh, ok
[10:00] <mathiaz> crimsun: ok. I'll have a look. Thank you.
[10:00] <keescook> yeah, it wasn't clear, and it seems that the vuln code is actually in 0.6.2 by way of a patch, so the patch itself needs update.  confusing!
[10:00] <pochu> lionel: btw, good luck with your MOTU membership request :)
[10:01] <lionel> pochu: thanks :)
[10:01] <lionel> pochu: it's on its way
[10:01] <ScottK> keescook: Ah.  That makes more sense.  Very odd.
[10:02] <crimsun> pochu: it already has the requisite acks, just awaiting last notification
[10:03] <tsmithe> hi - any DDs about?
[10:03] <tsmithe> i've got a package i'd like to get mentored into debian
[10:04] <tsmithe> it's wired, and it's on mentors.debian.net
[10:04] <pochu> crimsun: have you already submitted it to the TB?
[10:04] <crimsun> pochu: we're awaiting Andrew's input
[10:05] <crimsun> tsmithe: haven't /whois'd, but are you in the mentors channel? :)
[10:06] <Kmos> bug 114229
[10:06] <ubotu> Launchpad bug 114229 in k3b "Please update to k3b 1.0.1" [Undecided,Unconfirmed]  https://launchpad.net/bugs/114229
[10:06] <Kmos> anyone wants to do this ?
[10:06] <tsmithe> crimsun, oh no. is that on oftc, or here?
[10:07] <Seveas> there is no #ubuntu-mentors or #ubuntu-motu-mentors
[10:07] <tsmithe> not ubuntu :)
[10:07] <tsmithe> debian :)
[10:07] <Seveas> ah ;)
[10:07] <tsmithe> ;)
[10:08] <pleia2> tsmithe: oftc
[10:08] <tsmithe> thank :)
[10:08] <tsmithe> *s
[10:18] <evand> So when writing the changelog for a merge, you should always list the Ubuntu changes that were kept after the merge?
[10:18] <geser> yes
[10:18] <evand> ok, thanks for clairfying
[10:19] <ward_> Ash-Fox, did u find the time to look at the end of the make i pastebinned?
[10:22] <ward_> (i didnt find logs of this channel) :s
[10:24] <lionel> ward_: as for all Ubuntu channels: http://people.ubuntu.com/~fabbione/irclogs/
[10:25] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[10:26] <ward_> lionel, thanx :-)
[10:27] <ward_> damn no reply lol, i think Ash-Fox is afk or busy
[10:27] <ward_> can anyone else take a look?
[10:29] <ward_> http://paste.ubuntu-nl.org/23294/
[10:29] <ward_> that's what make says
[10:29] <ward_> when compiling gephex
[10:30] <ward_> i allready had to use gcc3.4 instead of 4 (with Ash-Fox his advice) to solve a few problems
[10:30] <ward_> then i needed to replace the ffmpeg wich is delivered with gephex with the recent svn version
[10:30] <ward_> that also solved the error
[10:30] <ward_> and then i got this
[10:31] <ward_> and i hav eno clue how to solve this
[10:31] <ward_> www.gephex.org is the webpage of the prog i'm trying to compile
[10:31] <ward_> (i will offcourse post a howto at some wiki if i get it to work, that goes without saying
[10:31] <ward_> )
[10:32] <ward_> been trying to compile it for days, never been so close
[10:39] <mathiaz> I have a question related to init scripts : the current package uses update-rc defaults to install init scripts. I'd like to install the init script in rcS instead. I know how to do that. But can I handle package upgrades ?
[10:39] <mathiaz> (ie removing all links during the package upgrade)
[10:39] <mathiaz> (ie removing old links during the package upgrade)
[10:40] <xxxxx1> bye all!
[10:41] <ward_> lol bitchx @ nintendo64
[10:48] <ScottK> keescook: It looks to me like the vulnerable patch for aircrack-ng is not present in the Edgy version, so I think it's clear.  LP is apparently offline just now, so I can't report that.  I also attached a debdiff for Feisty.
[10:51] <keescook> ScottK: great!  thanks.
[10:52] <Lure> can somebody explain this: http://merges.ubuntu.com/universe.html - digikam-doc is claimed to have 0.9.2~beta2-1 in debian, but it does not show on packages.d.o
[10:57] <pochu> Adri2000, Lutin ^
[10:57] <Lure> interesting... grab-merge.sh got it from somewhere... ;-)
[10:57] <pochu> Lure: it isn't in http://packages.debian.org/unstable/doc/digikam-doc either.
[10:59] <gnomefreak> is it bad to merge a package and fix everything but 2 issues (a bit over my head but daniel asked me to do it so i did. anyway is it bad to send the package as is with my patch and stuff but the 2 things still borked to revu and let him fix rest (or someone else?)
[11:00] <Lutin> pochu: Lure's pointing to MoM as far as I can see :)
[11:00] <pochu> Lutin: lol, you're right :-)
[11:01] <Lure> poningru: URL of DaD?
[11:01] <superm1> pochu, could you do a revu?
[11:01] <Lutin> pochu: seems it does
[11:01] <pochu> Lutin: YaY! it's also in DaD ;)
[11:01] <Lutin> Lure: http://dad.dunnewind.net
[11:01] <pochu> superm1: I'm not a MOTU, but I might find something interesting.
[11:02] <superm1> Oh thought you were :)
[11:02] <superm1> sure if you'd like to look anyhow, couldnt hurt: http://revu.tauware.de/details.py?upid=5325
[11:02] <pochu> I'll be... some day ;)
[11:04] <gnomefreak> ok let me change that. how do i stop autoregen of control file during clean
[11:04] <gnomefreak> ^^^ evil and has pissed me off for 3 or more hours now
[11:05] <crimsun> gnomefreak: it's good to update the source package continually, yes.
[11:05] <crimsun> apologies for not following up; I've been traveling today and won't have time until later tonight to review.
[11:05] <crimsun> what do you mean by regen?
[11:05] <crimsun> is debian/control being regenerated from debian/control.in?  If so, that's acceptable.
[11:05] <gnomefreak> its ok i took this on and should have known better (what started off as a simple merge + patch + changing a couple things in control 
[11:06] <crimsun> or is cdbs being used to regen it?
[11:06] <gnomefreak> its not acceptable in this case becase it reverts the debian/control to a bad place
[11:06] <Lutin> superm1: the source package name is libhdhomerun, however it doesn"t seem to provide any lib* binary package? why is that ?
[11:06] <gnomefreak> that i dont knwo let me look in rules real fast
[11:06] <superm1> Lutin,  thats what upstream calls it
[11:07] <Lutin> superm1: ok..weird
[11:07] <gnomefreak> can i guess and say cdbs
[11:07] <superm1> Lutin, I believe its because they build for multiple OS's from that same package
[11:07] <superm1> so they thought libhdhomerun made sense?
[11:07] <gnomefreak> crimsun: the clean part of rules is tiny and doesnt say either way. however there are 4 lines for cdbs in rules up top
[11:08] <Lutin> superm1: don't know 
[11:08] <crimsun> gnomefreak: you'll need to at least grep debian/control*'s ^Build-Depends for cdbs and check debian/rules, too, for the env var
[11:09] <pochu> superm1: I'd say you don't need to install the lgpl.txt file, since you're linking to it in debian/copyright, but I'm not sure though.
[11:09] <superm1> thats the same thing ScottK said yesterday, but you need to ship a copy of the LGPL with the package
[11:09] <superm1> as determined with the last package i worked on
[11:10] <Lutin> superm1: and iirc the README file is automagically added by debhelper.mk
[11:10] <gnomefreak> crimsun: ill wait till morning when im fresh and thinking better. thank you. have fun on your travels :)
[11:10] <superm1> Lutin, ah. 
[11:11] <Lutin> superm1: in this case, the package actually contains a copy of the license, so that's fine for the orig. concerning the package, as long as the copyright file points to a common license theres no point keeping it
[11:11] <Lutin> I mean, installing it a 2nd time
[11:12] <superm1> Ok Lutin.  Just had heard differently with mythbuntu-artwork-usplash.  crimsun had said to still install COPYING (which was a copy of the GPL)
[11:12] <Lutin> and btw, all the files chmod 755 in the orig..how can one do that ? :/ (it's not your fault, anyways)
[11:13] <superm1> silly Silicon Dust :)
[11:13] <ScottK> pochu: think of it as installing the COPYING file (which is normally done automatically)
[11:13] <Lutin> superm1: are you sure COPYING was no more than a full copy of the license ?
[11:13] <ScottK> keescook: LP is back up so I marked Edgy rejected for aircrack-ng
[11:14] <superm1> Lutin,  yes, thats exactly what it was
[11:14] <keescook> ScottK: great, thanks.  I've got feisty building now; it's a pretty minimal change, so I'm happy to get it published.  thanks for hunting down all the bits.  :)
[11:14] <pochu> ScottK: then it shouldn't be installed, unless it has some special clauses, right?
[11:14] <Lutin> ScottK: do you think it's worth installing it if it's nothing but a full copy ?
[11:14] <Lutin> seems quite pointless to me
[11:15] <ScottK> Lutin: I guess I put it in the can't hurt category.  Normally you install COPYING even if it's just a copy of the GPL, so I'd say yes.
[11:16] <ward_> can anyone take a look at this make output? http://paste.ubuntu-nl.org/23294/
[11:16] <Lutin> ScottK: humm well maybe. in a lot of cases though it 'just happens' through debhelper.mk
[11:16] <pochu> At least I didn't do it with my first Debian package, and it got accepted :)
[11:17] <ScottK> Yes.  Normally just happens.
[11:17] <superm1> Lutin, here is the last package that I did: http://revu.tauware.de/details.py?upid=5244.  It was the last thing keeping it from getting uploaded (Adding a COPYING file which was a copy of the GPL)
[11:18] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[11:18] <joejaxx> is there anyway to see what packages have the most bugs?
[11:18] <joejaxx> on lp
[11:19] <Lutin> superm1: oh, I see
[11:19] <pochu> joejaxx: probably OOo :)
[11:19] <joejaxx> pochu: :P
[11:20] <joejaxx> pochu: why do you say that?
[11:21] <pochu> joejaxx: because it has a lot ;)
[11:21] <joejaxx> lol
[11:21] <Lutin> heya persia 
[11:21] <pochu> joejaxx: but ubiquity has more...
[11:22] <joejaxx> 468 for OO.o
[11:22] <persia> Hi lutin
[11:26] <mocker> rrdtool is making my head hurt. :(
[11:27] <pochu> joejaxx: btw, why do you want to know it? :)
[11:27] <pochu> you can file a bug in lp about it ;)
[11:27] <DarkSun88> G'night.
[11:27] <joejaxx> well
[11:27] <joejaxx> i have found different ways to find bugs i can patch and upload
[11:27] <joejaxx> without other people taking them :P
[11:28] <joejaxx> while i am working on them
[11:28] <joejaxx> it is hard to explain
[11:31] <superm1> Lutin, will you be able to leave some comments advocating/not advocating on revu for that package? (Your motu right?)
[11:31] <joejaxx> but i want to run this method on the packages that have the most bugs
[11:31] <Lutin> superm1: sure
[11:31] <superm1> thx Lutin 
[11:31] <Lutin> np
[11:35] <ScottK> superm1: I just gave you a +1
[11:35] <superm1> Thanks ScottK :)
[11:37] <Lutin> ScottK: are you ok with the package name ? I'm still wondering if uploading a non-lib as libfoo source hurts or not 
[11:38] <ScottK> Lutin: That would fall under I'm new and what do I know.  It's a bit unexpected.  superm1 why did you give it a lib name if it's not a lib?
[11:39] <superm1> ScottK, because the upstream package was namd that
[11:39] <superm1> I just followed what the upstream source was titled
[11:41] <Lutin> imho, removing lib from the source name would be a good thing, though you'd have to deal with 'renaming the tarball' thing on each new release :)
[11:43] <ScottK> Lutin: It's just the source package name.  The binary package name doesn't say lib, so I don't think any actual end users will be confused.
[11:43] <superm1> well i guess the big question would be if there are any ramifications by having a source package name like that
[11:43] <superm1> could any other motu's comment?
[11:44] <Lutin> ScottK: would remain confusing on the developer side though. as superm1 said, having another opinion would be cool :)
[11:45] <fargiolas> Lamego: ping?
[11:48] <ward_> could anyone please look into my compilation problem?
[11:48] <ward_> http://paste.ubuntu-nl.org/23294/
[11:48] <ward_> make problem would maybe more accurate
[11:48] <ward_> be more accurate
[11:52] <fargiolas> Lamego: just sent you an email
[11:54] <persia> ward_: The new gcc is stricter about code syntax.  It looks to me like structscannnner.h shouldn't specify that some of the internal members are within the private namespace - this is already known.  On the other hand, addressing this requires looking at the code.  Try patching the header to not use the extra qualification.
[11:55] <ward_> persia, how do i patch the header not to use the eextra qualification?
[11:55] <ward_> (sorry is that sounds retarded :p )
[11:55] <ward_> if
[11:56] <Lamego> fargiolas, pong
[11:56] <Lamego> about :P ?
[11:56] <persia> ward_: You can find a good guide on patching systems from https://wiki.ubuntu.com/MOTU/School/PatchingSources
[11:56] <fargiolas> gnome-mastermind new release
[11:56] <fargiolas> you packaged the last version, remember?
[11:56] <ward_> persia, am i gonna be able to do that with not much programming skills?
[11:57] <Lamego> fargiolas, sure, will package it tomorrow, today I just have time to finish the current package :(
[11:57] <fargiolas> Lamego: don't worry there's no hurry :)
[11:58] <fargiolas> i've just released it, it can wait for this night :P
[11:58] <persia> ward_: That's hard to answer.  It depends on whether your "not much" is enough.  I suggest giving it a try - at first glance it looks like you just need to remove the utils::structscanner:: from before the member declarations.  If you're still confused, then you might want to pass.
[11:58] <Lamego> ok :)
[11:58] <Lamego> but I do like 0 day releases ;)
[11:59] <ajmitch> morning
[11:59] <ward_> persia, not confused, but surely not confident
[11:59] <ward_> lol
[11:59] <ward_> persia, i'll see if i understand the docs and go from there
[11:59] <persia> ward_: Try it.  If it tests clean, you've made a good patch :)
[12:00] <fargiolas> :)
[12:01] <ward_> persia, i'm still using gcc 3.4 because it is needed to compile gephex, that's not gonna be a problem right? just to make sure
[12:02] <persia> ward_: If you're using gcc 3.4, my earlier comments might not be right.  I recommend just retrying with the current latest gcc before trying a patch.
[12:03] <ward_> persia, i'm using gcc3.4 because gephex didnt work with gcc4, Ash-Fox recommended using 3.4 and that solved that part
[12:03] <ward_> (he helped me here earlyer but he seems to be afk)
[12:04] <ward_> persia, try with gcc4 anyway?
[12:05] <persia> ward_: When a package doesn't work for gcc4, it's good to retry that package with gcc3, but this should only be done for single packages, and only if absolutely required.  It's best to try with gcc4 for each new package first.
[12:05] <ward_> persia, that's what i did, tried first with gcc4 and it didnt work
[12:05] <ward_> persia, does the info on the webpage not count with gcc3.4 ?
[12:06] <persia> ward_: Which webpage?
[12:06] <ward_> https://wiki.ubuntu.com/MOTU/School/PatchingSources
[12:06] <ward_> persia, 
[12:07] <persia> ward_: That information counts for all packages.  It's just that using gcc4 might well solve the problem without a patch.  Where possible, all packages should use gcc4, with gcc3.4 only used when absolutely necessary.
[12:08] <ward_> persia, ok, well it certanly was necessary, it solved the first problems
[12:08] <ward_> persia, and Ash-Fox looked for himself on his own PC so he's probably right
[12:09] <persia> ward_: OK.  If you need to use gcc3.4, you'll still want to try the patch.  My apologies for confusion.
[12:09] <ward_> persia, there's no confusion :-)
[12:09] <ward_> but basically patching = editing the source code and then make a patch of what u edited right?
[12:12] <ward_> then i'll first look at the source code because the chance is extremely small i understand it, else i wasted my time on patch knowledge i don't need :-)