[08:34] <Naranek> tgm4883: did you find out anything?
[13:52] <Naranek> tgm4883: good news
[13:52] <Naranek> ubuntu security responded. cardamom and kapok are iso build servers.
[13:53] <Naranek> 11.04 mythbuntu .iso installs the livecd SSH host key by mistake when installing a system
[13:53] <Naranek> the root user is for acces to the database when booting off the livecd
[13:53] <tgm4883> Naranek, ah
[13:53] <Naranek> and root login is enabled by default in all ubuntus
[13:53] <Naranek> strange that last part
[13:53] <Naranek> but yeah
[13:54] <tgm4883> Naranek, in that case, can you open a bug at https://launchpad.net/mythbuntu for the SSH host key thing?
[13:54] <Zinn> [launchpad.net] Mythbuntu in Launchpad
[13:54] <tgm4883> root login is enabled by default?
[13:55] <tgm4883> I don't think it's enabled on my desktop, where exactly are you looking?
[13:55] <Naranek> /etc/ssh/sshd_config
[13:57] <tgm4883> hmm, i stand corrected
[13:57] <tgm4883> I suppose since the root user is disabled by default that it doesn't really allow the root user login
[14:01] <Naranek> yeah
[14:01] <Naranek> still.. it fooled me
[14:01] <Naranek> I couldn't imagine for a second that it would be the default setting
[14:02] <Naranek> a disturbing set of bugs this was
[16:26] <adam__> Hi there, I am having a bit of trouble I am setting up my ps3 bluetooth remote for my mythtv box, and for some reason when I put the box to sleep and then wake it up my keys are no longer set to what they are supposed to do. It appears it is creating a new event handler everytime I wakeup from suspend.
[21:57] <Shred00> latest master (0.25) build is 21 hours old.  i recall the last time i asked about builds taking so long there was in fact a problem and someobody needed to kick something.
[22:02] <tgm4883> Shred00, it's a daily build
[22:02] <tgm4883> 1 day == 24 hours right?
[22:02] <Shred00> tgm4883: hrm.  i thought it was done on-demand, i.e. per commit.
[22:03] <tgm4883> nope
[22:03] <tgm4883> that would be pretty crazy :)
[22:03] <tgm4883> it's built daily IF there is a new commit
[22:03] <tgm4883> so if there is no commits, it doesn't build
[22:03] <tgm4883> but if there are 27 commits in a day, it only builds once
[22:06] <Shred00> tgm4883: i'm not sure "crazy" is the right word.  understandable that it's a shared build infrastructure for many projects but it's not strange to see a build per commit in projects that have the build bandwidth.  so in the least it would not be crazy for a queue that simply triggered a build when a commit was done and all commits that were done when the job came up in the queue were included, such that the build system is alwa
[22:06] <Shred00> this is how systems like jenkins work
[22:06] <tgm4883> yep
[22:06] <Shred00> builds are done as frequently as needed and able.
[22:07] <tgm4883> but doesn't work out so well for shared build servers
[22:07] <tgm4883> and isn't something that is usually a problem
[22:07] <tgm4883> is there something that needs testing?
[22:07] <Shred00> you don't get a guaranteed build for each commit but you are guaranteed to get a build that includes all of the commits done when the build is dequeued.
[22:07] <Shred00> jenkins works perfectly fine for shared build servers
[22:08] <Shred00> anyway, just wanted to see how much 2f6c4eec57121a652e60c8e426e5bec5250a9076 helped things here
[22:11] <Shred00> and was hoping to upgrade before the evening "condition brown" (no upgrades while recordings are happening -- obviously) set in.
[22:12] <Shred00> but really, wed/thu are the more busy recording nights, so no rush i guess.  only a single recording on the second qam tuner here this evening.
[22:12] <Shred00> oh.  i lied.  two.  and one is a WAF recording.  i guess we'll see what happens tonight.
[22:15] <Shred00> oh, looks like 0542a100237dd26bcbc60212c443f4619586f15b goes even further