| *** bashrc_ [~motters@host109-156-188-158.range109-156.btcentralplus.com] has quit [Quit: Lost terminal] | 00:04 | |
| *** bashrc [~motters@host109-156-188-158.range109-156.btcentralplus.com] has joined #baserock | 08:09 | |
| *** tiagogomes [~tiagogome@host-92-25-187-78.as13285.net] has joined #baserock | 08:53 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:04 | |
| Mode #baserock +v ssam2 by ChanServ | 09:04 | |
| ssam2 | Since we deployed the 'firehose' machine before Christmas, it has had 86901 attempts to crack the root password | 09:21 |
|---|---|---|
| ssam2 | I'm very glad Baserock defaults to not setting a root password! | 09:21 |
| ssam2 | there's actually no need to give this machine a public IP at all, it has one right now just for easier debugging | 09:21 |
| ssam2 | seems that we forgot to actually enable the firehose.timer unit, though, so it didn't actually do anything over xmas | 09:23 |
| paulsherwood | cool :) | 09:27 |
| paulsherwood | i notice the masons are not finding any connection? | 09:28 |
| ssam2 | that's from 29th/30th Dec ... status page is misleading | 09:28 |
| ssam2 | http://testgerrit.baserock.org:8080/#/c/81/ -- a candidate branch with the latest commit of Linux ! | 09:29 |
| ssam2 | and a bunch of other changes, strangely | 09:29 |
| ssam2 | probably stuff that was committed to definitions.git since the last time firehose ran ... | 09:30 |
| paulsherwood | yup - sounds like a bug - fh should always test off master, no? | 09:32 |
| paulsherwood | or specified startpoint, at least? | 09:33 |
| ssam2 | that's a bug, I think it should be producing a commit that only changes the ref field for Linux | 09:34 |
| ssam2 | I shall note this when I get to reviewing it I guess | 09:34 |
| * paulsherwood wonders what all the | symbols are for in morph logs these days | 09:44 | |
| *** Krin [~mikesmith@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:52 | |
| ssam2 | paulsherwood: wow, those are weird | 09:56 |
| ssam2 | I never noticed before | 09:56 |
| ssam2 | you mean stuff like `2014-12-18 16:00:00 DEBUG [systems/devel-system-x86_64-chroot.morph]# g | i | t | | r | e | v | - | p | a | r | s | e | | - | - | v | e | r | i | f | y | | ' | e | d | d | 1 | 8 | a | 7 | 7 | 9 | 7 | 3 | d | 8 | c | d | 1 | 2 | b | 0 | 9 | b | c | 6 | e | 3 | a | c | 0 | 6 | f | e | c | d | 7 | 2 | a | 7 | e | 4 | 5 | ^ | { | c | o | m | m | i | t | } | '` ? | 09:56 |
| ssam2 | hah, that's my fault actually | 09:57 |
| tiagogomes | sysroot deployment is missing in morph deploy documentation | 10:16 |
| ssam2 | tiagogomes: the deploy docs are still a work in progress | 10:34 |
| ssam2 | do you need help understanding it? | 10:34 |
| tiagogomes | ssam2 not for that one, because it doesn't do much :) | 10:38 |
| tiagogomes | it seems a bit dangerous though, as it will delete the contents of the directory where the system is going to be installed. Maybe it was better to fail if the destination dir is not empty | 10:44 |
| ssam2 | tiagogomes: perhaps, yeah | 10:48 |
| ssam2 | when run by Morph the directory will always be a new, empty directory in /tmp | 10:48 |
| ssam2 | it's always good minimise the number of ways users can unexpectedly delete files, though ! | 10:48 |
| tiagogomes | will it be /tmp? I though that the destination dir will be the one pointed by the value of 'location' when 'type' is 'sysroot' | 10:50 |
| ssam2 | tiagogomes: oh, good point! | 10:56 |
| ssam2 | $1 will be the dir in /tmp, $2 will be the 'location' field | 10:57 |
| ssam2 | so yeah, definitely better to warn if it's not empty, rather than deleting the contents, I think ... | 10:57 |
| ssam2 | do you have time to make a patch ? | 10:57 |
| tiagogomes | yes | 11:00 |
| ssam2 | awesome! | 11:02 |
| tiagogomes | I am curious about this, why `find "$1" -maxdepth 1 -mindepth 1 -exec mv {} "$2/." +` instead of `mv "$1"/* "$2"` | 11:03 |
| ssam2 | don't know off hand, I think richard_maw wrote that | 11:04 |
| ssam2 | may be to preserve attributes, uids etc. ? Although I'd have thought `mv` did that anyway | 11:04 |
| tiagogomes | well, the former is is using mv as well | 11:05 |
| ssam2 | right | 11:07 |
| ssam2 | I'd be fine with changing it to `mv`, if there's no explanation of why that more complex command is being used | 11:08 |
| tiagogomes | I think that it could be because find will be faster than expanding the wild cards | 11:10 |
| *** bashrc_ [~motters@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 11:12 | |
| ssam2 | that makes sense | 11:12 |
| ssam2 | maybe add a comment then | 11:12 |
| * ssam2 looks forward to seeing 'ERROR: Some copyright years need fixing' regularly from morph's test suite for the next couple of months | 11:16 | |
| bashrc_ | on copyright headers I don't know whether you're supposed to have date ranges, or just the latest year | 11:25 |
| bashrc_ is now known as bashrc2 | 11:25 | |
| ssam2 | neither do I. | 11:26 |
| Kinnison | Copyright headers should list every year that a change was made | 11:29 |
| Kinnison | you can condense sequential years into a range | 11:29 |
| Kinnison | So you might have Copyright 2011,2013-2015 | 11:29 |
| Kinnison | fr.ex. | 11:29 |
| bashrc2 | ok. Thanks for clearing up a longstanding confusion | 11:30 |
| Kinnison | http://stackoverflow.com/questions/3487007/when-to-update-the-year-in-open-source-copyright-notice | 11:32 |
| Kinnison | that has some good answers on it | 11:32 |
| Kinnison | (top hit for 'copyright years in source code' on my google bubble) | 11:32 |
| bashrc2 | Once lets-encrypt is fully operational I expect that there will be no reason not to have a cert on baserock.org | 11:44 |
| paulsherwood | ssam2: i would more look forward to the removal of that test, since it is a waste of folks' time | 11:53 |
| paulsherwood | ssam2: i've +2 your log change | 12:23 |
| paulsherwood | is there an easy way to include the output of (successful) build commands in the log? | 12:24 |
| ssam2 | paulsherwood: thanks | 12:27 |
| ssam2 | paulsherwood: that's possible, but the log files would be enourmous | 12:27 |
| ssam2 | I think we should provide an option for writing them to stdout, though | 12:28 |
| ssam2 | making '--verbose' cause build output to be written to stdout would suit me | 12:28 |
| straycat | distbuild already does this, it uses an internal option --build-log-on-stdout | 12:37 |
| ssam2 | oh yeah! | 12:38 |
| ssam2 | that's super useful, I can't believe I never thought of it! | 12:41 |
| tiagogomes | I can't push to git.baserock.org | 12:42 |
| straycat | not sure it was intended as a user thing, but *shrug* | 12:42 |
| tiagogomes | ssh git@git.baserock.org whoami shows that I am not in any group, should I be in any? | 12:43 |
| straycat | baserock-writers if you want to push | 12:43 |
| tiagogomes | ah, can someone add me to that group then? | 12:44 |
| ssam2 | tiagogomes: just so we are following policy, could you send an email to the list and request access ? | 12:45 |
| ssam2 | I know you already had it from a while back | 12:45 |
| ssam2 | straycat: would you be happy to +1 tiago's request? I will too | 12:46 |
| straycat | sure | 12:46 |
| ssam2 | ok, cool | 12:46 |
| ssam2 | tiagogomes: I'll add you to the group now then :) but please send the mail too | 12:46 |
| tiagogomes | ssam2, ok | 12:46 |
| tiagogomes | ssam2 to baserock-dev I suppose? | 12:47 |
| ssam2 | yeah | 12:47 |
| tiagogomes | I can push now, thanks ssam2 | 13:43 |
| *** bashrc [~motters@host109-156-188-158.range109-156.btcentralplus.com] has quit [Quit: leaving] | 13:43 | |
| paulsherwood | straycat, ssam2 - the purpose of including it would be so that one could diff build log a vs b to work out what has changed, or what config broke etc | 13:48 |
| bashrc2 is now known as bashrc | 14:04 | |
| paulsherwood | ssam2: would firehose chunk logically go in build-system? | 14:10 |
| pedroalvarez_ | paulsherwood: comparing build logs is already possible but not easy for a human to do | 14:11 |
| pedroalvarez is now known as pedroalvarez | 14:12 | |
| paulsherwood | pedroalvarez_: how? | 14:12 |
| pedroalvarez | They are storied in the artifacts folder | 14:12 |
| paulsherwood | they are? | 14:12 |
| pedroalvarez | So, if you know the cache keys of the 2 builds, you can compare | 14:12 |
| pedroalvarez | But as I said, not easy to do | 14:13 |
| paulsherwood | interesting | 14:13 |
| ssam2 | paulsherwood: build-system would be an OK place, yeah | 14:14 |
| ssam2 | theoretically you could make a smaller firehose-system because firehose doesn't actually need to build anything itself, but I don't think that's worth the effort right now | 14:15 |
| paulsherwood | +1 | 14:15 |
| tiagogomes | what is a mason these days? I recall it was a debian image running Jenkins and some other executable which contacted with the trove | 14:37 |
| ssam2 | tiagogomes: it's a work-in-progress | 14:43 |
| ssam2 | Adam did some work on it recently and documented his plans in an RFC to the list | 14:43 |
| ssam2 | some of that work is now done | 14:43 |
| ssam2 | if you look in the baserock-dev archive for '[RFC] Updating Mason to use Zuul, Gearman and Turbo-Hipster' (Nov 2014) and '[PATCH 0/8] Implement Mason with Zuul and turbo-hipster' (Dec 2014) you'll find the relevant info | 14:44 |
| tiagogomes | ok, thanks ssam2 | 14:45 |
| Mode #baserock +v pedroalvarez by ChanServ | 17:26 | |
| Mode #baserock +o pedroalvarez by ChanServ | 17:26 | |
| *** bashrc [~motters@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Lost terminal] | 17:54 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Remote host closed the connection] | 18:17 | |
| *** tiagogomes [~tiagogome@host-92-25-187-78.as13285.net] has quit [Quit: Leaving] | 19:12 | |
| *** tiagogomes [~tiagogome@host-92-25-187-78.as13285.net] has joined #baserock | 20:00 | |
| *** tiagogomes [~tiagogome@host-92-25-187-78.as13285.net] has quit [Client Quit] | 20:00 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!