infoomatic wrote in <[email protected]>: > I kept my VM around, and upgraded to Beta 2 a few hours after announcement. > However, I have noticed that only few packages upgraded from b1 to b2, so in > the end I had a mix of b1 and b2 packages installed. Is this fine and as it > should be for future installations?
this is normal. for each build, only packages which have actually changed get a new version, and not much changed overall between b1 and b2. > [...] Now having packages with b1, b2, b3 it seems a bit odd since I > don't know if the pkg upgrade just had an error or the mirror was not > in sync or something else did not work the way it should. this is not that different from how freebsd-update worked, e.g. when an update doesn't touch the kernel, so you're running 15.0-RELEASE-p1 but uname says 15.0-RELEASE. at least with packages, you can tell what the actual installed version is, and compare it to the versions listed in the EN/SA. the alternative would be that updating a single file for 15.0-RELEASE-p1 would require building a new version of every package just to update the version number, which is not reasonable. > Will all new package versions be accompanied by erratas or security > announcements once 15.0-RELEASE is released? all updates to a release branch (e.g., 15.0-RELEASE) are published as EN/SA.
signature.asc
Description: PGP signature
