Re: git: b5b4b67baf4b - main - sysutils/iocage-devel: update to 1.6.20240531
- In reply to: Michael Gmelin : "Re: git: b5b4b67baf4b - main - sysutils/iocage-devel: update to 1.6.20240531"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 12 Jun 2024 12:27:14 UTC
Am 2024-06-12 09:35, schrieb Michael Gmelin: >> On 12. Jun 2024, at 09:26, Gleb Popov <arrowd@freebsd.org> wrote: > > On Wed, Jun 12, 2024 at 3:20 AM Neel Chauhan <nc@freebsd.org> wrote: > The branch main has been updated by nc: URL: > https://cgit.FreeBSD.org/ports/commit/?id=b5b4b67baf4bcc3e267da74fb6e4d8a69c1673d5 > commit b5b4b67baf4bcc3e267da74fb6e4d8a69c1673d5 Author: Neel > Chauhan <nc@FreeBSD.org> AuthorDate: 2024-06-11 20:20:35 +0000 Commit: > Neel Chauhan <nc@FreeBSD.org> CommitDate: 2024-06-11 20:20:35 +0000 > sysutils/iocage-devel: update to 1.6.20240531 > Should this really be named -devel? 1.6 is a proper release. Yes it should. After being stuck on 1.2 for years, the project was forked and the new maintainer released 1.3, 1.4, 1.5, and 1.6 all within about 48 hours. There still seem to be some issues, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269298, but those could be due to the python upgrade. Yes, the one remaining issue I see is because of python 3.11. And the fix I've quoted works for me. > So given the new release process, applying these patches to the -devel > port is very welcome to be able to actually test if things are stable. > > I'll do some more thorough real-world testing myself and, once done, > update devel/iocage. Works for my use case, when I fix the python 3.11 issue by hand. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF