From owner-freebsd-emulation@freebsd.org Sat May 1 09:50:35 2021 Return-Path: Delivered-To: freebsd-emulation@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 521D65F98CE for ; Sat, 1 May 2021 09:50:35 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FXPcW0wTlz3t5p for ; Sat, 1 May 2021 09:50:35 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by mailman.nyi.freebsd.org (Postfix) id 1F7075F98CD; Sat, 1 May 2021 09:50:35 +0000 (UTC) Delivered-To: emulation@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1E0C85F9844 for ; Sat, 1 May 2021 09:50:35 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FXPcV4Wb3z3t5n for ; Sat, 1 May 2021 09:50:34 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by freefall.freebsd.org (Postfix) id 8FF339321; Sat, 1 May 2021 09:50:34 +0000 (UTC) Delivered-To: vbox@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "mx1.freebsd.org", Issuer "R3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 8ABC69239 for ; Sat, 1 May 2021 09:50:34 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FXPcV2Zqpz3t3l; Sat, 1 May 2021 09:50:34 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4FXPcM3Qmjz6dWZ; Sat, 1 May 2021 11:50:27 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id ijKCS9Rkq3qU; Sat, 1 May 2021 11:50:25 +0200 (CEST) Subject: Re: FreeBSD Port: virtualbox-ose-6.1.20 outdated To: Dutchman01 , vbox@FreeBSD.org Cc: ports@FreeBSD.org References: <000001d73e17$0f756240$2e6026c0$@quicknet.nl> From: Guido Falsi Message-ID: <6b051e8f-93f5-85b7-c827-b50df62b4363@madpilot.net> Date: Sat, 1 May 2021 11:50:25 +0200 In-Reply-To: <000001d73e17$0f756240$2e6026c0$@quicknet.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FXPcV2Zqpz3t3l X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 May 2021 09:50:35 -0000 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