| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:14 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 00:14 | |
| *** rdale [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 00:14 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 00:14 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:14 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:14 | |
| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 00:20 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 258 seconds] | 00:21 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 272 seconds] | 00:21 | |
| *** rdale [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:30 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:32 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 00:32 | |
| *** genii [~quassel@ubuntu/member/genii] has quit [Write error: Connection reset by peer] | 01:43 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 01:48 | |
| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 01:48 | |
| *** rdale [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 01:48 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 01:48 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 01:49 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 01:50 | |
| *** thecorconian [4b1b2c1f@gateway/web/freenode/ip.75.27.44.31] has joined #baserock | 03:40 | |
| *** VVIBIN [~VVIBIN@202.0.77.198] has joined #baserock | 04:20 | |
| *** aananth [~caananth@74.112.167.117] has joined #baserock | 05:24 | |
| *** aananth [~caananth@74.112.167.117] has quit [Remote host closed the connection] | 07:07 | |
| *** aananth [~caananth@74.112.167.117] has joined #baserock | 07:18 | |
| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 07:35 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 07:35 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 07:35 | |
| *** rdale [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 07:35 | |
| *** violeta_ [~violeta@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 07:35 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 07:36 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 08:06 | |
| Mode #baserock +v ssam2 by ChanServ | 08:06 | |
| aananth | ssam2: I sent you an email regarding my trove deployment. Kindly reply. | 08:16 |
|---|---|---|
| ssam2 | Aananth: I shall do now | 08:16 |
| ssam2 | aananth: I can reply here, in fact | 08:18 |
| aananth | Ok | 08:19 |
| ssam2 | if your trove is running correctly then visiting it in a web browser, you'll see a list of the repos you have indexed | 08:19 |
| paulsherwood | aananth: did you manage to create your own trove? :) | 08:19 |
| ssam2 | at the bottom of that page is a link that says 'view lorry controller status' which should show info on where it is mirroring from and the progress of the mirroring | 08:19 |
| ssam2 | if there seem to be problems, the first place to check for errors is to run: `journalctl --full` | 08:20 |
| aananth | Ok sam. NTPD is failing... | 08:22 |
| ssam2 | That would suggest the Trove can't connect the network | 08:23 |
| ssam2 | I guess probably a proxy issue | 08:23 |
| aananth | Yeah. Madhu sent me some link regarding this yesterday, let me fix that. | 08:23 |
| ssam2 | actually, NTP goes on port 123 by default | 08:24 |
| ssam2 | so it could be being blocked by your firewall | 08:24 |
| ssam2 | that said, as long as you're sure the time is set correctly you can disable ntpd.service and ntpd-boot.service | 08:25 |
| ssam2 | Baserock has `date` for checking and setting time | 08:25 |
| *** petefoth [~petefoth@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 08:28 | |
| *** petefoth [~petefoth@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Remote host closed the connection] | 08:57 | |
| *** petefoth [~petefoth@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 08:57 | |
| *** mariaderidder [~maria@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 08:58 | |
| * pedroalvarez wonders if anybody has ever looked into upgrading busybox | 08:59 | |
| pedroalvarez | s/into/at/ :P | 09:00 |
| jjardon | I think we are using the latest already | 09:00 |
| pedroalvarez | jjardon: not sure, glibc requieres a patch that is IIRC in the latest version | 09:00 |
| jjardon | IIRC Kinnison updated it | 09:01 |
| jjardon | Ok, i was wrong: we are using 1.21 but 1.22.1 is available | 09:06 |
| pedroalvarez | yeah, I was revisiting the patches needed to move to glibc, and I wondered if it was better to upgrade busybox rather than patching it | 09:09 |
| pedroalvarez | but busybox chunk has a lot of changes from us | 09:10 |
| pedroalvarez | although I can always merge the latest tag | 09:10 |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:15 | |
| pedroalvarez | when moving to glibc I found a problem with lsof. It was complaining because it couldn't find "rpc/rpc.h". Upgrading it to the latest version solved the issue but I wonder if I'm missing something important | 09:17 |
| pedroalvarez | Also, in linuxfromscratch.org they say that the latest version depends on libtirpc-0.2.5, and I managed to get lsof building and running without doing anything else than upgrading to the latest version. | 09:19 |
| pedroalvarez | btw, to upgrade to the latest version I need to do this first: http://pastebin.com/a4uQTitc | 09:19 |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:23 | |
| jjardon | Yeah, rpc are not installed by default in modern versions Og glibc anymore; you can use --enable-obsolete-rpc if you needed | 09:26 |
| jjardon | About busybox; don't know the reasons of the patches buy my opinion is that the less amount of patches we carry, the better | 09:27 |
| *** jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:29 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 264 seconds] | 09:32 | |
| pedroalvarez | jjardon: wrt rpc - aha, that makes sense. I wonder why is working without installing the ti-rpc in the system | 09:32 |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:50 | |
| Mode #baserock +v ssam2 by ChanServ | 09:50 | |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:58 | |
| *** aananth [~caananth@74.112.167.117] has quit [Ping timeout: 258 seconds] | 10:02 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 264 seconds] | 10:07 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 10:13 | |
| persia | re: busybox: have those patches been sent upstream? Were any merged? | 10:13 |
| pedroalvarez | persia: as far as I could see, they were systemd units | 10:15 |
| persia | Hmm. Those probably don't belong upstream for either busybox or systemd. I wonder where they should belong. | 10:16 |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Client Quit] | 10:16 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 10:17 | |
| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 10:20 | |
| *** rdale [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] | 10:20 | |
| *** aananth [~caananth@74.112.167.117] has joined #baserock | 10:20 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 10:24 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 10:29 | |
| *** aananth [~caananth@74.112.167.117] has quit [Read error: Connection reset by peer] | 10:38 | |
| *** aananth [~caananth@74.112.167.117] has joined #baserock | 10:50 | |
| jjardon | pedroalvarez: note that libtirpc is already in stratum/nfs | 10:50 |
| pedroalvarez | jjardon: I know, but that is not present in the devel system | 10:51 |
| ssam2 | it could be, I think | 10:52 |
| jjardon | ssam2: thanks for the coreutils review! seems tcpwrapper are not really needed anymore: https://www.archlinux.org/news/dropping-tcp_wrappers-support/ so I will try to get rid of them | 10:52 |
| ssam2 | cool, yeah I don't think we actually use it in Trove / distbuild for anything | 10:52 |
| ssam2 | it was just a required build dep for some NFS component at the time | 10:52 |
| pedroalvarez | ssam2: what do you mean exactly with "it could be" | 10:54 |
| * pedroalvarez is confused | 10:54 | |
| ssam2 | you could add it there, if you need | 10:54 |
| *** thecorconian [4b1b2c1f@gateway/web/freenode/ip.75.27.44.31] has quit [Quit: Page closed] | 11:04 | |
| *** thecorconian1 [~jte@75-27-44-31.lightspeed.orpkil.sbcglobal.net] has joined #baserock | 11:10 | |
| *** thecorconian1 [~jte@75-27-44-31.lightspeed.orpkil.sbcglobal.net] has quit [] | 11:10 | |
| *** petefotheringham [~petefothe@access.ducie-dc1.codethink.co.uk] has quit [Quit: leaving] | 11:11 | |
| *** petefotheringham [~petefothe@access.ducie-dc1.codethink.co.uk] has joined #baserock | 11:11 | |
| petefotheringham is now known as petefoth1 | 11:12 | |
| jjardon | ssam2: build system built fine with coreutils + patch in baserock/jjardon/tcpwrappers :) | 11:21 |
| jjardon | ssam2: Do you want me to test any other system? | 11:21 |
| ssam2 | should be OK | 11:22 |
| ssam2 | I might have a go at deploying a build system and checking NFS still works | 11:22 |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 11:35 | |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 11:35 | |
| pedroalvarez | ha! I just figured out that I *can't* put a init script in /root | 11:39 |
| persia | heh | 11:40 |
| pedroalvarez | because /root is a btrfs subvolume!!! | 11:40 |
| pedroalvarez | /me sighs | 11:40 |
| * pedroalvarez too | 11:40 | |
| franred | hehe | 11:42 |
| pedroalvarez | jjardon: are you updating patch? | 11:49 |
| pedroalvarez | upgrading even | 11:49 |
| jjardon | pedroalvarez: in my coreutils branch, yes | 11:50 |
| pedroalvarez | jjardon: there was already a branch for that (baserock/v2.7.1). I was using that in my glibc branch | 11:51 |
| jjardon | pedroalvarez: yeah, Im using that one as well | 11:52 |
| pedroalvarez | great | 11:54 |
| aananth | ssam2: I could see trove server from any browser on any machines with in our local network. But it says "no repositories found" | 11:57 |
| aananth | paul: Sorry I missed your question. The answer is "yes". But I need to fix the ntpd issue and make my trove server to fetch git repos from baserock git. | 12:01 |
| pedroalvarez | aananth: at the bottom of the page there is a link which says "View Lorry Controller Status" | 12:03 |
| pedroalvarez | aananth: if you click in that link, you go to the lorry controller status page | 12:04 |
| pedroalvarez | that page has to be similar to this one: http://85.199.252.93/lc-status.html | 12:04 |
| aananth | Ok pedroalvarez. Let me check and come back. | 12:06 |
| aananth | pedroalvarez: Please find the text pasted in http://fpaste.org/146796/75733814/ | 12:08 |
| aananth | Could you explain me what that means? | 12:09 |
| ssam2 | Hi aananth | 12:09 |
| ssam2 | I see that it has 'git.baserock.org' in the list of configured troves | 12:09 |
| ssam2 | actually, I know what the problem is. Sorry, there's a step I failed to tell you about! | 12:10 |
| ssam2 | your Trove's 'lorry' key needs an account to be created on git.baserock.org | 12:10 |
| ssam2 | if you can look inside the Trove for /etc/trove/lorry.key.pub and send it to me, I can create an account | 12:11 |
| pedroalvarez | ssam2: are your sure? | 12:11 |
| Kinnison | ssam2: can they not use http? | 12:11 |
| aananth | Oh! I will send that key now. | 12:11 |
| ssam2 | Kinnison: perhaps, how can we change the Trove to use http ? | 12:11 |
| Kinnison | in the lorry controller config | 12:11 |
| Kinnison | in the trove stanza | 12:11 |
| ssam2 | OK | 12:11 |
| pedroalvarez | Is httpby default, no? | 12:11 |
| Kinnison | I think it's "protocol": "http" | 12:11 |
| Kinnison | pedroalvarez: I don't recall | 12:12 |
| ssam2 | it should be, but clearly it isn't | 12:12 |
| ssam2 | aananth: OK, so rather than sending the key you should be able to edit a config file | 12:12 |
| pedroalvarez | Maybe the ls is taking time | 12:12 |
| ssam2 | when I deployed the ct-training trove I had to add a key to the upstream trove | 12:12 |
| ssam2 | I forgot that with HTTP you don't need to do that | 12:13 |
| ssam2 | but clearly it's not the default | 12:13 |
| ssam2 | aananth: if you do 'git clone ssh://git@TROVE_HOST/TROVE_ID/local-config/lorries.git' you'll get a local clone of the lorries configuration repo | 12:13 |
| aananth | ssam2: I sent the public key to your email id. | 12:14 |
| ssam2 | ok, thanks. I'll add the key so that you can get up and running | 12:14 |
| aananth | ssam2: What to do after cloning lorries.git? | 12:15 |
| ssam2 | seems I was wrong about the default value for 'protocol' | 12:16 |
| ssam2 | it is 'http' in the Trove I created on Tuesday | 12:16 |
| ssam2 | aananth: if you cloned lorries.git successfully, can you paste the 'lorry-controller.conf' file somewhere so we can see it? | 12:17 |
| ssam2 | that's the file that configures how the mirroring is done | 12:18 |
| ssam2 | to clone the lorries.git repo you might need to add yourself to the correct group first so you can access it | 12:19 |
| ssam2 | if you do 'ssh git@TROVE group adduser local-config-writers USERNAME' it'll give you read and write permissions for the lorries repo | 12:19 |
| ssam2 | Trove has fine-grained access-control, as we said :) | 12:20 |
| ssam2 | Kinnison, pedroalvarez: I've deleted the key I added for the ct-training-trove from git.baserock.org to see if I can see mirror-over-HTTP working in action | 12:22 |
| pedroalvarez | ssam2: the baserock-clone trove doesn't have the keys in git.baserock.org | 12:23 |
| ssam2 | right | 12:23 |
| ssam2 | I guess I was impatient and lacking in knowledge | 12:23 |
| pedroalvarez | maybe something has changed | 12:23 |
| pedroalvarez | :/ | 12:23 |
| ssam2 | certainly, aananth is not seeing any repos yet :( | 12:23 |
| pedroalvarez | how can we do a 'ls' in gitano using http? | 12:24 |
| Kinnison | there's a gitano-command.cgi which straycat wrote \o/ | 12:25 |
| aananth | ssam2: I think I found an issue which could be a reason. | 12:25 |
| aananth | I need to install corkscrew and configure git, ssh to work behind the proxy in trove server. | 12:25 |
| aananth | I have not done this step. | 12:25 |
| aananth | Let me try that. | 12:26 |
| Kinnison | Oh dear | 12:27 |
| Kinnison | troves can be configured with proxy access details | 12:27 |
| Kinnison | but I don't think they can corkscrew per-se | 12:27 |
| pedroalvarez | Kinnison: thanks for the hint :) http://git.baserock.org/gitano-command.cgi?cmd=ls | 12:27 |
| ssam2 | aananth: it should be cloning over HTTP, so it shouldn't need corkscrew I think | 12:28 |
| ssam2 | it should just need access on port 80 | 12:28 |
| ssam2 | we have set up a Trove behind a firewall that prevented internet traffic on all ports except 80 | 12:28 |
| pedroalvarez | ssam2: indeed, and if that was the issue, at least the trove has to manage to get the remote repositories before cloning | 12:30 |
| pedroalvarez | that's why I was checking that 'ls' works in g.b.o | 12:30 |
| aananth | ssam2, I just tried cloning my project in github, inside the trove server :), but I get this error "Couldn't resolve host 'github.com'". I used git clone https://github.com/... | 12:33 |
| ssam2 | in my trove, I see a lot of this in the journal: | 12:33 |
| ssam2 | aananth: that's a good idea as a way of testing the connection | 12:34 |
| ssam2 | aananth: seems that something is wrong with the networking in the Trove | 12:34 |
| ssam2 | does 'ping 8.8.8.8' work ? | 12:34 |
| ssam2 | if so, it has network but not DNS, I think | 12:34 |
| aananth | It works, here is the output: 64 bytes from 8.8.8.8: seq=1 ttl=40 time=274.663 ms | 12:35 |
| ssam2 | ok, so network works but not DNS | 12:35 |
| ssam2 | what do you see in the file /etc/resolv.conf ? | 12:35 |
| aananth | I get the one in the link: http://fpaste.org/146810/75900514/ | 12:36 |
| aananth | Let me try adding 8.8.8.8 to the resolv.conf and try. | 12:37 |
| ssam2 | good idea | 12:37 |
| pedroalvarez | is not resolv.conf going to be regenerated? | 12:37 |
| aananth | Only on next boot, right? | 12:38 |
| ssam2 | yes. it's good as a test, to see if the problem is that none of the DNS servers currently listed are working | 12:38 |
| *** VVIBIN [~VVIBIN@202.0.77.198] has quit [Ping timeout: 264 seconds] | 12:39 | |
| aananth | ssam2: PING is with name seems to be disabled in our company. Even that did not work on my PC. | 12:45 |
| jjardon | ssam2: any idea why nfsv4 support got disabled? | 12:45 |
| ssam2 | jjardon: I think because at the time it did't work as well as nfsv3, and disabling it caused nfsv3 to be the default | 12:45 |
| aananth | Then, I used wget, without any proxy setting (http_proxy) inside trove server. It did not work or got "bad address" error. | 12:45 |
| ssam2 | jjardon: I don't if nfsv4 has improved, but I have an impression from a couple of years ago that it's quite bussy | 12:46 |
| ssam2 | *buggy | 12:46 |
| aananth | Then, I configured http_proxy environment variable and did a wget, it worked. | 12:46 |
| ssam2 | aananth: aha ! | 12:46 |
| aananth | sounds to me like a proxy issue. | 12:46 |
| ssam2 | jjardon: also, the policy for Baserock is that you need +2 before merging, not +1 | 12:46 |
| ssam2 | bear that in mind in future at least :) | 12:47 |
| ssam2 | aananth: yes | 12:47 |
| ssam2 | aananth: did you manage to clone local-config/lorries.git from your trove? | 12:47 |
| aananth | No, that again did not work | 12:48 |
| ssam2 | was it a permissions error or a networking error? | 12:48 |
| aananth | ssh: Could not resolve hostname TROVE_HOST: Name or service not known. | 12:48 |
| abdul_ | ssam2: getting error while building wandboard image in our target "ERROR: In staging area /src/tmp/staging/tmpNbVXt7: running command 'sh -c make' failed." | 12:49 |
| ssam2 | aananth: replace TROVE_HOST with the actual IP or hostname of your trove | 12:49 |
| aananth | sorry :) | 12:49 |
| ssam2 | abdul_: ok, does it give you the build output too? if so, paste that to fpaste.org and I'll see if I can see the problem | 12:49 |
| abdul_ | ssam2: http://fpaste.org/146814/ | 12:53 |
| aananth | ssam2: I cloned it into my PC, but got errors. See http://fpaste.org/146817/14760297/ | 12:57 |
| ssam2 | OK, that means you don't have the right SSH key available on your PC | 12:58 |
| ssam2 | aananth: you can run `ssh-add --l` to see what keys you have currently available on a machine | 12:58 |
| ssam2 | sorry, `ssh-add -l` | 12:58 |
| ssam2 | and to add a new one to your SSH agent so that it can be used, you need `ssh-add /path/to/key` | 12:59 |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Quit] | 12:59 | |
| ssam2 | since you created the Trove, you created the 'trove-admin' key | 12:59 |
| aananth | ok | 13:00 |
| ssam2 | that's the one you need now to authenticate yourself | 13:00 |
| ssam2 | abdul_: that problem is very special, I've never seen it before! | 13:00 |
| ssam2 | abdul_: is this building on NFS by any chance ? | 13:00 |
| abdul_ | ssam2: yes | 13:01 |
| aananth | Ok I understand why I am not able to clone the git from my trove server. Is there any relation with the trove server is unable to fetch repos? | 13:01 |
| ssam2 | aananth: no, I think that the Trove server can't fetch repos because you need to add the proxy configuration to 'lorry-controller.conf' | 13:01 |
| ssam2 | you can find that file in local-config/lorries.git, once you can get at local-config/lorries.git :-) | 13:02 |
| ssam2 | abdul_: we don't really test building on NFS, so there could be some problem in the Makefiles for XML-Parser that don't normally see | 13:02 |
| aananth | ssam2: Thanks I understand. | 13:03 |
| abdul_ | ssam2: okay. but in our hardware we dont have enough space to do baserock build. so opted for NFS | 13:04 |
| ssam2 | abdul_: OK. if you want to try and investigate the failure, you can do 'chroot /src/tmp/failed/tmpNbVXt7' | 13:04 |
| ssam2 | (i worked that path out from the last line of the log file you sent) | 13:05 |
| ssam2 | then you'll be in the build environment Morph is using for that chunk | 13:05 |
| ssam2 | there'll be a directory called something like /XML-Parser.build where the source for XML-Parser is | 13:05 |
| ssam2 | you can try running 'make' manually etc. and see if you can debug it | 13:05 |
| ssam2 | I hope to get a chance later to try building on NFS myself | 13:06 |
| *** thecorconian [~jte@75-27-44-31.lightspeed.orpkil.sbcglobal.net] has joined #baserock | 13:07 | |
| abdul_ | ssam2: okay i will try and let you know | 13:08 |
| ssam2 | alternately, if you can find an external hard disk I think the problem will go away | 13:11 |
| abdul_ | ssam2: http://fpaste.org/146821/ | 13:11 |
| abdul_ | ssam2: make is working when i do it manually | 13:11 |
| abdul_ | ssam2: how can go back and give morph build again | 13:12 |
| pedroalvarez | abdul_: type `exit` to exit from the chroot | 13:13 |
| abdul_ | ssam2: thanks sam | 13:14 |
| radiofree | it looks like the build for that returns make: *** [Makefile] Error 1 as part of the build | 13:14 |
| radiofree | you have to run make twice, morph is treating that as a build error? | 13:14 |
| abdul_ | okay | 13:14 |
| ssam2 | radiofree: perhaps, yeah | 13:16 |
| ssam2 | radiofree: it may be a timestamps issue | 13:16 |
| radiofree | ==> Your Makefile has been rebuilt. <==\n==> Please rerun the make command. <==\nfalse\nmake: *** [Makefile] Error 1 | 13:16 |
| radiofree | however in the manual build just running make again after that works | 13:16 |
| ssam2 | radiofree: makes sense | 13:17 |
| ssam2 | radiofree: but we always build XML-Parser and we don't normally have this problem | 13:17 |
| ssam2 | it might be a good enough workaround to change the build instructions to 'make || make' though :) | 13:17 |
| aananth | ssam2: I have sent you an email asking clarification w.r.t key generation. Kindly reply. | 13:21 |
| ssam2 | aananth: done | 13:29 |
| ssam2 | aananth: this is also documented here: http://wiki.baserock.org/guides/configuring-a-trove/ | 13:30 |
| abdul_ | again same problem in xml-parser | 13:30 |
| ssam2 | although it's really lacking quite a lot of info | 13:30 |
| ssam2 | abdul_: OK | 13:30 |
| ssam2 | abdul_: you could try radiofree's suggestion | 13:30 |
| ssam2 | currently XML-Parser is using the default build commands | 13:30 |
| ssam2 | you could add a chunk morphology for it which overrides them | 13:31 |
| ssam2 | so instead of running `make`, it runs `make || make` | 13:31 |
| ssam2 | so that if `make` fails the first time, it'll run it again instead of raising an error | 13:31 |
| ssam2 | this is a bit of a hack :) but it's worth a try | 13:31 |
| ssam2 | do you feel confident to add a chunk morph or do you want me to guide you through it ? | 13:31 |
| abdul_ | okay i will give a try..interesting !!! | 13:33 |
| * paulsherwood has missed backscroll... is this a new/different version of XML-Parser? | 13:33 | |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 264 seconds] | 13:33 | |
| ssam2 | paulsherwood: no, abdul_ is using NFS for /src, so he can build it on a small embedded device without an external HD | 13:33 |
| ssam2 | so it's probably some kind of timestamps / timing issue | 13:34 |
| * pedroalvarez ponders enabling "--enable-obsolete-rpc" in glibc after realising that libtirpc doesn't build with glibc | 13:34 | |
| aananth | ssam2: thanks. In case of different trove-admin, shouldn't I regenerate admin's public and private key again? | 13:38 |
| ssam2 | aananth: you mean, if you wanted to make someone else the admin of the Trove ? | 13:39 |
| ssam2 | aananth: i'd suggest just giving them the public and private trove-admin keys | 13:39 |
| ssam2 | it'd be possible to generate new keys and replace them, using 'ssh git@.. sshkey del ..' and 'ssh git@... sshkey add ..' | 13:40 |
| aananth | No, I used "trove-admin" in ssh-keygen command instead of "caananth" which is my ID. Hence I need to regenerate the keys. Not required? | 13:40 |
| aananth | Ok | 13:40 |
| aananth | I got it. | 13:40 |
| ssam2 | aananth: think of the trove-admin as a separate, special role | 13:41 |
| aananth | Thanks ssam2. I understood your email better now. Sorry, its friday evening :) and my mind is already tired with full weeks work load :). Let me do that and let you know. | 13:43 |
| ssam2 | aananth: trove is complex, I think you're doing really well to have one up and running already | 13:44 |
| ssam2 | we'll still be here on Monday, you should make sure to enjoy your Friday evening ! | 13:45 |
| jjardon | pedroalvarez: enable it , seems its needed to rebuild glibc | 13:47 |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 13:48 | |
| jjardon | Also Arch and fedora enable it as well so seems to be the correct thing to do | 13:51 |
| pedroalvarez | jjardon: hm... i shall give up | 13:58 |
| jjardon | pedroalvarez: never! ;) what is the problem now? | 13:59 |
| pedroalvarez | jjardon: you told me to give up enabling "--enable-obsolete-rpc" | 14:00 |
| pedroalvarez | I was trying to figure out how others build ti-rpc | 14:00 |
| pedroalvarez | using patches from fedora, looking at the patches of debian, etc | 14:00 |
| jjardon | pedroalvarez: oh yeah, I though you were giving up on building glibc | 14:01 |
| pedroalvarez | never! | 14:01 |
| paulsherwood | ssam2: max-jobs? | 14:02 |
| ssam2 | paulsherwood: for xml-parser? I don't think that's the problem, but it might help | 14:03 |
| jjardon | pedroalvarez :) Also you should finish soon so you can take a look to my coreutils branch: I need it for systemd 217 ;) | 14:03 |
| pedroalvarez | after this I'm going to update gcc | 14:06 |
| paulsherwood | that will be a big rebuild :) | 14:08 |
| pedroalvarez | slightly bigger than the one caused by moving to glibc | 14:10 |
| pedroalvarez | and I think that these upgrades are important | 14:13 |
| jjardon | pedroalvarez: they are. Even more for arm | 14:36 |
| pedroalvarez | jjardon: so is your coreutils branch ready? | 14:39 |
| jjardon | pedroalvarez: it is | 14:40 |
| jjardon | I build and run a build and a genivi-baseline systems with it | 14:41 |
| *** madhu [~madhu@202.0.77.198] has quit [Quit: Leaving] | 14:41 | |
| jjardon | s/I build/I built/ | 14:42 |
| paulsherwood | violeta_: did you or anyone manage to establish whether tegra can run in big endian mode? | 14:58 |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 15:01 | |
| paulsherwood | ridgerunner: ^^ ? | 15:01 |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Client Quit] | 15:05 | |
| rjek | paulsherwood: The ARM part running in BE is part of the standard that they must implement. | 15:05 |
| rjek | paulsherwood: My understanding is that the problem is if the drives can cope or if they need patching to be endian-agnostic. | 15:06 |
| rjek | drivers | 15:06 |
| rjek | (ie, if they need to byte-swap data written to peripherals) | 15:06 |
| paulsherwood | right thanks | 15:06 |
| * rjek is not an authoritative source, however. | 15:07 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 15:08 | |
| petefoth | do we need to publicise the project policies that have been discussed on the ML? The one I recall is ‘who gets committer access?” Maybe there were others? Should they be on the wiki? | 15:21 |
| ssam2 | Publicise meaning 'put them on the wiki' ? | 15:22 |
| pedroalvarez | I assume so | 15:22 |
| ssam2 | I think that's good, if they can be summarised sufficiently | 15:22 |
| ssam2 | petefoth: the training this week highlighted a couple of places the docs could do with improving, are you interested in me listing them? | 15:22 |
| persia | Didn't we already do that? | 15:23 |
| pedroalvarez | yeah, I think we did | 15:23 |
| persia | http://wiki.baserock.org/policies/ | 15:25 |
| pedroalvarez | and really well summarised | 15:25 |
| persia | It helps that the policy changes went through the code-review process on the patches, so lots of dicussion to get the wording right. | 15:26 |
| * persia wonders a bit why the large # got approved, but isn't concerned enough to submit a policy patch candidate. | 15:27 | |
| ssam2 | I thought we were strongly pro-# | 15:27 |
| persia | Apparently so. Change was merged by paulsherwood, presumably after review. I just had failed to notice I was asserting a pro-# position when I gave my +1 on policy. | 15:28 |
| pedroalvarez | I'll remove it | 15:28 |
| petefoth | persia: we don’t do patch reviews for wiki changes I’ll get rid of the rogue # | 15:28 |
| persia | petefoth: We *do* do patch reviews for wiki changes to the policy page (see the top of the policy page) | 15:29 |
| persia | As far as I'm concerned, anything else is fair game. | 15:29 |
| pedroalvarez | wow, I missed that bit | 15:29 |
| persia | (and honestly, it's probably safe to do IRC review for the # change, as with any trivial change) | 15:29 |
| petefoth | persia: OK I missed it too (though being pedantic it only says that changes to ‘ploicies’ are subject to review, not the plicy page :) | 15:30 |
| persia | heh, you're right. That's my fault for writing unclear policy :) | 15:30 |
| persia | (and so you can work around it within the text of the policy if you prefer) | 15:31 |
| petefoth | persia: I’ll change that. Oh, wait….. | 15:31 |
| pedroalvarez | I'd put that *important* bit in a highlighted note | 15:31 |
| petefoth | I have made some changes to the policies wiki page http://wiki.baserock.org/policies/. Please will someone review the changes? | 15:34 |
| petefoth | http://source.baserock.branchable.com/?p=source.git;a=commitdiff;h=4c37a4513a044e16b6f13e19be1471fbccae6530 | 15:34 |
| petefoth | Any objections if I make the Policy page a bit more visible (by putting a link to it in the ‘Community’ section of the sidebar? | 15:35 |
| ssam2 | sounds good to me | 15:36 |
| pedroalvarez | go ahead | 15:36 |
| * pedroalvarez drops the patch to create the highlighted note | 15:37 | |
| pedroalvarez | I should learn to type faster | 15:37 |
| petefoth | pedroalvarez: it’s hard to beat ‘edit in place’ for speed :) | 15:37 |
| paulsherwood | review of my change to the policy page happened on irc iirc | 15:38 |
| paulsherwood | (ie i screwed up the implementation of a discussed change) | 15:38 |
| pedroalvarez | paulsherwood: so do you want a jetson running in big endiian? | 15:40 |
| paulsherwood | yes. i even asked folks to do it, ages ago :) | 15:41 |
| pedroalvarez | paulsherwood: did anybody say "this is impossible" or "it's going to take a while" ? | 15:41 |
| paulsherwood | yes, someone says it's impossible. | 15:42 |
| paulsherwood | hence, now we *have* to try :) | 15:42 |
| pedroalvarez | aha! :) | 15:42 |
| pedroalvarez | I used to have some hardware running baserock in big endian.. now I don't know | 15:44 |
| radiofree | http://wiki.baserock.org/arm-big-endian/ | 15:44 |
| radiofree | ben boiled it down for me at the pub, essentially it's i) build a big endian kernel ii) boot a big endian rootfs with it | 15:44 |
| radiofree | it's that easy, if you're ben | 15:45 |
| pedroalvarez | yeah! easy like that :) | 15:46 |
| pedroalvarez | but if someone thinks that it's impossible,then maybe there are more implications | 15:47 |
| radiofree | oh yeah there was a big "if the hardware supports it" bit | 15:47 |
| persia | paulsherwood: I thought it was in the thread about maintainers, where I proposed a ludicrously complicated scheme, and ssam2 suggested the model we use now. | 15:50 |
| paulsherwood | persia: you may be right. my memory is soso | 16:16 |
| aananth | ssam2: where can I read proxy settings inside trove vm? | 17:24 |
| ssam2 | aananth: what do you mean? | 17:24 |
| ssam2 | the proxy settings that are set in lorry-controller.conf in the local-config/lorries.git repo are just for the importer process | 17:25 |
| aananth | ssam2: I configured the git proxy and ssh proxy on the vm hosting trove server. I need to find where the http proxy settings are stored. | 17:25 |
| ssam2 | I'm a little confused, sorry | 17:26 |
| aananth | no problem :) | 17:26 |
| ssam2 | what do you mean when you say 'git proxy' ? What did you need to do on the VM host to set one up? | 17:27 |
| aananth | ssam2: we create a git-proxy.sh file where we call or exec corkscrew to tunnel through our proxy server for every git command. | 17:29 |
| aananth | Similarly there is a setup for ssh | 17:29 |
| ssam2 | ah, OK | 17:30 |
| aananth | I can send a pdf file explaining the details. | 17:30 |
| ssam2 | do all your connections to the Trove have to go via your proxy ? | 17:30 |
| ssam2 | I would have thought that the proxy would only be between your company, and the internet | 17:30 |
| ssam2 | so as long as the Trove is inside your company network, there'd be no need for a proxy | 17:30 |
| ssam2 | and all you'd need would be to set the appropriate HTTP proxy settings in lorry-controller.conf in local-config/lorries.git, for the mirroring of git.baserock.org | 17:31 |
| ssam2 | I don't think I explained this clearly before, I apologise for any confusion | 17:32 |
| *** jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 17:32 | |
| *** dutch [~william@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Quit] | 17:34 | |
| aananth | Ok. I am just trying different options. | 17:34 |
| ssam2 | ok! | 17:35 |
| aananth | ssam2: I deployed another trove vm on same machine, I forgot to add proxy.conf when I created it. Now I am adding it, is this path OK "/home/lorry/confgit/proxy.conf" | 17:40 |
| ssam2 | aananth: no, it needs to go in the lorry-controller.conf file in the local-config/lorries.git repo | 17:40 |
| ssam2 | it's described here: http://wiki.baserock.org/guides/configuring-a-trove/ | 17:40 |
| ssam2 | aananth: hmm, I wonder if adding it in the confgit folder directly will be OK | 17:41 |
| ssam2 | it's best to add the proxy.conf file to the lorries.git repo, commit it, and push | 17:41 |
| ssam2 | but actually, /home/lorry/confgit IS that repo | 17:42 |
| ssam2 | so if you want to just add it in there from the commandline, I guess you can :) | 17:42 |
| ssam2 | be sure to commit, though, so other users can see it if they clone the lorries.git repo | 17:42 |
| ssam2 | sorry, I hadn't realised that it could be done in that way | 17:43 |
| aananth | sam: I committed it. Should I re-boot or the server will pick the configs? | 17:46 |
| ssam2 | i'm not sure. | 17:46 |
| ssam2 | may as well reboot :) | 17:47 |
| aananth | ssam: Any problem you see in this "Oct 31 23:20:28 vtsc-trove sshd[2305]: reverse mapping checking getaddrinfo for vtsc-trove [::1] failed - POSSIBLE BREAK-IN ATTEMPT!" | 17:54 |
| ssam2 | I see that in my Trove too | 17:54 |
| ssam2 | nothing to worry about I think | 17:54 |
| aananth | Ok. How about this? "Oct 31 23:19:27 vtsc-trove lighttpd[194]: 2014-10-31 23:19:27: (mod_fastcgi.c.2673) FastCGI-stderr: GitanoCommandFailure: Failed to run "ls" on Gitano" | 17:56 |
| ssam2 | hmm, that does sound bad | 17:56 |
| ssam2 | I'm afraid this is quite outside my area of expertise | 17:57 |
| ssam2 | I've not worked on Trove much, so it may be better to wait until next week to look at this problem when the Trove experts are back in the office | 17:57 |
| ssam2 | could you paste the lorry-controller.conf file ? | 17:57 |
| aananth | I will send more lines from log around that point. | 17:57 |
| ssam2 | more lines of log would be good, too | 17:58 |
| *** mariaderidder [~maria@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat] | 17:58 | |
| aananth | ssam2: Log is available in http://fpaste.org/146927/47783981/ | 17:59 |
| ssam2 | aananth: ok, it's getting 'Name or service not known' still | 18:00 |
| aananth | ssam2: Have a look at my lorry-controller.conf http://fpaste.org/146930/78559141/. Sounds like I missed to type https username password. | 18:02 |
| ssam2 | the 'protocol' field is correct | 18:06 |
| ssam2 | did you do 'git add' of the proxy.conf and 'git commit' ? | 18:07 |
| aananth | ssam2: I think adding from commandline within VM is not accepted. | 18:08 |
| ssam2 | it could be a permissions thing | 18:09 |
| aananth | I was able to type committ message and commit it, but now they dont exit. | 18:09 |
| ssam2 | check all the files are still owned by 'lorry' user and 'lorry' group | 18:09 |
| ssam2 | I'm going to have to go now, sorry | 18:10 |
| ssam2 | I'll be back Monday though, I'll be happy to continue looking through this with you | 18:10 |
| ssam2 | and hopefully I can work on making this process easier in future! | 18:10 |
| aananth | Ok Sam. | 18:11 |
| *** rdale_ [~quassel@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 272 seconds] | 18:11 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 18:12 | |
| *** aananth [~caananth@74.112.167.117] has quit [Quit: Leaving] | 18:12 | |
| *** tiagogomes [~tiagogome@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 240 seconds] | 18:20 | |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 18:43 | |
| *** abdul__ [uid49809@gateway/web/irccloud.com/x-zmoxwslrzajdqazl] has quit [Ping timeout: 272 seconds] | 19:12 | |
| *** abdul__ [uid49809@gateway/web/irccloud.com/x-xkjuupqnaeocbudn] has joined #baserock | 19:12 | |
| jjardon | mmm, seems nobody is building GNOME in a wayland-only system | 22:53 |
| * jjardon cleaning x11 deps from several modules | 22:53 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!