=== kiko-fud is now known as kiko-afk [20:29] <sinzui> beuno: I have this hole in my distro page. I really want to add one more portlet that is guaranteed to be present for all distros. Is there something from the page you want to see. [20:30] <beuno> sinzui, ah [20:30] <beuno> how can we fix that? [20:34] <barry> sinzui: thanks i saw that. probably will end up finishing that monday morning [20:35] <sinzui> beuno: cprov: I moved the package search into a nice portlet. I see there is a very nice ppa search form. IS there user demand to search ppas from the ubuntu page? [20:35] <beuno> sinzui, there's nowhere else to do so [20:35] <sinzui> may be we need a section that points to ubuntu.com to get ubuntu and flavors [20:36] <sinzui> oh!. We do not say anything about kubuntu on the ubuntu page. [20:36] <cprov> sinzui: yes, flavour do not exist in soyuz (UI) === mup_ is now known as mup [21:04] <gary_poster> salgado: hey. have you thought about the policy for how to manage source for our non-standard distributions (the one-offs we produce, like we did briefly for Storm and that I've done for other reasons) that kiko-afk asked us to talk about? [21:04] <gary_poster> do you want to talk about that sometime soonish? this evening, or Monday or something? [21:08] <salgado> gary_poster, I haven't, sorry. Monday sounds good to me [21:09] <gary_poster> salgado: np. ok cool. ping me sometime then, or I'll ping you. [21:13] <beuno> barry, https://staging.launchpad.net/bzr [21:13] <beuno> barry, try to edit the programming language [21:17] <barry> beuno: somebody br0x0red my beautiful ui [21:19] <beuno> barry, yes, just a heads up as it will hit edge tomorrow :) [21:19] <barry> beuno: good thing tomorrow is saturday! [21:19] <beuno> barry, no it's not [21:19] * barry might as well file the bug for it now though [21:19] <beuno> it's friday+1 [21:19] <barry> beuno: monday-2 [21:20] <beuno> see, I didn't want it to sounds depressing [21:20] * barry invokes warsaw's second law [21:20] <beuno> damn [21:20] <barry> beuno: in all seriousness, i'm putting money on it being a bug in lazr-js [21:21] <beuno> barry, probably [21:21] <beuno> some things still seem to be too fragile [21:21] <barry> s/some things/all of javascript/ [21:21] <beuno> heh [21:23] <barry> beuno: on the bright side, the page otherwise looks great :) [21:24] <barry> see, i can be optimistic [21:24] <barry> lpbug 413793 [21:24] <mup> Bug #413793: inline editing doesn't play nicely with launchpad 3.0 UI <LAZR Javascript Library:New> <https://launchpad.net/bugs/413793> [21:25] <beuno> barry, yeah, I'm lovin 3.0 === cprov is now known as cprov-afk [22:13] <beuno> rockstar, thumper, I've spent my afternoon working on the branch index page [22:13] <beuno> maybe I'll get it into a RFC state [22:13] <beuno> by the end of the day [22:13] <beuno> if not, early next week === salgado is now known as salgado-afk === matsubara is now known as matsubara-afk [22:43] <flacoste> mthaddon: can you set the default review team of https://code.edge.launchpad.net/~launchpad-pqm/canonical-identity-provider/trunk to the ~launchpad? === EdwinGrubbs is now known as Edwin-afk [23:32] <wgrant> maxb: I just ran the entire test suite, after giving it enough RAM and disk. Everything passed. [23:32] <wgrant> I have both ~launchpad/ppa and ~maxb/launchpad, with no other custom bits in the stack. Is that your config?

