1 This file documents some of the problems you may encounter when upgrading
2 your ports. We try our best to minimize these disruptions, but sometimes
5 You should get into the habit of checking this file for changes each time
6 you update your ports collection, before attempting any port upgrades.
9 AFFECTS: users of www/node
10 AUTHOR: bhughes@freebsd.org
12 The www/node port has been updated to Node.js v8.1.2, the latest
13 upstream release. This is a major release, including many significant
14 changes. Users are encouraged to read the release announcements before
17 https://nodejs.org/en/blog/release/v8.0.0/
18 https://nodejs.org/en/blog/release/v8.1.0/
21 AFFECTS: users of net-mgmt/zabbix24*
22 AUTHOR: dbaio@FreeBSD.org
24 Zabbix 2.4 has reached end of life and net-mgmt/zabbix24* ports have been
25 removed. Users that have not yet moved to a newer version, should use now
26 net-mgmt/zabbix3-* (LTS release) or net-mgmt/zabbix32-* (Standard release).
28 See more info about Zabbix releases here:
29 http://www.zabbix.com/life_cycle_and_release_policy
32 AFFECTS: users of mail/dcc-dccd
33 AUTHOR: ultima@FreeBSD.org
35 The ALT_HOME option was removed in 1.3.159_1. If this option is being
36 used, please be sure to move the old home directory, /var/dcc to
40 AFFECTS: users of net/rabbitmq
41 AUTHOR: olgeni@FreeBSD.org
43 The rabbitmq-3.6.10_1 port has been changed to use version 19 of
44 the Erlang runtime, because RabbitMQ is not yet compatible with
47 Upgrades to the previous rabbitmq-3.6.10 must be avoided as
48 they can lead to data corruption due to changes in Erlang 20.
51 AFFECTS: users of database/postgresql* and other software using PostgreSQL to run
52 AUTHOR: tz@FreeBSD.org
54 The default version of PostgreSQL has been switched from 9.3 to 9.5.
55 The upgrade procedure can use up twice the space the databases
56 currently needs. If you have a big amount of stored data take a
57 closer look at the manpage of pg_upgrade for avoidance and/or
58 speedup of the upgrade.
60 The upgrade instructions consider a basic usage and do not match
61 complex scenarious like replication, sharding or similar.
65 First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
66 If you have another Version of PostgreSQL installed, for example 9.3.12, your
67 files are named accourding to this.
69 # service postgresql stop
70 # pkg create postgresql93-server postgresql93-contrib
71 # mkdir /tmp/pg-upgrade
72 # tar xf postgresql93-server-9.3.17.txz -C /tmp/pg-upgrade
73 # tar xf postgresql93-contrib-9.3.17.txz -C /tmp/pg-upgrade
74 # mv /usr/local/pgsql/data /usr/local/pgsql/data93
75 # pkg delete -f databases/postgresql93-server databases/postgresql93-contrib databases/postgresql93-client
77 Now update PostgreSQL:
80 # pkg install databases/postgresql95-server databases/postgresql95-contrib
84 # portmaster databases/postgresql95-server databases/postgresql95-contrib
88 # portinstall databases/postgresql95-server databases/postgresql95-contrib
91 After installing the new PostgreSQL version you need to convert
92 all your databases to new version:
94 # service postgresql initdb
95 # 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/"
97 Now the migration is finished. You can start PostgreSQL again with:
99 # service postgresql start
102 AFFECTS: users of editors/calligra
103 AUTHOR: groot@kde.org
105 Calligra has been updated to 3.0.1, which is a KDE Frameworks 5 (KF5)
106 based application. Calligra now uses Qt5 and KF5. The translations have
107 been merged (upstream) into the application, so separate language /
108 translation ports are no longer provided. Krita has been split out
109 (upstream) into a separate application, which is packaged as
110 graphics/krita. Kexi, the visual database applications creator,
111 is packaged separately as databases/kexi.
113 Users of Calligra are encouraged to install Krita and Kexi separately,
114 and to report issues with the upgrade to kde@.
117 AFFECTS: users of net-im/ejabberd
118 AUTHOR: ashish@FreeBSD.org
120 After update to 17.04, there is an issue[1] expected with S2S connections,
121 which can be resolved by adding 'mod_s2s_dialback: {}' to 'modules' section
122 of configuration file.
124 [1] - https://github.com/processone/ejabberd/issues/1700
127 AFFECTS: users of www/kanboard
128 AUTHOR: joneum@FreeBSD.org
130 After update to 1.0.44, there are following breaking changes:
131 * Move calendar to external plugin: https://github.com/kanboard/plugin-calendar
132 * Move Gantt charts to external plugin: https://github.com/kanboard/plugin-gantt
133 * Move Gravatar to external plugin: https://github.com/kanboard/plugin-gravatar
136 AFFECTS: users of Qt 5 in presence of binutils
137 AUTHOR: amdmi3@FreeBSD.org
139 gold linker from binutils 2.28 may produce duplicate library
140 symbols, which makes shared libraries created with it not usable
141 with conventional ld linker.
143 This affects Qt, as qt5-qmake will detect gold and use it to build
144 Qt libraries. Broken libQt5Core will be produced and ports which
145 depend on it will then fail to link with the following errors:
147 ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `__bss_start at Qt_5'
148 ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here
149 ...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `_edata at Qt_5'
150 ...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here
151 ...lib/libQt5Core.so:(.dynamic+0x2b2d0): multiple definition of `_end at Qt_5'
153 Qt5 was fixed to ignore gold. If you see these errors, you
154 need to rebuild qt5-qmake, then all qt5-* ports.
157 AFFECTS: users of sysutils/dsbmd
158 AUTHOR: mk@freeshell.de
160 Due to new configuration variables and semantic changes, users of dsbmd
161 version 0.2 and earlier should consider recreating their dsbmd.conf from
162 the new dsbmd.conf.sample.
165 AFFECTS: users of www/yarn
166 AUTHOR: adamw@FreeBSD.org
168 The default node backend for yarn has switched to www/node. Binary
169 package users should expect the node backend to be switched during
170 the upgrade. To keep the node6 (LTS) backend, rebuild www/yarn with
171 the NODE6 backend option enabled.
174 AFFECTS: users of security/pecl-ssh2
175 AUTHOR: dbaio@FreeBSD.org
177 The security/pecl-ssh2 has been upgraded to version 1.0, and the new
178 version is not compatible with PHP5. If you need PHP5 support, you can
179 find version 0.13 in security/pecl-ssh2-0.
182 AFFECTS: users of sysutils/ansible
183 AUTHOR: lifanov@FreeBSD.org
185 The default value for ansible_python_interpreter has been changed
186 to match the upstream /usr/bin/python. If managing FreeBSD systems,
187 adjust the hosts database to explicitly set a valid python interpreter:
193 ansible_python_interpreter=/usr/local/bin/python2.7
196 AFFECTS: users of security/libressl
197 AUTHOR: brnrd@FreeBSD.org
199 The port has been updated to the latest stable version 2.5 of LibreSSL.
200 The shared library versions of the libraries have been bumped.
202 After upgrading, manually update all packages that depend on any of the
203 libraries provided by LibreSSL (libssl, libcrypto and libtls) since the
204 versions of these libraries have changed. Normally, you can obtain the
205 list of dependent software by running the following command:
207 # pkg info -r libressl
209 Then you should rebuild all ports depending on libressl to avoid dangling
210 shared library dependencies. Poudriere and pkg handle this correctly,
211 portmaster and portupgrade users can use the following to rebuild all
215 portmaster -r libressl
217 portupgrade -fr security/libressl
221 AUTHOR: gecko@FreeBSD.org
223 Firefox 53 or later may fail to build if sem(4) is present (see below)
224 because sysconf(3) still consults the old limits. If you don't plan to
225 run FreeBSD 8.x or older binaries make sure sem(4) isn't loaded during
226 boot or built statically into the kernel.
228 Creating config.status
229 Traceback (most recent call last):
230 File "configure.py", line 124, in <module>
231 sys.exit(main(sys.argv))
232 File "configure.py", line 34, in main
233 return config_status(config)
234 File "configure.py", line 119, in config_status
235 return config_status(args=[], **encode(sanitized_config, encoding))
236 File "python/mozbuild/mozbuild/config_status.py", line 136, in config_status
237 reader = BuildReader(env)
238 File "python/mozbuild/mozbuild/frontend/reader.py", line 886, in __init__
239 self._gyp_worker_pool = ProcessPoolExecutor(max_workers=max_workers)
240 File "python/futures/concurrent/futures/process.py", line 274, in __init__
241 _check_system_limits()
242 File "python/futures/concurrent/futures/process.py", line 263, in _check_system_limits
243 raise NotImplementedError(_system_limited)
244 NotImplementedError: system provides too few semaphores (30 available, 256 necessary)
247 AFFECTS: users of x11-wm/awesome
248 AUTHOR: garga@FreeBSD.org
250 Awesome Window Manager (x11-wm/awesome) was upgraded to 4.1 and its config
251 is not backward compatible with 3.5. A new port was created to keep 3.5
252 version available at x11-wm/awesome3 and it will be available for 6 months
253 until users have time to upgrade configuration.
255 There are references about what has changed in 4.0 at:
257 https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4
259 And configuration porting tips at:
261 https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4
263 If you would like to keep using 3.x, please run the collowing command to
266 # pkg set -n awesome:awesome3
267 # pkg set -o x11-wm/awesome:x11-wm/awesome3
270 AFFECTS: users of Xapian 1.2.x and www/ikiwiki
271 AUTHOR: sunpoet@FreeBSD.org
273 Xapian has been updated to 1.4.3. The 1.2.x series has been renamed with
274 suffix "12". The Perl binding for Xapian 1.4.x is databases/p5-Xapian.
275 Since www/ikiwiki depends on Search::Xapian, it stays with Xapian 1.2.
276 If you would like to keep using 1.2, please run the following commands
277 to update pkg database:
280 # pkg set -n xapian-core:xapian-core12
281 # pkg set -o databases/xapian-core:databases/xapian-core12
284 # pkg set -n p5-Search-Xapian:p5-Search-Xapian12
285 # pkg set -o databases/p5-Search-Xapian:databases/p5-Search-Xapian12
288 # pkg set -n xapian-bindings:xapian-bindings12
289 # pkg set -o databases/xapian-bindings:databases/xapian-bindings12
292 # pkg set -n xapian-omega:xapian-omega12
293 # pkg set -o databases/xapian-omega:databases/xapian-omega12
296 AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl*
297 AUTHOR: timur@FreeBSD.org
299 It turned out that arbitary versions of p5-Parse-Pidl may lead to the
300 hard to explain crashes of the Samba server and utilities(in particular
301 we suspect it was responsible for the troubles with the DC provisioning).
303 So, from now on net/samba* ports use bundled version of Pidl. You need to
304 remove external package from the system:
306 pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44
309 AFFECTS: users of security/openssh-portable
310 AUTHOR: bdrewery@FreeBSD.org
312 The format of several log messages emitted by the packet code has
313 changed to include additional information about the user and
314 their authentication state. Software that monitors ssh/sshd logs
315 may need to account for these changes. For example:
317 Connection closed by user x 1.1.1.1 port 1234 [preauth]
318 Connection closed by authenticating user x 10.1.1.1 port 1234 [preauth]
319 Connection closed by invalid user x 1.1.1.1 port 1234 [preauth]
321 Affected messages include connection closure, timeout, remote
322 disconnection, negotiation failure and some other fatal messages
323 generated by the packet code.
326 AFFECTS: users of samba43
327 AUTHOR: antoine@FreeBSD.org
329 The default version of samba has been switched from 4.3 to 4.4.
330 Upgrade instructions:
332 For package users having samba43 installed indirectly (as a dependency):
335 For package users having samba43 installed directly (leaf port):
337 # pkg install samba44
340 If you want to keep samba43, add DEFAULT_VERSIONS+= samba=4.3 to make.conf
342 If you want to upgrade to samba44, remove samba43 and obsolete packages:
343 # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 samba43 p5-Parse-Pidl
346 # portmaster net/samba44
350 # portinstall net/samba44
354 AFFECTS: net/samba46 and devel/p5-Parse-Pidl
355 AUTHOR: timur@FreeBSD.org
357 New version of Samba port from 4.6 branch is added. Before upgrading please read upgrade notes:
359 https://www.samba.org/samba/history/samba-4.6.0.html
361 For the vfs_fruit users:
363 Users on *BSD must rename the metadata xattr used by vfs_fruit when
364 using the default setting "fruit:metadata = netatalk".
366 Due to a glitch in the Samba xattr API compatibility layer for FreeBSD and a
367 mistake in vfs_fruit, vfs_fruit ended up using the wrong xattr name when
368 configured with "fruit:metadata = netatalk" (default). Instead of the correct
370 org.netatalk.Metadata
376 Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata"
377 which means existing installations must rename this xattrs. For this purpose
378 Samba now includes a new tool `mvxattr`.
381 AFFECTS: net/samba45, net/samba46 and devel/p5-Parse-Pidl
382 AUTHOR: timur@FreeBSD.org
384 While new Uses/samba.mk dosen't work well with slave ports to compile devel/p5-Parse-Pidl
385 for net/samba45 or net/samba46 you need explicitly set in the /etc/make.conf:
387 SAMBA4_PORT=net/samba46
389 explicitly. In the future that shouldn't be necessary.
392 AFFECTS: users of samba36-libsmbclient, samba36-nmblookup samba36-smbclient and samba36
393 AUTHOR: antoine@FreeBSD.org
395 The obsolete samba36-libsmbclient, samba36-nmblookup, samba36-smbclient and samba36 packages/ports were removed
396 and USES=samba was introduced.
397 Upgrade instructions:
399 For package users having those ports installed indirectly (as dependencies):
402 For package users having those ports installed directly (leaf ports):
404 # pkg install samba43
407 Choose you samba version, for instance add DEFAULT_VERSIONS+= samba=4.3 to make.conf
409 Remove obsolete packages:
410 # pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36
413 # portmaster net/samba43
417 # portinstall net/samba43
421 AFFECTS: users of mail/pecl-mailparse
422 AUTHOR: dbaio@bsd.com.br
424 The mail/pecl-mailparse has been upgraded to version 3.0.2, and the new
425 version is not compatible with PHP5. If you need PHP5 support, you can
426 find version 2.1.6 in mail/pecl-mailparse2.
429 AFFECTS: users of textproc/pecl-yaml
430 AUTHOR: dbaio@bsd.com.br
432 The pecl-yaml has been upgraded to version 2.0.0, and the new version is
433 not compatible with PHP5. If you need PHP5 support, you can find version
434 1.3.0 in textproc/pecl-yaml1.
437 AFFECTS: users of python setuptools
438 AUTHOR: antoine@FreeBSD.org
440 The python setuptools ports have been renamed to better match other python ports.
441 Ports users need to rename them so that portupgrade and portmaster do not
442 get confused. For example:
444 pkg set -n py27-setuptools27:py27-setuptools
445 pkg set -o devel/py-setuptools27:devel/py27-setuptools
447 pkg set -n py35-setuptools35:py35-setuptools
448 pkg set -o devel/py-setuptools35:devel/py35-setuptools
451 AFFECTS: users of textproc/ack
452 AUTHOR: sunpoet@FreeBSD.org
454 ack has been renamed back to p5-ack to match our perl naming. You could
455 run the following to update pkg database:
457 # pkg set -n ack:p5-ack
458 # pkg set -o textproc/ack:textproc/p5-ack
461 AFFECTS: users of games/tome4 with paid DLCs
462 AUTHOR: lifanov@FreeBSD.org
464 The Ashes of Urh'Rok and Embers of Rage DLCs have been updated to be
465 compatible with changes introduced in ToME 1.5.0. Users of these DLCs
466 will need to redownload nd place these in $HOME/.t-engine/4.0/addons.
469 AFFECTS: users of mail/thunderbird with Lightning
470 AUTHOR: cmt@FreeBSD.org
472 After changes in the packaging of the Lightning extension, profiles
473 using this extension have to be re-created.
476 AFFECTS: users of devel/mtbl
477 AUTHOR: truckman@FreeBSD.org
479 There is a libmtbl shared library version bump in mtbl version 1.0.0.
480 The affected dependent ports have had PORTREVISION bumps, but you will
481 need to rebuild any applications that link to libmtbl.
484 AFFECTS: sysutils/filebeat sysutils/metricbeat sysutils/packetbeat
485 AUTHOR: girgen@FreeBSD.org
487 The three elasticsearch beats ports have merged into one single port
488 systuils/beats that installs all of the above and some more. The reason is to
489 make the port more maintainable and also that the new heartbeat beat would
490 conflict with sysutils/heartbeat.
493 AFFECTS: devel/libevent2
494 AUTHOR: jbeich@FreeBSD.org
496 libevent2 has been renamed back to libevent as the default version.
497 If you manage out of tree ports make sure to run the following:
499 # pkg set -n libevent2:libevent
500 # pkg set -o devel/libevent2:devel/libevent
503 AFFECTS: users of Qt 4 and Qt 5
504 AUTHOR: kde@FreeBSD.org
506 Following what is already done in Qt 5, the Qt 4 ports no longer install
507 their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most
508 cases). Additionally, the "-qt4" suffix has been dropped from the file names
509 of the binaries that had it, such as "qmake-qt4".
511 The new misc/qtchooser port is now used to choose whether a Qt 4 or Qt 5
512 version of a binary such as "moc", "qmake" or "designer" will be used. By
513 default, the Qt 5 versions are preferred, but that can be changed by setting
514 the QT_SELECT environment variable to "qt4".
516 qtchooser also allows one to seamlessly use other Qt installations for those
517 binaries, which is particularly beneficial to people working on Qt itself or
518 who need their own checkouts.
520 See qtchooser(1) for more information on how to configure qtchooser.
523 AFFECTS: users of www/node*
524 AUTHOR: bradleythughes@fastmail.fm
526 The BUNDLED_SSL option is now enabled by default on FreeBSD 10, since
527 Node.js requires OpenSSL 1.0.2, and FreeBSD 10 is shipped with 1.0.1.
530 AFFECTS: users of graphics/libGL, graphics/libEGL, graphics/libglesv2
531 AUTHOR: kwm@FreeBSD.org
533 The workaround for handling conflicting libraries between the
534 nvidia-driver, libGL, libEGL and libglesv2 ports was removed. If the
535 nvidia-driver port is updated before the other ports, it will remove
536 the libraries of said ports. This is a side effect of how the workaround
537 worked. If this happens reinstalling the affected port is enough.
539 pkg users can run: pkg install -f libGL libEGL libglesv2
542 AFFECTS: users of x11-server/xorg-server
543 AUTHOR: rezny@FreeBSD.org
545 Xorg server has been updated to 1.18.4 and autodetection has changed.
546 The order in which drivers are now attempted is:
547 1) vendor/model specific driver according to PCI IDs
548 2) generic modesetting driver which requires a drm driver with KMS
549 3) scfb, the generic framebuffer driver
550 4) vesa (only if arch is x86)
552 This should minimize the need for xorg.conf files. It is recommended to
553 load the correct KMS driver (i915kms.ko or radeonkms.ko) via rc.conf,
554 i.e. kld_list="i915kms.ko", to ensure correct functionality. Although
555 the vendor drivers may attempt to load the correct drm driver, which
556 does not always work, the modesetting driver assumes the required KMS
557 driver is already loaded and will fail if there is none. The modesetting
558 driver is now recommended as an alternative to the Intel driver; the
559 performance is comparable and stability is better with modesetting. The
560 ATI driver continues to offer better performance than modesetting.
563 AFFECTS: users of security/libressl-devel
564 AUTHOR: brnrd@FreeBSD.org
566 The version 2.5.1 bumps the libcrypto, libssl and libtls shared library
567 versions. You will have to rebuild all packages that depend on
568 libressl-devel. Check the 20160811 libressl entry for more detailed
569 guidance on rebuilding.
572 AFFECTS: users of www/uwsgi
573 AUTHOR: feld@FreeBSD.org
575 The previous disruptive changes to uwsgi for security have been remediated
576 through creation of a dedicated uwsgi user/group and utilizing the
577 uwsgi feature to set socket ownership. The uwsgi daemon by default now
578 has the following properties:
580 * Process runs as uwsgi user and group (UID/GID 165)
581 * Socket mode is 660, still protecting unauthorized access from "other"
582 * Socket ownership is www:www, restoring compatibility
585 AFFECTS: users of devel/ice, devel/py-ice, devel/php5-ice
586 AUTHOR: grembo@FreeBSD.org
588 Since __WORDSIZE as defined by <stdint.h> always reports 32 when using
589 C++98/03 (unless __STDC_LIMIT_MACROS is set explictly), Ice 3.6.3 used
590 "long long" for Int64 instead of "long" on 64-bit platforms by mistake.
591 A workaround has been added in version 3.6.3_2 of these three ports,
592 requiring to upgrade all of them at the same time and to rebuild all
593 custom code that links against them.
596 AFFECTS: users of multimedia/motion
597 AUTHOR: jhale@FreeBSD.org
599 Version 3.x expected the configuration files to reside in:
601 Version 4.x expects the configuration files to reside in:
602 ${LOCALBASE}/etc/motion
603 This was unfortunately overlooked when the port was updated to 4.x, but it
604 has now been fixed to install the default configuration file in the new
605 location. The rc script now checks for motion.conf in the new location.
607 While you may be able to simply copy your old motion.conf to the new location,
608 it is recommended to review ${LOCALBASE}/etc/motion/motion.conf and make
609 changes to it based on your old ${LOCALBASE}/etc/motion.conf as some options
610 have been added and removed.
612 Further, if you use motion with multiple cameras and have
613 ${LOCALBASE}/etc/thread[0-9].conf files, they should be moved to
614 ${LOCALBASE}/etc/motion as well. These files are deprecated and should be
615 renamed to camera[0-9].conf and in motion.conf, lines like:
616 thread /usr/local/etc/thread1.conf
617 Should be converted to:
618 camera /usr/local/etc/motion/camera1.conf
621 AFFECTS: users of www/uwsgi
622 AUTHOR: feld@FreeBSD.org
624 The default socket mode for uwsgi as 777 is a severe security concern.
625 This has been remediated by changing the rc script to default to 600.
626 The mode is configurable with rc.conf values: uwsgi_socket_mode="600"
627 or for a profile named "www", uwsgi_www_socket_mode="600".
630 AFFECTS: users of security/tinc
631 AUTHOR: dinoex@FreeBSD.org
633 this version of tinc requires all nodes in the VPN to be linked with a
634 version of OpenSSL or LibreSSL that supports the AES256 and SHA256
639 AFFECTS: users of databases/mysql56-server
640 AUTHOR: feld@FreeBSD.org
642 databases/mysql56-server was updated to 5.6.35 which included backported
643 rc script changes from the mysql57-server port. This broke mysql_optfile in
644 rc.conf and also forced a sample my.cnf if none existed. MySQL has
645 some parameters which cannot be changed after a database has been
646 created, so this caused MySQL to fail to start.
648 This change was reverted in mysql56-server-5.6.35_1
650 An additional change was made in mysql56-server-5.6.35_2 to prevent
651 automatic loading of a sample my.cnf which was causing issues for
652 users who were running without a my.cnf.
655 AFFECTS: users of EoL'ed FreeBSD versions (<10.3, 11 prior to 11.0)
656 AUTHOR: amdmi3@FreeBSD.org
658 The ports system will now refuse to build anything if it's run on
659 outdated system version. This protects users from unexpected build
660 failures after code to support EoL'ed systems is removed from the
661 tree. You may define ALLOW_UNSUPPORTED_SYSTEM to override this and
662 allow builds, but no support will be provided in case of failures.
665 AFFECTS: users of java/wildfly10
666 AUTHOR: olgeni@FreeBSD.org
668 The java/wildfly10 port has been updated to 10.1.0. To complete the
669 migration you must copy your existing configuration (directories
670 "appclient", "standalone", and "domain") from /usr/local/wildfly-10.0.0
671 to /usr/local/wildfly10.
674 AFFECTS: users of net-mgmt/librenms
675 AUTHOR: dvl@FreeBSD.org
677 The following is recommended for /var/db/mysql/my.cnf
679 NOTE: these are global settings. Please read this first:
681 http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
684 innodb_file_per_table=1
688 AFFECTS: users of lang/ruby22
689 AUTHOR: swills@FreeBSD.org
691 The default ruby version has been updated from 2.2 to 2.3.
693 If you compile your own ports you may keep 2.2 as the default version by
694 adding the following lines to your /etc/make.conf file:
697 # Keep ruby 2.2 as default version
699 DEFAULT_VERSIONS+=ruby=2.2
701 If you wish to update to the new default version, you need to first stop any
702 software that uses ruby. Then, you will need to follow these steps, depending
703 upon how you manage your system.
705 If you use pkgng, simply upgrade:
708 If you use portmaster, install new ruby, then rebuild all ports that depend
710 # portmaster -o lang/ruby23 lang/ruby22
711 # portmaster -R -r ruby-2.3
713 If you use portupgrade, install new ruby, then rebuild all ports that depend
716 # pkg delete -f ruby portupgrade
717 # make -C /usr/ports/ports-mgmt/portupgrade install clean
718 # pkg set -o lang/ruby22:lang/ruby23
719 # portupgrade -x ruby-2.3.\* -fr lang/ruby23
722 AFFECTS: multimedia/ffmpeg
723 AUTHOR: jbeich@FreeBSD.org
725 OPTIMIZED_CFLAGS switched to only use vendor optimizations which
726 means -ffast-math -fno-finite-math-only are no longer applied. If
727 you did like the former behavior consider adding
729 # multimedia/ffmpeg/Makefile.local
730 OPTIMIZED_CFLAGS_CFLAGS += -ffast-math -fno-finite-math-only
735 .if ${.CURDIR:M*/multimedia/ffmpeg}
736 CFLAGS += -ffast-math -fno-finite-math-only
740 AFFECTS: users of x11/xfce4-terminal
741 AUTHOR: olivierd@FreeBSD.org
743 The port has been updated to the latest stable version 0.8.2.
744 Please, don't active the hidden 'MiscSlimTabs' option in
745 ~/.config/xfce4/terminal/terminalrc, it requires Gtk+ > 3.20.
748 AFFECTS: users of multimedia/mlt
749 AUTHOR: avilla@FreeBSD.org
751 MLT Qt plugins have been moved to their own ports, mlt-qt4 and
752 mlt-qt5. Please, uninstall multimedia/mlt before you update:
757 AFFECTS: users of security/openvpn, security/openvpn-polarssl
758 AUTHOR: Matthias Andree <mandree@FreeBSD.org>
760 The OpenVPN ports have been updated to the new upstream release v2.4,
761 and their predecessors preserved as openvpn23 and openvpn23-polarssl,
762 respectively. Note that for the new v2.4 release, the
763 openvpn-polarssl port has been renamed to openvpn-mbedtls to match the
764 upstream library's new name.
767 AFFECTS: users of www/nghttp2
768 AUTHOR: sunpoet@FreeBSD.org
770 nghttp2 has been split into 2 ports: www/libnghttp2 for core library and
771 www/nghttp2 for the rest. Please uninstall nghttp2 before you update
775 AFFECTS: mail/thunderbird, www/seamonkey
776 AUTHOR: gecko@FreeBSD.org
778 ENIGMAIL is no longer provided as part of the ports after upstream
779 dropped binary components in 1.9. Go to Tools -> Add-ons Manager
780 then type "enigmail" in the search box to install.
783 AFFECTS: users of devel/skalibs, lang/execline, sysutils/s6
784 AUTHOR: Colin Booth <colin-ports@heliocat.net>
786 skalibs has undergone a major version bump and compatibility is not
787 guaranteed for software with a runtime dependency on
788 libskarnet.so.2.3.9.0. This will not affect lang/execline or
789 sysutils/s6 as those are statically linked against libskarnet.a.
791 execline has undergone a major version bump and compatibility is not
792 guaranteed for software with a runtime dependency on
793 libexecline.so.2.1.4.5. This will not affect sysutils/s6 as all s6
794 programs are statically linked against libexecline.a.
796 s6 has undergone a major version bump and compatibility is not
797 guaranteed for software with a runtime dependency on
798 libs6.so.2.2.4.3. Additionally, s6-applyuidgid and s6-setuidgid
799 have moved from $PREFIX/sbin to $PREFIX/bin. Any scripts calling
800 those utilities that are not relying on $PATH resolution to find
801 them will need to be rewritten.
804 AFFECTS: users of www/node
805 AUTHOR: bradleythughes@fastmail.fm
807 The www/node port has been updated to node.js v7.2.0, the latest
808 upstream release. A new port, www/node6, has been created for the
809 v6.x LTS branch. Users wanting to stay on v6.x can replace www/node
810 with www/node6 with one of the following commands:
812 # pkg set -o www/node:www/node6
814 # portmaster -o www/node6 www/node
816 # portupgrade -o www/node6 www/node
819 AFFECTS: Users of textproc/p5-Search-Elasticsearch
820 AUTHOR: tj@FreeBSD.org
822 As of the 5.01 release of ths package, the client libraries for older
823 versions of Elasticsearch have started to be shipped seperately. If you are
824 using this library to access a none 5.X server you will need to install one of
825 the textproc/p5-Search-Elasticsearch-Client-* ports.
828 AFFECTS: Users of security/gpgme-*
829 AUTHOR: jhale@FreeBSD.org
831 Gpgme has been updated to 1.8.0.
832 With it comes the removal of libgpgme-pthread.so in favor of using
833 libgpgme.so itself as the thread-safe library. Ports that may have
834 linked to -lgpgme-pthread will now just link to -lgpgme. PORTREVISION
835 has been bumped on all ports with a dependency on security/gpgme.
837 The Python module provided by security/py-gpgme has been renamed
838 from pyme3 to gpg, as well.
843 portupgrade -fr security/gpgme
846 AFFECTS: Users of graphics/tiff
847 AUTHOR: antoine@FreeBSD.org
849 The tiff port was updated to 4.0.7.
850 The following tools are removed from this release: bmp2tiff, gif2tiff, ras2tiff, rgb2ycbcr and thumbnail.
853 AFFECTS: Users of sysutils/bareos-*
854 AUTHOR: rand@iteris.com
856 Bareos v1.6.x changed the configuration scheme, from one configuration
857 file per Bareos component (file daemon, storage daemon, and director)
858 to several configuration files, in several directories, for each
859 component. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html
861 The new scheme will use all files named *.conf in the directory
862 hierarchies for each component:
864 /usr/local/etc/bareos/bareos-dir.d/
865 /usr/local/etc/bareos/bareos-fd.d/
866 /usr/local/etc/bareos/bareos-sd.d/
868 To retain the old configuration scheme of one file per component add
869 appropriate lines such as these to your /etc/rc.conf:
871 bareos_dir_config="/usr/local/etc/bareos/bareos-dir.conf"
872 bareos_fd_config="/usr/local/etc/bareos/bareos-fd.conf"
873 bareos_sd_config="/usr/local/etc/bareos/bareos-sd.conf"
876 AFFECTS: users of devel/libosinfo
877 AUTHOR: novel@FreeBSD.org
879 The libosinfo port was separated into three different ports
880 to follow the upstream split:
882 - sysutils/osinfo-db-tools: contains the CLI tools
883 - misc/osinfo-db: contains database with OS data
884 - devel/libosinfo: the library
886 As osinfo-db-tools now ships binaries that previously were
887 part of libosinfo, it's required to delete the old libosinfo
888 package to prevent conflict because of same files installation:
890 # pkg delete libosinfo
892 And then install the new version.
895 AFFECTS: users of security/heimdal
896 AUTHOR: hrs@FreeBSD.org
898 Heimdal in the base system and security/heimdal <= 1.5.3_6 use
899 Berkeley DB to store principals into /var/heimdal/heimdal.db and
900 the database format is version 3 by default. On the other hand,
901 security/heimdal 1.5.3_7 or newer use the newer version of
902 Berkeley DB and the database format is version 9.
903 These two versions are not compatible with each other. If there is
904 a mismatch between Heimdal utilities and its database format,
905 you will get an error like the following:
907 # /usr/local/sbin/kadmin -l dump
908 BDB0641 __db_meta_setup: /var/heimdal/heimdal.db: unexpected file type or format
909 kadmin: hdb_open: opening /var/heimdal/heimdal: Invalid argument
911 This mismatch can occur in the following three cases:
913 1. You used Heimdal in the base system and switch to use security/heimdal
914 after creating /var/db/heimdal.db.
916 2. You used security/heimdal >= 1.5.3_7 and switch to use one in the
919 3. You used security/heimdal < 1.5.3_7 and upgrade it to 1.5.3_7 or later.
921 To fix this mismatch, you need to dump contents of heimdal.db and
922 rebuild the database by using kadmin(8) utility.
924 If you use Heimdal in the base system or older versions of
925 security/heimdal, and plan to switch to use
926 security/heimdal >= 1.5.3_7, execute the following command
927 *after* creating a backup copy of /var/heimdal and installing
930 # /usr/bin/kadmin -l dump /var/heimdal/heimdal.db.dump
931 # rm /var/heimdal/heimdal.db
932 # /usr/local/sbin/kadmin -l load /var/heimdal/heimdal.db.dump
933 # rm /var/heimdal/heimdal.db.dump
935 The above example assumes security/heimdal is installed into
936 /usr/local. If your base system is compiled with WITHOUT_KERBEROS
937 use the following instead:
939 # db_dump185-5 /var/heimdal/heimdal.db | db_load-5 /var/heimdal/heimdal.db.new
940 # chown 0600 /var/heimdal/heimdal.db.new
941 # mv /var/heimdal/heimdal.db.new /var/heimdal/heimdal.db
943 db_dump and db_load utilitites are installed by database/db5 as
944 dependency of security/heimdal.
946 If you want to switch from security/heimdal to Heimdal in the base
947 system, use the following:
949 # /usr/local/sbin/kadmin -l dump /var/heimdal/heimdal.db.dump
950 # rm /var/heimdal/heimdal.db
951 # /usr/bin/kadmin -l load /var/heimdal/heimdal.db.dump
952 # rm /var/heimdal/heimdal.db.dump
955 AFFECTS: users of security/heimdal
956 AUTHOR: hrs@FreeBSD.org
958 kadmin(8) in heimdal-1.5.3_5 and prior did not create a database
959 in /var/heimdal in Berkeley DB format which kdc(8) required. This
960 problem has been fixed in heimdal-1.5.3_6.
963 AFFECTS: users of mail/mu4e and mail/mu4e-maildirs
964 AUTHOR: hrs@FreeBSD.org
966 The package name of mail/mu4e* have been changed from mu4e* to
967 mu4e*-emacsNN. When upgrading the older versions, this change can
968 cause the following error which prevents it from upgrading:
970 pkg-static: mu4e-emacs25-0.9.16 conflicts with mu4e-0.9.16 (installs files into the same place).
972 If this error occurs, please remove the old packages by using
973 "pkg delete" manually:
975 # pkg delete mu4e-0.9.16 mu4e-maildirs-0.8.20160126_1
978 AFFECTS: users of lang/perl5*
979 AUTHOR: mat@FreeBSD.org
981 The default Perl version has been switched to Perl 5.24. If you are using
982 binary packages to upgrade your system, you do not have anything to do, pkg
983 upgrade will do the right thing. For the other people, assuming you are
984 migrating from 5.20 to 5.24, do:
986 First, add to /etc/make.conf:
988 DEFAULT_VERSIONS+= perl5=5.24
991 portupgrade -o lang/perl5.24 -f lang/perl5.20
993 You can now remove the DEFAULT_VERSIONS line added earlier
996 Then you will need to rebuild everything that uses libperl.so, you
999 portupgrade -f `pkg shlib -qR libperl.so.5.20`
1002 portmaster -o lang/perl5.24 lang/perl5.20
1004 You can now remove the DEFAULT_VERSIONS line added earlier
1007 Then you will need to rebuild everything that uses libperl.so, you
1010 portmaster -f `pkg shlib -qR libperl.so.5.20`
1013 AFFECTS: users of security/acme-client
1014 AUTHOR: brnrd@FreeBSD.org
1016 The default configuration paths have changed from 'letsencrypt' to
1017 'acme'. Rename the directories used accordingly
1019 mv /usr/local/etc/letsencrypt /usr/local/etc/acme
1020 mv /usr/local/etc/ssl/letsencrypt /usr/local/etc/ssl/acme
1021 mv /usr/local/www/letsencrypt /usr/local/www/acme
1023 Check your scripts to ensure proper operation.
1026 AFFECTS: users of mail/squirrelmail
1027 AUTHOR: adamw@FreeBSD.org
1029 For better php70 support, the squirrelmail port has switched from
1030 PEAR database access to PDO. If you are using squirrelmail with
1031 a database backend, you'll need to install a corresponding PDO
1032 database module, such as php56-pdo_sqlite.
1035 AFFECTS: users of security/srm
1036 AUTHOR: rakuco@FreeBSD.org
1038 srm has been updated from 1.2.12 to 1.2.15. Since version 1.2.14,
1039 srm defaults to using its "simple" mode to overwrite files (one pass
1040 writing 0x00 to the files) instead of the 35-pass Gutmann method.
1043 AFFECTS: users of irc/quassel
1044 AUTHOR: woodsb02@FreeBSD.org
1046 Quassel is now split into two ports / packages; one for providing
1047 the server backend (irc/quassel-core), and one for providing the
1048 client front-end (irc/quassel). Alternatively, the irc/quassel
1049 port can be built with the MONO option enabled to also install
1050 the client and server combined into a single monolithic binary.
1053 AFFECTS: users of security/openssl and security/openssl-devel
1054 AUTHOR: brnrd@FreeBSD.org
1056 The shared library versions of OpenSSL have been bumped to avoid
1057 issues with ports' and base's OpenSSL not being binary compatible.
1059 Please rebuild all ports that depend on OpenSSL if you use OpenSSL
1062 If you use portmaster:
1063 portmaster -r openssl
1064 If you use portupgrade:
1065 portupgrade -fr security/openssl
1068 AFFECTS: users of net-p2p/deluge
1069 AUTHOR: rm@FreeBSD.org
1071 Deluge port has been split out onto CLI part and GUI part. So if user
1072 only needs deluged, net-p2p/deluge-cli should be installed. For full
1073 deluge installation, including GTK+ GUI client, net-p2p/deluge should
1074 be installed as a usual.
1076 Old deluge package should be removed manually first:
1080 After that install preferred deluge package as usual.
1083 AFFECTS: users of x11/xfce4-terminal
1084 AUTHOR: olivierd@FreeBSD.org
1086 The port has been updated to the latest stable version 0.8.0.
1087 A warning appears each time we open new tab:
1089 Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate
1092 This issue will disappear with Gtk > 3.21.
1095 AFFECTS: users of lang/python3
1096 AUTHOR: antoine@FreeBSD.org
1098 The default version of python3 has changed from 3.4 to 3.5.
1099 If you wish to stick with older version, add "python3=3.4" to your
1100 DEFAULT_VERSIONS variable in /etc/make.conf. To upgrade:
1102 If using portupgrade:
1103 # portupgrade -o lang/python35 lang/python34
1105 If using portmaster:
1106 # portmaster -o lang/python35 lang/python34
1109 AFFECTS: Users of net-im/ejabberd
1110 AUTHOR: ashish@FreeBSD.org
1112 Before upgrading ejabberd to 16.09, please make sure to backup your
1113 ejabberd data using:
1115 % sudo -u ejabberd -H ejabberdctl backup /path/to/backup/file
1117 In some cases, ejabberd may fail to start, for which a workaround is to
1118 remove the schema.DAT file from /var/spool/ejabberd before starting, and
1119 then restoring everything from the backup using:
1121 % sudo -u ejabberd -H ejabberdctl restore /path/to/backup/file
1125 https://github.com/processone/ejabberd/issues/1305
1128 AFFECTS: Users of audio/squeezeboxserver (now audio/logitechmediaserver)
1129 AUTHOR: woodsb02@FreeBSD.org
1131 With the rename of the audio/squeezeboxserver port to
1132 audio/logitechmediaserver, the server and database are now installed in
1133 different locations by default (/usr/local/share/logitechmediaserver and
1134 /var/db/logitechmediaserver respectively).
1136 If you were an existing user of audio/squeezeboxserver, you should
1137 consider backing up you server configuration files and database before
1138 upgrading to audio/logitechmediaserver. If you wish to override the
1139 default locations for storing the server and database, you can set the
1140 SLIMDIR and SLIMDBDIR variables in your /etc/make.conf when building
1141 the audio/logitechmediaserver port.
1144 AFFECTS: mail/roundcube-carddav
1145 AUTHOR: gahr@FreeBSD.org
1147 There is no upgrade path from the 1.0 version. You'll need to:
1149 1. Log off from Roundcube.
1150 2. Manually drop all carddav_* tables from your db backend.
1151 3. Upgrade the mail/roundcube-carddav port.
1153 The new tables will be created upon login. The CardDAV plugin will need to be
1156 If you are running php < 7.0.0, you'll need to set the plugin option:
1157 $prefs['_GLOBAL']['suppress_version_warning'] = true;
1159 See https://github.com/blind-coder/rcmcarddav/issues/165 for details.
1162 AFFECTS: emulators/ppsspp
1163 AUTHOR: jbeich@FreeBSD.org
1165 Qt* GUI was split into separate ports:
1167 emulators/ppsspp-qt4
1168 emulators/ppsspp-qt5
1171 AFFECTS: sysutils/android-file-transfer
1172 AUTHOR: jbeich@FreeBSD.org
1174 Qt* GUI was split into separate ports:
1176 sysutils/android-file-transfer-qt4
1177 sysutils/android-file-transfer-qt5
1180 AFFECTS: users of databases/pglogical, databases/pglogical-output
1181 AUTHOR: matthew@FreeBSD.org
1183 As of version 1.2.0, databases/pglogical-output has been merged into
1184 databases/pglogical. portmaster or portupgrade users should delete
1185 pglogical-output manually before upgrading.
1188 AFFECTS: users of mail/sieve-connect
1189 AUTHOR: alexey@renatasystems.org
1191 Version 0.88 contains two breaking changes:
1192 1. If the Sieve server does not offer STARTTLS, then connections should now
1194 2. When deriving a remote script name from the local filename, use the
1195 basename and strip off directories.
1197 For additional information see:
1198 http://mail.globnix.net/pipermail/sieve-connect-announce/2016/000012.html
1201 AFFECTS: users of net/vtun
1202 AUTHOR: cy@FreeBSD.org
1204 The VTUN_EXTENDED_MODE option has been replaced by -e command line
1208 AFFECTS: users of www/nginx-devel
1209 AUTHOR: osa@FreeBSD.org
1211 Nginx now creates logs under /var/log/nginx/ and changes default log
1212 names from "nginx-access.log" and "nginx-error.log" to "access.log" and
1213 "error.log" respectively. This is important for the error log because
1214 the location is encoded and touched by nginx during startup regardless
1215 of the configured location for the error log.
1217 See http://trac.nginx.org/nginx/ticket/147 for additional information
1218 on why this happens.
1221 AFFECTS: users of deskutils/xfce4-volumed-pulse
1222 AUTHOR: olivierd@FreeBSD.org
1224 The port has been updated to the latest stable version 0.2.2.
1225 Support of xfce4-mixer has been removed, so you can delete
1226 its properties with the following command:
1228 xfconf-query -c xfce4-mixer -p / -rR
1231 AFFECTS: users of security/letsencrypt.sh
1232 AUTHOR: riggs@FreeBSD.org
1234 The config filename has been changed upstream from "config.sh"
1235 to "config". Users must rename the current config file manually.
1236 In addition, the default WELLKNOWN location has been changed to
1237 %%PREFIX%%/www/letsencrypt. In order to use the previous default
1238 location, the config file must be updated manually as well.
1241 AFFECTS: users of math/galculator
1242 AUTHOR: woodsb02@FreeBSD.org
1244 galculator now uses GTK3 by default. An option exists in the port to revert
1248 AFFECTS: uses of www/nginx
1249 AUTHOR: marino@FreeBSD.org
1251 Nginx now creates logs under /var/log/nginx/ and changes default log
1252 names from "nginx-access.log" and "nginx-error.log" to "access.log" and
1253 "error.log" respectively. This is important for the error log because
1254 the location is encoded and touched by nginx during startup regardless
1255 of the configured location for the error log.
1257 See http://trac.nginx.org/nginx/ticket/147 for additional information
1258 on why this happens.
1261 AFFECTS: users of databases/postgresql96-server
1262 AUTHOR: girgen@FreeBSD.org
1264 The default unix user used by the PostgreSQL daemon has changed to
1265 `postgres' to reflect the long time upstream's convention. Any scripts
1266 you have using the old `pgsql' unix user should be modified when upgrading to
1267 PostgreSQL version 9.6. Older versions of PostgreSQL will continue using
1268 `pgsql' until their end-of-life.
1270 For users with UTF-8 locales in the database: The ICU patch is *activated by
1271 default* for the PostgreSQL-9.6 server. For previous versions it was optional
1272 and default off, but this has changed. Please read the entry here below from
1273 20160811 and understand the consequences of changing between ICU and system
1274 locale for database collation (short version: don't). pg_upgrade requires the
1275 collation method to be the same (or a reindex), while pg_dump/restore does not.
1277 Also, the default home directory for the postgres user is now
1278 /var/db/postgres, and the default data directory for PostgreSQL 9.6 is
1279 /var/db/postgres/data96.
1282 AFFECTS: users of x11/nvidia-driver
1283 AUTHOR: cem@FreeBSD.org
1285 The NVidia driver has been updated to version 367.35. Starting with
1286 version 358.09, new kernel module was added, nvidia-modeset.ko. This
1287 new driver component works in conjunction with the nvidia.ko kernel
1288 module to program the display engine of the GPU.
1290 Users that experience hangs when starting X11 server, or observe
1292 (II) NVIDIA(0): Validated MetaModes:
1293 (II) NVIDIA(0): "NULL"
1295 messages in their /var/log/Xorg.0.log file should replace ``nvidia''
1296 with ``nvidia-modeset'' in /boot/loader.conf or /etc/rc.conf files,
1297 depending on how they prefer to load NVidia driver kernel module.
1300 AFFECTS: users of security/sshguard
1301 AUTHOR: feld@FreeBSD.org
1303 Sshguard has been updated to 1.7.0. There have been several changes to
1304 this release. Notably the hosts and ipfilter backends are no longer
1305 supported. If you need these backends to be supported and you missed
1306 the survey sent out by upstream I urge you to contact upstream.
1308 The hosts backend was previously served by security/sshguard directly.
1309 The additional backends were slave ports with package name suffixes. I
1310 have opted to keep the master/slave port relationship but not choose a
1311 specific backend for security/sshguard. Instead it is now a metaport
1312 which will prompt you for which backend you prefer. If no backend is
1313 configured it will depend on security/sshguard-ipfw, which is the
1314 native FreeBSD firewall. This my be surprising to users who depended
1315 on security/sshguard which only provided hosts/TCP Wrappers blocking,
1316 but there is no replacement at this time.
1318 I would also like to document that sshguard no longer accepts the -e
1319 argument which allowed external scripts to run when sshguard finds a
1320 match. As a result the null backend can no longer be used to create
1321 custom blocking functionality; it only serves as a detection backend.
1323 If the removed backends return due to user demand they will be added
1324 as slave ports for consistency. I apologize for any inconvenience and
1325 lack of notice on the deprecation of these features.
1328 AFFECTS: users of mail/rspamd*
1329 AUTHOR: vsevolod@FreeBSD.org
1331 Rspamd users should update Rspamd to 1.3.3 version as soon as possible
1332 and ensure that '/usr/local/etc/rspamd/module.d/fuzzy_check.conf` has
1333 the line `algorithm = "mumhash";` for the "rspamd.com" rule. The more
1334 detailed information could be found on
1335 https://rspamd.com/announce/2016/08/15/rspamd-1.3.3.html
1338 AFFECTS: users of dns/powerdns*
1339 AUTHOR: junovitch@FreeBSD.org
1341 PowerDNS Authoritative Server and Recursor 4.0.0+ introduce significant
1342 changes to the configuration files, which need to be handled before
1343 restarting the services. As from the Recursor changelog, "The Lua hook
1344 infrastructure was redone using LuaWrapper; old scripts will no longer
1345 work, but new scripts are easier to write under the new interface."
1348 AFFECTS: users of security/libressl
1349 AUTHOR: brnrd@FreeBSD.org
1351 The port has been updated to the latest stable version 2.4 of LibreSSL.
1352 The shared library versions of the libraries have been bumped.
1353 With this update, the patch for the OPENSSL_VERSION_NUMBER has been
1354 removed. This causes issues with a number of ports. Patches for all
1355 ports for which this issues is known can be found on
1356 https://wiki.freebsd.org/LibreSSL/Ports#OPENSSL_VERSION_NUMBER
1358 After upgrading, manually update all packages that depend on any of the
1359 libraries provided by LibreSSL (libssl, libcrypto and libtls) since the
1360 versions of these libraries have changed. Normally, you can obtain the
1361 list of dependent software by running the following command:
1363 # pkg info -r libressl
1365 Then you should rebuild all ports depending on libressl to avoid dangling
1366 shared library dependencies. Poudriere and pkg handle this correctly,
1367 portmaster and portupgrade users can use the following to rebuild all
1371 portmaster -r libressl
1373 portupgrade -fr security/libressl
1376 AFFECTS: users of databases/postgresqlNN-server with ICU patch
1377 AUTHOR: girgen@FreeBSD.org
1379 The ICU patch is added to the PostgreSQL-9.5 server. Please note that you
1380 must never change between using the ICU patch and using system locale for
1381 the same database cluster without REINDEXing all TEXT/VARCHAR columns, or
1382 dump and restore your database. Failing to do so will result in corrupted
1383 indexes due to the differences between the locale definitions. ICU will
1384 always be the better choice for speed and correctness.
1386 Also, the ICU patch used to support other Unicode encodings than UTF-8,
1387 but that has been removed due to lack of demand and the complicated testing
1388 required. If you use another Unicode encoding and rely on ICU for collation,
1389 please refrain from upgrading the postgresql server and instead contact the
1393 AFFECTS: users of emulators/virtualbox-ose
1394 AUTHOR: jkim@FreeBSD.org
1396 VirtualBox has been updated to 5.0.26 and it is incompatible with old
1397 kernel modules. You should upgrade emulators/virtualbox-ose-kmod and
1398 load new kernel modules before starting new version, e.g.,
1400 # service vboxnet restart
1403 AFFECTS: users of games/stonesoup-*
1404 AUTHOR: lifanov@mail.lifanov.com
1406 The WIZARD option has been renamed to NOWIZARD and is now an opt-out to
1407 better reflect the upstream. If you run a shared game server and would
1408 like the Wizard mode support disabled, please update port options.
1411 AFFECTS: users of www/awstats
1412 AUTHOR: adamw@FreeBSD.org
1414 The directory containing icons has changed from ".../icons" to ".../icon".
1415 awstats has, in its suggested configuration file, contained an alias
1416 from /awstatsicons. After applying the awstats-7.5 update, you must
1417 update that alias to point to /usr/local/www/awstats/icon (just remove
1418 the "s" at the end).
1421 AFFECTS: users of sysutils/screen
1422 AUTHOR: cy@FreeBSD.org
1424 GNU Screen was updated to version 4.4.0 (r417201). Note that there was
1425 fix to screen message structure field responsible for $TERM handling,
1426 making it impossible to attach to older versions.
1429 AFFECTS: users of databases/mysql57-*
1430 AUTHOR: riggs@FreeBSD.org
1432 The default location for my.cnf has changed from "/var/db/mysql/my.cnf"
1433 to "/usr/local/etc/mysql/my.cnf". Existing my.cnf files must be merged
1434 manually with the new default and moved to the new location. To
1435 continue using the my.cnf file at the old location, set "mysql_optfile"
1436 in /etc/rc.conf to point to the location of the existing my.cnf file.