[12:15] <phanatic> any MOTUs around who could possibly review and upload a package? (not a new one, just ubuntu revision bumped)
[12:16] <sladen> phanatic: paste the URL!
[12:16] <crimsun> URL?
[12:16] <Toadstool> :)
[12:17] <phanatic> sladen, crimsun: http://revu.tauware.de/details.py?upid=2585
[12:20] <sladen> phanatic: sysinfo is a fairly generic name, is there anything of that description already in the debian or ubuntu archives
[12:21] <sladen> phanatic: the package looks good otherwise
[12:21] <phanatic> sladen: it's already in ubuntu (dapper)
[12:21] <sladen> phanatic: ah okay.  +1 from me
[12:21] <phanatic> sladen: thanks
[12:21] <crimsun> phanatic: have you test-built?
[12:22] <phanatic> crimsun: yeah, with pbuilder too (edgy chroot). the fixes are confirmed to work...
[12:22] <crimsun> uploaded.
[12:24] <phanatic> crimsun: thanks
[12:24] <crimsun> np
[12:56] <zul> hey
[01:21] <zul> gah..
[01:27] <FunnyLookinHat> agreed.
[01:27] <FunnyLookinHat> : P
[01:51] <bddebian> Heya gang
[01:53] <crimsun> hey, go back to your vacation :-)
[01:54] <bddebian> Hmm, I see crimsun missed me :'-(
[01:55] <Fujitsu> What is the appropriate course of action if a package fails to work when compiled with GCC 4.1 unless -O0 is used? vpnc's latest upload doesn't work for that reason.
[01:56] <Kyral> use -O0?
[01:56] <crimsun> then we build it with -O0 until the bug is fixed.
[01:57] <Fujitsu> OK, I'll make it use -O0, and get it reuploaded.
[02:32] <bddebian> Heya Hobbsee
[02:35] <crimsun> Hobbsee & Toadstool are our newest MOTU
[02:35] <bddebian> w00t
[02:35] <bddebian> Congrats Hobbsee, sorry I missed the meeting, I was out of town :-(
[02:36] <Fujitsu> Hobbsee, congrats!
[02:39] <carthik> congrats Hobbsee (I thought you were already one)
[02:39] <carthik> I'm just waiting for crimsun's MOTU school lecture - immediately after which I'll be there with you ;)
[02:44] <Hobbsee> hi bddebian crimsun Fujitsu carthik
[02:44] <Hobbsee> carthik: hehe!  nope :)
[02:45] <Hobbsee> bddebian: fair enough, i had enough people to cheer.  and i said that whoever didnt approve me would be the next one bugged for uploads
[02:45] <Hobbsee> :P
[02:45] <Hobbsee> thanks all :)
[02:45] <Hobbsee> crimsun: yeah.  only had 3 rejected so far :P
[02:49] <Fujitsu> Out of how many, Hobbsee?
[02:50] <Hobbsee> Fujitsu: dunno, check edgy-changes mailing lsit
[02:51] <whiprush_> congrats Hobbsee and ToadZzZztool!
[02:53] <Hobbsee> whiprush_: thanks :D
[02:53] <Fujitsu> 33, looks like :)
[02:54] <Hobbsee> Fujitsu: that high?   nice
[02:55] <Fujitsu> I've just got 11 so far... And one of them is b0rked due to silly GCC 4.1
[02:57] <Laser_away> woah, MOTUs actually upload things? ;-)
[02:58] <Hobbsee> Laser_away: heh.  more when they arent MOTU's :P
[02:58] <crimsun> only ones who matter ;-)
[02:58] <Hobbsee> Fujitsu: ah yes
[02:58] <Hobbsee> crimsun: hehe!
[02:58] <Laser_away> Hobbsee: that's right. You work hard to get MOTU and then you slack for the next 2 years ;-)
[02:59] <bddebian> LaserJock!! :-)
[02:59] <Hobbsee> LaserJock: hehe :)
[02:59] <Hobbsee> LaserJock: not if i want core...
[03:00] <LaserJock> bah, who wants core when you can have so much fun in Universe ;-)
[03:00] <bddebian> Yeah, exactly :-)
[03:00] <crimsun> sadly, there are a fair number of MOTU who have become inactive (in terms of uploading and maintenance) most probably due to time constraints
[03:00] <bddebian> crimsun: Have you not gotten to ivtools yet?
[03:00] <LaserJock> yes, sadly
[03:01] <crimsun> bddebian: I've not fixed it yet; I'm waiting for you to do that since I did it for you last time ;-)
[03:01] <LaserJock> I'd upload more but I seem to be stuck working on other things and getting other people ready to upload :-)
[03:02] <bddebian> crimsun: Oh, heh
[03:02] <crimsun> yay, drama in pkg-*-devel
[03:03] <LaserJock> crimsun: yeah?
[03:03] <bddebian> ?
[03:03] <crimsun> LaserJock: hardly, you last uploaded at Sat Jul 8 03:35:09 BST 2006
[03:03] <crimsun> or rather that's when katie accepted
[03:03] <crimsun> s/katie/newSoyuzWorldOrder/g
[03:04] <LaserJock> I've sponsored at least 1 since then too
[03:04] <LaserJock> still
[03:04] <LaserJock> not very much
[03:04] <LaserJock> it'd be nice if I could just package
[03:04] <crimsun> "with great privilege..."
[03:05] <bddebian> Huh?
[03:05] <crimsun> [comes great responsibility] 
[03:05] <LaserJock> unfortunatley my boss got back from his 1 week vacation today
[03:06] <LaserJock> so tomorrow I'm supposed to show him all the research I did while he was gone
[03:06] <crimsun> my co-PIs called from their vacations :-(
[03:06] <crimsun> ended up having a conference call at 7 AM. Grr.
[03:06] <LaserJock> ouch, that stinks
[03:07] <crimsun> thankfully I had been awake chasing bugs anyhow
[03:07] <Hobbsee> LaserJock: me. because some of my packages got bumped to main.  and it whinges when i try to upload to main.
[03:07] <Hobbsee> crimsun: great responsibility is fun though
[03:08] <LaserJock> fun?
[03:08] <crimsun> true, is it.
[03:08] <crimsun> it is ^
[03:08] <crimsun> I think I'm distracted by the attractive young lady sitting near me in the coffee shop
[03:08] <crimsun> (d'oh)
[03:08] <LaserJock> hehe
[03:08] <Hobbsee> what's the debian equivalent of launchpad builds?  or of edgy changes?
[03:09] <LaserJock> I keep trying but I just can't get away
[03:09] <crimsun> http://packages.qa.debian.org/srcpackage
[03:09] <jsgotangco> hmm k3b hates rhythmbox
[03:09] <LaserJock> Hobbsee:
[03:09] <Hobbsee> thanks
[03:10] <LaserJock> Hobbsee: http://buildd.debian.org/
[03:11] <bddebian> crimsun: :-)
[03:12] <LaserJock> jsgotangco: hehe, why should they like each other? rythmbox says, "You're so elitest with all that configurablity" and k3b fires back "oh yeah, well my widget set can beat up your widget set any day"
[03:14] <micahcowan> mostly OOC... if I'm preparing packages for software that I wrote myself, do I bother to tack on the -0ubuntu1 bit? Prolly not, huh?
[03:14] <Hobbsee> debian 376586
[03:14] <Ubugtu> Debian bug 376586 in dar "Subject: dar: Library not found after upgrade to 2.3.0-3" [Grave,Closed]  http://bugs.debian.org/376586
[03:15] <LaserJock> micahcowan: you are packaging *for* yourself or you are the upstream author of the software?
[03:15] <micahcowan> LaserJock: upstream author.
[03:16] <Fujitsu> I'm getting a rather odd error when trying to pbuild my new vpnc:
[03:16] <Fujitsu> su: Authentication service cannot retrieve authentication info.
[03:16] <crimsun> micahcowan: do you intend to get it into Debian before getting it into Ubuntu?
[03:16] <crimsun> (hopefully the answer is "yes")
[03:16] <LaserJock> micahcowan: you should probably add -0ubuntu1 (assuming it isn't already in Debian) and not create a native package (i.e. keep the debian/ out of the source tarball)
[03:16] <micahcowan> crimsun: I... probably intend to stick it on REVU?
[03:17] <micahcowan> Ubuntu first, I think.
[03:17] <LaserJock> crimsun: don't you know, we don't contribute back upstream? ;-)
[03:17] <bddebian> heh
[03:17] <crimsun> micahcowan: understood. But it will be far easier maintenance-wise to get it into Debian first and then just sync into Ubuntu.
[03:17] <crimsun> LaserJock: ..."upstream"?
[03:17] <crimsun> what's this mythical pony?
[03:17] <LaserJock> Debian
[03:18] <tseng> I got jdub to put the pony on fridge
[03:18] <tseng> before it went live
[03:18] <tseng> and its still there.
[03:18] <micahcowan> Why not in the source tarball? Same reasons as given before for having all changes be in debian?
[03:18] <LaserJock> crimsun: dude, http://blog.madism.org/index.php/2006/07/19/95-sorry-but
[03:18] <micahcowan> LaserJock: "Debian" what?
[03:18] <tseng> the image originalyl appeared to the oss blogosphere in Haddess' blog
[03:18] <LaserJock> micahcowan: because seperating packaging from source is generally a good idea
[03:19] <ajmitch> LaserJock: yes, we're all bad & evil
[03:19] <LaserJock> micahcowan: what happens if you have a bug in the packaging? you have to release a new version
[03:19] <bddebian> ajmitch!!
[03:19] <LaserJock> micahcowan: when you could just change the .diff.gz and bumb the revision
[03:19] <ajmitch> bddebian: yes?
[03:19] <LaserJock> ajmitch: you're alive!
[03:19] <ajmitch> LaserJock: no I'm not
[03:19] <bddebian> ajmitch: Just Hi
[03:20] <ajmitch> hello bddebian
[03:20] <micahcowan> I wouldn't necessarily have to rerelease for the main package... but yeah, I see what you're saying.
[03:21] <micahcowan> LaserJock: why would it be easier to try to get it into debian first?
[03:22] <LaserJock> because if you put it in Debian then we can sync it into Ubuntu
[03:22] <LaserJock> I've done it both ways
[03:22] <LaserJock> I like the feedback from REVU
[03:22] <LaserJock> but if you want it to go into Debian you are better off sending it off the them after REVU is happy
[03:22] <micahcowan> Which do you prefer?
[03:23] <micahcowan> I guess it was crimsun who recommended debian first, not LaserJock...
[03:24] <LaserJock> I think (although I'm not sure if others would agree) I would put it on REVU and when people are happy with it there send it to debian-mentors to get sponsored in Debian
[03:25] <LaserJock> I like getting feedback from the people here, but it's kinda pointless to upload a -0ubuntu1 to Universe when a short time later you are going to need to sync -1
[03:26] <LaserJock> if however, we are getting close to the freeze and we won't have time to sync it I'd go for it in Ubuntu first
[03:26] <micahcowan> I'm not terribly familiar with REVU at all... there is a process by which, after the packaging job has been critiqued, you can choose to try to get it into debian, or ubuntu?
[03:27] <LaserJock> well, basically you could get it to the point were it could be uploaded to Universe and then rather than do that, take it to debian
[03:28] <LaserJock> you'd have to tell the advocators on REVU that you don't want it uploaded I guess
[03:28] <micahcowan> Okay, cool.
[03:28] <LaserJock> Hobbsee: fully?
[03:28] <crimsun> micahcowan: ok, post-REVU comments, if you go the Debian route, you can follow the New Maintainer's Guide for its processes, so you'd approach debian-mentors. If you went the Ubuntu route, a MOTU would just upload it to Ubuntu.
[03:29] <LaserJock> if you don't know anything about the Debian process it can be a bit tough, but it only took me 2 days to get my package uploaded to Debian after I had it OK'd on  REVU
[03:30] <micahcowan> How long after that was it sync'd to Ubuntu?
[03:31] <LaserJock> a long time because I was lazy (an -0ubuntu1 package was uploaded already)
[03:32] <micahcowan> Mmm so... the packager also has some responsibility for the sync? I thought they were automagic.
[03:32] <LaserJock> if it is during the time that automagic sycs are going on
[03:33] <LaserJock> if not then you'd have to poke the archive admins
[03:34] <LaserJock> anyway, if you have the package fairly ready to go and you seriously want to maintain it in Debian (which as the author I'd think you would be) then I'd go straight for Debian
[03:35] <Hobbsee> LaserJock: yeah.  how long does it take for p.d.o to update?
[03:35] <LaserJock> not sure
[03:35] <Fujitsu> Anybody got an ideas on my pbuilder problem?
[03:35] <LaserJock> are you wanting for something that just got into Debian?
[03:35] <crimsun> it's a daily cron job aiui
[03:36] <Hobbsee> LaserJock: does it need to update for me to request a sync on a package?  it's on the ftp
[03:36] <Hobbsee> LaserJock: yeah.  a bugfix.
[03:36] <crimsun> Hobbsee: no
[03:36] <Hobbsee> crimsun: excellent :)
[03:36] <ajmitch> Hobbsee: p.d.o is irrelevant for syncs
[03:36] <LaserJock> Hobbsee: if it's on the mirrors it's good to go for sure
[03:38] <LaserJock> ok, I seriously gotta get home, my wife will be upset
[03:38] <LaserJock> I'm late for dinner
[03:38] <crimsun> 'later
[03:39] <bddebian> Later Laser_away
[03:40] <bddebian> Are there any devscripts for checking a package against the new python policy?
[03:43] <ajmitch> bddebian: probably not much - at least cdbs complained about my packages not being compliant though
[03:43] <bddebian> Damn, well fix hamlib for me will ya? :-)
[03:43] <ajmitch> no
[03:44] <Hobbsee> ajmitch: cool :)
[03:44] <Hobbsee> bddebian: heh.  get fixing :P
[03:45] <bddebian> Hobbsee: Aye, I need it for gpredict too
[03:45] <Hobbsee> :P
[03:45] <bddebian> But I was told to leave it alone until it's fixed in Debian :-(
[03:46] <Hobbsee> ah
[03:46] <Hobbsee> okay then
[03:47] <bddebian> But I was hoping to nudge the Debian maintainer if I could supply a patch ;-)
[03:47] <ajmitch> bddebian: so do so
[03:47] <bddebian> I don't know the python policy at all yet :-(
[03:47] <ajmitch> time to read up on it
[03:47] <Hobbsee> ajmitch: fixed all of zope yet?
[03:48] <ajmitch> nope
[03:48] <bddebian> ajmitch: Where is it?
[03:48] <ajmitch> http://www.debian.org/doc/packaging-manuals/python-policy/
[03:48] <ajmitch> http://wiki.debian.org/DebianPythonFAQ
[03:49] <bddebian> Thank you honey
[03:51] <bddebian> Hmm, well maybe it's unfixable with a broken python2.3 anyway
[03:51] <ajmitch> shouldn't be
[03:52] <bddebian> Well if multiple versions are OK, then it can't be built
[03:55] <bddebian> ajmitch: hamlib-python2.3-dev, hamlib-python2.4-dev, etc
[03:57] <bddebian> It probably isn't
[04:01] <bddebian> Ack, why the hell is grass looking for libGLw?
[04:06] <bddebian> I don't understand how you can have a provides and conflicts and replaces in the same package?
[04:07] <Hobbsee> bddebian: because a package now includes package2, it conflicts it, so you cant install both at once, and it replaces it, so you need package 1 instead of package2.  it happens with kdelibs-bin and kdelibs4c2a
[04:08] <Hawkwind> Hobbsee: Say all of that 3 times super fast :P
[04:08] <Hobbsee> Hawkwind: hah.
[04:08] <bddebian> Hobbsee: I have the conflicts/replaces part but how can a package provide a package it conflicts or replaces?
[04:09] <Hobbsee> bddebian: well, package A replaces package B, if package A effectively contains package B
[04:09] <Hobbsee> and it just means that you cant have both package A and package B installed at the same time.
[04:10] <bddebian> Hmm, OK
[04:10] <ajmitch> bddebian: it's to avoid breaking dependencies for all the thousands of other packages
[04:13] <bddebian> So package: python2.3-libhamlib2 should become python-libhamlib2 and provide python2.3-libhamlib2 and conflict and replace: python2.3-libhamlib2 ?
[04:14] <ajmitch> Hobbsee: thanks for that
[04:14] <Hobbsee> ajmitch: :P not a problem.
[04:14] <Hobbsee> the machine that i was building on died :(
[04:14] <Hobbsee> fortunately, it finished the build first.
[04:15] <bddebian> anyone? ^^
[04:15] <Hobbsee> bddebian: sounds reasonable, but i try to avoid python stuff like the plague
[04:15] <bddebian> :-)
[04:15] <Hobbsee> bddebian: is that what they did in debian?
[04:26] <jsgotangco> my network died in edgy lol
[04:34] <bddebian> Hobbsee: That's seems to be what the python policy suggests afaict
[04:34] <Hobbsee> bddebian: oh good :)
[04:43] <bddebian> Ack, what do I do about a .dirs file?
[04:54] <sharms> howdy
[04:55] <bddebian> Heya sharms
[05:00] <sharms> for your build systems, does anyone here just put pbuilder update in a cronjob?
[05:01] <Hobbsee> sharms: i usually run it before i start building for the day...
[05:01] <Hobbsee> sharms: might be sensible for edgy though, with so many updates
[05:01] <sharms> yeah I was just thinking maybe everday at like 4am have it update automagically
[05:02] <Hobbsee> might be clever.  if it bails partway thru you can fix it again.
[05:03] <sharms> I finally took the dive today and installed XGL, the f12 and workspace functions are great
[05:12] <FunnyLookinHat> So what kind of information should I put on my wiki?  Anyone have any examples (or their own wiki page that I could see)?
[05:13] <Hobbsee> FunnyLookinHat: what for?
[05:14] <FunnyLookinHat> well I need to get my wiki page setup for becoming an ubuntero (or whatever that goofy name is!)  ;)
[05:16] <crimsun> FunnyLookinHat: that means you sign the latest revision of the Code of Conduct (CoC)
[05:17] <FunnyLookinHat> but I thought the CC would approve me and this and that, and that having my wiki updated with what I am doing with ubuntu was useful?
[05:17] <crimsun> a "ubuntero" is simply an LP user who has signed the Ubuntu CoC
[05:17] <FunnyLookinHat> hmm... then how about a ubuntu member?
[05:18] <FunnyLookinHat> I'm just looking at https://wiki.ubuntu.com/MOTU/Hopeful/Recruitment
[05:18] <crimsun> to become a "Ubuntu member", you should have a wiki page listing your continuing involvement in Ubuntu
[05:18] <FunnyLookinHat> Riiiiightt. That's what I meant then  : )
[05:18] <FunnyLookinHat> So just give a description of what I am doing w/ ubuntu etc. etc.?
[05:19] <crimsun> feel free to take a look at any of the wiki pages of users who are in the https://launchpad.net/people/ubuntumembers LP team
[05:19] <sharms> FunnyLookinHat: http://wiki.ubuntu.com/StevenHarms
[05:25] <FunnyLookinHat> Sweet thanks sharms    : )
[05:26] <FunnyLookinHat> Hmm... how do I sign the COC?  I have a gpg...
[05:26] <sharms> FunnyLookinHat: apt-get install seahorse
[05:26] <sharms> I did it all though that GUI
[05:26] <crimsun> click "Codes of Conduct"
[05:26] <FunnyLookinHat> Ahh it's in seahorse
[05:26] <FunnyLookinHat> ok, yea I use that  : )
[05:26] <sharms> well you download the coc to a text file
[05:27] <sharms> then right click it -> encrypt
[05:27] <sharms> then paste the encrypted version into the launchpad text box
[06:41] <FunnyLookinHat> Welcome back all!
[06:41] <nixternal> heh
[06:41] <FunnyLookinHat> nixternal, know how to force a newline in wiki code by any chance?
[06:42] <nixternal> enter twice
[06:42] <nixternal> ;)
[06:42] <nixternal> there isn't a <br /> or anything like that...at least that i know of
[06:42] <nixternal> however, if you are trying to force a break in a table...good luck
[06:43] <FunnyLookinHat> Ahhhh
[06:43] <FunnyLookinHat> Sweet thanks!
[06:46] <crimsun> man. that sucked.
[06:48] <FunnyLookinHat> Seveas is having a worse time than most of us I see....
[06:52] <crimsun> that's because he is at or has surpassed the per-client channel limit
[06:53] <lifeless> nah
[06:53] <lifeless> or is that what the channel hes joining sees ?
[06:54] <crimsun> afaik he's in a number of high-volume channels, but I could be completely off the mark.
[08:08] <sander> Hello. What is the official way to request a sync from the debian repositories for a package?
[08:20] <crimsun> sander: which package?
[08:21] <sander> gnome-hearts
[08:21] <sander> It was added to de debian repro's on July 5
[08:25] <crimsun> didn't you /just/ ask about this a day or two ago?
[08:26] <sander> 4 days ago IIRC. You guys told me to wait a few days because the build server were overloaded
[08:26] <crimsun> please wait til Knot-1 is released, then we'll take care of requesting new syncs.
[08:26] <crimsun> (ETA: sometime late today)
[08:27] <sander> Okay. And can I request that here? Or should I fill out a form/edit the wiki somewhere?
[08:28] <crimsun> normally you'd file a bug against the source package (gnome-hearts) requesting it to be synced from Debian Sid
[08:28] <sander> I can't, since it's a new package. Shall I file it against Ubuntu then?
[08:29] <crimsun> you can, sure.
[08:30] <sander> Thanks for your help :-)
[09:30] <dholbach> good morning
[09:30] <crimsun> hi Daniel
[09:31] <dholbach> hey Daniel
[09:35] <raphink> hey Daniels
[09:37] <crimsun> hi Mister Pinson
[09:39] <raphink> :)
[10:06] <bjp> hi guys, I'm trying to fix some comments that 'daemon@poleboy.de' provided on the Flamerobin package (http://revu.tauware.de/details.py?upid=2747) yesterday. I'm working on the Standards-Version and moved it to 3.7.2 instead of 3.6.2, although now linda warns that 3.7.2 is a newer standards version. Should the Standards-Version still be 3.7.2?
[10:08] <dholbach> bjp: yes
[10:09] <dholbach> bjp: dpkg -l debian-policy   gives you the version of the policy atm
[10:11] <bjp> dholbach: I'm probably doing something wrong, but when I run that command, it does not output any versions, but it gives: Desired=Unknown/Install/Remove/Purge/Hold and some more lines..
[10:11] <dholbach> then you don't have it installed, sorry
[10:12] <dholbach> apt-cache show debian-policy | grep ^Version
[10:13] <bjp> ah there the version is 3.6.2.2
[10:13] <bjp> although there is no newer version avaible right now.. ?
[10:17] <dholbach> that's in edgy
[10:17] <bjp> dholbach: probably it is because I'm running dapper, and the newer version is in edgy only?
[10:17] <dholbach> yeah
[10:17] <bjp> dholbach: right :)
[10:18] <dholbach> but as you're going to upload your package to edgy (once it's approved and all), ... :)
[10:18] <bjp> dholbach: well I can upgrade my system to edgy
[10:18] <dholbach> edgy is not a stable system, you have to be comfortable with that truth :-)
[10:18] <bjp> dholbach: I see, and linda will be runned after dputting the package?
[10:19] <dholbach> on the revu host, yes
[10:19] <bjp> dholbach: well I don't have to use an extremely stable system, but I should be able to bool every day :)
[10:20] <dholbach> hehe, it boots, yes :)
[10:20] <bjp> dholbach: but as long as it is not a problem building it on dapper I'll stick to that for now I think
[10:20] <dholbach> ok
[10:20] <dholbach> that's cool
[10:21] <bjp> dholbach: I'll experiment with Edgy later on :) (btw, how do I upgrade to that? Is it only by changing dapper to edgy in sources.list?)
[10:21] <dholbach> yes and then do a dist-upgrade
[10:22] <dholbach> there was a lot of flux in the archive, so lots of python packages changed their name, etc
[10:22] <dholbach> you have to have a close look on what gets replaced :)
[10:22] <bjp> I see :)
[10:23] <bjp> so the bottom line is that I'll ignore that one warning on my system for now :)
[10:26] <bjp> within the comments of the review, there is also mentioned that config.{sub|guess} should be copied before configure call and being removed in clean, which will skip them from the diff.gz file. Can you explain that a little bit more to me, please?
[10:39] <Gloubiboulga> hello world
[10:40] <Toadstool> 'morning
[10:44] <bjp> hello gloubiboulga
[10:44] <Arbiter> hey Gloubiboulga
[10:44] <Arbiter> :)
[10:44] <Gloubiboulga> hi bjp, Arbiter
[10:46] <Arbiter> Gloubiboulga, wanna advocate my package (again)? :D
[10:47] <Gloubiboulga> yep, could you give me the REVU url for it?
[10:47] <Arbiter> http://revu.tauware.de/details.py?upid=2742
[10:49] <Gloubiboulga> I really need to learn my gpg key ID
[10:50] <bjp> Arbiter, Gloubiboulga, maybe one of you can help me a bit further..
[10:50] <Arbiter> sure
[10:51] <Arbiter> but I think that Gloubiboulga is more expert than me ;)
[10:51] <bjp> yesterday 'daemon@poleboy.de' commented on my Flamerobin package (available at: http://revu.tauware.de/details.py?upid=2747). For some of those comments I need a bit more explaination I think
[10:51] <bjp> well you both are more than I am :)
[10:51] <Arbiter> bjp, hehe
[10:51] <bjp> for the debian/rules file: you should copy config.{sub|guess} before the configure call and remove them in the clean call, then they are not in the .diff.gz
[10:52] <bjp> how can I achieve this? The config.sub and config.guess are coming from subversion and are in the original source package
[10:52] <Arbiter> wait a sec.
[10:52] <Gloubiboulga> yep, your debian/rules use different config.{sub|guess} and replace the ones in the sources
[10:53] <Gloubiboulga> which creates an ugly diff.gz
[10:53] <Arbiter> bjp, you can remove these lines
[10:53] <Arbiter> +ifneq "$(wildcard /usr/share/misc/config.sub)" ""
[10:53] <Arbiter> +	cp -f /usr/share/misc/config.sub config.sub
[10:53] <Arbiter> +endif
[10:53] <Arbiter> +ifneq "$(wildcard /usr/share/misc/config.guess)" ""
[10:53] <Arbiter> +	cp -f /usr/share/misc/config.guess config.guess
[10:53] <Arbiter> +endif
[10:54] <Gloubiboulga> or you can backup them and copy them back during the clean call :)
[10:55] <bjp> well it seemed a bit odd to me that the clean call copies files to the directory and overwrites the current ones.
[10:56] <bjp> but if I remove the lines that Arbiter pasted, aren't the original files from the source package not used then?
[10:57] <Gloubiboulga> actually the lines that Arbiter pasted should be in the configure part
[10:57] <Gloubiboulga> with the backup
[10:57] <Arbiter> yep
[10:58] <bjp> okay so I have to backup the config.{sub|guess} files first (rename them by concatenating with .old I think) and then copy them from /usr/share/misc/config.*
[11:01] <bjp> am I right with that?
[11:02] <Gloubiboulga> yes
[11:03] <siretart> bjp: read /usr/share/doc/autotools-dev/README.Debian for a rationale about config.{sub,guess}
[11:03] <Gloubiboulga> and mv foo.old foo during the clean call
[11:05] <bjp> Gloubiboulga> right, thanks :)
[11:05] <bjp> Gloubiboulga> maybe you know how I should fix the last issue from the comments as well: files in /usr/share/flamerobin/doc should be installed to /usr/share/doc/flamerobin (or linked, in case flamerobin needs these files there)
[11:07] <bjp> the make install of Flamerobin installs the documents in flamerobin/doc. I can symlink them, I should do that in the install part of debian/rules I think?
[11:07] <Gloubiboulga> bjp, yes, you just ahve to move the files :)
[11:08] <Gloubiboulga> you should move the files to usr/share/doc/flamerobin, and create the links in /usr/share/flamerobin if needed
[11:09] <bjp> Gloubiboulga> okay so I have to change the makefiles of flamerobin if I'm right. Or do we have to fix it in flamerobin source package and then build the ubuntu package based on that?
[11:11] <Gloubiboulga> no need to patch the makefile
[11:12] <Gloubiboulga> you can use mv or dh_install to move the files
[11:12] <Gloubiboulga> bjp, http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3
[11:12] <bjp> okay great! :)
[11:13] <Gloubiboulga> dh_install is cleaner though
[12:51] <Arbiter> oh that weird
[12:52] <Arbiter> the author of colorscheme updated it's application and changed it's name
[12:52] <Arbiter> it's called agave now
[12:52] <Arbiter> pff...
[02:18] <zul> hi
[02:40] <Hobbsee> hi all
[02:47] <Yagisan> G'day Hobbsee
[02:47] <Hobbsee> hey Yagisan :)
[03:51] <xyzzy_bill> Well, here's a dumb newbie question:  What do I do if I want to contribute packages? (More on next line)
[03:52] <xyzzy_bill> Looks like contributing to Debian is the way to go... I'm not enjoying the Debian install... Can I develop on Ubuntu and upload the resulting packages?
[03:53] <Hobbsee> xyzzy_bill: yes
[03:53] <bjp> xyzzy_bill> of course you can
[03:54] <xyzzy_bill> Great!  So, I'll just get involved in Debian without actually every running it! :-D
[03:54] <xyzzy_bill> Thanks.
[04:00] <bjp> xyzzy_bill> well, packages aren't merged back to Debian if that's what you mean.
[04:00] <Enverex> Does anyone here want to have a look at my e-uae or ccd2iso uploads, I'm tempted to do more but I need to know if I've screwed anything up with those first so I don't do it again...
[04:05] <Enverex> Can you believe it, until thismorning I was running the basic 386 kernel on my Athlon64 X2 machine. Damn I feel stupid.
[04:05] <Enverex> Running 32bit was deliberate, but I didn't realise there was a K7-SMP kernel!
[04:08] <tritium> Enverex: notice a difference??
[04:09] <Enverex> Yeah, unsupprisingly, lol, considering I just over doubled my processing power
[04:10] <tritium> :)  I'll be getting an X2 soon, as soon as prices drop due to Conroe.
[04:12] <bddebian> Heya gang
[04:12] <tritium> hey bddebian
[04:13] <zul> x2?
[04:13] <Enverex> HAHA, I just noticed someones translated the Gnome applets wrong as they now have the carriage return icons in the tooltips
[04:13] <tseng> ok script kids
[04:14] <tseng> i need a quick one liner to find and remove files older than $DATE
[04:14] <tseng> any takers?
[04:14] <bddebian> Hi tritium
[04:15] <zul> tseng: find . -type f -ctime XXX -exec rm -f {} \; or something like that
[04:17] <tseng> hm
[04:17] <tseng> -ctime n seems to be days by the manpage?
[04:17] <Mithrandir> tseng: touch -d $date tmp ; find -older tmp -print0 | xargs -0 rm
[04:18] <tseng> $ find -older tmp -print0
[04:18] <tseng> find: invalid predicate `-older'
[04:19] <tseng> man only has newer
[04:19] <Mithrandir> hmm, find ! -newer -print0 |[...] , then?
[04:19] <tseng> seems to work
[04:19] <tseng> verifying
[04:21] <tseng> Mithrandir: thanks!
[04:21] <Mithrandir> at least I find the -newer syntax a lot less confusing than -ctime, etc
[04:21] <tseng> yeah I was struggling a bit with ctime
[04:21] <tseng> -ctime in the manpage was pretty useless, possibly other bits elsewhere
[04:22] <Mithrandir> you can also do -mtime +5 to find anything six days or older.
[04:24] <tortoise__> Hello, anyone here who gets a kick out of packaging python apps?  Only I need to get someone to look at the one I made.
[04:28] <tortoise__> The package works but I get some deprecation errors when building it.  Get it at https://wiki.ubuntu.com/Accessibility/Projects/SOK/dev?action=AttachFile&do=get&target=sok-packages2.tar.gz
[04:44] <Enverex> Does anyone here want to have a look at my e-uae or ccd2iso uploads, I'm tempted to do more but I need to know if I've screwed anything up with those first so I don't do it again...
[04:45] <Enverex> (would kinda be wasting lots of time making things that are broken, heh)
[04:51] <tseng> are there any ubuntu forums users here?
[04:51] <Hobbsee> tseng: very occasionally, why?
[04:51] <tseng> I need someone to reply to a thread for me
[04:52] <tseng> I have explained once already on IRC
[04:52] <tseng> and they continue on with spreading false information
[04:52] <Enverex> What do you put for "Type of package: single binary, multiple binary, library, kernel module or cdbs? [s/m/l/k/b] " if it's an app and a plugin for things?
[04:52] <Enverex> (i.e. binary and library)
[04:52] <tseng> I refuse to sign up for the forum, however.
[04:53] <Hobbsee> tseng: if you want to pastebin what you want me to say, and where, i'll put it in
[04:53] <tseng> Enverex: normally single.
[04:53] <tseng> Enverex: if you want to package the plugin seperately, m (multiple)
[04:53] <Enverex> thanks
[04:53] <FunnyLookinHat> tseng, please post a link to the forum post.
[04:53] <tseng> m is alot more complex
[04:57] <Enverex> Erm, where is the page where people request what packages they want people to port?
[04:57] <FunnyLookinHat> Enverex, a bug report on launchpad would be the proper place most likely
[04:57] <Enverex> FunnyLookinHat, There is a Wiki page about it where it says who's on what etc
[04:58] <Enverex> Ah, found it
[04:58] <Enverex> https://wiki.ubuntu.com/MOTU/Packages/Candidates
[05:02] <tseng> Hobbsee: http://pastebin.ca/93513
[05:02] <tseng> Hobbsee: thanks alot.
[05:04] <Hobbsee> tseng: :)
[05:05] <tseng> I have a feeling that wont work
[05:08] <Enverex> hmm, got an issue with one of my builds...
[05:08] <Enverex> mkdir -p "/usr/share/uade2/players"
[05:08] <Enverex> mkdir: cannot create directory `/usr/share/uade2': Permission denied
[05:08] <Enverex> (that's inside pbuilder)
[05:09] <tseng> yeah wrong DISTDIR
[05:09] <Enverex> How do I go about correcting that then?
[05:10] <tseng> do you already call $(MAKE) DISTDIR=$(CURDIR)....
[05:10] <tseng> ?
[05:10] <tseng> if not, it might be a problem with the usptream makefile
[05:10] <Enverex> I'm using the default deb/rules file
[05:11] <Enverex>  $(MAKE) install prefix=$(CURDIR)/debian/uade/usr
[05:12] <Enverex> /usr/share/uade2 is where it installs some config files afaik
[05:13] <tseng> DESTDIR sorry
[05:13] <Enverex> hmm, so the one I just posted (from the default rules file) won't work?
[05:13] <tseng> it should if upstream was sane
[05:14] <tseng> whats happening is they are installing stuff in /usr/ on your real system
[05:14] <tseng> not in debian/uade/user
[05:14] <tseng> -e
[05:14] <Enverex> Isn't it just like programs installing things to /etc though? (which I thought was done regardless of prefix)
[05:19] <fowlduck> hallo
[05:20] <Enverex> lo
[05:20] <Enverex> tseng, Any ideas to get around this then
[05:20] <Enverex> ?
[05:22] <tseng> no, without looking at it I am blaming the upstream makefile
[05:22] <Enverex> Time to edit the makefile then
[05:23] <h3sp4wn> Can cdbs deal with running autoconf / automake before configure - or how can I run autogen.sh from inside pbuilder ? (or should I just avoid cdbs - its only a simple program)
[05:24] <tseng> you could make cdbs do it by overloading the rule
[05:24] <tseng> not recommended.
[05:24] <dholbach> cdbs can run automake and autoconf beforehand
[05:25] <h3sp4wn> dholbach: Any example of a package which does that (or is still not recommended ?)
[05:25] <tseng> it is alot easier to add things to rules you can actually see
[05:26] <dholbach> DEB_AUTO_UPDATE_AUTOCONF and DEB_AUTO_UPDATE_AUTOMAKE
[05:26] <h3sp4wn> thanks
[05:26] <dholbach> i need to think about an example
[05:26] <dholbach> and i'm in a meeting atm
[05:26] <h3sp4wn> no problems
[05:27] <edscho> i'd like to do some development work on two Debian unstable/experimental packages with my Dapper system.  Could someone tell me how to configure sources.list and preferences.list to pull in just these two packages from Debian unstable and experimental without hosing my system?
[05:28] <tseng> edscho: for 2 packages it would be easier to go to packages.debian.org and going to the package page in the right dist
[05:28] <tseng> and download the source files
[05:28] <tseng> .dsc, diff.gz, .orig.tar.gz
[05:28] <tseng> dpkg-source -x foo.dsc
[05:29] <edscho> tseng: thanks. So just download them and use dpkg -i package?
[05:29] <tseng> erm. no do as I said.
[05:29] <edscho> thanks.
[05:29] <tseng> you need all 3 files for each
[05:30] <edscho> ok, got you
[05:30] <tseng> cool.
[05:31] <Enverex> tseng, any idea which makefile or file would be the one to normally specify things like this?
[05:31] <tseng> no, I don't have your sources
[05:33] <Enverex> grrr
[05:35] <Enverex> How do I search inside files for a string?
[05:36] <Mithrandir> grep foo file1 file2
[05:38] <Enverex> This makes no sense, in the makefile it has this
[05:38] <Enverex> DATADIR = {PACKAGEPREFIX}{DATADIR}
[05:38] <Enverex> then
[05:38] <Enverex> test -e "$(DATADIR)/uade.conf" || cp -f uade.conf "$(DATADIR)/"
[05:38] <LaserJock> Enverex: use grep
[05:38] <Enverex> So I don't see what's wrong...
[05:38] <Enverex> LaserJock, I did, heh
[05:40] <tseng> and what is PACKAGEPREFIX set to
[05:41] <Enverex> erm, nothing in Makefile.in... but it's in configure as...
[05:41] <Enverex> configure:    -e "s|{PACKAGEPREFIX}|$packageprefix|g" \
[05:48] <Enverex> I noticed this tseng ...
[05:49] <Enverex> if test "$user" = "no"; then
[05:49] <Enverex>     # global installation
[05:49] <Enverex>     if test -z "$prefix"; then
[05:49] <Enverex>         prefix="/usr/local"
[05:49] <Enverex>     fi
[05:49] <tseng> the dir should exist before configure
[05:51] <Enverex> eh?
[05:58] <Enverex> tseng, That's the only thing I can see that has anything to do with it, so unless that's wrong I don't know =/
[06:52] <bddebian> Heya LaserJock
[06:52] <LaserJock> hi bddebian
[07:22] <Tonio_> hello
[07:31] <Gloubiboulga> hi Tonio_
[08:00] <Arbiter> hi
[08:07] <sharms> Arbiter: howdy
[08:31] <crimsun> dholbach: are you still planning to do a class on merging/syncing?
[08:31] <dholbach> me? :)
[08:31] <dholbach> not sure, if i'm the best teacher for that :)
[08:31] <dholbach> i'll run a session on updating packages :)
[08:32] <crimsun> err, sorry, your name is attributed to merges on https://wiki.ubuntu.com/MOTU/School/Requests
[08:32] <LaserJock> crimsun: you want to do it?
[08:32] <LaserJock> crimsun: that means he is requesting it ;-)
[08:32] <LaserJock> not teaching it ;-)
[08:32] <dholbach> crimsun: i requested the sessions
[08:33] <dholbach> crimsun: since they were on the spec, i wanted to make sure they are in the wiki table
[08:33] <crimsun> ok
[08:33] <crimsun> I can do that one this weekend.
[08:33] <crimsun> or if that should block on pitti's, I can wait til patches are covered.
[08:34] <LaserJock> it sort of would be nice to have an overview of patches
[08:34] <LaserJock> because merge work is mostly looking at/managing patches
[08:34] <dholbach> i don't think it'd block
[08:34] <dholbach> it'd just be nice, if we could announce them big on u-motu and u-devel :)
[08:34] <crimsun> I don't think it would, either, though patch knowledge is certainly highly useful.
[08:35] <LaserJock> do you think this weekend would be enough notice?
[08:35] <LaserJock> I'd like to do u-motu u-devel the fourms and anything else we can think of
[08:36] <crimsun> since it would be two days away, probably not enough notice
[08:37] <crimsun> the evening (localtime, GMT -0400) of the 28th might be better
[08:38] <dholbach> nice
[08:38] <LaserJock> pitti's is on the 25th so that would only be 3 days in between
[08:38] <LaserJock> would that matter do you think?
[08:38] <LaserJock> "hit 'em hard, hit 'em fast" ;-)
[08:38] <dholbach> ok fellas - i'm off
[08:38] <dholbach> have a nice evening
[08:38] <crimsun> bye Daniel
[08:39] <dholbach> bye Daniel
[08:39] <crimsun> LaserJock: I don't think so, but I'm not in the best position to say.
[08:39] <fowlduck> are the motu school sessions logged?  I can't make this coming tuesday but I REALLY need to learn that
[08:40] <crimsun> yes, they are logged
[08:40] <LaserJock> fowlduck: yes, they will be logged and put on the wiki
[08:40] <fowlduck> fantastic
[08:40] <fowlduck> wow, i feel so excited, haven't felt like this in a while
[08:40] <fowlduck> like a kid on Christmas
[08:40] <fowlduck> i feel like a nerd
[08:40] <crimsun> what I'd /really/ like to use, which is blocked on infrastructure, is some sort of Internet whiteboard
[08:41] <LaserJock> crimsun: ok, how is 23:00 UTC on the 28th?
[08:41] <fowlduck> crimsun: ooh, I found a good one of those recently.
[08:41] <crimsun> we have a system here that's freely available that uses audio and video, but I think it may be Windows-only
[08:41] <fowlduck> hmm, vmware?
[08:42] <crimsun> it's heaps better that that reservation-based Internet2 teleconferencing class stuff, though
[08:42] <crimsun> LaserJock: sounds fine to me.
[08:42] <LaserJock> k
[08:43] <crimsun> I'll talk w/ our IT guys and see if something can be wrangled
[08:51] <LaserJock> ok, MOTU/School MOTU/School/Requests and MOTU/Calendar adjusted ;-)
[08:53] <bddebian> LaserJock: Awesome, what are you going to teach me? :-)
[08:54] <LaserJock> me?
[08:54] <LaserJock> I know nothing
[08:56] <bddebian> Bah
[08:57] <LaserJock> bddebian: I was thinking more the reverse, what are you going to teach me?
[08:58] <LaserJock> maybe we need a "How to slack like a MOTU" class ;-)
[08:58] <LaserJock> of course nobody would show up to teach it :-)
[08:59] <ogra> sure, but everybody would just lurk ...
[08:59] <LaserJock> heh
[08:59] <ogra> a practise session :)
[09:01] <zul> LaserJock: i can teach that one
[09:01] <sharms> I can commit to not showing up for it if that helps
[09:03] <LaserJock> zul: no you get, "MOTU Masochism" ;-)
[09:04] <zul> heh..
[09:04] <zul> why is everybody saying that these days
[09:05] <bddebian> LaserJock: Hehe
[09:09] <LaserJock> I think I'll be stuck with, "How to turn Ubuntu into a full-time volunteer job and totally neglect real life" :-)
[09:09] <Gloubiboulga> I can help you for this session LaserJock
[09:10] <ogra> even though i'm beyond the volunteering :)
[09:10] <LaserJock> yeah
[09:11] <Gloubiboulga> thunar
[09:11] <Gloubiboulga> hm, no, not here
[09:12] <LaserJock> I think ogra gets the "How to run a derivative while moving" session
[09:12] <LaserJock> he will come in and out
[09:13] <LaserJock> trying to shave every KB of the .iso
[09:13] <LaserJock> but in the end we will have a beautiful product
[09:13] <LaserJock> ;-)
[09:13] <h3sp4wn> Could anyone teach about using dpkg-cross ? Does anyone ever use it ?
[09:14] <LaserJock> hmm, I don't know if we do any cross compiling
[09:14] <LaserJock> I've never used it anyway
[09:16] <fowlduck> ugh
[09:16] <fowlduck> anyone know how to launch a gnome-terminal, have it execute a command, then stay open?
[09:16] <zul> screen
[09:39] <jrib> Universe Freeze on 9/28 is the last day that new packages from revu can be accepted into the edgy release right?
[09:39] <LaserJock> right
[09:47] <ogra> well, make that 9/27 rather ... you never know which TZ counts :P
[09:50] <zul> right im off...later
[10:01] <Tonio_> hum, stupid question but that's it...
[10:01] <Tonio_> can we restart upload packages now knot1 is out?
[10:02] <lucas> universe was never affected by knot1 freeze
[10:02] <Tonio_> lucas: thanks (I didn't follow the activity for 2 weeks)
[10:02] <Tonio_> that's the reason I'm a bit lost
[10:03] <lucas> :-)