Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: Update to minio-0.20241107
To:
Daniel Jakots <danj@chown.me>
Cc:
Peter Hessler <phessler@theapt.org>, ports@openbsd.org
Date:
Sat, 9 Nov 2024 19:14:58 +0000

Download raw body.

Thread
On 2024/11/09 11:20, Daniel Jakots wrote:
> On Sat, 9 Nov 2024 16:52:46 +0100, Peter Hessler <phessler@theapt.org>
> wrote:
> 
> > On 2024 Nov 09 (Sat) at 10:17:41 -0500 (-0500), Daniel Jakots wrote:
> > :Hi,
> > :
> > :Here's another attempt to update the minios (for now the server
> > part). :The status didn't change since my previous attempt so I let
> > you read it, :subject: Update to minio-0.20231214
> > :on this exact mailing list, also available in the archives:
> > :https://marc.info/?l=openbsd-ports&m=170329594113590&w=2
> > :
> > :Comments? OK?
> > :
> > :Cheers,
> > :Daniel
> > 
> > Does this still fuck over the ability to run 
> > "root /var/www/minio/export/bucket;" in a webserver?  if so, my
> > objection and comments still apply.
> 
> I have no indication that would lead me to believe otherwise, but I
> haven't looked.
> 
> > separately, the provided login file for minio is broken by default,
> > since the user will need to edit the file to set the password.  don't
> > they have a less garbage system for that?
> 
> I don't think so, but you're welcome to look at it.

I think that's the "MinIO gateway and the related filesystem mode"
that was removed, it didn't sound like it would be coming back.

> Your negativity doesn't help anyone.

Understandable though, it seems like there's no way to change over
in-place and you need to stand up new storage (quite possibly on
additional hardware), disable writes to the old installation, mirror (I
am guessing this will be Quite A Lot Of Data on a busy-ish mastodon
instance using this as a storage backend), and wait for tbat to finish
before re-enabling.

> I don't think it's fair to put that burden on the maintainer, since as
> far as I can tell, you're the only one having this weird setup.

But you said this:

: I tried to update then and... minio wouldn't start because I was
: actually impacted by the deprecation.
: 
: I don't have the exact error message anymore, but it's from
: cmd/format-erasure.go:
: return "", fmt.Errorf(`found backend type %s, expected %s or %s - to migrate to a \
: supported backend visit \
: https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html`, \
: meta.Format, formatBackendErasure, formatBackendErasureSingle)
: 
: I've no idea what the minio on OpenBSD users are running, and so whether
: they will be impacted. So I guess the best move is to assume they are.
: 
: To migrate away from the deprecated mode, the procedure is documented:
: https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html

Providing packages for both versions will certainly help users across
that bump if they want to upgrade, as well as helping people who want
to keep their existing setup.