Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 May 2022 18:16:18 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 263823] sysutils/iocage: most functionality broken on 14.0-CURRENT
Message-ID:  <bug-263823-7788-YSrvu4Q5Se@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-263823-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-263823-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263823

Michael Gmelin <grembo@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|ports-bugs@FreeBSD.org      |grembo@FreeBSD.org

--- Comment #1 from Michael Gmelin <grembo@FreeBSD.org> ---
@Alan: Well, simply updating is easier said than done, as the latest release
upstream tagged is actually 1.2 (same version as the port).

So first we would have to decide which commit to target (or ask upstream to=
 tag
a release) and then do extensive testing, as the target platform seems to b=
e an
iXsystems product and not vanilla FreeBSD (at least in the past it could br=
eak
in various ways on update).

So maybe patching the existing 1.2 port is the more realistic short-term
solution.

Do you have the time/resources to test devel/iocage-devel and see if that w=
orks
for you/is stable?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263823-7788-YSrvu4Q5Se>