[00:18] <ScottL> ailo_,  unless we have a -lowlatency kernel that we can put into a PPA for natty then i don't think we can implement it for natty
[00:18] <ScottL> unless you see another option
[00:19] <ailo_> ScottL: I'm not even sure about the PPA at this point. I don't know what the plan is, really. 
[00:19] <ScottL> but keep in mind that our firewire users would like an -rt kernel as well, which would have to be kept in a PPA
[00:20] <ailo_> If we add the -lowlatency through PPA, no problem to implement that. If and when we have an -rt kernel there as well, easy to put that in too.
[00:20] <ScottL> ailo_, let's say then that unless paultag has other ideas that given the late date in this cycle and that it's not in the repos we skip the -lowlatency kernel for natty
[00:21] <ScottL> getting the other stuff done will be a huge improvement :)
[00:21] <ScottL> hell, it will be functional again
[03:25] <ScottL> TheMuso, persia: can i get your opinion on several older bugs?
[03:26] <ScottL> there are several older bugs, some even dating back to 7.04, that i seriously doubt we will fix, would it be improper to simply mark them as "won't fix"?
[06:02] <TheMuso> ScottL: If they are from 7.04, just mark them won't fix, tell the reporters that feisty/gutsy are EOL, adn to test with the latest release, maverick.
[09:35] <mondi> anyone can help me
[09:36] <mondi> i have a problem opening computer or any disks
[13:33] <paultag> scott-work: dude, we can get it in
[13:33] <paultag> scott-work: it's bugfix only
[13:34] <paultag> scott-work: it's early in the FF, and it's not a new package
[13:34] <paultag> scott-work: it's ripe for a FFe :)
[13:34] <paultag> we need to just crank it out and get it sponsored 
[13:37] <scott-work> paultag:  do you have an idea when it might be ready?  I'll fill out the FFe then
[13:37] <paultag> scott-work: I have no idea, ailo has been rocking it, so I've stayed back
[13:38] <paultag> scott-work: he's less then 2 hours away from finishing it, I think (from what I've seen)
[13:38] <paultag> scott-work: if he can kill that off, then I can whip the package into shape and give it an upload to REVU
[13:41] <scott-work> i thought REVU was for new packages?
[13:41] <paultag> oh shucks
[13:41] <paultag> I think you might be right scott-work 
[13:42] <paultag> god, that's stupid
[13:42] <paultag> mentors.debian.net is awesome
[13:42] <paultag> then debdiff it is
[13:43] <scott-work> paultag: wow!  http://wiki.debian.org/DebianMentorsFaq           http://mentors.debian.net/cgi-bin/welcome  both look awesome
[13:44] <scott-work> i will have to look into them more
[13:45] <paultag> scott-work: whenever you do anything (new package / updated package) you dput to mentors.debian.net, then send out an email to the list :)
[13:45] <paultag> unless you have a mentor
[13:45] <paultag> then just do whatever, I guess :)
[13:52] <scott-work> but in this case, we are updating a package that is _only_ in ubuntu, will the debian mentors help with this?
[14:14] <paultag> scott-work: nah, d-m is of no use here :)
[14:19] <paultag> BBL, school
[14:39] <ailo_> scott-work: It'll be more than 2 hours og work for me, but yes. It's not far from being finished. I still haven't found out how to work out problems with packaging, which is something I have almost as little experience with as python coding, so it's hard to say when.
[14:41] <ailo_> The package won't build, probably because there are some settings that need to be straightened out. I've done my best to see what I need to edit (using the original ubuntustudio-controls package as base), but I'm clearly missing something.
[14:43] <ailo_> scott-work: paultag: I would prefer the new -controls to use python only, but to have things wrapped up fast, I will need to use zenity to complement the shell commands I'm using, cause the shell is freezing up the app when executing the commands. A zenity prograss dialog will at leas show the user something is happening.
[14:44] <ailo_> scott-work: paultag: So, if someone can help me with packaging, and I add the zenity thing, I'd say we can be ready within a day even.
[14:45] <paultag> ailo_: I'm good to package at the drop of a hat. If it's 90% there ( no install scripts or anything ) I can kill it off
[14:45] <paultag> zenity is not the worst case
[14:54] <ailo_> paultag: It's all there in the git repo.  The old package and the source to my stuff. There are more stuff that should end up in /usr/share/ubuntustudio-controls than in the original, otherwise it's the same deal.
[14:55] <ailo_> paultag: Just changing the changelog now
[15:01] <ailo_> paultag: How do I set my details, so they end up in the changelog?
[15:02] <paultag> ailo_: set DEBFULLNAME / DEBEMAIL ?
[15:02] <paultag> ailo_: and you should use dch :)
[15:11] <ailo_> paultag: Ok, so the changelog is ok I hope. I'll finish the program within 24 hours. Will you need Natty in order to build the package?
[15:13] <ailo_> paultag: I really don't know what things need to be edited in the package if we are to use the one that is already laid out. You can make your own from scratch, if you want to of course.
[15:13] <paultag> ailo_: I have a pbuilder
[15:13] <paultag> ailo_: it's OK. Paste the changelog, I'll take a look
[15:14] <ailo_> paultag: http://paste.ubuntu.com/573488/
[15:15] <paultag> ailo_: it looks OK so far. The close syntax also looks off. It should be: New release has a more robust interface, and small updates (LP: #nnnnn).
[15:16] <ailo_> paultag: The urgency could be changed? And maybe add that we have changed the program a bit.
[15:16] <paultag> ailo_: you should always describe what you're closing and why
[15:16] <paultag> ailo_: no, low is good
[15:16] <paultag> ailo_: naw, debian/changelog is for debian stuff, nto the project as a whole
[15:16] <paultag> ailo_: you're also the only commiter, so you can remove your name in []
[15:16] <paultag> see crimsun's commit
[15:16] <ailo_> Ok
[15:18] <ailo_> paultag: So, you never worked with Egg?
[15:19] <ailo_> I think this is Egg/debian packaging
[15:19] <ailo_> The original, that is
[15:20] <paultag> ailo_: aye
[15:20] <paultag> ailo_: for lintco, never anything serious
[15:27] <ailo_> paultag: http://paste.ubuntu.com/573492/ It's in the repo now.
[15:28] <paultag> ailo_: killer
[15:29] <paultag> ailo_: whoh, interesting way of storing stuff in the git branch
[15:29] <paultag> ailo_: have you looked into git-buildpackage and pristine-tar ?
[15:30] <paultag> ailo_: you also have issues -- http://pastebin.com/CGb5uGCa
[15:30] <paultag> I'll try a build
[15:31] <ailo_> paultag, If you try a build, at least you get a new tar I guess, which you can move somewhere else and start over.
[15:31] <paultag> ailo_: no no
[15:31] <paultag> ailo_: it's OK -- just use pritine-tar to stash it in it's own branch
[15:31] <paultag> ailo_: and you don't need to track the dsc
[15:32] <paultag> (and you have some policy issues)
[15:32] <ailo_> paultag: That's the kind of stuff I know nothing about :)
[15:32] <paultag> ailo_: i can spend some time after I get back from the Gym patching this, if you want
[15:33] <ailo_> paultag: Just building it gave me an error, where the python files would end up in folder for 2.7, but the package builder were looking for them in 2.6
[15:33] <ailo_> paultag: It would be great if you straightened the packaging out. Then we can finish this pretty quickly I hope
[15:34] <paultag> ailo_: awesome. Rock on. I'll send you a git-format-patch by tonight
[15:35] <ailo_> paultag: Going jogging myself. Catch you later.
[15:35] <paultag> ailo_: cheers!
[17:06] <scott-work> ailo_, paultag: both you guys rock! \m/
[17:09] <paultag> scott-work: <3
[17:09] <paultag> We've got you covered, dude
[17:37] <paultag> ailo_: I almost have it in shampe
[17:37] <paultag> shape *
[17:38] <paultag> running some tests / reviews
[17:40] <paultag> whoh, found some issues :)
[17:53] <paultag> ailo_: http://git.pault.ag/?a=summary&p=ubuntustudio-controls <-- I've cleaned most of the lintian issues out. It's in decent form with a prist-tar branch
[17:54] <paultag> ailo_: git clone git://pault.ag/paultag/ubuntustudio-controls.git  <-- so you can take a look before you merge
[18:14] <scott-work> paultag: will we be able to provide a debdiff for this once it's all done?
[18:14] <paultag> scott-work: I can do that now, but there's one outstanding issue on the deb that I'm not happy with. Just having ailo_ check out changes 
[18:14] <paultag> scott-work: but yes, 100%
[18:15] <paultag> scott-work: it's in "OK" shape right now, one hell of a lot better then when we started. Not perfect yet, but OK.
[18:15] <scott-work> paultag: sweet, don't need it immediately though
[18:15] <paultag> scott-work: understood :)
[19:32] <ailo_> paultag: So it's ready to be built now?
[19:33] <paultag> ailo_: it can be built, and it's clean ( save the gksudo call in the .desktop )
[19:33] <paultag> that throws an error, but I added a dep on gksu, so it's "safe"
[19:34] <ailo_> paultag, right. Can we remove that? We should not run the app as sudo.
[19:34] <paultag> ailo_: Oh! Yes! Please!
[19:34] <paultag> Let me do that ;)
[19:35] <ailo_> paultag: Ok. Just came back from a second lap. I'll finish the zenity bit. I'll still need someone to review/test the app before we can assume it's fine to be released.
[19:36] <paultag> ailo_: Oh OK. Well, if you want to change it, that's fine :)
[19:36] <paultag> ailo_: I also pushed the tarball into prist-tar 
[19:36] <paultag> ailo_: so beware of that :)
[19:38] <ailo_> paultag: I will only be changing the glade file and the main source file hopefully. Removing the -lowlatency option and adding a zenity progress bar. How about dependencies? How does that work?
[19:38] <paultag> ailo_: pull my branch
[19:39] <paultag> ailo_: it will be in good shape :)
[19:40] <ailo_> paultag: Did you change the .desktop yet? I did "git pull", but it says, already up to date.
[19:41] <paultag> ailo_: no, because you have to kill the tag (or bump the major number) repack and fix :)
[19:41] <paultag> ailo_: and I'm super busy right now, getting ready for klass
[19:42] <ailo_> paultag: Alright. I expect this will take a few hours for me to complete, so I'll ping you when you can pull the one base on your package.
[19:42] <ailo_> based*
[19:42] <paultag> ailo_: rock on, dude!
[19:42] <paultag> ailo_: remember to use: `lintian -iIE --pedantic' to test your deb and dsc :)
[19:44] <ailo_> paultag: Hmm, let's see if it helps me. I expect you won't have too much difficulty fixing it once it's done. What's the build command for building the package btw?
[19:45] <paultag> ailo_: my workflow is as follows (might be a bit backwards) -- dpkg-buildpackage -S, pbuilder-dist <dist> *.dsc, git-buildpackage --git-tag, pristine-tar commit ../<package orig tarball> <release id>
[19:45] <paultag> ailo_: I also do a review on most of that as I go, check for unneeded stuff, warnings, errors, info tags, all that
[19:46] <ailo_> paultag: Thanks. I'll try that.
[19:46] <paultag> ailo_: rock on
[20:13] <scott-work> paultag and ailo_ :  i'll be happy to test it when it's ready, i've got an updated natty install waiting
[22:53] <ailo_> bash scripting is not all that straight forward sometimes :/
[23:44] <ailo_> paultag: I think I need to add two small bash scripts to be able to do what I want. What's the policy about scripts? Where can they be kept, if they are a part of the program, but not meant to be executed by anything else?