20141008: AFFECTS: users of lang/ruby19 AUTHOR: swills@FreeBSD.org The default ruby version has been updated from 1.9 to 2.0. If you compile your own ports you may keep 1.9 as the default version by adding the following lines to your /etc/make.conf file: # # Keep ruby 1.9 as default version # DEFAULT_VERSIONS+=ruby=1.9 If you wish to update to the new default version, you need to first stop any software that uses ruby. Then, you will need to follow these steps, depending upon how you manage your system. If you use pkgng, simply upgrade: # pkg upgrade If you use portmaster, install new ruby, then rebuild all ports that depend on ruby: # portmaster -o lang/ruby20 lang/ruby19 # portmaster -R -r ruby-2.0 If you use portupgrade, install new ruby, then rebuild all ports that depend on ruby: # pkg delete -f ruby ruby-iconv portupgrade # make -C /usr/ports/ports-mgmt/portupgrade install clean # portupgrade -x ruby-2.0.\* -fr lang/ruby20
20141003: AFFECTS: xorg users AUTHOR: bapt@FreeBSD.org The WITH_NEW_XORG setting has been activated by default on all versions of FreeBSD, which allows us to have packages for xorg 1.12 and kde4. Please be aware that on systems that only support syscons switching virtual terminals or exiting X results in a black screen or the last image of their desktop (like a screenshot) being presented. Commands can still be typed blindly. Most, if not all, systems should be using vt(4) and this can be enabled by setting kern.vty=vt in /boot/loader.conf and reboot to activate.
20141001: AFFECTS: xorg users AUTHOR: bapt@FreeBSD.org The WITH_NEW_XORG setting has been activated by default on FreeBSD 10.0 and above, which allows us to have packages for xorg 1.12 and kde4. Please be aware that on systems that only support syscons switching virtual terminals or exiting X results in a black screen or the last image of their desktop (like a screenshot) being presented. Commands can still be typed blindly. Most, if not all, systems should be using vt(4) and this can be enabled by setting kern.vty=vt in /boot/loader.conf and reboot to activate.
20140930: AFFECTS: users of mail/maildrop AUTHOR: madpilot@FreeBSD.org Due to the way pkg works please note that the configuration variables MAILDROP_SUID and MAILDROP_SGID, despite keeping their old names, are now required to contain a valid username and groupname existing on the system in which the package will be installed, while in the past numeric uids and gids worked fine. Wrong values will cause pkg to skip installing the setuid binaries on the system. Please check your configuration.
20140930: AFFECTS: users of finance/gnucash AUTHOR: madpilot@FreeBSD.org The new version of gnucsh requires guile 2.0. If the update fails because the old guile 1.8 library is still present you will need to manally remove gnucash, guile and, if installed, boehm-gc: # pkg delete gnucash guile boehm-gc and then install gnucash again the usual way.
20140929: AFFECTS: users of comms/usbmuxd AUTHOR: avilla@FreeBSD.org libusbmuxd.so was split from comms/usbmuxd into comms/libusbmuxd. Remove usbmuxd before upgrading to avoid conflicts: # pkg delete -f usbmuxd If you need the daemon usbmuxd(1), you can reinstall the package after the upgrade.
20140928: AFFECTS: users of deskutils/calibre AUTHOR: madpilot@FreeBSD.org The dependency on graphics/py-imaging in calibre has been changed to using the graphics/py-pillow port. Due to this change automatic updating of the port will not work correctly. It is suggested to remove calibre and py-imaging from the system and then reinstall calibre again using binary packages or ports.
20140927: AFFECTS: users of net/foreman-proxy AUTHOR: mm@FreeBSD.org In version 1.6 Foreman Smart Proxy splits its configuration into multiple ruby files located in PREFIX/etc/foreman-proxy/settings.d. The configuration of each service (dhcp, dhs, bmc, etc.) has been moved into a dedicated file. You can use a bundled script to convert your old settings to new settings: PREFIX/share/foreman/extra/migrate_settings.rb
20140926: AFFECTS: users of shells/bash AUTHOR: bdrewery@FreeBSD.org Bash supports a feature of exporting functions in the environment with export -f. Running bash with exported functions in the environment will then import those functions into the environment of the script being ran. This resulted in security issues CVE-2014-6271 and CVE-2014-7169, commonly known as "shellshock". It also can result in poorly written scripts being tricked into running arbitrary commands. To fully mitigate against this sort of attack we have applied a non-upstream patch to disable this functionality by default. You can execute bash with --import-functions to allow it to import functions from the environment. The default can also be changed in the port by selecting the IMPORTFUNCTIONS option.