Date: Sat, 1 May 2021 11:50:25 +0200 From: Guido Falsi <mad@madpilot.net> To: Dutchman01 <dutchman01@quicknet.nl>, vbox@FreeBSD.org Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: virtualbox-ose-6.1.20 outdated Message-ID: <6b051e8f-93f5-85b7-c827-b50df62b4363@madpilot.net> In-Reply-To: <000001d73e17$0f756240$2e6026c0$@quicknet.nl> References: <000001d73e17$0f756240$2e6026c0$@quicknet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/05/21 01:17, Dutchman01 via freebsd-emulation wrote: > bugfix release 6.1.22 is released! > > > > There is need to upgrade from 6.1.20 to 6.1.22 This is known, automatic notifications already reached the mailing list yesterday at 8:55 UTC The notification actually contained an error and I already reacted to that by adding the PORTSCOUT variable to the legacy ports. I'm testing the new release and should be able to commit the update to the tree later. It looks like a n easy update, but testing this ports requires time. Time to compile it (and it's heavy dependencies) on multiple OS version, time to run it to verify there are no big regressions. This time the update looks easy with no need to modify patches or add new ones, but this looks like an exception not the rule. When someone (like me this time) is able to start working on the update right away it's anyway impossible to get it in the tree in less than 24/48 hours in the best scenarios. Much more it the update proves difficult due to incompatibilities or need to modify patches. It could also happen for committers to be all busy or unavailable so a week or two could also happen. Anyway, as stated, I should be able to commit the update today. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6b051e8f-93f5-85b7-c827-b50df62b4363>