aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMuhammad Moinur Rahman <bofh@FreeBSD.org>2024-01-03 17:49:10 +0000
committerMuhammad Moinur Rahman <bofh@FreeBSD.org>2024-01-03 17:52:19 +0000
commite83268eaaadc1cca0f2b8d69fd37dc442ed47173 (patch)
tree7e8b127dff372a09ca3253ac4e70b4ce8e47c53d
parent3c70f197cfa8d1232f250c687df419555681860c (diff)
downloadports-e83268eaaadc1cca0f2b8d69fd37dc442ed47173.tar.gz
ports-e83268eaaadc1cca0f2b8d69fd37dc442ed47173.zip
UPDATING: Trim upto stable/13 release
Next trim will happen after 13-STABLE reaches EOL. Approved by: portmgr
-rw-r--r--UPDATING2616
1 files changed, 2 insertions, 2614 deletions
diff --git a/UPDATING b/UPDATING
index 73e767c0806f..ef68f3dd115b 100644
--- a/UPDATING
+++ b/UPDATING
@@ -127,8 +127,7 @@ you update your ports collection, before attempting any port upgrades.
The default Perl version has been switched to Perl 5.36. 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 20181213, it should still be the same.
+ upgrade will do the right thing.
20231014:
AFFECTS: users of security/openssl and security/openssl30
@@ -425,8 +424,7 @@ you update your ports collection, before attempting any port upgrades.
The default Perl version has been switched to Perl 5.34. 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 20181213, it should still be the same.
+ upgrade will do the right thing.
20230726:
AFFECTS: users of misc/openhab
@@ -3009,2613 +3007,3 @@ reinstall the new ones without using the pkg upgrade facility.
# 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 20181213, 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 20181213, 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&section=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=<database> --dbxml=<database>.xml
- - import the database
- cego --mode=xmlimport --tableset=<database> \
- --dbxml=<database>.xml --impfile=export.xml --doLogging
- - modify /etc/rc.conf by adding
- cego_<database>_cpdump="YES"
- cego_<database>_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 <rlwestlund@gmail.com>
-
- 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 <user> <server>
-
-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)://<YourOpenHAB>/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, assuming you are
- migrating from 5.26 to 5.28, do:
-
- First, add to /etc/make.conf:
-
- DEFAULT_VERSIONS+= perl5=5.28
-
- Portupgrade users:
- portupgrade -o lang/perl5.28 -f lang/perl5.26
-
- 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.26`
-
- 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.26 but
- on libperl.so.5.28.
-
- Portmaster users:
- portmaster -o lang/perl5.28 lang/perl5.26
-
- 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 `pkg shlib -qR libperl.so.5.26`
-
- 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.26 but
- on libperl.so.5.28.
-
-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