| *** shibualex has joined #buildstream | 03:19 | |
| *** leopi has joined #buildstream | 04:55 | |
| *** leopi has quit IRC | 05:37 | |
| *** leopi has joined #buildstream | 05:42 | |
| *** leopi has quit IRC | 06:04 | |
| *** leopi has joined #buildstream | 06:48 | |
| *** leopi has quit IRC | 06:51 | |
| *** leopi has joined #buildstream | 06:52 | |
| *** tristan has joined #buildstream | 07:02 | |
| *** ChanServ sets mode: +o tristan | 07:06 | |
| gitlab-br-bot | buildstream: issue #609 ("CAS server doesn't seem to automatically remove artifacts so it gets fill up") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/609 | 07:19 |
|---|---|---|
| *** tristan has quit IRC | 07:35 | |
| *** toscalix has joined #buildstream | 07:47 | |
| *** Kinnison has joined #buildstream | 07:55 | |
| *** rdale has joined #buildstream | 08:08 | |
| gitlab-br-bot | buildstream: merge request (Qinusty/600-recursive-variables->master: Add cyclic check within variable resolution) #712 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/712 | 08:11 |
| gitlab-br-bot | buildstream: merge request (Qinusty/600-recursive-variables->master: Add cyclic check within variable resolution) #712 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/712 | 08:11 |
| *** shibualex has quit IRC | 08:14 | |
| *** tristan has joined #buildstream | 08:28 | |
| *** noisecell has joined #buildstream | 08:45 | |
| *** jonathanmaw has joined #buildstream | 08:46 | |
| *** tpollard has joined #buildstream | 08:52 | |
| gitlab-br-bot | buildstream: merge request (juerg/workspaced-dependencies->master: Fix key invalidation for workspaced dependencies) #740 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/740 | 09:03 |
| *** solid_black has joined #buildstream | 09:05 | |
| *** ChanServ sets mode: +o tristan | 09:07 | |
| *** jonathanmaw_ has joined #buildstream | 09:38 | |
| *** jonathanmaw has quit IRC | 09:39 | |
| *** tristan has quit IRC | 09:56 | |
| toscalix | I have been thinking about the known issues page | 09:57 |
| toscalix | the idea of the page is a list of bugs that we know it will hit the users early on | 09:58 |
| toscalix | so we can route them there when asking on the list or looking for workarounds | 09:58 |
| toscalix | the problem with including this list on the web is that we need a mechanism to show that the bug is close when the ticket is close | 09:58 |
| toscalix | we can do that if we have the known issues page in the gitlab wiki | 09:59 |
| toscalix | but I am not sure if we can have such feature if we have it on the web. I assume not | 09:59 |
| toscalix | otherwise we need to maintained by hand and it will not work well | 10:00 |
| qinusty | Can someone review https://gitlab.com/BuildStream/buildstream/merge_requests/712 if they get a chance? | 10:01 |
| toscalix | valentind: I need your help to review these MR since Laurence is on vacation https://gitlab.com/groups/BuildStream/nosoftware/-/merge_requests | 10:22 |
| *** jonathanmaw_ has quit IRC | 10:26 | |
| *** jonathanmaw has joined #buildstream | 10:26 | |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 10:31 |
| *** tristan has joined #buildstream | 10:41 | |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 10:53 |
| *** ChanServ sets mode: +o tristan | 10:57 | |
| juergbi | tristan: in case you haven't seen it yet, I've opened !740 as alternative fix for the #461 cache key issue | 11:11 |
| valentind | juergbi, Thank you. | 11:15 |
| juergbi | thank you for the investigation and the test case | 11:15 |
| tristan | juergbi, I hadn't seen it no, thanks ! | 11:16 |
| *** jonathanmaw_ has joined #buildstream | 11:16 | |
| toscalix | what if we refer to odds versions as development version and releases as user version | 11:17 |
| toscalix | ? | 11:17 |
| *** jonathanmaw has quit IRC | 11:17 | |
| toscalix | so we avoid the words release and maintenance | 11:17 |
| tristan | :-S | 11:18 |
| tristan | Did we ever have the word 'maintenance' ? | 11:18 |
| toscalix | we didn't but it is also a possibility: maintained version | 11:18 |
| tristan | I think 'user version' is rather ambiguous, while development version sounds right for what it is | 11:18 |
| toscalix | user sounds ambiguous... unless you are about to become a new user | 11:19 |
| toscalix | but fine, I will keep thinking | 11:19 |
| tristan | The language we are using these words for are for releases, tags and branches; if we say that a development snapshot is a development snapshot, then we reserve the word 'release' for releases only, I think this works well at least for the language I can think of so far | 11:21 |
| tristan | But it would be nice to avoid the word 'release' I guess, then we can use the word release for both (like if we used the standard terminology with 'stable') | 11:22 |
| toscalix | not sure I understood you | 11:22 |
| tristan | toscalix, Currently we are saying "Release 1.2.0" "Development Snapshot 1.3.0", etc | 11:22 |
| toscalix | I want to avoid release because is a word we use internally as final point of the delivery process | 11:22 |
| tristan | And we say "The release branch is bst-1.2", while development happens in master | 11:23 |
| toscalix | I would like to use a different word for people that are not familiar with our delivery jargon | 11:23 |
| toscalix | also release is a verb | 11:23 |
| tristan | toscalix, in the context we use it in software, it is also a noun | 11:24 |
| toscalix | I know | 11:24 |
| tristan | I think that the main point here is to avoid using the word 'stable', and to do that; I think we can satisfy any of the requirements which revolve around this by basically hiding the development work from users who are not developers | 11:25 |
| toscalix | if a new person comes to the project I would like to point him to X (without the word release). So we need a word which is not stable-maintained-user version | 11:26 |
| toscalix | I would like to avoid release too | 11:26 |
| tristan | I mean in the above: I would prefer never to have to say "This is a release release" | 11:26 |
| toscalix | stable-maintained-user-release version | 11:27 |
| toscalix | :-) | 11:27 |
| tristan | As in opposed to a "Development snapshot release", I'd rather not use the word release as an adjective | 11:27 |
| tristan | I think that every time we roll a tag, tarball, and send the notes etc... it is a release that we point someone to | 11:27 |
| toscalix | agree | 11:28 |
| tristan | Otherwise, we are *really* trying to be different and confusing | 11:28 |
| toscalix | I am fine with using the word release in foums for contributors | 11:28 |
| toscalix | forums | 11:28 |
| toscalix | but for users... I would rather not use it. It is not a good substitute for statbel, in my opinion | 11:29 |
| gitlab-br-bot | buildstream: issue #461 ("Cache key confusion when elements depend on an open workspace") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/461 | 11:29 |
| gitlab-br-bot | buildstream: merge request (juerg/workspaced-dependencies->master: Fix key invalidation for workspaced dependencies) #740 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/740 | 11:29 |
| toscalix | stable | 11:29 |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 11:29 |
| tristan | This is all a bit annoying, because the words 'stable' and 'development' for adjectives to describe a release; are really targetted at integrators who consume your releases and deliver those to users; usually by packaging them into a distro | 11:30 |
| tristan | The end user doesnt normally need to even see this jargon or know that it came from a git repository at all | 11:31 |
| toscalix | I am working on the design of the download page | 11:31 |
| toscalix | and I need to refer to the latest released stable version | 11:32 |
| tristan | Right, so in that case (thanks I was missing some context I think); do we need to distinguish ? | 11:32 |
| tristan | Can't we just say "Latest release" ? | 11:32 |
| toscalix | we can | 11:33 |
| toscalix | my point is to avoid the word release. | 11:33 |
| toscalix | :-) | 11:33 |
| tristan | If anyone wants the development snapshot, they should probably have to dig further, maybe in the contributing guides or such | 11:33 |
| toscalix | we can point them also in the download page, that is not an issue | 11:33 |
| tristan | Latest version ? | 11:33 |
| toscalix | maybe we can call our stable releases with a specific name and the development one also | 11:34 |
| toscalix | not a codename for each release, but a static name | 11:34 |
| tristan | Well, it's a bit confusing is someone starts to look at a list of tarballs on an ftp site or at a list of tags | 11:34 |
| tristan | where 1.2.0 is clearly not the "latest version" | 11:34 |
| tristan | juergbi, eh... I wonder if tests/frontend/workspace.py::test_cache_key_workspace_in_dependencies shouldn't just use git, and just try with strict vs non-strict | 11:37 |
| tristan | juergbi, is there any reason that a different Source plugin could cause a different outcome in that test case ? | 11:37 |
| tristan | juergbi, I already merged it, but noticed that when running the test locally after :-S | 11:37 |
| juergbi | I can't think of a reason. valentind, did you parameterize this just to be in line with the other test cases or do you think it's actually necessary? | 11:38 |
| tristan | A lot of the workspace tests wanted to try each repo because they exercise potential implementations of virtual methods in Sources | 11:39 |
| tristan | but when that is not the case, we should avoid spamming CI unnecessarily | 11:40 |
| tristan | w00t, my badge trick worked | 11:40 |
| tristan | https://gitlab.com/BuildStream/buildstream/tree/tristan/docs-version-badge | 11:40 |
| tristan | See the new badge in the readme, showing the latest release number with an even minor point | 11:41 |
| juergbi | :) | 11:48 |
| tristan | Oh cute, I can encode a link *into* the SVG, so when I generate the SVG, I can give it a custom target | 11:49 |
| tristan | So, for instance, any version like 1.0.1, I can point to https://download.gnome.org/sources/BuildStream/1.0/ | 11:50 |
| tristan | Or I could link to the actual tarball | 11:50 |
| tristan | Or, I could link it to https://gitlab.com/BuildStream/buildstream/tags/1.0.1 | 11:51 |
| tristan | What would be the best target for a release specific badge ? | 11:51 |
| tristan | Basically; how this works is that every time we build the docs by running a pipeline on master, it will update the badges to the latest versions (I have two badges, one for latest development snapshot too) | 11:52 |
| *** jonathanmaw_ is now known as jonathanmaw | 11:52 | |
| valentind | juergbi, I think it does not matter the plugin for this test. | 11:55 |
| juergbi | ok | 11:56 |
| juergbi | valentind: #316: are these steps you followed to reproduce the issue or is this purely theoretical how you think it might happen? | 11:56 |
| jonathanmaw | tristan: it looks like freedesktop-sdk users are resorting to an unpleasant workaround to have their CrateSource plugin inherit from DownloadableFileSource (https://gitlab.com/BuildStream/bst-external/merge_requests/48/diffs#fb08aba75dfacbf1cd0e50f0b80858984ee6f36c_0_11). Is there a better way to do this that we can recommend, or would the best practice be to open an issue with buildstream to get DownloadableFileSource accessible on the same | 11:56 |
| jonathanmaw | level as ScriptElement? | 11:56 |
| valentind | juergbi, Unfortunately still theoritical. | 11:57 |
| juergbi | valentind: could it be a duplicate of #383, which was fixed by !448? | 11:57 |
| valentind | I am writing some tests, but it is not easy. I have seen the build happening before the pull to finish with my eyes. But my eyes are not the thing to trust. | 11:57 |
| juergbi | valentind: could it be that you only saw it in the workspaced dependency case, which would now be fixed? | 11:58 |
| juergbi | or did you see it also without workspaces? | 11:58 |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config for libtool .la files) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 11:58 |
| valentind | juergbi, Yes. I think Michael uses non strict mode. | 11:58 |
| valentind | Oh, I see the fix was non strict mode. | 11:59 |
| valentind | juergbi, I think we added a assertion at commit that the keys we are using are the same as when we started building, then it would be fine. | 12:00 |
| valentind | One of the problem with testing non strict mode is that there is no plugin we can use to test without integration tests. | 12:01 |
| valentind | Because of BST_STRICT_REBUILD, both script and compose, behave differently. | 12:02 |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config for libtool .la files) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 12:02 |
| juergbi | valentind: what about a manual element without any actual commands? | 12:02 |
| juergbi | alternatively, we might need a test plugin | 12:03 |
| tristan | jonathanmaw, the best would indeed be to expose the abstract class I think | 12:03 |
| valentind | Yes, but to make sure you have the right dependencies, you need to copy files from dependencies to the artifact. And with manual, you cannot do that. | 12:04 |
| jonathanmaw | tristan: ok, I'll open an issue for that | 12:04 |
| valentind | juergbi, Yes I think that #316 is really a duplicate of #383. I suppose we can just close it then. | 12:06 |
| tristan | jonathanmaw, from your link, isn't it odd that it's got a .py extension but seems to be xml ? | 12:06 |
| juergbi | ok | 12:07 |
| tristan | jonathanmaw, or maybe gitlab is just rendering things really weirdly :-S | 12:07 |
| jonathanmaw | tristan: It didn't look like that a second ago, yeah | 12:07 |
| jonathanmaw | It looks normal when I follow the "view file" link, so it seems to be gitlab weirdness to me :S | 12:08 |
| tristan | jonathanmaw, also on a side note; I seem to recall that what freedesktop-sdk is doing for crates is a bit weird | 12:08 |
| tristan | jonathanmaw, I think there is some helper script you have to run right ? | 12:09 |
| tristan | jonathanmaw, from what I can tell, a proper crates plugin should be modeled after cs-shadow's new pip source plugin | 12:09 |
| *** bochecha has joined #buildstream | 12:12 | |
| jonathanmaw | tristan: looking at freedesktop-sdk 18.08, there doesn't appear to be any special script involved in getting the crates. there's special commands to run after building to get the flatpaks, but nothing special before invoking buildstream | 12:14 |
| tristan | jonathanmaw, looking at https://gitlab.com/BuildStream/bst-external/blob/e1732647e908a47222dfac4d152867d7f93b724e/bst_external/sources/crate.py, it seems the 'subdir' is completely redundant | 12:20 |
| tristan | i.e. you can just set the 'directory' to 'crates' and it will do the right thing, I don't see it writing outside of the crates directory | 12:21 |
| tristan | jonathanmaw, from elements/rust/cargo.bst: "# The following is generated with script generate_cargo_dependencies.py" | 12:22 |
| tristan | jonathanmaw, i.e. when you add rust dependencies, you have to run that - a proper crates plugin should do like pip does, and introspect what needs to be downloaded at `bst track` time, based on a local Cargo.toml file, and then serialize the resulting Cargo.lock into the resulting `ref`, using that to download what is needed at `bst fetch` time | 12:24 |
| tristan | I don't deny that that is a bit of work to do, and the current hack is certainly useful for the freedesktop-sdk folks | 12:24 |
| jonathanmaw | tristan: ah, okay. I didn't see that script. | 12:25 |
| tristan | jonathanmaw, But I think we certainly would not want to encourage this workflow by upstreaming it to a location where other people might start copying it and using it | 12:25 |
| tristan | As the ability to view previous sources in Source fetch & track is only added in master, people will probably need to use this method until 1.4 | 12:26 |
| *** edb has joined #buildstream | 12:40 | |
| gitlab-br-bot | buildstream: issue #610 ("Expose DownloadableFileSource to external plugin authors") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/610 | 12:43 |
| *** xjuan has joined #buildstream | 12:43 | |
| toscalix | can a native english speaker help here? https://gitlab.com/BuildStream/nosoftware/website/merge_requests/2#note_97334702 | 12:44 |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config for libtool .la files) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 12:48 |
| tristan | jonathanmaw, please try to remember to prefix branch names with your username (i.e. not like 610-expose-downloadablefilesource-to-external-plugin-authors) | 12:59 |
| tristan | I'm hoping to effect a cleanup of all the stale branches in git | 12:59 |
| qinusty | Branches -> Delete Merged Branches? | 13:00 |
| jonathanmaw | tristan: ah, ok. I thought using the branch generated by the issue was better because it links the branch to the issue | 13:00 |
| jonathanmaw | I'll keep that in mind | 13:01 |
| gitlab-br-bot | buildstream: merge request (tristan/remove-redundant-test->master: tests/frontend/workspaces.py: Removing some redundant tests) #741 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/741 | 13:04 |
| tristan | juergbi, your branch in !740 didn't cleanly apply in `bst-1.2` branch, please backport it | 13:07 |
| gitlab-br-bot | buildstream: merge request (valentindavid/workspace_reverse_dependencies->master: Invalidate reverse dependencies to scheduled element with workspace) #669 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/669 | 13:08 |
| gitlab-br-bot | buildstream: issue #461 ("Cache key confusion when elements depend on an open workspace") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/461 | 13:08 |
| gitlab-br-bot | buildstream: merge request (tristan/docs-version-badge->master: WIP: Release badges) #742 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/742 | 13:19 |
| gitlab-br-bot | buildstream: merge request (jonathan/expose-downloadablefilesource->master: Make DownloadableFileSource publically accessible) #743 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/743 | 13:31 |
| juergbi | tristan: !741 remove-redundant-test minor PEP8 failure. I'll push a fix such that I can also immediately put it in 1.2, unless you're already on it | 13:41 |
| tristan | oops :-S | 13:43 |
| tristan | juergbi, please thank you | 13:43 |
| tristan | I'm wrestling with rst :-S | 13:43 |
| gitlab-br-bot | buildstream: merge request (tristan/remove-redundant-test->master: tests/frontend/workspaces.py: Removing some redundant tests) #741 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/741 | 13:44 |
| gitlab-br-bot | buildstream: merge request (juerg/workspaced-dependencies-1.2->bst-1.2: Fix key invalidation for workspaced dependencies) #744 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/744 | 13:47 |
| gitlab-br-bot | buildstream: merge request (coldtom/autotools-libtool->master: Upstream freedesktop-sdk autotools config for libtool .la files) #683 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/683 | 13:55 |
| *** tlaxkit has joined #buildstream | 14:01 | |
| *** edb has quit IRC | 14:02 | |
| gitlab-br-bot | buildstream: merge request (jonathan/expose-downloadablefilesource->master: Make DownloadableFileSource publically accessible) #743 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/743 | 14:05 |
| tristan | Aha I see https://alligator.io/svg/hyperlinks-svg/ "This only works with inline SVGs, not with SVGs that are included in an <img> tag." | 14:10 |
| tristan | Well, that's sad :-/ | 14:11 |
| *** alatiera_ has joined #buildstream | 14:18 | |
| gitlab-br-bot | buildstream: merge request (tristan/remove-redundant-test->master: tests/frontend/workspaces.py: Removing some redundant tests) #741 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/741 | 14:25 |
| jonathanmaw | tristan: while I'm waiting for tests on DownloadableFileSource, iirc there was some discussion about using CAS as a common cache solution. Do you know where I can read more about that? I think it'd prove useful in my attempts to cache yaml parsing | 14:43 |
| gitlab-br-bot | buildstream: merge request (Qinusty/597-non-alias-url-fix->master: Fix ValueError traceback for URL without alias or URI scheme) #700 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/700 | 14:46 |
| tristan | jonathanmaw, scattered I think | 14:54 |
| tristan | jonathanmaw, My understanding is we want to use the CAS for this new thing called "SourceCache" which is a requisite for remote execution | 14:55 |
| jonathanmaw | I'm starting to acutely feel my ignorance while trying to write a cache for yaml parsing from scratch, so was hoping there would be something I could build from | 14:55 |
| tristan | jonathanmaw, in the back of my mind I've also been brewing a plan to shift integration commands to be done at the end of a build, and only if required at the beginning, and cache the integrations as well (which are not artifacts) | 14:56 |
| tristan | I'm not sure how that would work out but... it would be an idea to make `bst shell` snappy, with some tradeoff, and penalties depending on the shape of the build graph | 14:56 |
| tristan | shop closing... gotta scram :-/ | 14:57 |
| tristan | Almost hacked my badges to work when rendered on the page with <svg><use xlink:href="..."/></svg> and links clickable again | 14:58 |
| tristan | just lost the nice round edge, should be easy to fix | 14:58 |
| *** tristan has quit IRC | 15:01 | |
| gitlab-br-bot | buildstream: merge request (jonathan/expose-downloadablefilesource->master: Make DownloadableFileSource publically accessible) #743 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/743 | 15:13 |
| *** noisecell has quit IRC | 15:46 | |
| *** tristan has joined #buildstream | 15:53 | |
| jonathanmaw | tristan: I sorted out the public/private symbols distinction in https://gitlab.com/BuildStream/buildstream/merge_requests/743 | 15:58 |
| *** leopi has quit IRC | 15:58 | |
| *** leopi has joined #buildstream | 15:58 | |
| gitlab-br-bot | buildstream: merge request (tristan/docs-version-badge->master: WIP: Release badges) #742 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/742 | 16:03 |
| gitlab-br-bot | buildstream: merge request (tristan/docs-version-badge->master: WIP: Release badges) #742 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/742 | 16:06 |
| *** ChanServ sets mode: +o tristan | 16:15 | |
| tristan | That works: http://buildstream.gitlab.io/buildstream/main_about.html | 16:15 |
| tristan | but they disappear from the main README page displayed by gitlab, it doesnt like raw html embedded in it's rst | 16:16 |
| qinusty | Clicking snapshot gives interesting results | 16:16 |
| tristan | yeah | 16:17 |
| tristan | it needs a snapshot release to back it up | 16:17 |
| qinusty | ah | 16:17 |
| tristan | from master, a 1.3.1 will fix that | 16:17 |
| gitlab-br-bot | buildstream: merge request (chandan/pypi-badge->master: README.rst: Add status badges for PyPI release and Python versions) #719 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/719 | 16:18 |
| *** leopi has quit IRC | 16:25 | |
| *** leopi has joined #buildstream | 16:26 | |
| *** leopi has quit IRC | 16:29 | |
| gitlab-br-bot | buildstream: issue #316 ("Assertion error when building in non-strict mode") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/316 | 16:32 |
| gitlab-br-bot | buildstream: merge request (juerg/workspaced-dependencies-1.2->bst-1.2: Fix key invalidation for workspaced dependencies) #744 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/744 | 16:32 |
| gitlab-br-bot | buildstream: issue #461 ("Cache key confusion when elements depend on an open workspace") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/461 | 16:33 |
| *** leopi has joined #buildstream | 17:06 | |
| *** jonathanmaw has quit IRC | 17:09 | |
| gitlab-br-bot | buildstream: merge request (jjardon/fusepy->master: WIP: Depend on fusepy package instead internal copy) #745 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/745 | 17:17 |
| gitlab-br-bot | buildstream: merge request (jjardon/fusepy->master: WIP: Depend on fusepy package instead internal copy) #745 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/745 | 17:18 |
| gitlab-br-bot | buildstream: merge request (jjardon/fusepy->master: WIP: Depend on fusepy package instead internal copy) #745 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/745 | 17:19 |
| *** adds68 has quit IRC | 17:22 | |
| *** coldtom has quit IRC | 17:22 | |
| *** qinusty has quit IRC | 17:22 | |
| *** jennis has quit IRC | 17:22 | |
| gitlab-br-bot | buildstream: merge request (jjardon/fusepy->master: WIP: Depend on fusepy package instead internal copy) #745 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/745 | 17:27 |
| *** alatiera__ has joined #buildstream | 17:37 | |
| *** alatiera_ has quit IRC | 17:39 | |
| *** leopi has quit IRC | 17:46 | |
| *** leopi has joined #buildstream | 17:46 | |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 18:03 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 18:06 |
| *** dtf has joined #buildstream | 18:15 | |
| *** dtf_ has joined #buildstream | 18:15 | |
| *** dtf has joined #buildstream | 18:16 | |
| gitlab-br-bot | buildstream: issue #611 ("This repo doesn't follow PEP8 complately (as stated in the HACKING file)") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/611 | 18:27 |
| *** toscalix has quit IRC | 19:01 | |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 19:47 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 19:49 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 19:52 |
| *** xjuan has quit IRC | 20:31 | |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 20:59 |
| *** alatiera__ has quit IRC | 21:15 | |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 21:18 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 21:19 |
| *** tristan has quit IRC | 21:22 | |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle->master: WIP: Use pycodestyle instead pep8 python module) #638 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/638 | 22:01 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 22:12 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 22:13 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 22:20 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 22:20 |
| gitlab-br-bot | buildstream: merge request (jjardon/pycodestyle_fixes->master: Some pycodestyle (PEP8) fixes) #746 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/746 | 22:22 |
| *** rdale has quit IRC | 23:24 | |
| *** tlaxkit has quit IRC | 23:43 | |
| *** bochecha has quit IRC | 23:50 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!