Le Wed, Apr 14, 2021 at 10:39:05AM -0600, Aaron Bieber a écrit :
>
> Daniel Jakots writes:
>
> > On Wed, 14 Apr 2021 13:24:37 +0200, Denis Fondras
> > wrote:
> >
> >> Here is the updated diff :
> >
> > Thanks it works for me. ok danj@
> >
> > Out of curiosity, how did you find the V value? It do
Daniel Jakots writes:
> On Wed, 14 Apr 2021 13:24:37 +0200, Denis Fondras
> wrote:
>
>> Here is the updated diff :
>
> Thanks it works for me. ok danj@
>
> Out of curiosity, how did you find the V value? It doesn't match the
> release name on github which is where I thought I would have found i
On Wed, 14 Apr 2021 13:24:37 +0200, Denis Fondras
wrote:
> Here is the updated diff :
Thanks it works for me. ok danj@
Out of curiosity, how did you find the V value? It doesn't match the
release name on github which is where I thought I would have found it.
On 2021/04/13 23:55, Denis Fondras wrote:
> -V = 2019-03-20T21-29-03Z
> -GH_PROJECT = mc
> -GH_TAGNAME = RELEASE.${V}
> +V = 2021-03-22T20-27-01Z
> +CID =c3cae160b35d53056e454386c09850a158c049ec
> +MODGO_MODNAME = github.com/minio/mc
The shell `` are not idea
Le Tue, Apr 13, 2021 at 02:02:42PM -0400, Daniel Jakots a écrit :
>
> Did you try login through the web interface? Here it fails with "Invalid
> UI version in the JSON-RPC response". That said my mastodon instance
> seems to be able to upload content, which is the only thing that I care
> about :)
Stuart Henderson writes:
> On 2021/04/13 14:02, Daniel Jakots wrote:
>> This is using a random commit from upstream, isn't it? Would it be
>> possible to use a release/tag instead?
>
> ahahahahaa
>
> You're not familiar with the ways of the go stuff are you ;)
A bit more info on this. Since min
On 2021/04/13 14:02, Daniel Jakots wrote:
> This is using a random commit from upstream, isn't it? Would it be
> possible to use a release/tag instead?
ahahahahaa
You're not familiar with the ways of the go stuff are you ;)
On Sun, 11 Apr 2021 09:33:37 +0200, Denis Fondras
wrote:
> Here is an update to the "latest" version of MinIO.
Thanks for working on it! A few comments inline.
> Can someone test on aarch64 to check if BROKEN can be removed ?
Given they use a recent version of x/sys/unix, it should be fine.
>
