This file documents some of the problems you may encounter when upgrading your ports. We try our best to minimize these disruptions, but sometimes 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. 20230511: AFFECTS: users of net-mgmt/py-netbox-secretstore AUTHOR: kai@FreeBSD.org Upstream no longer maintains py-netbox-secretstore which it is not compatible with NetBox 3.5 or newer. To ensure compatibility with newer releases of NetBox, the py-netbox-secrets plugin should be used instead. To migrate from security/py-netbox-secretstore to security/py-netbox-secrets please do following steps: 1. Make a backup. 2. Install security/py-netbox-secrets 3. Enable both plugins by updating the following line in the netbox configuration (e.g. /usr/local/share/netbox/netbox/configuration.py): PLUGINS = ['netbox_secretstore', 'netbox_secrets'] 4. Run NetBox migrations: # cd /usr/local/share/netbox # python3.9 manage.py migrate 5. Re-adjust the indices for the netbox-secrets plugin: # python3.9 manage.py sqlsequencereset netbox_secrets > output.sql 6. Run the output of the previous command in the database, e.g.: # psql -d NETBOXDB < output.sql 7. You can now remove netbox-secretstore from the application by removing it from the PLUGINS line in the netbox configuration: PLUGINS = ['netbox_secrets'] 8. Collect static files of the netbox-secrets plugin: # python3.9 manage.py collectstatic --no-input 9. Restart WSGI/httpd environment (supervisord/apache/nginx/etc.). 10. You may have clean up your database of the old tables manually, e.g.: DROP TABLE netbox_secretstore_secret; DROP TABLE netbox_secretstore_secretrole; DROP TABLE netbox_secretstore_sessionkey; DROP TABLE netbox_secretstore_userkey; 11. Uninstall security/py-netbox-secretstore. 20230505: AFFECTS: users of mail/mutt AUTHOR: dereks@lifeofadishwasher.com The patches included in the mail/mutt port will be removed in approximately a month making the port more inline with upstream. If you require any of these features most are available in mail/neomutt or it's possible to use EXTRA_PATCH_TREE to patch a port when building locally. 20230504: AFFECTS: users of sysutils/py-mqttwarn AUTHOR: dvl@FreeBSD.org The redis optoin REISPUB has been renamed to REDISPUB You should update any make.conf setting etc which refer to this. e.g. change sysutils_py-mqttwarn_REISPUB to sysutils_py-mqttwarn_REDISPUB 20230416: AFFECTS: users of databases/mongodb50 and databases/mongodb44 AUTHOR: ronald@FreeBSD.org MongoDB removed the settings 'fork' and 'pidFilePath' from the default etc/mongodb.conf file. This does not affect mongod started by etc/rc.d/mongod as the settings are passed as arguments. Please verify custom uses of mongod. 20230414: AFFECTS: users of www/gitea AUTHOR: fernape@FreeBSD.org Gitea 1.19.1 contains a breaking change. actions unit has ben renamed to to repo.actions. 20230407: AFFECTS: users of devel/sonarqube-community AUTHOR: netchild@FreeBSD.org You need to make sure to update missing and changed values in PREFIX/libexec/sonarqube/conf/sonar.properties from PREFIX/libexec/sonarqube/conf/sonar.properties.sample 20230318: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 3.6 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. 20230315: AFFECTS: users of lang/ruby30 AUTHOR: yasu@FreeBSD.org The default ruby version has been updated from 3.0 to 3.1. If you compile your own ports you may keep 3.0 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 3.0 as default version # DEFAULT_VERSIONS+=ruby=3.0 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkg, simply upgrade: # pkg upgrade If you do not use pkg, please check entry 20190420. The description there should also work for this version. 20230314: AFFECTS: users of security/openssl-devel AUTHOR: brnrd@FreeBSD.org Users using DEFAULT_VERSIONS=ssl=openssl-devel must update their configuration to DEFAULT_VERSIONS=ssl=openssl30 or openssl31. 20230313: AFFECTS: users of databases/sqlite3 AUTHOR: fuz@FreeBSD.org Due to various ports not being prepared for this change (see 20230227 entry), the DQS option of databases/sqlite3 has been reenabled as a stop gap measure. It is scheduled to be disabled again for good no earlier than 20240101, giving downstream software authors more time to fix their queries. See also: https://sqlite.org/quirks.html#dblquote 20230311: AFFECTS: users of net/dshell AUTHOR: nobutaka@FreeBSD.org net/dshell now depends on net/py-pcapy-ng instead of net/py-pcapy. Because net/py-pcapy-ng conflicts with net/py-pcapy, please uninstall py39-pcapy with the following command before upgrading: # pkg delete -f py39-pcapy 20230310: AFFECTS: users of net-mgmt/unifi7 AUTHOR: otis@FreeBSD.org The mongodb dependency has been changed from 36 to 44, as MongoDB 3.6 is long out out support and end of life. The upgrade path should be as following: 1. Take a backup from within the unifi7 application PRIOR to updating! 2. Stop the unifi7 service (if running) 3. Copy the "backup" directory from LOCALBASE/share/java/unifi/data to a safe location. Also copy keystore and system.properties if you have made any modifications to those files 4. Remove files and directories under LOCALBASE/share/java/unifi/data 5. Upgrade the package 6. Copy the "backup" directory from a safe location back to LOCALBASE/share/java/unifi/data 7. Start the service 8. Restore the configuration from backup As an optional step, review system.properties and keystore to merge any manual modifications you have made (this has to be done with the application stopped) 20230310: AFFECTS: user of benchmarks/ddosify AUTHOR: fernape@FreeBSD.org keep-alive is removed from config file. In default mode, the engine will use keep-alive for all requests. If you want to disable keep-alive for a step, you can add Connection: close header to the step. 20230306: AFFECTS: users of www/qt5-webengine AUTHOR: kai@FreeBSD.org Users that upgrade www/qt5-webengine without using pkg/poudriere might experience failures due to conflicts with the installed version of 5.15.2. In that case, pkg delete -f the qt5-webengine package before building the updated version. 20230304: AFFECTS: users of accessibility/atk and accessibilty/at-spi2-atk AUTHOR: tcberner@FreeBSD.org The packages accessibility/atk and accessibility/at-spi2-atk have been integegrated upstream into at-spi2-core. Users of these packages can manually remove them prior to updating accessibility/at-spi2-core using pkg delete -f atk at-spi2-atk if the pkg update process fails due to conflicting files. 20230227: AFFECTS: users of databases/sqlite3 AUTHOR: fuz@FreeBSD.org Option DQS is now disabled by default. This option controls the "double quoted string literals are accepted" quirk, permitting the use of double quotes around string literals if enabled. Users who rely on this quirk need to manually build databases/sqlite3 with the DQS option enabled. See also: https://sqlite.org/quirks.html#dblquote 20230227: AFFECTS: users of mail/py-spf-engine AUTHOR: yasu@FreeBSD.org Default configuration file path of pyspf-milter has changed. Since it looks for ${PREFIX}/etc/etc/pyspf-milter/pyspf-milter.conf now, you should edit the file if you run pyspf-milter. Alternatively you can specify other configuration file path by setting pyspf_milter_conffile variable in /etc/rc.conf. 20230222: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org 1. Please make sure that the PostgreSQL server for the NetBox instance is running version 11 or higher. This is because PostgreSQL 10 is End-of-Life since November 2022 and Django 4.1 requires PostgreSQL 11 as a minimum. 2. Please also check the pkg-message and the changelogs for further info. 20230218: AFFECTS: users of databases/mysql57-(server|client) AUTHOR: joneum@FreeBSD.org The default MySQL version has been updated from 5.7 to 8.0. If you compile your own ports you may keep 5.7 as the default version by adding the following lines to your /etc/make.conf file: # # Keep MySQL 5.7 as default version # DEFAULT_VERSIONS+=mysql=5.7 If you wish to update to the new default version, you need to first stop any running server instance. Then, you will need to follow these steps, depending on installed packages. # pkg set -o databases/mysql57-client:databases/mysql80-client # pkg set -o databases/mysql57-server:databases/mysql80-server # pkg upgrade 20230213: Affects: users of sysutils/nut* AUTHOR: cy@FreeBSD.org The nut file ownership fixups due to the UID/GID change from uucp/uucp to nut/nut may not be desireable for all users. Some users with custom file ownership may wish ownership to remain untouched. This revision to the nut family of ports/packages allows users to optionally disable automatic fixup of nut file ownership. 20230213: AFFECTS: users of security/logcheck AUTHOR: yasu@FreeBSD.org Since 1.4.1 ${PREFIX}/etc/logcheck/logcheck.logfiles is empty and files to be checked by logcheck are specified in ${PREFIX}/etc/logcheck/logcheck.logfiles.d/syslog.logfiles. So if you previously edited the former, then you should edit the latter now. 20230210: AFFECTS: users of mail/fetchmail AUTHOR: fernape@FreeBSD.org Fetchmail now warns about OpenSSL before 1.1.1s or 3.0.7, and rejects wolfSSL older than 5.5.1. 20230209: AFFECTS: users of audio/jack AUTHOR: fernape@FreeBSD.org audio/jack 1.9.22 fixes an issue with latency correction on FreeBSD. Latency correction parameters have to be measured again after update. 20230130: AFFECTS: users of USES=nodejs, www/node*, www/npm* and www/yarn* AUTHOR: sunpoet@FreeBSD.org The current USES=nodejs has the following issues: - www/node is not the default version while www/node16 is. - It also means inconsistent naming of node ports. - www/npm duplicates with www/npm-node16. - www/yarn duplicates with www/yarn-node16. The notable changes are introduced to fix the above issues: - Rewrite Mk/Uses/nodejs.mk. - Add new LTS version of nodejs (www/node18). - Add new current version of nodejs (www/node19). - Change default nodejs version from 16 to 18 (latest LTS), - Use consistent naming for all supported node versions. - Convert www/node, www/npm and www/yarn to meta ports. After these changes: - All supported node versions are named as node{14,16,18,19}. - www/node is a meta port which depends on the default version (e.g. www/node18) - www/npm is a meta port which depends on the default version (e.g. www/npm-node18) - www/yarn is a meta port which depends on the default version (e.g. www/yarn-node18) 20230129: AFFECTS: users of benchmarks/ddosify AUTHOR: fernape@freebsd.org In 0.13.0 some configuration keys have been renamed for consistency. Have a look at https://github.com/ddosify/ddosify/releases/tag/v0.13.0 for details. 20230127: AFFECTS: users of security/openvpn AUTHOR: mandree@freebsd.org OpenVPN has been updated to the new upstream release v2.6.0, which is quite compatible with v2.5 versions. A copy of the latest v2.5.8 port is being kept as security/openvpn25 (or openvpn25 package) until end of March 2023. 20230116: AFFECTS: users of sysutils/nut and sysutils/nut-devel AUTHOR: cy@freebsd.org As of PR/268960 Network UPS Tools will now run under its own UID and GID instead of uucp. Users who wish to continue using the uucp user and group may add NUT_USER=uucp and NUT_GROUP=uucp to their make.conf. After upgrading sysutils/nut or sysutils/nut-devel with this patch, restart devd. Then restart nut. This will fix up the permissions of UPS USB devices and allow nut to start normally. 20230111: AFFECTS: users of sysutils/graylog AUTHOR: dch@freebsd.org Graylog 5.x and higher effectively constrains ElasticSearch dependencies, and in most cases will force a migration to OpenSearch 2.x, now available in ports. Plan accordingly. 20230104: AFFECTS: users of mail/spamassassin AUTHOR: cy@freebsd.org As of spamassassin 4.0.0 (3fdfceb36029) the deprecated HashCash plug-in was finally removed. Users using the HashCash plug-in will need to remove references to it. 20221226: AFFECTS: users of sysutils/zrepl AUTHOR: driesm@FreeBSD.org The Prometheus metric zrepl_version_daemon has been converted to the zrepl_start_time metric. The metric still reports the zrepl verison in a label. But the metric value is now the Unix timestamp at the time the daemon was started. The Grafana dashboard in dist/grafana has been updated. The RPC protocol version has also been bumped; all zrepl daemons in a setup must be updated and restarted before replication can resume. 20221220: AFFECTS: users of net-mgmt/unbound_exporter AUTHOR: thomas@beingboiled.info The config defaults for the log file and certificates have been changed. See /usr/local/etc/rc.d/unbound_exporter for possible options and adjust your rc.conf accordingly. 20221215: AFFECTS: users of security/clamav AUTHOR: yasu@FreeBSD.org Many users report that after updating ClamAV to 1.0.0 clamd and freshclam fails to start with integrity check error of databases. According to the result of investigation it happens with following conditions. 1. ClamAV is built on non-cleanroom environment (that is, neither FreeBSD official ClamAV package is used nor the package is built by user with poudriere). 2. math/tomsfastmath is installed in the system that ClamAV is built. So if the errror happens on you system, uninstall TomsFastMath first and then rebuild and reinstall ClamAV. The problem should disappear. 20221128: AFFECTS: devel/py-proxmoxer AUTHOR: einar@isnic.is AuthenticationError Moved proxmoxer.backends.https.AuthenticationError was moved to proxmoxer.AuthenticationError (the class itself is the same). Any imports or references to proxmoxer.backends.https.AuthenticationError should be changed to proxmoxer.AuthenticationError. ProxmoxResourceBase Removed While this should be a fully internal change, the ProxmoxResourceBase class was removed. Use ProxmoxResource instead. Removed ProxmoxHTTPTicketAuth The auth_token and csrf_token arguments are no longer supported. If an existing (still valid) token needs to be used, you can pass the token as password and proxmoxer will attempt to renew the ticket and retrieve a new token and CSRF token. 20221126: AFFECTS: textproc/kibana8 AUTHOR: otis@FreeBSD.org kibana8 now installs kibana-specific utilities into LOCALBASE/bin as symbolic links. Please check whether it will overwrite your local files with names same as these utilities and if so, please rename them or move out of the way in a different manner. 20221126: AFFECTS: textproc/elasticsearch8 AUTHOR: otis@FreeBSD.org elasticsearch8 now installs elasticsearch-specific utilities into LOCALBASE/bin as symbolic links (i.e. elasticsearch-cli and similar). Please check whether it will overwrite your local files with names same as these utilities and if so, please rename them or move out of the way in a different manner. 20221126: AFFECTS: users of lang/php80 AUTHOR: bofh@FreeBSD.org The default version of PHP has been switched from 8.0 to 8.1. If you use binary packages you should make a list of php packages before running 'pkg upgrade': # pkg info \*php80\* > ~/installed-php-ports-list After the upgrade, check with such list if all your php extensions are still installed, and reinstall them if needed. If you use mod_php80 you need to deinstall it and install mod_php81. 20221123: AFFECTS: x11-wm/jwm AUTHOR: fernape@FreeBSD.org jwm 2.4 introduces changes in the configuration. To convert an existing v2.3 configuration file using xsltproc, run: cp ~/.jwmrc ~/.jwmrc.old xsltproc jwm-2.4.xslt ~/.jwmrc.old > ~/.jwmrc If you have multiple configuration files, it may be necessary to apply the XSLT to some or all of them depending on what configuration options are stored in the file. 20221017: AFFECTS: archivers/star AUTHOR: fernape@FreeBSD.org With the update of devel/schilybase to 2022-10-16 a new port archivers/tartest has been splitted off from archivers/star. 20221016: AFFECTS: textproc/apache-solr AUTHOR: mfechner@FreeBSD.org Apache solr version 9 is released and made available as extra port textproc/apache-solr9. Version 9 cannot start directly with data from version 8. Additional steps for data migration is required. If you like to use the new version, deinstall the old version and install the new version: # pkg delete apache-solr # pkg install apache-solr9 After this you need to migrate data and migration, for this check the solr documentation. 20221015: AFFECTS: users of gstreamer1-* when upgrading via port builds on the host AUTHOR: riggs@FreeBSD.org The update of the gstreamer1-* ports to 1.20.3 requires a clean install of gstreamer1-* ports. In particular, when trying to update ports in-place using portupgrade or portmaster, the builds are likely to fail due to dependency mismatches. If this is your preferred update path, you need to deinstall (pkg delete -f) gstreamer1 and the plugins before reinstalling them from the ports tree. Note that pkg upgrade will do the right thing: If you use official FreeBSD packages or build your own set of packages using poudriere, nothing special is needed. 20221012: AFFECTS: devel/websvn AUTHOR: michael.osipov@siemens.com WebSVN 2.8.0 includes full PHP 8.x support which requires a change from PEAR to Composer 2. You must manually install dependencies through it, the ports system will not handle it anymore for you since */horde* (PR 266552) has been marked as incompatible with PHP 8.x for the time being. See pkg-message for detailed instructions. 20221011: AFFECTS: users of security/acme.sh AUTHOR: dvl@FreeBSD.org This update may break your install if you were using a symlink to %%EXAMPLESDIR%%/acme.sh.conf - that file is no longer installed. Instead, a log rotation configuration is now installed to etc/cron.d/acme.sh.sample you should modify etc/cron.d/acme.sh to needs. The port now installs a log rotation file to etc/newsyslog.d/acme.sh.sample and you you should update etc/newsyslog.d/acme.sh to suit your needs. This file has long been part of the port, but was never installed. Neither the log rotation nor the crontab are active until you remove the comments. 20221002: AFFECTS: users of shells/bash AUTHOR: ehaupt@FreeBSD.org Bash has been updated to version 5.2. In previous versions, the default port option-set used to link against libreadline from ports. However, the current version of devel/readline is too old for bash 5.2. For now, the default option has been switched to use the bundled version of libreadline and the other option is marked broken. Once devel/readline is updated this can be reverted. If you're updating bash from source and you've previously explicitly set to use use PORTS_READLINE, you'll have to disable the PORTS_READLINE option before updating: # cd /usr/ports/shells/bash # make config or flush it entirely: # cd /usr/ports/shells/bash # make rmconfig 20220929: AFFECTS: users of graphics/bmeps AUTHOR: takefu@airport.fm The executable name has been changed from this edition from bmpp to bitmap2pp 20220925: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 3.5 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. 20220919: AFFECTS: users of audio/strawberry AUTHOR: mandree@FreeBSD.org strawberry now uses FLAVORs based on the qt version, offering -qt5 and -qt6, with -qt5 the default. You may need to explicitly install either of the new flavors. 20220919: AFFECTS: users of sysutils/schilyutils AUTHOR: fuz@fuz.su Schilyutils has been split up into two ports. If you want the bosh shell, the new port is shells/bosh, which can be installed with: # pkg install bosh or # portmaster -o shells/bosh 20220918: AFFECTS: users of mail/roundcube AUTHOR: brnrd@FreeBSD.org Roundcube has been upgraded to 1.6.0 and introduces breaking changes to configuration options of remote services (imap, smtp, ldap, sieve). Check https://roundcube.net/news/2022/07/28/roundcube-1.6.0-released for details. Version 1.6 no longer includes the Classic and Larry skins, which are now available as separate mail/roundcube-classic and mail/roundcube-larry ports. 20220910: AFFECTS: users of devel/cmake AUTHOR: diizzy@FreeBSD.org CMake has been converted to a meta-port and new CMake packages created causes conflicts with old binary packages prior to this change. If CMake was installed using binary packages via pkg it needs to be uninstalled using pkg delete before installing CMake and related packages after this change. pkg delete cmake pkg install cmake-core If you're using portmaster you also need to delete the old CMake package before upgrading. 20220909: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org emulators/qemu has been updated to 7.1.0. Previous 7.0.X branch has been repocopied to emulators/qemu70. If someone wants to stick with 7.0.X branch please use one of the following command: # pkg install qemu70/qemu70-nox11(based on flavor used) or # portmaster -o emulators/qemu70 emulators/qemu or # portupgrade -o emulators/qemu70 emulators/qemu 20220903: AFFECTS: users of editors/vim AUTHOR: adamw@FreeBSD.org The Vim port no longer installs a system-wide vimrc. It drastically affected config loading order, and led to various settings being clobbered, duplicated, or ignored. Vim's provided defaults.vim (/usr/local/share/vim/vim90/defaults.vim) continues to be read just as before, but its settings are no longer clobbered. Take a look in there for any settings you may want to change, and do ':h initialization' to see where Vim looks for config files. 20220903: AFFECTS: users of archivers/py-borgbackup AUTHOR: mandree@FreeBSD.org Borgbackup has been upgraded to version 1.2. For users who you wish to continue using version 1.1, use either of these commands for upgrading: With binary packages through pkg: pkg set -o archivers/py-borgbackup:archivers/py-borgbackup11 pkg upgrade With portmaster or portupgrade (replace the command accordingly): portmaster -o archivers/py-borgbackup11 archivers/py-borgbackup 20220901: AFFECTS: users of mail/rainloop-community AUTHOR: yasu@FreeBSD.org Since 1.17.0 upstream distributes only one "legacy" edition under MIT license and mail/rainloop-community is removed as a result. So please uninstall mail/rainloop-community (rainloop-community-phpXY) and install mail/rainloop (rainloop-phpXY) instead. 20220831: AFFECTS: users of x11/xscreensaver on 13.1-RELEASE AUTHOR: zirias@FreeBSD.org With the update to 6.04, xscreensaver now uses security/unix-selfauth-helper for PAM authentication. This relies on pam_exec.so, which had a bug causing a segfault on authentication attempts prior to 13.1-RELEASE-p1. For details, please see https://www.freebsd.org/security/advisories/FreeBSD-EN-22:19.pam_exec.asc Make sure your system is fully upgraded, otherwise you might be unable to unlock your screen. 20220825: AFFECTS: users of net/xrdp or net/xrdp-devel AUTHOR: meta@FreeBSD.org After xorg upgrade to 21.1.4, xorgxrdp session doesn't start as before This is because bin/Xorg has been replaced with X server binary wrapper. You must manually edit the Xorg section in etc/xrdp/sesman.ini to get it working again. The following is a short example of where, how to modify sesman.ini. Make sure to replace LOCALBASE with your actual path. [Xorg] ; Specify the path of non-suid Xorg executable. It might differ depending ; on your distribution and version. Find out the appropreate path for your ; environment. The typical path is known as follows: ; ; Fedora 26 or later : param=/usr/libexec/Xorg ; Debian 9 or later : param=/usr/lib/xorg/Xorg ; Ubuntu 16.04 or later : param=/usr/lib/xorg/Xorg ; Arch Linux : param=/usr/lib/Xorg ; CentOS 7 : param=/usr/bin/Xorg or param=Xorg ; CentOS 8 : param=/usr/libexec/Xorg ; -param=Xorg +param=LOCALBASE/libexec/Xorg 20220815: AFFECTS: users of net/keycloak AUTHOR: fernape@FreeBSD.org The flavors -mysql and -postgres were removed, the necessary configuration for those database backends was rolled into the base release by upstream. The configuration files changed completely, so they need to be rebuilt from scratch. 20220807: AFFECTS: users of news/inn AUTHOR: kbowling@FreeBSD.org The inn port has been updated to 2.7 release. Users upgrading from prior versions should read through the announcement for any manual upgrading steps that apply to your environment. https://lists.isc.org/pipermail/inn-announce/2022-July/000015.html 20220711: AFFECTS: users of security/stunnel AUTHOR: zi@FreeBSD.org The stunnel port has been updated to drop privileges to the stunnel user by default. As a result of this change, the pid file location has changed. If you have a running copy of stunnel, you should stop the process before performing the upgrade. Alternatively, you will need to # pkill stunnel;service stunnel start after the upgrade has been completed. 202207XYZ: AFFECTS: users of devel/maven-wrapper and devel/maven AUTHOR: michaelo@apache.org The environment variable M2_HOME has been replaced with more common MAVEN_HOME which can be used to pass a custom Maven home directory. 20220629: AFFECTS: updating x11-servers/xorg-server from a port AUTHOR: se@FreeBSD.org The xorg-server port now has a library dependency on x11/libxcvt, which cannot be installed when the previous version of xorg-server is present. To be able to update xorg-server from a port, the previous version needs to be manually deinstalled to allow libxcvt to be installed. 20220628: AFFECTS: users of Erlang and Elixir AUTHOR: dch@FreeBSD.org For more than a decade, the Elixir Mix tool and the Erlang rebar or erlang.mk build tools have been the de facto way of installing and managing packages for specific applications. All main-stream applications, from Riak, CouchDB, RabbitMQ, Phoenix, and Elixir, expect that packages are fetched and compiled into an OTP Release, with in-built version locking, external package management. There is no point in maintaining a large number of libraries, that are used neither for development, nor operations. Users are directed to https://rebar3.org/ https://erlang.mk/ or https://elixir-lang.org/getting-started/mix-otp/introduction-to-mix.html to fetch custom packages. https://www.freebsd.org/status/report-2021-07-2021-09/#_freebsd_erlang_ecosystem_ports_update 20220626: AFFECTS: users of python AUTHOR: thierry@FreeBSD.org The default version of python3 and python was switched to 3.9. For ports users wanting to keep version 3.8 as default, add DEFAULT_VERSIONS+= python=3.8 python3=3.8 to make.conf Following procedures may ease the upgrade: For users of pre-build packages: # sh # for i in $(pkg query -g %n 'py38-*'); do pkg set -yn ${i}:py39-${i#py38-}; done # pkg upgrade For portmaster users: # sh # portmaster -o lang/python39 python38 # REINSTALL="$(pkg info -o "*py38*" | awk '{printf "%s ", $2}')" # pkg delete -f "*py38*" # portmaster $REINSTALL # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py39 | cut -d : -f 1 | sort -u) # portmaster $REBUILD # REBUILD2=$(pkg list | grep python-38 | xargs pkg which | awk '{print $6}' | sort -u) # portmaster $REBUILD2 Final steps (for pre-built packages & portmaster): If no longer required, Python 3.8 can be removed via "pkg remove python38" and the directory /usr/local/lib/python3.8 can then be deleted afterwards, if not empty. 20220625: AFFECTS: users of sysutils/fusefs-bindfs AUTHOR: doralitze@chaotikum.org Bindfs defaults to use direct I/O since version 1.16. While this results in major performance improvements as well as several bug fixes, this also breaks direct legacy calls to mmap. If your application still uses them consider these two options: 1. Mount using `--no-direct-io` 2. Upgrade your application in order to query mapping guards 20220623: AFFECTS: users of science/gramps AUTHOR: fernape@FreeBSD.org databases/py-bsddb3 is deprecated and will be removed in the future. With that gramps will lose the ability to load family trees using Berkeley DB. It is suggested to migrate all family trees using Berkeley DB by exporting them to gramps xml and import that gramps xml into a family tree using sqlite as database. 20220620: AFFECTS: users of www/selenium AUTHOR: fernape@FreeBSD.org The port has changed startup args so if you are using selenium_args= in rc.conf you need to add the parameter "standalone" manually. 20220616: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org /!\ WARNING /!\ The NetBox 3.2 release contains major changes, so at least items 1.), 2.) and 3.) must be checked before proceeding with the upgrade! /!\ WARNING /!\ 1. This release includes a database migration that will remove the "asn", "contact_name", "contact_phone", and "contact_email" fields from the site model. (These fields have been superseded by the ASN and contact models introduced in NetBox v3.1.) To protect against the accidental destruction of data, the upgrade process will fail if any sites still have data in any of these fields. To bypass this safeguard, set the NETBOX_DELETE_LEGACY_DATA environment variable when running the upgrade script, which will permit the destruction of legacy data. A set of migration scripts is available to assist with the migration of legacy site data: https://github.com/netbox-community/migration-scripts 2. NetBox v3.2 requires Python 3.8 or later. 3. If the NetBox Plugin "net-mgmt/py-netbox-plugin-extension" is used, please disable it before the migrations are applied. This can be done by removing the entry "netbox_plugin_extensions" from the "PLUGINS" section in the NetBox configuration. Once the upgrade is done, this port/package can be safely removed as it's no longer required. 4. Please also check the pkg-message and the changelogs for further info. 20220608: AFFECTS: devel/autoconf-wrapper, devel/autoconf213 AUTHOR: tijl@FreeBSD.org These ports have been renamed to devel/autoconf-switch and devel/autoconf2.13 respectively. If your favourite port updating tool cannot handle that then just remove the packages with "pkg delete" and then install the new port. 20220607: AFFECTS: security/openssh-portable AUTHOR: bdrewery@FreeBSD.org OpenSSH has been updated to 9.0p1 with incompatible changes. See https://www.openssh.com/txt/release-9.0 for details. 20220602: AFFECTS: sysutils/graylog AUTHOR: dch@FreeBSD.org Graylog 4.3.0+ fails to start if graylog's internal collector for system statistics is enabled. This will eventually be addressed upstream. Add disable_native_system_stats_collector=true to your graylog.conf. 20220513: AFFECTS: devel/nexus2-oss AUTHOR: michael.osipov@siemens.com Nexus 2.15.x introduces incompatible configuration changes. You must review changes in ETCDIR/wrapper.conf and ETCDIR/jetty*.xml with updated samples as well as NEXUS_WORKDIR/conf/logback-nexus.xml with its origin from DATADIR/nexus/WEB-INF/lib/nexus-core-VERSION.jar!/META-INF/log/logback-nexus.xml, grant write access to files in ETCDIR since Nexus itself might update files in place otherwise your instance will not properly work after the update. 20220510 AFFECTS: sysutils/zrepl AUTHOR: monwarez@gmail.com The zrepl update to 0.5.0.8 includes the following breaking changes: - The Prometheus metric zrepl_version_daemon was converted to zrepl_start_time The metric still reports the zrepl version in a label. But the metric *value* is now the Unix timestamp at the time the daemon was started. The Grafana dashboard in zrepl examples directory has been updated. 20220502: AFFECTS: mail/mutt AUTHOR: dereks@lifeofadishwasher.com Default header cache option has been changed to the new option LMDB using databases/lmdb. The BDB option still exists but now uses databases/db18 due to the EOL of databases/db5. 20220501: AFFECTS: users of drm-current-kmod and drm-devel-kmod AUTHOR: manu@FreeBSD.org Both ports where removed. If you were using either one of them directly (i.e. without using graphics/drm-kmod metaport) use graphics/drm-510-kmod. If you have some problems with this one try drm-54-kmod and report a bug on https://github.com/freebsd/drm-kmod. 20220428: AFFECTS: users of databases/redis AUTHOR: yasu@FreeBSD.org The databases/redis port has been updated to 7.0. Users wanting to stay on 6.2 can replace databases/redis with databases/redis62 with one of the following commands. If you use pkg with binary packages: # pkg set -o databases/redis:databases/redis62 # pkg upgrade If you use portmaster: # portmaster -o databases/redis62 databases/redis If you use portupgrade: # portupgrade -o databases/redis62 databases/redis 20220426: AFFECTS: users of deskutils/grantleetheme AUTHOR: kde@FreeBSD.org The pkg update of deskutils/grantleetheme to 22.04 can fail due to a filesystem location having changed from being a file to being a directory. This leads to pkg's temporary file creation throwing an error. To update to KDE Gear 22.04 please run # pkg delete -f grantleetheme prior to the update. 20220424: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org emulators/qemu has been updated to 7.0.0. Previous 6.2.X branch has been repocopied to emulators/qemu6. If someone wants to stick with 6.2.X branch please use one of the following command: # pkg install qemu6/qemu6-nox11(based on flavor used) or # portmaster -o emulators/qemu6 emulators/qemu or # portupgrade -o emulators/qemu6 emulators/qemu 20220421: AFFECTS: users of lang/ruby27 AUTHOR: yasu@FreeBSD.org The default ruby version has been updated from 2.7 to 3.0. If you compile your own ports you may keep 2.7 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.7 as default version # DEFAULT_VERSIONS+=ruby=2.7 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkg, simply upgrade: # pkg upgrade If you do not use pkg, please check entry 20190420. The description there should also work for this version. 20220413: AFFECTS: users of net-im/py-matrix-synapse AUTHOR: ports@skyforge.at Synapse will now refuse to start up if open registration is enabled, in order to help mitigate abuse across the federation. If you would like to provide registration to anyone, consider adding email, recaptcha or token-based verification in order to prevent automated registration from bad actors. This check can be disabled by setting the enable_registration_without_verification option in your homeserver configuration file to true. More details are available in the upgrade notes[0]. Synapse will additionally now refuse to start when using PostgreSQL with a non-C values for COLLATE and CTYPE, unless the config flag allow_unsafe_locale, found in the database section of the configuration file, is set to true. See the upgrade notes[1] for details. [0] https://matrix-org.github.io/synapse/v1.56/upgrade.html#open-registration-without-verification-is-now-disabled-by-default [1] https://matrix-org.github.io/synapse/v1.56/upgrade#change-in-behaviour-for-postgresql-databases-with-unsafe-locale 20220410: AFFECTS: users of sysutils/screen AUTHOR: cy@FreeBSD.org As of sysutils/screen-4.9.0_5, the MULTUSER option is default, reverting to the traditional setuid-root behavior. People who wish to secure their screen install must terminate all screen sessions, then install screen without the MULTIUSER option. The option was reversed because it caused too much astonishment among users of screen. 20220401: AFFECTS: security/sshguard AUTHOR: kevinz5000@gmail.com Blacklisting is now disabled by default to avoid overriding the setting in sshguard.conf. To enable blacklisting, uncomment the BLACKLIST_FILE line in sshguard.conf. 20220329: AFFECTS: users of sysutils/screen AUTHOR: cy@FreeBSD.org As of sysutils/screen-4.9.0_3, the multiuser feature is not supported by default. The multiuser feature requires setuid root to function. This creates a security risk. Some Linux distributions have had non-setuuid root screen for a dozen or more years. FreeBSD is following suit. A new MULTIUSER option has been added to enable users to install setuid root screen. The MULTIUSER option default is OFF. Users who wish to use the multiuser feature may, - Build screen using the MULTIUSER option, or - Poudriere users can use poudriere-options to enable the MULTIUSER option, or - Users can chmod the setuid bit for ${LOCALBASE}/bin/screen-4.9.0, making screen setuid root to enable the multiuser feature. 20220326: AFFECTS: users of misc/freebsd-doc-* AUTHOR: blackend@FreeBSD.org A change to the doc toolchain prevents the build of individual localized HTML versions of the documentation without building the en_US version. HTML option is currently disabled until a good solution is found. PDF version, the default option, is now the only available option. Please re-run "make config" to pick up this new default. 20220313: AFFECTS: users of net/unison AUTHOR: madpilot@FreeBSD.org unison has been updated to version 2.52. The new version introduces a new wire protocol and on disk archive format. This new version is compatible with 2.51 clients for communication, so it's now possible to upgrade one side and then the other. The archive files are automatically converted to the new version, but once they are converted the y are incompatible with the previous version. In case you need version 2.51, the previous version of the port is preserved in net/unison251. 20220311: AFFECTS: users of multimedia/get_iplayer AUTHOR: jamie@catflap.org get_iplayer has a number of changes to quality settings that may break existing configurations. Please see the release notes for further information: https://github.com/get-iplayer/get_iplayer/wiki/release320to329#release329 20220311: AFFECTS: users of emulators/virtualbox-ose AUTHOR: grembo@FreeBSD.org In order to comply to hier(7), VirtualBox's configuration of non-default IP ranges to be used in host-only mode moved from /etc/vbox/networks.conf to ${LOCALBASE}/etc/vbox/networks.conf. 20220311: AFFECTS: users of net/nats-server AUTHOR: olgeni@FreeBSD.org A dedicated 'nats' user was added, replacing 'nobody' in the startup script. You should check your configuration and assign updated ownership to your data files. 20220227: AFFECTS: users of graphics/bmeps AUTHOR: takefu@airport.fm The binary and man page have been renamed from bmpp{.1.gz} to bitmap2pp{.1.gz} 20220225: AFFECTS: users of x11-toolkits/py-wxPython40 AUTHOR: lbartoletti@FreeBSD.org x11-toolkits/py-wxPython40 has been removed to be replaced by the 4.1 version. However the new wxPython ports is now named x11-toolkits/py-wxPython4. Depending on the tools you use, you may have to remove the port before ports upgrade. 20220224: AFFECTS: users of net-im/openfire AUTHOR: nikita@druba.su The port version have been updated from 4.6.x to 4.7.x. It is recommended to do database and configs backup before updating. 20220219: AFFECTS: users of sysutils/intel-pcm-devel AUTHOR: egypcio@FreeBSD.org sysutils/intel-pcm-devel became quite obsolete once sysutils/intel-pcm is now pretty much following a constant and stable update cycle, so users of the -devel version are encouraged to switch to it. If you still have sysutils/intel-pcm-devel installed, please delete it from your system and install sysutils/intel-pcm instead: # pkg delete sysutils/intel-pcm-devel # pkg install sysutils/intel-pcm 20220219: AFFECTS: users of math/qhull* AUTHOR: stephen@FreeBSD.org Because of entries in MOVED, portupgrade can get confused updating qhull. It is recommended that you delete qhull and ports depending upon it, and then reinstalling all the dependent ports. 20220218: AFFECTS: users of TeX* AUTHOR: bofh@FreeBSD.org TeX system has been updated to 2021 from 2015. Normal pkg upgrade or portmaster -a should handle all the upgrade properly. In case not please create a ticket or send a mail to tex@FreeBSD.org print/tex-aleph has been removed as per upstream. This package should be removed manually. Additionally users have reported to delete texlive-texmf prior to starting update, or pkg-static will indicate there is a conflict during the upgrade of texlive-base : # pkg remove tex-aleph texlive-texmf 20220218: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org The storage directory has moved from WWWDIR to /var/db/librenms/storage to comply with man 7 hier. When upgrading, you may need to manually create this symlink. 20220212: AFFECTS: users of lang/php8[01][-extensions]? AUTHOR: bofh@FreeBSD.org Non-Default OPTION MYSQL80 has been removed in lieu of making php8[01]-openssl as part of DEFAULT php8[01] installation. Although for php74 it is not the case. Ports that depends on security/php8[01]-openssl will no longer be installed as these have been removed. There is no side effect of this for ports which have USE_PHP=openssl. In case for php74 as the default php74-openssl will be installed otherwise it will be used from php installation. If you are using pkg, you have to remove php8[01]-openssl manually after the upgrade : # pkg info \*php8\* > ~/installed-php-ports-list # pkg upgrade -y # pkg delete -f php8[01]-openssl # service -R While rebuilding from ports users old php.conf is not overwritten. So have to manually remove the ports. For portmaster users: # sh # REINSTALL="$(pkg info -o "*php80*" | grep -v openssl | awk '{printf "%s ", $2}')" # pkg delete -f "*php80*" # portmaster $REINSTALL # portmaster -a 20220207: AFFECTS: users of security/amavisd-new AUTHOR: flo@FreeBSD.org Amavis does now depend on archivers/7-zip (7zz) you might need to update your amavisd.conf and replace all ocurances of p7zip (7zr) accordingly. 20220129: AFFECTS: users of editors/neovim AUTHOR: adamw@FreeBSD.org Neovim now uses luajit-openresty as the Lua provider. Many neovim plugins compile some of their code (Packer does this, as do many LSP plugins). Neovim will produce errors and fail to load the plugins. Deleting and reinstalling any plugins that produce errors should fix the startup. If you use Packer, you also want to delete the startup cache: # rm -rf ~/.config/nvim/plugin/packer_compiled.lua 20220128: AFFECTS: users of x11-fonts/source-sans-ttf AUTHOR: fernape@FreeBSD.org The font name has changed its prefix from SourceSansPro* to SourceSans*. Users of this font might need to change their configurations to pick up the new names. 20220128: AFFECTS: users of net-im/dendrite AUTHOR: ashish@FreeBSD.org The configuration needs to be updated to version 2 following upgrade to Dendrite v0.6. Please refer to /usr/local/etc/dendrite/dendrite.yaml.sample for a sample configuration. 20220127: AFFECTS: users of PyQt AUTHOR: kde@FreeBSD.org Most of the PyQt ports have been merged into single port devel/py-qt5-pyqt. `pkg upgrade` will handle update automatically . 20220126: AFFECTS: users of mail/bogofilter, mail/bogofilter-lmdb AUTHOR: mandree@FreeBSD.org The default version of mail/bogofilter now uses LMDB instead of Berkeley DB. It is not compatible and cannot read databases. Your options are: 1. use bogoutil on each wordlist for each of your users first, ONLY THEN reinstall bogofilter, THEN reload the databases with bogoutil, OR 2. install the matching bogofilter version and If you had been using bogofilter-lmdb so far, install bogofilter. If you had been using bogofilter so far, install bogofilter-bdb. 20220125: AFFECTS: users of lang/php74 AUTHOR: tz@FreeBSD.org The default version of PHP has been switched from 7.4 to 8.0. If you use binary packages you should make a list of php packages before running 'pkg upgrade': # pkg info \*php7\* > ~/installed-php-ports-list After the upgrade, check with such list if all your php extensions are still installed, and reinstall them if needed. If you use mod_php74 you need to deinstall it and install mod_php80. 20220120: AFFECTS: users of x11-wm/dwm AUTHOR: 0mp@FreeBSD.org dwm has been updated to 6.3. The option RUGAPS is no longer available because it depends on a patch only available for version 6.2. RUGAPS can be reintroduced if desired once it is ported to 6.3 by the interested party. 20220118: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org 1. Please make sure that the PostgreSQL server for the NetBox instance is running version 10 or higher. This is because PostgreSQL 9.6 is End-of-Life since November 2021 and NetBox 3.1 makes use of the "macaddr8" field which was introduced with PostgreSQL 10. 2. Please also check the pkg-message and the changelogs for further info. 20220110: AFFECTS: users of security/bastillion AUTHOR: netchild@FreeBSD.org If you already performed the actions of the next entry, the following action in this entry needs to be performed regardless. If you did not already perform the actions of the next entry, only the action of this entry needs to be performed. The datastore of bastillion needs to be upgraded (if you do not see users / can not login, you forgot to upgrade it): java -jar %%PREFIX%%/jetty_bastillion/upgrade/bastillion-upgrade-4.00.01.jar %%PREFIX%%/jetty_bastillion/bastillion/WEB-INF/classes/BastillionConfig.properties 20220104: AFFECTS: users of security/bastillion AUTHOR: netchild@FreeBSD.org The datastore of bastillion needs to be upgraded (if you do not see users / can not login, you forgot to upgrade it): java -jar %%PREFIX%%/jetty_bastillion/upgrade/bastillion-upgrade-4.00.00.jar %%PREFIX%%/jetty_bastillion/bastillion/WEB-INF/classes/BastillionConfig.properties 20220102: AFFECTS: users of sysutils/py-azure-cli AUTHOR: dbaio@FreeBSD.org When upgrading to Azure CLI v2.31.0, you will need to re-authenticate on Azure services. $ az login --use-device-code Starting in version 2.30.0, Azure CLI uses MSAL as the underlying authentication library. MSAL uses AAD v2.0 authentication flow to provide more functionality and increases security for token cache. More info: https://docs.microsoft.com/en-us/cli/azure/msal-based-azure-cli 20211220: AFFECTS: users of devel/notcurses AUTHOR: nickblack@linux.com Notcurses 3 introduces a new SONAME and significant API/ABI changes. Dependent applications must be recompiled at a minimum. A complete guide to updating for the new API is available under "Porting API2 Applications to API3" at https://github.com/dankamongmen/notcurses/releases/tag/v3.0.0 20211220: AFFECTS: users of net-im/openfire AUTHOR: nikita@druba.su The port options have been renamed to be more readable. When not using the default options, they have to be regenerated. # cd /usr/ports/net-im/openfire # make config 20211213: AFFECTS: users of emulators/qemu-utils AUTHOR: bofh@FreeBSD.org New port emulators/qemu@tools has been introduced which is similar to emulators/qemu-utils. qemu-utils has also been DEPRECATED in favor for this as it's MASTER port has also been marked DEPRECATED and set to expire on 2022-01-09. For updating to qemu-tools please use one of the following command: # pkg install qemu-tools or # portmaster -o emulators/qemu-utils emulators/qemu@tools 20211116: AFFECTS: users of emulators/qemu50 AUTHOR: bofh@FreeBSD.org emulators/qemu50 has been moved to emulators/qemu5 and updated to 5.2.0 which is the last version from 5.X.X branch. This is done in preparation of updating emulators/qemu into latest 6.X branch. If someone wants to stick with 5.X.X branch please use one of the following command: # pkg install qemu5 or # portmaster -o emulators/qemu50 emulators/qemu5 This version also introduces a stripped nox11 version which can be installed with: # pkg install qemu5-nox11 or # portmaster emulators/qemu5@nox11 20211115: AFFECTS: AFFECTS: users of *-emacs2x-* packages AUTHOR: jrm@FreeBSD.org To avoid problems when editors/emacs or editors/emacs-devel are updated, the emacs major version has been removed from these package names. For example, the old and new package names of devel/magit are ----------------------------------------------------------- | Old Package Name | New Package Name | |-------------------------- |-----------------------------| | magit-emacs27 | magit | | magit-emacs27_nox | magit-emacs_nox | | magit-emacs27_canna | magit-emacs_canna | | | | | magit-emacs29_nox | magit-emacs_devel_nox | | magit-emacs29 | magit-emacs_devel | ----------------------------------------------------------- To handle these final package name changes, follow a similar procedure as the one described in the 20200811 entry. That is, simply running `pkg upgrade` will not upgrade, e.g., foo-emacs27_nox to foo-emacs_nox. Binary package users: To update these packages, run these commands under /bin/sh with superuser privileges before upgrading. # default flavor of editors/emacs installed for i in $(pkg query -g %n '*-emacs27'); do if [ "$i" != "notmuch-emacs27" ]; then nn=$(echo "$i" | sed -e 's/-emacs27//') else nn=$(echo "$i" | sed -e 's/-emacs27/-emacs/') fi pkg set -yn "$i":"$nn" done # canna or nox flavor of editors/emacs installed for i in $(pkg query -g %n '*-emacs27*'); do nn=$(echo "$i" | sed -e 's/emacs27/emacs/') pkg set -yn "$i":"$nn" done # editors/emacs-devel installed for i in $(pkg query -g %n '*-emacs29*'); do nn=$(echo "$i" | sed -e 's/emacs29/emacs_devel/') pkg set -yn "$i":"$nn" done portmaster users: portmaster -r emacs 20211110: AFFECTS: users of www/node*, www/npm*, www/yarn* AUTHOR: mfechner@FreeBSD.org The port framework was updated to use a default version for nodejs. The default version is pointing to the latest LTS version which is currently version 16. You can overwrite this by defining in /etc/make.conf, e.g. version 17: DEFAULT_VERSIONS=nodejs=17 Or if you would like to stick always to the current version use: DEFAULT_VERSIONS=nodejs=current If you would like to use yarn or npm together with nodejs version 17, just install the package that is pulling the wanted dependency to nodejs: # pkg install yarn-node17 # pkg install npm-node17 20211109: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 3.4 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. 20211107: AFFECTS: users of sysutils/devcpu-data AUTHOR: jrm@FreeBSD.org The RC variable name microcode_cpus is now deprecated. Users should instead use the variable microcode_update_cpus. Two new ports were branched from sysutils/devcpu-data, sysustils/devcpu-data-amd and sysustils/devcpu-data-intel. The two new ports contain only the CPU microcode updates for each vendor and sysutils/devcpu-data now only contains an RC script. Both new ports are on-by-default, optional dependencies of sysutils/devcpu-data. 20211101: AFFECTS: users of textproc/redisearch AUTHOR: osa@FreeBSD.org The textproc/redisearch port has been updated to the recent stable release - v2.2. Users wanting to stay on v2.0 can replace textproc/redisearch with textproc/redisearch20 with one of the following commands: # pkg install textproc/redisearch20 or # portmaster -o textproc/redisearch20 textproc/redisearch or # portupgrade -o textproc/redisearch20 textproc/redisearch NOTE: The textproc/redisearch20 brings a new name for the module, i.e. redisearch20.so, so be careful. 20211024: AFFECTS: sysutils/beats7 AUTHOR: otis@FreeBSD.org The following breaking changes apply to beats 7.15.0 and newer: - All beats: Loading Kibana assets (dashboards, index templates) rely on Saved Object API. So to provide a reliable service, Beats can only import and export dashboards using at least Kibana 7.15. - Filebeat: - Remove all alias fields pointing to ECS fields from modules. This affects the Suricata and Traefik modules. - Fix Crowdstrike ingest pipeline that was creating flattened process fields. - Rename log.path to log.file.path in filestream to be consistent with log input and ECS. - Heartbeat: - Remove long deprecated watch_poll functionality. - Fix inconsistency in event.dataset values between heartbeat and fleet by always setting this value to the monitor type / fleet dataset. - Metricbeat: - Fix Elasticsearch jvm.gc.collectors.old being exposed as young Full changelog: https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-7.15.0.html https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-7.15.1.html 20211024: 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 12 to 13. 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 12.8, your files are named according to this. # service postgresql stop # pkg create postgresql12-server postgresql12-contrib # mkdir /tmp/pg-upgrade # tar xf postgresql12-server-12.8.pkg -C /tmp/pg-upgrade # tar xf postgresql12-contrib-12.8.pkg -C /tmp/pg-upgrade # pkg delete -f databases/postgresql12-server databases/postgresql12-contrib databases/postgresql12-client Now update PostgreSQL: pkg user: # pkg install databases/postgresql13-server databases/postgresql13-contrib # pkg upgrade Portmaster users: # portmaster databases/postgresql13-server databases/postgresql13-contrib # portmaster -a Portupgrade users: # portinstall databases/postgresql13-server databases/postgresql13-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/data13 -U postgres" # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data12/ -B /usr/local/bin/ -D /var/db/postgres/data13/ -U postgres " Now the migration is finished. You can start PostgreSQL again with: # service postgresql start ATTENTION: 1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume the "postgres" database user and FreeBSD user. 2) See the updating entry 20190829 if you are updating from a release prior to 11. 3) If you use non-default initdb options, you have to adjust the initdb-command accordingly 20211023: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v17.0.0, the latest upstream release. A new port, www/node16, has been created for the upcoming v16.x LTS branch. Users wanting to stay on v16.x can replace www/node with www/node16 with one of the following commands: # pkg install www/node16 or # portmaster -o www/node16 www/node or # portupgrade -o www/node16 www/node 20211012: AFFECTS: users of devel/git AUTHOR: garga@FreeBSD.org devel/git port was split into multiple sub-ports that depend on devel/git and install additional files: - devel/git-cvs - CVS related scripts and man pages - devel/git-gui - GUI related scripts and man pages - devel/git-p4 - Perforce related scripts and man pages - devel/git-svn - Subversion related scripts and man pages Due to these changes, CVS, GUI, PERFORCE, and SUBVERSION options as well as gui and svn flavors were removed from the port. 20211010: AFFECTS: users of gtk2 flavored devel/geany* AUTHOR: madpilot@FreeBSD.org Upstream dropped support for gtk2. Due to this the ports are now unflavored, installing only with gtk3 support. If you are already using the default gtk3 flavor will get the new version with a simple "pkg upgrade". To upgrade when using the gtk2 flavors you need to use "pkg install" to install the new unflavored gtk3 packages, pkg will automatically uninstall the old gtk2 flavors. If using ports, you will need to uninstall all geany packages and its plugins and reinstall from an updated ports tree. The "geany-plugin-multiterm" plugin was only available as a gtk2 flavor when installing the gtk2 flavor of geany and has not been ported to gtk3, so has been removed from the tree, so the geany-plugin-multiterm-gtk2 package should be removed from the system. 20211007: AFFECTS: user of security/clamav AUTHOR: yasu@FreeBSD.org Upstream changed end-of-life policy and introduced long time support (LTS) feature release. * LTS feature release will be identified approximately every two years and supported for at least three years from the initial publication date of that LTS feature version. * Regular (non-LTS) feature releases will be supported for at least four months from the initial publication date of the next feature release or until the feature release after that is published. According to it new port security/clamav-lts is added for users who want to use LTS version of ClamAV. Users wanting to switch to LTS version can replace security/clamav with security/clamav-lts with one of following commands. If you use pkg with binary packages: # pkg set -o security/clamav:security/clamav-lts # pkg upgrade If you use portmaster: # portmaster -o security/clamav-lts security/clamav If you use portupgrade: # portupgrade -o security/clamav-lts security/clamav 20211006: AFFECTS: users of misc/freebsd-doc-* AUTHOR: blackend@FreeBSD.org The misc/freebsd-doc-* ports have been updated to the new doc toolchain, and use a somewhat different arrangement of directories and symlinks, which pkg 1.17 does not handle well. Users are encouraged to delete the misc/freebsd-doc-* ports, then reinstall the new ones without using the pkg upgrade facility. 20211006: AFFECTS: users of net/kafkacat AUTHOR: sergey@akhmatov.ru kafkacat has been renamed to kcat upstream. So switch to net/kcat instead. 20211004: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org /!\ WARNING /!\ The NetBox 3.0 release contains major changes, so at least items 1.), 2.) and 3.) must be checked before proceeding with the upgrade! /!\ WARNING /!\ 1. Please ensure that your local installation of net-mgmt/netbox is at the 2.11 release before attempting to upgrade to NetBox 3.0 or later. 2. Please also note that the previously deprecated secrets functionality has been removed with NetBox 3.0. This means, all of the secrets still remain in the database once upgraded, only the secrets functionality on the part of NetBox is no longer given. In order to continue to be able to access the stored secrets as usual (and then possibly migrate them to another solution, e.g. security/vault), please install the security/py-netbox-secretstore port once NetBox has been upgraded to 3.x and follow its installation instructions how to enable the plugin. 3. If plugins are used, they should be temporarily deactivated to avoid disruptions during the upgrade process. 4. Please also check the pkg-message and the changelogs for further info. 20211004: AFFECTS: users of www/py-pyjwt AUTHOR: rhurlin@FreeBSD.org To make it possible to easily import py-pyjwt v2.x the current port was moved to a versioned directory. If you use portmaster: portmaster -o www/py-pyjwt1 www/py-pyjwt If you use portupgrade: portupgrade -fo www/py-pyjwt1 www/py-pyjwt If you use pkg with binary packages: pkg set -o www/py-pyjwt:www/py-pyjwt1 20210912: AFFECTS: x11-wm/cage, x11-wm/hikari, x11-wm/labwc, x11-wm/sway, x11-wm/wayfire AUTHOR: jbeich@FreeBSD.org SUID option has been removed in favor of seatd-launch(1) which doesn't require special handling in every consumer and doesn't bypass group permissions. If you've already enabled seatd service or use consolekit2 then nothing changes. Otherwise, $ sway 00:00:00.001 [ERROR] [wlr] [libseat] [libseat/libseat.c:83] No backend was able to open a seat 00:00:00.001 [ERROR] [wlr] [backend/session/session.c:84] Unable to create seat: Function not implemented 00:00:00.001 [ERROR] [wlr] [backend/session/session.c:218] Failed to load session backend 00:00:00.001 [ERROR] [wlr] [backend/backend.c:353] Failed to start a DRM session 00:00:00.001 [ERROR] [sway/server.c:53] Unable to create backend can be fixed by $ ck-launch-session sway or $ seatd-launch sway or # sysrc seatd_enable=YES # service seatd start $ sway Replace "sway" with your compositor e.g., "cage", "hikari", "labwc", "wayfire". 20210907: AFFECTS: consumers of math/eigen[23] AUTHOR: adridg@FreeBSD.org math/eigen2 has been marked deprecated. There do not seem to be any consumers in FreeBSD ports. math/eigen3 has had its options re-vamped. The default options previously pulled in multiple useless library dependencies. The options also forced a specific BLAS implementation. The new options depend only on the default BLAS (whatever USES=blaslapack picks), but this can be turned off. The previous multiple useless libraries -- which are not useless when running the tests in Eigen -- are now hidden behind the default-off TEST option. Users of a carefully-tuned Eigen build should re-evaluate the options available. 20210902: AFFECTS: users of editors/vim AUTHOR: adamw@FreeBSD.org The vim ports have been completely reworked to take advantage of flavors. The biggest change is that the `vim' package is now console-only. If you want the GTk3 GUI, you'll need to install the `vim-gtk3' package instead. All the GUI toolkits have their own package now: vim-gtk3, vim-gtk2, -athena, -motif, and -x11. The vim-tiny package still exists. Also: only python3 bindings are included now. There are very few plugins written in Perl or Ruby, so there really wasn't a need to bundle those languages with Vim. They still exist as OPTIONS, so you can still enable them if you'd like. Also, support for py27 has been dropped. 20210901: AFFECTS: users of audio/ampache AUTHOR: crees@FreeBSD.org With the upgrade to Ampache 5.0.0, the root Ampache folder has changed to %%WWWDIR%%/ampache/public. Please update your web server aliases, for example if you use Apache, then in httpd.conf make sure the lines look like this: Alias /ampache /usr/local/www/ampache/public If you have customised your .htaccess files to allow for a different alias, you'll need to move them to the new location after upgrading: # sh -c 'cd /usr/local/www/ampache && for f in */.htaccess; do mv $f public/$f; done' More upgrade notes can be found on Github: https://github.com/ampache/ampache/releases/tag/5.0.0 20210823: AFFECTS: users of mail/mu AUTHOR: hrs@FreeBSD.org mail/mu now uses XDG Base Directory Specification for the default locations for various files. The mu database now lives under ~/.cache/mu rather than ~/.mu by default. After upgrading, move the contents under ~/.mu to ~/.cache/mu. 20210823: AFFECTS: users of mail/postfixadmin AUTHOR: ports.maintainer@evilphi.com The 3.2->3.3 upgrade requires generating a new setup password hash. The normal post-upgrade visit to setup.php will walk you through the steps. For more information, see the "Version 3.3" section of the change log: https://github.com/postfixadmin/postfixadmin/blob/postfixadmin-3.3.9/CHANGELOG.TXT 20210818: AFFECTS: users of databases/redis AUTHOR: osa@FreeBSD.org The databases/redis port has been updated to the recent stable release. Users wanting to stay on v6.0 can replace databases/redis with databases/redis6 with one of the following commands: # pkg install databases/redis6 or # portmaster -o databases/redis6 databases/redis or # portupgrade -o databases/redis6 databases/redis 20210805: AFFECTS: users of sysutils/beats7 AUTHOR: otis@FreeBSD.org Beats may not be sending data to some distributions of Elasticsearch In this release, Elastic is enabling a licensing change that was broadly communicated earlier in 2021. This change would imply that 7.13 instances of Beats would fail to connect to 7.10 or earlier open source distributions of Elasticsearch and Kibana. The most visible effect is that sysutils/beats7 users can expect difficulties to send data to Elastic instances hosted in AWS. For more information, see: https://www.elastic.co/guide/en/beats/libbeat/current/breaking-changes-7.13.html 20210801: AFFECTS: users of OpenLDAP AUTHOR: delphij@FreeBSD.org SASL is now always enabled for OpenLDAP. If you use portmaster: portmaster -o net/openldap24-client openldap-sasl-client If you use portupgrade: portupgrade -fo net/openldap24-client openldap-sasl-client If you use pkg with binary packages: pkg set -o net/openldap24-sasl-client:net/openldap24-client 20210730: AFFECTS: users of multimedia/mlt, multimedia/mlt-qt and multimedia/py-mlt AUTHOR: kde@FreeBSD.org multimedia/{py-,}mlt{-qt5,} has been moved to multimedia/{py-,}mlt6{-qt5,} to make room for importin the next major version of the mlt framework. 20210721: AFFECTS: users of x11/rxvt-unicode AUTHOR: thierry@FreeBSD.org Since 9.26, there is a regression in resource parsing, which no longer accepts a prefix of the form "URxvt*keysym" ("*." is equivalent to "*"). Changing "*." to "." should make your bindings work again. 20210704: AFFECTS: users of misc/qtchooser AUTHOR: kde@FreeBSD.org QtChooser allows you to select your version of Qt among those installed. However, this tool is no longer supported upstream and will not be available for Qt6. By default, our Qt installations are done in: ${LOCALBASE}/lib/qt${QT_VERSION} as recommended. We have added symbolic linking for the main binaries to ${LOCALBASE}/bin with the suffix -qt5. 20210628: AFFECTS: users of misc/openhab AUTHOR: netchild@FreeBSD.org You need to run sed -i -e 's:^karaf.framework.equinox=.*:karaf.framework.equinox=mvn\:org.eclipse.platform/org.eclipse.osgi/3.16.200: ; s:^karaf.framework.felix=.*:karaf.framework.felix=mvn\:org.apache.felix/org.apache.felix.framework/6.0.4:' /var/db/openhab/userdata/etc/config.properties to update the version numbers of some components in a config file. 20210621: AFFECTS: users of www/gitlab-ce AUTHOR: mfechner@FreeBSD.org The upgrade of Gitlab 14.0.0 is in preparation. You must upgrade first to 13.12. For more information see here: https://about.gitlab.com/blog/2021/06/04/gitlab-moving-to-14-breaking-changes/ To do the upgrade, make sure you follow the upgrade manuals: https://gitlab.fechner.net/mfechner/Gitlab-docu/-/tree/master/update I will merge the 14.0.0 upgrade later to quarterly branch to give you some time for the upgrade to 13.12. 20210620: AFFECTS: users of misc/openhab2 AUTHOR: netchild@FreeBSD.org The openhab v3 port has been committed. Upstream has removed the version from the name, as such the FreeBSD port follows in all places (start script name, directory names, ...). Users are encouraged to migrate from misc/openhab2 to misc/openhab. No automatic config migration is available Both versions can be installed in parallel, but an users has to take care to not run both at the same time on the same port. 20210617: AFFECTS: users of graphics/mesa-libs and x11/nvidia-driver AUTHOR: kbowling@FreeBSD.org Some libraries from mesa-libs are now provided by libglvnd while others were renamed. nvidia-driver already used libglvnd but bundled a copy which is now provided as a separate package. When building outside poudriere make sure to remove mesa-libs and nvidia-driver first in order to avoid conflict with libglvnd. For portmaster users: # pkg delete -f mesa-libs nvidia-driver # portmaster -a For portupgrade users: # pkg delete -f mesa-libs nvidia-driver # portupgrade -a 20210523: AFFECTS: users of www/tt-rss AUTHOR: dereks@lifeofadishwasher.com tt-rss config.php syntax has changed. You can find detailed changes here https://tt-rss.org/wiki/GlobalConfig or look at config.php.sample. Expect your config.php to not work with newer www/tt-rss releases. Due to changes in ttrssd before updating you should stop ttrssd or otherwise kill the php process running update_daemon2.php. 20210516: AFFECTS: users of security/bitwarden_rs AUTHOR: mr@FreeBSD.org bitwarden_rs has been renamed to vaultwarden upstream. So switch to security/vaultwarden instead. 20210515: AFFECTS: users of databases/postgresql??-server AUTHOR: girgen@FreeBSD.org The rc.conf parameter for the login class of the postgresql daemon has changed name from postgresql_class to postgresql_login_class. rc.subr(8) states that the parameter should be named ${name}_login_class. 20210512: AFFECTS: users of sysutils/ansible* AUTHOR: 0mp@FreeBSD.org Ansible has been updated to 3.3.0. Please follow the porting guide to update the rulesets: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_3.html 20210508: AFFECTS: users of devel/pycharm-ce AUTHOR: bsam@FreeBSD.org Pycharm-ce has switched to the supported java version 11. 20210506: AFFECTS: users of mail/postfix AUTHOR: ohauer@FreeBSD.org Postfix 3.6 and higher requires minimum OpenSSL 1.1.1 FreeBSD 11 users using base OpenSSL can switch to mail/postfix35 If you wish to use postfix35 until FreeBSD 11 EoL you might run the following command: # pkg set -o mail/postfix:mail/postfix35 # pkg upgrade 20210505: AFFECTS: users of sysutils/terraform AUTHOR: 0mp@FreeBSD.org Terraform has been updated from 0.13 to 0.15, which introduces several incompatible changes. Please follow upgrading guide when updating the package. https://www.terraform.io/upgrade-guides/0-14.html https://www.terraform.io/upgrade-guides/0-15.html 20210426: AFFECTS: users of x11-fonts/iosevka AUTHOR: 0mp@FreeBSD.org The selection of options for Iosevka has become less granular as the port has switched from TTF-based distfiles to super-TTC-based distfiles. Now all the spacing variants are contained within one file for each Iosevka style. 20210425: AFFECTS: users of python AUTHOR: kai@FreeBSD.org The default version of python3 and python was switched to 3.8. For ports users wanting to keep version 3.7 as default, add DEFAULT_VERSIONS+= python=3.7 python3=3.7 to make.conf Following procedures may ease the upgrade: For users of pre-build packages: # sh # for i in $(pkg query -g %n 'py37-*'); do pkg set -yn ${i}:py38-${i#py37-}; done # pkg upgrade For portmaster users: # sh # portmaster -o lang/python38 python37 # REINSTALL="$(pkg info -o "*py37*" | awk '{printf "%s ", $2}')" # pkg delete -f "*py37*" # portmaster $REINSTALL # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py38 | cut -d : -f 1 | sort -u) # portmaster $REBUILD # REBUILD2=$(pkg list | grep python-37 | xargs pkg which | awk '{print $6}' | sort -u) # portmaster $REBUILD2 20210420: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v16.0.0, the latest upstream release. This is a major release, including many significant changes. Users are encouraged to read the release announcements before upgrading: https://nodejs.org/en/blog/release/v16.0.0/ 20210416: AFFECTS: Users of shells/bash, shells/bash-static with PORTS_READLINE=off AUTHOR: olce.freebsd@certner.fr Bundled readline now will use LOCALBASE/etc/inputrc as its ultimate default inputrc file (instead of /etc/inputrc). This puts these ports in line with what devel/readline has been doing recently (since 20210103). 20210414: AFFECTS: users of graphics/OpenEXR or graphics/ilmbase AUTHOR: mandree@FreeBSD.org graphics/ilmbase was removed in favor of math/Imath 3.0.1, and graphics/OpenEXR was updated to 3.0.1. Ports that depend on OpenEXR and/or ilmbase according to INDEX were patched, for ports where OpenEXR is an option that defaults to off, these typical items needs to be changed - file bug reports in that case, preferably with tested patches: - The IlmBase parts Imath and half are now repackaged as Imath - The IlmThread and Iex libraries are now part of OpenEXR - Some header files were rearranged accordingly, into ${LOCALBASE}/include/OpenEXR vs. ${LOCALBASE}/include/Imath - Some code needs a few #include statements added, often #include or #include - Some classes were removed, and the C++11 standard library features need to be used, f. i. std::numeric_limits. - Some code used Int64 or SInt64 should use uint64_t or int64_t. Detailed porting hints are available here: https://github.com/AcademySoftwareFoundation/Imath/blob/v3.0.1/docs/PortingGuide2-3.md 20210411: AFFECTS: users or devel/py-RPyC AUTHOR: skozlov@FreeBSD.org devel/py-RPyC has been updated to version 5.0.1, which have some incompatibilities with 4.x branch. Be sure to check them out before upgrading: https://rpyc.readthedocs.io/en/latest/changelog.html#backwards-incompatible 20210414: AFFECTS: users of x11-fonts/oldschool-pc-fonts AUTHOR: evgeniy@khramtsov.org x11-fonts/oldschool-pc-fonts has been upgraded to 2.2. This version changed names of many fonts. If you have configuration files with specific font names set, you need to update your configurations after upgrade. 20210406: AFFECTS: users of www/phpvirtualbox AUTHOR: dereks@lifeofadishwasher.com www/phpvirtualbox has been updated to version 6.1. This new version only supports version 6.1 of VirtualBox. Version 5.x of phpvirtualbox has been preserved as www/phpvirtualbox-legacy. If you require support for VirtualBox 5.x please install this version. Remember to copy your configuration file in the new legacy installation. 20210328: AFFECTS: users of www/caddy AUTHOR: adamw@FreeBSD.org The default locations for caddy runtime files have changed. - Caddy's runtime log is now /var/log/caddy/caddy.log (was /var/log/caddy.log) - Automatic SSL certs are now stored in /var/db/caddy/data/caddy (was /root/.local/share/caddy) - Configuration autosaves are now stored in /var/db/caddy/config/caddy (was /root/.config/caddy) You can change these defaults. See /usr/local/etc/rc.d/caddy for the list of settings. 20210322: AFFECTS: users of net/wireguard AUTHOR: decke@FreeBSD.org A wireguard kernel implementation supporting FreeBSD 12.1 and newer was added as net/wireguard-kmod recently. The new default for users of net/wireguard is the kernel module. If you experience problems with it you can switch back to wireguard-go by removing net/wireguard-kmod and making sure net/wireguard-go is installed. The userland tools wg-quick(8) and wg(8) try to use kernel support if the kernel module is available and otherwise fall back to wireguard-go automatically. Config files are fully compatible. 20210317: AFFECTS: users of security/strongswan AUTHOR: driesm@FreeBSD.org The stroke starter interface has been deprecated by upstream for some time now. The default interface for controlling the charon daemon has switched from stroke to vici. Users still using the legacy config files such as ipsec.conf and ipsec.secret (stroke, starter) can easily revert to the old behavior by: # sysrc strongswan_interface="stroke" It is recommended to use the vici interface which is configured by swanctl.conf. Check : https://wiki.strongswan.org/projects/strongswan/wiki/Fromipsecconf to ease the transition from ipsec.* to swanctl.conf 20210313: AFFECTS: users of net-mgmt/phpipam AUTHOR: marko.cupac@mimar.rs ipaddresses table in phpipam database is likely to contain incorrect datetime values which prevent successful upgrade. Make sure to create backup of phpipam database. Before starting upgrade wizard in web interface run the following SQL query on phpipam database: UPDATE ipaddresses SET lastSeen='1970-01-01 00:00:01' WHERE lastSeen < '0000-01-01 00:00:00'; 20210310: AFFECTS: users of textproc/redisearch AUTHOR: osa@FreeBSD.org The textproc/redisearch port has been updated to the recent stable release - v2.0. Users wanting to stay on v1.6 can replace textproc/redisearch with textproc/redisearch16 with one of the following commands: # pkg install textproc/redisearch16 or # portmaster -o textproc/redisearch16 textproc/redisearch or # portupgrade -o textproc/redisearch16 textproc/redisearch NOTE: The textproc/redisearch16 brings a new name for the module, i.e. redisearch16.so, so be careful. 20210309: AFFECTS: users of emulators/virtualbox-ose AUTHOR: madpilot@FreeBSD.org emulators/virtualbox-ose has been updated to 6.1.18. This new version only works on amd64 hardware. Previous version 5.x of the virtualbox ports have been preserved as emulators/virtualbox-ose-legacy and similarly named ports for the other parts. If you can't run the latest version or wish to stay with the old version, please install the legacy ports. Also the additions at present build successfully only for amd64. If you need i386 additions you can fallback to the old legacy ones. NOTE: There is no support for moving saved running machine states across major updates of virtualbox. It is recommended to properly shutdown all virtual machines before upgrading. Otherwise the saved state can simply be discarded after the upgrade, if it's not important to preserve it. It should also be possible to downgrade to the legacy ports and shutdown the machine properly from the saved state and then upgrade back again. 20210302: AFFECTS: users of editors/emacs-devel AUTHOR: jrm@FreeBSD.org If you get the error "Symbol's value as variable is void: minor-modes", rebuild the offending Emacs packages. See https://lists.gnu.org/archive/html/emacs-devel/2021-02/msg01164.html for details. 20210220: AFFECTS: users of math/py-mathics AUTHOR: thierry@FreeBSD.org math/py-mathics has been split into several ports, and Mathics Core only provides a rudimentary command-line shell called mathics. To get the same functionality as in 1.x, you need to install either mathicsscript or Mathics-Django. 20210219: AFFECTS: users of games/mangband AUTHOR: adridg@FreeBSD.org The client has updated from 1.1.3 (which has a single public server left) to the current 1.5.3 (which has more public servers). If you update, you can NOT connect to the old server any more. Remember to finish your game before updating. 20210210: AFFECTS: users of audio/spotifyd AUTHOR: rodrigo@FreeBSD.org The configuration format for audio/spotifyd is now TOML, make sure to update your configuration file after upgrading the port. Look at the sample configuration file for a working example. https://github.com/Spotifyd/spotifyd/blob/master/docs/src/config/File.md 20210208: AFFECTS: users of mail/mailscanner AUTHOR: crees@FreeBSD.org The clamavmodule has finally been removed after a long deprecation period. Please remove all references to it in your mailscanner.conf as it will now count as a syntax error and may stop MailScanner starting! 20210204: AFFECTS: users of www/unit AUTHOR: osa@FreeBSD.org The default location for NGINX Unit's state directory has changed. It was moved from /usr/local/libexec/unit to /var/db/unit in order to avoid write operations on /usr/local filesystem. 20210130: AFFECTS: users of graphics/opencv-core AUTHOR: tcberner@FreeBSD.org graphics/opencv-core has been reintegrated into graphics/opencv. So there is no longer a circular dependency opencv-core -> ffmpeg -> opencv If you experience problems updating the packages, try pkg delete -f opencv-core 20210124: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org The Django templating language (DTL) is no longer supported for export templates. Please ensure that all export templates use Jinja2 before upgrading. Also the support for embedded graphs was completely removed and several changes to the REST API were made. Please check the changelogs for further details. 20210114: AFFECTS: users of net-im/matterircd AUTHOR: norrland@nullbyte.se Commandline switches Switched to viper for cmdline parsing, which does not support "short" flags. You'll need to use --flag instead of -flag. Eg ./matterircd --debug Bridge specific configuration is now only in configuration file. This means the following flags have been removed: -restrict,-mmteam,-mmserver, -mminsecure,-mmskiptlsverify. You can set those in matterircd.toml, see the example file. Config changes BlacklistUser feature for slack has been renamed to DenyUsers. JoinMpImOnTalk feature has been renamed to JoinDM and is available for slack/mattermost JoinInclude, JoinExclude now support regexp (see matterircd.toml.example) 20210113: AFFECTS: users of databases/redis[-devel] AUTHOR: osa@FreeBSD.org The databases/redis port has been updated to the recent stable release. Users wanting to stay on v5.x can replace databases/redis with databases/redis5 with one of the following commands: # pkg install databases/redis5 or # portmaster -o databases/redis5 databases/redis or # portupgrade -o databases/redis5 databases/redis 20210106: AFFECTS: mail/dovecot AUTHOR: pi@FreeBSD.org The VPOPMAIL option was removed, because it was dropped upstream, so please check your config before upgrading. 20210106: AFFECTS: sysutils/graylog AUTHOR: dch@FreeBSD.org graylog 4.0 and higher now use a new license, the SSPL. For more details, see https://www.graylog.org/post/graylog-v4-0-licensing-sspl 20210102: AFFECTS: x11/libexo, XFCE4 desktop users AUTHOR: madpilot@FreeBSD.org XFCE4 has been updated to version 4.16. Unluckily due to how the update works out it interacts badly with a defect in pkg which can cause files from the libexo package to be absent after upgrade. To avoid the issue, before upgrading all packages, please update libexo by itself: # pkg upgrade libexo # pkg upgrade If you have already upgraded and you notice XFCE issues due to missing libraries you can recover easily by forcing reinstallation of libexo: # pkg upgrade -f libexo Users upgrading via ports should not be affected. 20201228: AFFECTS: www/py-flexget AUTHOR: jbeich@FreeBSD.org py-flexget (or py37-flexget) has been renamed to flexget. "pkg upgrade" doesn't track MOVED file unlike portmaster, so provide a hint e.g., $ pkg upgrade -x flexget or install again, letting pkg remove the old version $ pkg install flexget 20201218: AFFECTS: users of www/qt5-webengine AUTHOR: kai@FreeBSD.org Users that upgrade www/qt5-webengine without using pkg/poudriere might experience failures due to conflicts with the installed version of 5.15.2. In that case, pkg delete -f the qt5-webengine package before building the updated version. 20201130: AFFECTS: users of graphics/jpeg AUTHOR: rene@FreeBSD.org The graphics/jpeg port has been removed in favor of graphics/jpeg-turbo. The former port was vulnerable and used an outdated ABI and API. Please check your make configuration for JPEG_PORT and remove it or set it to "jpeg-turbo" if it is currently set to "jpeg". 20201128: AFFECTS: users of databases/cego AUTHOR: pi@FreeBSD.org Database updates from 2.45.x to 2.46.x require a xml tableset export and import, since table structure information has been changed. 20201128: AFFECTS: users of lang/ruby26 AUTHOR: mfechner@FreeBSD.org The default ruby version has been updated from 2.6 to 2.7. If you compile your own ports you may keep 2.6 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.6 as default version # DEFAULT_VERSIONS+=ruby=2.6 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkg, simply upgrade: # pkg upgrade If you do not use pkg, please check entry 20190420. The description there should also work for this version. 20201112: AFFECTS: users of net-mgmt/pushgateway AUTHOR: rhurlin@FreeBSD.org The v0.10.0 release changes the storage format. v0.10 can read the storage format of v0.5--v0.9. It will then persist the new format so that a downgrade won't be possible anymore [1]. For later releases >= v1.0.0 only persistence files created by v0.10+ are usable. So please, upgrade to v0.10 first to convert existing persistence files. It is intended to replace v0.10.0 in about four weeks from now (not before 2020-12-12) by >= v1.3.0. [1] https://github.com/prometheus/pushgateway/releases/tag/v0.10.0 20201110: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org Changes related to the NetBox configuration: 1. If in use, LDAP authentication must be enabled by setting REMOTE_AUTH_BACKEND to 'netbox.authentication.LDAPBackend'. (The LDAP configuration parameters in ldap_config.py remain unchanged.) 2. REMOTE_AUTH_DEFAULT_PERMISSIONS now takes a dictionary rather than a list. This is a mapping of permission names to a dictionary of constraining attributes, or None. For example, ['dcim.add_site', 'dcim.change_site'] would become {'dcim.add_site': None, 'dcim.change_site': None}. 3. Support for the DEFAULT_TIMEOUT parameter under REDIS database configuration was removed. Set RQ_DEFAULT_TIMEOUT as a global configuration parameter instead. Please also check the pkg-message and the changelogs for further info. 20201106: AFFECTS: users of www/samdruckerserver AUTHOR: dvl@FreeBSD.org If upgrading from < 0.2.4, the database schema has changed. Run these scripts to update your database: * PostgreSQL/updates-2020.08.28.sql * PostgreSQL/procedures.sql These scripts are in /usr/local/share/samdrucker/PostgreSQL 20201030: AFFECTS: users of security/openvpn AUTHOR: mandree@FreeBSD.org The security/openvpn port has been updated to v2.5.0, which brings a change to the default ciphersuite, which no longer contains BF-CBC. Some options have been removed. Also, if you need to support very old (v2.3) and unsupported clients or servers, you will need to adjust the configuration. For details, see: https://github.com/OpenVPN/openvpn/blob/release/2.5/Changes.rst#overview-of-changes-in-25 20201029: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v15.0.0, the latest upstream release. A new port, www/node14, has been created for the v14.x LTS branch. Users wanting to stay on v14.x can replace www/node with www/node14 with one of the following commands: # pkg install www/node14 or # portmaster -o www/node14 www/node or # portupgrade -o www/node14 www/node 20201026: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org emulators/qemu has been updated to 5.0.1. Previous 4.2.X branch has been repocopied to emulators/qemu42. If someone wants to stick with 4.2.X branch please use one of the following command: # pkg install emulators/qemu42 or # portmaster -o emulators/qemu42 emulators/qemu or # portupgrade -o emulators/qemu42 emulators/qemu 20201021: AFFECTS: users of www/py-unit AUTHOR: osa@FreeBSD.org The www/py-unit port has been renamed to www/unit-python. 20201012: AFFECTS: Users of mesa-dri with VAAPI or VDPAU options AUTHOR: manu@FreeBSD.org The nondefault options VAAPI and VDPAU were removed from the mesa-dri port and two new ports, mesa-gallium-va and mesa-gallium-vdpau now contain the necessary libraries for using VAAPI or VDPAU on AMD hardware. 20201012: AFFECTS: users of devel/libsoup-gnome AUTHOR: bapt@FreeBSD.org libsoup-gnome has been merged back into libsoup for people building locally: first delete libsoup-gnome before installing the new libsoup $ pkg delete -f libsoup-gnome 20201011: AFFECTS: users of sysutils/rundeck3 who use MySQL as database AUTHOR: daniel.tihanyi@tetragir.com Please note that the MySQL JDBC driver is no longer bundled with Rundeck. Please make sure that you migrate to the MariaDB Connector or copy the driver yourself. More instructions: https://docs.rundeck.com/docs/upgrading/upgrading-to-rundeck-3.3.4.html 20201006: AFFECTS: users of sysutils/tenshi AUTHOR: 0mp@FreeBSD.org The default location for tenshi's configuration file has changed. It was moved to /usr/local/etc/tenshi/tenshi.conf from /usr/local/etc/tenshi.conf in order to follow upstream defaults. 20201002: AFFECTS: users of mail/fetchmail beginning with 6.4.12_1 AUTHOR: mandree@FreeBSD.org Note that if you are using fetchmail in a multi-user setup, i. e. with the fetchmail_users (mind the -s!) variable set, the $fetchmail_home_prefix + user second-guess work has been replaced by a real lookup of the user's home directory. In the majority of configurations, this should not make a difference, in some setups, it may open up some flexibility. The fetchmail_home_prefix variable is ignored from 6.4.12_1 onwards. Also, the rc script redirects its input from /dev/null so that passwords will not be interactively queried from an rcfile. Put passwords into the [.]fetchmailrc or into a .netrc file. 20201002: AFFECTS: users of sysutils/modules AUTHOR: 0mp@FreeBSD.org The upstream developers of the Modules port encourage users to consult the MIGRATING document, which describes the major changes occurring between versions of Modules. It provides an overview of the new features and changed behaviors that will be encountered when upgrading: https://modules.readthedocs.io/en/v4.6.0/MIGRATING.html 20200930: AFFECTS: users of sysutils/syslog-ng32[789] AUTHOR: cy@FreeBSD.org rc.conf variables syslog_ng_config and syslog_ng_pid have been replaced by syslog_ng_flags and syslog_ng_pidfile respectively, making them consistent with the rest of the ports tree. syslog_ng_config and syslog_ng_pid will continue to work until syslog-ng331 has been released and imported into ports. 20200924: AFFECTS: users of net/freeradius3, who need python support AUTHOR: zi@FreeBSD.org FreeRADIUS 3.x currently uses python 2.7 for rlm_python support, which has been deprecated and will be removed from the tree at the end of this year. Starting in 3.0.21_2, the PYTHON option has been converted to use python 3.x. Users should verify their python scripts are 3.x compatible and upgrade to 3.0.21_2 (or higher) to bring in python 3.x support. 20200921: 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 11 to 12. 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 11.9, your files are named according to this. # service postgresql stop # pkg create postgresql11-server postgresql11-contrib # mkdir /tmp/pg-upgrade # tar xf postgresql11-server-11.9.txz -C /tmp/pg-upgrade # tar xf postgresql11-contrib-11.9.txz -C /tmp/pg-upgrade # pkg delete -f databases/postgresql11-server databases/postgresql11-contrib databases/postgresql11-client Now update PostgreSQL: pkg user: # pkg install databases/postgresql12-server databases/postgresql12-contrib # pkg upgrade Portmaster users: # portmaster databases/postgresql12-server databases/postgresql12-contrib # portmaster -a Portupgrade users: # portinstall databases/postgresql12-server databases/postgresql12-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/data12 -U postgres" # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data11/ -B /usr/local/bin/ -D /var/db/postgres/data12/ -U postgres " Now the migration is finished. You can start PostgreSQL again with: # service postgresql start ATTENTION: 1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume the "postgres" database user and FreeBSD user. 2) See the updating entry 20190829 if you are updating from a release prior to 11. 3) If you use non-default initdb options, you have to adjust the initdb-command accordingly 20200918: AFFECTS: users of mail/thunderbird AUTHOR: cmt@FreeBSD.org Thunderbird has been updated to the 78esr series. Thunderbird will try to convert old profiles on first start, but conversion may fail especially on old profiles. Also, older versions of Thunderbird will not be able to use a profile once it has been converted. It is strongly recommended to move any ~/.thunderbird folder away before starting Thunderbird 78 for the first time, thus creating a new and empty profile. Also note that OpenPGP functionality has been integrated into Thunderbird, obsoleting the Enigmail extension. Check https://wiki.mozilla.org/Thunderbird:OpenPGP for details, and especially https://wiki.mozilla.org/Thunderbird:OpenPGP:Smartcards if your private key lives on a smartcard. 20200914: AFFECTS: users of lang/php72 AUTHOR: tz@FreeBSD.org The default version of PHP has been switched from 7.2 to 7.4. If you use binary packages you should make a list of php packages before running 'pkg upgrade': # pkg info php7\* > ~/installed-php-ports-list After the upgrade, check with such list if all your php extensions are still installed, and reinstall them if needed. If you use mod_php72 you need to deinstall it and install mod_php74. 20200811: AFFECTS: users of *-emacs26-* packages AUTHOR: jrm@FreeBSD.org With the release of Emacs version 27.1, the major version of editors/emacs has changed from 26 to 27. This means the names of some dependent packages have also changed, so simply running `pkg upgrade` will not upgrade foo-emacs26-x to foo-emacs27-x. To update these packages, run these commands with superuser privileges. Binary package users: # sh # for i in $(pkg query -g %n '*-emacs26*'); do \ nn=$(echo "$i" | sed -e 's/emacs26/emacs27/'); \ pkg set -yn "$i":"$nn"; \ done; # pkg upgrade portmaster users: # portmaster -r emacs 20200803: AFFECTS: users of lang/perl5* AUTHOR: mat@FreeBSD.org The default Perl version has been switched to Perl 5.32. If you are using binary packages to upgrade your system, you do not have anything to do, pkg upgrade will do the right thing. For the other people, follow the instructions in entry 20161103, it should still be the same. 20200726: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org The %%WWWDIR%%%/logs directory has been relocated to /var/log/librenms/ via the APP_LOG directive in %%WWWDIR%%%/.env.example - this won't affect existing installs, but you are strongly encouraged to update your .env file settings and relocate your logs. Logs which were going to /var/log/messages and /var/log/librenms/ now only go to /var/log/librenms/ 20200720: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org As mentioned previously in 20200503 polling via cronjob has been removed as of release 1.63 - see https://community.librenms.org/t/dropping-support-for-php-7-1-and-python-2/11851 A database upgrade is required: cd /usr/local/www/librenms sudo ./lnms migrate You must migrate to the Dispatch Service: https://docs.librenms.org/Extensions/Dispatcher-Service/ You may need to add LIBRENMS_USER to .env (see .env.example). These steps should get you running: * comment out the crontab entries listed above under PYPOLLER * populate %%WWWDIR%%/.env with: * APP_KEY - see farther below for how to create * NODE_ID - see just below for how to create * DB_HOST * DB_DATABASE * DB_USERNAME * DB_PASSWORD * you can create a NODE_ID with: php -r 'echo uniqid() . "\n";' * sysrc librenms_enable="YES" * service librenms start 20200719: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org emulators/qemu has been updated to 4.2.1. Previous 4.1.X branch has been repocopied to emulators/qemu41. If someone wants to stick with 4.1.X branch please use one of the following command: # pkg install emulators/qemu41 or # portmaster -o emulators/qemu41 emulators/qemu or # portupgrade -o emulators/qemu41 emulators/qemu 20200716: AFFECTS: users of shells/bash, shells/bash-static AUTHOR: ehaupt@FreeBSD.org In order to cleanly decouple bash from base, bash now reads `profile` from LOCALBASE/etc insead of from /etc. If you are using system wide bash configuration in /etc/profile please migrate to LOCALBASE/etc/profile # cp /etc/profile /usr/local/etc/profile or create a symlink # ln -s /etc/profile /usr/local/etc/ If you encounter the following error, you may have the obsolete /lib/libreadline.so.8 lying around after an incomplete base update: ld-elf.so.1: Undefined symbol "rl_signal_event_hook" referenced from COPY relocation in /usr/local/bin/bash Please refer to to (23.5.6.2) in the FreeBSD Handbook on how to safely check for outdated files and libraries: https://www.freebsd.org/doc/en/books/handbook/makeworld.html 20200713: AFFECTS: users of mail/php7[2-4]-imap AUTHOR: tz@FreeBSD.org The imap module of PHP was compiled against cclient till now. But this lib is unmaintained for over 7 years. When combined with modern OpenSSL there are various crashes reported. Switching to the fork panda-cclient fixes these issues. Therefore we make the usage of Panda cclient the new default. If you want to use the old cclient, you need to enable it now! 20200616: AFFECTS: users of www/baikal AUTHOR: gahr@FreeBSD.org The www/baikal has been updated to 0.7.1. With the 0.7.0 release, our configuration format was updated to use YAML files. You need to go through the installer again but we pre-fill most values with the ones from your old installation. We recommend that you make a full backup of your data, as a safety measure. Starting with 0.7.0, Baikal stores data in both the Specific and the config folders. Keep this in mind when upgrading! Known issue:: Upgrading from versions older than 0.6.1 does not work. 20200613: AFFECTS: users of editors/libreoffice AUTHOR: fluffy@FreeBSD.org LibreOffice was updated to 6.4 branch with some critical changes: - GTK2 option is obsolete by upstream - GTK3 option is not more set by default because of unstable yet and have visual glitches - QT5 option is set by default to provide comfy visual style for every user - KDE option was renamed to KF5 follows upstream Please re-run "make config" to pick up the new defaults 20200610: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v14.0.0, the latest upstream release. This is a major release, including many significant changes. Users are encouraged to read the release announcements before upgrading: https://nodejs.org/en/blog/release/v14.0.0/ 20200602: AFFECTS: users of www/radicale AUTHOR: decke@FreeBSD.org Migration from radicale 1.x to 2.x requires that you export the storage with radicale 1.1.6 before updating. Migration instructions are available at: https://web.archive.org/web/20190314225402/https://radicale.org/1to2/ 20200602: AFFECTS: users of sysutils/py-salt AUTHOR: krion@FreeBSD.org This port is moved to sysutils/py-salt-2019 and sysutils/py-salt was updated to version 3000. If you wish to use pysalt-2019 in the future, you might run the following command: # pkg set -o sysutils/py-salt:sysutils/py-salt-2019 # pkg upgrade 20200531: AFFECTS: users of mail/postfix-policyd-spf-python AUTHOR: yasu@utahime.org This port is now deprecated because upstream project is superseded by its successor. So uninstall this port and install mail/py-spf-engine instead. Keep in mind that the path of configuration file is changed from ${PREFIX}/etc/postfix-policyd-spf-python/policyd-spf.conf to ${PREFIX}/etc/python-policyd-spf/policyd-spf.conf. So you need to move it to new location unless you use the default one without changing. 20200526: AFFECTS: users of databases/mariadb104-client, databases/mariadb104-server AUTHOR: brnrd@FreeBSD.org The ports now add sample configuration files to /usr/local/etc/mysql. You must merge your client configuration with the conf.d/client.cnf and your server configuration with conf.d/server.cnf. 20200518: AFFECTS: users of converters/libiconv AUTHOR: zeising@FreeBSD.org Support for the Japanese specific patches have been discontinued. These were previously added in a nondefault ports options, for people who needed them. If you still need them, it might be possible to create a port of libiconv 1.14 which includes those patches. 20200517: AFFECTS: users of x11/sddm AUTHOR: arrowd@FreeBSD.org The home directory of sddm user has been moved to /var/lib/sddm. It is advised to run following commands as root after updating the package: # pw usermod -n sddm -d /var/lib/sddm # pwd_mkdb /etc/master.passwd # mv /usr/local/etc/sddm/home/state.conf /var/lib/sddm/state.conf # rm -rf /usr/local/etc/sddm/home Otherwise, SDDM will keep using /usr/local/etc/sddm/home/ as its HOME. 20200515: AFFECTS: users of devel/libphutil, devel/arcanist-lib, devel/phabricator AUTHOR: grembo@FreeBSD.org Upstream fully deprecated devel/libphutil and merged its functionality into devel/arcanist-lib and devel/phabricator. As a result, the devel/libphutil port will be removed from the ports tree. After upgrading devel/(arcanist-lib|phabricator) to version 20200514, it is recommended to remove the orphaned libphutil package by running: # pkg delete php\*-libphutil Alternatively, 'pkg autoremove' will also work as expected, but might remove orphaned packages unrelated to this update. 20200505: AFFECTS: users of net-im/pidgin-rocketchat AUTHOR: tobias.rehbein@web.de This port has been turned into a libpurple plugin (net-im/purple-rocketchat) to support other libpurple clients than pidgin. This also changes some dependencies and you should run the following command to prevent pidgin from being autoremoved. # mark pidgin as being not automatically installed pkg set -A 0 pidgin 20200504: AFFECTS: users of x11-wm/hs-xmonad AUTHOR: arrowd@FreeBSD.org From now, it is recommended to use "build script" method to compile XMonad config. See https://github.com/xmonad/xmonad-testing/ for general info and port's pkg-message for concrete steps. 20200503: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org Polling via cronjob is deprecated as of release 1.63 Please see https://community.librenms.org/t/dropping-support-for-php-7-1-and-python-2/11851 Please migrate to the Dispatch Service: https://docs.librenms.org/Extensions/Dispatcher-Service/ These steps should get you running: * comment out the crontab entries listed above under PYPOLLER * populate %%WWWDIR%%/.env with: * APP_KEY - see farther below for how to create * NODE_ID - see just below for how to create * DB_HOST * DB_DATABASE * DB_USERNAME * DB_PASSWORD * you can create a NODE_ID with: php -r 'echo uniqid() . "\n";' * sysrc librenms_enable="YES" * service librenms start 20200501: AFFECTS: users of www/phpmyfaq AUTHOR: flo@FreeBSD.org phpMyFAQ has been updated to 3.0.2, old templates are not compatible with this new version. Please see: https://www.phpmyfaq.de/docs/3.0#3.4 20200428: AFFECTS: users of sysutils/ansible AUTHOR: bofh@FreeBSD.org Ansible has been updated to 2.9.7. Please follow the porting guide to update the rulesets: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html If you wish to stay with 2.8 version, you can switch to new sysutils/ansible28 port, which tracks stable 2.8 branch: # pkg set -n ansible:ansible28 20200428: AFFECTS: x11-servers/xwayland-devel AUTHOR: jbeich@FreeBSD.org DRI3 is enabled by default since mesa-libs-18.3.2_4, so you no longer need to define LIBGL_DRI3_ENABLE in ~/.profile or ~/.login. See 20200308 entry for more details. 20200422: AFFECTS: users of devel/kyua AUTHOR: brooks@FreeBSD.org A tests group has been added and the tests user should be a member of it by default rather than nobody. You should update your password database to match (change the group from 65534 to 977 after updating). Please use the following command to do so: pw usermod -n tests -g tests 20200408: AFFECTS: users of security/openssh-portable AUTHOR: bdrewery@FreeBSD.org OpenSSH was upgraded to 8.2p1 on 2020-03-23. A restart of sshd is required after upgrade due to an incompatibility introduced in 8.2. Please see https://www.openssh.com/txt/release-8.2 for upcoming deprecation notices. 20200408 AFFECTS: users of net/irrd AUTHOR: bofh@FreeBSD.org Legacy version of net/irrd has been moved to net/irrd-legacy. net/irrd has been upgraded to 4.X branch. If someone wants to stick with legacy version then pkg users have to do something like # pkg set -o net/irrd:net/irrd-legacy For portmaster users # portmaster -o net/irrd-legacy net/irrd Both of the version can be installed and used concurrently in case there is a need for migration 20200403: AFFECTS: users of x11-fonts/fontconfig AUTHOR: desktop@FreeBSD.org Fontconfig 2.13.1 generated .uuid files in the fonts directory which where not properly registered to the packages. To clean them up, please execute the following command: find /usr/local/share/fonts -type f -name .uuid -delete 20200326: AFFECTS: users of devel/sonarqube and devel/sonar-ant-task AUTHOR: netchild@FreeBSD.org The outdated port devel/sonarqube has moved to devel/sonarqube-community to make it clear that it is the community edition. The log and DB files are still stored in the same location. The devel/sonar-ant-task port has moved to devel/sonarqube-ant-task to match the upstream-name. The install location is renamed accordingly. At the same time the user/group of the sonarqube port changed from www:www to sonarqube:sonarqube. It is expected that nobody was using the 6.2 version from 2016 anymore and no change needs to be done. No analysis was done to check if the old 6.2 version can be updated in-place to the 8.2 version. As such if there is still someone using the old 6.2 version, you may have to delete /var/log/sonarqube and /var/db/sonarqube before installing the new version. 20200320 AFFECTS: users of devel/qca AUTHOR: kde@FreeBSD.org New versions of devel/qca stopped supporting OpenSSL < 1.1. For this reason devel/qca-legacy has been added, which is held back at an older version until FreeBSD 11 goes EOL. Ports depending on devel/qca should stop adding direct LIB_DEPENDS and switch to depending on it via USES=qca. FreeBSD 11 users might want to run something like pkg set -o devel/qca:devel/qca-legacy 20200320: AFFECTS: users of x11/libxkbcommon AUTHOR: zeising@FreeBSD.org The libxkbcommon library (x11/libxkbcommon), used to handle keyboards in some applications, most notably kde and wayland, have been switched to use evdev rules by default on FreeBSD 12 and later. Some keys, most notably arrow keys, may not work in applications using libxkbcommon if you are using xf86-input-keyboard rather than xf86-input-libinput. If you have trouble with the keyboard keys, and if /var/log/Xorg.*.log shows that the "kbd" or "keyboard" driver is being used, you need to switch to legacy rules by setting the environment variable XKB_DEFAULT_RULES to xorg. This switch is made to match the default configuration on FreeBSD 12.1 and later, the default configuration on FreeBSD 11.3 still uses the legacy rules. 20200316: AFFECTS: users of net-im/slack-term AUTHOR: dmgk@FreeBSD.org The config file location was changed from ~/.slack-term to ~/.config/slack-term/config, please move your existing config file accordingly. 20200308 AFFECTS: users of graphics/mesa-libs and legacy graphics drivers AUTHOR: zeising@FreeBSD.org The mesa OpenGL library (graphics/mesa-libs) has been switched to use DRI3 by default, instead of the older DRI2 interface. This might cause regressions when using the legacy graphics drivers, either through graphics/drm-legacy-kmod or the graphics drivers in base. If you experience issues when running OpenGL applications it is possible to force the use of DRI2 by setting the LIBGL_DRI3_DISABLE environment variable to 1 before starting any OpenGL application. The easiest way to do this is by adding it to either your shell startup files or .xinitrc. 20200306 AFFECTS: users of databases/mysql80-server AUTHOR: joneum@FreeBSD.org As of MySQL 8.0.16, the MySQL server performs the upgrade tasks previously handled by mysql_upgrade. Consequently, mysql_upgrade is unneeded and is deprecated as of that version, and will be removed in a future MySQL version. Because mysql_upgrade no longer performs upgrade tasks, it exits with status 0 unconditionally. 20200303: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org 1. Apache / mod_php options removed The APACHEMOD option has been removed. LibreNMS can be used with other webservers, not just Apache. In order to simplify the port, the option was removed. Now you manually install the webserver of your preference. If upgrading from LibreNMS < 1.61, you can do this to prevent 'pkg autoremove' from uninstalling Apache / mod_php: $ sudo pkg set -A 0 apache24 mod_php74 Mark apache24-2.4.41 as not automatically installed? [y/N]: y Mark mod_php74-7.4.3 as not automatically installed? [y/N]: y Adjust mod_php74 to suit the version of mod_php you have. 2. include/defaults.inc.php is gone The file include/defaults.inc.php is no longer distributed by the upstream project. The FreeBSD port patched this file to correct the paths to common tools such as ping, snmpwalk, etc. These values previously adjusted by the port must now be specified in config.php. New installs will have this automatically, but existing installs must be updated manually. These are the entries you should add if upgrading from LibreNMS < 1.61: $config['snmpwalk'] = '/usr/local/bin/snmpwalk'; $config['snmpget'] = '/usr/local/bin/snmpget'; $config['snmpbulkwalk'] = '/usr/local/bin/snmpbulkwalk'; $config['snmptranslate'] = '/usr/local/bin/snmptranslate'; $config['ping'] = '/sbin/ping'; $config['mtr'] = '/usr/local/bin/mtr'; $config['nmap'] = '/usr/local/bin/nmap'; $config['nagios_plugins'] = '/usr/local/libexec/nagios'; $config['ipmitool'] = '/usr/local/bin/ipmitool'; $config['virsh'] = '/usr/local/bin/virsh'; $config['dot'] = '/usr/local/bin/dot'; $config['sfdp'] = '/usr/local/bin/sfdp'; $config['nfdump'] = '/usr/local/bin/nfdump'; 20200229: AFFECTS: users of textproc/apache-solr AUTHOR: mfechner@FreeBSD.org Apache-solr switched to the supported java LTS version 11. Make sure you update the following files accordingly: /usr/local/etc/solr.in.sh (see /usr/local/etc/solr.in.sh.sample) /usr/local/etc/javavm_opts.conf (JAVA_HOME=/usr/local/openjdk11/) 20200225: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org 1. Removal of the Topology Maps feature The deprecated topology maps feature has been removed. Please replicate any required data to another source before upgrading NetBox to v2.7.7, as any existing topology maps will be deleted. 2. Changed REDIS database configuration settings The REDIS database configuration parameters were splitted up in two discrete subsections named "webhooks" and "caching" with the 2.7 release. This requires modification of the REDIS parameter in configuration.py as follows: Old Redis sample configuration: REDIS = { 'HOST': 'localhost', 'PORT': 6379, 'PASSWORD': '', 'DATABASE': 0, 'CACHE_DATABASE': 1, 'DEFAULT_TIMEOUT': 300, 'SSL': False, } New Redis sample configuration: REDIS = { 'webhooks': { 'HOST': 'redis.example.com', 'PORT': 1234, 'PASSWORD': 'foobar', 'DATABASE': 0, 'DEFAULT_TIMEOUT': 300, 'SSL': False, }, 'caching': { 'HOST': 'localhost', 'PORT': 6379, 'PASSWORD': '', 'DATABASE': 1, 'DEFAULT_TIMEOUT': 300, 'SSL': False, } } Note that the CACHE_DATABASE parameter has been removed and the connection settings have been duplicated for both webhooks and caching. This allows one to make use of separate Redis instances if desired. It is fine to use the same Redis service for both functions, although the database identifiers should be different. Please also check the pkg-message and the changelogs for further info. 20200223: AFFECTS: users of security/gsasl AUTHOR: hrs@FreeBSD.org The library part of security/gsasl has been split into security/libgsasl. The security/gsasl now depends on security/libgsasl. Due to this change, old security/gsasl conflicts with the new security/libgsasl and it can prevent the installed security/gsasl from upgrading. Please remove the installed security/gsasl before upgrading if a conflict error occurs. 20200220: AFFECTS: users of x11-servers/xorg-server AUTHOR: zeising@FreeBSD.org x11-servers/xorg-server has been updated to 1.20.7. With this update, xorg-server has switched from using the devd backend to the udev backend for device configuration on FreeBSD 12 and 13. If you have issues with input devices, please see the install message for details. The HAL backend option has been completely removed, as it was deprecated. If you have problems with input devices, ensure that both x11/libinput and x11-drivers/xf86-input-libinput are installed. They are installed in the default configuration, but if you have a custom configuration, they might not be. 20200210: AFFECTS: users of net-im/prosody AUTHOR: thomas@beingboiled.info Prosody's pid file and data directory have moved to a new location. If you are upgrading from a version with the pid file and data directory in /usr/local/var/lib/prosody please perform these steps: # stop Prosody pkill -F /usr/local/var/lib/prosody/prosody.pid # copy the data directory cp -a /usr/local/var/lib/prosody /var/db/ rm -f /var/db/prosody/prosody.pid Make sure your prosody config has the following option set: pidfile = "/var/run/prosody/prosody.pid" Then start Prosody again. Everything should be working as before and the /usr/local/var/lib/prosody directory can now be removed. 20200207: AFFECTS: users of security/nss AUTHOR: lwhsu@FreeBSD.org NSS header files and libraries have been moved from ${PREFIX}/include/nss/nss and ${PREFIX}/lib/nss to ${PREFIX}/include/nss and ${PREFIX}/lib 20200204: AFFECTS: users of editors/vim AUTHOR: adamw@FreeBSD.org The PYTHON2 and PYTHON3 options have been turned into a single PYTHON option that uses whichever python you've set as default. However, this means that you cannot have both python2 and python3 support at the same time. 20200126: AFFECTS: users of multimedia/gstreamer1-plugins[-bad] AUTHOR: kwm@freebsd.org In GStreamer 1.16 some files moved from the gstreamer1-plugins-bad package to the gstreamer1-plugins package. If your using a tool like portmaster or portupgrade delete the old -bad port and then follow the normal upgrade method. # pkg delete -f gstreamer1-plugins-bad 20200126: AFFECTS: users of sysutils/helm AUTHOR: danilo@FreeBSD.org The Helm project have deprecated the Tiller utility in Helm 3. If you are using Helm 2 you will need to migrate the configuration to be compatible with Helm 3. Please, refer to the following documentation for more information about the migration process: https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/ Note that the 2to3 plugin binary is not available for FreeBSD and you will need to compile it yourself. 20200113: AFFECTS: users of python and net/samba410, devel/talloc, devel/tevent, databases/tdb, databases/ldb* AUTHOR: timur@FreeBSD.org In the entry 20191216 for the Python update the filtering constrains are too limiting and omit the Samba supplimentary libraries, which do have Python bindings to the default Python 3.x version. With the update of the default Python3 version you also need to rebuild all the supplementary Samba libraries and samba410 itself. For portmaster users it would be enough to run: # portmaster devel/talloc devel/tevent databases/tdb databases/ldb15 net/samba410 20200109: AFFECTS: www/firefox AUTHOR: gecko@FreeBSD.org Firefox requires Capsicum since r522464 for IPC and in future will require Capsicum for process sandboxing. If you use a custom kernel make sure to copy the following lines from GENERIC kernel: options CAPABILITY_MODE # Capsicum capability mode options CAPABILITIES # Capsicum capabilities 20200107: AFFECTS: Users of *-emacs27-* packages AUTHOR: ashish@FreeBSD.org There is a major version bump in 28.0.50, therefore to upgrade all the packages dependent on editors/emacs-devel, please use the following commands: # sh # for i in $(pkg query -g %n '*-emacs27*'); do \ nn=$(echo "$i" | sed -e 's/emacs27/emacs28/'); \ pkg set -yn "$i":"$nn"; done; # pkg upgrade 20200106: AFFECTS: users of net/gnatsd AUTHOR: olgeni@FreeBSD.org net/gnatsd has been replaced by net/nats-server to reflect the new naming upstream. All options in rc.conf should be renamed by replacing 'gnats' with 'nats' (nats_enable, nats_user, nats_options). 20200101: AFFECTS: users of security/openssl and security/openssl111 AUTHOR: brnrd@FreeBSD.org The openssl port was removed on 2019-12-31, subsequently the openssl111 port was renamed to openssl on 2020-01-01. The shared library version of OpenSSL has been bumped. Users of DEFAULT_VERSIONS= ssl=openssl111 must update this to ssl=openssl. You must rebuild all ports that depend on OpenSSL if you use OpenSSL from ports. 20191226: AFFECTS: users of sysutils/dsbmd AUTHOR: mk@freeshell.de With version 1.10 dsbmd now uses sysutils/fusefs-jmtpfs for mounting MTP devices. Please adjust your dsbmd.conf or recreate it from the new dsbmd.conf.sample. 20191225: AFFECTS: multimedia/libva-intel-media-driver AUTHOR: jbeich@FreeBSD.org As of libva 2.6.0 iHD driver is automatically enabled, so you no longer need to adjust LIBVA_DRIVER_NAME in ~/.profile or ~/.login. 20191221: AFFECTS: users of misc/openhab2 AUTHOR: netchild@FreeBSD.org If you upgrade from a pevious version, make a backup of /var/db/openhab2 read about the breaking changes in the release notes at https://github.com/openhab/openhab-distro/releases/tag/2.5.0 and run %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd which takes care about changes for: - Textual Configuration - Next Generation Rule Engine 20191216: AFFECTS: users of python AUTHOR: antoine@FreeBSD.org Default version of python3 and python was switched to 3.7. For ports users wanting to keep version 3.6 as default, add DEFAULT_VERSIONS+= python=3.6 python3=3.6 to make.conf This may ease the upgrade for users of pre-build packages: # sh # for i in $(pkg query -g %n 'py36-*'); do pkg set -yn ${i}:py37-${i#py36-}; done # pkg upgrade For portmaster users: # sh # portmaster -o lang/python37 python36 # REINSTALL="$(pkg info -o py36-\* | awk '{printf "%s ", $2}')" # pkg delete -f py36-\* # portmaster $REINSTALL # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py37 | cut -d : -f 1 | sort -u) # portmaster $REBUILD # REBUILD2=$(pkg list | grep python-36 | xargs pkg which | awk '{print $6}' | sort -u) # portmaster $REBUILD2 20191204 AFFECTS: users of mail/nextcloud-mail AUTHOR: brnrd@FreeBSD.org Version 0.20.0 removed the default mail configuration via config.php. All users will be prompted to enter account and SMTP- and IMAP-server details for sending and reading email. 20191126: AFFECTS: consumers of net/py-urllib3 AUTHOR: kai@FreeBSD.org Since version 1.25 HTTPS connections are now verified by default which is done via "cert_reqs = 'CERT_REQUIRED'". While certificate verification can be disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to leave it on. Various consumers of net/py-urllib3 already have implemented routines that either explicitly enable or disable HTTPS certificate verification (e.g. via configuration settings, CLI arguments, etc.). Yet it may happen that there are still some consumers which don't explicitly enable/disable certificate verification for HTTPS connections which could then lead to errors (as is often the case with self-signed certificates). In case of an error one should try first to temporarily disable certificate verification of the problematic urllib3 consumer to see if this approach will remedy the issue. 20191125: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org emulators/qemu31 has been updated to 4.1.1. Previous 3.1.X branch has been repocopied to emulators/qemu31. If someone wants to stick with 3.1.X branch please use one of the following command: # pkg install emulators/qemu31 or # portmaster -o emulators/qemu31 emulators/qemu or # portupgrade -o emulators/qemu31 emulators/qemu 20191124: AFFECTS: users of irc/eggdrop AUTHOR: dbaio@FreeBSD.org The irc/eggdrop port has been updated to 1.8.4 and its config is not backward compatible with 1.6.21. A new port was created to keep 1.6.21 version available at irc/eggdrop16 and it will be available for 3 months until users have time to upgrade their configuration. More information at: https://raw.githubusercontent.com/eggheads/eggdrop/v1.8.4/NEWS If you would like to keep using 1.6.21, please run the following command to update pkg database: pkg set -n eggdrop:eggdrop16 pkg set -o irc/eggdrop:irc/eggdrop16 20191108: AFFECTS: users of databases/redis[-devel] AUTHOR: osa@FreeBSD.org The databases/redis port has been updated to the recent stable release. Users wanting to stay on v4.x can replace databases/redis with databases/redis4 with one of the following commands: # pkg install databases/redis4 or # portmaster -o databases/redis4 databases/redis or # portupgrade -o databases/redis4 databases/redis 20191103: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v13.0.0, the latest upstream release. A new port, www/node12, has been created for the v12.x LTS branch. Users wanting to stay on v12.x can replace www/node with www/node12 with one of the following commands: # pkg install www/node12 or # portmaster -o www/node12 www/node or # portupgrade -o www/node12 www/node 20191029: AFFECTS: users of emulators/open-vm-tools[-nox11] AUTHOR: jpaetzel@FreeBSD.org open-vm-tools 11.0.1 has removed the vmxnet driver. This driver has been in tree for quite some time and hopefully everyone is using the in tree version, however if you had removed device vmx from your kernel, or are running an unsupported version of FreeBSD which didn't have the driver included in the base system, updating your open-vm-tools version will leave you without networking. 20191026: AFFECTS: users of www/qt5-webengine AUTHOR: kai@FreeBSD.org Users that upgrade www/qt5-webengine without using pkg/poudriere might experience failures due to conflicts with the installed version of 5.12.2. In that case, pkg delete -f the qt5-webengine package before building the updated version. 20191025: AFFECTS: users of x11/nvidia-driver (and slave ports) AUTHOR: danfe@FreeBSD.org x11/nvidia-driver* ports no longer install Linux programs and libraries, which had been moved to their own ports (x11/linux-nvidia-libs*). When updating the driver package next time, remember to install them manually if you need to run Linux OpenGL programs. 20191016: AFFECTS: users of KDE Plasma Desktop (x11/plasma5*) AUTHOR: kde@FreeBSD.org With Plasma 5.17 the startup script has been renamed. People who use the .xinitrc method to start Plasma have to call the new binary. Previously: exec ck-launch-session startkde Change to: exec ck-launch-session startplasma-x11 20191014: AFFECTS: users of mail/rspamd, mail/rspamd-devel AUTHOR: vsevolod@FreeBSD.org Sample configuration files has been removed as default configuration files are NOT intended for modification by users and SHOULD be overwritten on port upgrade. Make sure the default configuration files are unmodified and migrate all configuration changes to the proper places, before you continue. 20191002: AFFECTS: users of textproc/groff AUTHOR: bapt@FreeBSD.org with groff 1.2.4_3, groff does not depend anymore on ghostscript and netpbm. In order to be able to properly use the html backend the user can install ghostscript and netpbm from ports without the need of reinstalling the package. Also note that the X11 option has been removed. 20190930: AFFECTS: users of net-mgmt/netbox AUTHOR: kai@FreeBSD.org Since the 2.6 release a running Redis server instance is required for caching objects to run. Also the following settings like below need to be added (or modified) in the existing configuration.py: REDIS = { 'HOST': 'localhost', 'PORT': 6397, 'PASSWORD': '' 'DATABASE': 0, 'CACHE_DATABASE': 1, 'DEFAULT_TIMEOUT': 300, 'SSL': False, } Note that if you were using these settings in a prior release with webhooks, the DATABASE setting remains the same but an additional CACHE_DATABASE settings has been added with a default value of 1 to support the caching backend. The DATABASE setting will be renamed in a future release of NetBox to better relay the meaning of the setting. It is highly recommended to keep the webhook and cache databases separate. Using the same database number for both may result in webhook processing data being lost during cache flushing events. Please also check the pkg-message and the changelogs for further info. 20190927: AFFECTS: users of emulators/qemu-devel AUTHOR: bofh@FreeBSD.org qemu-devel has been updated to 4.1.0 and 4.0.0 has been merged into a new port emulators/qemu40. If you want to stick with 4.0.X branch, simply use: # portmaster -o emulators/qemu-devel emulators/qemu40 20190927: AFFECTS: users of XFCE desktop (x11-wm/xfce4) AUTHOR: madpilot@FreeBSD.org Due to changes in the XFCE 4.14 metaport, systems could end up with both xscreensaver and xfce4-screensaver installed and enabled simultaneously. This can cause conflicts and problems unlocking the screen. To avoid problems, please make sure to have only one enabled by going to the Application Autostart tab of the Session and Startup settings applet and enable only one Screensaver there. Some further information can be found in the xfce4-session pkg-message displayed on installation and upgrade. 20190920: AFFECTS: users of net-mgmt/pushgateway AUTHOR: 0mp@FreeBSD.org The persistent storage format used by pushgateway in the latest version is not backwards compatible. See the pushgateway changelogs for details. 20190911: AFFECTS: users of security/bastillion AUTHOR: netchild@FreeBSD.org The datastore of bastillion needs to be updated: java -jar $PREFIX/jetty_bastillion/upgrade/bastillion-upgrade-3.08.00.jar \ $PREFIX/jetty_bastillion/bastillion/WEB-INF/classes/BastillionConfig.properties 20190909: AFFECTS: users of lang/ruby25 AUTHOR: mfechner@FreeBSD.org The default ruby version has been updated from 2.5 to 2.6. If you compile your own ports you may keep 2.5 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.5 as default version # DEFAULT_VERSIONS+=ruby=2.5 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkgng, simply upgrade: # pkg upgrade If you do not use pkg, please check entry 20190420. The description there should also work for this version. 20190906: AFFECTS: users of devel/py-fabric AUTHOR: dbaio@FreeBSD.org Fabric (devel/py-fabric) was upgraded to 2.5.0, Fabric (2+) represents a near-total reimplementation and reorganization of the software. Fabric 2 is not at 100% feature parity with 1.x! Some features have been explicitly dropped, but others simply have not been ported over yet, either due to time constraints or because said features need to be re-examined in a modern context. More information at: https://www.fabfile.org/upgrading.html#upgrading https://www.fabfile.org/upgrading.html#upgrade-specifics If you would like to keep using 1.x, please run the following command to update pkg database: pkg set -n py27-fabric:py27-fabric1 pkg set -o devel/py-fabric:devel/py-fabric1 20190830: AFFECTS: users of www/gitlab-ce AUTHOR: mfechner@FreeBSD.org Make sure you upgrade your PostgreSQL to version 11 as described in 20190829, before you upgrade your gitlab-ce version. Gitlab-ce 12.1 needs at least PostgreSQL version 9.6. After this you can follow the usual upgrade guide: https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/12.0-12.1-freebsd.md 20190829: AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run AUTHOR: tz@FreeBSD.org The default version of PostgreSQL has been switched from 9.5 to 11. 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 9.5.19, your files are named according to this. # service postgresql stop # pkg create postgresql95-server postgresql95-contrib # mkdir /tmp/pg-upgrade # tar xf postgresql95-server-9.5.19.txz -C /tmp/pg-upgrade # tar xf postgresql95-contrib-9.5.19.txz -C /tmp/pg-upgrade # pkg delete -f databases/postgresql95-server databases/postgresql95-contrib databases/postgresql95-client Now update PostgreSQL: pkg user: # pkg install databases/postgresql11-server databases/postgresql11-contrib # pkg upgrade Portmaster users: # portmaster databases/postgresql11-server databases/postgresql11-contrib # portmaster -a Portupgrade users: # portinstall databases/postgresql11-server databases/postgresql11-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/data11 -U pgsql" # chown -R postgres /usr/local/pgsql/data/ # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data/ -B /usr/local/bin/ -D /var/db/postgres/data11/ -U pgsql " Now the migration is finished. You can start PostgreSQL again with: # service postgresql start ATTENTION: 1) The default user changed from "pgsql" to "postgres". The migration steps above preserve the "pgsql" database user while the database daemon is now executed as the "postgres" FreeBSD user. 2) The default data dir changed from "/usr/local/pgsql/data/" to "/var/db/postgres/data11/" 3) If you use non-default initdb options, you have to adjust the initdb-command accordingly 20190816: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org Riak support has been removed by upstream. For update instructions from 19.05, please refer to: https://docs.ejabberd.im/admin/upgrade/from_19.05_to_19.08/ 20190812: AFFECTS: users of lang/perl5* AUTHOR: mat@FreeBSD.org The default Perl version has been switched to Perl 5.30. If you are using binary packages to upgrade your system, you do not have anything to do, pkg upgrade will do the right thing. For the other people, follow the instructions in entry 20161103, it should still be the same. 20190801: AFFECTS: users of www/ot-recorder AUTHOR: dvl@FreeBSD.org The data directory has moved from /var/spool/owntracks to /var/db/owntracks Be sure to stop otrecorder, move the directory, and start otrecorder. service ot-recorder stop cd /var/spool mv owntracks /var/db service ot-recorder start 20190728: AFFECTS: users of net-im/py-matrix-synapse AUTHOR: kai@FreeBSD.org The support for Python 2.7 has been dropped with the 1.1.0 release of net/py-matrix-synapse. Users that still use the Python 2.7 version of net-im/py-matrix-synapse should switch to a newer Python version, e.g. 3.6, which is the default Python version since April 2019. 20190717: AFFECTS: users of net-p2p/zetacoin and net-p2p/zetacoin-nox11 AUTHOR: daniel@morante.net Zetacoin will default to using modern versions of BDB (5.x or 6.x) when the WALLET option is selected. See pkg-help for explanation. The zetacoin-nox11 slave port was renamed to zetacoin-daemon to align with the net-p2p/bitcoin format. The zetacoin-cli and zetacoin-tx utilities have been re-packaged into a separate port. If you require these programs, or use the zetacoin-cli program to access the daemon or the GUI, install net-p2p/zetacoin-utils to reinstall them. 20190717: AFFECTS: users of sysutils/py-borgmatic AUTHOR: egypcio@FreeBSD.org The default location for borgmatic's configurations changed. We moved it from '/etc/borgmatic' to '/usr/local/etc/borgmatic' in order to follow recommended standards used on FreeBSD. 20190710: AFFECTS: users with DEFAULT_VERSIONS+=linux=c6 or c6_64 in /etc/make.conf AUTHOR: tijl@FreeBSD.org On amd64 adding DEFAULT_VERSIONS+=linux=c6 to /etc/make.conf made Linux infrastructure ports (linux_base-c6 and linux-c6*) install i386 CentOS 6 packages. Using c6_64 instead of c6 made them install mixed amd64/i386 CentOS 6 packages and allowed Linux application ports to install amd64 binaries when available. The i386-only configuration was only useful for users of x11/nvidia-driver* which didn't provide Linux amd64 emulation until recently. With x11/nvidia-driver* now supporting Linux amd64 there's no longer a need for i386-only Linux on amd64 so DEFAULT_VERSIONS+=linux=c6 has been changed to make Linux infrastructure ports install mixed amd64/i386 CentOS 6 packages, like c6_64 before, and support for c6_64 has been removed. Users with DEFAULT_VERSIONS+=linux=c6 should reinstall linux_base-c6 and all packages that depend on it. A list of dependent packages can be obtained with the following command: pkg info -r linux_base-c6 Users with DEFAULT_VERSIONS+=linux=c6_64 only need to replace c6_64 with c6 in /etc/make.conf. Users of x11/nvidia-driver* should upgrade to FreeBSD 11.3 or 12.0 if they want to run Linux amd64 OpenGL programs. If you are running an older version you may want to postpone installing or updating Linux application ports until you find the time to upgrade because application ports may install amd64 binaries now. Infrastructure ports are safe to reinstall, and so is x11/nvidia-driver*. On i386 nothing has changed. 20190707: AFFECTS: users of www/gitlab-ce AUTHOR: mfechner@FreeBSD.org You must at first upgrade to version 11.11.5 before you can upgrade to version 12. Support for MySQL will be dropped with next version. Make sure you use at least PostgreSQL version 9.6. Follow the normal upgrade manual that can be found here: https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/11.11-12.0-freebsd.md 20190705: AFFECTS: users of net/serviio which bought a license for the non-free features AUTHOR: netchild@FreeBSD.org Version 2 of serviio needs a new license file. Updating without a new license file will disable the non-free features. 20190701: AFFECTS: users of databases/mysql56-(server|client) AUTHOR: ale@FreeBSD.org The default MySQL version has been updated from 5.6 to 5.7. If you compile your own ports you may keep 5.6 as the default version by adding the following lines to your /etc/make.conf file: # # Keep MySQL 5.6 as default version # DEFAULT_VERSIONS+=mysql=5.6 If you wish to update to the new default version, you need to first stop any running server instance. Then, you will need to follow these steps, depending on installed packages. # pkg set -o databases/mysql56-client:databases/mysql57-client # pkg set -o databases/mysql56-server:databases/mysql57-server # pkg upgrade 20190630: AFFECTS: users of net/samba410 AUTHOR: timur@FreeBSD.org If you used Samba in AD/DC mode with the previous versions of the port on UFS2 backed storage you have to add usage of vfs_freebsd VFS module for at least SYSVOL share and configure it to use 'legacy' mode(see manpage). The reason behind this is that previous versions Samba port used a hack to workaround broken mapping of Linux security and trusted extended attributes into FreeBSD namespace. In particular, essential security.NTACL attribute was replaced with the user.NTACL and placed in a insecure USER namespace. This port dropped this hack in favor of vfs_freebsd module, which should provide more controlled way of such a mapping. To maintain the compatibility with the previous installations on UFS2 storage (as ZFS uses it's own way of mapping SYSVOL, thanks to the iXsystems patches) the vfs_freebsd module provides 'legacy' mode that implements old functionality. For the fresh installations it is recommended to use 'secure' mode of operations for this module and use it as a global vfs objects. Caution: The given module is still considered EXPERIMENTAL. 20190630: AFFECTS: users of net/samba410, net/samba4[6-8] and devel/talloc?, devel/tevent?, databases/tdb?, databases/ldb* AUTHOR: timur@FreeBSD.org The port of the new version of Samba 4.10 is introduced. Due necessarily to keep backwards compatibility for the legacy samba4[6-8] ports the upgrade procedure is a bit convoluted. You are safe to perform fresh new install of samba410 port. In case you are upgrading from the previous versions of Samba, please use the following procedure: 0. Take backups of all the relevant files, in particular PREFIX/etc/smb4.conf and /var/db/samba4/ subdirectory. Keep in mind that files there (may) have extended attributes, so use appropriate tools to preserve them. 1a. If you haven't updated Samba between 20190619 and 20190630 then next step should be as simple as: portmaster -o net/samba410 net/samba48 1b. If you have been affected by the archiving legacy versions of Samba-related libraries for legacy versions of Samba, which happened in the given time frame, then you need to reverse operation from the 20190619 entry: for users of portmaster: portmaster -o devel/talloc devel/talloc1 portmaster -o devel/tevent devel/tevent1 portmaster -o databases/tdb databases/tdb1 portmaster -o net/samba410 net/samba48 for users of portupgrade: portupgrade -o devel/talloc devel/talloc1 portupgrade -o devel/tevent devel/tevent1 portupgrade -o databases/tdb databases/tdb1 portupgrade -o net/samba410 net/samba48 20190619: AFFECTS: users of samba4[6-8] and devel/talloc, devel/tevent, databases/tdb, databases/ldb* AUTHOR: timur@FreeBSD.org To introduce samba410(we deliberately skip samba49 due the complexity of handling) and to drop dependency on deprecated Python 2.7, Samba supplementary libraries talloc, tevent and tdb were split into current Python 3 compatible versions and legacy ones, with the suffix "1". Old versions of Samba were changed to depend on the legacy supplementary libraries, so if you need to install samba46, samba47 or samba48 over previous Samba installations you need to downgrade supplementary libs with the following commands: for users of portmaster: portmaster -o devel/talloc1 devel/talloc portmaster -o devel/tevent1 devel/tevent portmaster -o databases/tdb1 databases/tdb portmaster -r talloc1 for users of portupgrade: portupgrade -o devel/talloc1 devel/talloc portupgrade -o devel/tevent1 devel/tevent portupgrade -o databases/tdb1 databases/tdb portupgrade -fr devel/talloc1 20190613: AFFECTS: users of www/qt5-webengine AUTHOR: kai@FreeBSD.org Users that upgrade www/qt5-webengine without using pkg/poudriere might experience failures due to conflicts with the installed version of 5.12.2. In that case, pkg delete -f the qt5-webengine package before building the updated version. 20190611: AFFECTS: users of net/routinator AUTHOR: rodrigo@FreeBSD.org Release 0.4.0 fundamentally changes the command line options for running the server and introduces a new way to initialize the local RPKI repository used by Routinator. If you have been using previous releases, you will likely have to adjust your tooling. We apologize for this, but we also feel that the new commands are more intuitive and logical. 20190604: AFFECTS: users of net/samba47 AUTHOR: antoine@FreeBSD.org The default version of samba has been switched from 4.7 to 4.8. Upgrade instructions: For package users having samba47 installed indirectly (as a dependency): # pkg upgrade For package users having samba47 installed directly (leaf port): # pkg upgrade # pkg install samba48 For ports users: If you want to keep samba47, add DEFAULT_VERSIONS+= samba=4.7 to make.conf If you want to upgrade to samba48, remove samba47: # pkg delete -f samba47 Portmaster users: # portmaster net/samba48 # portmaster -a Portupgrade users: # portinstall net/samba48 # portupgrade -a 20180601: AFFECTS: www/tt-rss AUTHOR: dereks@lifeofadishwasher.com tt-rss now uses php intl for extension; a web server reload will be required if intl extension isn't already loaded. 20190522: AFFECTS: users of sysutils/graylog AUTHOR: dch@FreeBSD.org The port has been updated to the latest stable version 3.0.2, which includes more plugins by default, but also requires manual changes to graylog's configuration files, possibly port and URL changes, such as X-Graylog-Server-URL settings, and elasticsearch must be >= 5. The location of configuration files has been amended to align with the official distribution files and locations. After upgrading, manually review and merge changes from your /usr/local/etc/graylog/server/server.conf into /usr/local/etc/graylog/graylog.conf Consult https://www.graylog.org/post/announcing-graylog-v3-0-ga for further details. 20190506: AFFECTS: users of www/gitea AUTHOR: stb@lassitu.de Gitea requires the addition of another secret to the config file in order to start up. Either manually add JWT_SECRET to the ${PREFIX}/etc/gitea/conf/app.ini config file (see app.ini.sample), or allow Gitea to make the change for you by making the config file writable to the git user. 20190424: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v12.0.0, the latest upstream release. This is a major release, including many significant changes. Users are encouraged to read the release announcements before upgrading: https://nodejs.org/en/blog/release/v12.0.0/ 20190423: AFFECTS: users of www/gitlab-ce AUTHOR: mfechner@FreeBSD.org The directory where all repositories and ssh permissions are stored was changed from /usr/home/git back to /usr/local/git, to match again the recommended standards on FreeBSD. This will cause now some other git management packages to collide with gitlab. Make sure you migrate all you git repositories to gitlab first, before you continue. Make sure /usr/local/git/repositories and /usr/local/git/.ssh are not existing! Otherwise the next commands can break your installation for managing git repositories within gitlab and with your other gitlab management software! You must move the old files to the new location with: # service gitlab stop # mv /usr/home/git /usr/local/ # pkg upg Make sure you update your config files, diff shows you what you maybe must change: # cd /usr/local/www/gitlab-ce # git diff config/gitlab.yml.sample config/gitlab.yml # cd /usr/local/share/gitlab-shell/ # git diff config.yml.sample config.yml # cd /usr/local/share/gitaly # git diff config.toml.sample config.toml # Change home directory of user git back to /usr/local/git # vipw The line should now looks like: git:*:211:211::0:0:gitosis user:/usr/local/git:/bin/sh If you do an upgrade of gitlab follow the upgrade guide. If not, just start gitlab again with: # service gitlab start 20190422: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.9 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl 20190421: AFFECTS: users of databases/cego AUTHOR: pi@FreeBSD.org To upgrade from cego 2.39.16 to 2.44.1, you need to export to xml before the upgrade and import from xml after the upgrade, because the internal storage has changed for some types. Use these steps: - export your database while it runs, see http://www.lemke-it.com/litexec?request=pubcegodoc&user=&lang=en§ion=cgdoc_database_running.html#tsimpexp_mode for details. - stop the database service cego stop - upgrade the port/package - re-create the database cego --mode=create --tableset= --dbxml=.xml - import the database cego --mode=xmlimport --tableset= \ --dbxml=.xml --impfile=export.xml --doLogging - modify /etc/rc.conf by adding cego__cpdump="YES" cego__cleanup="YES" - start the database service cego start 20190420: AFFECTS: users of lang/ruby24 AUTHOR: mfechner@FreeBSD.org The default ruby version has been updated from 2.4 to 2.5. If you compile your own ports you may keep 2.4 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.4 as default version # DEFAULT_VERSIONS+=ruby=2.4 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkgng, simply upgrade: # pkg upgrade If you use portmaster, install new ruby, then rebuild all ports that depend on ruby: # portmaster -o lang/ruby25 lang/ruby24 # portmaster -R -r ruby-2.5 If you use portupgrade, install new ruby, then rebuild all ports that depend on ruby: # pkg delete -f ruby portupgrade # make -C /usr/ports/ports-mgmt/portupgrade install clean # pkg set -o lang/ruby24:lang/ruby25 # portupgrade -x ruby-2.5.\* -fr lang/ruby25 20190419: AFFECTS: users of emulators/qemu AUTHOR: bofh@FreeBSD.org qemu 2.X version has been moved to qemu2. If you would like to use 2.X you should use qemu2. Otherwise you can use the new stable upstream branch of 3.0.X. Portmaster users will need to run this command: portmaster -o emulators/qemu2 emulators/qemu 20190410: AFFECTS: users of python AUTHOR: antoine@FreeBSD.org Default version of python was switched to 3.6. For ports users wanting to keep version 2.7 as default, add DEFAULT_VERSIONS+= python=2.7 to make.conf 20190328: AFFECTS: www/firefox-i18n, www/firefox-esr-i18n, mail/thunderbird-i18n, www/seamonkey-i18n AUTHOR: gecko@FreeBSD.org Separate packages for localization packs are no longer supported. Firefox 65+ has in-browser menu while Firefox ESR60, Thunderbird 60 or SeaMonkey 2.49 should download preferred .xpi manually. Refer to the following article (including previous revisions) how to do this. https://support.mozilla.org/kb/use-firefox-another-language 20190328: AFFECTS: users of www/qt5-webengine AUTHOR: kde@FreeBSD.org Users that upgrade www/qt5-webengine without using pkg/poudriere might experience failures due to conflicts with the installed version of 5.9.5. In that case, pkg delete -f the qt5-webengine package before building the updated version. 20190314: AFFECTS: users of mail/rspamd, mail/rspamd-devel AUTHOR: vsevolod@FreeBSD.org User and group that rspamd run as are changed from nobody:nobody to rspamd:rspamd. Unless it is clean install you need to execute following command. # chown -R rspamd:rspamd /var/db/rspamd /var/log/rspamd /var/run/rspamd 20190311: AFFECTS: users of x11/xorg, x11-fonts/mkfontscale, x11-fonts/mkfontdir AUTHOR: zeising@FreeBSD.org The x11-fonts/mkfontdir port has been removed and the functionality has been merged into x11-fonts/mkfontscale. This might cause issues with upgrading. If you get conflicts between mkfontscale and mkfontdir please remove mkfontdir before upgrading. To do this, simply run the following: pkg delete -f mkfontdir 20190311: AFFECTS: users of www/igal2 AUTHOR: rodrigo@freebsd.org www/igal2 2.2-1 is now built with graphics/ImageMagick6-nox11 and don't install the ImageMagick X11 dependencies anymore. A build option allows you to restore the previous behaviour. 20190303: AFFECTS: users of x11-fonts/noto* AUTHOR: sunpoet@FreeBSD.org Google Noto Fonts family has been converted to several ports. x11-fonts/noto is a meta port which includes 1 old port and 5 new ports as follows: - x11-fonts/noto-basic (was noto-lite): basic fonts set with emoji - x11-fonts/noto-extra: extra fonts set - x11-fonts/noto-jp: Japanese fonts set - x11-fonts/noto-kr: Korean fonts set - x11-fonts/noto-sc: Simplified Chinese fonts set - x11-fonts/noto-tc: Traditional Chinese fonts set 20190302: AFFECTS: users of sysutils/paladin AUTHOR: Ryan Westlund The way paladin parses its config file has changed, please check the provided sample config. 20190227: AFFECTS: users of security/softether, security/softether-devel AUTHOR: meta@FreeBSD.org These ports' bridge, client, server daemon unintendedly had spit out chain_certs (certificate chain) directory on libexec directory until r494024. If your ${PREFIX}/libexec/softether/chain_certs directory is empty, you can remove the directory safely. If the directory is not empty, move it to ${SE_DBDIR} when upgrading softether. Following commands should help: service softether_(bridge|client|server) stop (portmaster, portupgrade or pkg upgrade) mv ${PREFIX}/libexec/softether/chain_certs ${SE_DBDIR}/ service softether_(bridge|client|server) start With the default Makefile settings, ${SE_DBDIR} is set to /var/db/softether. 20190224: AFFECTS: users of security/gnutls AUTHOR: tijl@FreeBSD.org GnuTLS now looks for its configuration files in PREFIX/etc (/usr/local/etc) instead of /etc. If the following files exist they have to be moved. On a default installation these files do not exist. /etc/gnutls/default-priorities /etc/gnutls/pkcs11.conf /etc/tpasswd /etc/tpasswd.conf 20190215: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org If you've mod_mam enabled with compress_xml set to true, then you're affected by bug where the XML namespace, and tag elements get interchanged in the MAM cache which results in invalid XML, and causing XMPP clients to disconnect. For more details, please refer to: https://github.com/processone/ejabberd/issues/2744 This upgrade contains the patch that fixes the problem going forward. For fixing already affected users, you'll need to wipe off the MAM cache for the affected users: sudo -u ejabberd -H ejabberdctl remove_mam_for_user 20190207: AFFECTS: users of net-mgmt/mk-livestatus AUTHOR: egypcio@FreeBSD.org The default Nagios version supported by net-mgmt/mk-livestatus changed from Nagios 3 to Nagios 4 - the respective Nagios package was added to net-mgmt/mk-livestatus' runtime dependencies. If you still need support for Nagios 3 you just need to change the options for net-mgmt/mk-livestatus and compile the port yourself. 20190202: AFFECTS: users of archivers/urbackup-server AUTHOR: freebsd@coombscloud.com Some of the port's sources previously included absolute references to /etc/urbackup. The upgrade now changes these references to ${PREFIX}/etc/urbackup. If you have placed any configuration files within /etc/urbackup, these should be relocated to ${PREFIX}/etc/urbackup. 20190130: AFFECTS: users of sysutils/password-store AUTHOR: rene@FreeBSD.org password-store now stores plugins in ${PREFIX}/libexec instead of ${PREFIX}/lib. Ensure to move your own extensions there too and update your scripts to avoid breakage. 20190124: AFFECTS: users of sysutils/rubygem-fluentd, sysutils/fluent-bit AUTHOR: girgen@FreeBSD.org The fluentd port has been upgraded from the 0.12 line to 1.3.3. The upgrade is mostly non-disruptive since there is a backward compatibility with 0.12 plugins and configuration files, but care should be taken about the order of server upgrades since fluentd 1.x is unable to send it's data to version 0.12 instances. You should carefully read https://docs.fluentd.org/v1.0/articles/update-from-v0.12 before performing any upgrade activities. 20190120: AFFECTS: users of mail/fetchmail AUTHOR: mandree@FreeBSD.org The fetchmail port no longer offers the X11 option and no longer depends on Python. The corresponding fetchmailconf Python program has now been split out into a separate port or package, so that fetchmail itself will no longer require Python. Users who wish to use fetchmailconf should install the new fetchmailconf port or package. 20190119: AFFECTS: users of german/webalizer2, japanese/webalizer, polish/webalizer2, portuguese/webalizer-pt_BR, portuguese/webalizer-pt_PT, ukrainian/webalizer, www/geolizer, www/webalizer AUTHOR: dinoex@FreeBSD.org The option GEOIP has been changed to used the new database. Either copy GeoLite2-Country.mmdb in the working directory, or set the GeoIPDatabase option to the location of the file. 20190114: AFFECTS: users of graphics/qgis AUTHOR: rhurlin@gwdg.de GIS 3.4 LTR, the first long-term release (LTR) of QGIS 3, has landed in the FreeBSD ports tree. It will also replace the previous 2.18 LTR in the QGIS package repositories in February 2019 [1]. Beside, the latest Qt4 version 4.8.7 has been EOL since December 2015 and its expiration date on FreeBSD is set to March, 15th 2019. Because QGIS 2 is based on Qt4 and Python2, it was decided to not create a legacy port for QGIS 2, after graphics/qgis changed to QGIS 3. For users moving over from the 2.18 LTR there is a huge list of new features and impactful changes in this new 3.4 LTR version. Most notably 3.x plugins are incompatible with 2.x plugins, so please review your plugin usage carefully. Before moving over, if you have not already done so, take a look at the changelogs from versions 3.0, 3.2, and 3.4 [2][3][4] to understand the full scope of changes in the 3.x release. [1] https://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule [2] http://changelog.qgis.org/en/qgis/version/3.0.0/ [3] http://changelog.qgis.org/en/qgis/version/3.2.0/ [4] http://changelog.qgis.org/en/qgis/version/3.4-LTR/ 20190114: AFFECTS: x11-wm/sway AUTHOR: jbeich@FreeBSD.org swayidle and swaylock split out into x11/swayidle and x11/swaylock. Check your sway config and install those if required. 20190113: AFFECTS: users of net/GeoIP AUTHOR: adamw@FreeBSD.org Maxmind no longer provides geolocation data in the legacy format used by net/GeoIP. All GEOIP-related OPTIONS have been removed, and all GeoIP-dependent ports will be removed soon. Where possible, you must switch to net/libmaxminddb, which uses the newer (and fully supported) GeoIP 2 format. Unfortunately, this is not a drop-in replacement. To fetch the GeoIP 2 geolocation databases, whether the free or paid versions, you must use net/geoipupdate (pkg install geoipupdate). The legacy database is no longer available, and we cannot distribute it by the Maxmind license, so the legacy GeoIP format is essentially dead. 20190108: AFFECTS: users of databases/mysql-connector-java AUTHOR: matthew@FreeBSD.org The databases/mysql-connector-java port has been updated to 8.0.13, which requires a minimum of Java 1.8, so dropping support for Java 1.6 and 1.7. Users of those versions of Java should substitute the databases/mysql-connector-java51 port which remains at version 5.1.47 20190103: AFFECTS: users of multimedia/vlc* AUTHOR: riggs@FreeBSD.org The multimedia/vlc port has been upgraded to 3.0.5, the latest upstream release. Subsequently, multimedia/vlc-qt4 and multimedia/vlc3 have been retired and removed from the ports tree. Users who previously used multimedia/vlc3 might want to switch to multimedia/vlc with the following commands: # pkg install multimedia/vlc or # portmaster -o multimedia/vlc multimedia/vlc3 or # portupgrade -o multimedia/vlc multimedia/vlc3 20190102: AFFECTS: users of net/serviio AUTHOR: netchild@FreeBSD.org If you have customized your etc/serviio/profile.xml you need to review and merge changes from the profile.xml.sample file, else you may not be able to watch mkv files. 20181228: AFFECTS: users of devel/trio AUTHOR: rodrigo@freebsd.org Since trio 1.16-1, the shared lib previously misnamed libtrio.so.2.0.0 is now named libtrio.so.2 and the symlink libtrio.so is created. 20181222: AFFECTS: users of net/ntopng AUTHOR: madpilot@FreeBSD.org Since ntopng 3.7, for security reasons, the default setting for the data directory has been changed to "/var/db/ntopng", and the default user has been changed to "ntopng". This new directory is created automatically by the port/package with correct permissions. In order to maintain backward compatibility, if you are already using "/var/tmp/ntopng" as data directory, ntopng keeps using that folder, owned by "nobody". This said, using the old defaults is not recommended and a manual action is required in order to migrate to the new settings, unless you are already using a custom directory: # service ntopng stop # mv /var/tmp/ntopng/* /var/db/ntopng/ # chown -R ntopng:ntopng /var/db/ntopng # service ntopng start Please check the upstream FAQ for reference: https://www.ntop.org/support/faq/migrate-the-data-directory-in-ntopng/ 20181218: AFFECTS: users of misc/openhab2 AUTHOR: netchild@FreeBSD.org If you upgrade from a previous version, make a backup of /var/db/openhab2 and run %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd Config specific info (changes from 2.3.0 to 2.4.0): Astro Binding: The 'kilometer' and 'miles' channels have been replaced by a new 'distance' channel Jeelink Binding: The 'currentWatt' and 'maxWatt' channels have been replaced with 'currentPower' and 'maxPower' channels WeatherUnderground Binding: A bridge has been added on top of the current things, you need to add a bridge containing your api-key. ZWave Binding: Major changes have been merged to support features such as security. All things must be deleted and re-added. Refer to https://community.openhab.org/t/zwave-binding-updates/51080 for further information. Synop Binding is now using UoM. 'wind-speed-ms' and 'wind-speed-knots' channels have been replaced by a single 'wind-speed' channel. Amazonechocontrol Binding: The account thing does not have settings anymore. You have to login at amazon once again through the proxy server http(s):///amazonechocontrol Milight Binding: The various available bulb types do not appear in the Paper UI Inbox anymore. The correct bulb need to be added manually. The bulb "zone" is now a configuration. Bulb Things need to be recreated to apply this change. Hue emulation: The item to hue ID mapping is no longer stored in files, but in the openHAB storage service. You need to rediscover "devices" in all services that use the hue emulation (Amazon Echo, Google Home, etc). 20181215: AFFECTS: users of sysutils/graylog AUTHOR: dch@FreeBSD.org The dependent ports for ElasticSearch and MongoDB have both changed, and upstream changes to the configuration file may require minor changes to work correctly. Refer to the new sample files installed alongside the port for reference: server.conf log4j.xml graylog_logging.xml 20181213: AFFECTS: users of lang/perl5* AUTHOR: mat@FreeBSD.org The default Perl version has been switched to Perl 5.28. If you are using binary packages to upgrade your system, you do not have anything to do, pkg upgrade will do the right thing. For the other people, follow the instructions in entry 20161103, it should still be the same. 20181212: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org There are some new features added in ejabberd 18.12, esp. related to bookmarks, and XML compression in message archive storage. Please refer to: https://blog.process-one.net/ejabberd-18-12/ 20181211: AFFECTS: users of news/inn when upgrading to FreeBSD 12 AUTHOR: naddy@FreeBSD.org When upgrading from FreeBSD 11 to 12, a change in the size of the ino_t type causes a binary incompatibility in the overview database if the default tradindexed format is used. After upgrading the inn package, remove the overview/group.index file and regenerate the history and overview database with makehistory(8) before starting innd. # echo '. /usr/local/news/lib/innshellvars && \ rm -f $OVERVIEWDIR/group.index && \ $NEWSBIN/makehistory -O -s `wc -l <$HISTORY`' | \ su -fm news -c '/bin/sh -s' 20181209: AFFECTS: users of DRM ports other than graphics/drm-kmod AUTHOR: jmd@FreeBSD.org In order to facilitate future porting efforts and help in supporting multiple FreeBSD versions, the DRM ports other than drm-kmod (graphics/drm-stable-kmod, graphics/drm-next-kmod, graphics/drm-devel-kmod) have been renamed to include the FreeBSD version they are designed for. drm-stable-kmod is drm-fbsd11.2-kmod drm-next-kmod is drm-fbsd12.0-kmod drm-devel-kmod is drm-current-kmod 20181209 AFFECTS: users of devel/geany and devel/geany-plugins AUTHOR: madpilot@FreeBSD.org Geany and its plugins port have been moved to gtk3 and a new gtk2 flavor has been added. The gtk2 flavor has a -gtk2 suffix added to the package name. If you want to stay with the gtk2 version you need to use "pkg install" to install the new gtk2 flavor, pkg will automatically deinstall the gtk3 flavors. If using port, to maintain the gtk2 version, you will need to deinstall geany and its plugins and reinstall specifying the gtk2 flavor. Note that the following plugins are not available if using the new gtk3 flavor: * geany-plugin-debugger * geany-plugin-devhelp * geany-plugin-geanypy * geany-plugin-multiterm * geany-plugin-scope 20181208: AFFECTS: users of misc/openhab2 AUTHOR: netchild@FreeBSD.org If you upgrade from a previous version, make a backup of /var/db/openhab2 and run %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd Config specific info (changes from 2.2.0 to 2.3.0): Nest Binding: The 'camera' Thing Type now has channel groups. Add 'camera#' before the channel ID in the channel UID of existing camera channels. The 'time_to_target_mins' channel of the 'thermostat' Thing Type is renamed to 'time_to_target' Oceanic Binding: The 'softener' Thing Type no longer exists and is replaced by the 'serial' and 'ethernet' Thing Types Yamaha Receiver Binding: The configuration parameter names now use lower camel case convention. Change 'HOST' to 'host', 'PORT' to 'port' etc 20181124: AFFECTS: users of sysutils/munin-master, sysutils/munin-node, www/owncloud, mail/mailman, net/ntpa AUTHOR: woodsb02@FreeBSD.org The newsyslog.conf(5) filename installed by the port has been changed: OLD: ${PREFIX}/etc/newsyslog.conf.d/${PORTNAME} NEW: ${PREFIX}/etc/newsyslog.conf.d/${PORTNAME}.conf Any file found at the old location will be automatically moved to the new location. This will ensure log rotation will continue to work after change r340318 to FreeBSD base, where the default newsyslog configuration now only includes filenames that end with '.conf' and do not begin with '.'. If you use provisioning/configuration management tools to create or edit this file, you will need to change their configuration to use the new filename. 20181111 AFFECTS: users of graphics/mesa-libs AUTHOR: jbeich@FreeBSD.org Wayland support has been enabled in ports where it doesn't exclude X11 support in order to make the binary packages usable with Wayland compositors. If you get strange build failures re-run "make config" to pick up the new defaults. If the extra dependencies are not desired add the following to make.conf: OPTIONS_UNSET += WAYLAND 20181109 AFFECTS: users of security/ossec-hids-server AUTHOR: dominik.lisiak@bemsoft.pl The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable". If using database output, you need to recreate database using new schema provided in /usr/local/share/doc/ossec-hids. 20181109 AFFECTS: users of security/ossec-hids-local AUTHOR: dominik.lisiak@bemsoft.pl The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable". If using database output, you need to recreate database using new schema provided in /usr/local/share/doc/ossec-hids. 20181109 AFFECTS: users of security/ossec-hids-client AUTHOR: dominik.lisiak@bemsoft.pl The ossec-hids-client port has been renamed to ossec-hids-agent. Portmaster users will need to run this command: portmaster -o security/ossec-hids-agent security/ossec-hids-client If the switch doesn't happen automatically for you, just delete the ossec-hids-client package and install ossec-hids-agent. The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable". 20181104: AFFECTS: users of sysutils/ansible* AUTHOR: lifanov@FreeBSD.org Default Ansible configuration location changed to LOCALBASE/etc/ansible instead of a per-flavor directory. If you use system-wide Ansible configuration, please migrate from a flavored directory to a common one: # mv /usr/local/etc/py27-ansible /usr/local/etc/ansible 20181031: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v11.0.0, the latest upstream release. A new port, www/node10, has been created for the v10.x LTS branch. Users wanting to stay on v10.x can replace www/node with www/node8 with one of the following commands: # pkg install www/node10 or # portmaster -o www/node10 www/node or # portupgrade -o www/node10 www/node 20181022: AFFECTS: users of lang/php71 AUTHOR: joneum@FreeBSD.org The default version of PHP has been switched from 7.1 to 7.2. If you use binary packages you should make a list of php packages before running 'pkg upgrade': # pkg info php7\* > ~/installed-php-ports-list After the upgrade, check with such list if all your php extensions are still installed, and reinstall them if needed. If you use mod_php71 you need to deinstall it and install mod_php72. 20181020: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.8 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl 20181018: AFFECTS: users of security/hitch AUTHOR: zi@FreeBSD.org Hitch has been updated to run as the hitch user/group, instead of the previous default of nobody/nobody. You should review your hitch configuration to ensure that everything has been updated to reflect this change. 20181014: AFFECTS: users of sysutils/ansible AUTHOR: lifanov@FreeBSD.org Ansible has been updated to 2.7.0. Please follow the porting guide to update the rulesets: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html If you wish to stay with 2.6 version, you can switch to new sysutils/ansible2.6 port, which tracks stable 2.6 branch: # pkg set -n ansible:ansible26 20181010: AFFECTS: users of mail/courier-imap and other courier ports AUTHOR: madpilot@FreeBSD.org Courier-IMAP 5.0.0 added IMAP UTF8 support, and converted maildir folders' names to Unicode. Updating an existing system to Courier-IMAP 5.0, and later, requires a manual one-time conversion of all existing maildirs using the maildirmake command. See the maildirmake(1) manual page for more information. All other courier ports accessing maildirs also need to be updated at the same time. 20181009: AFFECTS: users of devel/pecl-xdebug* AUTHOR: pizzamig@FreeBSD.org xdebug 2.6.1 (devel/pecl-xdebug) is the new default version and it supports PHP from 7.0 to 7.2 included. If you're using PHP 5.6, the previous compatible xdebug version is still available in devel/pecl-xdebug25 If you're using PHP 7.3, the only compatible xdebug version is available in devel/pecl-xdebug-devel 20180930: AFFECTS: users of DRM components AUTHOR: jmd@FreeBSD.org A metaport, graphics/drm-kmod, was introduced for users of both the LinuxKPI- based DRM components as well as the legacy ones. It is recommended to use the metaport from now on, which will select a recommended DRM version based on the FreeBSD version. 20180924: AFFECTS: www/libresonic-standalone AUTHOR: jlh@FreeBSD.org HTTPS support has been removed from the port, as it will be removed upstream: https://github.com/Libresonic/libresonic/issues/125#issuecomment-256227104 In order to avoid strange behavior for users who are using this feature, the rc.d script will fail fast if libresonic_ssl="YES". You should remove the following variables from rc.conf(5): libresonic_ssl libresonic_ssl_keystore libresonic_ssl_password. # sed -i '' /libresonic_ssl/d /etc/rc.conf Users needing SSL are encouraged to use an HTTP reverse-proxy. Example configurations can be found here: https://github.com/Libresonic/libresonic/issues/119 20180922: AFFECTS: users of graphics/ilmbase, graphics/OpenEXR AUTHOR: mandree@FreeBSD.org The IlmBase package has been updated to 2.3.0. The OpenEXR package has been renamed to openexr and updated to 2.3.0. The PORTREVISION of all ports requiring either has been bumped to ease the rebuilds, and where there were versions in the file names, these have been removed from the *_DEPENDS lines for easier maintenance. A full ports or package upgrade should just work. If you are doing partial updates, be sure to rebuild and reinstall all packages that require either of OpenEXR or ilmbase. Normally, these can be listed by running: # pkg info -q -r OpenEXR ilmbase | sort -u | xargs pkg info -q -o 20180905: AFFECTS: users of lang/php56 AUTHOR: tz@FreeBSD.org The default version of PHP has been switched from 5.6 to 7.1. If you use binary packages you should make a list of php packages before running 'pkg upgrade': # pkg info php5\* > ~/installed-php-ports-list After the upgrade, check with such list if all your php extensions are still installed, and reinstall them if needed. If you use mod_php56 you need to deinstall it and install mod_php71. 20180901: AFFECTS: net/samba48 AUTHOR: timur@FreeBSD.org Samba ports from now on are not dependent from the databases/ldb* ports, as the link between Samba and LDB is too tight and each next major Samba release requires it's own major LDB release. Please, remove installed version of databases/ldb13 from your system with: # pkg delete -f databases/ldb13 20180901: AFFECTS: net-mgmt/librenms AUTHOR: dvl@FreeBSD.org As of version 1.42, to conform with man hier, logs and rrd files have relocated outside the WWW directory. When upgrading from < 1.42 to more recent versions, the following steps are required. You must update config.php and manually relocate the rrd and log files. Before upgrading, please stop librenms, update the configuration, and relocate the files. If you find graphs are not updating, fping >= 4.0 requires an IPv6 address. Adding an IPv6 address should fix graphing. Please add these entries to config.php: $config['installed_from_package'] = true; $config['log_dir'] = '/var/log/librenms'; $config['rrd_dir'] = '/var/db/librenms/rrd'; To relocate the files: mkdir /var/log/librenms /var/db/librenms chown www:ww: /var/log/librenms /var/db/librenms cd /usr/local/www/librenms mv rrd /var/db/librenms/ mv logs/librenms.log /var/log/librenms/ rmdir logs An application key is required. Please follow these steps to generate it: cd /usr/local/www/librenms cp -i .env.sample .env You might need to set your database details in that file. Then run: php artisan key:generate The output should look something like this: ************************************** * Application In Production! * ************************************** Do you really wish to run this command? (yes/no) [no]: > y Application key [base64:P62La9V........qw=] set successfully. 20180901: AFFECTS: users of samba46 AUTHOR: antoine@FreeBSD.org The default version of samba has been switched from 4.6 to 4.7. Upgrade instructions: For package users having samba46 installed indirectly (as a dependency): # pkg upgrade For package users having samba46 installed directly (leaf port): # pkg upgrade # pkg install samba47 For ports users: If you want to keep samba46, add DEFAULT_VERSIONS+= samba=4.6 to make.conf If you want to upgrade to samba47, remove samba46: # pkg delete -f samba46 Portmaster users: # portmaster net/samba47 # portmaster -a Portupgrade users: # portinstall net/samba47 # portupgrade -a 20180813: AFFECTS: net/geoipupdate AUTHOR: adamw@FreeBSD.org There have been some breaking changes to the GeoIP.conf in version 3.0.0. Read about the changes at https://github.com/maxmind/geoipupdate/blob/master/ChangeLog.md and either edit your GeoIP.conf as needed, or recreate it from GeoIP.conf.sample. 20180810: AFFECTS: databases/postgresql??-server AUTHOR: girgen@FreeBSD.org The PostgreSQL server packages are no longer built with support for the XML datatype per default. To retain support for the XML datatype you should build the port and check the XML option in the option dialog. The reason for this is the bad security reputation of libxml2. 20180806: AFFECTS: www/tt-rss AUTHOR: thierry@FreeBSD.org tt-rss now uses pdo_mysql/pgsql for database access; a web server reload will be required if pdo ext. isn't installed. 20180804: AFFECTS: net-mgmt/zabbix*-server AUTHOR: dbaio@FreeBSD.org The JAVAGW option was removed from the Zabbix Server and an additional slave port was created, zabbix*-java, it installs only Zabbix Java Gateway files, this way is possible to deploy a Zabbix Java Gateway without the need to install Zabbix Server components. If you are using the JAVAGW option on Zabbix Server, please, install now the new zabbix*-java port. 20180803 AFFECTS: users of net/openntpd AUTHOR: naddy@FreeBSD.org The numerical ID of the "_ntp" user had to be moved after 12.0-CURRENT (revision 336525) took over its value for a user "ntpd" that uses a different privilege model. To avoid clashes between the two users, please remove the openntpd package, delete the old UID with # pw userdel _ntp and re-install openntpd. 20180731: AFFECTS: users of audio/sndio AUTHOR: tobik@FreeBSD.org sndiod(8) will now use the default audio device /dev/dsp instead of /dev/dsp0 if no device was specified. The location of ~/.aucat_cookie has moved to ~/.sndio/cookie. If you share audio devices via sndiod(8) on the network or between local users, please migrate it manually to the new location to guarantee a smooth upgrade. 20180731: AFFECTS: users of x11/xorg and all ports with USE_XORG=*proto AUTHOR: zeising@FreeBSD.org The xorg *proto packages have all been merged into one package, x11/xorgproto. This might cause issues with upgrading. If you get conflicts between xorgproto and old *proto packages, please remove the old package and install xorgproto again. In order to remove all orphaned ports, including all *proto port, the following can be used after the ports tree has been updated: pkg version -l \? | cut -f 1 -w | grep -v compat | xargs pkg delete -fy 20180728: AFFECTS: users who upgrade from security/kc to security/kc24 AUTHOR: pi@FreeBSD.org The ondisk format changes from kc 2.3 to kc 2.4, so please read the kc24 pkg-message file before the upgrade. It describes how to create a backup, the xml dump and how to import the xml dump afterwards. 20180725: AFFECTS: users of textproc/ibus-typing-booster AUTHOR: thierry@FreeBSD.org Due to a migration from IBusConfig to GSettings, the old settings are unfortunately lost, so one has to open the setup tool and recreate ones favourite settings. 20180714: AFFECTS: users of dns/dnsdist AUTHOR: cpm@FreeBSD.org After discussing with several users, we noticed that quite a lot of them were not aware that enabling the dnsdist's console without a key, even restricted to the local host, could be a security issue and allow privilege escalation by allowing an unprivileged user to connect to the console and execute Lua code as the dnsdist user. We therefore decided to refuse any connection to the console until a key has been set, so please check that you do set a key before upgrading if you use the console. For further details read: https://blog.powerdns.com/2018/07/10/dnsdist-1-3-2-released/ 20180704: AFFECTS: users of www/gitlab AUTHOR: mfechner@FreeBSD.org The gitlab port uses the package from gitlab.org instead of github.org. For this the port was renamed from gitlab to gitlab-ce. Please follow the instructions very carefully to not lose your data! Not only the package was renamed, also the directory name changed. You can find the current instruction here: https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/10.8-11.0-freebsd.md Please note the update was only tested for an update from 10.8.5 to 11.0.2. If your version of gitlab was released before 2014-03-13 you cannot update to this version. You need to make an intermediate update to an earlier version before. 20180701: AFFECTS: users of devel/bats AUTHOR: lifanov@FreeBSD.org The devel/bats port has been renamed to devel/bats-core to match the new upstream project. 20180630: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org In version 18.06, upstream has removed support for IRC transport. 20180625: AFFECTS: users of PHP based applications like drush AUTHOR: mfechner@FreeBSD.org Flavors are being added to PHP applications. If you use PHP 5.6 you need: # pkg set -n drush:drush-php56 For more details see 20180611. 20180612: AFFECTS: users of the nox flavor of editors/emacs-devel AUTHOR: jrm@FreeBSD.org The package name for the nox flavor of editors/emacs-devel changed from emacs-devel_nox to emacs-devel-nox. To install the new package, run # pkg install emacs-devel-nox pkg should remove the old and install the new package. 20180612: AFFECTS: users of packages that depend on Emacs AUTHOR: jrm@FreeBSD.org With the release of Emacs version 26.1, the major version of editors/emacs changed from 25 to 26, so the names of packages that depend on Emacs have also changed. For example, pdf-tools-emacs25-0.80.79_1 is now called pdf-tools-emacs26-0.80.79_1. The name change means simply running `pkg upgrade` will not upgrade foo-emacs25-x to foo-emacs26-x. To list the packages to upgrade, use # pkg info \*emacs25\* then install the new version for each with # pkg install foo-emacs26 pkg should remove the old and install the new packages. 20180611: AFFECTS: users of PHP based applications AUTHOR: mat@FreeBSD.org Flavors are being added to PHP applications. When a port is flavorized, pkg needs to be told about the name change, for example, if PHP 5.6 is the one you need: # pkg set -n squirrelmail:squirrelmail-php56 Most port will have packages for all PHP versions present in the ports tree, but some may not be compatible with a specific version. To get the available flavors, pkg rquery can be used: # pkg rquery %n mail/squirrelmail squirrelmail-php56 squirrelmail-php70 squirrelmail-php71 squirrelmail-php72 20180602: AFFECTS: users of net/frr AUTHOR: olivier@FreeBSD.org Due to regression detected in FRR version 4.0, port was renamed to frr4 to prepare re-introduction of frr3 port version. To rename the installed package to match the new naming scheme, run: # pkg set -n frr:frr4 20180529: AFFECTS: users of textproc/ibus-typing-booster AUTHOR: thierry@FreeBSD.org Attention, this release merges all engines into one. Therefore, the engine names had to change. The old engine names like "German - DE (Typing Booster)", "Hindi - HI (Typing Booster)" don't exist anymore! If one has entries for them in the Gnome Control Center or in ibus-setup, one needs to remove these old entries and add the new engine name "Other (Typing Booster)". 20180518: AFFECTS: users of sysutils/ansible* AUTHOR: lifanov@FreeBSD.org Ansible ports are now flavored. Package names for Ansible changed to include python version. Poudriere and package users don't need to do anything. To rename an installed package to match the new naming scheme, for example, for ansible24, run: # pkg set -n ansible24:py27-ansible24 20180514: AFFECTS: users of www/gitlab AUTHOR: mfechner@FreeBSD.org Gitlab-pages support was removed as new version does not compile. If you require gitlab-pages do not update to version 10.7.3 till it is fixed upstream. You can find the bug report here: https://gitlab.com/gitlab-org/gitlab-pages/issues/143 20180513: AFFECTS: users of net/xrdp AUTHOR: meta@FreeBSD.org net/xrdp has been updated from 0.6.2 to 0.9.6. There are significant changes between these versions. You should consider backing up your configuration files such as xrdp.ini and sesman.ini, and then migrate configuration files by hand. Regarding km-*.ini, don't use the old files. They can be safely replaced with new ones. 20180507: AFFECTS: users of math/suitesparse who build it locally AUTHOR: yuri@FreeBSD.org The suitesparse needs to be uninstalled before math/suitesparse can be correctly built. This is true for the version 5.2.0 and prior versions. 20180505: AFFECTS: users of www/gitea AUTHOR: stb@lassitu.de The www/gitea port no longer requires shell/bash. If you want to stop using bash and deinstall the package, make sure to set the configuration in etc/gitea/conf/app.ini, section [repository], SCRIPT_TYPE to "sh". See app.ini.sample for an example. 20180501: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v10.0.0, the latest upstream release. This is a major release, including many significant changes. Users are encouraged to read the release announcements before upgrading: https://nodejs.org/en/blog/release/v10.0.0/ In particular, Node.js now depends on OpenSSL 1.1.0h, so the BUNDLED_SSL option is enabled by default. Users can disable this option when using security/openssl-devel as their default SSL library. 20180430: AFFECTS: users of news/nntp AUTHOR: dinoex@FreeBSD.org The option INETD was removed. If you used inetd, please change the path in /etc/inetd.conf from /usr/local/sbin/nntpd to /usr/local/libexec/nntpd. 20180428: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.7 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl 20180427: AFFECTS: users of sysutils/zrepl AUTHOR: woodsb02@FreeBSD.org The zrepl update to 0.0.3 includes the following breaking changes: - Snapshots are automatically bookmarked and pruning of bookmarks must be configured by adding the keep_bookmarks parameter to the prune policy section of the zrepl configuration file (source side only). Be sure to understand the meaning bookmarks have for maximum allowable replication downtime. - The ssh+stdinserver transport protocol has changed, requiring zrepl to be updates on both the sending and receiving side, and the daemon restarted on both sides. - The first outlet in the global.logging section of the configuration file is now used for logging meta-errors (e.g. problems encountered when writing to other logging outlets). 20180425: AFFECTS: users of databases/pecl-redis AUTHOR: daniel@blodan.se pecl-redis 4.0.0 breaks backwards compatibility, users not aware if you are using the changed functionality or not should swap to databases/pecl-redis3 20180417: AFFECTS: users of dns/dnscrypt-proxy2 AUTHOR: egypcio@googlemail.com DNSCrypt-Proxy 2 has been updated to 2.0.10 and the configuration file has changed from ${PREFIX}/etc/dnscrypt-proxy.toml to ${PREFIX}/etc/dnscrypt-proxy/dnscrypt-proxy.toml. 20180416: AFFECTS: users of mail/postgrey AUTHOR: ports.maintainer@evilphi.com If you use any of the optional make.conf variables to specify the postgrey user, group, db dir, or run dir when building the port, you will need to change the prefix from PG_ to POSTGREY_*. The variables were renamed to solve a namespace collision with the PostgreSQL ports. 20180412: AFFECTS: users of devel/php-composer AUTHOR: madpilot@FreeBSD.org Flavors have been added to the composer port with the update to 1.6.3. Due to the change in PKGNAME pkg(and other tools) will not notice the update. It is required to tell pkg about the name change, for example: # pkg set -n php-composer:php56-composer 20180410: AFFECTS: users of KDE SC4 AUTHOR: kde@FreeBSD.org Most of KDE Applications 17.12.3 have now landed in the ports tree. There are still some missing pieces, that will follow soon. As mentioned in the commit messages, users of KDE SC4 should stick with the -kde4 named package. As the MOVED entries for ports like databases/akonadi-kde4 have been removed in the process of updating (as there now is again a databases/akonad), there might be issues for people that update from a too old installed package list with portmaster. These should be fixable by issuing a command à la # pkg set --change-origin databases/akonadi:databases/akonadi-kde4 akonadi 20180409: AFFECTS: users of net-im/matterircd AUTHOR: norrland@nullbyte.se Matterircd has been updated to 0.17.0 and mattermost configuration settings need to be migrated to [mattermost] section. See matterircd.toml.sample. 20180404: AFFECTS: users of www/nextcloud AUTHOR: brnrd@FreeBSD.org With the 13.0.1 update the path for Apps bundled with the package has changed from "apps" to "apps-pkg". You must add an entry to the "apps_paths" array in config/config.php of your nextcloud installation, a patch for the default installation can be applied with: # cd /usr/local/www/nextcloud # su -m www -c "php ./occ config:import < /usr/local/share/nextcloud/fix-apps_paths.json" 20180401: AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole AUTHOR: adamw@FreeBSD.org Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most existing dovecot installations MUST be modified for 2.3, but for most users the modifications are simple. Modify your Dovecot conf.d/ files before spinning up 2.3.1. The upgrading instructions are detailed here: https://wiki2.dovecot.org/Upgrading/2.3 20180330: AFFECTS: users of lang/perl5* AUTHOR: mat@FreeBSD.org The default Perl version has been switched to Perl 5.26. If you are using binary packages to upgrade your system, you do not have anything to do, pkg upgrade will do the right thing. For the other people, follow the instructions in entry 20161103, it should still be the same. 20180325: AFFECTS: users of net/samba48 AUTHOR: timur@FreeBSD.org New Samba 4.8 upgrades the relevant database files in the way, that doesn't allow easy fallback to the previous versions of Samba. So, before upgrading to the new version make a backup of the /var/db/samba4/ directory. Full list of changes, new features and upgrade procedure is available at: https://www.samba.org/samba/history/samba-4.8.0.html Please, read it carefully before upgrading!. 20180320: AFFECTS: users of x11/sterm AUTHOR: pkubaj@anongoth.pl The user-defined options in config.h have changed. You should compare your config.h file with the default one and change appropriately. 20180319: AFFECTS: users of dns/dnsmasq AUTHOR: mandree@FreeBSD.org Note that with dnsmasq 2.79, some parts of the interface have changed in an incompatible way versus previous versions. This comprises changed recursion behaviour, signature support, a change for SIGINT (vs. SIGHUP) behaviour. Note especially that dnsmasq will no longer answer non-recursive queries unless it is marked authoritative! Be sure to see the manual page for the various --auth-* options, such as --auth-zone. Please see the CHANGELOG that ships with dnsmasq for details. 20180317: AFFECTS: users of multimedia/plexpy AUTHOR: feld@FreeBSD.org Plexpy project has been renamed to Tautulli due to copyright infringement. The software also has received a major update. Please see the following upgrade instructions: - Install multimedia/tautulli - Create /var/db/tautulli, owned by the user you will run the daemon as (default: nobody). - Copy your config.ini and plexpy.db to /var/db/tautulli - Enable the service and start the software Tautulli should automatically find your database file, rename it to tautulli.db, and perform the required updates. 20180310: AFFECTS: users of security/openssl AUTHOR: brnrd@FreeBSD.org The EXPCIPHERS option has been removed from the security/openssl port. Use the security/openssl-unsafe port if you require this feature. 20180309: AFFECTS: users of net/unison AUTHOR: madpilot@FreeBSD.org Unison has been upgraded to version 2.51, which uses a different wire protocol than 2.48 did. In order to support synchronization with other computers where Unison is still at version 2.48, a new port net/unison248 has been created. It provides unison248 and, for the x11 flavor, also unison248-text. This unison248 port can be installed in parallel with the existing net/unison port. 20180308: AFFECTS: */php* */pecl* */pear* AUTHOR: mat@FreeBSD.org PHP extensions and modules have been flavored. People using Poudriere 3.2+ and binary packages do not have to do anything if they are using PHP applications. PHP modules and extensions may have change their names from php5- or php7- to fully versionned phpXY-. PECL extensions and PEAR modules package names have changed from pecl- and pear- to phpXX-pecl and phpXX-pear-. To rename an installed package to match the new naming scheme, for example, for the imagick pecl extension, run: # pkg set -n pecl-imagick:php56-pecl-imagick For other people, to build the PHP 7.2 version of, for example, databases/php-memcached, you need to run: # make FLAVOR=php72 install 20180220: AFFECTS: users of www/nextcloud AUTHOR: brnrd@FreeBSD.org The file and directory permissions of Nextcloud have changed. Write permissions have been removed from all directories except `data' and `config'. For the updater to work, the app store of your installation must be disabled. To disable the app-store prior to updating the package: # cd /usr/local/www/nextcloud # su -m www -c "php ./occ config:system:set appstoreenabled --value=false --type=boolean" If you've already updated your nextcloud package, you must manually edit the configuration of nextcloud (config/config.php) and add 'appstoreenabled' => false, to the CONFIG array before the updater will run. 20180214: AFFECTS: users of lang/ruby23 AUTHOR: swills@FreeBSD.org The default ruby version has been updated from 2.3 to 2.4. If you compile your own ports you may keep 2.3 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.3 as default version # DEFAULT_VERSIONS+=ruby=2.3 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkgng, simply upgrade: # pkg upgrade If you use portmaster, install new ruby, then rebuild all ports that depend on ruby: # portmaster -o lang/ruby24 lang/ruby23 # portmaster -R -r ruby-2.4 If you use portupgrade, install new ruby, then rebuild all ports that depend on ruby: # pkg delete -f ruby portupgrade # make -C /usr/ports/ports-mgmt/portupgrade install clean # pkg set -o lang/ruby23:lang/ruby24 # portupgrade -x ruby-2.4.\* -fr lang/ruby24 20180209: AFFECTS: users of japanese/lookup AUTHOR: yasu@utahime.org japanese/lookup is update to 1.99.96.20130920. This version is not compatible with previous version 1.4.1 and incompatibility includes how to setup. See info of Lookup for detail. 20180209: AFFECTS: users of net-mgmt/pmacct AUTHOR: pi@FreeBSD.org To allow separate pmacctd instances per interface, use pmacctd_enable="YES" pmacctd_interfaces="re1 re2" in /etc/rc.conf. The path to the config files will be /usr/local/etc/pmacct/ 20180208: AFFECTS: users of mail/mailman* AUTHOR: mandree@FreeBSD.org In order to overcome complaints about mismatched checksums in Mailman/Default.py, mailman now configures the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST to "localhost" statically, and the rc script will check this and refuse to start on next boot. Users must configure DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Mailman/mm_cfg.py properly and add this line below: add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) A short example has been added to: ${PREFIX}/local/share/doc/mailman/FreeBSD-post-install-notes. As of 2.1.26_3, the post-install script will add back the prior default settings to mm_cfg.py (instead of Defaults.py) if no virtual hosts have been defined, to cover the normal use cases and initial installation. 20180201: AFFECTS: users of editors/emacs* and all ports using Emacs via USES=emacs AUTHOR: jrm@FreeBSD.org The Emacs ports framework has been updated to support flavors and the editors/emacs-nox11 port has been replaced by the nox flavors of editors/emacs and editors/emacs-devel. Supported Flavors -------------------------------------------------------- editors/emacs: full canna nox editors/emacs-devel: full nox ports using Emacs: full canna nox devel_full devel_nox -------------------------------------------------------- For those using pre-built packages, if # pkg upgrade does not install the new Emacs package, use one of # pkg install emacs # pkg install emacs-canna # pkg install emacs-nox # pkg install emacs-devel # pkg install emacs-devel-nox For those building their own packages, a flavor other than the default must be specified. For example, to build the nox flavor of editors/emacs, or to build the devel_full flavor of a port using Emacs, use # poudriere bulk -j 11amd64 editors/emacs@nox # poudriere bulk -j 11amd64 print/pdf-tools@devel_full or # make FLAVOR=nox install # make FLAVOR=devel_full An alternative to the default flavor, full, for editors/emacs and editors/emacs-devel can be set in make.conf. For example, to specify nox as the default flavor for both ports, use .if ${.CURDIR:M*/editors/emacs*} FLAVOR?=nox .endif For ports using Emacs, an alternative to the default flavor, full, can be also be set in make.conf. For example, to automatically depend on emacs-nox, use DEFAULT_VERSIONS+=emacs=nox 20180117: AFFECTS: users of x11-toolkits/kf5-kirigami2 and x11/kf5-plasma-framework AUTHOR: kde@FreeBSD.org Files that were previously installed by kf5-kirigami2 are now installed by kf5-plasma-framework. This can lead to a conflict during the upgrade of the packages. It is recommended to first remove the package kf5-kirigami2. 20180115: AFFECTS: users of net-p2p/transmission-daemon AUTHOR: woodsb02@FreeBSD.org The transmission-daemon port has been updated to 2.92_4 to incorporate a patch which mitigates DNS rebinding attacks. This will prevent clients from being able to connect to the transmission daemon using DNS with any hostname other than localhost, unless one of the following is done: - Enable password authentication, then any hostname is allowed. This can be achieved by either: - setting rpc-authentication-required to true, and adding credentials to the rpc-username and rpc-password fields in settings.json (must be done whilst the transmission service is stopped); or - running transmission-daemon with the following arguments (these can be set with transmission_flags in /etc/rc.conf): -t -u USERNAME -v PASSWORD OR - Add the allowed server hostnames to the rpc-host-whitelist setting in settings.json (must be done whilst the transmission service is stopped). Note that this value is NOT a list of allowed CLIENTS, but instead a list of allowed SERVER hostnames. 20180111: AFFECTS: users of editors/vim-lite AUTHOR: adamw@FreeBSD.org The vim-lite port has been renamed to vim-console, because it isn't actually any lighter. All three vim packages are built with --enable-features=huge. Portmaster users will need to run this command: portmaster -o editors/vim-console editors/vim-lite If the switch doesn't happen automatically for you, just delete the vim-lite package and install vim-console. 20180109: AFFECTS: users of www/qt5-webengine AUTHOR: kde@FreeBSD.org The upgrade of www/qt5-webengine to 5.9.3 may fail if an older version of it is installed. It is recommended to either build the port in a builder like poudriere, or to deinstall and then doing an install. 20180107: AFFECTS: users of security/gnupg and mail/mutt and mail/neomutt AUTHOR: adamw@FreeBSD.org The invocation for gpg from mutt/neomutt changed between gnupg-2.0 (which has expired and is now removed) and gnupg-2.2 (the current version in the tree). Unless you're using gpgme, PGP-related commands may fail in (neo)mutt. In all cases, users are strongly urged to use security/gpgme to take care of the setup for you. If you prefer to roll your own, the following muttrc/neomuttrc entry has been reported to work: pgp_decrypt_command="gpg2 %?p?--passphrase-fd 0 --pinentry-mode=loopback? --no-verbose --batch --output - %f" See muttrc(5), neomuttrc(5), mutt.org, and neomutt.org for instructions on (neo)mutt's gpg and gpgme instructions. 20180102: AFFECTS: users of devel/awscli AUTHOR: bhughes@FreeBSD.org The package name for devel/awscli has changed (back) to just awscli. The introduction of flavors erroneously caused the awscli package to be renamed to py27-awscli. 20171230: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org If you are building ejabberd 17.11 on a host, which already has an older version of ejabberd installed, then build process will fail with "unknown type specifier" errors. As a workaround, please uninstall ejabberd before building ejabberd. This has been reported upstream at: https://github.com/processone/ejabberd/issues/2194 20171223: AFFECTS: users of dns/dnscrypt-proxy AUTHOR: egypcio@googlemail.com The 1.9.5_3 update of dns/dnscrypt-proxy replaces the default resolver used by dnscrypt-proxy (cisco/OpenDNS) by a random one that does not log entries and supports dnssec. 20171223: AFFECTS: users of samba44 AUTHOR: antoine@FreeBSD.org The default version of samba has been switched from 4.4 to 4.6. Upgrade instructions: For package users having samba44 installed indirectly (as a dependency): # pkg upgrade For package users having samba44 installed directly (leaf port): # pkg upgrade # pkg install samba46 For ports users: If you want to keep samba44, add DEFAULT_VERSIONS+= samba=4.4 to make.conf If you want to upgrade to samba46, remove samba44: # pkg delete -f samba44 Portmaster users: # portmaster net/samba46 # portmaster -a Portupgrade users: # portinstall net/samba46 # portupgrade -a 20171218: AFFECTS: users of devel/gogs AUTHOR: dg@syrec.org Gogs user has been changed to "git" and configuration files are now located in /usr/local/etc/gogs. Users should update ownership of the existing Gogs directories with # chown -R git:git /var/db/gogs # chown -R git:git /var/log/gogs and either move or merge the contents of /var/db/gogs/home/.ssh with /usr/local/git/.ssh. After migration, /var/db/gogs/home can be removed, and both the user "gogs" and the group "gogs" should be deleted: # rm -rf /var/db/gogs/home # pw userdel gogs # pw groupdel gogs 20171215: AFFECTS: users of finance/gnucash AUTHOR: madpilot@FreeBSD.org The gnucash port has been converted too use flavors, the GUILE1 and GUILE2 options have been converted to flavors so that two separate packages can be provided. Since the next major release of gnucash will drop guile1 support, the default flavor package is compiled against guile2, switching the previous default. Users who intend to stay on the guile1 version should deinstall the default gnucash package and install the gnucash-guile1 package. 20171214: AFFECTS: all ports users AUTHOR: adamw@FreeBSD.org Support for some deprecated variables is going to be removed soon. If you use any of the following constructs (usually in /etc/make.conf), you must switch to the new incantations: OLD NEW ------------------------------- ------------------------------ WITH_[...] OPTIONS_SET= [...] WITHOUT_[...] OPTIONS_UNSET= [...] WITHOUT_NLS OPTIONS_UNSET= NLS NOPORTDOCS OPTIONS_UNSET= DOCS NOPORTEXAMPLES OPTIONS_UNSET= EXAMPLES WITH_BDB_VER=[...] DEFAULT_VERSIONS+= bdb=[...] OVERRIDE_LINUX_BASE_PORT=[...] DEFAULT_VERSIONS+= linux=[...] WITH_OPENSSL_BASE DEFAULT_VERSIONS+= ssl=base WITH_OPENSSL_PORT DEFAULT_VERSIONS+= ssl=port 20171205: AFFECTS: users of dns/powerdns AUTHOR: krion@FreeBSD.org Recursor passthrough removal: This will impact many installations. Previously, the PowerDNS Authoritative Server contained a facility for sending recursion desired queries to a resolving backend, possibly after first consulting its local cache. This feature (‘recursor=’) was frequently confusing and also delivered inconsistent results, for example when a query ended up referring to a CNAME that was outside of the Authoritative Server’s knowledge. 20171203: AFFECTS: users of sysutils/dsbmd AUTHOR: mk@freeshell.de Due to new configuration variables and new features, users of dsbmd version 0.4.1 and earlier should consider recreating their dsbmd.conf from the new dsbmd.conf.sample. 20171130: AFFECTS: all ports users AUTHOR: adamw@FreeBSD.org The ports tree has gained "flavors," which are a way to produce multiple variations of a port. Some intended examples of this are language modules being produced for multiple language versions, and lite/nox11 packages, without needing separate ports for each variation. Python ports have already been flavored (see the below entry). Flavor support must be added to individual ports. Flavors are already supported by make, pkg, poudriere, and synth; see the manpages for those tools for usage instructions. Portmaster and portupgrade don't support flavors yet, but community work on those tools is in progress. Some bumps and breakages are inevitable for a major change such as this. Please report breakages and monitor the ports@ list for solutions as they become available. 20171130: AFFECTS: */py* AUTHOR: mat@FreeBSD.org Ports using Python via USES=python are now flavored. All the py3-* ports have been removed and folded into their py-* master ports. People using Poudriere 3.2+ and binary packages do not have to do anything. For other people, to build the Python 3.6 version of, for example, databases/py-gdbm, you need to run: # make FLAVOR=py36 install 20171126: AFFECTS: users of security/p5-openxpki AUTHOR: dbaio@FreeBSD.org OpenXPKI has been updated to 1.19.4, some important changes were made, please see the upgrading documentation for more details: http://openxpki.readthedocs.io/en/latest/upgrading.html 20171126: AFFECTS: users of mail/sympa AUTHOR: dgeo@centrale-marseille.fr Web's static dirs have moved to a single dedicated directory. Users should review webserver's /static configuration (examples in share/examples/sympa). 20171119: AFFECTS: users of sysutils/zrepl AUTHOR: woodsb02@FreeBSD.org Zrepl has been updated to 0.0.2, which introduces two changes that will require existing users to change their zrepl.yml config file: - global.logging is no longer a dictionary but a list. Refer to the new format here: https://zrepl.github.io/configuration/logging.html - source job field datasets renamed to filesystems. Refer to the new format here: https://zrepl.github.io/configuration/jobs.html https://zrepl.github.io/changelog.html#id1 20171117: AFFECTS: users of sysutils/terraform AUTHOR: lifanov@FreeBSD.org Terraform has been updated to 0.11, which introduces several incompatible changes. Please follow upgrading guide when updating the package. https://www.terraform.io/upgrade-guides/0-11.html 20171114: AFFECTS: users of ports-mgmt/poudriere AUTHOR: bdrewery@FreeBSD.org "poudriere options" now respects the -p flag while it did not before. This means that it may create an empty directory when used now rather than continue to use your existing options set. You may want to not use -p or move your existing options directory, in /usr/local/etc/poudriere.d/*-options, to the new format with the ports tree name in it. Otherwise "poudriere bulk" will use the new empty directory. This behavior will likely change in 3.2.1 to be more backwards-compatible. 20171112: AFFECTS: consumers of devel/oniguruma* AUTHOR: riggs@FreeBSD.org Outdated versions of oniguruma have been removed from the ports tree; devel/oniguruma is the only supported version, currently replacing devel/oniguruma6. pkg should handle this automatically while users of portmaster or portupgrade might need to take additional manual steps: for users of portmaster: portmaster -o devel/oniguruma devel/oniguruma6 portmaster -r devel/oniguruma for users of portupgrade: portupgrade -o devel/oniguruma devel/oniguruma6 portupgrade -fr devel/oniguruma 20171107: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to node.js v9.0.0, the latest upstream release. A new port, www/node8, has been created for the v8.x LTS branch. Users wanting to stay on v8.x can replace www/node with www/node8 with one of the following commands: # pkg install www/node8 or # portmaster -o www/node8 www/node or # portupgrade -o www/node8 www/node 20171107: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.6 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl 20171105: AFFECTS: users of www/mod_auth_cas AUTHOR: brnrd@FreeBSD.org The configuration of mod_auth_cas has changed since the previous version. Visit the https://github.com/apereo/mod_auth_cas page for an overview of all configuration parameters 20171105: AFFECTS: users of www/mod_rpaf2 AUTHOR: brnrd@FreeBSD.org The configuration of mod_rpaf2 has been heavily modified since version 0.6. Have a look at https://github.com/gnif/mod_rpaf/tree/v0.8.4 to determine what you need to change in your configuration. 20171031: AFFECTS: users of editors/vim AUTHOR: adamw@FreeBSD.org The default vim language bindings have changed. Python 2 and 3 bindings may now be enabled independently (the default vim package will continue to depend on python-2.7). Lua and Tcl bindings have been disabled by default. If you need these bindings, you'll need to compile vim yourself. Note that bindings are only for plugins written in those languages, and for interactive debugging. Editing, indenting, linting, completing, and syntax-highlighting those languages is NOT affected. 20171026: AFFECTS: users of devel/universal-ctags AUTHOR: rodrigo@FreeBSD.org Due to conflicts with emacs ctag (editors/emacs-devel, editors/emacs-nox11, editors/emacs), the installed files will be prefixed with the 'u' character. The new binaries will de named uctags and ureadtags. 20171015: AFFECTS: people using WITHOUT_DEBUG AUTHOR: madpilot@FreeBSD.org The WITHOUT_DEBUG flag has been retired. It's only purpose was to override a global WITH_DEBUG, if that was defined, but many ports were ignoring such flag even if honouring WITH_DEBUG. The same effect can be obtained using ".undef WITH_DEBUG" without any special support in port Makefiles. 20171012: AFFECTS: users of security/openssh-portable AUTHOR: bdrewery@FreeBSD.org OpenSSH has been upgraded to 7.6p1 which has removed several deprecated features: - SSH version 1 support dropped. - Dropped support for hmac-ripemd160 MAC. - Dropped support for the ciphers arcfour, blowfish and CAST. - RSA keys less than 1024 bits are refused. The HPN option is currently disabled by default, and does not build, in the package. This follows what happened in base as well. 20171004: AFFECTS: users of security/krb5-appl AUTHOR: cy@FreeBSD.org Configuration options to rename kerberos ftp, telnet, rlogin, rsh, and rcp are now default to avoid conflicting with net/bsdrcmds packages (in poudriere). Deselect the options to use the original command names and also uninstall net/bsdrcmds to avoid the conflict. 20171002: AFFECTS: users of x11-wm/cwm AUTHOR: tobik@FreeBSD.org Configuration options were renamed and you need to update your ~/.cwmrc accordingly. Make sure to check cwmrc(5) for the new option names. cwm-migrate-config.pl can help in migrating your ~/.cwmrc. 20171001: AFFECTS: users of mail/isync using Maildir sub-folders AUTHOR: ehaupt@FreeBSD.org If you have Maildir sub-folders, you need to update the configuration to specify the naming style. Please refer to the mbsync(1) man page section 'SubFolders Verbatim|Maildir++|Legacy' on how to make the apropriate changes. 20170930: AFFECTS: users of PHP and its modules AUTHOR: eugen@FreeBSD.org All lang/php* ports switched to depend on devel/oniguruma6 instead of previous oniguruma version some time ago. If you have not moved from devel/oniguruma5 before and have troubles updating PHP, for users of portmaster: portmaster -o devel/oniguruma6 devel/oniguruma5 portmaster -r devel/oniguruma6 for users of portupgrade: portupgrade -o devel/oniguruma6 devel/oniguruma5 portupgrade -fr devel/oniguruma6 pkg should handle this automatically. 20170928: AFFECTS: users of security/courier-authlib and its modules AUTHOR: madpilot@FreeBSD.org The affected ports have been modified to follow the upstream suggested best practice to use the sysconftool on installation. Please make sure your configuration files include all the comments that tool uses to correctly update the configuration on update. You can use the ".sample" or ".dist" files as templates for missing comments if needed. 20170915: AFFECTS: users of devel/cargo AUTHOR: rust@FreeBSD.org Starting with version 1.19.0, Cargo is provided with Rust. Therefore, devel/cargo was merged into lang/rust. 20170914: AFFECTS: users of CMake & CMake Modules AUTHOR: adridg@FreeBSD.org The devel/cmake-modules port has been merged into devel/cmake. The benefit of being able to update the modules without the binary is outweighed by the issues caused by having the binary out-of-sync with the modules. Users should delete the devel/cmake-modules package and then upgrade or reinstall devel/cmake. All ports have been updated to depend only on CMake. 20170904: AFFECTS: users of net-mgmt/seafile-server AUTHOR: ultima@FreeBSD.org Users using MySQL updating to 6.1.2 need to verify table's collation are utf8_unicode_ci. Upstream has set collation type to be implicit and will cause all libraries to disappear if set to incorrect collation. 20170828: AFFECTS: users of security/gnupg AUTHOR: adamw@FreeBSD.org security/gnupg has become the new stable version of GnuPG. This is an LTS branch. gnupg20 will reach EOL at the end of the year, and all gnupg20 users should migrate to gnupg22. See https://gnupg.org/faq/whats-new-in-2.1.html for important changes. 20170820: AFFECTS: users of www/uwsgi AUTHOR: ultima@FreeBSD.org The default socket owner and mode had been changed from www:www 600 to uwsgi:www 660. This should resolve issue #1471[1] on github. [1] https://github.com/unbit/uwsgi/issues/1471 20170808: AFFECTS: users of lang/ghc and */hs-* AUTHOR: haskell@FreeBSD.org The Glorious Glasgow Haskell Compiler has been updated to version 8.0.2. Hence it is recommended to rebuild or reinstall all the dependent ports and the lang/ghc port itself in one of the following ways: # portmaster -w -r ghc or # portupgrade -fr lang/ghc In case of pkg(8), it is probably safer to remove all the GHC-dependent packages along with GHC and reinstall everything from scratch. For example: # pkg query "%ro" ghc > ghc-pkgs.txt # pkg delete -y lang/ghc In ghc-pkgs.txt, check and remove all the packages that have been moved on the update, then use this command: # pkg install -y `cat ghc-pkgs.txt` 20170807: AFFECTS: users of mail/dovecot2 and mail/dovecot2-pigeonhole AUTHOR: adamw@FreeBSD.org Now that dovecot1 has been removed from the ports tree, dovecot2 and dovecot2-pigeonhole have been renamed to simply dovecot and dovecot-pigeonhole. pkg should handle the rename automatically, but if you run into trouble, you can point pkg at the new origin via: # pkg set -o mail/dovecot2:mail/dovecot # pkg set -o mail/dovecot2-pigeonhole:mail/dovecot-pigeonhole Similarly, you can point portmaster at the new location via: # portmaster -o mail/dovecot mail/dovecot2 If all else fails, just remove and reinstall the package: # pkg delete dovecot2 # pkg install dovecot 20170806: AFFECTS: users of mail/dovecot2-antispam-plugin AUTHOR: adamw@FreeBSD.org Development of the antispam plugin ceased years ago, and upstream recommends using pigeonhole (mail/dovecot2-pigeonhole) instead. See https://wiki2.dovecot.org/HowTo/AntispamWithSieve for a recipe to replicate the antispam plugin's behaviour. 20170803: AFFECTS: users of net/guacamole-client AUTHOR: ultima@FreeBSD.org As of version 0.9.13, the configuration directory for guacamole-client has changed from /usr/local/etc/guacamole to /usr/local/etc/guacamole-client. 20170803: AFFECTS: users of net/guacamole-server AUTHOR: ultima@FreeBSD.org As of version 0.9.13, the configuration directory for guacamole-server has changed from /usr/local/etc/guacd to /usr/local/etc/guacamole-server. 20170803: AFFECTS: users of sysutils/terraform AUTHOR: lifanov@FreeBSD.org Terraform was updated to version 0.10.0, which split out provider plugins. Provider plugins are now installed in the project directory the next time "terraform init" is run. Please see the complete upgrading guide: https://www.terraform.io/upgrade-guides/0-10.html 20170729: AFFECTS: users of net-p2p/bitcoin AUTHOR: lwhsu@FreeBSD.org Bitcoin data directory has been changed from /var/db/bitcoind to /var/db/bitcoin. Users of previous versions may want to migrate data to new location or specify bitcoind_data. 20170729: AFFECTS: users of mail/mailscanner AUTHOR: crees@FreeBSD.org Version 5.0.3 of MailScanner introduced a serious bug in packaging. Unfortunately if it is installed, your configuration has been deleted. If you have managed to get it working, please back up /usr/local/etc/MailScanner as it will also be deleted on deinstall of the same package. 20170726: AFFECTS: users of www/luakit AUTHOR: ports@textmail.me Luakit was updated to version 2017.07.26, which is incompatible to the previous release from 2012. Please remove old configuration files from the following directories: ${PREFIX}/etc/xdg/luakit ${HOME}/.config/luakit ${HOME}/.local/share/luakit 20170721: AFFECTS: users of security/sshguard* AUTHOR: dan.mcgregir@usask.ca security/sshguard was updated to 2.0.0, and security/sshguard-pf, security/sshguard-ipfw, and security/sshguard-null have been merged into security/sshguard. Configuration of the service is now handled in ${PREFIX}/etc/sshguard.conf. Please select the desired backend, -null is selected by default. In order to upgrade from 1.7.1 change the origin to security/sshguard # pkg set -o security/sshguard-ipfw:security/sshguard # pkg set -o security/sshguard-null:security/sshguard # pkg set -o security/sshguard-pf:security/sshguard 20170717: AFFECTS: users of devel/p5-Log-Any and devel/p5-Log-Any-Adapter-Syslog AUTHOR: eugen@FreeBSD.org devel/p5-Log-Any-Adapter-Syslog functionality have been merged into devel/p5-Log-Any and from now devel/p5-Log-Any must be used. devel/p5-Log-Any-Adapter-Syslog will be marked as deprecated and removed. 20170712: AFFECTS: users of devel/apr1 AUTHOR: brnrd@FreeBSD.org APR was updated to 1.6.0 and APR-util was updated to 1.6.2 The Apache Portable Runtime project removed support for FreeTDS from the APR Utilities in version 1.6. Users of FreeTDS will have to migrate configurations to use the newly added ODBC support in conjunction with FreeTDS using FreeTDS' ODBC capabilities. Please rebuild all ports which are using functions from APR/APR-util such as Apache, Subversion, etc. Normally, you can obtain the list of dependent software by running the following command: # pkg info -r apr Then you should rebuild all ports depending on APR(-util) to avoid dangling shared library dependencies. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r apr Portupgrade users: portupgrade -fr devel/apr1 20170710: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org After update to 17.07, there is an issue[1] expected related to certificate verification with TLS connections. [1] - https://github.com/processone/ejabberd/issues/1833 20170628: AFFECTS: users of www/node AUTHOR: bhughes@FreeBSD.org The www/node port has been updated to Node.js v8.1.2, the latest upstream release. This is a major release, including many significant changes. Users are encouraged to read the release announcements before upgrading: https://nodejs.org/en/blog/release/v8.0.0/ https://nodejs.org/en/blog/release/v8.1.0/ 20170626: AFFECTS: users of net-mgmt/zabbix24* AUTHOR: dbaio@FreeBSD.org Zabbix 2.4 has reached end of life and net-mgmt/zabbix24* ports have been removed. Users that have not yet moved to a newer version, should use now net-mgmt/zabbix3-* (LTS release) or net-mgmt/zabbix32-* (Standard release). See more info about Zabbix releases here: http://www.zabbix.com/life_cycle_and_release_policy 20170624: AFFECTS: users of mail/dcc-dccd AUTHOR: ultima@FreeBSD.org The ALT_HOME option was removed in 1.3.159_1. If this option is being used, please be sure to move the old home directory, /var/dcc to ${PREFIX}/dcc. 20170624: AFFECTS: users of net/rabbitmq AUTHOR: olgeni@FreeBSD.org The rabbitmq-3.6.10_1 port has been changed to use version 19 of the Erlang runtime, because RabbitMQ is not yet compatible with version 20. Upgrades to the previous rabbitmq-3.6.10 must be avoided as they can lead to data corruption due to changes in Erlang 20. 20170622: AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run AUTHOR: tz@FreeBSD.org The default version of PostgreSQL has been switched from 9.3 to 9.5. 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 9.3.12, your files are named according to this. # service postgresql stop # pkg create postgresql93-server postgresql93-contrib # mkdir /tmp/pg-upgrade # tar xf postgresql93-server-9.3.17.txz -C /tmp/pg-upgrade # tar xf postgresql93-contrib-9.3.17.txz -C /tmp/pg-upgrade # mv /usr/local/pgsql/data /usr/local/pgsql/data93 # pkg delete -f databases/postgresql93-server databases/postgresql93-contrib databases/postgresql93-client Now update PostgreSQL: pkg user: # pkg install databases/postgresql95-server databases/postgresql95-contrib # pkg upgrade Portmaster users: # portmaster databases/postgresql95-server databases/postgresql95-contrib # portmaster -a Portupgrade users: # portinstall databases/postgresql95-server databases/postgresql95-contrib # portupgrade -a After installing the new PostgreSQL version you need to convert all your databases to new version: # service postgresql initdb # su -l pgsql -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data93/ -B /usr/local/bin/ -D /usr/local/pgsql/data/" Now the migration is finished. You can start PostgreSQL again with: # service postgresql start 20170614: AFFECTS: users of editors/calligra AUTHOR: groot@kde.org Calligra has been updated to 3.0.1, which is a KDE Frameworks 5 (KF5) based application. Calligra now uses Qt5 and KF5. The translations have been merged (upstream) into the application, so separate language / translation ports are no longer provided. Krita has been split out (upstream) into a separate application, which is packaged as graphics/krita. Kexi, the visual database applications creator, is packaged separately as databases/kexi. Users of Calligra are encouraged to install Krita and Kexi separately, and to report issues with the upgrade to kde@. 20170613: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org After update to 17.04, there is an issue[1] expected with S2S connections, which can be resolved by adding 'mod_s2s_dialback: {}' to 'modules' section of configuration file. [1] - https://github.com/processone/ejabberd/issues/1700 20170603: AFFECTS: users of www/kanboard AUTHOR: joneum@FreeBSD.org After update to 1.0.44, there are following breaking changes: * Move calendar to external plugin: https://github.com/kanboard/plugin-calendar * Move Gantt charts to external plugin: https://github.com/kanboard/plugin-gantt * Move Gravatar to external plugin: https://github.com/kanboard/plugin-gravatar 20170602: AFFECTS: users of Qt 5 in presence of binutils AUTHOR: amdmi3@FreeBSD.org gold linker from binutils 2.28 may produce duplicate library symbols, which makes shared libraries created with it not usable with conventional ld linker. This affects Qt, as qt5-qmake will detect gold and use it to build Qt libraries. Broken libQt5Core will be produced and ports which depend on it will then fail to link with the following errors: ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `__bss_start at Qt_5' ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `_edata at Qt_5' ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here ...lib/libQt5Core.so:(.dynamic+0x2b2d0): multiple definition of `_end at Qt_5' Qt5 was fixed to ignore gold. If you see these errors, you need to rebuild qt5-qmake, then all qt5-* ports. 20170529: AFFECTS: users of sysutils/dsbmd AUTHOR: mk@freeshell.de Due to new configuration variables and semantic changes, users of dsbmd version 0.2 and earlier should consider recreating their dsbmd.conf from the new dsbmd.conf.sample. 20170518: AFFECTS: users of www/yarn AUTHOR: adamw@FreeBSD.org The default node backend for yarn has switched to www/node. Binary package users should expect the node backend to be switched during the upgrade. To keep the node6 (LTS) backend, rebuild www/yarn with the NODE6 backend option enabled. 20170517: AFFECTS: users of security/pecl-ssh2 AUTHOR: dbaio@FreeBSD.org The security/pecl-ssh2 has been upgraded to version 1.0, and the new version is not compatible with PHP5. If you need PHP5 support, you can find version 0.13 in security/pecl-ssh2-0. 20170412: AFFECTS: users of sysutils/ansible AUTHOR: lifanov@FreeBSD.org The default value for ansible_python_interpreter has been changed to match the upstream /usr/bin/python. If managing FreeBSD systems, adjust the hosts database to explicitly set a valid python interpreter: [freebsd] host1 [freebsd_vars] ansible_python_interpreter=/usr/local/bin/python2.7 20170411: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.5 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl 20170411: AFFECTS: www/firefox AUTHOR: gecko@FreeBSD.org Firefox 53 or later may fail to build if sem(4) is present (see below) because sysconf(3) still consults the old limits. If you don't plan to run FreeBSD 8.x or older binaries make sure sem(4) isn't loaded during boot or built statically into the kernel. Creating config.status Traceback (most recent call last): File "configure.py", line 124, in sys.exit(main(sys.argv)) File "configure.py", line 34, in main return config_status(config) File "configure.py", line 119, in config_status return config_status(args=[], **encode(sanitized_config, encoding)) File "python/mozbuild/mozbuild/config_status.py", line 136, in config_status reader = BuildReader(env) File "python/mozbuild/mozbuild/frontend/reader.py", line 886, in __init__ self._gyp_worker_pool = ProcessPoolExecutor(max_workers=max_workers) File "python/futures/concurrent/futures/process.py", line 274, in __init__ _check_system_limits() File "python/futures/concurrent/futures/process.py", line 263, in _check_system_limits raise NotImplementedError(_system_limited) NotImplementedError: system provides too few semaphores (30 available, 256 necessary) 20170410: AFFECTS: users of x11-wm/awesome AUTHOR: garga@FreeBSD.org Awesome Window Manager (x11-wm/awesome) was upgraded to 4.1 and its config is not backward compatible with 3.5. A new port was created to keep 3.5 version available at x11-wm/awesome3 and it will be available for 6 months until users have time to upgrade configuration. There are references about what has changed in 4.0 at: https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4 And configuration porting tips at: https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4 If you would like to keep using 3.x, please run the collowing command to update pkg database: # pkg set -n awesome:awesome3 # pkg set -o x11-wm/awesome:x11-wm/awesome3 20170404: AFFECTS: users of Xapian 1.2.x and www/ikiwiki AUTHOR: sunpoet@FreeBSD.org Xapian has been updated to 1.4.3. The 1.2.x series has been renamed with suffix "12". The Perl binding for Xapian 1.4.x is databases/p5-Xapian. Since www/ikiwiki depends on Search::Xapian, it stays with Xapian 1.2. If you would like to keep using 1.2, please run the following commands to update pkg database: xapian-core: # pkg set -n xapian-core:xapian-core12 # pkg set -o databases/xapian-core:databases/xapian-core12 p5-Search-Xapian: # pkg set -n p5-Search-Xapian:p5-Search-Xapian12 # pkg set -o databases/p5-Search-Xapian:databases/p5-Search-Xapian12 xapian-bindings: # pkg set -n xapian-bindings:xapian-bindings12 # pkg set -o databases/xapian-bindings:databases/xapian-bindings12 xapian-omega: # pkg set -n xapian-omega:xapian-omega12 # pkg set -o databases/xapian-omega:databases/xapian-omega12 20170401: AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl* AUTHOR: timur@FreeBSD.org It turned out that arbitary versions of p5-Parse-Pidl may lead to the hard to explain crashes of the Samba server and utilities(in particular we suspect it was responsible for the troubles with the DC provisioning). So, from now on net/samba* ports use bundled version of Pidl. You need to remove external package from the system: pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44 20170331: AFFECTS: users of security/openssh-portable AUTHOR: bdrewery@FreeBSD.org The format of several log messages emitted by the packet code has changed to include additional information about the user and their authentication state. Software that monitors ssh/sshd logs may need to account for these changes. For example: Connection closed by user x 1.1.1.1 port 1234 [preauth] Connection closed by authenticating user x 10.1.1.1 port 1234 [preauth] Connection closed by invalid user x 1.1.1.1 port 1234 [preauth] Affected messages include connection closure, timeout, remote disconnection, negotiation failure and some other fatal messages generated by the packet code. 20170326: AFFECTS: users of samba43 AUTHOR: antoine@FreeBSD.org The default version of samba has been switched from 4.3 to 4.4. Upgrade instructions: For package users having samba43 installed indirectly (as a dependency): # pkg upgrade For package users having samba43 installed directly (leaf port): # pkg upgrade # pkg install samba44 For ports users: If you want to keep samba43, add DEFAULT_VERSIONS+= samba=4.3 to make.conf If you want to upgrade to samba44, remove samba43 and obsolete packages: # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 samba43 p5-Parse-Pidl Portmaster users: # portmaster net/samba44 # portmaster -a Portupgrade users: # portinstall net/samba44 # portupgrade -a 20170325: AFFECTS: net/samba46 and devel/p5-Parse-Pidl AUTHOR: timur@FreeBSD.org New version of Samba port from 4.6 branch is added. Before upgrading please read upgrade notes: https://www.samba.org/samba/history/samba-4.6.0.html For the vfs_fruit users: Users on *BSD must rename the metadata xattr used by vfs_fruit when using the default setting "fruit:metadata = netatalk". Due to a glitch in the Samba xattr API compatibility layer for FreeBSD and a mistake in vfs_fruit, vfs_fruit ended up using the wrong xattr name when configured with "fruit:metadata = netatalk" (default). Instead of the correct org.netatalk.Metadata it used netatalk.Metadata Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" which means existing installations must rename this xattrs. For this purpose Samba now includes a new tool `mvxattr`. 20170325: AFFECTS: net/samba45, net/samba46 and devel/p5-Parse-Pidl AUTHOR: timur@FreeBSD.org While new Uses/samba.mk dosen't work well with slave ports to compile devel/p5-Parse-Pidl for net/samba45 or net/samba46 you need explicitly set in the /etc/make.conf: SAMBA4_PORT=net/samba46 explicitly. In the future that shouldn't be necessary. 20170321: AFFECTS: users of samba36-libsmbclient, samba36-nmblookup samba36-smbclient and samba36 AUTHOR: antoine@FreeBSD.org The obsolete samba36-libsmbclient, samba36-nmblookup, samba36-smbclient and samba36 packages/ports were removed and USES=samba was introduced. Upgrade instructions: For package users having those ports installed indirectly (as dependencies): # pkg upgrade For package users having those ports installed directly (leaf ports): # pkg upgrade # pkg install samba43 For ports users: Choose you samba version, for instance add DEFAULT_VERSIONS+= samba=4.3 to make.conf Remove obsolete packages: # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 Portmaster users: # portmaster net/samba43 # portmaster -a Portupgrade users: # portinstall net/samba43 # portupgrade -a 20170319: AFFECTS: users of mail/pecl-mailparse AUTHOR: dbaio@bsd.com.br The mail/pecl-mailparse has been upgraded to version 3.0.2, and the new version is not compatible with PHP5. If you need PHP5 support, you can find version 2.1.6 in mail/pecl-mailparse2. 20170319: AFFECTS: users of textproc/pecl-yaml AUTHOR: dbaio@bsd.com.br The pecl-yaml has been upgraded to version 2.0.0, and the new version is not compatible with PHP5. If you need PHP5 support, you can find version 1.3.0 in textproc/pecl-yaml1. 20170316: AFFECTS: users of python setuptools AUTHOR: antoine@FreeBSD.org The python setuptools ports have been renamed to better match other python ports. Ports users need to rename them so that portupgrade and portmaster do not get confused. For example: pkg set -n py27-setuptools27:py27-setuptools pkg set -o devel/py-setuptools27:devel/py27-setuptools or pkg set -n py35-setuptools35:py35-setuptools pkg set -o devel/py-setuptools35:devel/py35-setuptools 20170312: AFFECTS: users of textproc/ack AUTHOR: sunpoet@FreeBSD.org ack has been renamed back to p5-ack to match our perl naming. You could run the following to update pkg database: # pkg set -n ack:p5-ack # pkg set -o textproc/ack:textproc/p5-ack 20170311: AFFECTS: users of games/tome4 with paid DLCs AUTHOR: lifanov@FreeBSD.org The Ashes of Urh'Rok and Embers of Rage DLCs have been updated to be compatible with changes introduced in ToME 1.5.0. Users of these DLCs will need to redownload nd place these in $HOME/.t-engine/4.0/addons. 20170302: AFFECTS: users of mail/thunderbird with Lightning AUTHOR: cmt@FreeBSD.org After changes in the packaging of the Lightning extension, profiles using this extension have to be re-created. 20170223: AFFECTS: users of devel/mtbl AUTHOR: truckman@FreeBSD.org There is a libmtbl shared library version bump in mtbl version 1.0.0. The affected dependent ports have had PORTREVISION bumps, but you will need to rebuild any applications that link to libmtbl. 20170220: AFFECTS: sysutils/filebeat sysutils/metricbeat sysutils/packetbeat AUTHOR: girgen@FreeBSD.org The three elasticsearch beats ports have merged into one single port systuils/beats that installs all of the above and some more. The reason is to make the port more maintainable and also that the new heartbeat beat would conflict with sysutils/heartbeat. 20170220: AFFECTS: devel/libevent2 AUTHOR: jbeich@FreeBSD.org libevent2 has been renamed back to libevent as the default version. If you manage out of tree ports make sure to run the following: # pkg set -n libevent2:libevent # pkg set -o devel/libevent2:devel/libevent 20170218: AFFECTS: users of Qt 4 and Qt 5 AUTHOR: kde@FreeBSD.org Following what is already done in Qt 5, the Qt 4 ports no longer install their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most cases). Additionally, the "-qt4" suffix has been dropped from the file names of the binaries that had it, such as "qmake-qt4". The new misc/qtchooser port is now used to choose whether a Qt 4 or Qt 5 version of a binary such as "moc", "qmake" or "designer" will be used. By default, the Qt 5 versions are preferred, but that can be changed by setting the QT_SELECT environment variable to "qt4". qtchooser also allows one to seamlessly use other Qt installations for those binaries, which is particularly beneficial to people working on Qt itself or who need their own checkouts. See qtchooser(1) for more information on how to configure qtchooser. 20170213: AFFECTS: users of www/node* AUTHOR: bradleythughes@fastmail.fm The BUNDLED_SSL option is now enabled by default on FreeBSD 10, since Node.js requires OpenSSL 1.0.2, and FreeBSD 10 is shipped with 1.0.1. 20170213: AFFECTS: users of graphics/libGL, graphics/libEGL, graphics/libglesv2 AUTHOR: kwm@FreeBSD.org The workaround for handling conflicting libraries between the nvidia-driver, libGL, libEGL and libglesv2 ports was removed. If the nvidia-driver port is updated before the other ports, it will remove the libraries of said ports. This is a side effect of how the workaround worked. If this happens reinstalling the affected port is enough. pkg users can run: pkg install -f libGL libEGL libglesv2 20170211: AFFECTS: users of x11-server/xorg-server AUTHOR: rezny@FreeBSD.org Xorg server has been updated to 1.18.4 and autodetection has changed. The order in which drivers are now attempted is: 1) vendor/model specific driver according to PCI IDs 2) generic modesetting driver which requires a drm driver with KMS 3) scfb, the generic framebuffer driver 4) vesa (only if arch is x86) This should minimize the need for xorg.conf files. It is recommended to load the correct KMS driver (i915kms.ko or radeonkms.ko) via rc.conf, i.e. kld_list="i915kms.ko", to ensure correct functionality. Although the vendor drivers may attempt to load the correct drm driver, which does not always work, the modesetting driver assumes the required KMS driver is already loaded and will fail if there is none. The modesetting driver is now recommended as an alternative to the Intel driver; the performance is comparable and stability is better with modesetting. The ATI driver continues to offer better performance than modesetting. 20170203: AFFECTS: users of security/libressl-devel AUTHOR: brnrd@FreeBSD.org The version 2.5.1 bumps the libcrypto, libssl and libtls shared library versions. You will have to rebuild all packages that depend on libressl-devel. Check the 20160811 libressl entry for more detailed guidance on rebuilding. 20170202: AFFECTS: users of www/uwsgi AUTHOR: feld@FreeBSD.org The previous disruptive changes to uwsgi for security have been remediated through creation of a dedicated uwsgi user/group and utilizing the uwsgi feature to set socket ownership. The uwsgi daemon by default now has the following properties: * Process runs as uwsgi user and group (UID/GID 165) * Socket mode is 660, still protecting unauthorized access from "other" * Socket ownership is www:www, restoring compatibility 20170130: AFFECTS: users of devel/ice, devel/py-ice, devel/php5-ice AUTHOR: grembo@FreeBSD.org Since __WORDSIZE as defined by always reports 32 when using C++98/03 (unless __STDC_LIMIT_MACROS is set explictly), Ice 3.6.3 used "long long" for Int64 instead of "long" on 64-bit platforms by mistake. A workaround has been added in version 3.6.3_2 of these three ports, requiring to upgrade all of them at the same time and to rebuild all custom code that links against them. 20170129: AFFECTS: users of multimedia/motion AUTHOR: jhale@FreeBSD.org Version 3.x expected the configuration files to reside in: ${LOCALBASE}/etc Version 4.x expects the configuration files to reside in: ${LOCALBASE}/etc/motion This was unfortunately overlooked when the port was updated to 4.x, but it has now been fixed to install the default configuration file in the new location. The rc script now checks for motion.conf in the new location. While you may be able to simply copy your old motion.conf to the new location, it is recommended to review ${LOCALBASE}/etc/motion/motion.conf and make changes to it based on your old ${LOCALBASE}/etc/motion.conf as some options have been added and removed. Further, if you use motion with multiple cameras and have ${LOCALBASE}/etc/thread[0-9].conf files, they should be moved to ${LOCALBASE}/etc/motion as well. These files are deprecated and should be renamed to camera[0-9].conf and in motion.conf, lines like: thread /usr/local/etc/thread1.conf Should be converted to: camera /usr/local/etc/motion/camera1.conf 20170127: AFFECTS: users of www/uwsgi AUTHOR: feld@FreeBSD.org The default socket mode for uwsgi as 777 is a severe security concern. This has been remediated by changing the rc script to default to 600. The mode is configurable with rc.conf values: uwsgi_socket_mode="600" or for a profile named "www", uwsgi_www_socket_mode="600". 20170121: AFFECTS: users of security/tinc AUTHOR: dinoex@FreeBSD.org this version of tinc requires all nodes in the VPN to be linked with a version of OpenSSL or LibreSSL that supports the AES256 and SHA256 algorithms. 20170120: AFFECTS: users of databases/mysql56-server AUTHOR: feld@FreeBSD.org databases/mysql56-server was updated to 5.6.35 which included backported rc script changes from the mysql57-server port. This broke mysql_optfile in rc.conf and also forced a sample my.cnf if none existed. MySQL has some parameters which cannot be changed after a database has been created, so this caused MySQL to fail to start. This change was reverted in mysql56-server-5.6.35_1 An additional change was made in mysql56-server-5.6.35_2 to prevent automatic loading of a sample my.cnf which was causing issues for users who were running without a my.cnf. 20170117: AFFECTS: users of EoL'ed FreeBSD versions (<10.3, 11 prior to 11.0) AUTHOR: amdmi3@FreeBSD.org The ports system will now refuse to build anything if it's run on outdated system version. This protects users from unexpected build failures after code to support EoL'ed systems is removed from the tree. You may define ALLOW_UNSUPPORTED_SYSTEM to override this and allow builds, but no support will be provided in case of failures. 20170116: AFFECTS: users of java/wildfly10 AUTHOR: olgeni@FreeBSD.org The java/wildfly10 port has been updated to 10.1.0. To complete the migration you must copy your existing configuration (directories "appclient", "standalone", and "domain") from /usr/local/wildfly-10.0.0 to /usr/local/wildfly10. 20170115: AFFECTS: users of net-mgmt/librenms AUTHOR: dvl@FreeBSD.org The following is recommended for /var/db/mysql/my.cnf NOTE: these are global settings. Please read this first: http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html [mysqld] innodb_file_per_table=1 sql-mode="" 20170109: AFFECTS: users of lang/ruby22 AUTHOR: swills@FreeBSD.org The default ruby version has been updated from 2.2 to 2.3. If you compile your own ports you may keep 2.2 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 2.2 as default version # DEFAULT_VERSIONS+=ruby=2.2 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkgng, simply upgrade: # pkg upgrade If you use portmaster, install new ruby, then rebuild all ports that depend on ruby: # portmaster -o lang/ruby23 lang/ruby22 # portmaster -R -r ruby-2.3 If you use portupgrade, install new ruby, then rebuild all ports that depend on ruby: # pkg delete -f ruby portupgrade # make -C /usr/ports/ports-mgmt/portupgrade install clean # pkg set -o lang/ruby22:lang/ruby23 # portupgrade -x ruby-2.3.\* -fr lang/ruby23 20170102: AFFECTS: multimedia/ffmpeg AUTHOR: jbeich@FreeBSD.org OPTIMIZED_CFLAGS switched to only use vendor optimizations which means -ffast-math -fno-finite-math-only are no longer applied. If you did like the former behavior consider adding # multimedia/ffmpeg/Makefile.local OPTIMIZED_CFLAGS_CFLAGS += -ffast-math -fno-finite-math-only or # /etc/make.conf .if ${.CURDIR:M*/multimedia/ffmpeg} CFLAGS += -ffast-math -fno-finite-math-only .endif 20161230: AFFECTS: users of x11/xfce4-terminal AUTHOR: olivierd@FreeBSD.org The port has been updated to the latest stable version 0.8.2. Please, don't active the hidden 'MiscSlimTabs' option in ~/.config/xfce4/terminal/terminalrc, it requires Gtk+ > 3.20. 20161228: AFFECTS: users of multimedia/mlt AUTHOR: avilla@FreeBSD.org MLT Qt plugins have been moved to their own ports, mlt-qt4 and mlt-qt5. Please, uninstall multimedia/mlt before you update: # pkg delete mlt 20161227: AFFECTS: users of security/openvpn, security/openvpn-polarssl AUTHOR: Matthias Andree The OpenVPN ports have been updated to the new upstream release v2.4, and their predecessors preserved as openvpn23 and openvpn23-polarssl, respectively. Note that for the new v2.4 release, the openvpn-polarssl port has been renamed to openvpn-mbedtls to match the upstream library's new name. 20161218: AFFECTS: users of www/nghttp2 AUTHOR: sunpoet@FreeBSD.org nghttp2 has been split into 2 ports: www/libnghttp2 for core library and www/nghttp2 for the rest. Please uninstall nghttp2 before you update this port. 20161216: AFFECTS: mail/thunderbird, www/seamonkey AUTHOR: gecko@FreeBSD.org ENIGMAIL is no longer provided as part of the ports after upstream dropped binary components in 1.9. Go to Tools -> Add-ons Manager then type "enigmail" in the search box to install. 20161213: AFFECTS: users of devel/skalibs, lang/execline, sysutils/s6 AUTHOR: Colin Booth skalibs has undergone a major version bump and compatibility is not guaranteed for software with a runtime dependency on libskarnet.so.2.3.9.0. This will not affect lang/execline or sysutils/s6 as those are statically linked against libskarnet.a. execline has undergone a major version bump and compatibility is not guaranteed for software with a runtime dependency on libexecline.so.2.1.4.5. This will not affect sysutils/s6 as all s6 programs are statically linked against libexecline.a. s6 has undergone a major version bump and compatibility is not guaranteed for software with a runtime dependency on libs6.so.2.2.4.3. Additionally, s6-applyuidgid and s6-setuidgid have moved from $PREFIX/sbin to $PREFIX/bin. Any scripts calling those utilities that are not relying on $PATH resolution to find them will need to be rewritten. 20161207: AFFECTS: users of www/node AUTHOR: bradleythughes@fastmail.fm The www/node port has been updated to node.js v7.2.0, the latest upstream release. A new port, www/node6, has been created for the v6.x LTS branch. Users wanting to stay on v6.x can replace www/node with www/node6 with one of the following commands: # pkg set -o www/node:www/node6 or # portmaster -o www/node6 www/node or # portupgrade -o www/node6 www/node 20161202: AFFECTS: users of textproc/p5-Search-Elasticsearch AUTHOR: tj@FreeBSD.org As of the 5.01 release of ths package, the client libraries for older versions of Elasticsearch have started to be shipped seperately. If you are using this library to access a none 5.X server you will need to install one of the textproc/p5-Search-Elasticsearch-Client-* ports. 20161126: AFFECTS: users of security/gpgme-* AUTHOR: jhale@FreeBSD.org Gpgme has been updated to 1.8.0. With it comes the removal of libgpgme-pthread.so in favor of using libgpgme.so itself as the thread-safe library. Ports that may have linked to -lgpgme-pthread will now just link to -lgpgme. PORTREVISION has been bumped on all ports with a dependency on security/gpgme. The Python module provided by security/py-gpgme has been renamed from pyme3 to gpg, as well. Portmaster users: portmaster -r gpgme Portupgrade users: portupgrade -fr security/gpgme 20161121: AFFECTS: users of graphics/tiff AUTHOR: antoine@FreeBSD.org The tiff port was updated to 4.0.7. The following tools are removed from this release: bmp2tiff, gif2tiff, ras2tiff, rgb2ycbcr and thumbnail. 20161116: AFFECTS: users of sysutils/bareos-* AUTHOR: rand@iteris.com Bareos v1.6.x changed the configuration scheme, from one configuration file per Bareos component (file daemon, storage daemon, and director) to several configuration files, in several directories, for each component. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html The new scheme will use all files named *.conf in the directory hierarchies for each component: /usr/local/etc/bareos/bareos-dir.d/ /usr/local/etc/bareos/bareos-fd.d/ /usr/local/etc/bareos/bareos-sd.d/ To retain the old configuration scheme of one file per component add appropriate lines such as these to your /etc/rc.conf: bareos_dir_config="/usr/local/etc/bareos/bareos-dir.conf" bareos_fd_config="/usr/local/etc/bareos/bareos-fd.conf" bareos_sd_config="/usr/local/etc/bareos/bareos-sd.conf" 20161113: AFFECTS: users of devel/libosinfo AUTHOR: novel@FreeBSD.org The libosinfo port was separated into three different ports to follow the upstream split: - sysutils/osinfo-db-tools: contains the CLI tools - misc/osinfo-db: contains database with OS data - devel/libosinfo: the library As osinfo-db-tools now ships binaries that previously were part of libosinfo, it's required to delete the old libosinfo package to prevent conflict because of same files installation: # pkg delete libosinfo And then install the new version. 20161112: AFFECTS: users of security/heimdal AUTHOR: hrs@FreeBSD.org Heimdal in the base system and security/heimdal <= 1.5.3_6 use Berkeley DB to store principals into /var/heimdal/heimdal.db and the database format is version 3 by default. On the other hand, security/heimdal 1.5.3_7 or newer use the newer version of Berkeley DB and the database format is version 9. These two versions are not compatible with each other. If there is a mismatch between Heimdal utilities and its database format, you will get an error like the following: # /usr/local/sbin/kadmin -l dump BDB0641 __db_meta_setup: /var/heimdal/heimdal.db: unexpected file type or format kadmin: hdb_open: opening /var/heimdal/heimdal: Invalid argument This mismatch can occur in the following three cases: 1. You used Heimdal in the base system and switch to use security/heimdal after creating /var/db/heimdal.db. 2. You used security/heimdal >= 1.5.3_7 and switch to use one in the base system. 3. You used security/heimdal < 1.5.3_7 and upgrade it to 1.5.3_7 or later. To fix this mismatch, you need to dump contents of heimdal.db and rebuild the database by using kadmin(8) utility. If you use Heimdal in the base system or older versions of security/heimdal, and plan to switch to use security/heimdal >= 1.5.3_7, execute the following command *after* creating a backup copy of /var/heimdal and installing security/heimdal: # /usr/bin/kadmin -l dump /var/heimdal/heimdal.db.dump # rm /var/heimdal/heimdal.db # /usr/local/sbin/kadmin -l load /var/heimdal/heimdal.db.dump # rm /var/heimdal/heimdal.db.dump The above example assumes security/heimdal is installed into /usr/local. If your base system is compiled with WITHOUT_KERBEROS use the following instead: # db_dump185-5 /var/heimdal/heimdal.db | db_load-5 /var/heimdal/heimdal.db.new # chown 0600 /var/heimdal/heimdal.db.new # mv /var/heimdal/heimdal.db.new /var/heimdal/heimdal.db db_dump and db_load utilitites are installed by databases/db5 as dependency of security/heimdal. If you want to switch from security/heimdal to Heimdal in the base system, use the following: # /usr/local/sbin/kadmin -l dump /var/heimdal/heimdal.db.dump # rm /var/heimdal/heimdal.db # /usr/bin/kadmin -l load /var/heimdal/heimdal.db.dump # rm /var/heimdal/heimdal.db.dump 20161105: AFFECTS: users of security/heimdal AUTHOR: hrs@FreeBSD.org kadmin(8) in heimdal-1.5.3_5 and prior did not create a database in /var/heimdal in Berkeley DB format which kdc(8) required. This problem has been fixed in heimdal-1.5.3_6. 20161104: AFFECTS: users of mail/mu4e and mail/mu4e-maildirs AUTHOR: hrs@FreeBSD.org The package name of mail/mu4e* have been changed from mu4e* to mu4e*-emacsNN. When upgrading the older versions, this change can cause the following error which prevents it from upgrading: pkg-static: mu4e-emacs25-0.9.16 conflicts with mu4e-0.9.16 (installs files into the same place). If this error occurs, please remove the old packages by using "pkg delete" manually: # pkg delete mu4e-0.9.16 mu4e-maildirs-0.8.20160126_1 20161103: AFFECTS: users of lang/perl5* AUTHOR: mat@FreeBSD.org The default Perl version has been switched to Perl 5.24. If you are using binary packages to upgrade your system, you do not have anything to do, pkg upgrade will do the right thing. For the other people, assuming you are migrating from 5.20 to 5.24, do: First, add to /etc/make.conf: DEFAULT_VERSIONS+= perl5=5.24 Portupgrade users: portupgrade -o lang/perl5.24 -f lang/perl5.20 You can now remove the DEFAULT_VERSIONS line added earlier from /etc/make.conf Then you will need to rebuild everything that uses libperl.so, you can do so with: portupgrade -f `pkg shlib -qR libperl.so.5.20` If, for some reason, this command fails at one point, it is safe to run it again, it will not rebuild what it already rebuilt, as the ports that have been rebuilt no longer depend on libperl.so.5.20 but on libperl.so.5.24. Portmaster users: portmaster -o lang/perl5.24 lang/perl5.20 You can now remove the DEFAULT_VERSIONS line added earlier from /etc/make.conf Then you will need to rebuild everything that uses libperl.so, you can do so with: portmaster -f `pkg shlib -qR libperl.so.5.20` If, for some reason, this command fails at one point, it is safe to run it again, it will not rebuild what it already rebuilt, as the ports that have been rebuilt no longer depend on libperl.so.5.20 but on libperl.so.5.24. 20161102: AFFECTS: users of security/acme-client AUTHOR: brnrd@FreeBSD.org The default configuration paths have changed from 'letsencrypt' to 'acme'. Rename the directories used accordingly mv /usr/local/etc/letsencrypt /usr/local/etc/acme mv /usr/local/etc/ssl/letsencrypt /usr/local/etc/ssl/acme mv /usr/local/www/letsencrypt /usr/local/www/acme Check your scripts to ensure proper operation. 20161030: AFFECTS: users of mail/squirrelmail AUTHOR: adamw@FreeBSD.org For better php70 support, the squirrelmail port has switched from PEAR database access to PDO. If you are using squirrelmail with a database backend, you'll need to install a corresponding PDO database module, such as php56-pdo_sqlite. 20161030: AFFECTS: users of security/srm AUTHOR: rakuco@FreeBSD.org srm has been updated from 1.2.12 to 1.2.15. Since version 1.2.14, srm defaults to using its "simple" mode to overwrite files (one pass writing 0x00 to the files) instead of the 35-pass Gutmann method. 20161029: AFFECTS: users of irc/quassel AUTHOR: woodsb02@FreeBSD.org Quassel is now split into two ports / packages; one for providing the server backend (irc/quassel-core), and one for providing the client front-end (irc/quassel). Alternatively, the irc/quassel port can be built with the MONO option enabled to also install the client and server combined into a single monolithic binary. 20161028: AFFECTS: users of security/openssl and security/openssl-devel AUTHOR: brnrd@FreeBSD.org The shared library versions of OpenSSL have been bumped to avoid issues with ports' and base's OpenSSL not being binary compatible. Please rebuild all ports that depend on OpenSSL if you use OpenSSL from ports. If you use portmaster: portmaster -r openssl If you use portupgrade: portupgrade -fr security/openssl 20161026: AFFECTS: users of net-p2p/deluge AUTHOR: rm@FreeBSD.org Deluge port has been split out onto CLI part and GUI part. So if user only needs deluged, net-p2p/deluge-cli should be installed. For full deluge installation, including GTK+ GUI client, net-p2p/deluge should be installed as a usual. Old deluge package should be removed manually first: # pkg delete deluge After that install preferred deluge package as usual. 20161018: AFFECTS: users of x11/xfce4-terminal AUTHOR: olivierd@FreeBSD.org The port has been updated to the latest stable version 0.8.0. A warning appears each time we open new tab: Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with... This issue will disappear with Gtk > 3.21. 20161014: AFFECTS: users of lang/python3 AUTHOR: antoine@FreeBSD.org The default version of python3 has changed from 3.4 to 3.5. If you wish to stick with older version, add "python3=3.4" to your DEFAULT_VERSIONS variable in /etc/make.conf. To upgrade: If using portupgrade: # portupgrade -o lang/python35 lang/python34 If using portmaster: # portmaster -o lang/python35 lang/python34 20161011: AFFECTS: users of net-im/ejabberd AUTHOR: ashish@FreeBSD.org Before upgrading ejabberd to 16.09, please make sure to backup your ejabberd data using: % sudo -u ejabberd -H ejabberdctl backup /path/to/backup/file In some cases, ejabberd may fail to start, for which a workaround is to remove the schema.DAT file from /var/spool/ejabberd before starting, and then restoring everything from the backup using: % sudo -u ejabberd -H ejabberdctl restore /path/to/backup/file For more details: https://github.com/processone/ejabberd/issues/1305 20161005: AFFECTS: users of audio/squeezeboxserver (now audio/logitechmediaserver) AUTHOR: woodsb02@FreeBSD.org With the rename of the audio/squeezeboxserver port to audio/logitechmediaserver, the server and database are now installed in different locations by default (/usr/local/share/logitechmediaserver and /var/db/logitechmediaserver respectively). If you were an existing user of audio/squeezeboxserver, you should consider backing up you server configuration files and database before upgrading to audio/logitechmediaserver. If you wish to override the default locations for storing the server and database, you can set the SLIMDIR and SLIMDBDIR variables in your /etc/make.conf when building the audio/logitechmediaserver port. 20161004: AFFECTS: mail/roundcube-carddav AUTHOR: gahr@FreeBSD.org There is no upgrade path from the 1.0 version. You'll need to: 1. Log off from Roundcube. 2. Manually drop all carddav_* tables from your db backend. 3. Upgrade the mail/roundcube-carddav port. The new tables will be created upon login. The CardDAV plugin will need to be reconfigured. If you are running php < 7.0.0, you'll need to set the plugin option: $prefs['_GLOBAL']['suppress_version_warning'] = true; See https://github.com/blind-coder/rcmcarddav/issues/165 for details. 20160927: AFFECTS: emulators/ppsspp AUTHOR: jbeich@FreeBSD.org Qt* GUI was split into separate ports: emulators/ppsspp-qt4 emulators/ppsspp-qt5 20160927: AFFECTS: sysutils/android-file-transfer AUTHOR: jbeich@FreeBSD.org Qt* GUI was split into separate ports: sysutils/android-file-transfer-qt4 sysutils/android-file-transfer-qt5 20160922: AFFECTS: users of databases/pglogical, databases/pglogical-output AUTHOR: matthew@FreeBSD.org As of version 1.2.0, databases/pglogical-output has been merged into databases/pglogical. portmaster or portupgrade users should delete pglogical-output manually before upgrading. 20160921: AFFECTS: users of mail/sieve-connect AUTHOR: alexey@renatasystems.org Version 0.88 contains two breaking changes: 1. If the Sieve server does not offer STARTTLS, then connections should now fail. 2. When deriving a remote script name from the local filename, use the basename and strip off directories. For additional information see: http://mail.globnix.net/pipermail/sieve-connect-announce/2016/000012.html 20160919: AFFECTS: users of net/vtun AUTHOR: cy@FreeBSD.org The VTUN_EXTENDED_MODE option has been replaced by -e command line option. 20160914: AFFECTS: users of www/nginx-devel AUTHOR: osa@FreeBSD.org Nginx now creates logs under /var/log/nginx/ and changes default log names from "nginx-access.log" and "nginx-error.log" to "access.log" and "error.log" respectively. This is important for the error log because the location is encoded and touched by nginx during startup regardless of the configured location for the error log. See http://trac.nginx.org/nginx/ticket/147 for additional information on why this happens. 20160914: AFFECTS: users of deskutils/xfce4-volumed-pulse AUTHOR: olivierd@FreeBSD.org The port has been updated to the latest stable version 0.2.2. Support of xfce4-mixer has been removed, so you can delete its properties with the following command: xfconf-query -c xfce4-mixer -p / -rR 20160910: AFFECTS: users of security/letsencrypt.sh AUTHOR: riggs@FreeBSD.org The config filename has been changed upstream from "config.sh" to "config". Users must rename the current config file manually. In addition, the default WELLKNOWN location has been changed to %%PREFIX%%/www/letsencrypt. In order to use the previous default location, the config file must be updated manually as well. 20160907: AFFECTS: users of math/galculator AUTHOR: woodsb02@FreeBSD.org galculator now uses GTK3 by default. An option exists in the port to revert to GTK2 if desired. 20160906: AFFECTS: uses of www/nginx AUTHOR: marino@FreeBSD.org Nginx now creates logs under /var/log/nginx/ and changes default log names from "nginx-access.log" and "nginx-error.log" to "access.log" and "error.log" respectively. This is important for the error log because the location is encoded and touched by nginx during startup regardless of the configured location for the error log. See http://trac.nginx.org/nginx/ticket/147 for additional information on why this happens. 20160905: AFFECTS: users of databases/postgresql96-server AUTHOR: girgen@FreeBSD.org The default unix user used by the PostgreSQL daemon has changed to `postgres' to reflect the long time upstream's convention. Any scripts you have using the old `pgsql' unix user should be modified when upgrading to PostgreSQL version 9.6. Older versions of PostgreSQL will continue using `pgsql' until their end-of-life. For users with UTF-8 locales in the database: The ICU patch is *activated by default* for the PostgreSQL-9.6 server. For previous versions it was optional and default off, but this has changed. Please read the entry here below from 20160811 and understand the consequences of changing between ICU and system locale for database collation (short version: don't). pg_upgrade requires the collation method to be the same (or a reindex), while pg_dump/restore does not. Also, the default home directory for the postgres user is now /var/db/postgres, and the default data directory for PostgreSQL 9.6 is /var/db/postgres/data96. 20160829: AFFECTS: users of x11/nvidia-driver AUTHOR: cem@FreeBSD.org The NVidia driver has been updated to version 367.35. Starting with version 358.09, new kernel module was added, nvidia-modeset.ko. This new driver component works in conjunction with the nvidia.ko kernel module to program the display engine of the GPU. Users that experience hangs when starting X11 server, or observe (II) NVIDIA(0): Validated MetaModes: (II) NVIDIA(0): "NULL" messages in their /var/log/Xorg.0.log file should replace ``nvidia'' with ``nvidia-modeset'' in /boot/loader.conf or /etc/rc.conf files, depending on how they prefer to load NVidia driver kernel module. 20160829: AFFECTS: users of security/sshguard AUTHOR: feld@FreeBSD.org Sshguard has been updated to 1.7.0. There have been several changes to this release. Notably the hosts and ipfilter backends are no longer supported. If you need these backends to be supported and you missed the survey sent out by upstream I urge you to contact upstream. The hosts backend was previously served by security/sshguard directly. The additional backends were slave ports with package name suffixes. I have opted to keep the master/slave port relationship but not choose a specific backend for security/sshguard. Instead it is now a metaport which will prompt you for which backend you prefer. If no backend is configured it will depend on security/sshguard-ipfw, which is the native FreeBSD firewall. This my be surprising to users who depended on security/sshguard which only provided hosts/TCP Wrappers blocking, but there is no replacement at this time. I would also like to document that sshguard no longer accepts the -e argument which allowed external scripts to run when sshguard finds a match. As a result the null backend can no longer be used to create custom blocking functionality; it only serves as a detection backend. If the removed backends return due to user demand they will be added as slave ports for consistency. I apologize for any inconvenience and lack of notice on the deprecation of these features. 20160815: AFFECTS: users of mail/rspamd* AUTHOR: vsevolod@FreeBSD.org Rspamd users should update Rspamd to 1.3.3 version as soon as possible and ensure that '/usr/local/etc/rspamd/module.d/fuzzy_check.conf` has the line `algorithm = "mumhash";` for the "rspamd.com" rule. The more detailed information could be found on https://rspamd.com/announce/2016/08/15/rspamd-1.3.3.html 20160815: AFFECTS: users of dns/powerdns* AUTHOR: junovitch@FreeBSD.org PowerDNS Authoritative Server and Recursor 4.0.0+ introduce significant changes to the configuration files, which need to be handled before restarting the services. As from the Recursor changelog, "The Lua hook infrastructure was redone using LuaWrapper; old scripts will no longer work, but new scripts are easier to write under the new interface." 20160811: AFFECTS: users of security/libressl AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest stable version 2.4 of LibreSSL. The shared library versions of the libraries have been bumped. With this update, the patch for the OPENSSL_VERSION_NUMBER has been removed. This causes issues with a number of ports. Patches for all ports for which this issues is known can be found on https://wiki.freebsd.org/LibreSSL/Ports#OPENSSL_VERSION_NUMBER 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. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl Portupgrade users: portupgrade -fr security/libressl