| *** Prince781 has joined #buildstream | 00:32 | |
| *** Prince781 has quit IRC | 01:45 | |
| *** chrono has joined #buildstream | 02:38 | |
| *** Prince781 has joined #buildstream | 02:42 | |
| *** Prince781 has quit IRC | 03:00 | |
| *** Prince781 has joined #buildstream | 03:01 | |
| *** Prince781 has quit IRC | 03:43 | |
| *** Prince781 has joined #buildstream | 03:43 | |
| *** Prince781 has quit IRC | 05:08 | |
| gitlab-br-bot | buildstream: merge request (element-workspaces->master: Make workspaces element-wide instead of source-specific) #257 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/257 | 07:49 |
|---|---|---|
| *** tristan has quit IRC | 08:00 | |
| *** lantw44 has quit IRC | 08:00 | |
| *** tristan has joined #buildstream | 08:00 | |
| *** valentind has joined #buildstream | 08:12 | |
| *** bethw has joined #buildstream | 09:00 | |
| *** lantw44 has joined #buildstream | 09:02 | |
| *** tristan has quit IRC | 09:37 | |
| *** valentind has quit IRC | 09:55 | |
| *** tiago has joined #buildstream | 09:57 | |
| *** aday has joined #buildstream | 10:07 | |
| *** jonathanmaw has joined #buildstream | 10:08 | |
| *** tiago has quit IRC | 10:37 | |
| *** tiago has joined #buildstream | 10:38 | |
| *** aday has quit IRC | 11:10 | |
| *** aday has joined #buildstream | 11:28 | |
| gitlab-br-bot | buildstream: merge request (sam/conf-docs->master: Improve documentation for Autotools, CMake and Meson elements) #258 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/258 | 11:34 |
| *** tiago has quit IRC | 11:52 | |
| *** tiago has joined #buildstream | 11:53 | |
| gitlab-br-bot | buildstream: merge request (sam/conf-docs->master: Improve documentation for Autotools, CMake and Meson elements) #258 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/258 | 12:11 |
| *** ernestask has joined #buildstream | 12:20 | |
| *** aday has quit IRC | 12:33 | |
| *** aday has joined #buildstream | 12:59 | |
| jjardon[m] | hi, does anyone have any idea about https://gitlab.com/BuildStream/buildstream/issues/224 ? We are not getting any warning or error message but bst doesnt seem to try to push to the cache server | 13:10 |
| juergbi | jjardon[m]: have you specified push: true in the config? | 13:18 |
| juergbi | this was added with the support for multiple caches | 13:18 |
| jjardon[m] | juergbi: ah, that should be it | 13:22 |
| jjardon[m] | let me try | 13:22 |
| *** tiago has quit IRC | 13:32 | |
| *** tiago has joined #buildstream | 13:32 | |
| *** tiago has joined #buildstream | 13:33 | |
| jjardon[m] | juergbi: can it be the default to "push: true", so we can keep compatibility with the config? | 13:38 |
| jjardon[m] | If not, do you want me to open a issue to start a doc with incompatibilities between the bst-1.0 branch and master? | 13:39 |
| juergbi | i can understand the compatibility issue but defaulting to false generally sounds like a better idea | 13:39 |
| juergbi | we don't want accidental pushing | 13:39 |
| juergbi | a page with information about upgrading for each release series could indeed be useful | 13:40 |
| juergbi | maybe we could default to push for the old configuration style (where only one cache can be specified) | 13:41 |
| juergbi | however, it might be very confusing | 13:41 |
| juergbi | so i'd rather leave it as is despite the compatibility issue | 13:41 |
| gitlab-br-bot | buildstream: issue #224 ("buildstream is not pushing the artifacts even its using a SSH connection to download them") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/224 | 13:42 |
| gitlab-br-bot | buildstream: merge request (jjardon/jinja->master: setup.py: Require jinja >= 2.10) #239 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/239 | 13:43 |
| gitlab-br-bot | buildstream: issue #226 ("Document incompatibilities between bst-1.0 and current master branch") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/226 | 13:44 |
| *** mcatanzaro has joined #buildstream | 14:01 | |
| gitlab-br-bot | buildstream: issue #194 ("Pin Jinja2 to use at least 2.10") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/194 | 14:23 |
| gitlab-br-bot | buildstream: merge request (jjardon/jinja->master: setup.py: Require jinja >= 2.10) #239 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/239 | 14:23 |
| jonathanmaw | hrm, I'm trying to write tests for my implementation of allowing project.conf to override a source's config. Unfortunately, the method currently used to test element config overrides can't be extended to sources, since `bst show` doesn't let me output sources. | 14:30 |
| jonathanmaw | I think I'll stick to showing it off by what the end-result is, by showing it off in the git source | 14:30 |
| gitlab-br-bot | buildstream: issue #227 ("Allow building releases") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/227 | 15:21 |
| jjardon[m] | hi, any idea about ^ ? seems using bst shell and then make distcheck doesnt work as expected (Im trying here but mcatanzaro is getting an empty directory with nothing in it) | 15:32 |
| juergbi | hm, any error messages? | 15:39 |
| mcatanzaro | juergbi: I didn't notice any error messages last time I tried it | 15:40 |
| mcatanzaro | I'll try again soon; first I have to figure out how to get past harfbuzz which is currently unbuildable | 15:41 |
| mcatanzaro | I guess I can just manually change the tracked commit to something else as a workaround | 15:41 |
| *** noisecell has quit IRC | 15:47 | |
| mcatanzaro | juergbi: How is it supposed to work? | 15:48 |
| mcatanzaro | 'bst shell' brings me to an empty directory | 15:49 |
| mcatanzaro | # ls | 15:49 |
| mcatanzaro | # pwd | 15:49 |
| mcatanzaro | /buildstream/build | 15:49 |
| mcatanzaro | Are there supposed to be build products there...? | 15:49 |
| persia | bst shell should take you to a populated stages environment. Maybe you found a bug? Maybe the element definition is missing something? | 15:51 |
| persia | For source elements, I think the stage is the source and binary build dependencies. | 15:52 |
| persia | For others I do not have a good idea of what is staged. | 15:52 |
| mcatanzaro | I've never seen it do anything except take me to an empty build directory... I can actually run epiphany from there and it even sort of works, but definitely no way to run 'ninja dist' like I want to do | 16:00 |
| mcatanzaro | jjardon: ^ | 16:00 |
| gitlab-br-bot | buildstream: issue #228 ("Don't print tty process group warning when exiting bst shell") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/228 | 16:24 |
| jjardon[m] | mcatanzaro: can you try "bst workspace open core/epiphany.bst ~/epiphany" | 16:25 |
| jjardon[m] | the go to that folder and try to make distcheck? | 16:25 |
| mcatanzaro | jjardon[m]: I already have a workspace open for it | 16:25 |
| mcatanzaro | 'make distcheck' on the host will definitely fail, I need newer dependencies built by BuildStream for it to pass | 16:25 |
| mcatanzaro | (It's actually meson, so it would be 'ninja dist', but that doesn't matter.) | 16:26 |
| jjardon[m] | oh, seems workspaces doesnt work as I though | 16:27 |
| * paulsherwood wonders how the FOSDEM talk went? | 16:34 | |
| * jonathanmaw also | 16:45 | |
| jonathanmaw | when it's uploaded, it should appear on https://video.fosdem.org/2018/K.3.201/ | 16:45 |
| jonathanmaw | in, rather | 16:46 |
| gitlab-br-bot | buildstream: issue #229 ("Allow configuring default location for workspaces") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/229 | 16:53 |
| mcatanzaro | jjardon: I think I need to give up and reinstall jhbuild to do this week's releases, what do you think? If nobody knows how to do this...? :/ | 16:56 |
| mcatanzaro | Probably we should mail maintainers and let them know about this problem? I guess everybody who has released so far is still using jhbuild or host OS or hacking things somehow. | 16:57 |
| jjardon[m] | mcatanzaro: yep, I think tristan is travelling at the moment (coming back from FOSDEM) so maybe wait until he can reply? Or do you think is better to send an announcement to the GNOME mailist list now? | 16:59 |
| mcatanzaro | It can't really wait, because releases are due today, right? :P | 17:00 |
| mcatanzaro | Bad timing I guess | 17:00 |
| jjardon[m] | mcatanzaro: jbhuild modulesets and bst ones are not in sync anymore so there is a chance people will build using the incorrect deps. mmm | 17:00 |
| mcatanzaro | We could announce a delay | 17:02 |
| * mcatanzaro suggests delay | 17:06 | |
| jjardon[m] | mcatanzaro: Id suggest the same | 17:11 |
| mcatanzaro | I'll announce it, then | 17:11 |
| gitlab-br-bot | buildstream: issue #230 ("Error when trying to "bst shell" in a component") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/230 | 17:13 |
| mcatanzaro | jjardon[m]: What do you think about moving 3.19.90 to next week, and just skipping 3.19.91? | 17:23 |
| gitlab-br-bot | buildstream: merge request (212-git-source-needs-a-way-to-disable-checking-out-submodules->master: WIP: Resolve "Git source needs a way to disable checking out submodules") #259 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/259 | 17:23 |
| jjardon[m] | mcatanzaro: lets move this to #r-t | 17:24 |
| mcatanzaro | Ah yes | 17:24 |
| bochecha | mcatanzaro: about tarballs… why not simply do `bst shell --build MODULE` and then in that shell run the `make distcheck` or equivalent? | 18:05 |
| mcatanzaro | Aaaaah, it's the --build flag that we were missing | 18:06 |
| mcatanzaro | bochecha: Shame you didn't mention that five minutes ago :P | 18:06 |
| mcatanzaro | I was doing 'bst shell MODULE' without --build and was very confused why there was nothing there | 18:07 |
| bochecha | I didn't know you were searching for this information 5 minutes ago :) | 18:07 |
| bochecha | I only saw your email | 18:07 |
| mcatanzaro | ;) | 18:07 |
| mcatanzaro | Thanks | 18:07 |
| bochecha | yeah, `bst shell MODULE` gives you a shell in a sandbox where the module was already built and installed | 18:07 |
| bochecha | with the `--build` you get a shell just before building the module | 18:07 |
| bochecha | you can even run: `bst shell --build -- make distcheck` and that should work | 18:08 |
| mcatanzaro | Indeed, I see stuff there now! | 18:08 |
| bochecha | however, the problem will be getting the tarball out of the sandbox | 18:08 |
| bochecha | when you exit the shell, it is lost | 18:08 |
| bochecha | and inside the shell you don't have access to the host filesystem :-/ | 18:08 |
| *** ruben has joined #buildstream | 18:08 | |
| mcatanzaro | Aaaaaah | 18:08 |
| bochecha | what might work is the following: | 18:09 |
| bochecha | `bst shell --build app.bst bash -- -c "make distcheck; cat ${TARBALL}" > ${TARBALL}` | 18:09 |
| bochecha | but of course, you need to know the name of the generated tarball :-/ | 18:10 |
| bochecha | this is similar to a problem I had for a project of mine, we came up with this invocation with ssam2 | 18:11 |
| mcatanzaro | I didn't realize bst shell could run commands like that, OK.... | 18:11 |
| bochecha | (in my case it was extracting the translatable strings, running gettext in the sandbox and getting the resulting pot file outside the sandbox) | 18:11 |
| bochecha | it can run pretty much anything :) | 18:13 |
| bochecha | it would be great if it had something like flatpak's `--filesystem` option, so you could get the result of the command out of the sandbox, though | 18:14 |
| *** slaf has quit IRC | 18:14 | |
| *** slaf- has joined #buildstream | 18:14 | |
| *** slaf- is now known as slaf | 18:14 | |
| *** jonathanmaw has quit IRC | 18:15 | |
| mcatanzaro | I'm trying: bst shell --build core/epiphany.bst bash -- -c "cd _builddir; meson ..; ninja; ninja dist; cat epiphany-3.27.90.tar.xz > epiphany-3.27.90.tar.xz" | 18:20 |
| mcatanzaro | I think it ran out of file descriptors | 18:20 |
| mcatanzaro | Wow | 18:20 |
| mcatanzaro | https://paste.gnome.org/pxxnvag4q | 18:21 |
| mcatanzaro | Never seen that before | 18:21 |
| mcatanzaro | bochecha: https://gitlab.com/BuildStream/buildstream/issues/227 <-- thanks for the help! | 18:25 |
| juergbi | mcatanzaro: for access to the release tarball, open a workspace | 18:31 |
| juergbi | nor sure about the file descriptor issue | 18:31 |
| mcatanzaro | Oh wow, it's already there in my workspace! | 18:33 |
| mcatanzaro | Cool | 18:33 |
| *** valentind has joined #buildstream | 18:37 | |
| bochecha | oh, I didn't know workspaces would have the tarball | 18:53 |
| *** aday has quit IRC | 19:33 | |
| gitlab-br-bot | buildstream: issue #231 ("Bash completion broken inside bst shell") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/231 | 19:34 |
| *** ernestask has quit IRC | 19:36 | |
| gitlab-br-bot | buildstream: issue #232 ("fd leak when generating epiphany tarball") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/232 | 19:44 |
| *** aday has joined #buildstream | 20:19 | |
| *** Prince781 has joined #buildstream | 21:55 | |
| *** valentind has quit IRC | 21:56 | |
| *** spamdoctor_ has joined #buildstream | 22:06 | |
| *** aday has quit IRC | 22:07 | |
| *** Prince781 has quit IRC | 22:12 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!