--- Log opened Fri Mar 16 00:00:39 2018
00:02 -!- Horwitz [~mich1@p200300800E0E0C00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
00:15 -!- Horwitz [~mich1@p200300800E2EE800022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:15 -!- mode/#navit [+o Horwitz] by ChanServ
01:20 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
01:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
01:39 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
05:35 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
05:35 -!- mode/#navit [+v xenos1984] by ChanServ
06:40 -!- noradtux [~noradtux@2a02:2028:632:5e01:f494:e8c:a0b3:87f9] has quit [Ping timeout: 252 seconds]
06:45 -!- noradtux [~noradtux@134.101.209.154] has joined #navit
10:33 -!- udovdh [~udovdh@2001:981:a812:0:240:63ff:fef6:201] has joined #navit
11:29 -!- udovdh [~udovdh@2001:981:a812:0:240:63ff:fef6:201] has quit [Quit: Leaving]
12:01 -!- pmckinley [~Peter_McK@host-92-19-98-147.as13285.net] has joined #navit
12:02 #navit: < pmckinley> Hello world
12:25 -!- xemarkus-k [~tujgxahz@2604:a880:400:d1::4f5:a001] has joined #navit
12:25 -!- xemarkus-k [~tujgxahz@2604:a880:400:d1::4f5:a001] has quit [Client Quit]
12:31 -!- pmckinley [~Peter_McK@host-92-19-98-147.as13285.net] has quit [Read error: Connection reset by peer]
15:19 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
15:30 #navit: <+jkoan> Hi @all
15:30 #navit: <+jkoan> KaZeR: could you provide me a background of our trac data? 
15:49 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
15:49 -!- mode/#navit [+v xenos1984] by ChanServ
16:31 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has joined #navit
17:07 #navit: <@KaZeR> jkoan: a background?
17:08 #navit: <+jkoan> Trac upgrade, tests and possible move to github
17:09 #navit: <@KaZeR> upgrades are quite easy. what kind of tests?
17:10 #navit: <+jkoan> I want to try how trac can interact with git, probably to read tags automatically and so on
17:29 #navit: <@KaZeR> i can setup a test config for you to play with
17:30 #navit: <@KaZeR> if you want to play with git interactions, circleci is supposed to notify us when build fails, but it isn't working
17:30 #navit: <+jkoan> Yes, because the password is false
17:30 #navit: <+jkoan> Or something like that
17:31 #navit: <@KaZeR> which password?
17:32 #navit: <+jkoan> So that circleci can join this channel. The user password seems to be false
17:33 #navit: <@KaZeR> but there's no password on our channel
17:33 #navit: <+jkoan> i mean for the user
17:35 #navit: <@KaZeR> ha, you mean Nickserv registration?
17:35 #navit: <+jkoan> i think so
17:35 #navit: <@KaZeR> we don't enforce it
17:35 #navit: <+jkoan> i will check it
17:35 #navit: <@KaZeR> thanks!
17:36 #navit: <@KaZeR> we only have [tz] set on the channel (so topic protection and something else)
17:36 #navit: <+jkoan> okay :D
17:44 #navit: <+jkoan> i think those notifications are a v1 feature and has never been repaired 
17:50 #navit: <+jkoan> KaZeR: i have a idea: workflow --> add a workflow step to combine all current steps and wait to complete them, after that a container could just start to check all results and send the required notifications
17:53 #navit: <@KaZeR> that's an idea yeah. but this is supposed to be a standard feature
17:53 #navit: <@KaZeR> haha it's quite awesome, if you google our issue, you'll find this in the top results : https://discuss.circleci.com/t/add-freenode-channel-notification/3238/3
17:53 #navit: <@KaZeR> 2nd comment is from mdankov and about our channel :)
17:53 #navit: <+jkoan> yes, this what i have also seen
17:57 #navit: <+jkoan> thanks to the this comment i now understand why we have the defaults:
17:57 #navit: <+jkoan> # The following stanza defines a map named defaults with a variable that may be inserted using the YAML merge (<<: *) key  # later in the file to save some typing. See http://yaml.org/type/merge.html for details. 
17:59 #navit: <@KaZeR> yeah, it's a nice yaml trick
18:18 #navit: <+jkoan> KaZeR: what do you think about using the workflows even more?
18:35 #navit: <+jkoan> KaZeR: what about something like this? https://www.draw.io/#Uhttps%3A%2F%2Fgist.githubusercontent.com%2Fjkoan%2Fb22e5b229f694c44f3b2b8df9ab13529%2Fraw%2F8d4b76adb8ec6dda51bb1404e6f6227db6a0af80%2Fgistfile1.txt
18:38 #navit: <+jkoan> the download center thing could been handled be sharing a workspace like described here: https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs
19:06 #navit: <@KaZeR> makes sense. i'm not sure that artifacts paths are preserved between tasks though
19:06 #navit: <@KaZeR> also not sure that it's worth checking out the download center before the builds
19:35 #navit: <+ilovekiruna> KaZeR: I found a very interesting gentoo package recently
19:36 #navit: <@KaZeR> ha?
19:36 #navit: <+ilovekiruna> dev-python/ebuildtester
19:36 #navit: <+ilovekiruna> heard of it before?
19:36 #navit: <+ilovekiruna> exactly what i discussed with you earlier, more or less
19:36 #navit: <@KaZeR> i don't think so!
19:36 #navit: <@KaZeR> nice!
19:36 #navit: <+ilovekiruna> based on docker builds a Gentoo package with a clean stage 3
19:37 #navit: <+ilovekiruna> only thing missing would be USE flag extraction ;-)
19:37 #navit: <@KaZeR> exactly how we wanted to do it
20:15 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 260 seconds]
20:43 -!- jandegr [d5d38ece@gateway/web/freenode/ip.213.211.142.206] has joined #navit
21:22 #navit: <@KaZeR> jkoan: As you may be aware, there recently was an interruption in the availability of the Coverity Scan service. In February 2018, we discovered that servers used for the Coverity Scan service were accessed by an unauthorized third-party. The access appears to have started earlier in the month. We suspect that the access was to utilize our computing power for cryptocurrency mining. We have not found evidence
21:22 #navit: <@KaZeR> that database files or artifacts uploaded by the open source community users of the Coverity Scan service were accessed. We retained a well-known computer forensics company to assist us in our investigation. 
21:23 #navit: <@KaZeR> so Coverity should be back
21:28 #navit: <+ilovekiruna> KaZeR: was it just our account or a general problem of coverity?
21:34 -!- jandegr [d5d38ece@gateway/web/freenode/ip.213.211.142.206] has quit [Quit: Page closed]
21:57 -!- Netsplit *.net <-> *.split quits: noradtux
21:57 -!- Netsplit over, joins: noradtux
22:01 #navit: <@KaZeR> ilovekiruna: yeah it was a general problem
22:02 #navit: <@KaZeR> so we're back with our 135 defects to fix :D
23:24 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 264 seconds]
23:32 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
23:49 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
23:49 -!- mode/#navit [+v xenos1984] by ChanServ
--- Log closed Sat Mar 17 00:00:41 2018