[01:49] <rlameiro> ScottL: ping
[01:52] <rlameiro> holstein: how is your voice?
[01:53] <rlameiro> up for a dubbing session?
[01:54] <holstein> rlameiro: OH speaking
[01:54] <holstein> hmmm
[01:54] <holstein> Ricardus has a great radio voice
[01:54] <holstein> if you can talk him into it
[01:54] <holstein> im not saying no
[01:54] <rlameiro> well, i just recorded a video of the ubuntustudio install process
[01:54] <rlameiro> maybe you could do the audio part?
[01:55] <holstein> im just saying, i dont think im the best candidate
[01:55] <rlameiro> my english is not that perceptible....
[01:55] <holstein> rlameiro: i'll try it
[01:55] <holstein> you got a script?
[01:55] <rlameiro> nope
[01:55] <holstein> i mean, you can use it or not
[01:55] <rlameiro> :D 
[01:55] <rlameiro> its al yours
[01:55] <holstein> hmmm
[01:55] <holstein> wheres the vid?
[01:55] <holstein> you want to email me?
[01:55] <holstein> mikeh789 at the gmail
[01:56] <rlameiro> holstein: its encodign from recordmydesktop
[01:56] <rlameiro> 9%
[01:56] <rlameiro> i need to edit it a bit
[01:56] <holstein> OH
[01:56] <holstein> let me know
[01:56] <holstein> i'll give it a go :)
[01:56] <rlameiro> take out the long boring parts :D
[01:56] <rlameiro> you know Xjadeo?
[01:57] <holstein> nah
[01:58] <rlameiro> holstein: its a video player, just video no audio, and it is conrolled via jack transport :D
[01:59] <rlameiro> so you can be recording it realtime on ardour. you pause in ardour, and the video pauses :D
[01:59] <holstein> i'll figure it out :)
[03:23] <ronj> hello abogani and everybody, I'm prepping my test machine for some kernel tests (generic and lowlatency/realtime from abogani's ppa --thanks!--) but linux-headers-lowlatency is not installable because it depends on linux-headers-2.6.35.20-lowlatency, which depends linux-headers-2.6.35.20, which seems to no longer be in the repos. Is this known / expected? Any alternative way to install this lowlatency kernel?
[03:25] <ronj> uh, correction: linux-headers-lowlatency seems to install even though the dependency isn't satisfied oÔ; but I doubt my lowlatency will work without the headers, will it?
[03:47] <persia> Should work fine: you just won't be able to compile kernel modules, so stuff like nvidia or fgrlx drivers won't work.
[03:49] <ronj> persia, should be ok indeed, I'm using an intel chip. thanks!
[05:10] <paultag> persia, roger
[05:12] <persia> paultag, In the very short term, chasing the status of highly-visible bugs would also help: holstein or rlameiro usually have a good handle on what is causing the most pain (from testing and user-support activities).  ScottL can probably give specific direction if you need, but he's already largely focused on strategy for the next release, expecting the rest of us to make sure this one is in great shape.
[05:13] <paultag> persia, OK, awesome. Well, I'll play the bar-back, I'll just try and find stuff to blast away thats just a pita and not a nested bug or anything like that
[05:13] <persia> Excellent
[05:17] <paultag> persia, is there a LP project that has all the ubuntu-studio bugs filed against ( as well as against Ubuntu ) ?
[05:17] <paultag> wait, found it
[05:17] <paultag> sorry :)
[05:18] <holstein> hey paultag :)
[05:18] <paultag> hey there holstein, how are you?
[05:18] <holstein> let me know if i can help at all with the bug-work
[05:18] <holstein> im good
[05:18] <paultag> holstein, for sure, I'll be sure to take you up on that
[05:18] <holstein> i joined the bug squad
[05:18] <holstein> but i got busy
[05:19] <holstein> and it ended up being a bit too much to take on
[05:19] <paultag> it happens :)
[05:19] <paultag> holstein, aye, you should avoid burnout at all costs :)
[05:19] <holstein> but i could tackle a few things with you if needed
[05:20] <paultag> holstein, for sure, thank you for the offer
[05:21] <persia> paultag, 95% of bugs are going to just be normal Ubuntu bugs.
[05:21] <paultag> persia, aye, well I'm on bug control / bug squad, so no harm no foul.
[05:22] <paultag> persia, is there a tag for "not our problem" ?
[05:22] <persia> What would fall into that category?  Do you have an example?
[05:23] <paultag> persia, well by definition a bug against ubuntu studio would also be a bug against ubuntu -- if it's not something that falls into ubuntu studio ( read: normal Ubuntu work ), is there a tag we can apply ( yes, it's valid in studio, but the Ubuntu community should look at this as well )
[05:24] <persia> We're *part* of the Ubuntu community :)
[05:24] <paultag> persia, well duh! :) -- but something that gets filed against Ubuntu Studio that has to do with something like binutils
[05:24] <persia> That said, I think we're primarily interested in bugs on packages that end up in our primary tasks.
[05:25] <persia> A cleanup of the UbuntuStudio project would be good: every bug there should have an Ubuntu task, if it's valid.
[05:25] <paultag> yes it's "valid", but it's really not something we should spend time on, that sort of thing
[05:25] <paultag> persia, OK, cool. I'll start with that
[05:26] <paultag> I'll start doing some work when it's not 12:30 AM :)
[05:26] <persia> Might even be safe to make the UbuntuStudio tasks "Invalid" with a comment saying "this affects all of Ubuntu, and is better tracked there" or similar.
[05:26] <persia> heh.
[05:26] <paultag> persia, yeah, I was thinking a tag, just because it's it's "valid"
[05:26] <paultag> persia, but you're right, it kinda seems silly to track it twice
[05:27] <persia> My concern is that I doubt anyone will go hunt for bugs closed in Ubuntu and still open in UbuntuStudio, and close them.  None of the other final statuses are correct.
[05:27] <paultag> persia, good point
[05:27] <persia> So, semantically, one can say "It's not a valid bug for UbuntuStudio, but it *is* valid for Ubuntu" by creating the Ubuntu task, and marking the ubuntustudio one invalid.
[05:27] <paultag> persia, OK, that sounds sensible to me
[05:28] <persia> If you come up with good comment text to inform the users, that may make it even smoother.  If you do that, I recommending adding the comment *before* adding the Ubuntu task, just to avoid sending lots of duplicate notices to e.g. the binutils developers.
[05:29] <paultag> persia, I'll be sure to come up with something sane and template it on the wiki for us :)
[05:30] <paultag> Righto, well I'm off. Got some work in six hours or so
[05:31] <paultag> persia, nice talking with you again, thanks :)
[05:31] <paultag> holstein, you too, we'll talk soon :)
[05:31] <paultag> night, all
[05:31] <holstein> GN
[12:50] <persia> rlameiro, Good day.  RC images are starting to get posted: dunno if ours are up yet, but ... :)
[12:50] <rlameiro> persia: did you look at the mailing list?
[12:51] <rlameiro> major fails on the iso building, says collin watson bot
[12:52] <astraljava> Uhh... damn, just as I got bandwidth for downloading. :D
[12:53] <rlameiro> well, you can use jidgo to download the iso, when is fixed just update :D
[12:55] <astraljava> I prefer to use zsync.
[12:57] <persia> rlameiro, I'm glad to hear you're on top of it: you probably know more than I.  I just saw you join IRC, and wanted to pass on stuff I saw in traffic whilst you were disconnected.
[12:58] <rlameiro> persia: I recorded a video yesterday, for the install. I will edit it today evening and send it to holstein for voice dubbing
[12:59] <rlameiro> try to make an "official" how to install Ubuntu studio
[12:59] <rlameiro> so people ca see how it works
[12:59] <persia> I'm looking forward to seeing that.  "How to install Ubuntu Studio: video produced on Ubuntu Studio"
[12:59] <rlameiro> it should be ready before the launch, I hope
[12:59] <persia> Cool!
[13:04] <abogani> really cool
[13:05] <rlameiro> I think we coudl do a series of little videos on different ways to configure jack
[13:05] <rlameiro> one for firewire devices
[13:05] <rlameiro> one for alsa, usb etc
[13:05] <rlameiro> and do some explanation of the latency and settings
[13:06] <rlameiro> so, everytime someone comes with questions on how to configure it, we forward him/her to the video
[13:09] <ScottL> rlameiro, that is an awesome idea!
[13:09] <rlameiro> thanks
[13:09] <rlameiro> well, need to go to works
[13:09] <rlameiro> cya later
[13:21] <astraljava> So wait, cdimage.u.c shows the list of files, but they're not accessible?
[13:21] <astraljava> Morning Scott!
[13:23] <astraljava> Meh, PEBKAC.
[13:26] <astraljava> Nice! 100.0% 1187.8 kBps DONE
[14:57] <scott-work> abogani: i read your email about the -lowlatency and -rt kernels
[14:57] <scott-work> abogani: i want to apologize because i did not realize that you had wanted testing done at this time
[14:57] <scott-work> abogani: i will certainly start testing them this week
[14:59] <abogani> scott-work: No you don't understand me. I want that someone else offers for the task and for this I'm doing some "fear" for see replies...
[15:00] <abogani> scott-work: We can't do the work if the tasks are always done by same two o three persons.
[15:02] <scott-work> abogani: ooohhhh, i see :)
[15:16] <astraljava> abogani: How many hours do you normally spend on a given kernel release, when you were preparing the -rt flavor?
[15:19] <abogani> astraljava: On wonderful Hardy release I spend 1/2 hours a day.
[15:20] <abogani> Since that I spend most of the time on burecrotic works.
[15:20] <abogani> scott-work: Could you read my last email and say me if it is understable?
[15:20] <astraljava> abogani: Half an hour, every day?
[15:21] <abogani> astraljava: No 1 or 2 hours every day. But since Hardy things are more easy probably 1/2 every three days should be enough.
[15:22] <astraljava> abogani: Okay. I'm trying to come up with an estimate of how long it would take me. Might be too much :-/
[15:22] <abogani> Test, Upload rights and alignment with the -generic one are the most critical issues.
[15:22] <abogani> astraljava: If aren't forced to do all the jobs.
[15:22] <abogani> astraljava: You can do be a part of it.
[15:22] <persia> Upload rights are the hard part, because only kernel folk tend to be happy sponsoring kernels, and there's only ~4 kernel folk who *can* upload.
[15:23] <persia> Might be best to have abogani continue to be the focal point for the uploads, sharing the coorindation, testing, patch hunting, etc. with others, just because the process is painful.
[15:23] <abogani> astraljava: Test for example is only made on new release arise.
[15:24] <abogani> persia: I really don't know if it is the right thing for the Studio project.
[15:26] <abogani> persia: As you know well I'm a lot unreliable  lately...
[15:26] <abogani> :-(
[15:41] <astraljava> abogani: Sure, I can participate in the process, and learn by doing.
[16:05] <astraljava> abogani: For the most part, at least in the beginning, I'd need you to organize, though. There's so much to learn, I'd work better if I were given "orders". :)
[22:45] <scott-work> ugh, we have RC ISO image ready to test but tonnes of applications apparently failed to build installable binaries this morning :(
[22:45] <holstein> :/
[22:46] <holstein> whens the deadline or whatever?
[22:46] <holstein> for testing?
[22:46]  * holstein will do the 64bit ones again
[22:46] <holstein> i just dont want to be doing it last minute like last time if possible
[22:50] <scott-work> holstein: i believe the thought is we have approximately two days to validate the ISO image before it is released
[22:53] <scott-work> or not released if we don't test it :P
[23:15] <ronj> is it normal to have to sudo /etc/init.d/networking restart in order to have my network, even after a clean restart ?
[23:17] <ronj> s/normal/expected/g: I mean is this known, or due to some misconfiguration?