[01:58] <sistpoty> hey bddebian: I'll upload an ftbfs fixed version of gmult any minute. Please don't ask, why it does work with my patch, that was an epiphany and I have no real clue about the build system :(
[01:58] <sistpoty> bddebian: hence I'd very much like to not file a but in unstable about that... but in case it works for you as well... ;)
[02:09] <LaserJock> sistpoty: what are you doing up so late?
[02:10] <sistpoty> hey LaserJock
[02:10] <sistpoty> LaserJock: I'm waiting for my spouse to return home
[02:11] <LaserJock> sistpoty: what TZ are you in? Seems awfully late/early for Europe
[02:11] <sistpoty> LaserJock: utc+2 and, yes, it's quite late for me
[02:12] <LaserJock> I'm tired and I'm -4 :-)
[02:12] <sistpoty> hehe
[02:12] <bddebian> Bunch a sissies! :)
[02:13] <bddebian> sistpoty: Did you already post/upload gmult?
[02:13] <LaserJock> bddebian: did I hear that you made DD?
[02:13] <sistpoty> bddebian: uploaded: yes, but it's still in the queue
[02:13] <bddebian> LaserJock: Yeah, a while ago.  Amazing eh? :)
[02:13] <LaserJock> I can't believe it
[02:14] <bddebian> Hey! :'-(
[02:14] <LaserJock> ;-)
[02:14] <sistpoty> LaserJock: you missed the bits about ftp-master, I guess
[02:14] <bddebian> Heh
[02:14] <bddebian> Well just ftp assistant
[02:14] <LaserJock> ohhhhh!
[02:14] <LaserJock> I think I did see that in my mail box
[02:14] <LaserJock> and to think, we never thought he'd amount to anythin :p
[02:14] <bddebian> I'm totally absent from Ubuntu these days though
[02:15] <bddebian> LaserJock: Amen brother! :)
[02:15] <sistpoty> well, I always new to cheat revu by reviewing only stuff that went through bddebian before :P
[02:15] <LaserJock> heh
[02:15] <bddebian> bah
[02:17] <LaserJock> I'm sadly absent from Ubuntu these days as well
[02:17] <LaserJock> I can't believe somebody actually gave me a real job
[02:17] <LaserJock> I was starting to think I was going to  be a grad student forever
[02:17] <bddebian> heh
[02:17] <LaserJock> I had been there longer than all of the secretaries
[02:17] <bddebian> You can have my "real" job! :)
[02:18] <LaserJock> I'd been through 3 department chairs
[02:18] <bddebian> dang
[02:18] <LaserJock> and I'd seen 6 new faculty hired
[02:18] <LaserJock> 2 of which I was on the hiring committee
[02:19] <bddebian> sistpoty: Is it a small patch?
[02:19] <LaserJock> you know you've been there too long when professors you helped hire are getting tenure :-)
[02:19] <bddebian> hehe
[02:20] <LaserJock> I like my new job, but I'm not sure about Boston/New England yet
[02:21] <LaserJock> weather's been nice, but the traffic sucks
[02:21] <sistpoty> bddebian: yep
[02:21] <bddebian> Yeah Boston is about the worst traffic I've ever seen and I lived in California for 12 years :)
[02:22] <sistpoty> bddebian: http://paste.ubuntu.com/278359/
[02:22] <bddebian> wtf?
[02:23]  * sistpoty hides under http://launchpadlibrarian.net/31703518/buildlog_ubuntu-karmic-amd64.gmult_7.2-1_FAILEDTOBUILD.txt.gz
[02:26] <bddebian> sistpoty: I'm not doubting you, I'm just confused by that one :)
[02:27] <sistpoty> heh
[02:28] <sistpoty> well, usually I can tell exactly what went wrong, and I even believe that I'm not too bad with automake... in this case it still escapes me why the patch fixes the problem though
[02:28] <bddebian> Aye
[02:29] <sistpoty> ok, spouse just returned home... must leave now... cya
[02:30] <bddebian> Later man, thanks
[02:30] <LaserJock> you know
[02:30] <sistpoty> cya bddebian and LaserJock
[02:30] <LaserJock> we'd get so much more done on Ubuntu if it wasn't for spouses ;-)
[02:30] <sistpoty> haha
[02:30] <bddebian> Heh and jobs
[02:30] <LaserJock> but don't tell mine I said that :p
[02:30] <sistpoty> heh
[02:30] <sistpoty> <- now really leaves, cya
[03:39] <zooko> Hi folks.  Anybody interested in uploading Tahoe-LAFS to the Karmic Queue?  http://revu.ubuntuwire.com/p/tahoe-lafs
[03:59] <ScottK> Note: It's a reupload due to a licensing issue.
[03:59] <ScottK> So it's OK/desired even though it's late in the cycle.
[04:02] <jdong> plus, it sounds like a pretty damn cool project :)
[04:03] <ScottK> zooko:^^^^ There's your victim.
[04:04] <jdong> ROFL
[04:05] <jdong> ok let wrap up what I'm doing and take a look :)
[04:05] <jdong> boy you think after these years I'd learn what speaking up means in IRC ;-)
[04:06] <zooko> :-)
[04:11] <ScottK> jdong: I'd do it, but then I couldn't be the archive admin to review it.  Thanks.
[04:21] <jdong> ok, lemme look :)
[04:24] <jdong> zooko: sponsored :)
[04:26] <zooko> jdong: whoo!  :-)
[04:27] <jdong> I'll keep my fingers crossed for you too ;-)
[04:31] <zooko> Thank you very much!
[04:31] <jdong> sure thing, anytime!
[04:32]  * ScottK digs around.  Finds the remote for jdong's alarm clock and hands it over to zooko to make sure "anytime" is enforcable.
[04:33] <jdong> well as long as it's not the 150dB one on Digg or my roommate's which is always in some foreign timezone, that's fine :)
[04:34] <dtchen> git fetch
[04:34] <dtchen> bah, sorry
[04:35] <jdong> while you're here... ALSA on my 17" MBP
[04:35] <jdong> kidding ;-) another time
[04:35] <dtchen> you know the drill: ubuntu-bug alsa-base
[04:36] <jdong> it's already got a fairly lengthy LP bug... *finds number*
[04:36] <jdong> bug 337947?
[04:37] <jdong> idn what information it needs; with the latest posted patches and/or forcing model=mb5 I've got sound in everything, just no jack sense
[04:40] <dtchen> jdong: right, that bug is pretty unhelpful for me WRT your specific issue, because i have no way of knowing if your codec matches the reporter's precisely
[04:40] <jdong> dtchen: *nods* in that case I shall boot that machine up right now :)
[04:40] <dtchen> jdong: it is more helpful to just post another bug report with that info attached (which ubuntu-bug alsa-base will do)
[04:40] <jdong> will do, thank you sir
[04:42] <zooko> Okay folks, I'm definitely about to fall asleep.  As soon as Tahoe-LAFS is apt-gettable I'll post about it on my blog and identi.ca and so on and invite Tahoe-LAFS users to install Karmic and test it out.
[04:43] <jdong> whoo :)
[04:43] <jdong> good night, man!
[04:44] <zooko> Tomorrow I'm taking my children to aikido, then soccer, then having my father over for a visit, so at some point tomorrow night or Sunday I'll probably check for Tahoe-LAFS in Karmic...
[04:45]  * zooko tries to fall asleep, but is having too much fun listening to http://radio1190.org/1190high.m3u
[04:45] <jdong> whew, what a packed day
[04:45] <jdong> kids these days are involved in so many things
[04:49] <dtchen> headdesk. i hate brown paperbag bugs.
[05:19] <jdong> dtchen: ok I filed bug 437034 regarding my issue
[05:19] <jdong> thanks in advance
[05:19] <dtchen> jdong: thanks
[05:31] <Amaranth> Oh, should I file a bug for my laptop needing model=mb3?
[07:35] <wrapster> im a beginner at packaging and wanted to clarify a few things... have a look at this http://pastie.org/631355... (as an eg ) i wanted to know if all the files present in the upstream dir are necessary.. or can we do without some?
[07:51] <jmarsden> wrapster: You seem to have mixed source files with temp files from the build process in the same directory??  That's horribly confusing.  if you want to repackage flex, apt-get source flex and start from there.
[07:52] <wrapster> jmarsden: yeah thats where i started from .. i had already built flex but guess i needed to pull the source then ask the question ... :)
[07:52] <wrapster> sorry about that..
[07:52] <wrapster> will get back in a while
[07:53] <jmarsden> wrapster: Oh, then run make clean or make -f debian/rules clean    or both and try again :)
[07:57] <wrapster> jmarsden: is this better to base my question on? http://pastie.org/631368
[07:58] <jmarsden> Probably... but now you just have source files, so of course they are all needed... what makes you think otherwise?
[07:59] <jmarsden> Well, you could consider config.guess and config.sub disposable... but... what are you really trying to do here?
[08:02] <wrapster> jmarsden: when i looked at ways of packaging...(when my seniors were doing it) i thought i saw them remove files that ended with *.ex so was wondering what they are and why are they being removed.. forgot to ask then.. so troubing you.
[08:03] <wrapster> how about in the debian dir? apart from control,rules,changelog,copyright are there any other files that are necessary? to build a pkg?
[08:03] <jmarsden> Inside the debian/ dir if you use dh_make to generate a starting set of debian packaging files you can get that; but here you are starting from an existing package so there should not be any files around which are unnecessary.
[08:04] <jmarsden> wrapster: To build "a" package, or to build this one in particular?
[08:04] <wrapster> to build a pkg
[08:05] <jmarsden> at minimum you should only need those 4.  See https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20from%20Scratch
[08:06] <jmarsden> That guide also talks about removing the *.ex files, by the way.  Reading the whole guide is *strongly* recommended.
[14:36] <sistpoty> hi folks
[14:36]  * ScottK waves to sistpoty.
[14:36] <sistpoty> hi ScottK
[14:36] <diwic> hi there
[14:50] <ScottK> zooko: What are the licensing terms for src/allmydata/util/mathutil.py?
[15:28] <ScottK> sistpoty: IIRC maven is one of those things where you generally want the crack of the day, so while we'd need someone to shepherd through a set of updates, I'm don't think we need to be really picky about testing.
[15:29] <sistpoty> ScottK: ok, but I'd at least like to see a rudimentary test though
[15:29] <ScottK> OK.
[15:33] <less11> Hi all, I need to know where to ask questions ubuntu boot process (more specifically, initrd related questions)
[15:33] <ScottK> less11: I think there is an #ubuntu-boot channel.  I know there's a LP team with a mailing list.
[15:36] <less1> ScottK: thanks.. :-)
[17:47] <lamalex> Does anyone know about cdbs simple-patchsys?
[17:47] <lamalex> how do I create a new patch? Do I edit the code then do a diff and revert the code?
[17:49] <diwic> cdbs-edit-patch
[17:50] <Darxus> If I created a new package today, which didn't qualify for karmic, what would happen to it?
[17:51] <lamalex> Darxus: get it into debian and have it sync for lucid
[17:52] <diwic> lamalex: if you have the choice, switching to quilt is generally recommended
[17:52] <lamalex> diwic: yeah, but I don't have the authority to do that unfortunately
[17:52] <pochu> diwic: is it?
[17:53] <pochu> oh, generally
[17:54] <diwic> pochu: I believe most people think so (myself included), but I'm not sure if it is an official policy.
[17:54] <Darxus> Ohh, a name for what comes after kamric :P
[17:55] <Darxus> Packages can't be added to lucid yet though?
[17:56] <pochu> no
[17:57] <Darxus> Heh, wikipedia is already updated.
[18:00] <Darxus> Which event on the Lucid release schedule markes when new packages can be uploaded?
[18:00] <Darxus> https://wiki.ubuntu.com/LucidReleaseSchedule
[18:01] <lamalex> diwic: thanks
[18:02] <lamalex> Darxus: they can be uploaded at any point before feature freeze
[18:02] <lamalex> but debian import freeze is where it won't be synced from debian
[18:02] <lamalex> so I would try and get it uploaded into debian as soon as possible
[18:02] <Darxus> lamalex: Well, since they can't be uploaded now, that's not true.  When is the soonest they can be uploaded?
[18:03] <RainCT> (*automatically synced, you can still manually request syncs afterwards)
[18:03] <lamalex> Darxus: idk, as soon as the repos open I guess
[18:03] <RainCT> Darxus: as soon as the archive is opened, which is usually a few weeks after the previous release coming out
[18:03] <lamalex> nov 5 maybe?
[18:04] <Darxus> RainCT: Thanks.
[18:04] <Darxus> That should be on the schedule :)
[18:07] <Darxus> I just contacted the last person to edit the schedule and asked him to add it.
[18:11] <Darxus> Can you give me an example of a package that only has a couple .h files?
[18:11] <joaopinto> Darxus, .h are usually contained on -dev packages
[18:12] <Darxus> joaopinto: I know, I'm looking through them, thanks.
[18:15] <Darxus> $ for file in `dpkg -l '*dev' | grep ^i | awk '{print $2}'` ; do echo -n  `dpkg -L $file | wc -l` >> headercount.txt ; echo " $file " >> headercount.txt; done
[18:16] <Darxus> I love linux.
[18:17] <Darxus> libbz2-dev looks good.
[18:19] <Darxus> Well, before I start trying to build a new package for the first time I should ask if this makes sense.
[18:19] <Darxus> Nvidia has made hardware acceleration of video decoding available.
[18:20] <Darxus> Support is included in the source of the karmic mplayer package, but it's not enabled.
[18:20] <Darxus> Enabling it requires two .h files from nvidia.
[18:20] <Darxus> So I should package these two .h files and make that a build-dep of mplayer, right?
[18:21] <Darxus> (I have it working on my computer.  It's awesome.)
[18:21] <joaopinto> Darxus, have you checked those .h files copyright ?
[18:22] <Darxus> joaopinto: Just did.  It's good.
[18:23] <Darxus> 'Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction...'
[18:23] <joaopinto> Darxus, if the copyright is compatible with mplayer, it makes more sense to add those 2 .h as a building patch
[18:24] <joaopinto> i mean, to mplayer
[18:24] <Darxus> Does it?  What about other players that might build against it?
[18:27] <Darxus> Bah, trying to find somebody at nvidia to ask for a version number.
[18:27] <joaopinto> there are some cases of .h files repeated on several sources, if those 2 .h are part of a library it makes sense to package the entire lib :)
[18:33] <Darxus> joaopinto: I believe this support only exists as patches nvidia made to mplayer and these two .h files.
[18:34] <Darxus> So.. should I be making a package of two .h files?
[18:37] <Darxus> I don't think I got an answer to this before:  Do I need to use my real name when packaging/signing for upload to the archives, if I make it to that point?
[18:38] <sistpoty> Darxus: it's highly encouraged to use the real name
[18:38] <sistpoty> Darxus: header files belong to the package with the library that actually has the implementation, a standalone package with only two header files would be a little bit strange
[18:40] <sistpoty> (i.e. to the -dev package actually, see the library packaging guide for details)
[18:40] <Darxus> I finally had the sense to google to see what debian is doing with this.  There's an RFP bug:  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511555
[18:41] <ScottK> diwic: Very few people are neutral on the subject of quilt.  I think saying it's generally recommended overstates the case.
[18:43]  * sistpoty shoves more packages into ScottK's queue :)
[18:43] <ScottK> Excellent
[18:44] <Darxus> "Headers are alreay included in the nvidia source package"
[18:52] <Darxus> Looks like those headers are already packaged in nvidia-glx-185-dev in karmic, heh.
[18:58] <Darxus> Except they're not actually in there :(
[19:04] <ScottK> kirkland: I'm going over Universe stuff and accepting it.  Your versioning of the sobby upload seems a bit odd to me.  Didn't you want 0.4.5-1ubuntu1?
[19:29] <sistpoty> meh, no ftbfs bugs in the universe sponsors list... where's my whip? *g*
[19:35]  * sistpoty is off again, cya
[22:09] <hyperair> kirkland: i think i might have bugged you about this previously, but checking for $TERM screws up ssh sessions with byobu-launcher grandly.
[22:09] <hyperair> kirkland: please, just check *anything* except TERM
[22:09] <hyperair> what's wrong with just checking STY?
[22:10] <hyperair> in fact, what are the cases where STY goes missing?
[22:11]  * hyperair reads the bug report.
[22:12] <hyperair> i take it that it's acceptable to have byobu *not* launch, and instead have "exec byobu-launcher" just exit the shell instead.
[22:12] <hyperair> great. just great.
[22:13] <hyperair> $ ssh 192.168.1.3
[22:13] <hyperair> Connection to 192.168.1.3 closed.
[22:13] <hyperair> whee. fun.
[22:14] <hyperair> in the first place, what's wrong with having byobu-inside-byobu when you ssh to another machine that has byobu in it?
[22:15] <hyperair> hmm byobu is in main. maybe i should have ranted in #ubuntu-devel instead.
[22:15] <hyperair> oh well, what's done is done.
[23:45] <ScottK> zooko: Did you see my ping from this morning about licensing?