=== kiko is now known as kiko-afk [00:12] maxb: OK, now I'll run that test.. [00:12] Let's see how it goes... [00:14] maxb: Runs fine here. [00:14] I'm confused. [00:14] You have a few other tests failing that work for me, don't you? [00:15] one other - LaunchpadOnKarmic is up to date [00:16] maxb: Ah, hadn't seen that latest change. [00:18] right, let's see if it's arch-specific [00:18] * maxb runs it on netbook.... [00:18] I would try on amd64, but that means cleaning out sourcedeps which I don't have a good process for yet. [00:20] rm -rf eggs/* && for d in sourcecode/*/; do (cd $d && bzr clean-tree --force --ignored --unknown --detritus); done [00:20] I suppose so! [00:21] I guess if you're lucky you can leave the eggs [00:21] They should be version/arch-specific [00:22] So yes. [00:22] We'll see. [00:22] * maxb has been caught out by py2.5/UCS4 vs. py2.5/UCS2 [00:22] Hm. [00:22] I'd forgotten about a Python I had in /usr/local/bin/ [00:23] Somebody broke Python 2.6 like that in late Jaunty, I recall. [00:23] Caused a lot of things to die in strange ways. [00:24] Fortunately most had missing symbols, so it was obvious. [00:24] Right, well I've reproduced the DONE != ACCEPTED one on entirely separate Karmic installations on different hardware, one amd64, one i386, so I've no idea how it's passing for you! :-) [00:26] Intriguing. [00:26] package-diff.txt is grinding away on the netbook now [00:26] I might try cleaning out my ~/launchpad and starting from scratch. [00:30] Overkill perhaps, but I can't see anything else wrong :/ [00:32] package-diff.txt failure likewise reproduced [00:32] Damnit. [00:50] Hi, how to manage update ? rocketfuel-get and what ? [00:52] Would a branch to convince rocketfuel-setup to use bzr+ssh for the initial download be accepted? [00:52] It still forces http. [00:58] Isn't that deliberate? [00:59] It was. [00:59] Not sure there's any reason for it to be now. [00:59] spm: Is LP still [00:59] ... still hot? [00:59] There was server-side support to force HTTP, which has probably been turned off now. [01:00] So I don't know why it's forced in the client too. [01:00] how did the server know? [01:01] There's a config option which specifies products whose development focus branches should only resolve to HTTP, not bzr+ssh. [01:01] Added just before the release. [01:06] sinzui: maybe you know what's the new deal with lazr branches? [01:08] wgrant: I may be missing the thrust of the discussion, but you could always - aiui - branch using http. It's a much lighter process at the cost of having the branch parent be not so helpful [01:08] lp is not hot any more :) [01:08] wgrant: we could update it [01:08] spm: And it daaaaaaaamn slow. [01:08] wgrant: http is used when you haven't done lp-login [01:08] lifeless: I know. [01:08] But rocketfuel-setup explicitly uses an HTTP URL to lessen the load. [01:09] Which probably isn't a valid concern any more. [01:09] wgrant: if the rocketfuel-get script either overrides HOME, BZR_HOME, or that setting specifically, ... [01:09] oh, it does what?! [01:09] insane [01:09] in the membrane [01:09] I keep saying this; there is no good evidence that the load is lighter over http [01:09] and some serious reason to believe that its /a lot higher/ at the moment. [01:09] because we have bugs. [01:09] 2a over HTTP really really sucks. [01:10] yes [01:10] Although it's not much better over bzr+ssh at the moment. [01:10] it makes millions of requests rather than 5 [01:10] (using latest nightly on the client, and LP as the server) [01:11] * thumper doesn't use rocketfuel-* scripts [01:12] * wgrant only uses rocketfuel-setup [01:12] wgrant: interesting. it should still be streaming [01:12] lifeless: It is. [01:12] But at ~100kbps [01:12] Oops. KB/s. [01:12] But still very very slow, even from the UK. [01:13] ha crap [01:13] there is a failure on the devel builder [01:13] soyuz bindarypackagerelease-views.txt [01:14] wgrant: whats your link capable of? [01:14] and when did you move to the UK ? :P [01:14] thumper: There was a testfix for that one this morning, wasn't there? [01:14] was there? [01:15] wgrant: yes there was [01:15] lifeless: 10Mbps. I can nearly saturate that from a UK host normally. [01:15] thanks for the heads up [01:15] thumper: It was the same one? (I can't see buildbot) [01:16] wgrant: it seems so [01:16] wgrant: have you alerted sysadmins? bzr should saturate the link. [01:17] spm: ^ [01:17] lifeless: how do we test where the blockage is? [01:17] lifeless: Let me test a host just near LP to see how the bandwidth is now... [01:17] what are youguys talking abou [01:17] the rewrite script is fucked [01:17] you know this [01:18] This is bzr+ssh, though. [01:18] I know you know this [01:18] elmo: wgrant is saying that the bzr+ssh streaming performance is underpar [01:18] oh [01:18] sorry [01:18] :) [01:18] thumper: I'd start by looking for swapping [01:18] thumper: failing that it might finally be a reproducible case of the problems the python VCS PEP guy had [01:19] * lifeless starts a stream up [01:19] lifeless: maybe [01:20] I'm getting 600KB/s from the UK now, so it does seem to be an LP problem. [01:21] I'm seeing 50-80 KB/sec - 40-160kbits, on a 1500kbit link [01:22] * lifeless tries mysql [01:22] can y'all try downloading a large file from the librarian to rule out general network issues? [01:22] woah. [01:22] elmo: yup, I was just looking for one [01:22] bzr is eating around a gigabyte of RAM. [01:22] http://launchpadlibrarian.net/28202431/dia_0.96.1-7.1_0.97-2.diff.gz [01:22] lifeless: ^-- is one I have in my browser history that isn't tiny [01:23] ~. [01:23] That sits at around 500KB/s for me. [01:24] Although it's not precisely large. [01:24] * wgrant fetches a buildd chroot. [01:24] 3,730,692 101K/s in 36s [01:24] elmo: ^ [01:25] Hrm. [01:25] bzr is now streaming at ~350KB/s [01:25] super, so not my problem ;-) [01:26] So much better, but still not as good as it could be. [01:26] ... and back below 100KB/s [01:26] elmo: did you just disown all of codehosting? :) [01:26] possibilities: [01:26] - ssh windowing problem [01:27] - bzr networking issue [01:27] - bzr performance problem [01:27] bzr is eating hundreds of megabytes of RAM at the moment. [01:27] Even branching lp:launchpad locally. [01:27] Both 1.17 and bzr.dev. [01:27] How odd. [01:28] lifeless: no, but there are other people available right now more qualified and suited to diagnose operational LP issues, as opposed to operational network issues [01:28] elmo: I was just teasing [01:36] I need claws to say something like "Hey, it looks like you're trying to do a code review in this email. Did you remember to sign it?" [01:43] wgrant: is it still very slow for you? [01:44] wgrant: can you wireshark and see if the window is closing up (would indicate bzr not reading fast enough) [01:50] wgrant: who is your isp? [01:52] intellectronica: ping [01:52] sinzui: hi [01:52] I'm going to reply to your email. === matsubara is now known as matsubara-afk [01:53] I think I know the answer. But I heard last week that we should not submit [01:53] intellectronica: If leonardr gave the all clear than you can [01:54] what, push to the lazr-developers branch? [01:54] intellectronica: their two branches listed in my email, the pqm one that launchpad uses and the official lazr.restful, which you must prepare a patch for (mine did not apply cleanly) [01:54] leonardr reviewed my branch, so presumably he's ok with that [01:54] intellectronica: lazr.restful. I presume so to [01:54] * sinzui looks to both branches [01:55] my branch is of the laze-developers one, so it applies cleanly. it doesn't apply cleanly against the pqm-managed one, but it shouldn't be hard to prepare a patch for that. it's a really simple change [01:55] okay [01:55] the question is, how do it get my change in? [01:56] should i submit to pqm, which is targeting an outdated branch, or somehow get it into the lazr-developers branch. and if the latter, how do i then get my changes used in LP? [01:56] for he pqm one, yes [01:59] sinzui: you sure? it seems to me that what we're using in LP is the newer branch (from casual inspection of the code) [02:00] I am sure you need to submit to two places with different rules [02:00] no, actually i may be wrong. maybe it is the pqm branch we're using [02:00] intellectronica: I need to put this in an email. I cannot think or type quickly at the moment [02:01] intellectronica: we are using the pqm. we then backport to our branch [02:01] sinzui: you can probably imagine what state i'm in. i'll look at this again in the morning and i'm sure everything we'll be clearer :) [02:02] okay. You will have an email which will help [02:02] sinzui: thanks a lot! [02:05] wgrant: ping [02:06] wgrant: I suspect you weren't using bzr+ssh [02:07] lifeless: Sorry, was in transit to work. [02:07] 9684KB 153KB/s | Fetching revisions:Inserting stream [02:07] It certainly was. [02:07] lp: appears to still use http [02:07] ISP is Optus (Cable) [02:07] Right. [02:07] But I gave it bzr+ssh explicitly. [02:07] bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel ? [02:07] Precisely. [02:08] ok, well thats good to know [02:08] bzr.log agrees that it was using that. [02:08] owever, I see my adsl saturated [02:08] which is good [02:19] wgrant: if you can reproduce, please be getting tcpdumps [02:19] and filing bugs [02:19] if its a bzr bug, we want to fix it [02:19] if its an operational issue we want to fix it [02:23] I'm going to be around but not near my computer for a while while I help with a submission to stop a huge building go up across the road [02:23] rockstar: if you need me, text :) [02:44] thumper: when you get back [02:44] is lp: meant to still force http? if its not, then something isn't deployed. [02:46] lifeless: I'm not back yet, but the change has landed but hasn't been rolled out [03:13] lifeless: I think it's probably a general bzr problem, not specific to streaming. It's really slow and memory hungry even doing a local branch. Can you try to reproduce? [03:13] (branching 2a lp:launchpad from a local shared repo to a new branch outside the repo. [03:14] wgrant: do you have the C extensions? [03:17] lifeless: The only .so I can see is _patiencediff_c.so. This is the ~bzr-daily-ppa build. [03:18] then you don't [03:18] check in bzrlib/bzrlib/ [03:19] james_w: around? [03:19] lifeless: Let's try Karmic's 1.18rc1, which might be more sane... [03:25] lifeless: That's muuuuuch better locally. [03:25] file a bug please [03:25] assign to james_w [03:25] on bzr [03:26] Although it's still eating lots of RAM and CPU, it's much faster. [03:26] Will do. [03:26] Thanks. [03:26] its caused by the bug I've filed about builds on karmic doing WEIRD SHIT with were the .so's go [03:26] but the daily debs should seperately be erroring/requiring the .so's [03:26] * wgrant disappears for lunch. [05:01] spm, g'f'day mate! [05:01] jtv: hey! [05:01] an Australian dared me to pinpoint his accent last night, and I couldn't even say for sure whether he was British or not. [05:01] :-) [05:02] In all fairness, he was from Adelaide, born in London, from two English parents. It all happened because I caught a few words his friend said and went "he's from Manchester, isn't he?" [05:03] (Apparently he lived in London and only betrayed bits of his original accent given sufficient beer) [05:04] spm: but seriously, I've got two CP requests up for the codehosting server... any chance we can do them nowish? [05:04] jtv: funny you should ask... [05:04] * jtv cowers behind laptop [05:04] both (plus 2 others) have passed testing [05:04] no wait, this thing is expensive [05:04] * jtv cowers in front of laptop [05:05] ...was there a "but" coming? [05:05] I was in the process of re-cowbowing the changes preparatory to pushing when a ... bigger priority fail hit [05:05] -ETOOMANYFAILURES [05:05] that seems to have recovered sufficiently atm, that I should be able to get back on the CP in <5 [05:05] catch (const exception &e) { puts(e.what()); } [05:05] heh [05:06] (I mean, "what happened, Steve?") [05:15] puts? [05:15] ew [05:16] std::cerr << e.what() surely [05:16] and it should be "catch (exception const& e)" [05:16] ask me why some time [05:17] thumper: that's ugly... like "1 == x" because some people _might_ occasionally write assignment instead of comparison. [05:17] thumper: the whitespace for the &? [05:18] btw if you're going to std::cerr << e.what() then don't forget the eol. [05:18] << '\n' [05:18] const& on the RHS of the type [05:18] thumper: now now, who's being all old-school a-better-C here? [05:19] cerr flushes automatically, so explicit not needed [05:19] thumper: the const and the & have basically nothing to do with each other... the const qualifies the exception, not the & [05:19] I know clog flushes automatically, but cerr..? [05:19] jtv: we need beer and time to talk this through [05:19] Now now people. Let's keep the channel Python-friendly. [05:19] cerr yes [05:19] thumper: aye to that! [05:19] wgrant: why? [05:20] thumper: C++ is too much like Java. [05:20] * jtv screams [05:20] We were here first. [05:21] * wgrant kicks Python 2.4 to death. [05:22] wgrant: "don't kill it yet, we still need it" [05:38] spm: are you un-paniced yet? [05:38] nope [05:41] I'll go away and check back later... [05:44] thumper: oh doh, I should have noticed the const positioning [05:44] of course, its a PITA. [05:50] maxb: Running 'make check' on karmic amd64 with 2.4 has so far given me a LayerIsolationError in timeout.txt, but package-diff.txt just passed fine. I think LP might hate you. [05:50] maxb: This is all freshly downloaded and installed. [06:39] I want pizza [06:40] * thumper is thinking of Poppa's pizza [06:48] mmmmm [06:48] do not be tempting me like that [06:52] spm: reminder to re-enable pqm :) [06:52] oo. ta. will do. [06:58] Why must PQM be turned off for CPs? [07:00] the same machine is used to validate the production branch changes [07:00] wgrant: e.g. 'why can't you run two lp test suites at once on the same machine' [07:01] lifeless: Ah. I thought buildbot was all EC2, so the CP tests would be on another instance. [07:01] But that makes sense. === Ursinha is now known as Ursinha-afk [07:26] spm: are you working on this now? [07:26] poolie: bzr access? very much so. [07:26] the CP went sour in a big way [07:27] cp? [07:27] cherry pick [07:28] Ooh dear. [07:29] we've reverted - so back to where we were; but still open to the HTTP errors. :-/ [07:30] i actually really like sour cherries [07:32] Was it the rewrite stuff that was CPed? [07:32] poolie: a sincere thank you! jokes during a crisis are *always* appreciated :-) [07:32] poolie: They are good, yes. [07:32] wgrant: amonst some other bits, yes. [07:43] spm, ssh seems to still be down [07:44] poolie: yes; trying a hopefully fixed update. should be back now. [08:23] good morning [08:38] hi adeuring! [09:01] morning [09:01] Morning. [09:11] hi bigjools, hi gmb === jtv is now known as jtv-eat [09:18] Why is my postgres eating a couple of gigabytes of disk after a test run failed due to a lack of disk space? [09:18] Is it told not to clean up, or something? [09:22] autovacuum not running? [09:22] I was thinking that. [09:22] But I don't see why it wouldn't be. [09:23] * wgrant checks more carefully this time. [09:23] I've had it vanish silently on me before. [09:23] But it's been a while since that happened (might even have been back when we were on PG8.2 rather than 8.3) [09:23] I shall watch more carefully this time. [09:27] This has probably happened all five times I've run 'make check' now, but the first three times I didn't realise it was the database. [09:27] So it seems unlikely that autovacuum is going missing. [09:33] Morning === jtv-eat is now known as jtv [10:58] Morning, all. [11:24] morning thumper [11:27] hey Fly-Man-, thumper's most likely afk ... it's late Friday evening for him [11:27] mrevell: Ahh, he's the Australian one ? [11:28] mrevell: morning btw :) [11:28] Fly-Man-: Heh, New Zealand -- I think it's a capital offence to confuse the two. Morning :) [11:28] sorry thumper ;) [11:28] mrevell: I asked a question yesterday about the launchpad download [11:29] as it seems the version is still the 2.2.6 version [11:29] Fly-Man-: The LP source code? [11:29] and i'm part of the beta team [11:29] Fly-Man-: Ah, the version number that appears in the footer on edge? [11:29] and it seems the beta site is running a lower version then my local launchpad [11:29] which surprises me ... [11:29] mrevell: Yes, the source that you can get [11:30] My local version is [11:30] Launchpad 2.2.6 (r9108) [11:30] the version from edge is [11:30] edge only updates every 24 hours, and it updates from a branch that is always several hours out of date. [11:31] So yours is very probably newer. [11:31] Launchpad 2.2.6 (r9041) [11:31] wgrant: yes, but thumper also mentioned that the new 2.2.7 version should be available as download as well [11:32] but I can't seem to find that one anywhere [11:32] Fly-Man-: There's no '2.2.7' version. [11:32] It's all the same branch. [11:32] But the version number hasn't been changed yet. [11:32] Fly-Man-: The version number that shows in the footer isn't all that reliable. Usually it is but it's actually just a text string that's manually updated. [11:32] Ooo, so the version I download is the "2.2.7" ? [11:32] Fly-Man-: The version you download is whatever is the latest version [11:32] 2.2.7 only exists as a snapshot in time on the live production server [11:33] Ahh, that makes perfect sense [11:33] So, the version you download is 2.2.7 plus whatever has been committed since the 2.2.7 release. [11:33] Ahhh, that's good :) [11:34] so I don't need to perform the rocketfuel-setup every time to get the latest version [11:34] but can just pull the version with bzr [11:35] but now a question that might be a hard one .... [11:35] Fly-Man-: Or run utilities/rocketfuel-get [11:35] "How to get the code importer function to work" [11:36] and clean up the projects that I don't need in there [11:36] because thumper mentioned that the codeimporter should work [11:37] but then had to fire fight something on the site [11:37] What exactly are you trying to do? [11:37] I am trying to import the SVN trunk from a server [11:38] to see if I get the same errors that the launchpad.net gets [11:38] to analyse where it might go wrong [11:38] and also planning on the Git import [11:38] All of the Code guys are hopefully asleep, so there's probably not much help around for that right now. [11:39] abentley should be around in two or three hours [11:39] so I can match the problem and see where that might have a patch/fix that might help [11:39] Git is easy to test. [11:39] Just install bzr-git and try to check the repo out with it. [11:40] SVN is harder, because cscvs is old and confuses me. [11:41] k, bzr-git doesn't come up when I do a apt-cache search bzr [11:41] so I might not have the right repository's set [11:48] * Fly-Man- does a lightbulb above his head [11:48] See, I was right about 1 thing ... [11:48] https://code.edge.launchpad.net/~vcs-imports/opensim/svn-trunk [11:48] if I check it out with bzr svn-import url [11:49] it gives an error [11:49] when I check it out without the trunk [11:49] it's importing ... [11:56] Fly-Man-: LP doesn't use bzr-svn. [11:57] okay ... [11:57] It uses cscvs, from which you want to swiftly escape. [11:57] So in other words, cscvs does the things different [11:57] Yes. [11:57] Completely. [11:58] and a code change would be required to make it go from cscvs to bzr-svn / [11:58] Yes, but there are bigger problems with the transition. [11:59] I believe it is on the list for post-3.0 [12:01] I keep wondering why it gets those messages on the SVN [12:01] WARNING N changeset 1 [12:01] WARNING N changeset 2 [12:01] and then it just "poofs" [12:05] gmb, bigjools: So, autovacuum is running as it should, and even manually vacuuming doesn't help :( [12:06] Hrm. [12:06] o\ [12:08] 'make schema' almost cuts it back to where it started. So I'm pretty confused. === kiko-afk is now known as kiko [12:48] mrevell: I just found a simular bug like the one I have [12:48] and it seems Paul Hummer is working on that [12:49] Would it be wise to match the bug I made and put it on that bug report as well ? [12:49] Ah, that's good to hear -- he's on US mountain time so he'll be around in two or three hours [12:49] Fly-Man-: If you've already made a bug report, you can mark it as a duplicate of the one Paul's working on [12:49] k === matsubara-afk is now known as matsubara === salgado-afk is now known as salgado === adeuring1 is now known as adeuring === mrevell is now known as mrevell-lunch [14:14] wgrant: 2009-08-14 13:09:34 ERROR No mail box is configured. Please see mailbox.txt for info on how to configure one. [14:14] * Fly-Man- doesn't see a mailbox.txt file anywhere ? [14:23] kfogel: Goodafternoon kfogel [14:24] kfogel: You were gone when I was finished [14:24] but here's the page to the local setup [14:24] https://dev.launchpad.net/Running/LocalNetwork [14:26] Fly-Man-: reading now [14:26] k [14:27] Fly-Man-: is this only for machines on your local network? Would it work for machines on the WAN too? [14:28] Fly-Man-: IOW, I'm wondering if the name of this page should be "RemoteAccess" or something [14:30] Fly-Man-: the summary at the top says "This page tells you how to change the Launchpad so you can access it on your own machine." I think maybe that's too vague? After all, that's what the normal Running instructions give. Your tutorial is about something bigger: the ability to access Launchpad from a *different* machine than the one it is running on (right?). === mrevell-lunch is now known as mrevell [14:32] kfogel: It will work on a Wan as well [14:33] Fly-Man-: so, let's rename the page. It's not linked to from anywhere yet, right? [14:33] But for a WAN I would suggest using a DNS server that an register [14:33] it's only registered at the Running page [14:33] Fly-Man-: I'm sorry, I didn't understand your last sentence. [14:33] oh [14:33] linked [14:33] yes [14:33] you used "register" twice, but with different meanings :-) [14:34] sorry, Dutch ;) [14:34] heh [14:34] Fly-Man-: we can fix the Running link, no problem [14:34] RemoteAccess could be a good name for that [14:34] but then it needs a step with it for Wan usage [14:34] so, first: let's rename the page. then, if it needs any tweaks to explain difference between LAN and WAN access, maybe you can put those in? [14:34] "If you want to use it on a Wan, please make sure you can access a DNS server to setup the values" [14:34] Fly-Man-: I can rename right now and fix Running, if yuo wnt. [14:34] go ahead :) [14:34] "you want", sorry [14:35] typo [14:35] ok [14:36] Fly-Man-: all done [14:36] Fly-Man-: fixed summary bar too [14:36] k [14:36] Fly-Man-: I'll leave the WAN changes to you, since you know the material better [14:36] Well, that's the easy part ;) [14:39] kfogel: done ;) [14:40] Fly-Man-: thanks! [14:40] Yw [14:40] and now to find the people that can explain the parts that I miss [14:40] like the setting up of the cron jobs [14:40]