diff options
| -rw-r--r-- | UPDATING | 2899 |
1 files changed, 0 insertions, 2899 deletions
@@ -5003,2902 +5003,3 @@ leave you without networking. available in devel/pecl-xdebug25 If you're using PHP 7.3, the only compatible xdebug version is available in devel/pecl-xdebug-devel - -20180930: - AFFECTS: users of DRM components - AUTHOR: jmd@FreeBSD.org - - A metaport, graphics/drm-kmod, was introduced for users of both the LinuxKPI- - based DRM components as well as the legacy ones. It is recommended to use the - metaport from now on, which will select a recommended DRM version based on - the FreeBSD version. - -20180924: - AFFECTS: www/libresonic-standalone - AUTHOR: jlh@FreeBSD.org - - HTTPS support has been removed from the port, as it will be removed upstream: - https://github.com/Libresonic/libresonic/issues/125#issuecomment-256227104 - - In order to avoid strange behavior for users who are using this feature, the - rc.d script will fail fast if libresonic_ssl="YES". You should remove the - following variables from rc.conf(5): libresonic_ssl libresonic_ssl_keystore - libresonic_ssl_password. - - # sed -i '' /libresonic_ssl/d /etc/rc.conf - - Users needing SSL are encouraged to use an HTTP reverse-proxy. Example - configurations can be found here: - https://github.com/Libresonic/libresonic/issues/119 - -20180922: - AFFECTS: users of graphics/ilmbase, graphics/OpenEXR - AUTHOR: mandree@FreeBSD.org - - The IlmBase package has been updated to 2.3.0. - The OpenEXR package has been renamed to openexr and updated to 2.3.0. - - The PORTREVISION of all ports requiring either has been bumped to - ease the rebuilds, and where there were versions in the file names, - these have been removed from the *_DEPENDS lines for easier maintenance. - - A full ports or package upgrade should just work. - - If you are doing partial updates, be sure to rebuild and reinstall - all packages that require either of OpenEXR or ilmbase. - Normally, these can be listed by running: - - # pkg info -q -r OpenEXR ilmbase | sort -u | xargs pkg info -q -o - -20180905: - AFFECTS: users of lang/php56 - AUTHOR: tz@FreeBSD.org - - The default version of PHP has been switched from 5.6 to 7.1. - - If you use binary packages you should make a list of php packages - before running 'pkg upgrade': - - # pkg info php5\* > ~/installed-php-ports-list - - After the upgrade, check with such list if all your php extensions - are still installed, and reinstall them if needed. - - If you use mod_php56 you need to deinstall it and install mod_php71. - -20180901: - AFFECTS: net/samba48 - AUTHOR: timur@FreeBSD.org - - Samba ports from now on are not dependent from the databases/ldb* ports, - as the link between Samba and LDB is too tight and each next major Samba - release requires it's own major LDB release. Please, remove installed - version of databases/ldb13 from your system with: - - # pkg delete -f databases/ldb13 - -20180901: - AFFECTS: net-mgmt/librenms - AUTHOR: dvl@FreeBSD.org - - As of version 1.42, to conform with man hier, logs and rrd files have - relocated outside the WWW directory. When upgrading from < 1.42 to more - recent versions, the following steps are required. - - You must update config.php and manually relocate the rrd and log files. - Before upgrading, please stop librenms, update the configuration, and - relocate the files. - - If you find graphs are not updating, fping >= 4.0 requires an IPv6 - address. Adding an IPv6 address should fix graphing. - - Please add these entries to config.php: - - $config['installed_from_package'] = true; - $config['log_dir'] = '/var/log/librenms'; - $config['rrd_dir'] = '/var/db/librenms/rrd'; - - To relocate the files: - - mkdir /var/log/librenms /var/db/librenms - chown www:ww: /var/log/librenms /var/db/librenms - cd /usr/local/www/librenms - mv rrd /var/db/librenms/ - mv logs/librenms.log /var/log/librenms/ - rmdir logs - - An application key is required. Please follow these steps to generate it: - - cd /usr/local/www/librenms - cp -i .env.sample .env - - You might need to set your database details in that file. - Then run: - - php artisan key:generate - - The output should look something like this: - - ************************************** - * Application In Production! * - ************************************** - - Do you really wish to run this command? (yes/no) [no]: - > y - - Application key [base64:P62La9V........qw=] set successfully. - -20180901: - AFFECTS: users of samba46 - AUTHOR: antoine@FreeBSD.org - - The default version of samba has been switched from 4.6 to 4.7. - Upgrade instructions: - - For package users having samba46 installed indirectly (as a dependency): - # pkg upgrade - - For package users having samba46 installed directly (leaf port): - # pkg upgrade - # pkg install samba47 - - For ports users: - If you want to keep samba46, add DEFAULT_VERSIONS+= samba=4.6 to make.conf - - If you want to upgrade to samba47, remove samba46: - # pkg delete -f samba46 - - Portmaster users: - # portmaster net/samba47 - # portmaster -a - - Portupgrade users: - # portinstall net/samba47 - # portupgrade -a - -20180813: - AFFECTS: net/geoipupdate - AUTHOR: adamw@FreeBSD.org - - There have been some breaking changes to the GeoIP.conf in version 3.0.0. - Read about the changes at - https://github.com/maxmind/geoipupdate/blob/master/ChangeLog.md - and either edit your GeoIP.conf as needed, or recreate it from - GeoIP.conf.sample. - -20180810: - AFFECTS: databases/postgresql??-server - AUTHOR: girgen@FreeBSD.org - - The PostgreSQL server packages are no longer built with support for the XML - datatype per default. To retain support for the XML datatype you should build - the port and check the XML option in the option dialog. The reason for this - is the bad security reputation of libxml2. - -20180806: - AFFECTS: www/tt-rss - AUTHOR: thierry@FreeBSD.org - - tt-rss now uses pdo_mysql/pgsql for database access; a web server reload - will be required if pdo ext. isn't installed. - -20180804: - AFFECTS: net-mgmt/zabbix*-server - AUTHOR: dbaio@FreeBSD.org - - The JAVAGW option was removed from the Zabbix Server and an additional slave - port was created, zabbix*-java, it installs only Zabbix Java Gateway files, - this way is possible to deploy a Zabbix Java Gateway without the need to - install Zabbix Server components. - - If you are using the JAVAGW option on Zabbix Server, please, install now the - new zabbix*-java port. - -20180803 - AFFECTS: users of net/openntpd - AUTHOR: naddy@FreeBSD.org - - The numerical ID of the "_ntp" user had to be moved after 12.0-CURRENT - (revision 336525) took over its value for a user "ntpd" that uses a - different privilege model. - - To avoid clashes between the two users, please remove the openntpd - package, delete the old UID with - - # pw userdel _ntp - - and re-install openntpd. - -20180731: - AFFECTS: users of audio/sndio - AUTHOR: tobik@FreeBSD.org - - sndiod(8) will now use the default audio device /dev/dsp instead - of /dev/dsp0 if no device was specified. - - The location of ~/.aucat_cookie has moved to ~/.sndio/cookie. If - you share audio devices via sndiod(8) on the network or between - local users, please migrate it manually to the new location to - guarantee a smooth upgrade. - -20180731: - AFFECTS: users of x11/xorg and all ports with USE_XORG=*proto - AUTHOR: zeising@FreeBSD.org - - The xorg *proto packages have all been merged into one package, - x11/xorgproto. This might cause issues with upgrading. If you - get conflicts between xorgproto and old *proto packages, please - remove the old package and install xorgproto again. - - In order to remove all orphaned ports, including all *proto port, - the following can be used after the ports tree has been updated: - pkg version -l \? | cut -f 1 -w | grep -v compat | xargs pkg delete -fy - -20180728: - AFFECTS: users who upgrade from security/kc to security/kc24 - AUTHOR: pi@FreeBSD.org - - The ondisk format changes from kc 2.3 to kc 2.4, so please - read the kc24 pkg-message file before the upgrade. It describes - how to create a backup, the xml dump and how to import the - xml dump afterwards. - -20180725: - AFFECTS: users of textproc/ibus-typing-booster - AUTHOR: thierry@FreeBSD.org - - Due to a migration from IBusConfig to GSettings, the old settings are - unfortunately lost, so one has to open the setup tool and recreate ones - favourite settings. - -20180714: - AFFECTS: users of dns/dnsdist - AUTHOR: cpm@FreeBSD.org - - After discussing with several users, we noticed that quite a lot of them - were not aware that enabling the dnsdist's console without a key, even - restricted to the local host, could be a security issue and allow privilege - escalation by allowing an unprivileged user to connect to the console and - execute Lua code as the dnsdist user. We therefore decided to refuse any - connection to the console until a key has been set, so please check that - you do set a key before upgrading if you use the console. - - For further details read: - https://blog.powerdns.com/2018/07/10/dnsdist-1-3-2-released/ - -20180704: - AFFECTS: users of www/gitlab - AUTHOR: mfechner@FreeBSD.org - - The gitlab port uses the package from gitlab.org instead of github.org. - For this the port was renamed from gitlab to gitlab-ce. - Please follow the instructions very carefully to not lose your data! - Not only the package was renamed, also the directory name changed. - - You can find the current instruction here: - https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/10.8-11.0-freebsd.md - - Please note the update was only tested for an update from 10.8.5 to 11.0.2. - If your version of gitlab was released before 2014-03-13 you cannot update - to this version. You need to make an intermediate update to an earlier - version before. - -20180701: - AFFECTS: users of devel/bats - AUTHOR: lifanov@FreeBSD.org - - The devel/bats port has been renamed to devel/bats-core to match the - new upstream project. - -20180630: - AFFECTS: users of net-im/ejabberd - AUTHOR: ashish@FreeBSD.org - - In version 18.06, upstream has removed support for IRC transport. - -20180625: - AFFECTS: users of PHP based applications like drush - AUTHOR: mfechner@FreeBSD.org - - Flavors are being added to PHP applications. If you use PHP 5.6 you need: - - # pkg set -n drush:drush-php56 - - For more details see 20180611. - -20180612: - AFFECTS: users of the nox flavor of editors/emacs-devel - AUTHOR: jrm@FreeBSD.org - - The package name for the nox flavor of editors/emacs-devel changed from - emacs-devel_nox to emacs-devel-nox. To install the new package, run - - # pkg install emacs-devel-nox - - pkg should remove the old and install the new package. - -20180612: - AFFECTS: users of packages that depend on Emacs - AUTHOR: jrm@FreeBSD.org - - With the release of Emacs version 26.1, the major version of editors/emacs - changed from 25 to 26, so the names of packages that depend on Emacs have also - changed. For example, pdf-tools-emacs25-0.80.79_1 is now called - pdf-tools-emacs26-0.80.79_1. The name change means simply running `pkg - upgrade` will not upgrade foo-emacs25-x to foo-emacs26-x. - - To list the packages to upgrade, use - - # pkg info \*emacs25\* - - then install the new version for each with - - # pkg install foo-emacs26 - - pkg should remove the old and install the new packages. - -20180611: - AFFECTS: users of PHP based applications - AUTHOR: mat@FreeBSD.org - - Flavors are being added to PHP applications. When a port is flavorized, pkg - needs to be told about the name change, for example, if PHP 5.6 is the one - you need: - - # pkg set -n squirrelmail:squirrelmail-php56 - - Most port will have packages for all PHP versions present in the ports tree, - but some may not be compatible with a specific version. - - To get the available flavors, pkg rquery can be used: - - # pkg rquery %n mail/squirrelmail - squirrelmail-php56 - squirrelmail-php70 - squirrelmail-php71 - squirrelmail-php72 - -20180602: - AFFECTS: users of net/frr - AUTHOR: olivier@FreeBSD.org - - Due to regression detected in FRR version 4.0, port was renamed to frr4 - to prepare re-introduction of frr3 port version. - - To rename the installed package to match the new naming scheme, run: - # pkg set -n frr:frr4 - -20180529: - AFFECTS: users of textproc/ibus-typing-booster - AUTHOR: thierry@FreeBSD.org - - Attention, this release merges all engines into one. Therefore, the - engine names had to change. The old engine names like "German - DE - (Typing Booster)", "Hindi - HI (Typing Booster)" don't exist anymore! - If one has entries for them in the Gnome Control Center or in - ibus-setup, one needs to remove these old entries and add the new - engine name "Other (Typing Booster)". - -20180518: - AFFECTS: users of sysutils/ansible* - AUTHOR: lifanov@FreeBSD.org - - Ansible ports are now flavored. Package names for Ansible changed - to include python version. Poudriere and package users don't need - to do anything. - - To rename an installed package to match the new naming scheme, - for example, for ansible24, run: - - # pkg set -n ansible24:py27-ansible24 - -20180514: - AFFECTS: users of www/gitlab - AUTHOR: mfechner@FreeBSD.org - - Gitlab-pages support was removed as new version does not compile. - If you require gitlab-pages do not update to version 10.7.3 till it is - fixed upstream. - You can find the bug report here: - https://gitlab.com/gitlab-org/gitlab-pages/issues/143 - -20180513: - AFFECTS: users of net/xrdp - AUTHOR: meta@FreeBSD.org - - net/xrdp has been updated from 0.6.2 to 0.9.6. There are significant - changes between these versions. You should consider backing up your - configuration files such as xrdp.ini and sesman.ini, and then migrate - configuration files by hand. - - Regarding km-*.ini, don't use the old files. They can be safely replaced - with new ones. - -20180507: - AFFECTS: users of math/suitesparse who build it locally - AUTHOR: yuri@FreeBSD.org - - The suitesparse needs to be uninstalled before math/suitesparse can be - correctly built. This is true for the version 5.2.0 and prior versions. - -20180505: - AFFECTS: users of www/gitea - AUTHOR: stb@lassitu.de - - The www/gitea port no longer requires shell/bash. If you want to - stop using bash and deinstall the package, make sure to set the - configuration in etc/gitea/conf/app.ini, section [repository], - SCRIPT_TYPE to "sh". See app.ini.sample for an example. - -20180501: - AFFECTS: users of www/node - AUTHOR: bhughes@FreeBSD.org - - The www/node port has been updated to Node.js v10.0.0, the latest - upstream release. This is a major release, including many significant - changes. Users are encouraged to read the release announcements before - upgrading: - - https://nodejs.org/en/blog/release/v10.0.0/ - - In particular, Node.js now depends on OpenSSL 1.1.0h, so the - BUNDLED_SSL option is enabled by default. Users can disable this - option when using security/openssl-devel as their default SSL library. - -20180430: - AFFECTS: users of news/nntp - AUTHOR: dinoex@FreeBSD.org - - The option INETD was removed. If you used inetd, please change the path - in /etc/inetd.conf from /usr/local/sbin/nntpd to /usr/local/libexec/nntpd. - -20180428: - AFFECTS: users of security/libressl - AUTHOR: brnrd@FreeBSD.org - - The port has been updated to the latest stable version 2.7 of LibreSSL. - The shared library versions of the libraries have been bumped. - - After upgrading, manually update all packages that depend on any of the - libraries provided by LibreSSL (libssl, libcrypto and libtls) since the - versions of these libraries have changed. Normally, you can obtain the - list of dependent software by running the following command: - - # pkg info -r libressl - - Then you should rebuild all ports depending on libressl to avoid dangling - shared library dependencies. Poudriere and pkg handle this correctly, - portmaster and portupgrade users can use the following to rebuild all - dependent ports. - - Portmaster users: - portmaster -r libressl - Portupgrade users: - portupgrade -fr security/libressl - -20180427: - AFFECTS: users of sysutils/zrepl - AUTHOR: woodsb02@FreeBSD.org - - The zrepl update to 0.0.3 includes the following breaking changes: - - Snapshots are automatically bookmarked and pruning of bookmarks must - be configured by adding the keep_bookmarks parameter to the prune - policy section of the zrepl configuration file (source side only). - Be sure to understand the meaning bookmarks have for maximum - allowable replication downtime. - - The ssh+stdinserver transport protocol has changed, requiring zrepl - to be updates on both the sending and receiving side, and the daemon - restarted on both sides. - - The first outlet in the global.logging section of the configuration - file is now used for logging meta-errors (e.g. problems encountered - when writing to other logging outlets). - -20180425: - AFFECTS: users of databases/pecl-redis - AUTHOR: daniel@blodan.se - - pecl-redis 4.0.0 breaks backwards compatibility, users - not aware if you are using the changed functionality or not - should swap to databases/pecl-redis3 - -20180417: - AFFECTS: users of dns/dnscrypt-proxy2 - AUTHOR: egypcio@googlemail.com - - DNSCrypt-Proxy 2 has been updated to 2.0.10 and the configuration file - has changed from ${PREFIX}/etc/dnscrypt-proxy.toml to - ${PREFIX}/etc/dnscrypt-proxy/dnscrypt-proxy.toml. - -20180416: - AFFECTS: users of mail/postgrey - AUTHOR: ports.maintainer@evilphi.com - - If you use any of the optional make.conf variables to specify the - postgrey user, group, db dir, or run dir when building the port, you will - need to change the prefix from PG_ to POSTGREY_*. The variables were - renamed to solve a namespace collision with the PostgreSQL ports. - -20180412: - AFFECTS: users of devel/php-composer - AUTHOR: madpilot@FreeBSD.org - - Flavors have been added to the composer port with the update to - 1.6.3. Due to the change in PKGNAME pkg(and other tools) will not - notice the update. It is required to tell pkg about the name - change, for example: - - # pkg set -n php-composer:php56-composer - -20180410: - AFFECTS: users of KDE SC4 - AUTHOR: kde@FreeBSD.org - - Most of KDE Applications 17.12.3 have now landed in the ports tree. - There are still some missing pieces, that will follow soon. - - As mentioned in the commit messages, users of KDE SC4 should stick with the - <foo>-kde4 named package. - - As the MOVED entries for ports like databases/akonadi-kde4 have been removed - in the process of updating (as there now is again a databases/akonad), there - might be issues for people that update from a too old installed package list - with portmaster. - - These should be fixable by issuing a command à la - # pkg set --change-origin databases/akonadi:databases/akonadi-kde4 akonadi - -20180409: - AFFECTS: users of net-im/matterircd - AUTHOR: norrland@nullbyte.se - - Matterircd has been updated to 0.17.0 and mattermost configuration settings - need to be migrated to [mattermost] section. See matterircd.toml.sample. - -20180404: - AFFECTS: users of www/nextcloud - AUTHOR: brnrd@FreeBSD.org - - With the 13.0.1 update the path for Apps bundled with the package has - changed from "apps" to "apps-pkg". You must add an entry to the - "apps_paths" array in config/config.php of your nextcloud installation, - a patch for the default installation can be applied with: - - # cd /usr/local/www/nextcloud - # su -m www -c "php ./occ config:import < /usr/local/share/nextcloud/fix-apps_paths.json" - -20180401: - AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole - AUTHOR: adamw@FreeBSD.org - - Dovecot has been upgraded to 2.3.1, and pigeonhole to 0.5.1. Most - existing dovecot installations MUST be modified for 2.3, but for - most users the modifications are simple. - - Modify your Dovecot conf.d/ files before spinning up 2.3.1. The - upgrading instructions are detailed here: - - https://wiki2.dovecot.org/Upgrading/2.3 - -20180330: - AFFECTS: users of lang/perl5* - AUTHOR: mat@FreeBSD.org - - The default Perl version has been switched to Perl 5.26. If you are using - binary packages to upgrade your system, you do not have anything to do, pkg - upgrade will do the right thing. For the other people, follow the - instructions in entry 20161103, it should still be the same. - -20180325: - AFFECTS: users of net/samba48 - AUTHOR: timur@FreeBSD.org - - New Samba 4.8 upgrades the relevant database files in the way, that doesn't - allow easy fallback to the previous versions of Samba. So, before upgrading - to the new version make a backup of the /var/db/samba4/ directory. - - Full list of changes, new features and upgrade procedure is available at: - - https://www.samba.org/samba/history/samba-4.8.0.html - - Please, read it carefully before upgrading!. - -20180320: - AFFECTS: users of x11/sterm - AUTHOR: pkubaj@anongoth.pl - - The user-defined options in config.h have changed. You should - compare your config.h file with the default one and change - appropriately. - -20180319: - AFFECTS: users of dns/dnsmasq - AUTHOR: mandree@FreeBSD.org - - Note that with dnsmasq 2.79, some parts of the interface have changed in an - incompatible way versus previous versions. This comprises changed recursion - behaviour, signature support, a change for SIGINT (vs. SIGHUP) behaviour. - - Note especially that dnsmasq will no longer answer non-recursive queries - unless it is marked authoritative! Be sure to see the manual page for the - various --auth-* options, such as --auth-zone. - - Please see the CHANGELOG that ships with dnsmasq for details. - -20180317: - AFFECTS: users of multimedia/plexpy - AUTHOR: feld@FreeBSD.org - - Plexpy project has been renamed to Tautulli due to copyright - infringement. The software also has received a major update. Please - see the following upgrade instructions: - - - Install multimedia/tautulli - - Create /var/db/tautulli, owned by the user you will run the daemon as - (default: nobody). - - Copy your config.ini and plexpy.db to /var/db/tautulli - - Enable the service and start the software - - Tautulli should automatically find your database file, rename it to - tautulli.db, and perform the required updates. - -20180310: - AFFECTS: users of security/openssl - AUTHOR: brnrd@FreeBSD.org - - The EXPCIPHERS option has been removed from the security/openssl port. - Use the security/openssl-unsafe port if you require this feature. - -20180309: - AFFECTS: users of net/unison - AUTHOR: madpilot@FreeBSD.org - - Unison has been upgraded to version 2.51, which uses a different - wire protocol than 2.48 did. In order to support synchronization - with other computers where Unison is still at version 2.48, a new - port net/unison248 has been created. It provides unison248 and, - for the x11 flavor, also unison248-text. This unison248 port can - be installed in parallel with the existing net/unison port. - -20180308: - AFFECTS: */php* */pecl* */pear* - AUTHOR: mat@FreeBSD.org - - PHP extensions and modules have been flavored. - - People using Poudriere 3.2+ and binary packages do not have to do anything if - they are using PHP applications. - - PHP modules and extensions may have change their names from php5- or php7- to - fully versionned phpXY-. - PECL extensions and PEAR modules package names have changed from pecl- and - pear- to phpXX-pecl and phpXX-pear-. - - To rename an installed package to match the new naming scheme, for example, - for the imagick pecl extension, run: - - # pkg set -n pecl-imagick:php56-pecl-imagick - - For other people, to build the PHP 7.2 version of, for example, - databases/php-memcached, you need to run: - - # make FLAVOR=php72 install - -20180220: - AFFECTS: users of www/nextcloud - AUTHOR: brnrd@FreeBSD.org - - The file and directory permissions of Nextcloud have changed. Write - permissions have been removed from all directories except `data' and - `config'. For the updater to work, the app store of your installation - must be disabled. To disable the app-store prior to updating the - package: - - # cd /usr/local/www/nextcloud - # su -m www -c "php ./occ config:system:set appstoreenabled --value=false --type=boolean" - - If you've already updated your nextcloud package, you must manually edit - the configuration of nextcloud (config/config.php) and add - - 'appstoreenabled' => false, - - to the CONFIG array before the updater will run. - -20180214: - AFFECTS: users of lang/ruby23 - AUTHOR: swills@FreeBSD.org - - The default ruby version has been updated from 2.3 to 2.4. - - If you compile your own ports you may keep 2.3 as the default version by - adding the following lines to your /etc/make.conf file: - - # - # Keep ruby 2.3 as default version - # - DEFAULT_VERSIONS+=ruby=2.3 - - If you wish to update to the new default version, you need to first stop any - software that uses ruby. Then, you will need to follow these steps, depending - upon how you manage your system. - - If you use pkgng, simply upgrade: - # pkg upgrade - - If you use portmaster, install new ruby, then rebuild all ports that depend - on ruby: - # portmaster -o lang/ruby24 lang/ruby23 - # portmaster -R -r ruby-2.4 - - If you use portupgrade, install new ruby, then rebuild all ports that depend - on ruby: - - # pkg delete -f ruby portupgrade - # make -C /usr/ports/ports-mgmt/portupgrade install clean - # pkg set -o lang/ruby23:lang/ruby24 - # portupgrade -x ruby-2.4.\* -fr lang/ruby24 - -20180209: - AFFECTS: users of japanese/lookup - AUTHOR: yasu@utahime.org - - japanese/lookup is update to 1.99.96.20130920. This version is not - compatible with previous version 1.4.1 and incompatibility includes - how to setup. See info of Lookup for detail. - -20180209: - AFFECTS: users of net-mgmt/pmacct - AUTHOR: pi@FreeBSD.org - - To allow separate pmacctd instances per interface, use - - pmacctd_enable="YES" - pmacctd_interfaces="re1 re2" - - in /etc/rc.conf. The path to the config files will be - - /usr/local/etc/pmacct/<interface> - -20180208: - AFFECTS: users of mail/mailman* - AUTHOR: mandree@FreeBSD.org - - In order to overcome complaints about mismatched checksums in - Mailman/Default.py, mailman now configures the DEFAULT_EMAIL_HOST - and DEFAULT_URL_HOST to "localhost" statically, and the rc script - will check this and refuse to start on next boot. - - Users must configure DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in - Mailman/mm_cfg.py properly and add this line below: - add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) - - A short example has been added to: - ${PREFIX}/local/share/doc/mailman/FreeBSD-post-install-notes. - - As of 2.1.26_3, the post-install script will add back the prior - default settings to mm_cfg.py (instead of Defaults.py) if no - virtual hosts have been defined, to cover the normal use cases - and initial installation. - -20180201: - AFFECTS: users of editors/emacs* and all ports using Emacs via USES=emacs - AUTHOR: jrm@FreeBSD.org - - The Emacs ports framework has been updated to support flavors and the - editors/emacs-nox11 port has been replaced by the nox flavors of - editors/emacs and editors/emacs-devel. - - Supported Flavors - -------------------------------------------------------- - editors/emacs: full canna nox - editors/emacs-devel: full nox - ports using Emacs: full canna nox devel_full devel_nox - -------------------------------------------------------- - - For those using pre-built packages, if - - # pkg upgrade - - does not install the new Emacs package, use one of - - # pkg install emacs - # pkg install emacs-canna - # pkg install emacs-nox - # pkg install emacs-devel - # pkg install emacs-devel-nox - - For those building their own packages, a flavor other than the default must be - specified. For example, to build the nox flavor of editors/emacs, or to build - the devel_full flavor of a port using Emacs, use - - # poudriere bulk -j 11amd64 editors/emacs@nox - # poudriere bulk -j 11amd64 print/pdf-tools@devel_full - - or - - # make FLAVOR=nox install - # make FLAVOR=devel_full - - An alternative to the default flavor, full, for editors/emacs and - editors/emacs-devel can be set in make.conf. For example, to specify nox as - the default flavor for both ports, use - - .if ${.CURDIR:M*/editors/emacs*} - FLAVOR?=nox - .endif - - For ports using Emacs, an alternative to the default flavor, full, - can be also be set in make.conf. For example, to automatically depend on - emacs-nox, use - - DEFAULT_VERSIONS+=emacs=nox - -20180117: - AFFECTS: users of x11-toolkits/kf5-kirigami2 and x11/kf5-plasma-framework - AUTHOR: kde@FreeBSD.org - - Files that were previously installed by kf5-kirigami2 are now installed - by kf5-plasma-framework. This can lead to a conflict during the upgrade - of the packages. - It is recommended to first remove the package kf5-kirigami2. - -20180115: - AFFECTS: users of net-p2p/transmission-daemon - AUTHOR: woodsb02@FreeBSD.org - - The transmission-daemon port has been updated to 2.92_4 to incorporate - a patch which mitigates DNS rebinding attacks. This will prevent - clients from being able to connect to the transmission daemon using - DNS with any hostname other than localhost, unless one of the - following is done: - - Enable password authentication, then any hostname is allowed. - This can be achieved by either: - - setting rpc-authentication-required to true, and adding - credentials to the rpc-username and rpc-password fields in - settings.json (must be done whilst the transmission service is - stopped); or - - running transmission-daemon with the following arguments - (these can be set with transmission_flags in /etc/rc.conf): - -t -u USERNAME -v PASSWORD - OR - - Add the allowed server hostnames to the rpc-host-whitelist setting - in settings.json (must be done whilst the transmission service is - stopped). Note that this value is NOT a list of allowed CLIENTS, - but instead a list of allowed SERVER hostnames. - -20180111: - AFFECTS: users of editors/vim-lite - AUTHOR: adamw@FreeBSD.org - - The vim-lite port has been renamed to vim-console, because it isn't - actually any lighter. All three vim packages are built with - --enable-features=huge. Portmaster users will need to run this - command: - - portmaster -o editors/vim-console editors/vim-lite - - If the switch doesn't happen automatically for you, just delete the - vim-lite package and install vim-console. - -20180109: - AFFECTS: users of www/qt5-webengine - AUTHOR: kde@FreeBSD.org - - The upgrade of www/qt5-webengine to 5.9.3 may fail if an older version - of it is installed. It is recommended to either build the port in a - builder like poudriere, or to deinstall and then doing an install. - -20180107: - AFFECTS: users of security/gnupg and mail/mutt and mail/neomutt - AUTHOR: adamw@FreeBSD.org - - The invocation for gpg from mutt/neomutt changed between gnupg-2.0 - (which has expired and is now removed) and gnupg-2.2 (the current - version in the tree). Unless you're using gpgme, PGP-related - commands may fail in (neo)mutt. - - In all cases, users are strongly urged to use security/gpgme to take - care of the setup for you. If you prefer to roll your own, the - following muttrc/neomuttrc entry has been reported to work: - - pgp_decrypt_command="gpg2 %?p?--passphrase-fd 0 --pinentry-mode=loopback? --no-verbose --batch --output - %f" - - See muttrc(5), neomuttrc(5), mutt.org, and neomutt.org for instructions - on (neo)mutt's gpg and gpgme instructions. - -20180102: - AFFECTS: users of devel/awscli - AUTHOR: bhughes@FreeBSD.org - - The package name for devel/awscli has changed (back) to just awscli. - The introduction of flavors erroneously caused the awscli package to - be renamed to py27-awscli. - -20171230: - AFFECTS: users of net-im/ejabberd - AUTHOR: ashish@FreeBSD.org - - If you are building ejabberd 17.11 on a host, which already has an older - version of ejabberd installed, then build process will fail with "unknown type - specifier" errors. As a workaround, please uninstall ejabberd before building - ejabberd. - - This has been reported upstream at: - https://github.com/processone/ejabberd/issues/2194 - -20171223: - AFFECTS: users of dns/dnscrypt-proxy - AUTHOR: egypcio@googlemail.com - - The 1.9.5_3 update of dns/dnscrypt-proxy replaces the default resolver used - by dnscrypt-proxy (cisco/OpenDNS) by a random one that does not log entries - and supports dnssec. - -20171223: - AFFECTS: users of samba44 - AUTHOR: antoine@FreeBSD.org - - The default version of samba has been switched from 4.4 to 4.6. - Upgrade instructions: - - For package users having samba44 installed indirectly (as a dependency): - # pkg upgrade - - For package users having samba44 installed directly (leaf port): - # pkg upgrade - # pkg install samba46 - - For ports users: - If you want to keep samba44, add DEFAULT_VERSIONS+= samba=4.4 to make.conf - - If you want to upgrade to samba46, remove samba44: - # pkg delete -f samba44 - - Portmaster users: - # portmaster net/samba46 - # portmaster -a - - Portupgrade users: - # portinstall net/samba46 - # portupgrade -a - -20171218: - AFFECTS: users of devel/gogs - AUTHOR: dg@syrec.org - - Gogs user has been changed to "git" and configuration files are now - located in /usr/local/etc/gogs. Users should update ownership of the - existing Gogs directories with - - # chown -R git:git /var/db/gogs - # chown -R git:git /var/log/gogs - - and either move or merge the contents of /var/db/gogs/home/.ssh with - /usr/local/git/.ssh. After migration, /var/db/gogs/home can be removed, - and both the user "gogs" and the group "gogs" should be deleted: - - # rm -rf /var/db/gogs/home - # pw userdel gogs - # pw groupdel gogs - -20171215: - AFFECTS: users of finance/gnucash - AUTHOR: madpilot@FreeBSD.org - - The gnucash port has been converted too use flavors, the GUILE1 - and GUILE2 options have been converted to flavors so that two - separate packages can be provided. - - Since the next major release of gnucash will drop guile1 support, - the default flavor package is compiled against guile2, switching - the previous default. - - Users who intend to stay on the guile1 version should deinstall - the default gnucash package and install the gnucash-guile1 package. - -20171214: - AFFECTS: all ports users - AUTHOR: adamw@FreeBSD.org - - Support for some deprecated variables is going to be removed soon. If - you use any of the following constructs (usually in /etc/make.conf), - you must switch to the new incantations: - - OLD NEW - ------------------------------- ------------------------------ - WITH_[...] OPTIONS_SET= [...] - WITHOUT_[...] OPTIONS_UNSET= [...] - WITHOUT_NLS OPTIONS_UNSET= NLS - NOPORTDOCS OPTIONS_UNSET= DOCS - NOPORTEXAMPLES OPTIONS_UNSET= EXAMPLES - WITH_BDB_VER=[...] DEFAULT_VERSIONS+= bdb=[...] - OVERRIDE_LINUX_BASE_PORT=[...] DEFAULT_VERSIONS+= linux=[...] - WITH_OPENSSL_BASE DEFAULT_VERSIONS+= ssl=base - WITH_OPENSSL_PORT DEFAULT_VERSIONS+= ssl=port - -20171205: - AFFECTS: users of dns/powerdns - AUTHOR: krion@FreeBSD.org - - Recursor passthrough removal: This will impact many installations. - Previously, the PowerDNS Authoritative Server contained a facility - for sending recursion desired queries to a resolving backend, - possibly after first consulting its local cache. This feature - (‘recursor=’) was frequently confusing and also delivered - inconsistent results, for example when a query ended up referring - to a CNAME that was outside of the Authoritative Server’s - knowledge. - -20171203: - AFFECTS: users of sysutils/dsbmd - AUTHOR: mk@freeshell.de - - Due to new configuration variables and new features, users of dsbmd - version 0.4.1 and earlier should consider recreating their dsbmd.conf from - the new dsbmd.conf.sample. - -20171130: - AFFECTS: all ports users - AUTHOR: adamw@FreeBSD.org - - The ports tree has gained "flavors," which are a way to produce multiple - variations of a port. Some intended examples of this are language - modules being produced for multiple language versions, and lite/nox11 packages, - without needing separate ports for each variation. Python ports have already - been flavored (see the below entry). Flavor support must be added to - individual ports. - - Flavors are already supported by make, pkg, poudriere, and synth; see the - manpages for those tools for usage instructions. Portmaster and portupgrade - don't support flavors yet, but community work on those tools is in progress. - - Some bumps and breakages are inevitable for a major change such as this. - Please report breakages and monitor the ports@ list for solutions as they - become available. - -20171130: - AFFECTS: */py* - AUTHOR: mat@FreeBSD.org - - Ports using Python via USES=python are now flavored. All the py3-* ports - have been removed and folded into their py-* master ports. - - People using Poudriere 3.2+ and binary packages do not have to do anything. - - For other people, to build the Python 3.6 version of, for example, - databases/py-gdbm, you need to run: - - # make FLAVOR=py36 install - -20171126: - AFFECTS: users of security/p5-openxpki - AUTHOR: dbaio@FreeBSD.org - - OpenXPKI has been updated to 1.19.4, some important changes were made, please - see the upgrading documentation for more details: - - http://openxpki.readthedocs.io/en/latest/upgrading.html - -20171126: - AFFECTS: users of mail/sympa - AUTHOR: dgeo@centrale-marseille.fr - - Web's static dirs have moved to a single dedicated directory. - Users should review webserver's /static configuration (examples in - share/examples/sympa). - -20171119: - AFFECTS: users of sysutils/zrepl - AUTHOR: woodsb02@FreeBSD.org - - Zrepl has been updated to 0.0.2, which introduces two changes that will - require existing users to change their zrepl.yml config file: - - global.logging is no longer a dictionary but a list. - Refer to the new format here: https://zrepl.github.io/configuration/logging.html - - source job field datasets renamed to filesystems. - Refer to the new format here: https://zrepl.github.io/configuration/jobs.html - - https://zrepl.github.io/changelog.html#id1 - -20171117: - AFFECTS: users of sysutils/terraform - AUTHOR: lifanov@FreeBSD.org - - Terraform has been updated to 0.11, which introduces several incompatible - changes. Please follow upgrading guide when updating the package. - - https://www.terraform.io/upgrade-guides/0-11.html - -20171114: - AFFECTS: users of ports-mgmt/poudriere - AUTHOR: bdrewery@FreeBSD.org - - "poudriere options" now respects the -p flag while it did not before. - This means that it may create an empty directory when used now rather - than continue to use your existing options set. You may want to not - use -p or move your existing options directory, in - /usr/local/etc/poudriere.d/*-options, to the new format with the - ports tree name in it. Otherwise "poudriere bulk" will use the - new empty directory. - - This behavior will likely change in 3.2.1 to be more backwards-compatible. - -20171112: - AFFECTS: consumers of devel/oniguruma* - AUTHOR: riggs@FreeBSD.org - - Outdated versions of oniguruma have been removed from the ports - tree; devel/oniguruma is the only supported version, currently - replacing devel/oniguruma6. - pkg should handle this automatically while users of portmaster or - portupgrade might need to take additional manual steps: - - for users of portmaster: - portmaster -o devel/oniguruma devel/oniguruma6 - portmaster -r devel/oniguruma - - for users of portupgrade: - portupgrade -o devel/oniguruma devel/oniguruma6 - portupgrade -fr devel/oniguruma - -20171107: - AFFECTS: users of www/node - AUTHOR: bhughes@FreeBSD.org - - The www/node port has been updated to node.js v9.0.0, the latest - upstream release. A new port, www/node8, has been created for the - v8.x LTS branch. Users wanting to stay on v8.x can replace www/node - with www/node8 with one of the following commands: - - # pkg install www/node8 - or - # portmaster -o www/node8 www/node - or - # portupgrade -o www/node8 www/node - -20171107: - AFFECTS: users of security/libressl - AUTHOR: brnrd@FreeBSD.org - - The port has been updated to the latest stable version 2.6 of LibreSSL. - The shared library versions of the libraries have been bumped. - - After upgrading, manually update all packages that depend on any of the - libraries provided by LibreSSL (libssl, libcrypto and libtls) since the - versions of these libraries have changed. Normally, you can obtain the - list of dependent software by running the following command: - - # pkg info -r libressl - - Then you should rebuild all ports depending on libressl to avoid dangling - shared library dependencies. Poudriere and pkg handle this correctly, - portmaster and portupgrade users can use the following to rebuild all - dependent ports. - - Portmaster users: - portmaster -r libressl - Portupgrade users: - portupgrade -fr security/libressl - -20171105: - AFFECTS: users of www/mod_auth_cas - AUTHOR: brnrd@FreeBSD.org - - The configuration of mod_auth_cas has changed since the previous - version. Visit the https://github.com/apereo/mod_auth_cas page for - an overview of all configuration parameters - -20171105: - AFFECTS: users of www/mod_rpaf2 - AUTHOR: brnrd@FreeBSD.org - - The configuration of mod_rpaf2 has been heavily modified since version - 0.6. Have a look at https://github.com/gnif/mod_rpaf/tree/v0.8.4 to - determine what you need to change in your configuration. - -20171031: - AFFECTS: users of editors/vim - AUTHOR: adamw@FreeBSD.org - - The default vim language bindings have changed. Python 2 and 3 bindings - may now be enabled independently (the default vim package will continue - to depend on python-2.7). - - Lua and Tcl bindings have been disabled by default. If you need these - bindings, you'll need to compile vim yourself. Note that bindings are - only for plugins written in those languages, and for interactive - debugging. Editing, indenting, linting, completing, and syntax-highlighting - those languages is NOT affected. - -20171026: - AFFECTS: users of devel/universal-ctags - AUTHOR: rodrigo@FreeBSD.org - - Due to conflicts with emacs ctag (editors/emacs-devel, editors/emacs-nox11, editors/emacs), - the installed files will be prefixed with the 'u' character. - The new binaries will de named uctags and ureadtags. - -20171015: - AFFECTS: people using WITHOUT_DEBUG - AUTHOR: madpilot@FreeBSD.org - - The WITHOUT_DEBUG flag has been retired. It's only purpose was - to override a global WITH_DEBUG, if that was defined, but many - ports were ignoring such flag even if honouring WITH_DEBUG. - - The same effect can be obtained using ".undef WITH_DEBUG" without - any special support in port Makefiles. - -20171012: - AFFECTS: users of security/openssh-portable - AUTHOR: bdrewery@FreeBSD.org - - OpenSSH has been upgraded to 7.6p1 which has removed several deprecated - features: - - - SSH version 1 support dropped. - - Dropped support for hmac-ripemd160 MAC. - - Dropped support for the ciphers arcfour, blowfish and CAST. - - RSA keys less than 1024 bits are refused. - - The HPN option is currently disabled by default, and does not build, - in the package. This follows what happened in base as well. - -20171004: - AFFECTS: users of security/krb5-appl - AUTHOR: cy@FreeBSD.org - - Configuration options to rename kerberos ftp, telnet, rlogin, rsh, and - rcp are now default to avoid conflicting with net/bsdrcmds packages - (in poudriere). Deselect the options to use the original command names - and also uninstall net/bsdrcmds to avoid the conflict. - -20171002: - AFFECTS: users of x11-wm/cwm - AUTHOR: tobik@FreeBSD.org - - Configuration options were renamed and you need to update your ~/.cwmrc - accordingly. Make sure to check cwmrc(5) for the new option names. - cwm-migrate-config.pl can help in migrating your ~/.cwmrc. - -20171001: - AFFECTS: users of mail/isync using Maildir sub-folders - AUTHOR: ehaupt@FreeBSD.org - - If you have Maildir sub-folders, you need to update the configuration - to specify the naming style. - - Please refer to the mbsync(1) man page section 'SubFolders - Verbatim|Maildir++|Legacy' on how to make the apropriate changes. - -20170930: - AFFECTS: users of PHP and its modules - AUTHOR: eugen@FreeBSD.org - - All lang/php* ports switched to depend on devel/oniguruma6 - instead of previous oniguruma version some time ago. - - If you have not moved from devel/oniguruma5 before and - have troubles updating PHP, - - for users of portmaster: - portmaster -o devel/oniguruma6 devel/oniguruma5 - portmaster -r devel/oniguruma6 - - for users of portupgrade: - portupgrade -o devel/oniguruma6 devel/oniguruma5 - portupgrade -fr devel/oniguruma6 - - pkg should handle this automatically. - -20170928: - AFFECTS: users of security/courier-authlib and its modules - AUTHOR: madpilot@FreeBSD.org - - The affected ports have been modified to follow the upstream - suggested best practice to use the sysconftool on installation. - - Please make sure your configuration files include all the comments - that tool uses to correctly update the configuration on update. - - You can use the ".sample" or ".dist" files as templates for missing - comments if needed. - -20170915: - AFFECTS: users of devel/cargo - AUTHOR: rust@FreeBSD.org - - Starting with version 1.19.0, Cargo is provided with Rust. Therefore, - devel/cargo was merged into lang/rust. - -20170914: - AFFECTS: users of CMake & CMake Modules - AUTHOR: adridg@FreeBSD.org - - The devel/cmake-modules port has been merged into devel/cmake. - - The benefit of being able to update the modules without the binary - is outweighed by the issues caused by having the binary out-of-sync - with the modules. - - Users should delete the devel/cmake-modules package and then - upgrade or reinstall devel/cmake. - - All ports have been updated to depend only on CMake. - -20170904: - AFFECTS: users of net-mgmt/seafile-server - AUTHOR: ultima@FreeBSD.org - - Users using MySQL updating to 6.1.2 need to verify table's collation - are utf8_unicode_ci. Upstream has set collation type to be implicit - and will cause all libraries to disappear if set to incorrect collation. - -20170828: - AFFECTS: users of security/gnupg - AUTHOR: adamw@FreeBSD.org - - security/gnupg has become the new stable version of GnuPG. This is - an LTS branch. gnupg20 will reach EOL at the end of the year, and all - gnupg20 users should migrate to gnupg22. - - See https://gnupg.org/faq/whats-new-in-2.1.html for important changes. - -20170820: - AFFECTS: users of www/uwsgi - AUTHOR: ultima@FreeBSD.org - - The default socket owner and mode had been changed from www:www 600 - to uwsgi:www 660. This should resolve issue #1471[1] on github. - - [1] https://github.com/unbit/uwsgi/issues/1471 - -20170808: - AFFECTS: users of lang/ghc and */hs-* - AUTHOR: haskell@FreeBSD.org - - The Glorious Glasgow Haskell Compiler has been updated to version - 8.0.2. Hence it is recommended to rebuild or reinstall all the - dependent ports and the lang/ghc port itself in one of the following - ways: - - # portmaster -w -r ghc - or - # portupgrade -fr lang/ghc - - In case of pkg(8), it is probably safer to remove all the GHC-dependent - packages along with GHC and reinstall everything from scratch. For - example: - - # pkg query "%ro" ghc > ghc-pkgs.txt - # pkg delete -y lang/ghc - - In ghc-pkgs.txt, check and remove all the packages that have been moved - on the update, then use this command: - - # pkg install -y `cat ghc-pkgs.txt` - -20170807: - AFFECTS: users of mail/dovecot2 and mail/dovecot2-pigeonhole - AUTHOR: adamw@FreeBSD.org - - Now that dovecot1 has been removed from the ports tree, dovecot2 - and dovecot2-pigeonhole have been renamed to simply dovecot and - dovecot-pigeonhole. - - pkg should handle the rename automatically, but if you run into - trouble, you can point pkg at the new origin via: - - # pkg set -o mail/dovecot2:mail/dovecot - # pkg set -o mail/dovecot2-pigeonhole:mail/dovecot-pigeonhole - - Similarly, you can point portmaster at the new location via: - - # portmaster -o mail/dovecot mail/dovecot2 - - If all else fails, just remove and reinstall the package: - - # pkg delete dovecot2 - # pkg install dovecot - -20170806: - AFFECTS: users of mail/dovecot2-antispam-plugin - AUTHOR: adamw@FreeBSD.org - - Development of the antispam plugin ceased years ago, and upstream - recommends using pigeonhole (mail/dovecot2-pigeonhole) instead. - - See https://wiki2.dovecot.org/HowTo/AntispamWithSieve for a recipe - to replicate the antispam plugin's behaviour. - -20170803: - AFFECTS: users of net/guacamole-client - AUTHOR: ultima@FreeBSD.org - - As of version 0.9.13, the configuration directory for guacamole-client - has changed from /usr/local/etc/guacamole to - /usr/local/etc/guacamole-client. - -20170803: - AFFECTS: users of net/guacamole-server - AUTHOR: ultima@FreeBSD.org - - As of version 0.9.13, the configuration directory for guacamole-server - has changed from /usr/local/etc/guacd to /usr/local/etc/guacamole-server. - -20170803: - AFFECTS: users of sysutils/terraform - AUTHOR: lifanov@FreeBSD.org - - Terraform was updated to version 0.10.0, which split out provider plugins. - Provider plugins are now installed in the project directory the next time - "terraform init" is run. Please see the complete upgrading guide: - - https://www.terraform.io/upgrade-guides/0-10.html - -20170729: - AFFECTS: users of net-p2p/bitcoin - AUTHOR: lwhsu@FreeBSD.org - - Bitcoin data directory has been changed from /var/db/bitcoind to - /var/db/bitcoin. Users of previous versions may want to migrate data to - new location or specify bitcoind_data. - -20170729: - AFFECTS: users of mail/mailscanner - AUTHOR: crees@FreeBSD.org - - Version 5.0.3 of MailScanner introduced a serious bug in packaging. - Unfortunately if it is installed, your configuration has been deleted. - - If you have managed to get it working, please back up - /usr/local/etc/MailScanner as it will also be deleted on deinstall - of the same package. - -20170726: - AFFECTS: users of www/luakit - AUTHOR: ports@textmail.me - - Luakit was updated to version 2017.07.26, which is incompatible to the - previous release from 2012. Please remove old configuration files from - the following directories: - ${PREFIX}/etc/xdg/luakit - ${HOME}/.config/luakit - ${HOME}/.local/share/luakit - -20170721: - AFFECTS: users of security/sshguard* - AUTHOR: dan.mcgregir@usask.ca - - security/sshguard was updated to 2.0.0, and security/sshguard-pf, - security/sshguard-ipfw, and security/sshguard-null have been merged into - security/sshguard. - - Configuration of the service is now handled in ${PREFIX}/etc/sshguard.conf. - Please select the desired backend, -null is selected by default. - - In order to upgrade from 1.7.1 change the origin to security/sshguard - - # pkg set -o security/sshguard-ipfw:security/sshguard - # pkg set -o security/sshguard-null:security/sshguard - # pkg set -o security/sshguard-pf:security/sshguard - -20170717: - AFFECTS: users of devel/p5-Log-Any and devel/p5-Log-Any-Adapter-Syslog - AUTHOR: eugen@FreeBSD.org - - devel/p5-Log-Any-Adapter-Syslog functionality have been merged into - devel/p5-Log-Any and from now devel/p5-Log-Any must be used. - - devel/p5-Log-Any-Adapter-Syslog will be marked as deprecated and removed. - -20170712: - AFFECTS: users of devel/apr1 - AUTHOR: brnrd@FreeBSD.org - - APR was updated to 1.6.0 and APR-util was updated to 1.6.2 - - The Apache Portable Runtime project removed support for FreeTDS from the - APR Utilities in version 1.6. Users of FreeTDS will have to migrate - configurations to use the newly added ODBC support in conjunction with - FreeTDS using FreeTDS' ODBC capabilities. - - Please rebuild all ports which are using functions from APR/APR-util - such as Apache, Subversion, etc. Normally, you can obtain the list of - dependent software by running the following command: - - # pkg info -r apr - - Then you should rebuild all ports depending on APR(-util) to avoid - dangling shared library dependencies. Poudriere and pkg handle this - correctly, portmaster and portupgrade users can use the following to - rebuild all dependent ports. - - Portmaster users: - portmaster -r apr - Portupgrade users: - portupgrade -fr devel/apr1 - -20170710: - AFFECTS: users of net-im/ejabberd - AUTHOR: ashish@FreeBSD.org - - After update to 17.07, there is an issue[1] expected related to certificate - verification with TLS connections. - - [1] - https://github.com/processone/ejabberd/issues/1833 - -20170628: - AFFECTS: users of www/node - AUTHOR: bhughes@FreeBSD.org - - The www/node port has been updated to Node.js v8.1.2, the latest - upstream release. This is a major release, including many significant - changes. Users are encouraged to read the release announcements before - upgrading: - - https://nodejs.org/en/blog/release/v8.0.0/ - https://nodejs.org/en/blog/release/v8.1.0/ - -20170626: - AFFECTS: users of net-mgmt/zabbix24* - AUTHOR: dbaio@FreeBSD.org - - Zabbix 2.4 has reached end of life and net-mgmt/zabbix24* ports have been - removed. Users that have not yet moved to a newer version, should use now - net-mgmt/zabbix3-* (LTS release) or net-mgmt/zabbix32-* (Standard release). - - See more info about Zabbix releases here: - http://www.zabbix.com/life_cycle_and_release_policy - -20170624: - AFFECTS: users of mail/dcc-dccd - AUTHOR: ultima@FreeBSD.org - - The ALT_HOME option was removed in 1.3.159_1. If this option is being - used, please be sure to move the old home directory, /var/dcc to - ${PREFIX}/dcc. - -20170624: - AFFECTS: users of net/rabbitmq - AUTHOR: olgeni@FreeBSD.org - - The rabbitmq-3.6.10_1 port has been changed to use version 19 of - the Erlang runtime, because RabbitMQ is not yet compatible with - version 20. - - Upgrades to the previous rabbitmq-3.6.10 must be avoided as - they can lead to data corruption due to changes in Erlang 20. - -20170622: - AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run - AUTHOR: tz@FreeBSD.org - - The default version of PostgreSQL has been switched from 9.3 to 9.5. - The upgrade procedure can use up twice the space the databases - currently needs. If you have a big amount of stored data take a - closer look at the manpage of pg_upgrade for avoidance and/or - speedup of the upgrade. - - The upgrade instructions consider a basic usage and do not match - complex scenarios like replication, sharding, or similar. - - Upgrade instructions: - - First stop your PostgreSQL, create PostgreSQL-binaries and backup your data. - If you have another Version of PostgreSQL installed, for example 9.3.12, your - files are named according to this. - - # service postgresql stop - # pkg create postgresql93-server postgresql93-contrib - # mkdir /tmp/pg-upgrade - # tar xf postgresql93-server-9.3.17.txz -C /tmp/pg-upgrade - # tar xf postgresql93-contrib-9.3.17.txz -C /tmp/pg-upgrade - # mv /usr/local/pgsql/data /usr/local/pgsql/data93 - # pkg delete -f databases/postgresql93-server databases/postgresql93-contrib databases/postgresql93-client - - Now update PostgreSQL: - - pkg user: - # pkg install databases/postgresql95-server databases/postgresql95-contrib - # pkg upgrade - - Portmaster users: - # portmaster databases/postgresql95-server databases/postgresql95-contrib - # portmaster -a - - Portupgrade users: - # portinstall databases/postgresql95-server databases/postgresql95-contrib - # portupgrade -a - - After installing the new PostgreSQL version you need to convert - all your databases to new version: - - # service postgresql initdb - # su -l pgsql -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data93/ -B /usr/local/bin/ -D /usr/local/pgsql/data/" - - Now the migration is finished. You can start PostgreSQL again with: - - # service postgresql start - -20170614: - AFFECTS: users of editors/calligra - AUTHOR: groot@kde.org - - Calligra has been updated to 3.0.1, which is a KDE Frameworks 5 (KF5) - based application. Calligra now uses Qt5 and KF5. The translations have - been merged (upstream) into the application, so separate language / - translation ports are no longer provided. Krita has been split out - (upstream) into a separate application, which is packaged as - graphics/krita. Kexi, the visual database applications creator, - is packaged separately as databases/kexi. - - Users of Calligra are encouraged to install Krita and Kexi separately, - and to report issues with the upgrade to kde@. - -20170613: - AFFECTS: users of net-im/ejabberd - AUTHOR: ashish@FreeBSD.org - - After update to 17.04, there is an issue[1] expected with S2S connections, - which can be resolved by adding 'mod_s2s_dialback: {}' to 'modules' section - of configuration file. - - [1] - https://github.com/processone/ejabberd/issues/1700 - -20170603: - AFFECTS: users of www/kanboard - AUTHOR: joneum@FreeBSD.org - - After update to 1.0.44, there are following breaking changes: - * Move calendar to external plugin: https://github.com/kanboard/plugin-calendar - * Move Gantt charts to external plugin: https://github.com/kanboard/plugin-gantt - * Move Gravatar to external plugin: https://github.com/kanboard/plugin-gravatar - -20170602: - AFFECTS: users of Qt 5 in presence of binutils - AUTHOR: amdmi3@FreeBSD.org - - gold linker from binutils 2.28 may produce duplicate library - symbols, which makes shared libraries created with it not usable - with conventional ld linker. - - This affects Qt, as qt5-qmake will detect gold and use it to build - Qt libraries. Broken libQt5Core will be produced and ports which - depend on it will then fail to link with the following errors: - - ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `__bss_start at Qt_5' - ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here - ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `_edata at Qt_5' - ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here - ...lib/libQt5Core.so:(.dynamic+0x2b2d0): multiple definition of `_end at Qt_5' - - Qt5 was fixed to ignore gold. If you see these errors, you - need to rebuild qt5-qmake, then all qt5-* ports. - -20170529: - AFFECTS: users of sysutils/dsbmd - AUTHOR: mk@freeshell.de - - Due to new configuration variables and semantic changes, users of dsbmd - version 0.2 and earlier should consider recreating their dsbmd.conf from - the new dsbmd.conf.sample. - -20170518: - AFFECTS: users of www/yarn - AUTHOR: adamw@FreeBSD.org - - The default node backend for yarn has switched to www/node. Binary - package users should expect the node backend to be switched during - the upgrade. To keep the node6 (LTS) backend, rebuild www/yarn with - the NODE6 backend option enabled. - -20170517: - AFFECTS: users of security/pecl-ssh2 - AUTHOR: dbaio@FreeBSD.org - - The security/pecl-ssh2 has been upgraded to version 1.0, and the new - version is not compatible with PHP5. If you need PHP5 support, you can - find version 0.13 in security/pecl-ssh2-0. - -20170412: - AFFECTS: users of sysutils/ansible - AUTHOR: lifanov@FreeBSD.org - - The default value for ansible_python_interpreter has been changed - to match the upstream /usr/bin/python. If managing FreeBSD systems, - adjust the hosts database to explicitly set a valid python interpreter: - - [freebsd] - host1 - - [freebsd_vars] - ansible_python_interpreter=/usr/local/bin/python2.7 - -20170411: - AFFECTS: users of security/libressl - AUTHOR: brnrd@FreeBSD.org - - The port has been updated to the latest stable version 2.5 of LibreSSL. - The shared library versions of the libraries have been bumped. - - After upgrading, manually update all packages that depend on any of the - libraries provided by LibreSSL (libssl, libcrypto and libtls) since the - versions of these libraries have changed. Normally, you can obtain the - list of dependent software by running the following command: - - # pkg info -r libressl - - Then you should rebuild all ports depending on libressl to avoid dangling - shared library dependencies. Poudriere and pkg handle this correctly, - portmaster and portupgrade users can use the following to rebuild all - dependent ports. - - Portmaster users: - portmaster -r libressl - Portupgrade users: - portupgrade -fr security/libressl - -20170411: - AFFECTS: www/firefox - AUTHOR: gecko@FreeBSD.org - - Firefox 53 or later may fail to build if sem(4) is present (see below) - because sysconf(3) still consults the old limits. If you don't plan to - run FreeBSD 8.x or older binaries make sure sem(4) isn't loaded during - boot or built statically into the kernel. - - Creating config.status - Traceback (most recent call last): - File "configure.py", line 124, in <module> - sys.exit(main(sys.argv)) - File "configure.py", line 34, in main - return config_status(config) - File "configure.py", line 119, in config_status - return config_status(args=[], **encode(sanitized_config, encoding)) - File "python/mozbuild/mozbuild/config_status.py", line 136, in config_status - reader = BuildReader(env) - File "python/mozbuild/mozbuild/frontend/reader.py", line 886, in __init__ - self._gyp_worker_pool = ProcessPoolExecutor(max_workers=max_workers) - File "python/futures/concurrent/futures/process.py", line 274, in __init__ - _check_system_limits() - File "python/futures/concurrent/futures/process.py", line 263, in _check_system_limits - raise NotImplementedError(_system_limited) - NotImplementedError: system provides too few semaphores (30 available, 256 necessary) - -20170410: - AFFECTS: users of x11-wm/awesome - AUTHOR: garga@FreeBSD.org - - Awesome Window Manager (x11-wm/awesome) was upgraded to 4.1 and its config - is not backward compatible with 3.5. A new port was created to keep 3.5 - version available at x11-wm/awesome3 and it will be available for 6 months - until users have time to upgrade configuration. - - There are references about what has changed in 4.0 at: - - https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4 - - And configuration porting tips at: - - https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4 - - If you would like to keep using 3.x, please run the collowing command to - update pkg database: - - # pkg set -n awesome:awesome3 - # pkg set -o x11-wm/awesome:x11-wm/awesome3 - -20170404: - AFFECTS: users of Xapian 1.2.x and www/ikiwiki - AUTHOR: sunpoet@FreeBSD.org - - Xapian has been updated to 1.4.3. The 1.2.x series has been renamed with - suffix "12". The Perl binding for Xapian 1.4.x is databases/p5-Xapian. - Since www/ikiwiki depends on Search::Xapian, it stays with Xapian 1.2. - If you would like to keep using 1.2, please run the following commands - to update pkg database: - - xapian-core: - # pkg set -n xapian-core:xapian-core12 - # pkg set -o databases/xapian-core:databases/xapian-core12 - - p5-Search-Xapian: - # pkg set -n p5-Search-Xapian:p5-Search-Xapian12 - # pkg set -o databases/p5-Search-Xapian:databases/p5-Search-Xapian12 - - xapian-bindings: - # pkg set -n xapian-bindings:xapian-bindings12 - # pkg set -o databases/xapian-bindings:databases/xapian-bindings12 - - xapian-omega: - # pkg set -n xapian-omega:xapian-omega12 - # pkg set -o databases/xapian-omega:databases/xapian-omega12 - -20170401: - AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl* - AUTHOR: timur@FreeBSD.org - - It turned out that arbitary versions of p5-Parse-Pidl may lead to the - hard to explain crashes of the Samba server and utilities(in particular - we suspect it was responsible for the troubles with the DC provisioning). - - So, from now on net/samba* ports use bundled version of Pidl. You need to - remove external package from the system: - - pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44 - -20170331: - AFFECTS: users of security/openssh-portable - AUTHOR: bdrewery@FreeBSD.org - - The format of several log messages emitted by the packet code has - changed to include additional information about the user and - their authentication state. Software that monitors ssh/sshd logs - may need to account for these changes. For example: - - Connection closed by user x 1.1.1.1 port 1234 [preauth] - Connection closed by authenticating user x 10.1.1.1 port 1234 [preauth] - Connection closed by invalid user x 1.1.1.1 port 1234 [preauth] - - Affected messages include connection closure, timeout, remote - disconnection, negotiation failure and some other fatal messages - generated by the packet code. - -20170326: - AFFECTS: users of samba43 - AUTHOR: antoine@FreeBSD.org - - The default version of samba has been switched from 4.3 to 4.4. - Upgrade instructions: - - For package users having samba43 installed indirectly (as a dependency): - # pkg upgrade - - For package users having samba43 installed directly (leaf port): - # pkg upgrade - # pkg install samba44 - - For ports users: - If you want to keep samba43, add DEFAULT_VERSIONS+= samba=4.3 to make.conf - - If you want to upgrade to samba44, remove samba43 and obsolete packages: - # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 samba43 p5-Parse-Pidl - - Portmaster users: - # portmaster net/samba44 - # portmaster -a - - Portupgrade users: - # portinstall net/samba44 - # portupgrade -a - -20170325: - AFFECTS: net/samba46 and devel/p5-Parse-Pidl - AUTHOR: timur@FreeBSD.org - - New version of Samba port from 4.6 branch is added. Before upgrading please read upgrade notes: - - https://www.samba.org/samba/history/samba-4.6.0.html - - For the vfs_fruit users: - - Users on *BSD must rename the metadata xattr used by vfs_fruit when - using the default setting "fruit:metadata = netatalk". - - Due to a glitch in the Samba xattr API compatibility layer for FreeBSD and a - mistake in vfs_fruit, vfs_fruit ended up using the wrong xattr name when - configured with "fruit:metadata = netatalk" (default). Instead of the correct - - org.netatalk.Metadata - - it used - - netatalk.Metadata - - Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" - which means existing installations must rename this xattrs. For this purpose - Samba now includes a new tool `mvxattr`. - -20170325: - AFFECTS: net/samba45, net/samba46 and devel/p5-Parse-Pidl - AUTHOR: timur@FreeBSD.org - - While new Uses/samba.mk dosen't work well with slave ports to compile devel/p5-Parse-Pidl - for net/samba45 or net/samba46 you need explicitly set in the /etc/make.conf: - - SAMBA4_PORT=net/samba46 - - explicitly. In the future that shouldn't be necessary. - -20170321: - AFFECTS: users of samba36-libsmbclient, samba36-nmblookup samba36-smbclient and samba36 - AUTHOR: antoine@FreeBSD.org - - The obsolete samba36-libsmbclient, samba36-nmblookup, samba36-smbclient and samba36 packages/ports were removed - and USES=samba was introduced. - Upgrade instructions: - - For package users having those ports installed indirectly (as dependencies): - # pkg upgrade - - For package users having those ports installed directly (leaf ports): - # pkg upgrade - # pkg install samba43 - - For ports users: - Choose you samba version, for instance add DEFAULT_VERSIONS+= samba=4.3 to make.conf - - Remove obsolete packages: - # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 - - Portmaster users: - # portmaster net/samba43 - # portmaster -a - - Portupgrade users: - # portinstall net/samba43 - # portupgrade -a - -20170319: - AFFECTS: users of mail/pecl-mailparse - AUTHOR: dbaio@bsd.com.br - - The mail/pecl-mailparse has been upgraded to version 3.0.2, and the new - version is not compatible with PHP5. If you need PHP5 support, you can - find version 2.1.6 in mail/pecl-mailparse2. - -20170319: - AFFECTS: users of textproc/pecl-yaml - AUTHOR: dbaio@bsd.com.br - - The pecl-yaml has been upgraded to version 2.0.0, and the new version is - not compatible with PHP5. If you need PHP5 support, you can find version - 1.3.0 in textproc/pecl-yaml1. - -20170316: - AFFECTS: users of python setuptools - AUTHOR: antoine@FreeBSD.org - - The python setuptools ports have been renamed to better match other python ports. - Ports users need to rename them so that portupgrade and portmaster do not - get confused. For example: - - pkg set -n py27-setuptools27:py27-setuptools - pkg set -o devel/py-setuptools27:devel/py27-setuptools - or - pkg set -n py35-setuptools35:py35-setuptools - pkg set -o devel/py-setuptools35:devel/py35-setuptools - -20170312: - AFFECTS: users of textproc/ack - AUTHOR: sunpoet@FreeBSD.org - - ack has been renamed back to p5-ack to match our perl naming. You could - run the following to update pkg database: - - # pkg set -n ack:p5-ack - # pkg set -o textproc/ack:textproc/p5-ack - -20170311: - AFFECTS: users of games/tome4 with paid DLCs - AUTHOR: lifanov@FreeBSD.org - - The Ashes of Urh'Rok and Embers of Rage DLCs have been updated to be - compatible with changes introduced in ToME 1.5.0. Users of these DLCs - will need to redownload nd place these in $HOME/.t-engine/4.0/addons. - -20170302: - AFFECTS: users of mail/thunderbird with Lightning - AUTHOR: cmt@FreeBSD.org - - After changes in the packaging of the Lightning extension, profiles - using this extension have to be re-created. - -20170223: - AFFECTS: users of devel/mtbl - AUTHOR: truckman@FreeBSD.org - - There is a libmtbl shared library version bump in mtbl version 1.0.0. - The affected dependent ports have had PORTREVISION bumps, but you will - need to rebuild any applications that link to libmtbl. - -20170220: - AFFECTS: sysutils/filebeat sysutils/metricbeat sysutils/packetbeat - AUTHOR: girgen@FreeBSD.org - - The three elasticsearch beats ports have merged into one single port - systuils/beats that installs all of the above and some more. The reason is to - make the port more maintainable and also that the new heartbeat beat would - conflict with sysutils/heartbeat. - -20170220: - AFFECTS: devel/libevent2 - AUTHOR: jbeich@FreeBSD.org - - libevent2 has been renamed back to libevent as the default version. - If you manage out of tree ports make sure to run the following: - - # pkg set -n libevent2:libevent - # pkg set -o devel/libevent2:devel/libevent - -20170218: - AFFECTS: users of Qt 4 and Qt 5 - AUTHOR: kde@FreeBSD.org - - Following what is already done in Qt 5, the Qt 4 ports no longer install - their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most - cases). Additionally, the "-qt4" suffix has been dropped from the file names - of the binaries that had it, such as "qmake-qt4". - - The new misc/qtchooser port is now used to choose whether a Qt 4 or Qt 5 - version of a binary such as "moc", "qmake" or "designer" will be used. By - default, the Qt 5 versions are preferred, but that can be changed by setting - the QT_SELECT environment variable to "qt4". - - qtchooser also allows one to seamlessly use other Qt installations for those - binaries, which is particularly beneficial to people working on Qt itself or - who need their own checkouts. - - See qtchooser(1) for more information on how to configure qtchooser. - -20170213: - AFFECTS: users of www/node* - AUTHOR: bradleythughes@fastmail.fm - - The BUNDLED_SSL option is now enabled by default on FreeBSD 10, since - Node.js requires OpenSSL 1.0.2, and FreeBSD 10 is shipped with 1.0.1. - -20170213: - AFFECTS: users of graphics/libGL, graphics/libEGL, graphics/libglesv2 - AUTHOR: kwm@FreeBSD.org - - The workaround for handling conflicting libraries between the - nvidia-driver, libGL, libEGL and libglesv2 ports was removed. If the - nvidia-driver port is updated before the other ports, it will remove - the libraries of said ports. This is a side effect of how the workaround - worked. If this happens reinstalling the affected port is enough. - - pkg users can run: pkg install -f libGL libEGL libglesv2 - -20170211: - AFFECTS: users of x11-server/xorg-server - AUTHOR: rezny@FreeBSD.org - - Xorg server has been updated to 1.18.4 and autodetection has changed. - The order in which drivers are now attempted is: - 1) vendor/model specific driver according to PCI IDs - 2) generic modesetting driver which requires a drm driver with KMS - 3) scfb, the generic framebuffer driver - 4) vesa (only if arch is x86) - - This should minimize the need for xorg.conf files. It is recommended to - load the correct KMS driver (i915kms.ko or radeonkms.ko) via rc.conf, - i.e. kld_list="i915kms.ko", to ensure correct functionality. Although - the vendor drivers may attempt to load the correct drm driver, which - does not always work, the modesetting driver assumes the required KMS - driver is already loaded and will fail if there is none. The modesetting - driver is now recommended as an alternative to the Intel driver; the - performance is comparable and stability is better with modesetting. The - ATI driver continues to offer better performance than modesetting. - -20170203: - AFFECTS: users of security/libressl-devel - AUTHOR: brnrd@FreeBSD.org - - The version 2.5.1 bumps the libcrypto, libssl and libtls shared library - versions. You will have to rebuild all packages that depend on - libressl-devel. Check the 20160811 libressl entry for more detailed - guidance on rebuilding. - -20170202: - AFFECTS: users of www/uwsgi - AUTHOR: feld@FreeBSD.org - - The previous disruptive changes to uwsgi for security have been remediated - through creation of a dedicated uwsgi user/group and utilizing the - uwsgi feature to set socket ownership. The uwsgi daemon by default now - has the following properties: - - * Process runs as uwsgi user and group (UID/GID 165) - * Socket mode is 660, still protecting unauthorized access from "other" - * Socket ownership is www:www, restoring compatibility - -20170130: - AFFECTS: users of devel/ice, devel/py-ice, devel/php5-ice - AUTHOR: grembo@FreeBSD.org - - Since __WORDSIZE as defined by <stdint.h> always reports 32 when using - C++98/03 (unless __STDC_LIMIT_MACROS is set explictly), Ice 3.6.3 used - "long long" for Int64 instead of "long" on 64-bit platforms by mistake. - A workaround has been added in version 3.6.3_2 of these three ports, - requiring to upgrade all of them at the same time and to rebuild all - custom code that links against them. - -20170129: - AFFECTS: users of multimedia/motion - AUTHOR: jhale@FreeBSD.org - - Version 3.x expected the configuration files to reside in: - ${LOCALBASE}/etc - Version 4.x expects the configuration files to reside in: - ${LOCALBASE}/etc/motion - This was unfortunately overlooked when the port was updated to 4.x, but it - has now been fixed to install the default configuration file in the new - location. The rc script now checks for motion.conf in the new location. - - While you may be able to simply copy your old motion.conf to the new location, - it is recommended to review ${LOCALBASE}/etc/motion/motion.conf and make - changes to it based on your old ${LOCALBASE}/etc/motion.conf as some options - have been added and removed. - - Further, if you use motion with multiple cameras and have - ${LOCALBASE}/etc/thread[0-9].conf files, they should be moved to - ${LOCALBASE}/etc/motion as well. These files are deprecated and should be - renamed to camera[0-9].conf and in motion.conf, lines like: - thread /usr/local/etc/thread1.conf - Should be converted to: - camera /usr/local/etc/motion/camera1.conf - -20170127: - AFFECTS: users of www/uwsgi - AUTHOR: feld@FreeBSD.org - - The default socket mode for uwsgi as 777 is a severe security concern. - This has been remediated by changing the rc script to default to 600. - The mode is configurable with rc.conf values: uwsgi_socket_mode="600" - or for a profile named "www", uwsgi_www_socket_mode="600". - -20170121: - AFFECTS: users of security/tinc - AUTHOR: dinoex@FreeBSD.org - - this version of tinc requires all nodes in the VPN to be linked with a - version of OpenSSL or LibreSSL that supports the AES256 and SHA256 - algorithms. - -20170120: - AFFECTS: users of databases/mysql56-server - AUTHOR: feld@FreeBSD.org - - databases/mysql56-server was updated to 5.6.35 which included backported - rc script changes from the mysql57-server port. This broke mysql_optfile in - rc.conf and also forced a sample my.cnf if none existed. MySQL has - some parameters which cannot be changed after a database has been - created, so this caused MySQL to fail to start. - - This change was reverted in mysql56-server-5.6.35_1 - - An additional change was made in mysql56-server-5.6.35_2 to prevent - automatic loading of a sample my.cnf which was causing issues for - users who were running without a my.cnf. - -20170117: - AFFECTS: users of EoL'ed FreeBSD versions (<10.3, 11 prior to 11.0) - AUTHOR: amdmi3@FreeBSD.org - - The ports system will now refuse to build anything if it's run on - outdated system version. This protects users from unexpected build - failures after code to support EoL'ed systems is removed from the - tree. You may define ALLOW_UNSUPPORTED_SYSTEM to override this and - allow builds, but no support will be provided in case of failures. - -20170116: - AFFECTS: users of java/wildfly10 - AUTHOR: olgeni@FreeBSD.org - - The java/wildfly10 port has been updated to 10.1.0. To complete the - migration you must copy your existing configuration (directories - "appclient", "standalone", and "domain") from /usr/local/wildfly-10.0.0 - to /usr/local/wildfly10. - -20170115: - AFFECTS: users of net-mgmt/librenms - AUTHOR: dvl@FreeBSD.org - - The following is recommended for /var/db/mysql/my.cnf - - NOTE: these are global settings. Please read this first: - - http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html - - [mysqld] - innodb_file_per_table=1 - sql-mode="" - -20170109: - AFFECTS: users of lang/ruby22 - AUTHOR: swills@FreeBSD.org - - The default ruby version has been updated from 2.2 to 2.3. - - If you compile your own ports you may keep 2.2 as the default version by - adding the following lines to your /etc/make.conf file: - - # - # Keep ruby 2.2 as default version - # - DEFAULT_VERSIONS+=ruby=2.2 - - If you wish to update to the new default version, you need to first stop any - software that uses ruby. Then, you will need to follow these steps, depending - upon how you manage your system. - - If you use pkgng, simply upgrade: - # pkg upgrade - - If you use portmaster, install new ruby, then rebuild all ports that depend - on ruby: - # portmaster -o lang/ruby23 lang/ruby22 - # portmaster -R -r ruby-2.3 - - If you use portupgrade, install new ruby, then rebuild all ports that depend - on ruby: - - # pkg delete -f ruby portupgrade - # make -C /usr/ports/ports-mgmt/portupgrade install clean - # pkg set -o lang/ruby22:lang/ruby23 - # portupgrade -x ruby-2.3.\* -fr lang/ruby23 - -20170102: - AFFECTS: multimedia/ffmpeg - AUTHOR: jbeich@FreeBSD.org - - OPTIMIZED_CFLAGS switched to only use vendor optimizations which - means -ffast-math -fno-finite-math-only are no longer applied. If - you did like the former behavior consider adding - - # multimedia/ffmpeg/Makefile.local - OPTIMIZED_CFLAGS_CFLAGS += -ffast-math -fno-finite-math-only - - or - - # /etc/make.conf - .if ${.CURDIR:M*/multimedia/ffmpeg} - CFLAGS += -ffast-math -fno-finite-math-only - .endif - -20161230: - AFFECTS: users of x11/xfce4-terminal - AUTHOR: olivierd@FreeBSD.org - - The port has been updated to the latest stable version 0.8.2. - Please, don't active the hidden 'MiscSlimTabs' option in - ~/.config/xfce4/terminal/terminalrc, it requires Gtk+ > 3.20. - -20161228: - AFFECTS: users of multimedia/mlt - AUTHOR: avilla@FreeBSD.org - - MLT Qt plugins have been moved to their own ports, mlt-qt4 and - mlt-qt5. Please, uninstall multimedia/mlt before you update: - - # pkg delete mlt - -20161227: - AFFECTS: users of security/openvpn, security/openvpn-polarssl - AUTHOR: Matthias Andree <mandree@FreeBSD.org> - - The OpenVPN ports have been updated to the new upstream release v2.4, - and their predecessors preserved as openvpn23 and openvpn23-polarssl, - respectively. Note that for the new v2.4 release, the - openvpn-polarssl port has been renamed to openvpn-mbedtls to match the - upstream library's new name. - -20161218: - AFFECTS: users of www/nghttp2 - AUTHOR: sunpoet@FreeBSD.org - - nghttp2 has been split into 2 ports: www/libnghttp2 for core library and - www/nghttp2 for the rest. Please uninstall nghttp2 before you update - this port. - -20161216: - AFFECTS: mail/thunderbird, www/seamonkey - AUTHOR: gecko@FreeBSD.org - - ENIGMAIL is no longer provided as part of the ports after upstream - dropped binary components in 1.9. Go to Tools -> Add-ons Manager - then type "enigmail" in the search box to install. - -20161213: - AFFECTS: users of devel/skalibs, lang/execline, sysutils/s6 - AUTHOR: Colin Booth <colin-ports@heliocat.net> - - skalibs has undergone a major version bump and compatibility is not - guaranteed for software with a runtime dependency on - libskarnet.so.2.3.9.0. This will not affect lang/execline or - sysutils/s6 as those are statically linked against libskarnet.a. - - execline has undergone a major version bump and compatibility is not - guaranteed for software with a runtime dependency on - libexecline.so.2.1.4.5. This will not affect sysutils/s6 as all s6 - programs are statically linked against libexecline.a. - - s6 has undergone a major version bump and compatibility is not - guaranteed for software with a runtime dependency on - libs6.so.2.2.4.3. Additionally, s6-applyuidgid and s6-setuidgid - have moved from $PREFIX/sbin to $PREFIX/bin. Any scripts calling - those utilities that are not relying on $PATH resolution to find - them will need to be rewritten. - -20161207: - AFFECTS: users of www/node - AUTHOR: bradleythughes@fastmail.fm - - The www/node port has been updated to node.js v7.2.0, the latest - upstream release. A new port, www/node6, has been created for the - v6.x LTS branch. Users wanting to stay on v6.x can replace www/node - with www/node6 with one of the following commands: - - # pkg set -o www/node:www/node6 - or - # portmaster -o www/node6 www/node - or - # portupgrade -o www/node6 www/node - -20161202: - AFFECTS: users of textproc/p5-Search-Elasticsearch - AUTHOR: tj@FreeBSD.org - - As of the 5.01 release of ths package, the client libraries for older - versions of Elasticsearch have started to be shipped seperately. If you are - using this library to access a none 5.X server you will need to install one of - the textproc/p5-Search-Elasticsearch-Client-* ports. - -20161126: - AFFECTS: users of security/gpgme-* - AUTHOR: jhale@FreeBSD.org - - Gpgme has been updated to 1.8.0. - With it comes the removal of libgpgme-pthread.so in favor of using - libgpgme.so itself as the thread-safe library. Ports that may have - linked to -lgpgme-pthread will now just link to -lgpgme. PORTREVISION - has been bumped on all ports with a dependency on security/gpgme. - - The Python module provided by security/py-gpgme has been renamed - from pyme3 to gpg, as well. - - Portmaster users: - portmaster -r gpgme - Portupgrade users: - portupgrade -fr security/gpgme - -20161121: - AFFECTS: users of graphics/tiff - AUTHOR: antoine@FreeBSD.org - - The tiff port was updated to 4.0.7. - The following tools are removed from this release: bmp2tiff, gif2tiff, ras2tiff, rgb2ycbcr and thumbnail. - -20161116: - AFFECTS: users of sysutils/bareos-* - AUTHOR: rand@iteris.com - - Bareos v1.6.x changed the configuration scheme, from one configuration - file per Bareos component (file daemon, storage daemon, and director) - to several configuration files, in several directories, for each - component. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html - - The new scheme will use all files named *.conf in the directory - hierarchies for each component: - - /usr/local/etc/bareos/bareos-dir.d/ - /usr/local/etc/bareos/bareos-fd.d/ - /usr/local/etc/bareos/bareos-sd.d/ - - To retain the old configuration scheme of one file per component add - appropriate lines such as these to your /etc/rc.conf: - - bareos_dir_config="/usr/local/etc/bareos/bareos-dir.conf" - bareos_fd_config="/usr/local/etc/bareos/bareos-fd.conf" - bareos_sd_config="/usr/local/etc/bareos/bareos-sd.conf" - -20161113: - AFFECTS: users of devel/libosinfo - AUTHOR: novel@FreeBSD.org - - The libosinfo port was separated into three different ports - to follow the upstream split: - - - sysutils/osinfo-db-tools: contains the CLI tools - - misc/osinfo-db: contains database with OS data - - devel/libosinfo: the library - - As osinfo-db-tools now ships binaries that previously were - part of libosinfo, it's required to delete the old libosinfo - package to prevent conflict because of same files installation: - - # pkg delete libosinfo - - And then install the new version. - -20161112: - AFFECTS: users of security/heimdal - AUTHOR: hrs@FreeBSD.org - - Heimdal in the base system and security/heimdal <= 1.5.3_6 use - Berkeley DB to store principals into /var/heimdal/heimdal.db and - the database format is version 3 by default. On the other hand, - security/heimdal 1.5.3_7 or newer use the newer version of - Berkeley DB and the database format is version 9. - These two versions are not compatible with each other. If there is - a mismatch between Heimdal utilities and its database format, - you will get an error like the following: - - # /usr/local/sbin/kadmin -l dump - BDB0641 __db_meta_setup: /var/heimdal/heimdal.db: unexpected file type or format - kadmin: hdb_open: opening /var/heimdal/heimdal: Invalid argument - - This mismatch can occur in the following three cases: - - 1. You used Heimdal in the base system and switch to use security/heimdal - after creating /var/db/heimdal.db. - - 2. You used security/heimdal >= 1.5.3_7 and switch to use one in the - base system. - - 3. You used security/heimdal < 1.5.3_7 and upgrade it to 1.5.3_7 or later. - - To fix this mismatch, you need to dump contents of heimdal.db and - rebuild the database by using kadmin(8) utility. - - If you use Heimdal in the base system or older versions of - security/heimdal, and plan to switch to use - security/heimdal >= 1.5.3_7, execute the following command - *after* creating a backup copy of /var/heimdal and installing - security/heimdal: - - # /usr/bin/kadmin -l dump /var/heimdal/heimdal.db.dump - # rm /var/heimdal/heimdal.db - # /usr/local/sbin/kadmin -l load /var/heimdal/heimdal.db.dump - # rm /var/heimdal/heimdal.db.dump - - The above example assumes security/heimdal is installed into - /usr/local. If your base system is compiled with WITHOUT_KERBEROS - use the following instead: - - # db_dump185-5 /var/heimdal/heimdal.db | db_load-5 /var/heimdal/heimdal.db.new - # chown 0600 /var/heimdal/heimdal.db.new - # mv /var/heimdal/heimdal.db.new /var/heimdal/heimdal.db - - db_dump and db_load utilitites are installed by databases/db5 as - dependency of security/heimdal. - - If you want to switch from security/heimdal to Heimdal in the base - system, use the following: - - # /usr/local/sbin/kadmin -l dump /var/heimdal/heimdal.db.dump - # rm /var/heimdal/heimdal.db - # /usr/bin/kadmin -l load /var/heimdal/heimdal.db.dump - # rm /var/heimdal/heimdal.db.dump - -20161105: - AFFECTS: users of security/heimdal - AUTHOR: hrs@FreeBSD.org - - kadmin(8) in heimdal-1.5.3_5 and prior did not create a database - in /var/heimdal in Berkeley DB format which kdc(8) required. This - problem has been fixed in heimdal-1.5.3_6. - -20161104: - AFFECTS: users of mail/mu4e and mail/mu4e-maildirs - AUTHOR: hrs@FreeBSD.org - - The package name of mail/mu4e* have been changed from mu4e* to - mu4e*-emacsNN. When upgrading the older versions, this change can - cause the following error which prevents it from upgrading: - - pkg-static: mu4e-emacs25-0.9.16 conflicts with mu4e-0.9.16 (installs files into the same place). - - If this error occurs, please remove the old packages by using - "pkg delete" manually: - - # pkg delete mu4e-0.9.16 mu4e-maildirs-0.8.20160126_1 - -20161103: - AFFECTS: users of lang/perl5* - AUTHOR: mat@FreeBSD.org - - The default Perl version has been switched to Perl 5.24. If you are using - binary packages to upgrade your system, you do not have anything to do, pkg - upgrade will do the right thing. For the other people, assuming you are - migrating from 5.20 to 5.24, do: - - First, add to /etc/make.conf: - - DEFAULT_VERSIONS+= perl5=5.24 - - Portupgrade users: - portupgrade -o lang/perl5.24 -f lang/perl5.20 - - You can now remove the DEFAULT_VERSIONS line added earlier - from /etc/make.conf - - Then you will need to rebuild everything that uses libperl.so, you - can do so with: - - portupgrade -f `pkg shlib -qR libperl.so.5.20` - - If, for some reason, this command fails at one point, it is safe to - run it again, it will not rebuild what it already rebuilt, as the - ports that have been rebuilt no longer depend on libperl.so.5.20 but - on libperl.so.5.24. - - Portmaster users: - portmaster -o lang/perl5.24 lang/perl5.20 - - You can now remove the DEFAULT_VERSIONS line added earlier - from /etc/make.conf - - Then you will need to rebuild everything that uses libperl.so, you - can do so with: - - portmaster -f `pkg shlib -qR libperl.so.5.20` - - If, for some reason, this command fails at one point, it is safe to - run it again, it will not rebuild what it already rebuilt, as the - ports that have been rebuilt no longer depend on libperl.so.5.20 but - on libperl.so.5.24. - -20161102: - AFFECTS: users of security/acme-client - AUTHOR: brnrd@FreeBSD.org - - The default configuration paths have changed from 'letsencrypt' to - 'acme'. Rename the directories used accordingly - - mv /usr/local/etc/letsencrypt /usr/local/etc/acme - mv /usr/local/etc/ssl/letsencrypt /usr/local/etc/ssl/acme - mv /usr/local/www/letsencrypt /usr/local/www/acme - - Check your scripts to ensure proper operation. - -20161030: - AFFECTS: users of mail/squirrelmail - AUTHOR: adamw@FreeBSD.org - - For better php70 support, the squirrelmail port has switched from - PEAR database access to PDO. If you are using squirrelmail with - a database backend, you'll need to install a corresponding PDO - database module, such as php56-pdo_sqlite. - -20161030: - AFFECTS: users of security/srm - AUTHOR: rakuco@FreeBSD.org - - srm has been updated from 1.2.12 to 1.2.15. Since version 1.2.14, - srm defaults to using its "simple" mode to overwrite files (one pass - writing 0x00 to the files) instead of the 35-pass Gutmann method. - -20161029: - AFFECTS: users of irc/quassel - AUTHOR: woodsb02@FreeBSD.org - - Quassel is now split into two ports / packages; one for providing - the server backend (irc/quassel-core), and one for providing the - client front-end (irc/quassel). Alternatively, the irc/quassel - port can be built with the MONO option enabled to also install - the client and server combined into a single monolithic binary. - -20161028: - AFFECTS: users of security/openssl and security/openssl-devel - AUTHOR: brnrd@FreeBSD.org - - The shared library versions of OpenSSL have been bumped to avoid - issues with ports' and base's OpenSSL not being binary compatible. - - Please rebuild all ports that depend on OpenSSL if you use OpenSSL - from ports. - - If you use portmaster: - portmaster -r openssl - If you use portupgrade: - portupgrade -fr security/openssl - -20161026: - AFFECTS: users of net-p2p/deluge - AUTHOR: rm@FreeBSD.org - - Deluge port has been split out onto CLI part and GUI part. So if user - only needs deluged, net-p2p/deluge-cli should be installed. For full - deluge installation, including GTK+ GUI client, net-p2p/deluge should - be installed as a usual. - - Old deluge package should be removed manually first: - - # pkg delete deluge - - After that install preferred deluge package as usual. - -20161018: - AFFECTS: users of x11/xfce4-terminal - AUTHOR: olivierd@FreeBSD.org - - The port has been updated to the latest stable version 0.8.0. - A warning appears each time we open new tab: - - Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate - widget with... - - This issue will disappear with Gtk > 3.21. - -20161014: - AFFECTS: users of lang/python3 - AUTHOR: antoine@FreeBSD.org - - The default version of python3 has changed from 3.4 to 3.5. - If you wish to stick with older version, add "python3=3.4" to your - DEFAULT_VERSIONS variable in /etc/make.conf. To upgrade: - - If using portupgrade: - # portupgrade -o lang/python35 lang/python34 - - If using portmaster: - # portmaster -o lang/python35 lang/python34 - -20161011: - AFFECTS: users of net-im/ejabberd - AUTHOR: ashish@FreeBSD.org - - Before upgrading ejabberd to 16.09, please make sure to backup your - ejabberd data using: - - % sudo -u ejabberd -H ejabberdctl backup /path/to/backup/file - - In some cases, ejabberd may fail to start, for which a workaround is to - remove the schema.DAT file from /var/spool/ejabberd before starting, and - then restoring everything from the backup using: - - % sudo -u ejabberd -H ejabberdctl restore /path/to/backup/file - - For more details: - - https://github.com/processone/ejabberd/issues/1305 - -20161005: - AFFECTS: users of audio/squeezeboxserver (now audio/logitechmediaserver) - AUTHOR: woodsb02@FreeBSD.org - - With the rename of the audio/squeezeboxserver port to - audio/logitechmediaserver, the server and database are now installed in - different locations by default (/usr/local/share/logitechmediaserver and - /var/db/logitechmediaserver respectively). - - If you were an existing user of audio/squeezeboxserver, you should - consider backing up you server configuration files and database before - upgrading to audio/logitechmediaserver. If you wish to override the - default locations for storing the server and database, you can set the - SLIMDIR and SLIMDBDIR variables in your /etc/make.conf when building - the audio/logitechmediaserver port. - -20161004: - AFFECTS: mail/roundcube-carddav - AUTHOR: gahr@FreeBSD.org - - There is no upgrade path from the 1.0 version. You'll need to: - - 1. Log off from Roundcube. - 2. Manually drop all carddav_* tables from your db backend. - 3. Upgrade the mail/roundcube-carddav port. - - The new tables will be created upon login. The CardDAV plugin will need to be - reconfigured. - - If you are running php < 7.0.0, you'll need to set the plugin option: - $prefs['_GLOBAL']['suppress_version_warning'] = true; - - See https://github.com/blind-coder/rcmcarddav/issues/165 for details. - -20160927: - AFFECTS: emulators/ppsspp - AUTHOR: jbeich@FreeBSD.org - - Qt* GUI was split into separate ports: - - emulators/ppsspp-qt4 - emulators/ppsspp-qt5 - -20160927: - AFFECTS: sysutils/android-file-transfer - AUTHOR: jbeich@FreeBSD.org - - Qt* GUI was split into separate ports: - - sysutils/android-file-transfer-qt4 - sysutils/android-file-transfer-qt5 - -20160922: - AFFECTS: users of databases/pglogical, databases/pglogical-output - AUTHOR: matthew@FreeBSD.org - - As of version 1.2.0, databases/pglogical-output has been merged into - databases/pglogical. portmaster or portupgrade users should delete - pglogical-output manually before upgrading. - -20160921: - AFFECTS: users of mail/sieve-connect - AUTHOR: alexey@renatasystems.org - - Version 0.88 contains two breaking changes: - 1. If the Sieve server does not offer STARTTLS, then connections should now - fail. - 2. When deriving a remote script name from the local filename, use the - basename and strip off directories. - - For additional information see: - http://mail.globnix.net/pipermail/sieve-connect-announce/2016/000012.html - -20160919: - AFFECTS: users of net/vtun - AUTHOR: cy@FreeBSD.org - - The VTUN_EXTENDED_MODE option has been replaced by -e command line - option. - -20160914: - AFFECTS: users of www/nginx-devel - AUTHOR: osa@FreeBSD.org - - Nginx now creates logs under /var/log/nginx/ and changes default log - names from "nginx-access.log" and "nginx-error.log" to "access.log" and - "error.log" respectively. This is important for the error log because - the location is encoded and touched by nginx during startup regardless - of the configured location for the error log. - - See http://trac.nginx.org/nginx/ticket/147 for additional information - on why this happens. - -20160914: - AFFECTS: users of deskutils/xfce4-volumed-pulse - AUTHOR: olivierd@FreeBSD.org - - The port has been updated to the latest stable version 0.2.2. - Support of xfce4-mixer has been removed, so you can delete - its properties with the following command: - - xfconf-query -c xfce4-mixer -p / -rR - -20160910: - AFFECTS: users of security/letsencrypt.sh - AUTHOR: riggs@FreeBSD.org - - The config filename has been changed upstream from "config.sh" - to "config". Users must rename the current config file manually. - In addition, the default WELLKNOWN location has been changed to - %%PREFIX%%/www/letsencrypt. In order to use the previous default - location, the config file must be updated manually as well. - -20160907: - AFFECTS: users of math/galculator - AUTHOR: woodsb02@FreeBSD.org - - galculator now uses GTK3 by default. An option exists in the port to revert - to GTK2 if desired. - -20160906: - AFFECTS: uses of www/nginx - AUTHOR: marino@FreeBSD.org - - Nginx now creates logs under /var/log/nginx/ and changes default log - names from "nginx-access.log" and "nginx-error.log" to "access.log" and - "error.log" respectively. This is important for the error log because - the location is encoded and touched by nginx during startup regardless - of the configured location for the error log. - - See http://trac.nginx.org/nginx/ticket/147 for additional information - on why this happens. - -20160905: - AFFECTS: users of databases/postgresql96-server - AUTHOR: girgen@FreeBSD.org - - The default unix user used by the PostgreSQL daemon has changed to - `postgres' to reflect the long time upstream's convention. Any scripts - you have using the old `pgsql' unix user should be modified when upgrading to - PostgreSQL version 9.6. Older versions of PostgreSQL will continue using - `pgsql' until their end-of-life. - - For users with UTF-8 locales in the database: The ICU patch is *activated by - default* for the PostgreSQL-9.6 server. For previous versions it was optional - and default off, but this has changed. Please read the entry here below from - 20160811 and understand the consequences of changing between ICU and system - locale for database collation (short version: don't). pg_upgrade requires the - collation method to be the same (or a reindex), while pg_dump/restore does not. - - Also, the default home directory for the postgres user is now - /var/db/postgres, and the default data directory for PostgreSQL 9.6 is - /var/db/postgres/data96. - -20160829: - AFFECTS: users of x11/nvidia-driver - AUTHOR: cem@FreeBSD.org - - The NVidia driver has been updated to version 367.35. Starting with - version 358.09, new kernel module was added, nvidia-modeset.ko. This - new driver component works in conjunction with the nvidia.ko kernel - module to program the display engine of the GPU. - - Users that experience hangs when starting X11 server, or observe - - (II) NVIDIA(0): Validated MetaModes: - (II) NVIDIA(0): "NULL" - - messages in their /var/log/Xorg.0.log file should replace ``nvidia'' - with ``nvidia-modeset'' in /boot/loader.conf or /etc/rc.conf files, - depending on how they prefer to load NVidia driver kernel module. - -20160829: - AFFECTS: users of security/sshguard - AUTHOR: feld@FreeBSD.org - - Sshguard has been updated to 1.7.0. There have been several changes to - this release. Notably the hosts and ipfilter backends are no longer - supported. If you need these backends to be supported and you missed - the survey sent out by upstream I urge you to contact upstream. - - The hosts backend was previously served by security/sshguard directly. - The additional backends were slave ports with package name suffixes. I - have opted to keep the master/slave port relationship but not choose a - specific backend for security/sshguard. Instead it is now a metaport - which will prompt you for which backend you prefer. If no backend is - configured it will depend on security/sshguard-ipfw, which is the - native FreeBSD firewall. This my be surprising to users who depended - on security/sshguard which only provided hosts/TCP Wrappers blocking, - but there is no replacement at this time. - - I would also like to document that sshguard no longer accepts the -e - argument which allowed external scripts to run when sshguard finds a - match. As a result the null backend can no longer be used to create - custom blocking functionality; it only serves as a detection backend. - - If the removed backends return due to user demand they will be added - as slave ports for consistency. I apologize for any inconvenience and - lack of notice on the deprecation of these features. - -20160815: - AFFECTS: users of mail/rspamd* - AUTHOR: vsevolod@FreeBSD.org - - Rspamd users should update Rspamd to 1.3.3 version as soon as possible - and ensure that '/usr/local/etc/rspamd/module.d/fuzzy_check.conf` has - the line `algorithm = "mumhash";` for the "rspamd.com" rule. The more - detailed information could be found on - https://rspamd.com/announce/2016/08/15/rspamd-1.3.3.html - -20160815: - AFFECTS: users of dns/powerdns* - AUTHOR: junovitch@FreeBSD.org - - PowerDNS Authoritative Server and Recursor 4.0.0+ introduce significant - changes to the configuration files, which need to be handled before - restarting the services. As from the Recursor changelog, "The Lua hook - infrastructure was redone using LuaWrapper; old scripts will no longer - work, but new scripts are easier to write under the new interface." - -20160811: - AFFECTS: users of security/libressl - AUTHOR: brnrd@FreeBSD.org - - The port has been updated to the latest stable version 2.4 of LibreSSL. - The shared library versions of the libraries have been bumped. - With this update, the patch for the OPENSSL_VERSION_NUMBER has been - removed. This causes issues with a number of ports. Patches for all - ports for which this issues is known can be found on - https://wiki.freebsd.org/LibreSSL/Ports#OPENSSL_VERSION_NUMBER - - After upgrading, manually update all packages that depend on any of the - libraries provided by LibreSSL (libssl, libcrypto and libtls) since the - versions of these libraries have changed. Normally, you can obtain the - list of dependent software by running the following command: - - # pkg info -r libressl - - Then you should rebuild all ports depending on libressl to avoid dangling - shared library dependencies. Poudriere and pkg handle this correctly, - portmaster and portupgrade users can use the following to rebuild all - dependent ports. - - Portmaster users: - portmaster -r libressl - Portupgrade users: - portupgrade -fr security/libressl |