[00:02] <Len-1204> ailo: do you happen to know what order the install process looks at the packages?
[00:03] <ailo> Len-1204: No idea. I really don't have much of a clue about the whole install process as a whole
[00:03] <Len-1204> It is kind of a black box.
[00:04] <ailo> Len-1204: I'm sure Debian has documentation on it, and then there's additional Ubuntu way of doing things
[00:04] <Len-1204> I have figured out how to get jackd rt, but it needs to run after jackd's config.
[00:04] <ailo> Len-1204: As a part of the package itself, or something else?
[00:05] <Len-1204> I don't want to touch jackd, but we could do it as part of our settings package.
[00:05] <Len-1204> we would save the true value where the jackd package expects to find it.
[00:06] <ailo> I'm wondering if there is a force yes parameter that can be used for installing jackd
[00:07] <ailo> Again, no idea about how it works. Suspecting that there is a file which is read and applied
[00:07] <ailo> Seeds?
[00:07] <Len-1204> I haven't seen any way of giving parameters except what they use.
[00:08] <Len-1204> There is a command to set instead of use the input. But we need to do that after jackd's config has tried to get an answer.
[00:08] <Len-1204> Otherwise jackd might over write it.
[00:09] <Len-1204> They use the db-config package.
[00:09] <Len-1204> It is built for these kinds of things.
[00:12] <Len-1204> ailo: if the packages are opened in the order the files are in the directory, it should be fine.
[00:13] <Len-1204> but if it uses the order of the seeds, then not.
[00:13] <ailo> Len-1204: Whatever way works. It's only for the DVD install procedure after all
[00:14] <Len-1204> we could always put a audio-settings package in too.
[00:36] <micahg> holstein: I really didn't do much for it
[02:28] <ScottL> len-nb, we can get the -rt setting to work
[02:28] <ScottL> for jack
[02:28] <ScottL> len-nb, cjwatson has said that preseeding should be able to answer this question correctly
[02:28] <len-nb> Ok
[02:29] <ScottL> but it looked like ubiquity was ordering the preseeding after the installation :P
[02:29] <ScottL> we filed a bug on it i believe
[02:29] <ScottL> after we get a few things done with lightdm and such and our image boots and installs like it should (more or less)
[02:30] <len-nb> He may know more about db_config than I do.
[02:30] <ScottL> i was going to poke cjwatson about this (ubiquity and the preseeding) again
[02:30] <ScottL> len-nb, heh, cjwatson know many a thing, arcane and otherwise ;)
[02:31] <ScottL> but seriously he felt very confident it should work and will work, we just probably just need to poke him again later on
[02:31] <ScottL> i hope to push the lightdm fixes this week so we can get the install from hanging and fix a few other issues
[02:31] <len-nb> I tried reading the docs on it... and what jack does and that was what I figured
[10:49] <abogani> TheMuso: Your changes:
[10:49] <abogani> 1) Add a huge burden on maintenance without any pro (symlinks are made to make maintance at zero cost)
[10:50] <abogani> 2) they requires to upload (aka dput-ing) the complete source code (i.e. ~500 MB  vs ~2 MB)
[10:50] <abogani> 3) It seems that you don't want place that package in Universe (Field "Section" in control file)
[10:50] <abogani> 4) It seems that you don't make d-i modules for this package ("disable_d_i = true" in rules.d/*.mk).
[10:51] <micahg> abogani: adding universe to section is unnecessary, that's set at the archive level
[10:56] <abogani> But should it be better if it would be explicit? 
[10:57] <abogani> contributor could know nothing about archive level...
[11:15] <micahg> no
[11:15] <micahg> it shouldn't matter for contributors what component something is in
[11:30] <abogani> If it is really matters Section field simply doesn't exist.
[11:31] <abogani> s/matters/doesn't matter
[15:53] <scott-work> micahg: i hope to have some fixes uploaded this evening to fix a few bugs, will you be able to help me upload them?
[19:39] <micahg> scott-work: over the weekend, sure
[20:22] <scott-work> micahg: thank you
[20:22] <scott-work> i have a question though
[20:22] <scott-work> well, two qustions, at least
[20:22] <scott-work> are we going to need a FFe for the lowlatency kernel?
[20:23] <scott-work> debian has supposedly made a change to mudita24 to add the .desktop file (i have not verified this), will we need a FFe or a sync request for this?
[20:49] <micahg> no, low latency kernel is uploaded
[20:49] <micahg> no, a .desktop file isn't a feature
[20:49] <micahg> jst requestsync should be fine
[22:40] <scott-work> just so the channel knows, i'm hoping to fix the lightdm issue this weekend and perhaps the "ubiquity hangs" bug as well
[22:41] <scott-work> i'm guessing the lightdm issue is affecting ubiquity as well, because i realized i had done a few things incorrectly when i parsed the xubuntu packages into ours
[22:41] <scott-work> but then i would really like to focus on getting RT permissions to work, both in the live environment and installed
[22:41] <scott-work> and get the pulseaudio<->jack bridge working
[22:42] <scott-work> after those two would be the ubiquity plugin that astraljava was working on
[22:42] <scott-work>  
[22:43] <scott-work> this weekend i hope to accomplish getting the lightdm/default-settings packages updated (need to test build/install), file the LTS application, and file a syncrequest for gettin the mudita24.desktop file issue resolved
[22:48] <astraljava> scott-work: Yeah, sorry I haven't had time for that, but I should from Tuesday onwards.
[22:54] <scott-work> astraljava: no problems, i'll get it probably tomorrow :)
[22:54] <scott-work> heading home