diff options
Diffstat (limited to 'UPDATING')
-rw-r--r-- | UPDATING | 104 |
1 files changed, 104 insertions, 0 deletions
@@ -5,6 +5,110 @@ they are unavoidable. You should get into the habit of checking this file for changes each time you update your ports collection, before attempting any port upgrades. +20250510: + AFFECTS: users of net-p2p/bitcoin and/or net-p2p/bitcoin-daemon + AUTHOR: kbowling@FreeBSD.org + + 29.x is the last release series that will support the legacy BDB wallet + format. We are already doing this awkwardly since the format is BDB 4.8 + and we are building with BDB 5. This will be removed in 30.0 later this + year. + + You should upgrade your wallet now if you are still using a legacy wallet. + + Instructions: + https://github.com/bitcoin/bitcoin/blob/29.x/doc/managing-wallets.md#migrating-legacy-wallets-to-descriptor-wallets + + This release switches to CMake which results in a major refacoring of + the port and underlying build. The result seems good, but please + provide feedback if there are any unexpected changes or problems. + + This release dropped UPnP support due to security concerns. NAT-PMP is + implemented as an alternative. + +20250506: + AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run + AUTHOR: kbowling@FreeBSD.org + + The default version of PostgreSQL has been switched from 16 to 17. + The upgrade procedure can use up twice the space the databases + currently needs. If you have a big amount of stored data take a + closer look at the manpage of pg_upgrade for avoidance and/or + speedup of the upgrade. + + The upgrade instructions consider a basic usage and do not match + complex scenarios like replication, sharding, or similar. + + Upgrade instructions: + + First stop your PostgreSQL, create PostgreSQL-binaries and backup your data. + If you have another Version of PostgreSQL installed, for example 16, your + files are named according to this. + + # service postgresql stop + # pkg create postgresql16-server postgresql16-contrib + # mkdir /tmp/pg-upgrade + # tar xf postgresql16-server-16.8.pkg -C /tmp/pg-upgrade + # tar xf postgresql16-contrib-16.8.pkg -C /tmp/pg-upgrade + # pkg delete -f databases/postgresql16-server databases/postgresql16-contrib databases/postgresql16-client + + Now update PostgreSQL: + + pkg user: + # pkg install databases/postgresql17-server databases/postgresql17-contrib + # pkg upgrade + + Portmaster users: + # portmaster databases/postgresql17-server databases/postgresql17-contrib + # portmaster -a + + Portupgrade users: + # portinstall databases/postgresql17-server databases/postgresql17-contrib + # portupgrade -a + + After installing the new PostgreSQL version you need to convert + all your databases to new version: + + # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data17 -U postgres" + # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data16/ -B /usr/local/bin/ -D /var/db/postgres/data17/ -U postgres " + + Now the migration is finished. You can start PostgreSQL again with: + + # service postgresql start + + ATTENTION: + 1) If you use non-default initdb options, you have to adjust the initdb-command accordingly + +20250503: + AFFECTS: users of sysutils/bastille + AUTHOR: jdhurtado@orbiware.com + + The `rcorder` has been deprecated, and new `boot` and `priority` options have + been added to the jails. A boot file will be created with default values of + `boot=on` and `priority=99` on jail creation. For existing jails, the boot file + will be generated on the next subcommand execution to the jail. If you want to + generate the file for all the jails, you can use `bastille restart ALL` to fill + in the defaults. To change these values, use `bastille config TARGET set boot off` + or `bastille config TARGET set priority 10` or some other number according to + your needs. + +20250503: + AFFECTS: users of security/libressl + AUTHOR: brnrd@FreeBSD.org + + The port has been updated to the latest stable version 4.1 of LibreSSL. + The shared library versions of the libraries have been bumped. + + After upgrading, manually update all packages that depend on any of the + libraries provided by LibreSSL (libssl, libcrypto and libtls) since the + versions of these libraries have changed. Normally, you can obtain the + list of dependent software by running the following command: + + # pkg info -r libressl + + Then you should rebuild all ports depending on libressl to avoid dangling + shared library dependencies. + 20250502: AFFECTS: users of databases/redis AUTHOR: yasu@FreeBSD.org |