You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

18290 lines

  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
  3. they are unavoidable.
  4. You should get into the habit of checking this file for changes each time
  5. you update your ports collection, before attempting any port upgrades.
  6. 20200602:
  7. AFFECTS: users of www/radicale
  8. AUTHOR:
  9. Migration from radicale 1.x to 2.x requires that you export the storage
  10. with radicale 1.1.6 before updating.
  11. Migration instructions are available at:
  13. 20200602:
  14. AFFECTS: users of sysutils/py-salt
  15. AUTHOR:
  16. This port is moved to sysutils/py-salt-2019 and sysutils/py-salt was
  17. updated to version 3000.
  18. If you wish to use pysalt-2019 in the future, you might run the
  19. following command:
  20. # pkg set -o sysutils/py-salt:sysutils/py-salt-2019
  21. # pkg upgrade
  22. 20200531:
  23. AFFECTS: users of mail/postfix-policyd-spf-python
  24. AUTHOR:
  25. This port is now deprecated because upstream project is superseded by its
  26. successor. So uninstall this port and install mail/py-spf-engine instead.
  27. Keep in mind that the path of configuration file is changed from
  28. ${PREFIX}/etc/postfix-policyd-spf-python/policyd-spf.conf to
  29. ${PREFIX}/etc/python-policyd-spf/policyd-spf.conf. So you need to move
  30. it to new location unless you use the default one without changing.
  31. 20200526:
  32. AFFECTS: users of databases/mariadb104-client, databases/mariadb104-server
  33. AUTHOR:
  34. The ports now add sample configuration files to /usr/local/etc/mysql. You
  35. must merge your client configation with the conf.d/client.cnf and your
  36. server configuration with conf.d/server.cnf.
  37. 20200518:
  38. AFFECTS: users of converters/libiconv
  39. AUTHOR:
  40. Support for the Japanese specific patches have been discontinued.
  41. These were previously added in a nondefault ports options, for people who
  42. needed them.
  43. If you still need them, it might be possible to create a port of libiconv 1.14
  44. which includes those patches.
  45. 20200517:
  46. AFFECTS: users of x11/sddm
  47. AUTHOR:
  48. The home directory of sddm user has been moved to /var/lib/sddm. It is advised
  49. to run following commands as root after updating the package:
  50. # pw usermod -n sddm -d /var/lib/sddm
  51. # pwd_mkdb /etc/master.passwd
  52. # mv /usr/local/etc/sddm/home/state.conf /var/lib/sddm/state.conf
  53. # rm -rf /usr/local/etc/sddm/home
  54. Otherwise, SDDM will keep using /usr/local/etc/sddm/home/ as its HOME.
  55. 20200515:
  56. AFFECTS: users of devel/libphutil, devel/arcanist-lib, devel/phabricator
  57. AUTHOR:
  58. Upstream fully deprecated devel/libphutil and merged its functionality
  59. into devel/arcanist-lib and devel/phabricator. As a result, the
  60. devel/libphutil port will be removed from the ports tree.
  61. After upgrading devel/(arcanist-lib|phabricator) to version 20200514, it is
  62. recommended to remove the orphaned libphutil package by running:
  63. # pkg delete php\*-libphutil
  64. Alternatively, 'pkg autoremove' will also work as expected, but might
  65. remove orphaned packages unrelated to this update.
  66. 20200505:
  67. AFFECTS: users of net-im/pidgin-rocketchat
  68. AUTHOR:
  69. This port has been turned into a libpurple plugin (net-im/purple-rocketchat)
  70. to support other libpurple clients than pidgin.
  71. This also changes some dependencies and you should run the following command
  72. to prevent pidgin from being autoremoved.
  73. # mark pidgin as being not automatically installed
  74. pkg set -A 0 pidgin
  75. 20200504:
  76. AFFECTS: users of x11-wm/hs-xmonad
  77. AUTHOR:
  78. From now, it is recommended to use "build script" method to compile XMonad
  79. config. See for general info and
  80. port's pkg-message for concrete steps.
  81. 20200503:
  82. AFFECTS: users of net-mgmt/librenms
  83. AUTHOR:
  84. Polling via cronjob is deprecated as of release 1.63
  85. see see
  86. Please migrate to the Dispatch Service:
  88. These steps should get you running:
  89. * comment out the crontab entries listed above under PYPOLLER
  90. * populate %%WWWDIR%%/.env with:
  91. * APP_KEY - see farther below for how to create
  92. * NODE_ID - see just below for how to create
  93. * DB_HOST
  97. * you can create a NODE_ID with: php -r 'echo uniqid() . "\n";'
  98. * sysrc librenms_enable="YES"
  99. * service librenms start
  100. 20200501:
  101. AFFECTS: users of www/phpmyfaq
  102. AUTHOR:
  103. phpMyFAQ has been updated to 3.0.2, old templates are not compatible with
  104. this new version. Please see:
  106. 20200428:
  107. AFFECTS: users of sysutils/ansible
  108. AUTHOR:
  109. Ansible has been updated to 2.9.7. Please follow the porting guide
  110. to update the rulesets:
  112. If you wish to stay with 2.8 version, you can switch
  113. to new sysutils/ansible28 port, which tracks stable 2.8 branch:
  114. # pkg set -n ansible:ansible28
  115. 20200428:
  116. AFFECTS: x11-servers/xwayland-devel
  117. AUTHOR:
  118. DRI3 is enabled by default since mesa-libs-18.3.2_4, so you no
  119. longer need to define LIBGL_DRI3_ENABLE in ~/.profile or ~/.login.
  120. See 20200308 entry for more details.
  121. 20200422:
  122. AFFECTS: users of devel/kyua
  123. AUTHOR:
  124. A tests group has been added and the tests user should be a member
  125. of it by default rather than nobody. You should update your password
  126. database to match (change the group from 65534 to 977 after updating).
  127. Please use the following command to do so:
  128. pw usermod -n tests -g tests
  129. 20200408:
  130. AFFECTS: users of security/openssh-portable
  131. AUTHOR:
  132. OpenSSH was upgraded to 8.2p1 on 2020-03-23.
  133. A restart of sshd is required after upgrade due to an incompatibility
  134. introduced in 8.2.
  135. Please see for upcoming
  136. deprecation notices.
  137. 20200408
  138. AFFECTS: users of net/irrd
  139. AUTHOR:
  140. Legacy version of net/irrd has been moved to net/irrd-legacy.
  141. net/irrd has been upgraded to 4.X branch. If someone wants to stick with
  142. legacy version then pkg users have to do something like
  143. # pkg set -o net/irrd:net/irrd-legacy
  144. For portmaster users
  145. # portmaster -o net/irrd-legacy net/irrd
  146. Both of the version can be installed and used concurrently in case there is
  147. a need for migration
  148. 20200403:
  149. AFFECTS: users of x11-fonts/fontconfig
  150. AUTHOR:
  151. Fontconfig 2.13.1 generated .uuid files in the fonts directory which where
  152. not properly registered to the packages. To clean them up, please execute the
  153. following command:
  154. find /usr/local/share/fonts -type f -name .uuid -delete
  155. 20200326:
  156. AFFECTS: users of devel/sonarqube and devel/sonar-ant-task
  157. AUTHOR:
  158. The outdated port devel/sonarqube has moved to
  159. devel/sonarqube-community to make it clear that it is the community
  160. edition. The log and DB files are still stored in the same location.
  161. The devel/sonar-ant-task port has moved to devel/sonarqube-ant-task
  162. to match the upstream-name. The install location is renamed
  163. accordingly.
  164. At the same time the user/group of the sonarqube port changed from
  165. www:www to sonarqube:sonarqube.
  166. It is expected that nobody was using the 6.2 version from 2016
  167. anymore and no change needs to be done. No analysis was done to check
  168. if the old 6.2 version can be updated in-place to the 8.2 version.
  169. As such if there is still someone using the old 6.2 version, you may
  170. have to delete /var/log/sonarqube and /var/db/sonarqube before
  171. installing the new version.
  172. 20200320
  173. AFFECTS: users of devel/qca
  174. AUTHOR:
  175. New versions of devel/qca stopped supporting OpenSSL < 1.1.
  176. For this reason devel/qca-legacy has been added, which is
  177. held back at an older version until FreeBSD 11 goes EOL.
  178. Ports depending on devel/qca should stop adding direct LIB_DEPENDS
  179. and switch to depending on it via USES=qca.
  180. FreeBSD 11 users might want to run something like
  181. pkg set -o devel/qca:devel/qca-legacy
  182. 20200320:
  183. AFFECTS: users of x11/libxkbcommon
  184. AUTHOR:
  185. The libxkbcommon library (x11/libxkbcommon), used to handle keyboards
  186. in some applications, most notably kde and wayland, have been switched
  187. to use evdev rules by default on FreeBSD 12 and later. Some keys, most
  188. notably arrow keys, may not work in applications using libxkbcommon if
  189. you are using xf86-input-keyboard rather than xf86-input-libinput.
  190. If you have trouble with the keyboard keys, and if /var/log/Xorg.*.log
  191. shows that the "kbd" or "keyboard" driver is being used, you need to
  192. switch to legacy rules by setting the environment variable
  193. XKB_DEFAULT_RULES to xorg.
  194. This switch is made to match the default configuration on FreeBSD 12.1 and
  195. later, the default configuration on FreeBSD 11.3 still uses the legacy
  196. rules.
  197. 20200316:
  198. AFFECTS: users of net-im/slack-term
  199. AUTHOR:
  200. The config file location was changed from ~/.slack-term to
  201. ~/.config/slack-term/config, please move your existing config file
  202. accordingly.
  203. 20200308
  204. AFFECTS: users of graphics/mesa-libs and legacy graphics drivers
  205. AUTHOR:
  206. The mesa OpenGL library (graphics/mesa-libs) has been switched to use DRI3
  207. by default, instead of the older DRI2 interface. This might cause regressions
  208. when using the legacy graphics drivers, either through
  209. graphics/drm-legacy-kmod or the graphics drivers in base.
  210. If you experience issues when running OpenGL applications it is possible
  211. to force the use of DRI2 by setting the LIBGL_DRI3_DISABLE environment
  212. variable to 1 before starting any OpenGL application. The easiest way to
  213. do this is by adding it to either your shell startup files or .xinitrc.
  214. 20200306
  215. AFFECTS: users of databases/mysql80-server
  216. AUTHOR:
  217. As of MySQL 8.0.16, the MySQL server performs the upgrade tasks previously
  218. handled by mysql_upgrade. Consequently, mysql_upgrade is unneeded and is
  219. deprecated as of that version, and will be removed in a future MySQL version.
  220. Because mysql_upgrade no longer performs upgrade tasks,
  221. it exits with status 0 unconditionally.
  222. 20200303:
  223. AFFECTS: users of net-mgmt/librenms
  224. AUTHOR:
  225. 1. Apache / mod_php options removed
  226. The APACHEMOD option has been removed. LibreNMS can be used
  227. with other webservers, not just Apache. In order to simplify
  228. the port, the option was removed.
  229. Now you manually install the webserver of your preference.
  230. If upgrading from LibreNMS < 1.61, you can do this to
  231. prevent 'pkg autoremove' from uninstalling Apache / mod_php:
  232. $ sudo pkg set -A 0 apache24 mod_php74
  233. Mark apache24-2.4.41 as not automatically installed? [y/N]: y
  234. Mark mod_php74-7.4.3 as not automatically installed? [y/N]: y
  235. Adjust mod_php74 to suit the version of mod_php you have.
  236. 2. include/ is gone
  237. The file include/ is no longer distributed by
  238. the upstream project. The FreeBSD port patched this file to
  239. correct the paths to common tools such as ping, snmpwalk, etc.
  240. These values previously adjusted by the port must now be specified
  241. in config.php. New installs will have this automatically, but existing
  242. installs must be updated manually. These are the entries you should
  243. add if upgrading from LibreNMS < 1.61:
  244. $config['snmpwalk'] = '/usr/local/bin/snmpwalk';
  245. $config['snmpget'] = '/usr/local/bin/snmpget';
  246. $config['snmpbulkwalk'] = '/usr/local/bin/snmpbulkwalk';
  247. $config['snmptranslate'] = '/usr/local/bin/snmptranslate';
  248. $config['ping'] = '/sbin/ping';
  249. $config['mtr'] = '/usr/local/bin/mtr';
  250. $config['nmap'] = '/usr/local/bin/nmap';
  251. $config['nagios_plugins'] = '/usr/local/libexec/nagios';
  252. $config['ipmitool'] = '/usr/local/bin/ipmitool';
  253. $config['virsh'] = '/usr/local/bin/virsh';
  254. $config['dot'] = '/usr/local/bin/dot';
  255. $config['sfdp'] = '/usr/local/bin/sfdp';
  256. $config['nfdump'] = '/usr/local/bin/nfdump';
  257. 20200229:
  258. AFFECTS: users of textproc/apache-solr
  259. AUTHOR:
  260. Apache-solr switched to the supported java LTS version 11.
  261. Make sure you update the following files accordingly:
  262. /usr/local/etc/ (see /usr/local/etc/
  263. /usr/local/etc/javavm_opts.conf (JAVA_HOME=/usr/local/openjdk11/)
  264. 20200225:
  265. AFFECTS: users of net-mgmt/netbox
  266. AUTHOR:
  267. 1. Removal of the Topology Maps feature
  268. The deprecated topology maps feature has been removed. Please replicate
  269. any required data to another source before upgrading NetBox to v2.7.7, as
  270. any existing topology maps will be deleted.
  271. 2. Changed REDIS database configuration settings
  272. The REDIS database configuration parameters were splitted up in two
  273. discrete subsections named "webhooks" and "caching" with the 2.7 release.
  274. This requires modification of the REDIS parameter in as
  275. follows:
  276. Old Redis sample configuration:
  277. REDIS = {
  278. 'HOST': 'localhost',
  279. 'PORT': 6379,
  280. 'PASSWORD': '',
  281. 'DATABASE': 0,
  282. 'CACHE_DATABASE': 1,
  283. 'DEFAULT_TIMEOUT': 300,
  284. 'SSL': False,
  285. }
  286. New Redis sample configuration:
  287. REDIS = {
  288. 'webhooks': {
  289. 'HOST': '',
  290. 'PORT': 1234,
  291. 'PASSWORD': 'foobar',
  292. 'DATABASE': 0,
  293. 'DEFAULT_TIMEOUT': 300,
  294. 'SSL': False,
  295. },
  296. 'caching': {
  297. 'HOST': 'localhost',
  298. 'PORT': 6379,
  299. 'PASSWORD': '',
  300. 'DATABASE': 1,
  301. 'DEFAULT_TIMEOUT': 300,
  302. 'SSL': False,
  303. }
  304. }
  305. Note that the CACHE_DATABASE parameter has been removed and the connection
  306. settings have been duplicated for both webhooks and caching. This allows
  307. one to make use of separate Redis instances if desired. It is fine to use
  308. the same Redis service for both functions, although the database
  309. identifiers should be different.
  310. Please also check the pkg-message and the changelogs for further info.
  311. 20200223:
  312. AFFECTS: users of security/gsasl
  313. AUTHOR:
  314. The library part of security/gsasl has been split into security/libgsasl.
  315. The security/gsasl now depends on security/libgsasl. Due to this change,
  316. old security/gsasl conflicts with the new security/libgsasl and it can
  317. prevent the installed security/gsasl from upgrading. Please remove the
  318. installed security/gsasl before upgrading if a conflict error occurs.
  319. 20200220:
  320. AFFECTS: users of x11-servers/xorg-server
  321. AUTHOR:
  322. x11-servers/xorg-server has been updated to 1.20.7.
  323. With this update, xorg-server has switched from using the devd backend to
  324. the udev backend for device configuration on FreeBSD 12 and 13. If you have
  325. issues with input devices, please see the install message for details.
  326. The HAL backend option has been completely removed, as it was deprecated.
  327. If you have problems with input devices, ensure that both x11/libinput and
  328. x11-drivers/xf86-input-libinput are installed. They are installed in the
  329. default configuration, but if you have a custom configuration, they might not
  330. be.
  331. 20200210:
  332. AFFECTS: users of net-im/prosody
  333. AUTHOR:
  334. Prosody's pid file and data directory have moved to a new location.
  335. If you are upgrading from a version with the pid file and data
  336. directory in /usr/local/var/lib/prosody please perform these steps:
  337. # stop Prosody
  338. pkill -F /usr/local/var/lib/prosody/
  339. # copy the data directory
  340. cp -a /usr/local/var/lib/prosody /var/db/prosody
  341. rm -f /var/db/prosody/
  342. Make sure your prosody config has the following option set:
  343. pidfile = "/var/run/prosody/"
  344. Then start Prosody again. Everything should be working as before and
  345. the /usr/local/var/lib/prosody directory can now be removed.
  346. 20200207:
  347. AFFECTS: users of security/nss
  348. AUTHOR:
  349. NSS header files and libraries have been moved from ${PREFIX}/include/nss/nss
  350. and ${PREFIX}/lib/nss to ${PREFIX}/include/nss and ${PREFIX}/lib
  351. 20200204:
  352. AFFECTS: users of editors/vim
  353. AUTHOR:
  354. The PYTHON2 and PYTHON3 options have been turned into a single PYTHON
  355. option that uses whichever python you've set as default. However,
  356. this means that you cannot have both python2 and python3 support at
  357. the same time.
  358. 20200126:
  359. AFFECTS: users of multimedia/gstreamer1-plugins[-bad]
  360. AUTHOR:
  361. In GStreamer 1.16 some files moved from the gstreamer1-plugins-bad package
  362. to the gstreamer1-plugins package.
  363. If your using a tool like portmaster or portupgrade delete the old -bad
  364. port and then follow the normal upgrade method.
  365. # pkg delete -f gstreamer1-plugins-bad
  366. 20200126:
  367. AFFECTS: users of sysutils/helm
  368. AUTHOR:
  369. The Helm project have deprecated the Tiller utility in Helm 3. If you are using
  370. Helm 2 you will need to migrate the configuration to be compatible with Helm 3.
  371. Please, refer to the following documentation for more information about the
  372. migration process:
  374. Note that the 2to3 plugin binary is not available for FreeBSD and you will need
  375. to compile it yourself.
  376. 20200113:
  377. AFFECTS: users of python and net/samba410, devel/talloc, devel/tevent, databases/tdb, databases/ldb*
  378. AUTHOR:
  379. In the entry 20191216 for the Python update the filtering constrains
  380. are too limiting and omit the Samba supplimentary libraries, which do
  381. have Python bindings to the default Python 3.x version. With the update
  382. of the default Python3 version you also need to rebuild all the
  383. supplimentary Samba libraries and samba410 itself.
  384. For portmaster users it would be enough to run:
  385. # portmaster devel/talloc devel/tevent databases/tdb databases/ldb15 net/samba410
  386. 20200109:
  387. AFFECTS: www/firefox
  388. AUTHOR:
  389. Firefox requires Capsicum since r522464 for IPC and in future will
  390. require Capsicum for process sandboxing. If you use a custom kernel
  391. make sure to copy the following lines from GENERIC kernel:
  392. options CAPABILITY_MODE # Capsicum capability mode
  393. options CAPABILITIES # Capsicum capabilities
  394. 20200107:
  395. AFFECTS: Users of *-emacs27-* packages
  396. AUTHOR:
  397. There is a major version bump in 28.0.50, therefore to upgrade all the
  398. packages dependent on editors/emacs-devel, please use the following commands:
  399. # sh
  400. # for i in $(pkg query -g %n '*-emacs27*'); do \
  401. nn=$(echo "$i" | sed -e 's/emacs27/emacs28/'); \
  402. pkg set -yn "$i":"$nn"; done;
  403. # pkg upgrade
  404. 20200106:
  405. AFFECTS: users of net/gnatsd
  406. AUTHOR:
  407. net/gnatsd has been replaced by net/nats-server to reflect the
  408. new naming upstream.
  409. All options in rc.conf should be renamed by replacing 'gnats'
  410. with 'nats' (nats_enable, nats_user, nats_options).
  411. 20200101:
  412. AFFECTS: users of security/openssl and security/openssl111
  413. AUTHOR:
  414. The openssl port was removed on 2019-12-31, subsequently the openssl111
  415. port was renamed to openssl on 2020-01-01.
  416. The shared library version of OpenSSL has been bumped.
  417. Users of DEFAULT_VERSIONS= ssl=openssl111 must update this to
  418. ssl=openssl.
  419. You must rebuild all ports that depend on OpenSSL if you use OpenSSL
  420. from ports.
  421. 20191226:
  422. AFFECTS: users of sysutils/dsbmd
  423. AUTHOR:
  424. With version 1.10 dsbmd now uses sysutils/fusefs-jmtpfs for mounting
  425. MTP devices. Please adjust your dsbmd.conf or recreate it from the new
  426. dsbmd.conf.sample.
  427. 20191225:
  428. AFFECTS: multimedia/libva-intel-media-driver
  429. AUTHOR:
  430. As of libva 2.6.0 iHD driver is automatically enabled, so you no
  431. longer need to adjust LIBVA_DRIVER_NAME in ~/.profile or ~/.login.
  432. 20191221:
  433. AFFECTS: users of misc/openhab2
  434. AUTHOR:
  435. If you upgrade from a pevious version, make a backup of
  436. /var/db/openhab2
  437. read about the breaking changes in the release notes at
  439. and run
  440. %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd
  441. which takes care about changes for:
  442. - Textual Configuration
  443. - Next Generation Rule Engine
  444. 20191216:
  445. AFFECTS: users of python
  446. AUTHOR:
  447. Default version of python3 and python was switched to 3.7.
  448. For ports users wanting to keep version 3.6 as default,
  449. add DEFAULT_VERSIONS+= python=3.6 python3=3.6 to make.conf
  450. This may ease the upgrade for users of pre-build packages:
  451. # sh
  452. # for i in $(pkg query -g %n 'py36-*'); do pkg set -yn ${i}:py37-${i#py36-}; done
  453. # pkg upgrade
  454. For portmaster users:
  455. # sh
  456. # portmaster -o lang/python37 python36
  457. # REINSTALL="$(pkg info -o py36-\* | awk '{printf "%s ", $2}')"
  458. # pkg delete -f py36-\*
  459. # portmaster $REINSTALL
  460. # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py37 | cut -d : -f 1 | sort -u)
  461. # portmaster $REBUILD
  462. # REBUILD2=$(pkg list | grep python-36 | xargs pkg which | awk '{print $6}' | sort -u)
  463. # portmaster $REBUILD2
  464. 20191204
  465. AFFECTS: users of mail/nextcloud-mail
  466. AUTHOR:
  467. Version 0.20.0 removed the default mail configuration via config.php.
  468. All users will be prompted to enter account and SMTP- and IMAP-server
  469. details for sending and reading email.
  470. 20191126:
  471. AFFECTS: consumers of net/py-urllib3
  472. AUTHOR:
  473. Since version 1.25 HTTPS connections are now verified by default which is
  474. done via "cert_reqs = 'CERT_REQUIRED'". While certificate verification
  475. can be disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to
  476. leave it on.
  477. Various consumers of net/py-urllib3 already have implemented routines that
  478. either explicitly enable or disable HTTPS certificate verification (e.g.
  479. via configuration settings, CLI arguments, etc.).
  480. Yet it may happen that there are still some consumers which don't
  481. explicitly enable/disable certificate verification for HTTPS connections
  482. which could then lead to errors (as is often the case with self-signed
  483. certificates).
  484. In case of an error one should try first to temporarily disable
  485. certificate verification of the problematic urllib3 consumer to see if
  486. this approach will remedy the issue.
  487. 20191125:
  488. AFFECTS: users of emulators/qemu
  489. AUTHOR:
  490. emulators/qemu31 has been updated to 4.1.1. Previous 3.1.X branch has
  491. been repocopied to emulators/qemu31. If someone wants to stick with 3.1.X
  492. branch please use one of the following command:
  493. # pkg install emulators/qemu31
  494. or
  495. # portmaster -o emulators/qemu31 emulators/qemu
  496. or
  497. # portupgrade -o emulators/qemu31 emulators/qemu
  498. 20191124:
  499. AFFECTS: users of irc/eggdrop
  500. AUTHOR:
  501. The irc/eggdrop port has been updated to 1.8.4 and its config is not
  502. backward compatible with 1.6.21. A new port was created to keep 1.6.21
  503. version available at irc/eggdrop16 and it will be available for 3 months
  504. until users have time to upgrade their configuration.
  505. More information at:
  507. If you would like to keep using 1.6.21, please run the following command
  508. to update pkg database:
  509. pkg set -n eggdrop:eggdrop16
  510. pkg set -o irc/eggdrop:irc/eggdrop16
  511. 20191108:
  512. AFFECTS: users of databases/redis[-devel]
  513. AUTHOR:
  514. The databases/redis port has been updated to the recent stable release.
  515. Users wanting to stay on v4.x can replace databases/redis with
  516. databases/redis4 with one of the following commands:
  517. # pkg install databases/redis4
  518. or
  519. # portmaster -o databases/redis4 databases/redis
  520. or
  521. # portupgrade -o databases/redis4 databases/redis
  522. 20191103:
  523. AFFECTS: users of www/node
  524. AUTHOR:
  525. The www/node port has been updated to Node.js v13.0.0, the latest
  526. upstream release. A new port, www/node12, has been created for the
  527. v12.x LTS branch. Users wanting to stay on v12.x can replace www/node
  528. with www/node12 with one of the following commands:
  529. # pkg install www/node12
  530. or
  531. # portmaster -o www/node12 www/node
  532. or
  533. # portupgrade -o www/node12 www/node
  534. 20191029:
  535. AFFECTS: users of emulators/open-vm-tools[-nox11]
  536. AUTHOR:
  537. open-vm-tools 11.0.1 has removed the vmxnet driver. This driver has been
  538. in tree for quite some time and hopefully everyone is using the in tree
  539. version, however if you had removed device vmx from your kernel, or are
  540. running an unsupported version of FreeBSD which didn't have the driver
  541. included in the base system, updating your open-vm-tools version will
  542. leave you without networking.
  543. 20191026:
  544. AFFECTS: users of www/qt5-webengine
  545. AUTHOR:
  546. Users that upgrade www/qt5-webengine without using pkg/poudriere might
  547. experience failures due to conflicts with the installed version of 5.12.2.
  548. In that case, pkg delete -f the qt5-webengine package before building
  549. the updated version.
  550. 20191025:
  551. AFFECTS: users of x11/nvidia-driver (and slave ports)
  552. AUTHOR:
  553. x11/nvidia-driver* ports no longer install Linux programs and libraries,
  554. which had been moved to their own ports (x11/linux-nvidia-libs*). When
  555. updating the driver package next time, remember to install them manually
  556. if you need to run Linux OpenGL programs.
  557. 20191016:
  558. AFFECTS: users of KDE Plasma Desktop (x11/plasma5*)
  559. AUTHOR:
  560. With Plasma 5.17 the startup script has been renamed. People who use the
  561. .xinitrc method to start Plasma have to call the new binary.
  562. Previously:
  563. exec ck-launch-session startkde
  564. Change to:
  565. exec ck-launch-session startplasma-x11
  566. 20191014:
  567. AFFECTS: users of mail/rspamd, mail/rspamd-devel
  568. AUTHOR:
  569. Sample configuration files has been removed as default configuration files
  570. are NOT intended for modification by users and SHOULD be overwritten on
  571. port upgrade.
  572. Make sure the default configuration files are unmodified and migrate all
  573. configuration changes to the proper places, before you continue.
  574. 20191002:
  575. AFFECTS: users of textproc/groff
  576. AUTHOR:
  577. with groff 1.2.4_3, groff does not depend anymore on ghostscript and
  578. netpbm. In order to be able to properly use the html backend the user
  579. can install ghostscript and netpbm from ports without the need of
  580. reinstalling the package.
  581. Also note that the X11 option has been removed.
  582. 20190930:
  583. AFFECTS: users of net-mgmt/netbox
  584. AUTHOR:
  585. Since the 2.6 release a running Redis server instance is required for
  586. caching objects to run. Also the following settings like below need to be
  587. added (or modified) in the existing
  588. REDIS = {
  589. 'HOST': 'localhost',
  590. 'PORT': 6397,
  591. 'PASSWORD': ''
  592. 'DATABASE': 0,
  593. 'CACHE_DATABASE': 1,
  594. 'DEFAULT_TIMEOUT': 300,
  595. 'SSL': False,
  596. }
  597. Note that if you were using these settings in a prior release with
  598. webhooks, the DATABASE setting remains the same but an additional
  599. CACHE_DATABASE settings has been added with a default value of 1 to
  600. support the caching backend.
  601. The DATABASE setting will be renamed in a future release of NetBox to
  602. better relay the meaning of the setting. It is highly recommended to keep
  603. the webhook and cache databases separate. Using the same database number
  604. for both may result in webhook processing data being lost during cache
  605. flushing events.
  606. Please also check the pkg-message and the changelogs for further info.
  607. 20190927:
  608. AFFECTS: users of emulators/qemu-devel
  609. AUTHOR:
  610. qemu-devel has been updated to 4.1.0 and 4.0.0 has been merged into a new port
  611. emulators/qemu40. If you want to stick with 4.0.X branch, simply use:
  612. # portmaster -o emulators/qemu-devel emulators/qemu40
  613. 20190927:
  614. AFFECTS: users of XFCE desktop (x11-wm/xfce4)
  615. AUTHOR:
  616. Due to changes in the XFCE 4.14 metaport, systems could end up with
  617. both xscreensaver and xfce4-screensaver installed and enabled
  618. simultaneously.
  619. This can cause conflicts and problems unlocking the screen.
  620. To avoid problems, please make sure to have only one enabled by
  621. going to the Application Autostart tab of the Session and Startup
  622. settings applet and enable only one Screensaver there.
  623. Some further information can be found in the xfce4-session
  624. pkg-message displayed on installation and upgrade.
  625. 20190920:
  626. AFFECTS: users of net-mgmt/pushgateway
  627. AUTHOR:
  628. The persistent storage format used by pushgateway in the latest version
  629. is not backwards compatible. See the pushgateway changelogs for details.
  630. 20190911:
  631. AFFECTS: users of security/bastillion
  632. AUTHOR:
  633. The datastore of bastillion needs to be updated:
  634. java -jar $PREFIX/jetty_bastillion/upgrade/bastillion-upgrade-3.08.00.jar \
  635. $PREFIX/jetty_bastillion/bastillion/WEB-INF/classes/
  636. 20190909:
  637. AFFECTS: users of lang/ruby25
  638. AUTHOR:
  639. The default ruby version has been updated from 2.5 to 2.6.
  640. If you compile your own ports you may keep 2.5 as the default version by
  641. adding the following lines to your /etc/make.conf file:
  642. #
  643. # Keep ruby 2.5 as default version
  644. #
  645. DEFAULT_VERSIONS+=ruby=2.5
  646. If you wish to update to the new default version, you need to first stop any
  647. software that uses ruby. Then, you will need to follow these steps, depending
  648. upon how you manage your system.
  649. If you use pkgng, simply upgrade:
  650. # pkg upgrade
  651. If you do not use pkg, please check entry 20190420.
  652. The description there should also work for this version.
  653. 20190906:
  654. AFFECTS: users of devel/py-fabric
  655. AUTHOR:
  656. Fabric (devel/py-fabric) was upgraded to 2.5.0, Fabric (2+) represents
  657. a near-total reimplementation and reorganization of the software.
  658. Fabric 2 is not at 100% feature parity with 1.x! Some features have been
  659. explicitly dropped, but others simply have not been ported over yet,
  660. either due to time constraints or because said features need to be
  661. re-examined in a modern context.
  662. More information at:
  665. If you would like to keep using 1.x, please run the following command to
  666. update pkg database:
  667. pkg set -n py27-fabric:py27-fabric1
  668. pkg set -o devel/py-fabric:devel/py-fabric1
  669. 20190830:
  670. AFFECTS: users of www/gitlab-ce
  671. AUTHOR:
  672. Make sure you upgrade your PostgreSQL to version 11 as described in 20190829,
  673. before you upgrade your gitlab-ce version.
  674. Gitlab-ce 12.1 needs at least PostgreSQL version 9.6.
  675. After this you can follow the usual upgrade guide:
  677. 20190829:
  678. AFFECTS: users of database/postgresql* and other software using PostgreSQL to run
  679. AUTHOR:
  680. The default version of PostgreSQL has been switched from 9.5 to 11.
  681. The upgrade procedure can use up twice the space the databases
  682. currently needs. If you have a big amount of stored data take a
  683. closer look at the manpage of pg_upgrade for avoidance and/or
  684. speedup of the upgrade.
  685. The upgrade instructions consider a basic usage and do not match
  686. complex scenarios like replication, sharding, or similar.
  687. Upgrade instructions:
  688. First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
  689. If you have another Version of PostgreSQL installed, for example 9.5.19, your
  690. files are named according to this.
  691. # service postgresql stop
  692. # pkg create postgresql95-server postgresql95-contrib
  693. # mkdir /tmp/pg-upgrade
  694. # tar xf postgresql95-server-9.5.19.txz -C /tmp/pg-upgrade
  695. # tar xf postgresql95-contrib-9.5.19.txz -C /tmp/pg-upgrade
  696. # pkg delete -f databases/postgresql95-server databases/postgresql95-contrib databases/postgresql95-client
  697. Now update PostgreSQL:
  698. pkg user:
  699. # pkg install databases/postgresql11-server databases/postgresql11-contrib
  700. # pkg upgrade
  701. Portmaster users:
  702. # portmaster databases/postgresql11-server databases/postgresql11-contrib
  703. # portmaster -a
  704. Portupgrade users:
  705. # portinstall databases/postgresql11-server databases/postgresql11-contrib
  706. # portupgrade -a
  707. After installing the new PostgreSQL version you need to convert
  708. all your databases to new version:
  709. # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data11 -U pgsql"
  710. # chown -R postgres /usr/local/pgsql/data/
  711. # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data/ -B /usr/local/bin/ -D /var/db/postgres/data11/ -U pgsql "
  712. Now the migration is finished. You can start PostgreSQL again with:
  713. # service postgresql start
  715. 1) The default user changed from "pgsql" to "postgres". The migration steps above preserve
  716. the "pgsql" database user while the database daemon is now executed as the "postgres" FreeBSD user.
  717. 2) The default data dir changed from "/usr/local/pgsql/data/" to "/var/db/postgres/data11/"
  718. 3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
  719. 20190816:
  720. AFFECTS: users of net-im/ejabberd
  721. AUTHOR:
  722. Riak support has been removed by upstream. For update instructions from
  723. 19.05, please refer to:
  725. 20190812:
  726. AFFECTS: users of lang/perl5*
  727. AUTHOR:
  728. The default Perl version has been switched to Perl 5.30. If you are using
  729. binary packages to upgrade your system, you do not have anything to do, pkg
  730. upgrade will do the right thing. For the other people, follow the
  731. instructions in entry 20161103, it should still be the same.
  732. 20190801:
  733. AFFECTS: users of www/ot-recorder
  734. AUTHOR:
  735. The data directory has moved from /var/spool/owntracks to
  736. /var/db/owntracks
  737. Be sure to stop otrecorder, move the directory, and start otrecorder.
  738. service ot-recorder stop
  739. cd /var/spool
  740. mv owntracks /var/db
  741. service ot-recorder start
  742. 20190728:
  743. AFFECTS: users of net-im/py-matrix-synapse
  744. AUTHOR:
  745. The support for Python 2.7 has been dropped with the 1.1.0 release of
  746. net/py-matrix-synapse.
  747. Users that still use the Python 2.7 version of net-im/py-matrix-synapse
  748. should switch to a newer Python version, e.g. 3.6, which is the default
  749. Python version since April 2019.
  750. 20190717:
  751. AFFECTS: users of net-p2p/zetacoin and net-p2p/zetacoin-nox11
  752. AUTHOR:
  753. Zetacoin will default to using modern versions of BDB (5.x or 6.x) when
  754. the WALLET option is selected. See pkg-help for explanation.
  755. The zetacoin-nox11 slave port was renamed to zetacoin-daemon to align
  756. with the net-p2p/bitcoin format.
  757. The zetacoin-cli and zetacoin-tx utilities have been re-packaged into
  758. a separate port. If you require these programs, or use the zetacoin-cli
  759. program to access the daemon or the GUI, install net-p2p/zetacoin-utils
  760. to reinstall them.
  761. 20190717:
  762. AFFECTS: users of sysutils/py-borgmatic
  763. AUTHOR:
  764. The default location for borgmatic's configurations changed. We moved it
  765. from '/etc/borgmatic' to '/usr/local/etc/borgmatic' in order to follow
  766. recommended standards used on FreeBSD.
  767. 20190710:
  768. AFFECTS: users with DEFAULT_VERSIONS+=linux=c6 or c6_64 in /etc/make.conf
  769. AUTHOR:
  770. On amd64 adding DEFAULT_VERSIONS+=linux=c6 to /etc/make.conf made Linux
  771. infrastructure ports (linux_base-c6 and linux-c6*) install i386 CentOS 6
  772. packages. Using c6_64 instead of c6 made them install mixed amd64/i386
  773. CentOS 6 packages and allowed Linux application ports to install amd64
  774. binaries when available. The i386-only configuration was only useful for
  775. users of x11/nvidia-driver* which didn't provide Linux amd64 emulation
  776. until recently.
  777. With x11/nvidia-driver* now supporting Linux amd64 there's no longer a
  778. need for i386-only Linux on amd64 so DEFAULT_VERSIONS+=linux=c6 has been
  779. changed to make Linux infrastructure ports install mixed amd64/i386
  780. CentOS 6 packages, like c6_64 before, and support for c6_64 has been
  781. removed.
  782. Users with DEFAULT_VERSIONS+=linux=c6 should reinstall linux_base-c6 and
  783. all packages that depend on it. A list of dependent packages can be
  784. obtained with the following command:
  785. pkg info -r linux_base-c6
  786. Users with DEFAULT_VERSIONS+=linux=c6_64 only need to replace c6_64 with
  787. c6 in /etc/make.conf.
  788. Users of x11/nvidia-driver* should upgrade to FreeBSD 11.3 or 12.0 if
  789. they want to run Linux amd64 OpenGL programs. If you are running an
  790. older version you may want to postpone installing or updating Linux
  791. application ports until you find the time to upgrade because application
  792. ports may install amd64 binaries now. Infrastructure ports are safe to
  793. reinstall, and so is x11/nvidia-driver*.
  794. On i386 nothing has changed.
  795. 20190707:
  796. AFFECTS: users of www/gitlab-ce
  797. AUTHOR:
  798. You must at first upgrade to version 11.11.5 before you can upgrade
  799. to version 12.
  800. Support for MySQL will be dropped with next version.
  801. Make sure you use at least PostgreSQL version 9.6.
  802. Follow the normal upgrade manual that can be found here:
  804. 20190705:
  805. AFFECTS: users of net/serviio which bought a license for the non-free features
  806. AUTHOR:
  807. Version 2 of serviio needs a new license file. Updating without a new license
  808. file will disable the non-free features.
  809. 20190701:
  810. AFFECTS: users of databases/mysql56-(server|client)
  811. AUTHOR:
  812. The default MySQL version has been updated from 5.6 to 5.7.
  813. If you compile your own ports you may keep 5.6 as the default version by
  814. adding the following lines to your /etc/make.conf file:
  815. #
  816. # Keep MySQL 5.6 as default version
  817. #
  818. DEFAULT_VERSIONS+=mysql=5.6
  819. If you wish to update to the new default version, you need to first stop any
  820. running server instance. Then, you will need to follow these steps, depending
  821. on installed packages.
  822. # pkg set -o databases/mysql56-client:databases/mysql57-client
  823. # pkg set -o databases/mysql56-server:databases/mysql57-server
  824. # pkg upgrade
  825. 20190630:
  826. AFFECTS: users of net/samba410
  827. AUTHOR:
  828. If you used Samba in AD/DC mode with the previous versions of the port on UFS2
  829. backed storage you have to add usage of vfs_freebsd VFS module for at least
  830. SYSVOL share and configure it to use 'legacy' mode(see manpage).
  831. The reason behind this is that previous versions Samba port used a hack to
  832. workaround broken mapping of Linux security and trusted extended attributes
  833. into FreeBSD namespace. In particular, essential security.NTACL attribute
  834. was replaced with the user.NTACL and placed in a insecure USER namespace.
  835. This port dropped this hack in favor of vfs_freebsd module, which should
  836. provide more controlled way of such a mapping.
  837. To maintain the compatibility with the previous installations on UFS2 storage
  838. (as ZFS uses it's own way of mapping SYSVOL, thanks to the iXsystems patches)
  839. the vfs_freebsd module provides 'legacy' mode that implements old functionality.
  840. For the fresh installations it is recommended to use 'secure' mode of operations
  841. for this module and use it as a global vfs objects.
  842. Caution: The given module is still considered EXPERIMENTAL.
  843. 20190630:
  844. AFFECTS: users of net/samba410, net/samba4[6-8] and devel/talloc?, devel/tevent?, databases/tdb?, databases/ldb*
  845. AUTHOR:
  846. The port of the new version of Samba 4.10 is introduced. Due necessarily
  847. to keep backwards compatibility for the legacy samba4[6-8] ports the
  848. upgrade procedure is a bit convoluted.
  849. You are safe to perform fresh new install of samba410 port. In case you
  850. are upgrading from the previous versions of Samba, please use the
  851. following procedure:
  852. 0. Take backups of all the relevant files, in particular PREFIX/etc/smb4.conf
  853. and /var/db/samba4/ subdirectory. Keep in mind that files there (may)
  854. have extended attributes, so use appropriate tools to preserve them.
  855. 1a. If you haven't updated Samba between 20190619 and 20190630 then next
  856. step should be as simple as:
  857. portmaster -o net/samba410 net/samba48
  858. 1b. If you have been affected by the archiving legacy versions of
  859. Samba-related libraries for legacy versions of Samba, which happened
  860. in the given time frame, then you need to reverse operation from the
  861. 20190619 entry:
  862. for users of portmaster:
  863. portmaster -o devel/talloc devel/talloc1
  864. portmaster -o devel/tevent devel/tevent1
  865. portmaster -o databases/tdb databases/tdb1
  866. portmaster -o net/samba410 net/samba48
  867. for users of portupgrade:
  868. portupgrade -o devel/talloc devel/talloc1
  869. portupgrade -o devel/tevent devel/tevent1
  870. portupgrade -o databases/tdb databases/tdb1
  871. portupgrade -o net/samba410 net/samba48
  872. 20190619:
  873. AFFECTS: users of samba4[6-8] and devel/talloc, devel/tevent, databases/tdb, databases/ldb*
  874. AUTHOR:
  875. To introduce samba410(we deliberately skip samba49 due the complexity of handling)
  876. and to drop dependency on deprecated Python 2.7, Samba supplementary libraries
  877. talloc, tevent and tdb were split into current Python 3 compatible versions
  878. and legacy ones, with the suffix "1".
  879. Old versions of Samba were changed to depend on the legacy supplementary libraries,
  880. so if you need to install samba46, samba47 or samba48 over previous Samba
  881. installations you need to downgrade supplementary libs with the following commands:
  882. for users of portmaster:
  883. portmaster -o devel/talloc1 devel/talloc
  884. portmaster -o devel/tevent1 devel/tevent
  885. portmaster -o databases/tdb1 databases/tdb
  886. portmaster -r talloc1
  887. for users of portupgrade:
  888. portupgrade -o devel/talloc1 devel/talloc
  889. portupgrade -o devel/tevent1 devel/tevent
  890. portupgrade -o databases/tdb1 databases/tdb
  891. portupgrade -fr devel/talloc1
  892. 20190613:
  893. AFFECTS: users of www/qt5-webengine
  894. AUTHOR:
  895. Users that upgrade www/qt5-webengine without using pkg/poudriere might
  896. experience failures due to conflicts with the installed version of 5.12.2.
  897. In that case, pkg delete -f the qt5-webengine package before building
  898. the updated version.
  899. 20190611:
  900. AFFECTS: users of net/routinator
  901. AUTHOR:
  902. Release 0.4.0 fundamentally changes the command line options for
  903. running the server and introduces a new way to initialize the local RPKI
  904. repository used by Routinator.
  905. If you have been using previous releases, you will likely have to adjust
  906. your tooling. We apologize for this, but we also feel that the new commands
  907. are more intuitive and logical.
  908. 20190604:
  909. AFFECTS: users of net/samba47
  910. AUTHOR:
  911. The default version of samba has been switched from 4.7 to 4.8.
  912. Upgrade instructions:
  913. For package users having samba47 installed indirectly (as a dependency):
  914. # pkg upgrade
  915. For package users having samba47 installed directly (leaf port):
  916. # pkg upgrade
  917. # pkg install samba48
  918. For ports users:
  919. If you want to keep samba47, add DEFAULT_VERSIONS+= samba=4.7 to make.conf
  920. If you want to upgrade to samba48, remove samba47:
  921. # pkg delete -f samba47
  922. Portmaster users:
  923. # portmaster net/samba48
  924. # portmaster -a
  925. Portupgrade users:
  926. # portinstall net/samba48
  927. # portupgrade -a
  928. 20180601:
  929. AFFECTS: www/tt-rss
  930. AUTHOR:
  931. tt-rss now uses php intl for extension; a web server reload
  932. will be required if intl extension isn't already loaded.
  933. 20190522:
  934. AFFECTS: users of sysutils/graylog
  935. AUTHOR:
  936. The port has been updated to the latest stable version 3.0.2, which
  937. includes more plugins by default, but also requires manual changes to
  938. graylog's configuration files, possibly port and URL changes, such as
  939. X-Graylog-Server-URL settings, and elasticsearch must be >= 5.
  940. The location of configuration files has been amended to align with the
  941. official distribution files and locations.
  942. After upgrading, manually review and merge changes from your
  943. /usr/local/etc/graylog/server/server.conf into
  944. /usr/local/etc/graylog/graylog.conf
  945. Consult for
  946. further details.
  947. 20190506:
  948. AFFECTS: users of www/gitea
  949. AUTHOR:
  950. Gitea requires the addition of another secret to the config file in order
  951. to start up. Either manually add JWT_SECRET to the
  952. ${PREFIX}/etc/gitea/conf/app.ini config file (see app.ini.sample), or allow
  953. Gitea to make the change for you by making the config file writable to the
  954. git user.
  955. 20190424:
  956. AFFECTS: users of www/node
  957. AUTHOR:
  958. The www/node port has been updated to Node.js v12.0.0, the latest
  959. upstream release. This is a major release, including many significant
  960. changes. Users are encouraged to read the release announcements before
  961. upgrading:
  963. 20190423:
  964. AFFECTS: users of www/gitlab-ce
  965. AUTHOR:
  966. The directory where all repositories and ssh permissions are stored
  967. was changed from /usr/home/git back to /usr/local/git, to match again the
  968. recommended standards on FreeBSD.
  969. This will cause now some other git management packages to collide with
  970. gitlab. Make sure you migrate all you git repositories to gitlab first,
  971. before you continue.
  972. Make sure /usr/local/git/repositories and /usr/local/git/.ssh are not
  973. existing!
  974. Otherwise the next commands can break your installation for managing
  975. git repositories within gitlab and with your other gitlab management
  976. software!
  977. You must move the old files to the new location with:
  978. # service gitlab stop
  979. # mv /usr/home/git /usr/local/
  980. # pkg upg
  981. Make sure you update your config files, diff shows you what you maybe
  982. must change:
  983. # cd /usr/local/www/gitlab-ce
  984. # git diff config/gitlab.yml.sample config/gitlab.yml
  985. # cd /usr/local/share/gitlab-shell/
  986. # git diff config.yml.sample config.yml
  987. # cd /usr/local/share/gitaly
  988. # git diff config.toml.sample config.toml
  989. # Change home directory of user git back to /usr/local/git
  990. # vipw
  991. The line should now looks like:
  992. git:*:211:211::0:0:gitosis user:/usr/local/git:/bin/sh
  993. If you do an upgrade of gitlab follow the upgrade guide.
  994. If not, just start gitlab again with:
  995. # service gitlab start
  996. 20190422:
  997. AFFECTS: users of security/libressl
  998. AUTHOR:
  999. The port has been updated to the latest stable version 2.9 of LibreSSL.
  1000. The shared library versions of the libraries have been bumped.
  1001. After upgrading, manually update all packages that depend on any of the
  1002. libraries provided by LibreSSL (libssl, libcrypto and libtls) since the
  1003. versions of these libraries have changed. Normally, you can obtain the
  1004. list of dependent software by running the following command:
  1005. # pkg info -r libressl
  1006. Then you should rebuild all ports depending on libressl to avoid dangling
  1007. shared library dependencies. Poudriere and pkg handle this correctly,
  1008. portmaster and portupgrade users can use the following to rebuild all
  1009. dependent ports.
  1010. Portmaster users:
  1011. portmaster -r libressl
  1012. Portupgrade users:
  1013. portupgrade -fr security/libressl
  1014. 20190421:
  1015. AFFECTS: users of databases/cego
  1016. AUTHOR:
  1017. To upgrade from cego 2.39.16 to 2.44.1, you need to export to xml before
  1018. the upgrade and import from xml after the upgrade, because the internal
  1019. storage has changed for some types.
  1020. Use these steps:
  1021. - export your database while it runs, see
  1023. for details.
  1024. - stop the database
  1025. service cego stop
  1026. - upgrade the port/package
  1027. - re-create the database
  1028. cego --mode=create --tableset=<database> --dbxml=<database>.xml
  1029. - import the database
  1030. cego --mode=xmlimport --tableset=<database> \
  1031. --dbxml=<database>.xml --impfile=export.xml --doLogging
  1032. - modify /etc/rc.conf by adding
  1033. cego_<database>_cpdump="YES"
  1034. cego_<database>_cleanup="YES"
  1035. - start the database
  1036. service cego start
  1037. 20190420:
  1038. AFFECTS: users of lang/ruby24
  1039. AUTHOR:
  1040. The default ruby version has been updated from 2.4 to 2.5.
  1041. If you compile your own ports you may keep 2.4 as the default version by
  1042. adding the following lines to your /etc/make.conf file:
  1043. #
  1044. # Keep ruby 2.4 as default version
  1045. #
  1046. DEFAULT_VERSIONS+=ruby=2.4
  1047. If you wish to update to the new default version, you need to first stop any
  1048. software that uses ruby. Then, you will need to follow these steps, depending
  1049. upon how you manage your system.
  1050. If you use pkgng, simply upgrade:
  1051. # pkg upgrade
  1052. If you use portmaster, install new ruby, then rebuild all ports that depend
  1053. on ruby:
  1054. # portmaster -o lang/ruby25 lang/ruby24
  1055. # portmaster -R -r ruby-2.5
  1056. If you use portupgrade, install new ruby, then rebuild all ports that depend
  1057. on ruby:
  1058. # pkg delete -f ruby portupgrade
  1059. # make -C /usr/ports/ports-mgmt/portupgrade install clean
  1060. # pkg set -o lang/ruby24:lang/ruby25
  1061. # portupgrade -x ruby-2.5.\* -fr lang/ruby25
  1062. 20190419:
  1063. AFFECTS: users of emulators/qemu
  1064. AUTHOR:
  1065. qemu 2.X version has been moved to qemu2. If you would like to use
  1066. 2.X you should use qemu2. Otherwise you can use the new stable
  1067. upstream branch of 3.0.X.
  1068. Portmaster users will need to run this command:
  1069. portmaster -o emulators/qemu2 emulators/qemu
  1070. 20190410:
  1071. AFFECTS: users of python
  1072. AUTHOR:
  1073. Default version of python was switched to 3.6.
  1074. For ports users wanting to keep version 2.7 as default,
  1075. add DEFAULT_VERSIONS+= python=2.7 to make.conf
  1076. 20190328:
  1077. AFFECTS: www/firefox-i18n, www/firefox-esr-i18n, mail/thunderbird-i18n, www/seamonkey-i18n
  1078. AUTHOR:
  1079. Separate packages for localization packs are no longer supported.
  1080. Firefox 65+ has in-browser menu while Firefox ESR60, Thunderbird 60
  1081. or SeaMonkey 2.49 should download preferred .xpi manually. Refer to
  1082. the following article (including previous revisions) how to do this.
  1084. 20190328:
  1085. AFFECTS: users of www/qt5-webengine
  1086. AUTHOR:
  1087. Users that upgrade www/qt5-webengine without using pkg/poudriere might
  1088. experience failures due to conflicts with the installed version of 5.9.5.
  1089. In that case, pkg delete -f the qt5-webengine package before building
  1090. the updated version.
  1091. 20190314:
  1092. AFFECTS: users of mail/rspamd, mail/rspamd-devel
  1093. AUTHOR:
  1094. User and group that rspamd run as are changed from nobody:nobody to
  1095. rspamd:rspamd. Unless it is clean install you need to execute following
  1096. command.
  1097. # chown -R rspamd:rspamd /var/db/rspamd /var/log/rspamd /var/run/rspamd
  1098. 20190311:
  1099. AFFECTS: users of x11/xorg, x11-fonts/mkfontscale, x11-fonts/mkfontdir
  1100. AUTHOR:
  1101. The x11-fonts/mkfontdir port has been removed and the functionality
  1102. has been merged into x11-fonts/mkfontscale. This might cause issues
  1103. with upgrading. If you get conflicts between mkfontscale and mkfontdir
  1104. please remove mkfontdir before upgrading.
  1105. To do this, simply run the following:
  1106. pkg delete -f mkfontdir
  1107. 20190311:
  1108. AFFECTS: users of www/igal2
  1109. AUTHOR:
  1110. www/igal2 2.2-1 is now built with graphics/ImageMagick6-nox11
  1111. and don't install the ImageMagick X11 dependencies anymore.
  1112. A build option allows you to restore the previous behaviour.
  1113. 20190303:
  1114. AFFECTS: users of x11-fonts/noto*
  1115. AUTHOR:
  1116. Google Noto Fonts family has been converted to several ports. x11-fonts/noto
  1117. is a meta port which includes 1 old port and 5 new ports as follows:
  1118. - x11-fonts/noto-basic (was noto-lite): basic fonts set with emoji
  1119. - x11-fonts/noto-extra: extra fonts set
  1120. - x11-fonts/noto-jp: Japanese fonts set
  1121. - x11-fonts/noto-kr: Korean fonts set
  1122. - x11-fonts/noto-sc: Simplified Chinese fonts set
  1123. - x11-fonts/noto-tc: Traditional Chinese fonts set
  1124. 20190302:
  1125. AFFECTS: users of sysutils/paladin
  1126. AUTHOR: Ryan Westlund <>
  1127. The way paladin parses its config file has changed, please
  1128. check the provided sample config.
  1129. 20190227:
  1130. AFFECTS: users of security/softether, security/softether-devel
  1131. AUTHOR:
  1132. These ports' bridge, client, server daemon unintendedly had spit out
  1133. chain_certs (certificate chain) directory on libexec directory until
  1134. r494024.
  1135. If your ${PREFIX}/libexec/softether/chain_certs directory is empty, you
  1136. can remove the directory safely. If the directory is not empty, move it
  1137. to ${SE_DBDIR} when upgrading softether. Following commands should help:
  1138. service softether_(bridge|client|server) stop
  1139. (portmaster, portupgrade or pkg upgrade)
  1140. mv ${PREFIX}/libexec/softether/chain_certs ${SE_DBDIR}/
  1141. service softether_(bridge|client|server) start
  1142. With the default Makefile settings, ${SE_DBDIR} is set to /var/db/softether.
  1143. 20190224:
  1144. AFFECTS: users of security/gnutls
  1145. AUTHOR:
  1146. GnuTLS now looks for its configuration files in PREFIX/etc (/usr/local/etc)
  1147. instead of /etc. If the following files exist they have to be moved. On a
  1148. default installation these files do not exist.
  1149. /etc/gnutls/default-priorities
  1150. /etc/gnutls/pkcs11.conf
  1151. /etc/tpasswd
  1152. /etc/tpasswd.conf
  1153. 20190215:
  1154. AFFECTS: users of net-im/ejabberd
  1155. AUTHOR:
  1156. If you've mod_mam enabled with compress_xml set to true, then you're affected
  1157. by bug where the XML namespace, and tag elements get interchanged in the MAM cache
  1158. which results in invalid XML, and causing XMPP clients to disconnect. For more
  1159. details, please refer to:
  1160. This upgrade contains the patch that fixes the problem going forward. For fixing already
  1161. affected users, you'll need to wipe off the MAM cache for the affected users:
  1162. sudo -u ejabberd -H ejabberdctl remove_mam_for_user <user> <server>
  1163. 20190207:
  1164. AFFECTS: users of net-mgmt/mk-livestatus
  1165. AUTHOR:
  1166. The default Nagios version supported by net-mgmt/mk-livestatus changed
  1167. from Nagios 3 to Nagios 4 - the respective Nagios package was added to
  1168. net-mgmt/mk-livestatus' runtime dependencies.
  1169. If you still need support for Nagios 3 you just need to change the
  1170. options for net-mgmt/mk-livestatus and compile the port yourself.
  1171. 20190202:
  1172. AFFECTS: users of archivers/urbackup-server
  1173. AUTHOR:
  1174. Some of the port's sources previously included absolute references to /etc/urbackup.
  1175. The upgrade now changes these references to ${PREFIX}/etc/urbackup. If you have
  1176. placed any configuration files within /etc/urbackup, these should be relocated to
  1177. ${PREFIX}/etc/urbackup.
  1178. 20190130:
  1179. AFFECTS: users of sysutils/password-store
  1180. AUTHOR:
  1181. password-store now stores plugins in ${PREFIX}/libexec instead of ${PREFIX}/lib.
  1182. Ensure to move your own extensions there too and update your scripts to avoid
  1183. breakage.
  1184. 20190124:
  1185. AFFECTS: users of sysutils/rubygem-fluentd, sysutils/fluent-bit
  1186. AUTHOR:
  1187. The fluentd port has been upgraded from the 0.12 line to 1.3.3. The upgrade
  1188. is mostly non-disruptive since there is a backward compatibility with 0.12
  1189. plugins and configuration files, but care should be taken about the order of
  1190. server upgrades since fluentd 1.x is unable to send it's data to version 0.12
  1191. instances. You should carefully read
  1192. before performing
  1193. any upgrade activities.
  1194. 20190120:
  1195. AFFECTS: users of mail/fetchmail
  1196. AUTHOR:
  1197. The fetchmail port no longer offers the X11 option and no longer
  1198. depends on Python. The corresponding fetchmailconf Python program has now
  1199. been split out into a separate port or package, so that fetchmail itself
  1200. will no longer require Python.
  1201. Users who wish to use fetchmailconf should install the new fetchmailconf
  1202. port or package.
  1203. 20190119:
  1204. AFFECTS: users of german/webalizer2, japanese/webalizer, polish/webalizer2, portuguese/webalizer-pt_BR, portuguese/webalizer-pt_PT, ukrainian/webalizer, www/geolizer, www/webalizer
  1205. AUTHOR:
  1206. The option GEOIP has been changed to used the new database.
  1207. Either copy GeoLite2-Country.mmdb in the working directory,
  1208. or set the GeoIPDatabase option to the location of the file.
  1209. 20190114:
  1210. AFFECTS: users of graphics/qgis
  1211. AUTHOR:
  1212. GIS 3.4 LTR, the first long-term release (LTR) of QGIS 3, has landed
  1213. in the FreeBSD ports tree. It will also replace the previous 2.18 LTR
  1214. in the QGIS package repositories in February 2019 [1].
  1215. Beside, the latest Qt4 version 4.8.7 has been EOL since December 2015
  1216. and its expiration date on FreeBSD is set to March, 15th 2019.
  1217. Because QGIS 2 is based on Qt4 and Python2, it was decided to not create
  1218. a legacy port for QGIS 2, after graphics/qgis changed to QGIS 3.
  1219. For users moving over from the 2.18 LTR there is a huge list of new
  1220. features and impactful changes in this new 3.4 LTR version. Most notably
  1221. 3.x plugins are incompatible with 2.x plugins, so please review your
  1222. plugin usage carefully. Before moving over, if you have not already
  1223. done so, take a look at the changelogs from versions 3.0, 3.2, and
  1224. 3.4 [2][3][4] to understand the full scope of changes in the 3.x release.
  1225. [1]
  1226. [2]
  1227. [3]
  1228. [4]
  1229. 20190114:
  1230. AFFECTS: x11-wm/sway
  1231. AUTHOR:
  1232. swayidle and swaylock split out into x11/swayidle and x11/swaylock.
  1233. Check your sway config and install those if required.
  1234. 20190113:
  1235. AFFECTS: users of net/GeoIP
  1236. AUTHOR:
  1237. Maxmind no longer provides geolocation data in the legacy format used
  1238. by net/GeoIP. All GEOIP-related OPTIONS have been removed, and all
  1239. GeoIP-dependent ports will be removed soon.
  1240. Where possible, you must switch to net/libmaxminddb, which uses the
  1241. newer (and fully supported) GeoIP 2 format. Unfortunately, this is
  1242. not a drop-in replacement. To fetch the GeoIP 2 geolocation databases,
  1243. whether the free or paid versions, you must use net/geoipupdate
  1244. (pkg install geoipupdate).
  1245. The legacy database is no longer available, and we cannot distribute
  1246. it by the Maxmind license, so the legacy GeoIP format is essentially
  1247. dead.
  1248. 20190108:
  1249. AFFECTS: users of databases/mysql-connector-java
  1250. AUTHOR:
  1251. The databases/mysql-connector-java port has been updated to 8.0.13,
  1252. which requires a minimum of Java 1.8, so dropping support for Java
  1253. 1.6 and 1.7. Users of those versions of Java should substitute the
  1254. databases/mysql-connector-java51 port which remains at version
  1255. 5.1.47
  1256. 20190103:
  1257. AFFECTS: users of multimedia/vlc*
  1258. AUTHOR:
  1259. The multimedia/vlc port has been upgraded to 3.0.5, the latest upstream
  1260. release. Subsequently, multimedia/vlc-qt4 and multimedia/vlc3 have been
  1261. retired and removed from the ports tree. Users who previously used
  1262. multimedia/vlc3 might want to switch to multimedia/vlc with the following
  1263. commands:
  1264. # pkg install multimedia/vlc
  1265. or
  1266. # portmaster -o multimedia/vlc multimedia/vlc3
  1267. or
  1268. # portupgrade -o multimedia/vlc multimedia/vlc3
  1269. 20190102:
  1270. AFFECTS: users of net/serviio
  1271. AUTHOR:
  1272. If you have customized your etc/serviio/profile.xml you need to review
  1273. and merge changes from the profile.xml.sample file, else you may not be
  1274. able to watch mkv files.
  1275. 20181228:
  1276. AFFECTS: users of devel/trio
  1277. AUTHOR:
  1278. Since trio 1.16-1, the shared lib previously misnamed
  1279. is now named and the symlink is created.
  1280. 20181222:
  1281. AFFECTS: users of net/ntopng
  1282. AUTHOR:
  1283. Since ntopng 3.7, for security reasons, the default setting for
  1284. the data directory has been changed to "/var/db/ntopng", and the
  1285. default user has been changed to "ntopng". This new directory is
  1286. created automatically by the port/package with correct permissions.
  1287. In order to maintain backward compatibility, if you are already
  1288. using "/var/tmp/ntopng" as data directory, ntopng keeps using that
  1289. folder, owned by "nobody". This said, using the old defaults is not
  1290. recommended and a manual action is required in order to migrate to
  1291. the new settings, unless you are already using a custom directory:
  1292. # service ntopng stop
  1293. # mv /var/tmp/ntopng/* /var/db/ntopng/
  1294. # chown -R ntopng:ntopng /var/db/ntopng
  1295. # service ntopng start
  1296. Please check the upstream FAQ for reference:
  1298. 20181218:
  1299. AFFECTS: users of misc/openhab2
  1300. AUTHOR:
  1301. If you upgrade from a previous version, make a backup of
  1302. /var/db/openhab2
  1303. and run
  1304. %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd
  1305. Config specific info (changes from 2.3.0 to 2.4.0):
  1306. Astro Binding: The 'kilometer' and 'miles' channels have been replaced
  1307. by a new 'distance' channel
  1308. Jeelink Binding: The 'currentWatt' and 'maxWatt' channels have been
  1309. replaced with 'currentPower' and 'maxPower' channels
  1310. WeatherUnderground Binding: A bridge has been added on top of the
  1311. current things, you need to add a bridge
  1312. containing your api-key.
  1313. ZWave Binding: Major changes have been merged to support features
  1314. such as security. All things must be deleted and
  1315. re-added. Refer to
  1317. for further information.
  1318. Synop Binding is now using UoM. 'wind-speed-ms' and 'wind-speed-knots'
  1319. channels have been replaced by a single 'wind-speed'
  1320. channel.
  1321. Amazonechocontrol Binding: The account thing does not have settings
  1322. anymore. You have to login at amazon
  1323. once again through the proxy server
  1324. http(s)://<YourOpenHAB>/amazonechocontrol
  1325. Milight Binding: The various available bulb types do not appear in
  1326. the Paper UI Inbox anymore. The correct bulb need
  1327. to be added manually. The bulb "zone" is now a
  1328. configuration. Bulb Things need to be recreated
  1329. to apply this change.
  1330. Hue emulation: The item to hue ID mapping is no longer stored in
  1331. files, but in the openHAB storage service. You need
  1332. to rediscover "devices" in all services that use the
  1333. hue emulation (Amazon Echo, Google Home, etc).
  1334. 20181215:
  1335. AFFECTS: users of sysutils/graylog
  1336. AUTHOR:
  1337. The dependent ports for ElasticSearch and MongoDB have both changed,
  1338. and upstream changes to the configuration file may require minor
  1339. changes to work correctly. Refer to the new sample files installed
  1340. alongside the port for reference:
  1341. server.conf
  1342. log4j.xml
  1343. graylog_logging.xml
  1344. 20181213:
  1345. AFFECTS: users of lang/perl5*
  1346. AUTHOR:
  1347. The default Perl version has been switched to Perl 5.28. If you are using
  1348. binary packages to upgrade your system, you do not have anything to do, pkg
  1349. upgrade will do the right thing. For the other people, follow the
  1350. instructions in entry 20161103, it should still be the same.
  1351. 20181212:
  1352. AFFECTS: users of net-im/ejabberd
  1353. AUTHOR:
  1354. There are some new features added in ejabberd 18.12, esp. related to
  1355. bookmarks, and XML compression in message archive storage. Please
  1356. refer to:
  1357. 20181211:
  1358. AFFECTS: users of news/inn when upgrading to FreeBSD 12
  1359. AUTHOR:
  1360. When upgrading from FreeBSD 11 to 12, a change in the size of the
  1361. ino_t type causes a binary incompatibility in the overview database
  1362. if the default tradindexed format is used.
  1363. After upgrading the inn package, remove the overview/group.index
  1364. file and regenerate the history and overview database with
  1365. makehistory(8) before starting innd.
  1366. # echo '. /usr/local/news/lib/innshellvars && \
  1367. rm -f $OVERVIEWDIR/group.index && \
  1368. $NEWSBIN/makehistory -O -s `wc -l <$HISTORY`' | \
  1369. su -fm news -c '/bin/sh -s'
  1370. 20181209:
  1371. AFFECTS: users of DRM ports other than graphics/drm-kmod
  1372. AUTHOR:
  1373. In order to facilitate future porting efforts and help in supporting multiple
  1374. FreeBSD versions, the DRM ports other than drm-kmod (graphics/drm-stable-kmod,
  1375. graphics/drm-next-kmod, graphics/drm-devel-kmod) have been renamed to
  1376. include the FreeBSD version they are designed for.
  1377. drm-stable-kmod is drm-fbsd11.2-kmod
  1378. drm-next-kmod is drm-fbsd12.0-kmod
  1379. drm-devel-kmod is drm-current-kmod
  1380. 20181209
  1381. AFFECTS: users of devel/geany and devel/geany-plugins
  1382. AUTHOR:
  1383. Geany and its plugins port have been moved to gtk3 and a new gtk2
  1384. flavor has been added. The gtk2 flavor has a -gtk2 suffix added to the
  1385. package name.
  1386. If you want to stay with the gtk2 version you need to use "pkg install"
  1387. to install the new gtk2 flavor, pkg will automatically deinstall the
  1388. gtk3 flavors.
  1389. If using port, to maintain the gtk2 version, you will need to deinstall
  1390. geany and its plugins and reinstall specifying the gtk2 flavor.
  1391. Note that the following plugins are not available if using the new
  1392. gtk3 flavor:
  1393. * geany-plugin-debugger
  1394. * geany-plugin-devhelp
  1395. * geany-plugin-geanypy
  1396. * geany-plugin-multiterm
  1397. * geany-plugin-scope
  1398. 20181208:
  1399. AFFECTS: users of misc/openhab2
  1400. AUTHOR:
  1401. If you upgrade from a previous version, make a backup of
  1402. /var/db/openhab2
  1403. and run
  1404. %%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd
  1405. Config specific info (changes from 2.2.0 to 2.3.0):
  1406. Nest Binding: The 'camera' Thing Type now has channel groups.
  1407. Add 'camera#' before the channel ID in the channel UID of
  1408. existing camera channels. The 'time_to_target_mins' channel
  1409. of the 'thermostat' Thing Type is renamed to 'time_to_target'
  1410. Oceanic Binding: The 'softener' Thing Type no longer exists and is replaced
  1411. by the 'serial' and 'ethernet' Thing Types
  1412. Yamaha Receiver Binding: The configuration parameter names now use lower
  1413. camel case convention. Change 'HOST' to 'host',
  1414. 'PORT' to 'port' etc
  1415. 20181124:
  1416. AFFECTS: users of sysutils/munin-master, sysutils/munin-node, www/owncloud, mail/mailman, net/ntpa
  1417. AUTHOR:
  1418. The newsyslog.conf(5) filename installed by the port has been changed:
  1419. OLD: ${PREFIX}/etc/newsyslog.conf.d/${PORTNAME}
  1420. NEW: ${PREFIX}/etc/newsyslog.conf.d/${PORTNAME}.conf
  1421. Any file found at the old location will be automatically moved to the new
  1422. location. This will ensure log rotation will continue to work after change
  1423. r340318 to FreeBSD base, where the default newsyslog configuration now only
  1424. includes filenames that end with '.conf' and do not begin with '.'.
  1425. If you use provisioning/configuration management tools to create or edit this
  1426. file, you will need to change their configuration to use the new filename.
  1427. 20181111
  1428. AFFECTS: users of graphics/mesa-libs
  1429. AUTHOR:
  1430. Wayland support has been enabled in ports where it doesn't exclude
  1431. X11 support in order to make the binary packages usable with Wayland
  1432. compositors. If you get strange build failures re-run "make config"
  1433. to pick up the new defaults. If the extra dependencies are not
  1434. desired add the following to make.conf:
  1436. 20181109
  1437. AFFECTS: users of security/ossec-hids-server
  1438. AUTHOR:
  1439. The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable".
  1440. If using database output, you need to recreate database using new schema
  1441. provided in /usr/local/share/doc/ossec-hids.
  1442. 20181109
  1443. AFFECTS: users of security/ossec-hids-local
  1444. AUTHOR:
  1445. The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable".
  1446. If using database output, you need to recreate database using new schema
  1447. provided in /usr/local/share/doc/ossec-hids.
  1448. 20181109
  1449. AFFECTS: users of security/ossec-hids-client
  1450. AUTHOR:
  1451. The ossec-hids-client port has been renamed to ossec-hids-agent.
  1452. Portmaster users will need to run this command:
  1453. portmaster -o security/ossec-hids-agent security/ossec-hids-client
  1454. If the switch doesn't happen automatically for you, just delete the
  1455. ossec-hids-client package and install ossec-hids-agent.
  1456. The "ossechids_enable" rc variable has been renamed to "ossec_hids_enable".
  1457. 20181104:
  1458. AFFECTS: users of sysutils/ansible*
  1459. AUTHOR:
  1460. Default Ansible configuration location changed to LOCALBASE/etc/ansible
  1461. instead of a per-flavor directory. If you use system-wide Ansible
  1462. configuration, please migrate from a flavored directory to a common
  1463. one:
  1464. # mv /usr/local/etc/py27-ansible /usr/local/etc/ansible
  1465. 20181031:
  1466. AFFECTS: users of www/node
  1467. AUTHOR:
  1468. The www/node port has been updated to Node.js v11.0.0, the latest
  1469. upstream release. A new port, www/node10, has been created for the
  1470. v10.x LTS branch. Users wanting to stay on v10.x can replace www/node
  1471. with www/node8 with one of the following commands:
  1472. # pkg install www/node10
  1473. or
  1474. # portmaster -o www/node10 www/node
  1475. or
  1476. # portupgrade -o www/node10 www/node
  1477. 20181022:
  1478. AFFECTS: users of lang/php71
  1479. AUTHOR:
  1480. The default version of PHP has been switched from 7.1 to 7.2.
  1481. If you use binary packages you should make a list of php packages
  1482. before running 'pkg upgrade':
  1483. # pkg info php7\* > ~/installed-php-ports-list
  1484. After the upgrade, check with such list if all your php extensions
  1485. are still installed, and reinstall them if needed.
  1486. If you use mod_php71 you need to deinstall it and install mod_php72.
  1487. 20181020:
  1488. AFFECTS: users of security/libressl
  1489. AUTHOR:
  1490. The port has been updated to the latest stable version 2.8 of LibreSSL.
  1491. The shared library versions of the libraries have been bumped.
  1492. After upgrading, manually update all packages that depend on any of the
  1493. libraries provided by LibreSSL (libssl, libcrypto and libtls) since the
  1494. versions of these libraries have changed. Normally, you can obtain the
  1495. list of dependent software by running the following command:
  1496. # pkg info -r libressl
  1497. Then you should rebuild all ports depending on libressl to avoid dangling
  1498. shared library dependencies. Poudriere and pkg handle this correctly,
  1499. portmaster and portupgrade users can use the following to rebuild all
  1500. dependent ports.
  1501. Portmaster users:
  1502. portmaster -r libressl
  1503. Portupgrade users:
  1504. portupgrade -fr security/libressl
  1505. 20181018:
  1506. AFFECTS: users of security/hitch
  1507. AUTHOR:
  1508. Hitch has been updated to run as the hitch user/group, instead of the
  1509. previous default of nobody/nobody. You should review your hitch
  1510. configuration to ensure that everything has been updated to reflect
  1511. this change.
  1512. 20181014:
  1513. AFFECTS: users of sysutils/ansible
  1514. AUTHOR:
  1515. Ansible has been updated to 2.7.0. Please follow the porting guide
  1516. to update the rulesets: