Hi all,
> Looks like golang-google-cloud FTBFS as a result of golang-google-genproto
> 0.0~git20190111.db91494-1. This is going to cause a lot of packages to be
> removed.
>
> I took a stab at updating golang-google-cloud to the latest release
Hmm, please correct me if I am wrong, but I think
Antony, Tobias,
I am looking at updating x/tools and I see two things:
* Tobias: you prepared a new release, but did not upload. Was there any
reason for this? I see tests failing, maybe that was the reason?
* Anthony: the last upload was made from the "release-branch.go1.10"
branch; should we c
Am 27.01.2019 um 21:02 schrieb Martín Ferrari:
> Antony, Tobias,
>
> I am looking at updating x/tools and I see two things:
>
> * Tobias: you prepared a new release, but did not upload. Was there any
> reason for this? I see tests failing, maybe that was the reason?
Hi Martín,
thanks for taking
uploaded, thanks for working on this!
-rt
On Sun, Jan 20, 2019 at 3:45 AM Arnaud Rebillout <
arnaud.rebill...@collabora.com> wrote:
> Dear Go team,
>
> According to the announce at [1], etcd started to provide a go vanity
> import path 'go.etc.io'. Consequently, some packages started using it.
> On Jan 27, 2019, at 11:41 AM, Sascha Steinbiss wrote:
>
> Hi all,
>
>> Looks like golang-google-cloud FTBFS as a result of golang-google-genproto
>> 0.0~git20190111.db91494-1. This is going to cause a lot of packages to be
>> removed.
>>
>> I took a stab at updating golang-google-cloud to