> Is it that 4.1.10 was released less than 24h ago and the ports > are not updated yet?
Not at all, just an inventory. Lag time on new releases is totally understandable. They need ported and tested. And life is first priority :) > Is it because 4.1.8 packages for 8-stable are not available? Using the packages-major-stable example for 8 and 9, we have this FTP index. Notably, RELENG_8 i386 is missing the base 'virtualbox-ose' package. I think it used to be there last month. 8sa: 69174652 Mar 08 02:43 virtualbox-ose-4.1.8.tbz 8sa: 1039991 Mar 08 22:58 virtualbox-ose-additions-4.1.8.tbz 8sa: 110285 Mar 07 22:13 virtualbox-ose-kmod-4.1.8_1.tbz 8sa: 107500 Mar 08 02:12 virtualbox-ose-kmod-legacy-4.0.16.tbz 8si: 953365 Feb 29 14:33 virtualbox-ose-additions-4.1.8.tbz 8si: 109301 Feb 28 20:41 virtualbox-ose-kmod-4.1.8_1.tbz 8si: 106336 Feb 29 01:05 virtualbox-ose-kmod-legacy-4.0.16.tbz 9sa: 69315786 Mar 05 22:56 virtualbox-ose-4.1.8.tbz 9sa: 1062649 Mar 06 09:15 virtualbox-ose-additions-4.1.8.tbz 9sa: 110743 Mar 05 17:46 virtualbox-ose-kmod-4.1.8_1.tbz 9sa: 108026 Mar 05 22:33 virtualbox-ose-kmod-legacy-4.0.16.tbz 9si: 64462589 Feb 08 10:42 virtualbox-ose-4.0.14.tbz 9si: 1052081 Feb 09 06:06 virtualbox-ose-additions-4.0.14.tbz 9si: 106199 Jan 30 18:51 virtualbox-ose-kmod-4.0.14.tbz 9si: 96474 Jan 30 20:32 virtualbox-ose-kmod-legacy-3.2.12_3.tbz 9si: 53094010 Feb 09 07:13 virtualbox-ose-legacy-3.2.12_3.tbz > Is it because the packages are not identical to the current ports? The svn port -> FTP building process is presumed to have some delay. Likely because, even though parallelism might yield a complete build of all ports in a few days, it is surely and rightly checkpointed by humans to prevent automated mayhem :) _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
