IRC logs for #buildstream for Thursday, 2018-05-24

*** mohan43u has quit IRC03:08
*** mohan43u has joined #buildstream03:08
*** toscalix has joined #buildstream06:28
*** toscalix has quit IRC07:00
gitlab-br-botbuildstream: merge request (juerg/googlecas->master: WIP: Remote Execution CAS-based artifact cache) #337 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/33707:31
*** toscalix has joined #buildstream08:23
*** jonathanmaw has joined #buildstream08:40
*** tiagogomes has joined #buildstream08:51
*** toscalix has quit IRC09:01
*** juergbi has quit IRC09:07
*** juergbi has joined #buildstream09:15
*** juergbi has quit IRC09:16
*** juergbi has joined #buildstream09:16
*** noisecell has joined #buildstream09:32
*** aday has joined #buildstream09:35
*** noisecell has quit IRC11:16
*** bochecha_ has joined #buildstream11:24
jennisHi guys, I'm getting an error while trying to stage a source: Could not find base directory matching pattern: *11:38
jennisThat to me seems like it can't find any base directory in the source...?11:39
tlaterSounds like it, have you attempted manually downloading and extracting the source?11:59
tlaterThe * is specifically used so that all contents of the tarfile are extracted into the working directory12:00
tlaterSince most packages contain a single root directory that in turn is the *actual* source.12:00
tlaterAnd you kind of don't want that to be staged, but whatever is in that root directory.12:01
gitlab-br-botbuildstream: merge request (valentindavid/359_cross_junction_elements->master: Allow names for cross junction elements) #454 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/45412:11
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34712:29
*** noisecell has joined #buildstream12:32
jennistlater, ok thanks, no I've not attempted this manually. Will try that though13:11
gitlab-br-botbuildstream: merge request (valentindavid/331_include->master: WIP: Add support for include in project.conf) #471 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/47113:13
*** xjuan has joined #buildstream13:19
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34714:13
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34714:42
*** toscalix has joined #buildstream14:58
*** noisecell has quit IRC15:15
*** Prince781 has joined #buildstream15:18
*** xjuan has quit IRC15:22
gitlab-br-botbuildstream: merge request (correcting_typo->master: Correcting a typo in safe_remove's comment) #472 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/47215:31
Nexuscan someone quickly review this for me? https://gitlab.com/BuildStream/buildstream/merge_requests/47215:31
*** aday has quit IRC15:52
*** aday has joined #buildstream15:52
*** toscalix has quit IRC15:58
*** tiagogomes has quit IRC16:19
*** xjuan has joined #buildstream16:22
bochecha_one thing I'd really like in buildstream is « what brings the contents of ELEMENT1.bst into ELEMENT2.bst? »16:28
bochecha_like, right now I'm trying to track why base/perl.bst ends up in org.freedesktop.Platform (platform.bst) ; going at it with grep and trying to figure out the dep tree, then having to rebuild the whole thing to see whether it's out is very time consuming :(16:29
* tlater would personally love a little SVG tree like what systemd does for boot dependencies16:30
tlaterBut I think `bst show` already sports such functionality, bochecha_16:30
bochecha_it does?16:30
tlater`bst show -d none/plan/run/build/all`16:31
bochecha_I don't see where16:31
bochecha_oh, -d none?16:31
tlaterNone shows no dependencies, it's the default16:31
bochecha_but then how does that answer my question?16:32
tlaterYou should be able to grep for perl in something like `bst show -d all platform.bst`, no?16:32
tlaterOh, wait, it doesn't list them as a tree16:32
bochecha_sure, but if perl is in the output of bst show, that doesn't answer my question :)16:32
bochecha_even as a tree16:32
bochecha_perl could end up in the list if it's a build dep of something that is a dep of platform.bst16:33
tlaterYes, sorry, for some reason I imagined that showed a full dependency tree16:33
bochecha_that doesn't mean the artifacts built by perl.bst end up in the result of platform.bst16:33
bochecha_a dep tree still wouldn't answer my question16:33
tlaterHm, right16:33
*** jonathanmaw has quit IRC16:34
bochecha_basically what I want is for bst to look at platform.bst, see it's a "compose" element, look at the stuff it puts in, then recursively look at the runtime deps of those things16:34
bochecha_that is, not "do I need to build perl before building platform?", but "do the perl artifacts end up in the platform compose?"16:35
bochecha_basically, a tree of the stuff that ends up in the platform.bst compose would answer my question :)16:35
bochecha_is that worth an issue?16:35
tlaterYes, I think so16:35
*** finn has quit IRC16:36
tlater(Unless, of course, I'm missing some vital piece of functionality tristan already thought of, wouldn't be the first time)16:36
tlaterIMO being able to show information like that is one of the strengths of buildstream, it should definitely be exposed :)16:36
bochecha_yeah16:37
bochecha_I agree on both16:37
bochecha_it's been my experience with buildstream so far that every time I had a grand idea for something super cool that could be done with it, tristan told me it was already there ^_^16:37
ltubochecha_, tlater, is there any issue on gitlab raised to capture this already?16:42
ltuif not, could you raise one to describe?16:42
bochecha_ltu: I'm writing one16:42
ltubochecha_, great :)16:43
ltui'm on a bit of a rampage to tidy up gitlab atm. it has a lot more features than i ever realised.16:43
ltuwhich i know now i've read the proposal(s) from toscalix16:43
* tlater is glad we're finally pushing to use more of them16:45
tlaterMy private gitlab instance feels so lonely because I'm the only one using them so this stuff is pointless16:45
tlaterBut it looks so pretty!16:45
bochecha_I'm not sure what to write for " Acceptance Criteria"16:46
bochecha_is it alright if I skip it? :P16:46
bochecha_same for "Task Description" actually16:47
gitlab-br-botbuildstream: merge request (gitignore->master: .gitignore: Ignore autogenerated docs) #464 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/46416:47
gitlab-br-botbuildstream: merge request (gitignore->master: .gitignore: Ignore autogenerated docs) #464 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/46416:49
*** aday has quit IRC16:50
*** aday has joined #buildstream16:50
gitlab-br-botbuildstream: issue #406 ("RFE: Provide a way to show what ends up in a compose") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/40616:54
bochecha_I left these 2 sections as they are by default16:54
ltubochecha_, i think what you put for 'The way I think it could work is:' could have gone into task description16:58
ltuand acceptance criteria should outline what would solve it, so for this it's not going through the pain of something so time consuming16:59
ltuit's a solution that isn't so time consuming, i should say*17:00
ltubut yes, i have also struggled to fill out those bits before now.17:00
ltumaybe we need a template for a feature request, actually17:00
*** xjuan_ has joined #buildstream17:00
*** xjuan has quit IRC17:00
ltuI'll give some feedback to toscalix17:00
juergbialbfan[m]: thanks for the update. looks good to me, however, CI doesn't seem to be setup on your repo, which means I can't merge the MR via gitlab17:07
juergbiwould it possible for you to enable CI on your side?17:08
*** bochecha_ has quit IRC17:37
*** max has joined #buildstream17:38
*** max has left #buildstream17:38
albfan[m]juergbi: I have commit permissions on buildstream repo, so I can stop using the fork17:44
juergbiok, unfortunately gitlab doesn't allow changing the source branch in a MR17:45
juergbido you want to open a replacement MR with a branch in the main repo?17:45
*** max has joined #buildstream18:12
*** max has left #buildstream18:12
*** juergbi has quit IRC18:12
*** juergbi has joined #buildstream18:16
*** max has joined #buildstream19:00
*** max has left #buildstream19:00
albfan[m]juergbi: that's my idea19:04
*** bochecha_ has joined #buildstream19:11
*** toscalix has joined #buildstream19:18
toscalixI hope I did better the commit this time to the issue_template folder19:18
*** Prince781 has quit IRC19:25
*** Prince781 has joined #buildstream19:27
*** Prince781 has quit IRC19:35
toscalixif not, please let me know19:37
*** Prince781 has joined #buildstream19:37
*** max has joined #buildstream19:49
*** max has left #buildstream19:49
*** Prince781 has quit IRC20:01
*** Prince781 has joined #buildstream20:04
*** max has joined #buildstream20:14
*** max has left #buildstream20:14
*** max has joined #buildstream20:26
*** max has left #buildstream20:26
*** xjuan_ has quit IRC20:35
*** xjuan has joined #buildstream20:39
*** Prince781 has quit IRC20:59
*** max has joined #buildstream21:15
*** max has left #buildstream21:15
*** aday has quit IRC21:29
*** xjuan has quit IRC21:36
*** toscalix has quit IRC22:57
*** bochecha_ has quit IRC23:00
*** cs_shadow has quit IRC23:53

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!