I was able to upgrade to 13.2-RELEASE reddit / freebsd ---------------------------------------------------------------------- ImageJPEG · 2023-04-08 20:31 So far looking good. Just out of curiosity, is it standard practice to allow someone to upgrade before a release statement? I'm not seeing it yet on [freebsd.org](https://freebsd.org) as something that can be downloaded to upgraded to. ---------------------------------------------------------------------- arrogantvindictve · 2023-04-08 20:41 If you look at the release schedule, you will see that they were starting to build the release build as of the 7th. So that's when it would become available. https://www.freebsd.org/releases/13.2R/schedule/ ---------------------------------------------------------------------- perciva · 2023-04-09 00:02 It takes a while for mirrors to sync. You got one of the faster mirrors. ;-) Announcement will be on Tuesday. ---------------------------------------------------------------------- EstablishmentBig7956 · 2023-04-09 01:34 13.2 how did you ever do that? Nothing on the website yet 11 April 2023 uname -a FreeBSD FBSD13-2RC6.yeahbabyyeah 13.2-RC6 FreeBSD 13.2-RC6 releng/13.2-n254616-a92e3fa2ade5 GENERIC amd64 that's as far as they have gotten ---------------------------------------------------------------------- AhmedNabilG · 2023-04-09 02:01 It's available to download from official site https://download.freebsd.org/ftp/releases/ISO-IMAGES/ ---------------------------------------------------------------------- Kumba42 · 2023-04-09 02:10 I can only speak for doing this with binary updates via freebsd- update, but when waiting on a new FreeBSD release to drop, I usually keep an eye on one of the FTP release folders for the new ISO downloads. Those seem to always drop first, usually early morning UTC (I think); e.g., 5AM-7AM. Once those ISO images appear, take their creation timestamp and add about ~8-12 hours. That will be the rough time to begin to use freebsd-update to check for the new release signature file on the mirrors. If freebsd-update can't find the signature file, wait at least an hour before trying again. During major releases (12.x -> 13.0, etc), you sometimes have to be a bit more patient, likely because there's going to be a larger changeset between versions that needs to sync across the mirrors, before that signature file appears. I've sometimes had to wait until the day of release in the schedule before freebsd-update will find the new signature on the update servers. If you want speedier updates, there's an AWS server that I don't think is documented anywhere notable (someone correct me if wrong). Edit `/etc/freebsd-update.conf` and change **ServerName** to use `dualstack.aws.update.freebsd.org`. For me, it is much faster than the default update server, but YMMV. Happy updating! ---------------------------------------------------------------------- perciva · 2023-04-09 04:01 The exact timing of when bits become available depends among other things on when a human looks at logs, says "yup this looks reasonable", and runs the "publish everything" command. Builds usually start soon after midnight UTC and the first publicly visible sign will typically be EC2 AMIs, since those are uploaded automatically. After that, bits will land on ftp-master and propagate out to the mirrors. Then the security team builds FreeBSD Update bits and those propagate out. The aws endpoint you mention exists to make things faster for EC2, but to quote Amazon "it's ok if other people discover it and decide to use it". It's actually a network of 7 mirrors spanning 6 continents, with IP unicast used to steer traffic to the closest mirror. The same mirrors serve up the Portsnap bits, incidentally. ---------------------------------------------------------------------- Kumba42 · 2023-04-09 04:41 >The aws endpoint you mention exists to make things faster for EC2, but to quote Amazon "it's ok if other people discover it and decide to use it". It's actually a network of 7 mirrors spanning 6 continents, with IP unicast used to steer traffic to the closest mirror. The same mirrors serve up the Portsnap bits, incidentally. Basically anycast, just like the root nameservers. Makes sense. And I am aware of the portsnap variant, too. Been using both for quite a while :) ---------------------------------------------------------------------- perciva · 2023-04-09 06:57 Err yes, I meant anycast. Sorry, it's been a long day. ---------------------------------------------------------------------- grahamperrin · 2023-04-09 08:55 > … Nothing on the website yet … Please see the previous comment. Announcement will be on Tuesday. In the meantime: * at the most recent commit shows the change from `RC6` to `RELEASE` – and so on. ---------------------------------------------------------------------- grahamperrin · 2023-04-09 08:57 Also , although I should discourage people from downloading/upgrading until after the release announcement is made. ---------------------------------------------------------------------- grahamperrin · 2023-04-09 09:02 > … Builds usually start soon after midnight UTC … Shall I make 7 April 2023 the *actual* date at ? ---------------------------------------------------------------------- grahamperrin · 2023-04-09 09:09 ### Locally modified files With freebsd-update(8) on RC6: … The following files are affected by updates. No changes have been downloaded, however, because the files have been modified locally: /var/db/etcupdate/log … I assume that `/var/db/etcupdate/log` is negligible in this context. ---------------------------------------------------------------------- Kumba42 · 2023-04-09 09:34 No worries, fully understood! Thanks for the effort and looking forward to 14.0 in a few more months! ---------------------------------------------------------------------- jeb0921 · 2023-04-09 14:05 I was able to update my system this morning also. Everything went very smooth ---------------------------------------------------------------------- daemonpenguin · 2023-04-09 14:46 > Just out of curiosity, is it standard practice to allow someone to upgrade before a release statement? Obviously they need to upload the ISO and package files before making the announcement. So virtually every project "allows" you to upgrade before an announcement is made. However, it's a really bad idea to try to upgrade before the announcement. You don't know if there is still testing going on which would require a new round of fixes and testing, you won't get any support if you botch the upgrade, you won't get the benefit of early errata reports. This isn't a matter of "standard practises", it's just the way uploading and syncing to public mirrors works. You're welcome to shoot yourself in the foot if you want. ---------------------------------------------------------------------- grahamperrin · 2023-04-09 15:49 +1 to awaiting the announcement, in most cases. ---- > … you won't get any support if you botch the upgrade … I'd expect **good** support. ---- Upgrades aside: if *fresh installation* is from an image and if there's a problem, the user might be asked to await publication of checksums … that type of thing. ---------------------------------------------------------------------- perciva · 2023-04-09 16:36 I'm in the process of updating (well, adding) a bunch of bits to the 13.2R directory, so please hold off for now if you haven't done it yet. I can include the date when I do the other changes. ---------------------------------------------------------------------- grahamperrin · 2023-04-09 16:49 OK. On hold. ---------------------------------------------------------------------- AhmedNabilG · 2023-04-09 19:52 I'm update today from freebsd 13.1 to 13.2 ---------------------------------------------------------------------- EstablishmentBig7956 · 2023-04-09 20:18 Okay I'm retracting what I said https://download.freebsd.org/releases/ISO-IMAGES/13.2/ ---------------------------------------------------------------------- [deleted] · 2023-04-10 01:19 [deleted]