{"push_id":2649859070,"size":1,"distinct_size":1,"ref":"refs/heads/2018-04","head":"cb54c26f6c824be2a98bd5799890f90ca87d2dc7","before":"569bd3bc52fad89536c7aa07f30870d3d8b6603a","commits":[{"sha":"cb54c26f6c824be2a98bd5799890f90ca87d2dc7","author":{"name":"Alexander Köplinger","email":"a4d3028640b16b8635f2d7ab9cbb07a71466c3cb@outlook.com"},"message":"Bump bockbuild to fix environment variables expansion bug (#9178)\n\nBrings in https://github.com/mono/bockbuild/pull/67.\r\n\r\nThis fixes the msbuild build problem where it'd crash with `error MSB4242: The SDK resolver \"NuGetSdkResolver\" failed to run. Unexpected failure reading NuGet.Config. Path: '@/external/bockbuild/builds/msbuild-15/artifacts/toolset/restore.proj/$HOME/.config/NuGet/NuGet.Config'.`.\r\n\r\nThe reason is that bockbuild exported the `XDG_CONFIG_HOME` environment variable with the value `$HOME/.config`. The problem is that the `$HOME` in there is never expanded so it just stays as the literal value. \r\n\r\n`XDG_CONFIG_HOME` is later used by e.g. `Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData)` which is what nuget uses to construct the path to NuGet.config - hence why we end up with the weird path.\r\n\r\nWe now just expand the variables in bockbuild before we pass them on.\r\n\r\nFixes https://github.com/mono/mono/issues/9179","distinct":true,"url":"https://api.github.com/repos/mono/mono/commits/cb54c26f6c824be2a98bd5799890f90ca87d2dc7"}]}
{"actor":{"display_login":"akoeplinger"}}