IRC logs for #buildstream for Friday, 2019-05-31

*** mohan43u has quit IRC05:47
*** tristan has quit IRC05:53
*** mohan43u has joined #buildstream06:12
*** tristan has joined #buildstream06:16
*** tristan has quit IRC07:38
*** tristan has joined #buildstream07:38
*** toscalix has joined #buildstream07:39
*** toscalix has quit IRC07:40
*** bochecha has joined #buildstream07:49
*** toscalix has joined #buildstream08:05
*** raoul has joined #buildstream08:39
*** finn has joined #buildstream08:47
gitlab-br-botjennis approved MR !1362 (raoul/1024-artifact-docs->master: Update docs regarding artifact and source caches) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136209:09
finnAny reason tar isn't a core plugin for buildstream?09:10
jennistar source is, tar element isn't09:12
finnhow come?09:12
jennisI guess because legacy reasons, we've supported `bst artifact checkout foo.bst --tar foo.tar.gz` for a very long time now09:13
jennisBut to actually have the tarball in your build, to be consumed by another element, you need the plugin, and IIRC the freedesktop guys needed this09:14
finnHeh ok...09:16
*** jonathanmaw has joined #buildstream09:17
jennisfinn: my guess would be that because we've decided we're going to start migrating plugins from core, it wouldn't make sense to add another plugin to core, but I'm not 100% sure on that09:22
finnRight, yes someone just told me of that. I wasn't aware09:23
finnThanks!09:23
gitlab-br-botmarge-bot123 closed issue #1024 (Update arch/design docs to reflect move to Proto based artifact services) on buildstream https://gitlab.com/BuildStream/buildstream/issues/102409:39
gitlab-br-botmarge-bot123 merged MR !1362 (raoul/1024-artifact-docs->master: Update docs regarding artifact and source caches) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136209:39
*** lachlan has joined #buildstream09:41
*** rdale has quit IRC10:04
tpollardhave we made any changes recently that would have significantly reduced the size of the integration cache from the test suite?10:25
gitlab-br-botraoul.hidalgocharman opened (was WIP) MR !1366 (raoul/1025-legacy-remotes->master: Improved handling of legacy remotes) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136610:25
*** ChanServ sets mode: +o tristan10:30
tristantpollard, possibly... is there a commit which uses a slimmed down freedesktop-sdk base instead of the alpine image ? I'm not sure if it might have done the opposite though10:30
tristani.e. as I recall tlater[m] may have added that, but it may be an *additional* runtime and we did not drop alpine10:30
tristantpollard, depending on what you are looking at as evidence, also remember the accumulative nature of the gitlab caches10:31
tristanso zapping the gitlab cache may result in removing unused cruft from side branches10:31
tpollardthis is locally10:32
tpollardtesting against an older commit now for my own sanity :)10:32
tlater[m]tristan it hasn't been added yet10:33
tlater[m]And I'd expect it to increase the size if anything...10:34
tristanright10:46
gitlab-br-botBenjaminSchubert opened MR !1367 (bschubert/cython-disable-linetrace->master: Setup.py: Disable linetrace by default and only enable when using coverage) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136710:59
*** alatiera has joined #buildstream11:12
*** lachlan has quit IRC11:36
*** lachlan has joined #buildstream11:45
*** alatiera has quit IRC12:27
*** raoul_ has joined #buildstream12:39
*** raoul has quit IRC12:41
*** bochecha has quit IRC12:53
*** bochecha has joined #buildstream12:54
benschubertphil: tests/examples/flatpak-autotools: shouldn't be that moved to the ostree plugin tests?13:00
tpollardrelated https://gitlab.com/BuildStream/buildstream/issues/103213:02
benschubertoh thanks tpollard13:03
benschubertIs there any reason why we would want this test here and not in ostree?13:03
WSalmonThe examples did/do cover a few diffrent ways to "bootstrap" your project eg, ostree/tar from alphine/fd-sdk, so it is "right" that the tests that cover what the docs do live in examples, but it dosent make sence if they never get run, i think tlater[m] was looking at moving all the examples to use FD-sdk which might solve this too13:26
gitlab-br-botdanielsilverstone-ct approved MR !1367 (bschubert/cython-disable-linetrace->master: Setup.py: Disable linetrace by default and only enable when using coverage) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136713:27
*** lachlan has quit IRC13:28
tpollardWSalmon: good points about example test coverage, I hadn't considered that13:29
WSalmonI personally think it would be a shame if the exmples didnt show you at least a variety of ways to boot strap a project after all this is one of the big advantages over yockto/pokey but i think i am a minority voice in this regard, the above from Ben dose seem to be a good reson to move to FD-sdk for all examples to reduce maintance13:29
tlater[m]WSalmon: We're not using ostree to bootstrap anything anymore as far as I am aware, so that would technically obsolete the test case here.13:31
tlater[m]We definitely don't after my branch. Whether we want to keep an example of it for the sake of showing off third party plugins is a different question, of course.13:32
tlater[m]But I think it would make more sense to link to the third party docs in that case.13:32
WSalmonmaybe we could just have a exmples stage in the tests taht had lots of plugins installed and then remove the examples from the other tests, this would reduce testing laps-time and total compute time, but still give use a interesting test coverage13:33
benschuberttlater[m]: should I make a PR to the ostree plugin with those tests then?13:34
*** lachlan has joined #buildstream13:35
tlater[m]benschubert: I think that's a good way to go about it, yeah.13:36
benschubertthanks!13:36
tlater[m]As long as we have tests in buildstream that make sure the plugin API stays stable I don't see how this can break it.13:37
tlater[m]benschubert: But please check the docs and make sure the relevant example is also moved (:13:37
benschubertSure!13:38
philbenschubert, sorry I missed your ping. I don't have much to add to what has already been said, but for what it's worth I agree it makes sense to move that test over.13:40
benschubertthanks phil and no worries!13:41
finnValueError: Namespace OSTree not available >> What does this mean?13:59
finnOr more importantly, how do I fix it14:00
finnI've installed buildstream and buildstream-externals via pip14:00
tpollardhave you added the plugin to your project.conf?14:02
jennisfinn: https://docs.buildstream.build/format_project.html#external-plugins14:03
jennisOh actually, you're using bst 1.2, that's in core14:03
jennisYou don't have the right system dependencies, that's the problem14:04
finnjennis, yes as that's what pip provides me14:04
finnI've done an `apt install ostree`14:04
finnWhat else do I need?14:04
jennisWas distro are you using?14:04
jenniswhat*14:04
finnubuntu 18.04 docker image14:05
jenniscool, apt install ostree and pip install pygobject *should* do it14:05
jennisIn fact, just the former mayber14:05
finnI already have ostree installed14:05
finnStill doesn't work14:07
*** lachlan has quit IRC14:07
juergbifinn: do you also have gir1.2-ostree-1.0 ?14:08
juergbiand python3-gi14:08
juergbi(debian package names)14:09
tlater[m]finn: You also need to install gobject-introspection14:10
tlater[m]Which you will need to install through distro packages14:10
tlater[m]As well as, well, ostree14:11
tlater[m]Neither of those things are available through pip14:11
finngot ostree, first thing I tried14:11
tlater[m]finn: If you *have* those things installed, your distro may not by default export ostree's gobject-introspection bindings, in which case you'd need to install something along the lines of ostree-dev14:12
finnIf these are core deps, shouldn't they be in here? https://buildstream.build/source_install.html#installing_dependencies14:12
gitlab-br-botmarge-bot123 merged MR !1367 (bschubert/cython-disable-linetrace->master: Setup.py: Disable linetrace by default and only enable when using coverage) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/136714:15
tlater[m]jennis: Are you sure ubuntu provides ostree dev bindings by default?14:16
finnmaybe not the dev bindings14:16
finnhang on14:16
tlater[m](I know you use ubuntu, so...)14:16
tlater[m]Doesn't look like it: https://packages.ubuntu.com/cosmic/libostree-dev14:16
tlater[m]finn: Try installing libostree-dev as well14:17
*** lachlan has joined #buildstream14:18
finnlibostree-dev was what I needed14:19
finnthanks :)14:19
finnperhaps that doc should be updated14:19
tlater[m]finn: They are all optional dependencies because ostree is optional14:24
finnOh sorry I thought it was part of bst 1.2?14:25
finn<jennis> Oh actually, you're using bst 1.2, that's in core14:25
tlater[m]But yes, it should be documented. Hopefully documentation for this will improve with the dependency split.14:25
* tlater[m] really wonders what this chat log looks like on finn's end x)14:29
jennistlater[m], it used to be documented14:30
finntlater[m], what do you mean?14:30
tlater[m]It does look like my client has a serious delay compared to the actual channel.14:30
jennisWhat I think happened was: OStree moved from core and this was taken out of the docs, and then the docs were split into 1.2 and master... so both versions don't have any mention of installing ostree14:31
tlater[m]finn: It's *part of* bst 1.2, but not everybody needs all plugins 1.2 provides. Hence plugin dependencies are not considered "core"14:31
tlater[m]It would be a shame if you needed to have gobject-introspection installed to run buildstream, when it can funcion just fine without.14:31
finnI see your point14:32
finnThanks for the help anyway14:32
jennisbut tlater[m], the 1.2 docs still have a "install plugin dependencies" section14:32
jennisand ostree deps are not present14:32
jennishttps://buildstream.build/source_install.html#installing_dependencies14:33
jennisostree deps used to be there too14:33
*** xjuan has joined #buildstream14:34
tlater[m]jennis: close. BuildStream used to *require* ostree (for artifact management), but when we changed that it no longer required  ostree as a core dep14:35
tlater[m]I suspect whoever changed that doc forgot to update the plugin dependencies section - we'll definitely want to update that :)14:35
jennistlater[m], those docs I just linked include, for each distro: "system requirements for the default plugins", for example they say for Debian you should `apt install bzr git lzip patch python3-arpy`14:47
jennisFrom what I remember, OSTree used to be included here, and the ostree dev libraries, but not anymore, so it seems14:47
jennisAnd way before that, yeah it was a core dependency14:47
tlater[m]jennis: I agree it's a bug in any case, hehe. Do you want to set up the ticket or should I?14:48
jennisI think we just need to revert a commit somewhere14:49
tlater[m]Well, unless someone wants to do that right now, we should have an issue telling us that14:49
jennistlater[m], yeah I'll do it now14:52
tlater[m]jennis: I have a feeling this might be because the website is out of sync with the project...14:54
tlater[m]Looking into how these things are put together again14:54
*** xjuan has quit IRC15:04
jennistlater[m]: https://gitlab.com/BuildStream/website/merge_requests/12215:08
tlater[m]jennis: alas, I lack the authority to approve that :|15:11
jennisdang15:11
jennistpollard ^^ ?15:12
*** xjuan has joined #buildstream15:12
jennisSeems you have power15:12
tpollardsec15:12
tpollardlooks like you have a merge commit in that repo tlater[m] can you merge it?15:22
tlater[m]tpollard: I have a merge commit in that repo?15:23
tlater[m]Only a merge request15:23
tlater[m]In any case, that particular commit isn't that important atm, I'll merge it whenever someone approves.15:24
tpollardI've approved it :) but apparently I can't merge lol15:25
tlater[m]tpollard: I think you meant jennis ;p15:28
*** lachlan has quit IRC15:28
* tpollard is confused, but it is friday afternoon15:29
*** lachlan has joined #buildstream15:31
tlater[m]tpollard: It's friday rapidly-approaching-evening ;)15:31
tpollardafaict, your gitlab account has merged to the website repo15:32
tpollardso I don't understand why it doesn't allow you to approve xD15:32
tlater[m]Ahh, I see what you mean15:44
tlater[m]Yeah, no idea, I expect that the permissions are managed manually on that repo15:44
tlater[m]Not that I really mind, fewer things I have to look at ;p15:45
tpollard;)15:47
*** bochecha has quit IRC15:59
*** tpollard has quit IRC16:02
gitlab-br-botraoul.hidalgocharman opened issue #1041 (Support seperate end points for artifact caches) on buildstream https://gitlab.com/BuildStream/buildstream/issues/104116:05
*** raoul_ is now known as raoul16:08
*** finn has quit IRC16:26
*** finn has joined #buildstream16:29
*** phildawson has joined #buildstream16:30
*** xjuan has quit IRC16:33
*** raoul has quit IRC17:01
*** lachlan has quit IRC17:02
*** lachlan has joined #buildstream17:11
*** jonathanmaw has quit IRC17:38
*** slaf has quit IRC18:01
*** lachlan has quit IRC18:16
*** toscalix has quit IRC18:28
*** lachlan has joined #buildstream18:37
*** lachlan has quit IRC18:47
*** lachlan has joined #buildstream19:46
*** lachlan has quit IRC19:56
*** lachlan has joined #buildstream19:56
*** lachlan has quit IRC19:58

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